Serialization of IDocs

Hello friends,
I have one question pertaining to serialization:
Does serialization depends only on the order of message type maintained in serialization group. Is the content of the IDoc also taken into consideration during processing.
Eg. Say I have serialization of 2 Idocs - ORDERS and MATMAS
a) MATMAS first followed by ORDERS.
b) I send 4 IDocs:
         - MATMAS IDoc containing material "Tube"
         - ORDERS IDoc having PO number 12 and material "Tube".
         - MATMAS IDoc containing material "Nail"
         - ORDERS IDoc having PO number 14 and material "Nail".
c) As we see above 1st two IDocs are dependent and so are the last two.
d) Now in the receiver system the IDocs are received as follows:
         - MATMAS IDoc containing material "Nail"
         - ORDERS IDoc having PO1: 12 and material "Tube".
         - MATMAS IDoc containing material "Tube"
         - ORDERS IDoc having PO2: 14 and material "Nail".
How will serialization behave in this case. Will the system wait for all the MATMAS IDocs be posted first and then continue the posting of ORDERS IDoc (as per serialization group)? What is the internal processing logic in serialization?
If the system uses the order (as in d above) to post IDocs (which is as per the serialization order also ignoring data) then it will lead to failure of 2nd IDoc (as the material IDoc for it comes later).
Appreciate your help/inputs in this.
Thanks.
Regards,
Gajendra.

Hi,
it means that IDOCs will be received in the order in which they were send - nothing more:)
have a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
BTW
you can find out more about serialization of IDOCS with XI
in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

Serialization of idoc

Hi ,
I have theoretically gained knowledge on SERIALIZATION of Idoc. I want it to implement in my project. Can anybody tell me the steps how to use serialization of Idoc for inbound process .If possible, give detail steps.
Regards
Abhishek

http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm
this will help u

How to serialize the IDoc of DEBMAS by time sequence?

Hi experts,
We want to transfer customer master data from one client to the other.
We have carried out the serialization distribution for message type DEBMAS
and actived the change point.
Scenario:
time 1 : We created one "NEW" customer 100436.
time 2 : We assigned the Head Office of "existed" customer100435 as 100436
The time of the distribution job was arrived,
the job started to run and failed to change "existed" customer 100435
even though "NEW" customer 100436 has created sucessfully.
We think the IDoc should be processed by time sequence,
but it seems not.
Did you think it is processed by customer key ascendence ?
How do we define the process sequence of the IDoc?
Any advice will be appreciated.
Regards,

But what if i want to check the format of date that my
database supports ?
Actually situation is :
I am making a form designer by which user will inset
date to a particular column. okay.
now the format of date must match with the underlying
format of database. Then only query will be
successfull. Is it not so.?No.
Basically you will be doing the following:
Browser -> java.util.Date
java.util.Date -> JDBC -> database
JDBC does the 'conversion' work for you, you just need to put it in the java.util.Date.
suppose database table-> column's format is
YYYY/DD/MM Databases don't store dates like that. They usually (probably always) store it as a signed integer value which is relative to a specific date/time.
When you use a database tool to look at the value the database tool converts it from the number to a format that looks familar to you.
and user enters date in the format
DD/MM/YYYY, then i will have show an error message to
the user that the format of date that he has entered
is wrong. No need for that.
The user does need to put the date in in a form that you understand. So you can convert it to a java.util.Date.
java.text.SimpleDateFormat can help with that.

What is the serialization concept in ALE/IDOC?

what is the serialization concept in ALE/IDOC?

