|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Serialization of IDOC Message type
Step 3 à
Define Inbound Processing
In this section you can make the settings for processing
inbound message types for a serialization group. These settings are made in the receiving system.
You can specify the size of the IDoc packet forwarded to the
application, whether the packet is transferred in parallel and what server group
For a serialization group containing materials and associated
classifications you can specify how the message types MATMAS (material) and
CLFMAS (classification) are processed.
For the message SERDAT processing in the inbound partner
profiles should be set to 'immediate
the SALE transaction select Define inbound processing as shown in the image
On the next screen click on NEW ENTRIES button and add the
details as shown below
the groups column mention the Serialization group name created in the first
step. Under the Message Type define the messages assigned to the Serialization
group. Under the sending system column enter the sending systems. If the data is
sent to more than one system then all these steps have to repeated for all the
individual receiving systems. Under the Object column enter the number of
objects per process. In our case we will use 1 per process.
Example: Number of objects (e.g. materials, vendors, customers) assigned to an
the Indicator: Parallel processing yes/no set the indicator as per your
requirement. Generally it is set to YES.
the indicator is set then the inbound processing of the application uses one
free dialog process for each IDoc packet on the application server
('asynchronous RFC' is used for this). This means that the packets can be
processed in parallel. If several IDoc packets have been selected, then the IDoc
processing will occupy all the dialog processes on the application server.
the indicator is not set then the IDocs will not be processed in parallel. This
means that each packet will passed to the application in turn. Only one work
process will be used for this action on the application server.
the RFC server group define the server which will be used by the transaction in
can check the server group from the transaction RZ12.
done save your entries.
Enable Change pointers in the system globally using BD61 transaction and also
for all the message types using the BD50 transaction.
pointer has to be activated to enable data distribution through Change
SETTINGS IN THE RECEIVING SYSTEM
you have completed the above steps in the sending system login to the receiving
system and do the following steps.
Maintain the serialization group as done in the above steps in the receiving
system as well.
Go to to the distribution model and select the model that was distributed from
the sending system. And from the menu generate the partner profile in the
receiving system. This step will create the partner profiles in the receiving
Change the partner profile settings for all the message types EXCEPT the SERDAT
message type to TRIGGER BY BACKGROUND PROGRAM
DO NOT CHANGE THE SETTINGS FOR THE SERDAT message type.
will have the option TRIGGER IMMEDIATELY.
these settings are done both the systems are now ready for distributing data in
a serialized order.
dispatch a serialization group two steps are required:
The IDocs belonging to a serialization group are created
These IDocs are then dispatched
two activities are scheduled as a periodic job in the sending system.
report RBDSER01 creates the IDocs for
a serialization group. The serialization group to be created is specified as a
parameter in this report. The report selects all the master data change pointers
assigned to this serialization group. The IDocs are then created from the change
the IDocs have been created the report RBDSER02
dispatches the IDocs belonging to a serialization group. The name of the
serialization group to be sent is specified as a parameter in this report. You
can also specify the receiving systems and in the time period that IDocs can be
report also schedules the report RBDSER03
which checks whether all the IDocs have been successfully sent to the receiving
system. If they have, a control message of message type SERDAT is sent to the
receiving system and posts the serialization group there. To do this specify in
the parameters of report RBDSER02 the time that should be scheduled after
sending report RBDSER03.
also have the option to always dispatch the control message. This means dispatch
it even if all the IDocs have not been passed to the receiving system. This
means that IDocs arriving in the receiving system can be processed even if some
IDocs are still being transferred. However, serialization difficulties may
can schedule reports RBDSER01 and RBDSER02 after each other in the same job
(choose SAP Menu -> Tools -> ALE -> ALE Administration -> Services
-> Periodic Processing -> Outbox -> Serialized Distribution Using
Message Types - SM36).
report RBDSER03 can be scheduled as an independent job. In this case you should
not enter the date and time.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards