How To Fix FMCA_PSOB138 - Partner &2 preselected for archiving. Deletion run not executed yet

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCA_PSOB - Contract Object

• Message number: 138

• Message text: Partner &2 preselected for archiving. Deletion run not executed yet

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 FMCA_PSOB138 - Partner &2 preselected for archiving. Deletion run not executed yet ?

  The SAP error message FMCA_PSOB138 indicates that a partner (in this case, represented by &2) has been preselected for archiving, but the deletion run has not yet been executed. This message typically arises in the context of archiving processes within SAP, particularly in the Financial Management (FM) module.
  Cause:
  
  Preselection for Archiving: The partner has been marked for archiving, which means that it is eligible to be archived based on certain criteria (e.g., inactivity, completion of processes).
  Deletion Run Not Executed: The actual deletion process that would remove the data from the database has not yet been performed. This could be due to a variety of reasons, such as scheduling issues, lack of authorization, or simply that the deletion run has not been initiated.
  
  Solution:
  
  
  Execute the Deletion Run: 
  
  Navigate to the relevant transaction for executing the deletion run. This is typically done through transaction codes like SARA (Archive Administration) or specific transactions related to the archiving object in question.
  Ensure that the deletion run is executed for the relevant archiving object that includes the partner in question.
  
  
  
  Check Archiving Settings:
  
  Verify the archiving settings and ensure that the partner is correctly configured for archiving.
  Check if there are any prerequisites or conditions that need to be met before the deletion run can be executed.
  
  
  
  Review Logs and Authorizations:
  
  Check the logs for any errors or warnings that may have occurred during the archiving process.
  Ensure that you have the necessary authorizations to execute the deletion run.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files related to archiving and deletion runs for specific instructions and best practices.
  
  
  
  Contact SAP Support: 
  
  If the issue persists or if you encounter unexpected behavior, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Archiving in SAP: Archiving is a process used to remove data from the database to improve performance and manage data growth. It involves marking data for archiving, executing the archiving process, and then performing a deletion run to remove the data.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA for archiving administration, SARI for archiving information, and others specific to your SAP version and configuration.
  Data Retention Policies: Ensure that your organization’s data retention policies are adhered to when archiving and deleting data.
  
  By following these steps, you should be able to resolve the FMCA_PSOB138 error and successfully execute the deletion run for the preselected partner.