Inbound ORDERS05 will not get processed.

[Former Member]

I customized an Inbound IDOC ORDCHG ORDERS05, the process code used is ORDC, this inbound ORDERS05 is automatically created via an outbound IDOC ORDCHG ORDERS05, application EF Message type a Z... (marked as change) and Process code ME11. The Outpbound ORDCHG is triggered by a change of the purchase order. The outbound IDOC is created perfectly, the Inbound IDOC is created as well. This means, to my opninion, that all partner settings are ok otherwise there will be no inbound IDOC. The problem is, that the IDOC is created and gets status 50 "IDOC added" first which is normal, the next status is 64 "IDoc ready to be transferred to application" which is ok as well, but then the latter status is 50 again which isn't correct, and it stays for ever that way

The message is "Status set to '50' during IDoc inbound processing" Message no. EA705.

Diagnosis

The status was set so that the IDoc interface is compatible with earlier releases. Processes could check IDocs for status '50'.

Reprocessing of the IDOC isn't possible due to the status 50. Tried program BD87, and program RBDAPP01.

When I copy the IDOC to WE19 and process it with FM "IDOC_INPUT_ORDCHG", in the background it is processed correctly. When I process the IDOC in the foreground and press as many times entries untill the last code is reached the sales order gets update correctly, no errors. When processing in the foreground after error, you never know, the sales order gets updated as well.
Even when I change the partner to trigger by background the 3 status will be the same, tha last one is 50. At this moment I don't have a clue what the reason is.

[Former Member]

I customized an Inbound IDOC ORDCHG ORDERS05, the process code used is ORDC, this inbound ORDERS05 is automatically created via an outbound IDOC ORDCHG ORDERS05, application EF Message type a Z... (marked as change) and Process code ME11. The Outpbound ORDCHG is triggered by a change of the purchase order. The outbound IDOC is created perfectly, the Inbound IDOC is created as well. This means, to my opninion, that all partner settings are ok otherwise there will be no inbound IDOC. The problem is, that the IDOC is created and gets status 50 "IDOC added" first which is normal, the next status is 64 "IDoc ready to be transferred to application" which is ok as well, but then the latter status is 50 again which isn't correct, and it stays for ever that way

The message is "Status set to '50' during IDoc inbound processing" Message no. EA705.

Diagnosis

The status was set so that the IDoc interface is compatible with earlier releases. Processes could check IDocs for status '50'.

Reprocessing of the IDOC isn't possible due to the status 50. Tried program BD87, and program RBDAPP01.

When I copy the IDOC to WE19 and process it with FM "IDOC_INPUT_ORDCHG", in the background it is processed correctly. When I process the IDOC in the foreground and press as many times entries untill the last code is reached the sales order gets update correctly, no errors. When processing in the foreground after error, you never know, the sales order gets updated as well.
Even when I change the partner to trigger by background the 3 status will be the same, tha last one is 50. At this moment I don't have a clue what the reason is.

[nabheetscn]

Can you Please add some screen shots of your partner profile setting for inbound idoc, for example how to process once inbound idoc is received and status logs of the idoc in question.

Nabheet

[chaouki_akir]

How is the inbound IDOC created automatically (via an outbound IDOC ORDCHG ORDERS05) ? Is there some SAP customizing point to activate ? Or some specific coding ?

[Former Member]

Hi there,

This issue is solved. Cause: The process codes of the partner type KU customer and supplier type LI was correct ORDC, but the process code of the partner type LS was SD03 (should be ORDC as well), this leads to an unexpected behavior as explained above of the IDOC.

Sorry for the late reaction, I didn't receive the response from you in my own E-mail.

This Issue can be closed.

[Former Member]

Hi Chaouki AKIR,

This is a very specific process solved with almost 99% standard SAP.

Just to answer your question, this is a process where a purchase order (outbound IDOC) triggers an inbound Sales Order (Inbound IDOC), due to the fact that we use the same port for inbound and outbound, the sales order gets created automatically in the same system as the created purchase order.

The process or requirement was that a supplier will be charged with a % of the purchase price (statistical in the sales order), so the purchase order price was added to the outbound IDOC and some fields like the purchasing payment terms where removed because these will be different from that of the sales order. The % to be charged is defined with VK11. So we used the standards of SAP for 99% (no specific IDOC segments ORDERS05) and it works like a charme.