SAP Knowledge Base Article - Preview

3571840 - The entries in secondary index tables are not deleted during the postprocessing of archiving object FI_DOCUMNT

Symptom

  • After successful write and delete steps of archiving object FI_DOCUMNT, postprocessing is executed to clean up secondary indexes.
  • It is found that the entries in secondary index tables are not deleted even though table entries have XARCH=X marked.


Read more...

Environment

  • Financial Accounting (FI)
  • SAP R/3
  • SAP R/3 Enterprise
  • SAP ERP Central Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA
  • SAP S/4HANA Finance
  • SAP S/4HANA 

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA Finance all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

Data Archiving, Object FI_DOCUMNT, SAP ERP, BSAK Table, XARCH=X, SecondaryIdxRunTme, T-code OBR7, Secondary Indexes, Postprocessing. , KBA , FI-GL-GL-E , Archiving , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.