Do you have any question about this error?
Message type: E = Error
Message class: BORGR - Messages Multi-Level Goods Receipt
Message number: 659
Message text: No changes received for inbound delivery &1, item &2
The system assumes that the vendor transmits exactly one outbound
delivery per pick-up list, which contains exactly the items of the
pick-up list. Internally, several inbound deliveries can belong to this
pick-up list. The changes are then distributed among the inbound
deliveries. Item &V2& of inbound delivery &V1& belongs to the pick-up
list, but is not referred to in the IDoc.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the IDoc.
Error message extract from SAP system. Copyright SAP SE.
BORGR659
- No changes received for inbound delivery &1, item &2 ?The SAP error message BORGR659 indicates that there are no changes received for a specific inbound delivery and item. This error typically occurs in the context of inbound delivery processing, particularly when using EDI (Electronic Data Interchange) or other integration methods to update inbound delivery information.
Cause:
- No Changes Made: The most straightforward cause is that there are indeed no changes to the inbound delivery or item that need to be processed.
- Incorrect Data: The data being sent to SAP may not match the expected format or may not correspond to an existing inbound delivery or item.
- Communication Issues: There may be issues with the communication channel (e.g., EDI, IDoc) that prevent the changes from being received or processed correctly.
- Configuration Issues: There may be configuration issues in the system that prevent the processing of inbound delivery updates.
Solution:
- Verify Changes: Check if there are any actual changes made to the inbound delivery or item. If there are no changes, this message can be ignored.
- Check Data Format: Ensure that the data being sent to SAP is in the correct format and that it corresponds to the correct inbound delivery and item numbers.
- Review Communication Logs: If using EDI or IDocs, review the communication logs to identify any errors or issues in the transmission of data.
- Check Configuration: Review the configuration settings related to inbound delivery processing and ensure that they are set up correctly.
- Debugging: If necessary, use debugging tools in SAP to trace the processing of the inbound delivery and identify where the issue may be occurring.
Related Information:
VL31N
(Create Inbound Delivery) or VL32N
(Change Inbound Delivery) to see the status of the inbound delivery.WE02
or WE05
to monitor IDocs and check for any errors or issues related to the inbound delivery processing.If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further assistance.
Get instant SAP help. Start your 7-day free trial now.
BORGR658
Mat. &3 of the inbound delivery is not mat. &4 of change IDoc
What causes this issue? A change of inbound delivery item &V2& has been transmitted for inbound delivery &V1&. However, material &...
BORGR657
Reference of inbound delivery item for item of pick-up list is empty
What causes this issue? The IDoc contains item &V1&, which is to be changed. This item does not refer to the item of the pick-up list.System ...
BORGR660
HU &1 &2 contains several internal inbound deliveries (example &3)
What causes this issue? The change message contains handling unit &V1& &V2&. This handling unit contains materials and/or other handl...
BORGR661
Item &3: PO item &1 &2 of IDoc does not match existing PO item
What causes this issue? In the IDoc, purchase order item &V1& &V2& is specified for item &V3& of inbound delivery &V4&...
Click on this link to search all SAP messages.