Hi Srinu ,
IDoc Serialization means, sending/posting the idocs in sequence.
We serialize IDocs in the following cases:
· If you want the Integration Server to process the corresponding IDoc XML messages in the same sequence that it receives them from the IDoc adapter at the inbound channel.
· If you want the receiver to receive the IDocs in the same sequence that the IDoc adapter sends them at the Integration Server outbound channel.
The sequence at the Integration Server inbound or outbound channel can only be guaranteed if only IDocs are processed, and not if different protocols (for example, IDocs and proxies) are processed together.
Do not confuse IDoc serialization using the IDoc adapter with the ALE serialization of IDocs.
Prerequisites
· The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
· The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
Procedure
If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
· Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
· In the communication channel, select the check box Queue processing for the receiver.
The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
Serialization of Messages
Use
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
Prerequisites
IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
Features
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
· IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
· IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
Ex: ADRMAS, DEBMAS(customer)
ADRMAS, CREMAS(Vendor)
In this case, Before posting Customer Data or Vendor Data it requires Address Data.
Rgds
Sree m

IDoc serialization in XI

Hi Experts,
My scenario is Idoc to Idoc
SAP system (R/3)>XI> Legacy SAP
I need to do the serialization of IDoc i.e in what order the Idoc is sent from SAP system Xi should process the Idoc in same order(EOIO) for outbound scenario.
Can you please let me know the required steps i need to do in both SAP system and XI system to serialize the IDocs.
Please advice
Thanks in advance
Anku

Hi Anku,
-->If you want to send the idocs from application system to PI in the EOIO, you need to check the queue processing and maintain the RULE name in outbound partner profiles.
--> If you want to send the idocs from PI to target in the EOIO in the receiver IDOC adapter you need to check the check box queue processing.
-->You no need to perform any pre-configuration steps if your system is based on WAS 6.40 and above.
-->The RULE which you defined at WE20 need to assign the function module and in the FM you need to maintain the QUEUE name.
For" Idoc to Idoc" outbound scenario we have to do the following steps for Serialization of Idoc
the above steps which you mentioned are perfect.
Thanks

HRMD_A IDoc Serialization Help

Hi,
I have a client that wants to activate IDoc serialization for HRMD_A. They have a global system that sends HR master data to multiple regional systems, MDM and SRM.
The requirement is to serialize the IDocs for all regional systems, but not for MDM or SRM.
My understanding is that we would need to activate both outbound and inbound serialization through SALE->Modelling and Implementing Business Processes->Configure Predefined ALE Business Processes->Human Resources->Master Data Distribution->Serialize HR Master Data.
We would activate outbound in the global sending system, and inbound in each regional target system, but not in MDM or SRM.
By activating serialization, will it activate for HRMD_A only, or for HRMDA_ABA as well?
We would then need to make sure that the serialization counters are all initialized in both source and target systems. We can do this with transactions RE_RHALE_HRMDRGOUT and RE_RHALE_HRMDRGIN.
Please correct me if any of the above is incorrect?
Once serialization is activated, how will this effect the system? If for example an IDoc is sent with 100 objects, and one fails, then what status will the IDoc go into? Will all other objects process correctly? How would the error object affect subsequent IDocs?
What steps need to be taken in order to resolve the following potential IDoc errors:
- Change for person xxxxxxxx extends too far into past
Delete IDoc? What to do with counters?
- Object 01 ,z ,xxxxxxxx does not exist: infotype 1001 cannot be created.
Resend missing objects with PFAL and then reprocess IDoc?
- Relationship starting from 01 y xxxxxxxx impossible u2013 01 w zzzzzzzz does not exist/is not active.
Resend missing objects with PFAL and then reprocess IDoc?
- Personnel number xxxxxxxx is locked
Will this sort itself out, or do we need to manually reprocess the Idoc?
- Payroll area yy is locked for master data maintenance.
Reprocess the IDoc after payroll areas is unlocked?
Thanks very much for your help
Edited by: David Bann on Sep 22, 2011 4:52 PM

Hi,
If change pointers are to be written for custom fields then the change document flag at the domain level should be checked for that field. Then maintain an entry for this field in transaction BD52. Object name will be the same as the original fields. Changes to custom fields will be only picked if the change document for such fields is maintained in table BDCP.
Try now!
Reddy

Serialize ---- Proxy to Idoc scenario

