3357946 - Incorrect Action codes in the API Purchase Order

Incorrect Action codes in the API Purchase Order – Send, Update, Cancel (OrderRequest_Out)

SAP S/4HANA Cloud 2302

1. Scheduling is not supported for EDI channel Outputs.

This happens because:

• EDI channel follows asynchronous communication and does not expect scheduling.
• Scheduling supressed the past changes in the purchase orders. In this case, the initial EDI output for the purchase order creation gets supressed, and the first message that the supplier receives is an update of the purchase order, and this purchase order does not exist in the supplier system.

2 . Manual output generation from Purchase order Apps cannot guarantee correct Action codes.

Determination of the Action codes are highly dependent on the output history of system generated EDI messages.

When business user adds a Manual Output Request Item , that output request item is slightly different from that of the system generated  output request items and therefore incorrect Action codes could be the result.

Hence It is highly recommended to

1. Not to send Manual Output for EDI Channel, but instead rely on the system generated outputs whenever you do a change in the Purchase Order. ( How to send a system generated Output ? For eg. You may do a ‘Dummy change’ on a Print relevant field of the purchase order which doesn’t affect the communication to the supplier )
2. If at all the business user happen to send the Manual Output, in such cases please ignore the Action code values.

1-If you only have EDI output configured in the system, then

• Schedule the output with Dispatch Time as Immediately instead of Scheduling in the app Output Parameter Determination.

2- If you are using all channels like Print and Email along with EDI, and if you need to SCHEDULE output for PRINT and EMAIL, as there is no possibility for configuring at the channel level as a work around, the user will have to opt for the below option to set EDI output frequently.

• The user can use ‘Schedule Release of Purchase Order Outputs’ App to send the EDI output request frequently.

For more information on Schedule Release of Purchase Order Outputs App:

Cloud Link

OnPremise Link

Steps to be followed in the Schedule Release of Purchase Order Outputs App.

1-Login with Configuration Expert user (for Cloud) / a user with a role -SAP_BR_BPC_EXPERT assigned (for OnPremise).

2-Open the Schedule Release of Purchase Order Outputs App

3-In below screen – Click on ‘Create’

4-In Step1 - Select the Job Template as ‘Schedule Purchase Order Output’ and give a Job Name – ‘EDI_JOB_IMMEDIATE_RUN’

5-Click on Step2 – we mention the occurrences, here we need to change the Recurrence Pattern to every Minute using the ‘Define Recurrence Pattern’

According to requirement we can opt the pattern. Here we are choosing ‘Minutes’.

Once the Minute pattern is selected, we need to provide the duration as below:

Post these settings, below are data is shown in the scheduling options.

6-In Step 3, Provide the parameter Output channel as EDI and if require the user fill the other Purchase Order Data parameter and then click on ‘SCHEDULE’ button.

7-Once the above steps are created, we will be able to see job name which is expected to run every minute.

Please note:  This resolution is a work around to set the EDI schedule application jobs to the smallest Pattern recurrence of 1 minute (equivalent to immediate execution). But it does not guarantee that the output results will always be the same as that of the Dispatch time option as ‘Immediate’. Whenever the user has a choice, it is advised to opt for Dispatch time as ‘Immediate’ for EDI channel.

Resolution of Cause 2 ( Manual Output Generation Case)

 In case, one needs to retrigger an EDI output for any reason whatsoever and neither can Action codes be ignored, in such a scenario, we recommend to perform a print relevant change to the Purchase Order so that a system generated EDI output is triggered and therefore the triggering of manual output can be avoided.

KBA , MM-PUR-GF-EDI , Electronic Data Interchange , Problem