From their README:

FrePPLe is an easy-to-use and easy-to-implement open source advanced planning and scheduling tool for manufacturing companies.

FrePPLe implements planning algoritms based on best practices such as theory of constraints (ie plan around the bottleneck), pull-based planning (ie start production as late as possible and directly triggered by demand) and lean manufacturing (ie avoid intermediate delays and inventory).

More on FrePPLe: https://frepple.com

uzERP is an open source ERP system focused on UK SME/Owner managed businesses. It delivers big company functionality on a small company budget, including accounting, stock, manufacturing and more.

The FrePPLe connector for uzERP allows uzERP users to import sales orders, work orders, stock position, structures, operations, etc. into FrePPLe Community Edition and generate proposed purchase and work orders. The connector provides complete two way integration including the export of proposed orders back to uzERP for execution. Proposed orders can be exported en mass, respecting a time-fence, or individually.

More on uzERP: https://www.uzerp.com

If you run FrePPLe using a python virtualenv, as we prefer to do, you can use pip to install the connector. You can also follow the setup.py method.

Install using pip:

$ pip install git+https://github.com/uzerpllp/uzerpfrepple.git

Install using setup.py:

Clone or download from github, then run setup.py

$ python uzerpfrepple/setup.py install

If you installed FrePPLe from binary packages, you will need to prefix the above command with sudo to install it system-wide

The frepple schema is included in the schema folder with the connector software. The frepple.sql file assumes that you have created a DB role called 'frepple' when installing the FrePPLe application and will be using that with the uzERP connector.

The schema can can be added to the uzERP database using the PostgreSQL client by running the following command:

$ sudo -u postgres psql < /<path-to-connector>/schema/frepple.sql <uzerp-db-name>

Grant the frepple role the permissions it needs to write to the uzERP database when exporting planned orders back to uzERP:

$ sudo -u postgres psql < /<path-to-connector>/schema/frepple-grants.sql <uzerp-db-name>

Note: you will need to replace <path-to-connector> with the location where you downloaded the connector to. <uzerp-db-name> is the name of your uzERP database

Once the connector is installed it is configured by adding additional settings to FrePPLe's djangosetting.py file, located at /etc/frepple/djangosettings.py for binary package installations.

# FrePPLe djangosettings.py

# uzERP database connection settings
UZERP_DB = {
	'NAME': 'uzerp',
	'USER': 'frepple',
	'PASSWORD': 'xxx',
	'HOST': 'localhost',
	'PORT': ''
}

# uzERP connector settings
UZERP_SETTINGS = {
	'EXPORT': {
		'wo_documentation': ('26', '9'),
			# Database id's of the uzERP work order
			# documentation injector classes
		'wo_release_fence': 2,
			# Planned purchase orders due to start after this
			# number of days from today will not be exported
		'po_release_fence': 2
			# Planned purchase orders due to start after this
			# number of days from today will not be exported
	}
}

# Add the uzERP connector
INSTALLED_APPS = (
	...
    # Add any project specific apps here
    'uzerp',
	...

# uzERP Frepple authentication backend (optional)
#
# Authenticate frepple user logins against the uzERP database.
# Users must be assigned to a uzERP role with the name 'frepple'
# and the user must have also been creted in the frepple application.
AUTHENTICATION_BACKENDS = ['uzerp.uzerpauth.uzerpAuthBackend']

The uzERP connector adds two tasks to FrePPLe's Execute menu:

• Import data from uzERP (erp2frepple)
• Export data to uzERP (frepple2erp)

These tasks can also be run from the command line, e.g.:

$ frepplectl.py erptofrepple

Data from uzERP is imported via a number of PostgreSQL views under the frepple schema in the uzERP database. The connector retrieves the data from these views, creating a set of CSV files, then runs FrePPLe's importfromfolder command to import them.

See below for more detail on the mapping of data from uzERP to FrePPLe

For both Manufacturing and Purchase Orders, orders are only exported if they have a proposed status and their start date falls within the time-fence defined in the connector configuration. Order status in FrePPLe is changed to approved after exporting.

As well as using the execute task to export all proposed orders to uzERP, individual orders can be selected and exported from their list in Frepple. Look for the 'Select action' button in, say, Manufacturing Orders and select 'Export to uzERP'. The time-fence settings are ignored for individual exports.

For Manufacturing Orders, the connector selects the operation plan for routing type operations in FrePPLe and creates a matching work order in uzERP, at status NEW, for each requirement. Each work order will have the documents defined in the djangosettings.py configuration.

Purchase orders from the operation plan are created in uzERP as potential, individual order lines and are viewed in the Review Planned screen. From there they can be grouped as required and turned into actual purchase orders.

Table: uzERP/Frepple Data Mapping

Locations are modelled at the uzERP Store level and named using the store code

Note: this connector has not been tested on windows