Definicja serialization effect

Potential consequence of a faulty queue entry when making a transfer using a queued Remote Function Call (qRFC). For transfers using qRFC, the system adheres strictly to the sequence of the objects transferred (serialization), in contrast to a transactional Remote Function Call (tRFC).

The serialization principle also applies if different queue entries are processed for this queue in different logical units of work (LUWs). For example, this can be the case if you make a number of changes at different points in time for an order in the ERP system. Due to the queue name, these orders are contained in the same queue and are therefore subject to serialization. However, since the postings were made at different points in time, the corresponding queue entries are contained in different LUWs.

If a queue has a faulty queue entry, subsequent queue entries can also not be transferred. This leads to a queue block. A queue block does not just affect the LUW containing the faulty queue entry, but rather all LUWs containing subsequent queue entries. This is called the serialization effect.

Example

You change order XY in the ERP system and post this change. The change is to be transferred to SAP APO. The change (A) leads to a queue entry with the queue name CFXY, which belongs to the LUW A because of the time when it was posted. You then change order XY again and post this change (B). This change also leads to a queue entry with the queue name CFXY, but this belongs to LUW B. There is an error when change A is transferred that leads to LUW A being blocked. The serialization effect means that change B cannot be transferred either, which also causes LUW B to be blocked.