1, Background

New inbound SOAP API is provided to API Hub. This asynchronous inbound service enables you as the supplier using SAP S/4HANA Cloud to automatically receive and update delivery schedules of sales scheduling agreements. It is based on the SOAP protocol with namespace http://sap.com/xi/EDI/Supplier.

This service enables the following operations for delivery schedules of sales scheduling agreements:

· Receive schedule lines

· Create schedule lines

· Update schedule lines with revised quantities and dates

2, Error Handling

Due to incorrect configuration or master data, inbound message processing would be stopped, and error message would be persisted in message monitoring tool. You need to launch the application of ‘Message Dashboard’ to correct the message.

3, Trouble shooting

Here you can proceed the correction according to below messages and procedures.

Purpose

On the Message Dashboard, you can analyze the deployed log.

Procedure

1. Log on to FLP and navigate to Message Monitoring tab. Open the Message Dashboard.
2. Choose Sales SchedgAgrmt process integration – /SDSAR
3. Choose All Messages to check all relevant AIF messages.
4. Below error messages are usually displayed in message dashboard.

4, Message Handling

Delivery schedule type &1 is not supported

Diagnosis:

The system uses two release type in sales scheduling agreement:

· Forecast Schedule release

· JIT Schedule release

System Response:

The system stops processing the EDI message

Procedure:

Please provide Delivery Schedule type JIT or FRC in Payload file or EDI segment fields

Multiple sales scheduling agreements are found for Sold-to Party &1

Diagnosis:

The system uses the following search criteria to search for a sales scheduling agreement:

• The Sold-to Party that either comes in with the EDI message or is determined in the Assign Sold-to Parties app.

• Customer material, partner description, and unloading point (if any) that comes in with the EDI message.

If the system finds multiple sales scheduling agreement, it could be due to the following reasons:

New sales scheduling agreements created for the same sold-to party but haven’t deleted or rejected the old sales schedule agreement. System Response: The system stops processing the EDI message

System Response:

The system stops processing the EDI message

Procedure:

• Delete the old sales schedule agreement in Change Sales Scheduling Agreement app > More > Sales Document > Delete.

• Reject both header and item level of sales schedule agreement in Change Sales Scheduling Agreement app > Reason for Rejection .

No sales scheduling agreement is found for sold-to party

Diagnosis:

The system uses the following search criteria to search for a sales scheduling agreement:

• The sold-to party that either comes in with the EDI message or is determined in the Assign Sold-to Parties app.

• Customer material, partner description, and unloading point (if any) that comes in with the EDI message

If the system cannot find a sales scheduling agreement, it could be due to the following reasons:

• None of the existing sales scheduling agreements match the search criteria.

• The sales scheduling agreement is rejected.

System Response:

The system stops processing the EDI message

Procedure:

Contact the business users and tell them to do the following:

• Enter search criteria and manually search for the sales scheduling agreement in the Change Scheduling Agreements app.
• If necessary, correct the sales scheduling agreement or change the master data of the sales scheduling agreement. Manually search for the sales scheduling agreement again.
• Reprocess the EDI message in the Message Dashboard app.

If the reprocessing fails, contact the business users and ask them to create a new sales scheduling agreement.

Customer Reference &2 of customer &1 is currently being processed

Diagnosis

The system locked the sales scheduling agreement right now

System Response

The system stops processing the EDI message

Procedure

Unlock the sales scheduling agreement and process again

Sales scheduling agreement processing failed

Diagnosis

General system message mentioned that the processing failed due to some issue occurred

System Response

Procedure

Check if detail error message output

&1 must be provided in the source data

Diagnosis

Necessary fields have to be provided in pay-load file.

For example, the system uses two release type in sales scheduling agreement:

• Forecast Schedule release
• JIT Schedule release

System Response

The system stops processing the EDI message

Procedure

Provide those mentioned fields in Payload file or EDI segment fields

Customer reference &2 doesn’t match purchase order number &1

Diagnosis

Customer reference in sales scheduling agreement does not match purchase order number.

PO Number Check(No Update)(X) in the Manage Delivery Schedule Processing app

System Response

The system stops processing the EDI message

Procedure

• Change check options for Purchase Order Number with sold-to party in the Manage Delivery Schedule Processing app.

• Manually change the customer reference filed with the matched purchase order number in the Change Sales Scheduling Agreement app

Unloading point &1 does not match in sales scheduling agreement &2

Diagnosis

• Unloading point not match in sales scheduling agreement.
• Unloading point Check(No Update)(X) in the Manage Delivery Schedule Processing app

System Response

The system stops processing the EDI message

Procedure

• Change check options for unloading point with sold-to party in the Manage Delivery Schedule Processing app.
• Manually change to matched unloading point filed in the Change Sales Scheduling Agreement app

