How To Fix CRM_MKTGS_ARCHIVING002 - BOR methods, preselect and check, not found

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTGS_ARCHIVING - Generic Marketing Archiving

• Message number: 002

• Message text: BOR methods, preselect and check, not found

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 CRM_MKTGS_ARCHIVING002 - BOR methods, preselect and check, not found ?

  The SAP error message CRM_MKTGS_ARCHIVING002 typically indicates that the system is unable to find the necessary BOR (Business Object Repository) methods related to the archiving process for marketing documents. This can occur during the archiving of marketing documents in the SAP CRM system.
  Cause:
  
  Missing BOR Methods: The error suggests that the required BOR methods for the archiving process (specifically the "preselect" and "check" methods) are not defined or are not accessible in the system.
  Configuration Issues: There may be configuration issues in the archiving object settings or in the related business object definitions.
  Transport Issues: If the system has recently undergone a transport of changes, the necessary methods may not have been transported correctly.
  Authorization Issues: There may be authorization issues preventing access to the required methods.
  
  Solution:
  
  
  Check BOR Methods:
  
  Use transaction SWO1 to check the Business Object Repository. Look for the relevant business object related to marketing documents and verify if the "preselect" and "check" methods are defined.
  If they are missing, you may need to create or activate them.
  
  
  
  Review Archiving Object Configuration:
  
  Go to transaction SARA and check the configuration for the archiving object related to marketing documents. Ensure that all necessary settings are correctly configured.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly. You may need to re-transport the missing objects.
  
  
  
  Authorization Check:
  
  Ensure that the user executing the archiving process has the necessary authorizations to access the BOR methods. You can check this in transaction SU53 after the error occurs.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  
  
  
  Debugging:
  
  If you have access to development tools, you can debug the archiving process to identify where the failure occurs and gather more information about the missing methods.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for archiving in CRM to understand the prerequisites and configurations needed for successful archiving.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have already taken.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.