Skip to Content
Author's profile photo Gavin Gao

Tables ACCTHD, ACCTIT & ACCTCR size problem

Situation:

You meet following problems in your system.
1) Tables ACCTHD, ACCTIT & ACCTCR grow significantly even you update statistics.
2)  After the archiving and the tables reorganization still there is no change for the size of tables.
3) EWA report shows recommendation about  ACCTIT Table Reorganization.

Reason:

The ACCT** tables store document information for postings from material management. So on every MM invoice or goods movement posting a document will be stored in the ACCT** tables. This document is basically a copy of the document information sent from MM to accounting.

The information stored in tables ACCTHD, ACCTIT and ACCTCR are only available during the runtime of document processing for postings from MM.

So if you post large invoices or goods movement documents frequently, the number of records in ACCT** tables will increase accordingly.

Solution:
First, SAP Best Practices recommend that you archive Accounting Interface documents (MM) entries after 6 months, since they probably no longer need to be accessed frequently after this period of time.

Second,  archive the content of database tables ACCTHD, ACCTIT and ACCTCR using the archiving object MM_ACCTIT either in transaction SARA

Third, If you do not use subsequentdocument update in special ledger, profit center accounting, CO or funds management and do not need the content of tables ACCTHD, ACCTIT and ACCTCR you can also deactivate the update of those tables completely.

Fourth, from technical point of view, it is no problem to delete the ACCT* table entries. Of course you can archive them before deleting, in case you want to restore those information.

For more information, please check SAP notes 48009 and 83076 and following KBAs.

1886315

1885677

1885760

1901585

1901507

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      I have read SAP Note 48009. Our SAP FI implementation meets all the criteria that you and the SAP note 48009 identifies to deactivate the update of the ACCT* tables.  Have you implemented the ACCT* deactivation for any customers and have there been any negative impacts as a result of implementing the ACCT* table deactivation?

      Regards,

      Chris Milstead

      Author's profile photo Former Member
      Former Member

      As per Above Note we can deactivate the ACCT* table but i want to know what will the impact on historical data what are demerits it effect all the different table it may be FI,CO, MM & SD some time system may through inconsistency data through dump messages.

      Author's profile photo Sandeep Kumar
      Sandeep Kumar

      All mentioned KBA s are showing as not released.