Delivery schedule processing option not found for sold-to party &1

Diagnosis

MRP for DS type setting to E JIT delivery schedules are not used in sales schedule agreement

System Response

• If only created JIT delivery schedule release, system stops processing the EDI message.
• If create both FRC and JIT schedule release, system will only process FRC release, JIT will not process

Procedure

Manually change the MRP for DS type setting in Change Sales Scheduling Agreement app > More > Goto > Header > Sales .

Delivery schedule &2 already exists in sales scheduling agreement &1.

Diagnosis

The delivery schedule entered has already been allowed for, that is, it corresponds to the delivery schedule for the preceding delivery schedule.

System Response

If only created JIT delivery schedule release, system stops processing the EDI message.

If create both FRC and JIT schedule release, system will only process FRC release, JIT will not process

Procedure

Choose another delivery schedule from the number for the preceding delivery schedule.

The text ID for the received text type &1 cannot be determined

Diagnosis

The system could not determine a text type as no record has been specified in view EDI_V_TXTIN_SUP

System Response

The system stops processing the EDI message

Procedure

Define mapping for inbound texts type for integration with buyers.

Define mapping in the SSC UI step Define Mapping for Inbound Texts for Integration with Buyers under Sales > Integration with Buyers .

The old delivery schedule &1 is not identical with delivery schedule &2.

Diagnosis

It is possible that a previous delivery schedule number of the incoming EDI message was not scheduled in Sales Scheduling Agreement, which means there was a gap in delivery schedule numbers

System Response

The system stops processing the EDI message

Procedure

Choose another release number from the number for the preceding release number, change in Change Sales Scheduling Agreement app > Select Item > Fore.DlSch or JIT DlSch > Dlv.schedule filed .

The delivery schedule &1 cannot be processed.

Diagnosis

The delivery schedule key is not set to 1, 2, or blank.

The system processes the delivery schedule when the delivery schedule key is one of the following:

• 1 – The delivery schedule is to meet the Odette standard. Schedule lines in the old delivery schedule that come before the validity period of the new delivery schedule are copied to the new delivery schedule.
• 2 – The delivery schedule is to meet the German Automobile Suppliers Association (VDA) standard. No schedule lines in the old delivery schedule are copied to the new delivery schedule.
• Blank – No schedule lines in the old delivery schedule are copied to the new delivery schedule.

System Response

The system stops processing the EDI message

Procedure

As the message sender, you review the schedule line in the purchase scheduling agreement. To recreate those old schedule lines that are not copied, you do it manually.

Order quantities in schedule lines have been added.

Diagnosis

The system determined that you have delivered materials behind schedule according to the planned cumulative quantity that comes in with electronic data interchange (EDI) message.

System Response

The system adds (a) order quantities in the existing schedule lines or (b) existing schedule lines by the quantity that has been delivered behind schedule.

Procedure

To identify changed schedule lines, compare data in the delivery schedule with original data in the EDI message.

Order quantities in schedule lines have been deducted.

Diagnosis

The system determined that you have delivered materials ahead of schedule according to the planned cumulative quantity that comes in with electronic data interchange (EDI) message.

System Response

The system reduces (a) order quantities in the existing schedule lines or (b) existing schedule lines by the quantity that has been delivered ahead of schedule.

Procedure

To identify changed schedule lines, compare data in the delivery schedule with original data in the EDI message.

The date type &1 is invalid. It can only be D, W, or M.

Diagnosis

In the electronic data interchange (EDI) message, the date type in the schedule line is invalid.

System Response

The system stops processing the EDI message.

Procedure

Manually correct the date type to one of the followings and reprocess the message:

• D (Day)
• W (Week)
• M (Month)

Error UNCAUGHT_EXCEPTION (1F09B73915F6B645E10000000A11447B) when calling EDI_SD_SCHEDGAGRMT_PROCESSING

Line 1 in CL_GOAL_ACCESS================CM01I (CL_GOAL_ACCESS================CP)

An exception with the type CX_GOAL_SCHDA_EXC was raised, but was not handled locally or declared in a RAISING clause.

…

…

Error when calling EDI_SD_SCHEDGAGRMT_PROCESSING

Diagnosis

The error happens when the buyer releases a quantity of the outlined material for the first time (Initial version).

They may send the following:

• A forecast delivery schedule and a JIT delivery schedule at the same time.
• A JIT delivery schedules without a forecast delivery schedule.

The system only processes the EDI message if the first inbound delivery schedules is forecast delivery schedule

System Response

The system stops processing and raise exception when JIT release coming and execute first.

The system stops processing the EDI message

Procedure

Contact the buyer to resend the forecast delivery schedule.

After the system processes the forecast delivery schedule, manually reprocess the JIT delivery schedule