Do you have any question about this error?
Message type: E = Error
Message class: BORGR - Messages Multi-Level Goods Receipt
Message number: 652
Message text: Reference item &3 for item &2 not found
In the inbound delivery &V1&, item &V2& refers to item &V3& of the
pick-up list. The system could not determine an internal inbound
delivery item for this item.
The system rejects the change message.
Check the change 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.
BORGR652
- Reference item &3 for item &2 not found ?The SAP error message BORGR652 indicates that a reference item for a specific item could not be found. This error typically occurs in the context of document processing, such as in purchasing or sales documents, where items are linked or referenced to one another.
Cause:
- Missing Reference: The reference item (item &3) that is supposed to be linked to the main item (item &2) does not exist in the system. This could be due to data entry errors, deletion of the reference item, or incorrect configuration.
- Data Inconsistency: There may be inconsistencies in the data, such as missing or incorrect entries in the database that prevent the system from finding the reference item.
- Document Status: The document might be in a status that does not allow for the reference item to be processed or accessed.
- Configuration Issues: There may be issues with the configuration of the document types or item categories that affect how references are handled.
Solution:
- Check Item Existence: Verify that the reference item (item &3) exists in the system. You can do this by checking the relevant tables or using transaction codes like ME23N (for purchase orders) or VA03 (for sales orders).
- Correct Data Entry: If the reference item is missing, ensure that it is created or re-entered correctly. If it was deleted, you may need to recreate it or adjust the main item to reference a valid item.
- Review Document Status: Check the status of the document to ensure it is in a state that allows for the reference item to be processed.
- Configuration Review: If the issue persists, review the configuration settings related to the document types and item categories to ensure they are set up correctly.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the error message and the context in which it occurs.
- Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the BORGR652 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
BORGR651
No inbound deliveries for pick-up list &1 found
What causes this issue? In the IDoc, changes to the inbound deliveries for pick-up list &V1& have been transmitted. For this pick-up list, no...
BORGR650
Internal inconsistency: Item &1 not found
What causes this issue? An internal inconsistency has occurred: Inbound delivery &v1& does not contain inbound delivery item &v2&.Sys...
BORGR653
GR has already been posted for inb. delivery &1; no changes possible
What causes this issue? Goods receipt has been posted partially or completely for at least one inbound delivery which the pick-up list refers to. (ex...
BORGR654
Referenced pick-up list is ambiguous
What causes this issue? In item &V1&, there is a reference to pick-up list &V2&. However, the header of the inbound delivery or a pre...
Click on this link to search all SAP messages.