HASH verification

The Connector can suppress the delivery of unchanged objects  to FSM. ‘Unchanged’ here means that objects remains unchanged from FSM perspective only. As the Connector transfers a certain subset of all available information to the FSM, it is common that data that have changed belongs to the irrelevant category and should not cause updates in FSM.

 This is done to:

• Limit network traffic (not only from backend to FSM but mostly from FSM to mobile devices)

• Limit system load related to actual sending objects to message broker

• Limit the risk of synchronisation conflicts which occurs when the same object is, in parallel,  updated in the  backend and FSM

The solution relies on the HASH calculated for Idocs messages and algorithm is following:

1. Connector calculate HASH for created IDOC

2. Compares the value with value stored in /PACG/ECM_AHASH table

3. If values are the same processing is terminated

4. If not object is sent to FSM and new value is stored in /PACG/ECM_AHASH

This is why sending reports have the option ‘Force sending’. When it is enabled HASH check is ignored