Hi Folks,
I m using Proxy to Idoc scenario and am trigerring proxy messages one after other from my function module on the outbound side. However sometimes idoc2 gets posted before idoc1.
My requirement is that idoc2 to be processed only after idoc1 is successfully posted. Where and how do I serialize the idoc processing?
--- AKJ

Hi,
This issue is basically at ur receiver IDoc side, when its getting processed.
To ensure, ur IDoc 2 gets processed only after IDoc 1, changes can be done during message mapping.
During mapping, inside control records of target IDoc, there is an 'serial' field. Fill this 'serial' field with a new unique number which increases with each and every new IDoc creation.
This serial field with increasing number will be used during processing of IDocs in a sequence.
Refer SAP Note - 752194 & 152239 for more details..
Please let me know if still there are any issues.
Thanks,
Anoop

Multiple Idocs (DEBMAS/ADRMAS) with SERDAT serialization to PI

Hi All,
I have a requirement that R3 systems sends data by means of serialization Idocs SERDAT basically which has two Idocs DEBMAS/ADRMAS. I need to generate a single structure at target side out of two incoming Idocs (DEBMAS/ADRMAS).
Could any one please advise me how can i extract data from two idocs in a single scenario?
Is there any standard approach already for this.
Thanks in advance.
Regards,
Prasad Babu.

You can achieve the scenario by using ALE Serilization at IDOC Message Type
The below example addresss a similar scenario but for MATMAS material master and CLFMAS classification .
Search for "Serialization by IDOC Type" . The first link will give you the insight. (I am unable to post the link here..)
After the IDOC's come to PI, you can have a BPM to co-relate (DEBMAS/ADRMAS using Customer / Contact Numbers) and create a single Outout message.
- Siva Maranani
Edited by: Siva Maranani on Nov 9, 2009 10:09 PM

Serialization of XI's outgoing messages (IDocs)

Hi guys,
We have a file->IDoc scenario. Each line of source file produces an IDoc. What values should we put to SERIAL node of target message (IDoc) to ensure correct proessing? Should it be a numeric value? Alfanumeric?
Thank you, Olian

Hi,
My understanding is that, you will provide a timestamp in XI .
Then module IDOC_SERIALIZATION_CHECK (in inbound process code) update the entry in BDSER table for a key field of IDoc.
Table BDSER - "Serialization Time: Last Date at Sender for Each Object".
Set up serialization via tcodes:
BD57 - assign serialization object to the message type
BD95 - assign a segment field to serialization object
Idocs processed by RRBDAPP01 are sorted by SERIAL (timestamp), then table BDSER is updated.
Regards,
Jakub

File splitting and idoc serialization into XI

Dear experts,
I am brand new with XI so please be indulgent with my following question.
We have to define a new inbound interface with R/3 (4.7). We also have XI 3.0 into our landscape.
The legacy system will send us a flat file whose lines will all have the same structure. The first part of the files is aimed at creating a FI posting into R/3. The second part of the file is aimed at creating a CO posting. This CO posting has to be created after the FI posting.
I would like to know whether it is possible for XI :
1) to split the input flat file into 2 "files" (one for FI posting, the other for CO posting)
2) to create 2 idocs : one for FI posting and one for CO posting
3) to serialize those idocs into R/3
Thank you in advance for your help.
Regards,
Fabrice

Hi Fabrice,
this may help you....
File to Multiple IDocs
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
also see File splitting
Re: splitting of messages using BPM
Re: splitting of messages using BPM
regards
biplab
**reward points if u find it is useful

When IDoc Serialization is required ?

Hello,
IDoc's are serialized in master data distribution.
When IDoc serialization by IDoc adapter is required and also when ALE serialization of IDoc's is requried?
Is it necessary to tune on both of the above at the same time or any one?
In which scenario both serialzation technique is tuned on?
Please shed me some lights on this with business cases.
Regards,
Thiyagu

