Do you have any question about this error?
Message type: E = Error
Message class: EDI_SD - Messages for EDI SD Integration
Message number: 842
Message text: Sales scheduling agreement &1 not used. Supplier number not suitable.
The supplier number that comes in is not defined in the customer master
or in the corresponding sales area.
This message is for information only. The system keeps processing if it
finds other sales scheduling agreements that can be used. Otherwise, the
system stops processing the EDI message.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
EDI_SD842
- Sales scheduling agreement &1 not used. Supplier number not suitable. ?The SAP error message EDI_SD842 indicates that there is an issue with a sales scheduling agreement in the context of Electronic Data Interchange (EDI). Specifically, the message states that the sales scheduling agreement is not being used because the supplier number is not suitable. Here’s a breakdown of the potential causes, solutions, and related information for this error:
Causes:
- Incorrect Supplier Number: The supplier number specified in the scheduling agreement may not match any valid supplier in the system.
- Inactive Supplier: The supplier may be inactive or not set up correctly in the vendor master data.
- Data Inconsistency: There may be inconsistencies in the data between the sales scheduling agreement and the vendor master data.
- Missing EDI Configuration: The EDI configuration for the supplier may not be set up correctly, leading to issues in processing the scheduling agreement.
- Plant or Company Code Issues: The plant or company code associated with the scheduling agreement may not be valid for the specified supplier.
Solutions:
- Verify Supplier Number: Check the supplier number in the sales scheduling agreement and ensure it is correct. You can do this by navigating to the vendor master data (transaction code
XK03
orMK03
).- Check Vendor Status: Ensure that the supplier is active and properly set up in the system. If the supplier is inactive, you may need to reactivate it.
- Review Scheduling Agreement: Look at the details of the sales scheduling agreement to ensure that all relevant data (such as plant, company code, and item details) is correct and matches the vendor master data.
- EDI Configuration: Check the EDI settings for the supplier to ensure that they are configured correctly. This includes verifying the partner profile settings (transaction code
WE20
).- Consult Documentation: Review any relevant SAP documentation or notes related to EDI and scheduling agreements for additional troubleshooting steps.
- Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
Related Information:
ME33K
(Display Scheduling Agreement), XK03
(Display Vendor), and WE20
(Partner Profiles).By following these steps, you should be able to identify and resolve the issue causing the EDI_SD842 error message.
Get instant SAP help. Start your 7-day free trial now.
EDI_SD841
Zero or multiple items received.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EDI_SD840
Material usage indicator &1 not matched in sales scheduling agreement &2.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EDI_SD843
Zero or multiple delivery schedules received.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EDI_SD844
Enter S, W, I, or E for the message type.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.