Symptom
Special-period data is not visible in ICMR matching results.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Post an intercompany transaction in a special period (for example, period 13–16).
- Run ICMR reconciliation/matching.
- Compare ICMR matching results with elimination balances and observe differences for special-period postings.
Cause
For data source SC_JOURNAL_ENTRIES_01 (view ICA_CONSJOURNALENTRIES_4) selects ACDOCU with rrcty = '0', plevl in '', '00', '01', '0C', '10', and draft <> 'X', which excludes posting level 20 and certain document types (for example, 2G), so those documents are not taken into ICMR from ACDOCU.
For record type U with document type 0F originating from accounting, data is retrieved from ACDOCA instead of ACDOCU; when posted in special periods, these items are mapped to period 12 in ICMR based on the posting date, so they do not appear under periods 13–16.
Resolution
- Confirm that the ICMR matching method uses data source SC_JOURNAL_ENTRIES_01 and view ICA_CONSJOURNALENTRIES_4.
- Review the ACDOCU selection logic (rrcty = '0'; plevl in '', '00', '01', '0C', '10'; draft <> 'X') and note that documents with posting level 20 or document type 2G are not selected by this view.
- For record type U with document type 0F posted in special periods, check ICMR results for period 12, as these items are mapped to period 12 based on the posting date.
- If expected special-period balances are missing in ICMR, verify whether they fall into the excluded categories above or originate from ACDOCA, and adjust period filters/reporting accordingly.
See Also
Refer to: SAP Note 3072643
Keywords
icmr, special period, period 13, period 14, period 15, period 16, matching results, group reporting, acdocu, acdoca, ICA_CONSJOURNALENTRIES_4, posting level 20, record type U, document type 0F, document type 2G, period mapping , KBA , FIN-CS-ICR-2CL , S/4HANA Intercompany Matching and Reconciliation (Publ Cld) , Problem
SAP Knowledge Base Article - Public