1) Check the support package level in table CVERS for component: S4CORE & UIAPFI70 , with the support package level, search SAP notes for components FIN-CS-COR-DT-RUJ, make sure all notes are implemented in your system. This is quite important if you want to avoid duplicate efforts.
2) Once the notes are completly implemented, you may go to the app "Schedule jobs for consolidation tasks", and create a new job with template "Release Universal Journals". Then in step 3, select "Complete Period" under replication type. And run the data release again. In most of the cases, the issue can be resolved with a complete run. If the issue persist, plesae go to next step.
3) Check in table FINCS_BUNIT , FINCS_BUNIT_ATD, and FINCS_BUNIT_ATVD for related cons.unit
3.1) in FINCS_BUNIT, you can get the assigned company for the cons.unit. And then use it to check in table T001 with RCOMP = company, with this you will know the company code(BUKRS)
3.2) in table FINCS_BUNIT_ATD, you can get the from and to fiscal year periods for the cons.unit.
3.3) In table FINCS_BUNIT_ATVD, find "CU Attributes CUAVS" and "Univ. Journ. Integr. TRANS". With "CU Attributes CUAVS", you can go to t-cd: CXB1, and check related consolidation version. Make sure the "CU Attributes" in the consolidation version correctly customized. And for "Univ. Journ. Integr.", value "H" means "Transfer from Universal Journal", while value "U" means no integration(no records can be released from universal journal)
4) Check in CXB3, for the field "From Year for Preparation Ledger". This helps you to know if GRPL is used or not for the period you run RUJ.
4.1) If GRPL is used, then check the FAQ note 3412034 - Troubleshooting Tips for Realignment Function (RF) or Release of Universal Journals (RUJ) in S/4HANA Group Reporting with Integration with Preparation Ledger (GRPL) active. This FAQ can help you to analyze the reason why data missing.
4.2) If GRPL is not used, then check the note 3393548 - SAP S/4HANA Group Reporting: How to use Delta Mode in Release Universal Journals Task in a non-Group Reporting Preparation Ledger (GRPL) Integration Scenario
5) if above steps cannot help you, then you will need to do data analysis with CDS view.
Basically, the data flow for release universal journal looks like:
ACDOCA -> a lot of CDS views -> ACDOCU (meanwhile, it will refer to "Data release Aggregation" setting in t-cd: FINCS_ADDLFLD_SEL_U.
For a lot of CDS views, which looks like below, when you check it in t-cd: SE16N, you will be asked to input Time Stamp, please input 0 - 999999999999999.
P_REALTIMERPTDFINDATANRL
P_REALTIMERPTDFINDATANRL_06
P_REALTIMERPTDFINDATANRL_05
P_REALTIMERPTDFINDATANRL_04
P_REALTIMERPTDFINDATANRL_03
P_REALTIMERPTDFINDATANRL_02
P_REALTIMERPTDFINDATANRL_01
I_JournalEntryItem
ACDOCA
Those are basic CDS view/table used for the RUJ data flow, there are a lot of other CDS views also be joined within those CDS view, eg. I_CompanyCode / I_CnsldtnUnit_3 /I_CnsldtnUnitByTime /I_CnsldtnUnitByTimeVersion /I_CnsldtnVersion / I_FiscalCalendarDate /I_FSItemMappingAssgmtWithVers /I_CnsldtnFinStmntItem /I_BreakdownCategoryField /I_CnsldtnSubItemCategoryEnhcd /I_CnsldtnSubassgmtDfltValue
All of those Joining CDS view are also quite important, for example when GRPL is not used, you might have fiscal year variant in FI not same with fiscal year variant in Group reporting version, which need you to do analysis carefully.
==============
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 |