Show TOC

 Serialization Effect

This is a potential consequence of a faulty queue entry during a data transfer using queued remote function calls (qRFC). When using qRFCs for a data transfer, the system adheres strictly to the sequence of objects to be transferred (serialization), in contrast to the transfer using transactional remote function calls (tRFC).

Serialization also applies if queue entries from different logical units of work (LUWs) are being processed in this queue. For example, this could be the case if a number of changes are made for an order in the ERP system at different points in time. The changes are in the same queue due to the queue name and they are therefore subject to serialization. However, since the postings took place at different points in time, the corresponding queue entries are in different LUWs.

If a queue contains a faulty queue entry, the subsequent queue entries are not transferred either. This leads to a queue block. A queue block not only affects the LUW containing the faulty queue entry, but also all LUWs containing subsequent queue entries. This effect is called the serialization effect.


A confirmation is issued for a production order with goods movement. This affects the material ROH1. The action leads to the following entries:


CFPLO 0815 xxxxxx



The first entry in LUW 1 is faulty and is not transferred. This also blocks the subsequent entries in this LUW.

Shortly afterwards, a goods issue is posted for delivery that also concerns material ROH1. The action leads to the following entries:


CFSLS 4711




Entries with the same queue names (in this case CFSTK ROH1) may only be transferred in serial. This means that entry CFSTK ROH1 in LUW 2 cannot be transferred if entry CFSTK ROH1 is blocked in LUW1. All entries in LUW 2 are also blocked.