How To Fix OIJ_RU504 - Different company code in source document items


SAP Error Message - Details

  • Message type: E = Error

  • Message class: OIJ_RU - Messages for TSW-ETRAN integration

  • Message number: 504

  • Message text: Different company code in source document items

  • Show details Hide details
  • What causes this issue?

    The program found different company codes in different items of the
    source document from which you want to copy this data.

    System Response

    The program does not fill the company code data field in the customs
    declaration header.

    How to fix this error?

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

    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 OIJ_RU504 - Different company code in source document items ?

    The SAP error message OIJ_RU504, which states "Different company code in source document items," typically occurs in the context of SAP Oil and Gas (OIJ) when there is an inconsistency in the company codes associated with the source documents being processed. This error is often encountered during transactions that involve multiple documents or when trying to perform operations that require consistency in company codes.

    Cause:

    The primary cause of this error is that the source documents (such as purchase orders, invoices, or other financial documents) being referenced in the transaction belong to different company codes. In SAP, each company code represents a separate legal entity, and transactions involving multiple company codes must be handled with care to maintain financial integrity.

    Solution:

    To resolve the OIJ_RU504 error, you can take the following steps:

    1. Identify the Source Documents: Determine which source documents are causing the error. You may need to check the document numbers or references in the transaction that triggered the error.

    2. Check Company Codes: Review the company codes associated with each of the source documents. You can do this by navigating to the relevant transaction or document in SAP and checking the header information.

    3. Ensure Consistency: Make sure that all source documents involved in the transaction belong to the same company code. If they do not, you will need to either:

      • Change the company code of the documents to match, if appropriate and possible.
      • Adjust your transaction to only include documents from a single company code.
    4. Reprocess the Transaction: After ensuring that all documents are consistent in terms of company code, reprocess the transaction that triggered the error.

    5. Consult Documentation: If you are unsure about how to change company codes or handle the documents, refer to your organization's SAP documentation or consult with your SAP support team.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes that may help you in checking document details, such as ME23N (Display Purchase Order), FB03 (Display Document), or others depending on the type of document.
    • SAP Notes: Check for any SAP Notes related to this error message in the SAP Support Portal, as there may be specific patches or updates that address known issues.
    • User Authorization: Ensure that you have the necessary authorizations to view and modify the documents in question, as lack of permissions can also lead to errors.

    By following these steps, you should be able to resolve the OIJ_RU504 error and proceed with your transaction in SAP.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker