problem in ALE Idoc

[Former Member]

Dear All,

We have transferred master data from one client to another using Ale - Idoc methodology. But it has been observed that complete master data not transferred to destination client.

Now I want to know how to find out missing information through standard method because it is not feasible to check line by line every master data.

Thanks,

Rameshwar.

[Former Member]

Dear All,

We have transferred master data from one client to another using Ale - Idoc methodology. But it has been observed that complete master data not transferred to destination client.

Now I want to know how to find out missing information through standard method because it is not feasible to check line by line every master data.

Thanks,

Rameshwar.

[Former Member]

down load the table entries into Excel from both systems and compare the records..

[Former Member]

Hi Rameshwar,

if it is master data it is hard to compare..

but you can do one thing...

use the FUnction module 'RFC_READ_TABLE' use get the table entries from remote system..

if it is table mara the erdat date field is there..Pass the condition into tables in the function module as the Options...pass erdat = sy-datum...

retrive the data and compare..

Regards,

Prabhudas

[Former Member]

First try to find out why it happened and try finding the same patten then things will be lot clearer.

[Former Member]

Hi,

First try WE02 for Failed IDOC's. For the MATMAS IDOC Type. You will be getting a better idea. If SAP is the Source and target system. You can compare WE02 Report on both the systems.

Thanks,

Mathivanan.G

[Former Member]

Hi,

First we have to check the segments for the IDOC in the sender system and then Receiver system, So comparing both Segements we can find out which all information is missing in Receiver system. You can check Material master data through MM03 transaction to compare.

Regards

Sathish

[Former Member]

Hi,

1) Please check if you have set any filtering mechanism in sender system that is restricting some IDocs to be sent.

2) Also go and check in WE02 how many IDocs have been sent in sender system and how many IDocs have been recieved in the reciever system

3) Check how many IDocs have gone into error in the receiving system.

I hope the issue will lie in any of the above scenarios

BR/Yogesh

[Former Member]

Hi,

When master data is distributed, interdependent objects are often distributed together. With serialized message distribution IDocs are created, dispatched and posted in a specific order. The interdependency of objects is at message type level and this avoids errors occurring during inbound processing of IDocs. Serialization groups in which the messages to be used and the posting order is specified, are used to distribute interdependent messages serially.

For example:

If you distribute materials and the material classes, they must be distributed together. You cannot process classification data in the receiver system, if this system does not also have the data of the material to be classified

Todo this......Follow the below steps

1) Define serialization groups

2) Assign Message types to the serialization groups

The distribution model should have all the message types defined in the serialization groups, add additional message type SERDAT