12-21-2006 6:35 PM
12-21-2006 6:41 PM
Hi Uday,
Welcome to SDN.
IDoc Serialization:
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).
For more information, please check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
Hope this will help.
Regards,
Ferry Lianto
12-21-2006 6:45 PM
Hi Uday,
Welcome to SDN.........
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.
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
<b> IDOC_SERIALIZATION_CHECK</b>
checks the time stamps in the serialization field of the IDoc header.
<b> IDOC_SERIAL_POST</b>
updates the serialization table.
Serialization status of IDOC is represented with No.66 as a status of IDoc is waiting for predecessor IDoc (serialization)
Check these links for Serializations
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66c9507d11d18ee90000e8366fc2/content.htm
Thanks,
Vinay