Hi,
Please check this link for example program.
http://help.sap.com/saphelp_nw04/helpdata/en/78/2175a751ce11d189570000e829fbbd/content.htm
Also, check out
Checkout
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm
http://www.sapfans.com/forums/posting.php?mode=quote&p=383070&sid=3907f12b866299cc7e2e3e9728674ef3
Check if the above links helps...
Regards,
Swetha.

Idoc serialization for vendor and address master

Hi friends,
My gole is to transfer vendor master data from one sap ecc system to other ecc through PI.
I have achived this but the gmail and address data is not transfering as this is not a part of vendor master but even this address data need to passed to receiver system when ever there is change and creation of vendor.
Then i refered note Note 752194 - Serialization of IDoc processing and few threads in sdn ..
i am trying to do this serialization but i am facing issues to trigger idocs.
first this is the way we need to achive this.
if so adrmas is of type bapi so how can we group using Serialization Group of mesage type ..
guide me how to achive this.
And my vendor message type is customized one with zcremas_Xxx.
Regards
Vijay
Edited by: vijay Kumar on Dec 16, 2010 6:48 AM

Hi Vijay,
I am not sure whether you are active in SDN or not. I need your help in IDOC serialization
I have the same requirement like you here I need to Post ADRMAS and CREMAS. I am able to generate both the idocs succefully but the ADRNR is not assigned to the created Vendor. I might be missing something in config or in code.
Please reply to this thread and help me.

IDOC DATA in F110

Hi All,
We are trying to send the data of F110 from R/3 to PI system by using 2 IDOC types EUPEXR and PAYTEXT.
We are receiving the IDOC's in the PI system but, we would like to have the data of the IDOC type EUPEXR and PAYTEXT, where as we are getting the PAYTEXT idoc first and EUPEXR next.
We tried to implement the serialization of Idoc Message type technique, but we are receiving the both the IDOcs in the PI system with same type stamp.
Can anyone suggest us how do we avoid this such that we always receive the EUPEXR idoc first and PAYTEXT idoc second in the PI system...
Thanks,
Rajesh.G

Hi
Why are you picking the Idocs based on TimeStamp?
We are also using simliar process with PI as middleware but we are not facing any issues?
Let me know what is the requirement and where does these idoc finally go and get updated?
Regards
Jyo

Doubt in Sender IDoc Adapter

Hi Gurus
I have doubts regarding the sender IDoc adapter.The sender IDoc adapter is present by default and we do not create manually. the qos of this is EO by default.
How can we change the QOS of the sender IDoc adapter? do we have to maitain any settings on the R/3 side, please explain??
thanking you

Dear Abhinav,
Check my comments in this forum thread:
[IDOC Serialization|Re: IDOC Serialization in PI]
Regards
Praveen K

Customer Master IDOC

Hi all,
I am new to IDOCS. And i have some knowledge regarding the same. Now i had a requirement to send as well as obtain customers from other system.
So can i know how can i procceed. Please can any body explain me step by step how to do In-bound and Outbound fro the Customer master. And also the problems we are going to face.
Thanks and Regards,
sagar

Hi,
Do make the ale set up as per the previous posts....
Pondering over the problems that you might face, as you had asked for might be any of the following....
1. Idocs might not get generated, i.e., 0 communication IDocs would be generated in which case you need to re-check the distribution model configuration.
2. If IDocs are generated, they might fail in any of the error status (status 02, 26, 29 - outbound or status 60, 51, 56 - inbound) in which case you would have to rectify the error according to the status text and then reprocess the IDocs using the standard programs, RBDMANI2, RBDAGAIN based on their present status.
3. Idocs might stay in yellow status(unprocessed IDocs - status 30 (outbound) or 64 (inbound)) in which case you would have to recheck the partner profile configuration and then push the IDocs via programs RSEOUT00 or RBDAPP01 respectively.
6. In case if you tend to use serialization of IDocs, IDocs might fail in 66 status(inbound) at which point of time, you need to check with the serialization.
These are a few normal cases.......you might come across a few weird ones to.....
~ Bineah.

Serialization of IDocs

Similar Messages

Maybe you are looking for