Continuous synchronization of Build, Produce and Inspect with SAP Business One

Some data from your ERP system is continuously synchronized with Cloud Apps. For the different applications, separate synchronizations need to be started.

Synchronization only starts if all prerequisites are met.

For synchronization upon first initialization, see Synchronization with the ERP system - First synchronization.

Every 4.5 seconds, the Cloud Apps synchronization engine checks if any new events happened in your ERP system that must be synchronized to Cloud Apps.

This is done by querying the U_BOY_CLOUD_WAREHOUSE (for inventory transaction events) and U_BOY_CLOUD_NOTICE (for all other events) services using the SAP Service Layer. A maximum of 50 events of each type are queried every time.

These queries are lightweight, as they consist of a very limited amount of information, essentially the object type, object key and transaction type.

Even when no events are created in SAP Business One, the Cloud Apps synchronization engine still polls both events services every 4.5 seconds.

The events are added to the U_BOY_CLOUD_WAREHOUSE and U_BOY_CLOUD_NOTICE tables by the stored procedure that is installed automatically by the Cloud Apps Installer add-on or installed manually. (For details on manual installation, see Creating stored procedures in the SAP Business One database - HANA and Creating stored procedures in the SAP Business One database - MS SQL.)

If an event is detected, then it is removed from the SAP Business One event services, and forwarded for processing to each Cloud Apps application that requires the given event type. Cloud Apps will then perform further queries to the SAP Service Layer when processing the events.

If the Cloud Apps synchronization engine fails to connect to the SAP Service Layer while querying the events, then the SAP Business One connection is considered disconnected from Cloud Apps. In that situation:

• users of Cloud Apps will see a message informing them that the connection to SAP Business One is lost, and
• the Cloud Apps synchronization engine tries to connect to the SAP Service Layer every minute instead of the standard 4.5 seconds.

When the connection to the SAP Service Layer is working again, users are allowed back to Cloud Apps, and the events are checked again every 4.5 seconds.