cancel
Showing results for 
Search instead for 
Did you mean: 

Article IDoc not getting processed in PI for particle article type

former_member205100
Participant
0 Kudos

Hello All,

I have an strange behaviour in my system.

i.e 1, we are creating an article IDOC by using BD10 for particulat article type.

2, IDOC created succesfully , then

3, Process the IDOC in BD87 to push the IDOC to PI system .

4, But i could not see the message in PI that too only for one article type.

I'm wondering why this is not getting processed only for one article type and not for others.

we also checked the basic filter for the message type in dist model and even i could not see any condition in PI also,

Is there any thing else i should check? can you please help us on this.

Regards , Sethu.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi,

Please refer bellow steps:

First you need to check status of idoc by using t.c we05/we02 on R3 Sys

If status is Success(03) , you need to check RFC Monitoring by using t.c SM58 on R3 Sys

If there is no issue in Sm58,you need to check Inbound QUEUE by using t.c SMQ2 ON PI Sys.

former_member205100
Participant
0 Kudos

Hello All,

Thanks for your input,

I cheked in SM58 and i found this error "EDISDEF: Port SAPFCR segment defn Z2MD_E1BPEMARABO M001001 in IDoc type ZM"

when checked at the segment definition it looks fine and no inconsistence on the segment, also i cheked in we20 with the IDOC type version its also 4.0 so not sure where is the error?

is this with segment or idoc type or somewhere else?

BR, Sethu.

PriyankaAnagani
Active Contributor
0 Kudos

Hi,

Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.

Regards,

Priyanka

former_member205100
Participant
0 Kudos

Thanks a lot for all your guidance.

The issue is now resolved , as said I just reimported the metadata in IDX2 and after that it got processed .

once again thanks for all.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Along with the points mentioned by Grzegorz, also check in transaction SM58 in ECC side for errors.

Reg,

former_member184681
Active Contributor
0 Kudos

Hi,

Try debugging the process from the source:

1. Is the IDoc created in ECC for that one particular article type? Can you see it in we02 or similar tool?

2. Is the RFC connection established successfully (no errors in sm58)?

3. Can you see your IDoc in IDX5 in PI?

4. Can you see your message in sxi_monitor in PI? Are there any errors?

Let us know about the results for further help,

Greg