topic Inbound IDoc creation for basic type PORDCR103 : Error in Application Development and Automation Discussions

Inbound IDoc creation for basic type PORDCR103 : Error

former_member203070 — Sat, 23 May 2015 18:55:58 GMT

Hi experts,

When I'm creating PO using inbound IDoc (PORDCR103), getting data from local file as input, there was no issue with POs where only 1 line item exists per PO.

But whenever there are multiple line items for single PO, there I'm getting error in IDoc.

The reason is very simple, as I'm populating the E1BPMEPOITEM and E1BPMEPOITEMX segment one after another in loop, there the Error IDoc segment is like below.

The same thing is applicable for schedule line segment as well.

So if any how I could manage to keep all the E1BPMEPOITEM one after another and then all E1BPMEPOITEMX.. likewise then my issue would resolve.

Like in the below sequence:

E1BPMEPOITEM

E1BPMEPOITEMX

E1BPMEPOSCHEDULE

E1BPMEPOSCHEDULEX

Please help me with your valuable inputs....

FYI.. the error status is '60' and error details as below:

Re: Inbound IDoc creation for basic type PORDCR103 : Error

jitendra_it — Sun, 24 May 2015 12:30:48 GMT

Hello Partha,


When I'm creating PO using inbound IDoc (PORDCR103), getting data from local file as input, there was no issue with POs where only 1 line item exists per PO.

But whenever there are multiple line items for single PO, there I'm getting error in IDoc.

If it is inbound scenario then why you are populating segments. Just create partner profile and standard FM will get called that will process idoc.

If you are working on outbound then you can refer FM ALE_INB_DELIVERY_SAVEREPLICA

and check how standard is populating idoc SHP_IBDLV_SAVE_REPLICA04 in that FM.

Idoc SHP_IBDLV_SAVE_REPLICA04 contains same structure as idoc PORDCR103.

Here you can refer standard is populating segments

E1BPIBDLVITEM

E1BPIBDLVITEMORG

E1BPDLVITEMSTTR in sequence.

Hope this helps you.

Re: Inbound IDoc creation for basic type PORDCR103 : Error

former_member203070 — Sun, 24 May 2015 14:08:10 GMT

Hello Jitandra,

You are correct, I only used the standard FM: IDOC_INPUT_PORDCR1 and standard basic type: PORDCR103 for inbound IDoc process to PO conversion.

But.. here my requirement is to get data from presentation server's file (local file within ECC not from any other system), so I have to collect the file data and populate IDoc segments.

Here I populated IDoc segments and used FM: IDOC_INBOUND_WRITE_TO_DB from my standalone programe, fyi.. all the partner profile setting have been set correctly.

Re: Inbound IDoc creation for basic type PORDCR103 : Error

jitendra_it — Mon, 25 May 2015 04:58:45 GMT

Ok got your scenario

For segment population part as I have mentioned in previous reply you can check the FM ALE_INB_DELIVERY_SAVEREPLICA.

Idea is to populate idoc segments in the same sequence as those appears in WE30 so that syntax check failure can be avoided.