How To Fix ARCH_STANDARDS165 - Customizing error: Wrong presetting for the commit counter

SAP Error Message - Details

• Message type: E = Error

• Message class: ARCH_STANDARDS - Standard Archiving Checks

• Message number: 165

• Message text: Customizing error: Wrong presetting for the commit counter

What causes this issue?

According to the data archiving standard, the default setting for the
commit counter should be:
0 (this means that the parameter is no longer used) if the new concept
with function module ARCHIVE_CHECK_COMMIT_NEEDED is used in the delete
program.
10 if the new concept with function module ARCHIVE_CHECK_COMMIT_NEEDED
is not used in the delete program.

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

However, in Customizing for archiving object &V1&, the value &V2& has
been entered.

System Response

INCLUDE ARCH_STNDRD_CHECK_SYS_RESP_9 OBJECT DOKU ID TX

How to fix this error?

INCLUDE ARCH_STNDRD_CHECK_WHATODO_1 OBJECT DOKU ID TX

Procedure for System Administrators

INCLUDE ARCH_STNDRD_CHECK_WHATODO_2 OBJECT DOKU ID TX
For the archiving object &V1&, check the value of the commit counter in
the field with the same name in the Customizing transaction <LS>AOBJ</>.
INCLUDE ARCH_STNDRD_CHECK_WHATODO_3 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ARCH_STANDARDS165 - Customizing error: Wrong presetting for the commit counter ?

  The SAP error message ARCH_STANDARDS165 indicates a customizing error related to the commit counter in the archiving process. This error typically arises when the settings for the commit counter in the archiving configuration are not correctly defined, leading to issues during the archiving process.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Incorrect Configuration: The commit counter settings in the archiving object configuration may not be set correctly. This can happen if the values are outside the acceptable range or if they are not aligned with the system's capabilities.
  Inconsistent Settings: There may be inconsistencies between the archiving object settings and the actual data being processed.
  Missing Authorizations: Sometimes, the user executing the archiving process may not have the necessary authorizations to perform the operation, leading to errors.
  
  Solution:
  To resolve the ARCH_STANDARDS165 error, you can follow these steps:
  
  
  Check Archiving Object Configuration:
  
  Go to the transaction code SARA (Archive Administration).
  Select the relevant archiving object and check the configuration settings.
  Ensure that the commit counter is set correctly. The commit counter typically defines how many records are processed before a commit is made to the database.
  
  
  
  Adjust Commit Counter:
  
  If the commit counter is set to a value that is too high or too low, adjust it to a more appropriate value. A common practice is to set it to a value that balances performance and system stability (e.g., between 1000 and 10000).
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the archiving process has the necessary authorizations. Check the roles and profiles assigned to the user.
  
  
  
  Check for Data Consistency:
  
  Ensure that the data being archived is consistent and does not have any issues that could cause the archiving process to fail.
  
  
  
  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 that can resolve the issue.
  
  
  
  Test the Archiving Process:
  
  After making the necessary adjustments, test the archiving process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SARI: Archive Information System
  
  
  Documentation: Refer to SAP Help documentation for archiving objects and customizing settings.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.