1. Home
  2. Help Center
  3. Integrations
  4. Requirements and configuration for MONITOR ERP

Requirements and configuration for MONITOR ERP

Requirement for MONITOR ERP 

The integration requires a G5 version of MONITOR ERP, and the API module must be activated.  

The API must be accessible from the CRIBWISE Cloud meaning that incoming https-calls to the API originated from CRIBWISE Cloud IP-address must be accepted. This may require firewall configurations at customer side.

It’s also recommended to setup a specific API-user in MONITOR ERP to use for the integration. 

To be able to create Purchase Orders in MONITOR ERP via integration a default coding (account) must be configured for “Free order rows”. This configuration is performed in MONITOR settings. 

The API user must have the following access rights: 

  • Show supplier 
  • Show purchase orders 
  • Show order types 
  • Show company information 
  • Show part 
  • Show chart of accounts 
  • Show dimensions/dimension codes 
  • Create new purchase order 
  • Modify purchase order 
  • Report arrival of purchase order 
  • Show currencies

Currency settings

The system currency in CRIBWISE must match the default purchase currency in MONITOR ERP. If multiple purchase currencies are used in CRIBWISE, each currency must also exist in MONITOR ERP. Currencies are matched by currency code (ISO).

Configuration 

Before the integration can be used it must be configured. The configuration is made from CRIBWISE Administration Portal from the menu Administration – Integration. If the integration addon is activated for the customer a menu-option will be displayed like in the picture below.  

When selecting the menu item, a new blade will be displayed from which configuration and verification of the integration is performed. The blade also contains a tab for the execution log. 

Settings to configure – General 

Name  Mandatory  Comment/Description 
MONITOR G5 API – Base url address  Yes  Base address of the MONITOR server.
More info: https://api.monitor.se/articles/v1/url.html 
MONITOR G5 API – Language Code  Yes  The language code specifies the language that the API will scope the request to which means that any language-dependent functionality will use this language when processing. 

The value is case-insensitive and must be a valid ISO-639-1 (two letter) language code.
More info: https://api.monitor.se/articles/v1/url.html 

MONITOR G5 API – Company Number  Yes  A company number is the compound of a database number and company id.  

The database number is a numeric string that identifies the MONITOR database that you are targeting. The company id is currently always 1. 

<database-number>.<company-id> 

Ex. 001.1 

More info: https://api.monitor.se/articles/v1/url.html 

MONITOR G5 API – Username  Yes  The username to use when connecting to the MONITOR API.
More info: https://api.monitor.se/articles/authentication.html 
MONITOR G5 API – Password  Yes  The password to use when connecting to the MONITOR API 

More info: https://api.monitor.se/articles/authentication.html 

  

 

Settings to configure – Workflow level 

Name  Mandatory  Comment/Description 
MONITOR G5 – Purchaseordertype Number  Yes  Specifies the order type to set on the purchase orders. 

The human readable identifier of the order type. This number is found in MONITOR ERP Settings. 

MONITOR G5 – Warehouse Code  No  If multiple warehouses is used in the MONITOR ERP system and the Cribwise PO:s must be assigned to a specific warehouse, then the id (code) of this warehouse is assigned here.
More info:
https://www.monitorerp.com/media/6597/
product_sheet_g5_warehouse_en.pdf
  
MONITOR G5 – Supplier Code for Verification  No  A supplier code to use when verifying the configuration settings. The supplier must exist. 

If this is specified, then the integration verification procedure will execute the PO Create Command with the /Validate option to verify the input data without actually creating the PO.
More info:
https://api.monitor.se/articles/v1/commands/simulate-validate.html 

CRIBWISE – Exclude orders created before  No  This can be used to filter out “old” orders created in the past. Orders that for some reason should not be included in the synchronization.
If specified, this setting is used to exclude Purchase Orders created before the specified date. It matches against the PO Order date attribute 
CRIBWISE – Suppliers to Synchronize  No  This can be used to specify which vendors (suppliers) should be included in the synchronization to MONITOR ERP. 

The suppliers (vendors) to include is specified in a comma separated list of CRIBWISE Vendor IDs (MONITOR ERP Supplier codes). 

If the list is empty, all Vendors will be included in the synchronization. 

Example: 1001,1023,1131
During integration verification the value list will be checked to see if all IDs exists in CRIBWISE and in MONITOR. 

CRIBWISE – Set Item Description as MONITOR PO Row Sub Content  No  If checked, then the purchased Item’s Description text is set as Sub Row content on Purchase Order row in MONITOR.
The setting applies to all Purchase Orders synchronized to MONITOR. 

 

After the configuration is set, it’s recommended to test the settings by clicking “Save and test configuration”. This saves the configuration and executes the verification.   

The status and information of the Verification is shown on a new blade to the right. 

If everything looks ok the integration can be activated meaning that the synchronization will start. Purchase orders created or updated after the Activation is done will be synchronized. 

 

 

Status of synchronization 

If there are errors in the synchronization, then those will be displayed in the execution log (Event log). If the log contains errors or warnings from the latest 24h hours there will be an indicator icon displaying this at workflow level. See picture below. 


The event log also shows every successfully executed synchronization as an information entry.   

Was this article helpful?

Related Articles