frePPLeOpen source Production Planning
  • Home
  • Documentation
  • C++ API

OpenERP connector module

FrePPLe provides an integration with the OpenERP, a leading open source ERP. The connector provides the following functionality:

  • Two-way integration:
    • Synchronizes the frePPLe database with items, locations, bill of materials, routings, resources, sales orders, customers, inventory, production orders, purchase orders from OpenERP.
    • Uploads new production orders and/or purchase orders from frePPLe to OpenERP.
      Optionally the commitment date of sales orders can be uploaded as well.
  • Uses the XMLRPC API to access OpenERP.
  • For optimal performance the connector allows net-change download. Only the objects that have been created or changed in OpenERP within a certain time frame are extracted.
  • You can still maintain additional data in the frePPLe user interface. I.e. OpenERP doesn’t need to be the only source of data for your model.
  • Easy to customize.

The integration contains 2 parts:

  • An additional Django application to be deployed in the frePPLe web application.
    It contains the commands to pull data from OpenERP and push results back to OpenERP.

  • An OpenERP module that defines extra models, fields and screens in OpenERP.
    It is used to allow frePPLe-specific input information to be maintained in OpenERP.

The integration is based on OpenERP v6 and requires the following modules to be installed:

  • mrp
  • mrp_subproduct
  • sale
  • sale_order_dates

Configuring the frePPLe web application

  • Copy the application folder
    The folder contrib/openerp/openerp needs to be copied to contrib/django/freppledb (orcustom/freppledb when you used the Windows installer).

  • Edit the file djangosettings.py
    The following settings need updating:

    • INSTALLED_APPS: Add (or uncomment) freppledb.openerp in the list of applications.
  • Configure the following parameters:
    • openerp_url: URL for the XML-RPC server
    • openerp_db: OpenERP database to connect to
    • openerp_user: OpenERP user for the connection
    • openerp_password: Password for the connection

    If you use the syncdb command to initialize the database, the parameters will be created automatically. Otherwise you can create them manually.

  • You are now ready to synchronize the frePPLe database with OpenERP.
    Issue the command:

        frepplectl openerp_import

    The following optional arguments can be provided:

    • openerp_url: URL for the XML-RPC server. Overrides the parameter with the same name.
    • openerp_db: OpenERP database to connect to. Overrides the parameter with the same name.
    • openerp_user: OpenERP user for the connection. Overrides the parameter with the same name.
    • openerp_password: Password for the connection. Overrides the parameter with the same name.
    • user: frePPLe user running the command
    • delta: Number of days for which we extract changed OpenERP data. Older data is expected to be already in frePPLe and are no extracted again. The default value is 3650, meaning that all data is extracted.
    • database: The frePPLe database to load the data into. Only relevant for configurations with multiple frePPLe databases.
  • When the frePPLe plan is ready, you can bring the results back to OpenERP with the following command:
       frepplectl openerp_export

    The following optional arguments can be provided:

    • openerp_url: URL for the XML-RPC server. Overrides the parameter with the same name.
    • openerp_db: OpenERP database to connect to. Overrides the parameter with the same name.
    • openerp_user: OpenERP user for the connection. Overrides the parameter with the same name.
    • openerp_password: Password for the connection. Overrides the parameter with the same name.
    • user: frePPLe user running the command
    • database: The frePPLe database to load the data into. Only relevant for configurations with multiple frePPLe databases.

    Implementation of this command is in progress.

Configuring the OpenERP module

The module can be installed as a regular extension module.

It extends OpenERP with the following capabilities:

  • Add setupmatrix as a new model.

This module is currently in development and not ready.

    • Getting started
      • 1 – Introduction
      • 2 – Installation
      • 3 – Entering data
      • 4 – Modelling concepts
      • 5 – Your first model
      • 6 – Your first plan
    • Modeling guide
      • Simplified domain model
      • Detailed domain model
      • Environment variables
      • Python interpreter
      • Global parameters
      • Buffer
      • Calendar
      • Customer
      • Demand
      • Flow
      • Item
      • Load
      • Location
      • Operation
      • Suboperation
      • Operationplan
      • Problem
      • Resource
      • SetupMatrix
      • Skill
      • Resource skill
      • Solver
    • User guide
      • Supported browsers
      • Getting around
        • Logging in
        • Logging out
        • Changing password
        • Navigation
          • Menu bar
          • Jump search
          • Context menus
        • Filtering data
        • Sorting data
        • Selecting time buckets
        • Exporting data
        • Importing data
        • Customizing a screen
        • User preferences
        • User permissions and roles
        • Comments
        • History – Audit trail
      • Data maintenance screens
      • Supply Path / Where Used
      • Plan analysis screens
        • Problem report
        • Constraint report
        • Inventory report
        • Inventory detail report
        • Resource report
        • Resource Gantt report
        • Resource detail report
        • Operation report
        • Operation detail report
        • Demand report
        • Demand detail report
        • Demand Gantt report
        • Forecast report
        • Performance indicator report
      • Execution screen
      • Batch commands
        • frepplectl
        • frepple
        • freppleservice.exe (Windows only)
    • Installation guide
      • Windows installer
      • Compiling on Windows
      • Linux binary packages
      • Compiling on Linux
      • Compiling from the source code repository
      • Running the VMWare virtual machine
      • Other platforms
      • Configuring multiple models in the user interface
      • Configuring as a Python extension module
    • Extension modules
      • Forecast module
      • Order quoting module
      • REST web service module
      • OpenERP connector module
      • Linear programming solver module
    • Technical guide
      • Architecture
      • Source code repository
      • User interface
        • Creating an extension app
        • Translating the user interface
        • Adding or customizing a report
        • Style guide
      • Solver engine
        • Code structure
        • Class diagram
        • Planning algorithm
          • Top level loop
          • Demand solver
          • Buffer solver
          • Flow solver
          • Load solver
          • Operation solver
          • Resource solver
        • Cluster and level algorithm
        • Extension modules
        • Style guide
        • Portability
      • Security
      • Unit tests
        • buffer_procure_1
        • calendar
        • callback
        • cluster
        • constraints_combined_1
        • constraints_combined_2
        • constraints_leadtime_1
        • constraints_material_1
        • constraints_material_2
        • constraints_material_3
        • constraints_material_4
        • constraints_resource_1
        • constraints_resource_2
        • constraints_resource_3
        • constraints_resource_4
        • constraints_resource_5
        • datetime
        • deletion
        • demand_policy
        • flow_alternate_1
        • flow_alternate_2
        • flow_effective
        • forecast_1
        • forecast_2
        • forecast_3
        • forecast_4
        • forecast_5
        • forecast_6
        • jobshop
        • load_alternate
        • load_effective
        • lpsolver_1
        • multithreading
        • name
        • operation_alternate
        • operation_available
        • operation_effective
        • operation_pre_post
        • operation_routing
        • pegging
        • problems
        • python_1
        • python_2
        • python_3
        • safety_stock
        • sample_module
        • scalability_1
        • scalability_2
        • scalability_3
        • setup_1
        • setup_2
        • skill
        • xml
        • xml_remote
    • FAQ
    • License
      • GNU Affero General Public License
      • GNU Free Documentation License
    • Third party add-ons
  • Copyright © 2010-2013 frePPLe bvba