Semantic Compression of Back-End
Keys
The data exchange between the back-end systems and the Data Orchestration Engine (DOE) can be triggered either by the back-end system or the DOE. In case of back-end triggered replication, when a user modifies the data in the back-end system, the back end sends the instance keys to the DOE. After the DOE receives the instance keys, the Get Detail BAPI wrapper obtains the corresponding instances from the back end and transfers them to the DOE. If an instance is modified repeatedly in the back end within a short period of time, the instance keys are transferred to the DOE for each modification. As a result, the Get Detail BAPI wrapper is called to obtain each modified instance. This increases the load on the network and as a result reduces performance. To reduce the load on the network and improve performance, you can perform semantic compression on the back-end keys.
Purpose
Semantic compression ensures that if an instance is modified repeatedly in the back end within a short period of time, only one instance key is stored for all the modifications. As a result, the Get Detail BAPI wrapper is not called for each modification. Instead, it is called only once for all the modifications that are performed on that single instance. This reduces the load on the network and as a result improves performance.
To ensure semantic compression of back-end keys, you need to schedule a background job for the required back-end business object. In the background job, you need to specify the interval after which the Get Detail BAPI wrapper must obtain the modified instances from the back end.
This interval must not be long because the purpose of semantic compression is to ensure that the Get Detail BAPI wrapper is not called for each modification within a short period of time.
Behavior
When the back end sends an instance key along with the task (INSERT, UPDATE, DELETE) and back-end business object to the DOE, a function module is called to check if a background job is scheduled for the corresponding back-end business object. If a background job is scheduled, the instance key is stored in the semantic compression table and the message exits the flow. If an instance is modified repeatedly in the back end, only one instance key is stored in the semantic compression table for all the modifications. When the background job is executed, the Get Detail BAPI wrapper obtains the modified instances from the back end for the instance keys stored in the semantic compression table.
If a background job is not scheduled for a back-end business object, then the Get Detail BAPI wrapper obtains the instance from the back end immediately and transfers it to the DOE.
More Information