SAP Knowledge Base Article - Preview

3730058 - SAP S/4 HANA fi_tf_glf write: acdoca archiving fails with dbsql_stmnt_too_large

Symptom

  • Archiving write for FI_TF_GLF ends with runtime error DBSQL_STMNT_TOO_LARGE in transaction ST22.
  • Short text: “Open SQL command is too big.”
  • Exception: CX_SY_OPEN_SQL_DB.
  • ABAP program: CL_FML_AEXT_ARCHIVING=========CP (also referenced: CL_FML_AEXT_ARCHIVING=========CM00N).


Read more...

Environment

  • Controlling (CO)
  • SAP S/4 HANA 2021.
  • SAP S/4 HANA 2022.
  • SAP S/4 HANA 2023.

Product

SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023

Keywords

FI_TF_GLF, FI_RF_GLF_WRI, ACDOCA archiving, DBSQL_STMNT_TOO_LARGE, SAPSQL_STMNT_TOO_LARGE, CL_FML_AEXT_ARCHIVING, SELECT_CKMLHD, ST22 dump, Open SQL command too big, Material Ledger, CO-PC-ML, write phase error, archiving write, memory limit, large selection ranges, S/4HANA, G/L Transaction Figures (New), s4core, SQL error "SQL code: 2048" occurred while accessing table "CKMLHD", DBSQL_SQL_INTERNAL_DB_ERROR, CL_FML_AEXT_ARCHIVING=========CM006, DET_DEPENDENCY_MBEW, table exceeds entries, S4CORE 106, S4CORE 107, S4CORE 108, memory problems. , KBA , CO-PC-ML , Material Subledger , Problem

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.