How To Fix OIJ_RU600 - SD invoice &1 &2 not posted to FI

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 600

• Message text: SD invoice &1 &2 not posted to FI

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message OIJ_RU600 - SD invoice &1 &2 not posted to FI ?

  The SAP error message OIJ_RU600, which indicates that an SD invoice (Sales and Distribution invoice) has not been posted to Financial Accounting (FI), can arise from various causes. Here’s a breakdown of potential causes, solutions, and related information:
  Causes:
  
  
  Missing Configuration: The integration between SD and FI may not be properly configured. This can include missing account determination settings or incorrect settings in the billing document type.
  
  
  Document Status: The invoice may be in a status that prevents it from being posted to FI. For example, it might be in a "blocked" status or not fully processed.
  
  
  Posting Period Issues: The posting period for the invoice may be closed, preventing it from being posted to FI.
  
  
  Data Inconsistencies: There may be inconsistencies in the data that prevent the invoice from being processed correctly, such as missing or incorrect master data.
  
  
  Authorization Issues: The user attempting to post the invoice may not have the necessary authorizations to perform the action.
  
  
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may interfere with the standard posting process.
  
  
  Solutions:
  
  
  Check Configuration: Review the configuration settings for the integration between SD and FI. Ensure that the account determination is set up correctly and that the billing document type is configured to allow posting to FI.
  
  
  Review Document Status: Check the status of the invoice in the system. If it is blocked or in a non-postable status, investigate the reasons and resolve any issues.
  
  
  Open Posting Period: Verify that the posting period for the invoice is open. If it is closed, you may need to open the period or post the invoice in a different period.
  
  
  Data Validation: Check for any data inconsistencies. Ensure that all required fields are filled out correctly and that master data (such as customer and material master records) is accurate.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to post invoices to FI. If not, work with your security team to grant the required permissions.
  
  
  Debugging Custom Code: If there are custom developments, consider debugging the code to identify any issues that may be causing the error.
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VF03 (Display Billing Document) to review the invoice details and FB03 (Display Document) to check the FI document status.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.