In Sales Scheduling Agreements, the delivery schedules are updated via EDI messages, the customers of component suppliers will send the requirements, and during the inbound process of supplier system, the delivery schedules and corresponding schedule lines, please refer to the latest document : Help Document.
During the EDI process, if there is issue occurs in application level, the logs would be persisted and users can review the failed message in dashboard. After the users fixing the issue, they reprocess the failed EDI messages of Message Dashboard.
However, there is possibilities that although the previous EDI messages are in processing, new EDI message would also receive to update the same sales scheduling agreement number. And they would be blocked by the same issue. If the there are more and more EDI message come in to update the same document, There would be plenty failed messages in dashboard. Users have to reprocess them one by one after fixing the issue.
2, Error message reprocessed in AIF
With the new AIF(Application Interface Frame) setting in back-end, new kinds of error are introduced to reprocess automatically in new cloud delivery. After the adaption of new cloud upgrade, below failed EDI messages would be reprocessed automatically without any user interactions.
Below EDI messages are locked by the following errors can they be reprocessed automatically:
The old delivery schedule number is not identical with the current delivery schedule.
There is no forecast delivery schedule in the sales scheduling agreement.
The sales scheduling agreement is currently being processed by another user.
With the automatic reprocessing function, the system will try to reprocess the failed message up to 10 times in every 5 minutes. While waiting for the next automatic reprocessing, it will display the status as ‘In Process’ in Message Dashboard.
Note: Beside of EDI for updating the delivery schedule, the EDI for creating the Consignment Issue of Sales Scheduling Agreement is provided the following error:
- The sales scheduling agreement is currently being processed by another user.
3, Use Case
Here we take one example that: ‘The sales scheduling agreement is currently being processed by another user.’, to see what is happened after the new upgrade of AIF customizing.
3.1 Create a new Sales Scheduling Agreement and go to the Edit mode
Here you can create one sales scheduling agreement, maintain the information which are relevant for customer.
3.2 Send the EDI message to update the delivery schedule of this sales scheduling agreement.
With B2B API or individual API tool like POSTMAN, and send the new delivery schedule:
3.3 Check the Message Dashboard, the message status display as in process as default
Due to the lock of sales scheduling agreement, the new EDI message would be processed failed, you can review the error message in Message Dashboard.
3.4 Unlock the sales scheduling agreement
You can unlock sales scheduling agreement, which can ensure the incoming messages are able the process successfully.
3.5 EDI message is process automatically
You can wait for 5 minutes the most, the message was been reprocess automatically with any user interaction.
And delivery schedule has been updated to new version successfully.
There are similar with the errors which are mentioned in chapter 2. With the auto reprocess, you don’t need to monitor the dashboard and process the EDI message manually, it would save lots of effort on message monitoring.