Serialization by Message Type

Use

IDocs can be created, sent and posted in a specified order by distributing message types serially.

Object interdependency is important at the message type level.

Consider a purchasing info record with a vendor and a material.  To avoid any processing errors, the vendor and material must be created in the receiving system before the purchasing info record.

Prerequisites

You have to activate serialized distribution of message types in both systems in ALE Customizing.

ALE IMG (transaction SALE)

   Model and Implement Business Processes
    Configure Master Data Distribution
      Set-Up Data
for Sending and Receiving Serialization
        Serialization by Message Type

Features

Serialized distribution is only used to transfer changes to master data. IDoc message types are assigned to serialization groups according to the order specified for their transfer. Master data is distributed in exactly the same order. If all the IDocs belonging to the same serialization group are dispatched successfully, the sending system sends a special control message to the receiving system. This control message contains the order IDocs are to be processed in and starts inbound processing in the receiving systems.

Serialized distribution of message types is not a completely new way of distributing master data; it uses existing ALE distribution mechanisms whilst adhering to a specified order of message type. This distribution could also be carried out manually using existing ALE programs. However, serialized distribution automates the single steps and can schedule them in a batch job.

In the serialization menu selection criteria determine how certain parts of the serialized distribution will be processed, for example, control message dispatch and inbound processing. This includes sending the control message and the inbound processing of the IDoc.