cancel
Showing results for 
Search instead for 
Did you mean: 

How to enable serialization group for update classification data in MATMAS through Inbound interface

0 Kudos

Hi Friends,

The is regarding inbound interface of material master. Business wants to update classification data as well. To update both information we need to map both MATMAS and CLFMAS message type. Another message type SERDATA is required to process these message types(This is my understanding)

I did the following setup in ECC.

I have done the setting required under SALE transaction.

1. Define Serilization groups

2. Define inbound processing

Added all the 3 message types in we20 under inbound section. and

set "Trigger Immidiately" under section processing by function module for SERDAT message type.

set "Trigger by background program" under section processing by function for MATMAS and CLFMAS message types.

Is there any other steps required to complete this ?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Santosh,

i have a similar requirement now for CREMAS and ADRMAS idocs. I did the same cofiguration in SALE and WE20 as you did.

Please tell me the other steps and coding practice which need to follow here.

Appreciates your help.

Thanks,

Srinivas.

Former Member
0 Kudos

Please read the following regarding serialization. It is from an official SAP documentation. So you can trust the information contained in it

Serialization in the inbound:

This type of serialization is available as the default. The prerequisite for it is that inbound processing is set to "Trigger by background program" and that you use the RBDAPP01 report to process the IDocs.

The RBDAPP01 report sorts the IDocs that are to be processed according to the following criteria before processing them:

     1.  Partner number of the sender

     2.  Partner type of the sender

     3.  Partner function of the sender

     4.  Message type

     5.  Logical message variant

     6.  Logical message function

     7.  Test indicator

     8.  Serialization field

This type of serialization does not require any Customizing settings or technical adjustments to the program.

More Info that is also helpful:

There are various procedures for processing IDocs in a serialized way. Depending on your respective requirements, one of the proposed methods may be more suitable, or may not be suitable at all for the required purpose.

Note that the IDoc number is not suitable as a serialization characteristic. The number range server assigns the numbers in ranges to the individual application servers. Therefore, in systems that has several application servers, it is very likely that IDocs that have lower numbers will be saved in the system later than IDocs that have higher numbers. Likewise, certain numbers may not be assigned because of number buffering.

Serialization using message types (serialization groups)

Serialization using serialization groups is used if several different message types are dependent on each other. Therefore, for example, you can assign classes to material masters in logistics. However, it does not make sense to generate this assignment if the definitions of the material masters and  classes are not up-to-date. For this reason, the message types involved (MATMAS, CLSMAS and CLFMAS) are grouped together in a serialization group, in which the processing sequence is defined.

How does serialization using groups work? Serialization in the sending system

·     In the sending system, check whether there is a serialization group in which the required messages are   available in the necessary sequence (transaction BD44).

      In the distribution model, maintain a distribution of the SERDAT message type for all target systems to which you want to distribute the messages.

·    The outbound partner profile in the sending system should be set to 'Collect IDocs' for the message types in question. For the SERDAT message type, the output mode should be set to 'Transfer  IDoc immediately'.

·    You can use the RBDSER01 report to generate IDocs for the message types of a serialization group. This creates the relevant Idocs  from change pointers. You can use the RBDSER02 report to send the IDocs. If required, you can use this report to create the control message SERDAT, which is to trigger processing in the receiving system. If you only want to create a control message, use the  RBDSER03 report.

Serialization in the target system

·     

C   Check whether the required serialization group also exists in the  target system.

·    Maintain the inbound settings for all message types of the  serialization group. (Transaction SALE: Modeling and Implementing   Business Processes   > Master Data Distribution   > Serialization for Sending and Receiving Data   > Serialization using Message  Types).

1.      1. If you leave the field 'Object/Process' empty, the IDocs are transferred separately to the inbound  function module of the  application, which can result in long runtimes.

2.     

         2.  If you do not select the field 'Parallel', the inbound function module is called in the current work process. The IDocs are processed one after the other.

3.       3. If you select the field 'Parallel', parallel processing is used for each package. Since this only concerns the processing of IDocs for a message type, serialization is not compromised.

·         You must set the inbound partner profile for all message types involved to "Trigger by background program".

·         Set "Trigger immediately" and the process code SERD for the  SERDAT message type. In any case, the inbound processing of SERDAT must trigger the processing of further IDocs indirectly.

·       

          Make sure that no jobs that also select the serialized message  types are scheduled for the RBDAPP01 and RBDSER04 reports.

Alternatively, when you start inbound processing with the SERDAT message type, you can also use the RBDSER04 report to transfer IDocs to the application.

·         Specify a variant and a serialization group.

·         Restrict the logical sending systems where necessary.

·         If possible, schedule the program for a time when the system workload is low. The settings (TBD41)   are taken into account in processing. If you have set parallel processing, processing is executed in several dialog work processes.

Hope that helps you complete your configuration

JL23
Active Contributor
0 Kudos