Serialize messages

Example scenario: Webshop integration to SAP
Customers ¹⁾ and webshop orders are to be transmitted to the host system in such a way that the correct serialization sequence is ensured.
This means that for new customer installations or changes, the customer data should be processed first before the orders can be created.

Required eBiss components:

1. Creating a Counter
2. Create value provider
3. Lookup table types
4. Value Tables
5. NextCounterValue()
6. AddLookupKeyValue()

As soon as a business partner is to be created or changed, a counter value is determined in the first mapping (WebshopOrder to BusinessPartner).
This value is transferred to the corresponding target data element (here @SERIAL) in a predefined format.
Then the counter value is entered with the order ID into the previously defined recoding table (here 'Serializer').
This makes the counter value available in another mapping.

As a secondary condition, the first mapping checks whether a new creation or change of the business partner is required. If not, this mapping returns no result and no lookup is created.

In the second step, the previously determined counter value with the order ID is again read from the recoding table, incremented by 1 and passed to the target data element with the same formatting.
Here it is still checked whether a new creation or change of the business partner is necessary at all.
If this is the case, the lookup must also return a result.
If the business partner is already known according to the WebShop Order and does not need to be updated, no lookup can be done and only a counter value is resolved as in the first mapping.