Production Idoc Issue - Change pointers

[Former Member]

Hi Experts,

Need your suggestion on the below issue.

I have a Production Idoc issue. Last week there was a Go-Live in my project .

Nature  of the issue :

Whenever a BOM is created, or changed, Idoc gets triggered through change pointers. Change pointers for zbommat message type has been activated.

Idoc generated in ECC will be sent to middleware systems. In middleware more than 300 idocs gets failed due to the missing of E1STPOM Item segment.

with the help of test data, i have debugged the code in Development. In development, whenever an Item data for a material has been changed, logs are captured in change pointers and Item segment E1STPOM segment is populated in Idoc. i have debugged the same in Development. I am getting the expected output.

Based on the failure of production data, i have analyzed the issue. Ex. An Idoc 123 has a material '345'. With the help of the material no,Idoc created date, and the message type, i have searched in WE09. WE09 shows the list of Idocs. In the list, i can see, for a same material, 3 docs were generated. Among the three, one idoc has a item segment, and the other two idoc doesn't have the item segment. The Idoc with a Item segment is a valid one for our functionality. In development, only single idoc gets generated for a change in material. The issue is how come multiple idocs are generated in production ?

I dont know how to proceed my analysis, because in Development the same scenario is not occuring. Please help me on this.

[Former Member]

hello,

Few questions and a suggestion -

Questions -

1) are the Idocs with blank E1STPOM segments generated before the Idoc with correct E1STPOM segment ?

2) is there any specific logic incorporated for the change pointer creation ?

3)

Suggestion -

In your zbommat have you made the segment E1STPOM mandatory ?

best regards

swanand

[Former Member]

Hi,

1) Idocs with Correct E1STPOM segment got generated in the middle (Among the 3 Idocs, 2 one is the correct Idoc. First and third idoc doesn't have an e1stpom segment. )

2) I have checked the code in debugging. I couldn't find any special logic for change pointers.

E1STPOM  is not a mandatory segment. In ECC side, all the idocs were successful. But in middleware, e1stpom is a mandatory segment. Business is asking how come three idocs got generated ?

Thanks and Regards

Siva.

[surya_prakash18]

Hi Siva,

1) I guess multiple IDoc's generated because of distribution model configuration.

2) For missing segment E1STPOM, check any segment filters used.

Regards,

Surya