How To Fix F5A460 - Invalid document reference &1 &2 &3 for cross-company-code transaction.

F5A460 - Overview

• Message type: E = Error

• Message class: F5A - Document Editing

• Message number: 460

• Message text: Invalid document reference &1 &2 &3 for cross-company-code transaction.

What causes this issue?

In the case of postings using the reference transaction &V1&, the
document number of the FI document is derived from the reference key of
the posting.
. When a cross-company-code transaction is posted, the reference key
must be built on the basis of the leading company code.
.
.
However, the company code specified in organizational unit &V3& is not
the leading company code of this transaction.
. Consequently, document number &V2& cannot be applied for the document
of the leading company code.
.
.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

The document number specified in the reference key needs to be
determined from the leading company code.
.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message F5A460 - Invalid document reference &1 &2 &3 for cross-company-code transaction. ?

  The SAP error message F5A460 "Invalid document reference &1 &2 &3 for cross-company-code transaction" typically occurs in the context of financial transactions that involve multiple company codes. This error indicates that there is an issue with the document reference being used in a cross-company-code transaction.
  
  Cause:
  
  Invalid Document Reference: The document reference specified in the transaction does not exist or is not valid for the specified company codes.
  Cross-Company Code Issues: The transaction may be trying to reference a document that is not properly linked or does not exist in the other company code involved in the transaction.
  
  Configuration Issues: There may be configuration settings in the system that do not allow for cross-company-code transactions for the specific document type or transaction type being used.
  Data Inconsistencies: There may be inconsistencies in the data between the company codes, such as missing entries in the relevant tables.
  
  
  Solution:
  
  Check Document Reference: Verify that the document reference (&1 &2