Solution : https://service.sap.com/sap/support/notes/3992 (SAP Service marketplace login required)
Summary :
The INDX table is utilized for storing binary packed data, typically used for accommodating large internal data structures using ABAP 'EXPORT TO DATABASE' and 'IMPORT FROM DATABASE' commands. Its contents are identified by a RELID field in its key, allowing segmentation by application usages. Due to potential risks of data corruption and restructuring, data that cannot be reconstituted post-destruction should not be stored in this table. SAP recommends distinct INDX tables for each application to prevent data merging issues between applications using the same RELID, which also aids in swift data identification and reduced collision risk. Key applications and their corresponding RELIDs detail how data storage is managed across various components, emphasizing customized table usage.
Key words :
pc ec-pca 1089012 pr bc-sec-aut-pfc 1291662 rh bc-bmt-om rt bc-dwb-sem 1294414 sh bc-doc-hlp 989070 sm ca-gtf-scm 977726 v1 plm-cfo vm bc-dwb-sem 1294414, relid component note // pa-bc 836478 al bc-srv-bal ap sv-bo ar ps-, 998892 iw kw-km 1292125 ix lo-vc-loi 684744 kc fs-cd, 1399175 cy pp-crp fl bc-dwb-, -pc 1302042 oa bc-srv-arl pe, bc-i18-uni, -fub 1672188 gl fi-sl-, -b-dp-edt 1055431 ke, -pa 1318670 ku, applications component
Related Notes :
1583140 | Deletion of INDX entries with RELID = 'ST' for India: CIN |
1399175 | Cleanup table INDX(AR) |
1319517 | Unicode Collection Note |
1294414 | Cleaning up table INDX (VM/RT) |
1089012 | Cleanup table INDX(PE)/(PC) |
1055431 | Deletion of INDX entries |
989070 | Cleanup for table INDX(SH) |
977726 | INDX cluster table contains many entries in area SM |
836478 | HR authorizations: Displaying the data in the INDX |
706478 | Preventing Basis tables from increasing considerably |
420945 | Table INDX reaches maximum allowed size |
18523 | Using INDX in the Report Writer |