IDOC serialization

[former_member190313]

Hi Experts

Could any one tell me what is IDOC serialization / ALE Serialization.?

Could anyone provide any links on this topic

Regards

Sheetal

[Former Member · Accepted solution]

Hi,

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

Thnx

Chirag

[Former Member]

Hi Sheetal,

IDoc Serialization means, sending/posting the idocs in sequence.

Ex: ADRMAS, DEBMAS(customer)

ADRMAS, CREMAS(Vendor)

In this case, Before posting Customer Data or Vendor Data it requires Address Data.

There is a SAP Note (752194), which explains clearly about Serialization.

If you are not able to find the SAP note, let me know. I will send.

Regards,

Naveen

[former_member600110]

Hi Naveen,

I need a detailed document of idoc serialization and the end to end configuration steps to achieve this requirement. Could you please send me that link and also about idoc bundling if possible?

Thanks in Advance,

Praveen Kumar.

[aashish_sinha]

Hi,

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.

Hope this clarify you.

Regards

Aashish Sinha

PS : reward points if helpful