How To Fix FAR_POSTING_RULES142 - Due to the reprocessing rule, the posting of the ext. app was skipped.

SAP Error Message - Details

• Message type: E = Error

• Message class: FAR_POSTING_RULES - AR Posting Rules

• Message number: 142

• Message text: Due to the reprocessing rule, the posting of the ext. app was skipped.

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 FAR_POSTING_RULES142 - Due to the reprocessing rule, the posting of the ext. app was skipped. ?

  The SAP error message FAR_POSTING_RULES142 indicates that the posting of an external application was skipped due to the reprocessing rule defined in the system. This error typically occurs in the context of the Fixed Asset Accounting (FI-AA) module when there are issues with the posting rules or configurations related to external applications.
  Cause:
  
  
  Reprocessing Rules: The error suggests that the reprocessing rules set up in the system are preventing the posting from occurring. This could be due to:
  
  Incorrect configuration of the reprocessing rules.
  The external application data not meeting the criteria defined in the reprocessing rules.
  Missing or incorrect data in the external application that is being processed.
  
  
  
  Posting Period: The posting period may be closed or not open for the transaction being processed.
  
  
  Authorization Issues: The user may not have the necessary authorizations to perform the posting.
  
  
  Data Inconsistencies: There may be inconsistencies or errors in the data being sent from the external application.
  
  
  Solution:
  
  
  Check Reprocessing Rules:
  
  Review the configuration of the reprocessing rules in the system. Ensure that they are set up correctly and that they align with the data being posted from the external application.
  Adjust the rules if necessary to allow for the posting.
  
  
  
  Verify Posting Period:
  
  Check if the posting period is open for the transaction. If it is closed, you may need to open it or adjust the transaction date.
  
  
  
  Review Data from External Application:
  
  Ensure that the data being sent from the external application is complete and meets all necessary criteria for posting.
  Validate the data for any inconsistencies or errors.
  
  
  
  Check Authorizations:
  
  Ensure that the user attempting to perform the posting has the necessary authorizations to do so.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on the error message and related configurations.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify the exact point of failure and gather more information about the data being processed.
  
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like OABR (for reprocessing rules) or OAYZ (for asset accounting configuration) to review and adjust settings.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Support: If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.