Serialization of IDOC Message type

By Vijayendra Krishnamurthy Rao, Hewlett-Packard

Serialization for Sending and Receiving Data

With serialized message distribution, IDocs are created, sent and posted in a specific order. This prevents errors occurring when inbound IDocs are processed. Interdependent messages can be distributed serially in different ways, as described in the following sections.

  • Serialization Using Message Types

  • Serialization Using Business Objects

In this Tutorial we will learn Serialization using IDOC Message types and the details steps involved.

Serialization Using Message Types

When master data is distributed, interdependent objects are often distributed together (for example, purchasing info record is distributed with vendor and material). With serialized message distribution IDocs are created, dispatched and posted in a specific order. The interdependency of objects is at message type level and this avoids errors occurring during inbound processing of IDocs. Serialization groups in which the messages to be used and the posting order is specified, are used to distribute interdependent messages serially.

Example

If you distribute materials and the material classes, they must be distributed together. You cannot process classification data in the receiver system, if this system does not also have the data of the material to be classified. For this reason materials should be included with the associated classifications in a serialization group. To use serialized distribution you must carry out the following steps in Customizing:

Steps to be followed: -

  • Define Serialization Groups

  • Assign Message Types to the Serialization Group

In addition to the message types used, the dispatch of the message type SERDAT must be modeled in the distribution model.

STEP 1 à Define Serialization Groups

In this section you create serialization groups and assign message types and the processing order to each group. Both the sender and the receiver of the serialization group must know the assignments. This means this step needs to be carried out in both the receiving system and the sending system.

Serialization groups are required to distribute interdependent objects together so that they are processed in the correct order.

Example

The message types MATMAS (material master) and CLFMAS (classification) are assigned to a serialization group for dispatching materials and their accompanying classifications. The message type MATMAS is assigned the suffix 1 and the message type CLFMAS the suffix 2, so that the materials are processed first and then the classifications.

Create serialization group: Goto IMG à Modelling and Implementing Business Proccess àMaster Data Distribution à Serialization for sending and Receiving data à Serialization using Message types and click on DEFINE SERIALIZATION GROUPS

On the next screen Choose 'New entries' in the view 'Serialization groups' to add a new entry, In our case we will just modify one of the existing groups provided by SAP.

We will modify the existing group GRP_MATMAS – Material Master Complete. So select the group from the list and Place the cursor on a serialization group and choose 'Assign message types to serialization group'.

Click on the Change/Display button and Select 'New entries'. In our case we will add one more message type in this group. The message type to be added is CLSMAS. After adding the new entry we need to adjust the sequence of serialization if required.

Enter the message types used and add a sequence number for each one.

Save your entries.

Further notes

The message types in a serialization group are processed in ascending order of the sequence number added. You can also leave spaces between the individual numbers. (For example: 1,2,4,10,20).

If the serialization group is to be dispatched later a setting must be made so that the outbound IDocs are collected and inbound processing is carried out in the background for all message types. This is set under Partner Profiles -> Generate Partner Profiles. You can also make these settings in the SAP Menu for each partner profile and message type (choose ALE -> ALE Administration -> Services -> Runtime Settings -> Partner Profiles).

Step 2 à Maintain Distribution Model

Maintain the Distribution model as per the requirement and add the additional message type SERDAT as shown in the screen shot below.

Note: The distribution model needs to have all the message types that will be distributed between systems. It however need not have all the message types defined in the Serialization groups.

Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image