No data was released for version Y10 and Consolidation Unit - SAP Group Reporting

[VMSAPExplorer63]

Dear all,

I'm facing this warning in SAP Group Reporting - Data Monitor for the task "Release from Universal Journal". 

GL ACCOUNTS - FS ITEMS  are mapped

Assign Mapping done

Consolidation Unit is confiugured to read from Universal Journal

Version Y10 is configured in this way:

What could be the problem? how Can I solve this? I have the same problem with the other consolidation units and task Balance Carryforward ended successfully with No Data. 

Thank you in advance.

[Allam_Chinnapa_Reddy]

System shows this warning if there is no more data to release from ACDOCA to GR. Here, I see that you are doing a FULL release, yet you are not getting any data into Group Reporting.
1) Please check if you have any data for this period and Consolidation Unit in ACDOCA.
2) If you don't have data in ACDOCA, then the warning message is justified.
3) But, if you have data in ACDOCA, but still not getting any data into GR after Data Release, that means the Consolidation Related Fields (Cons Unit, FS Item, SubItem, Partner Unit etc.,) are not derived for these lines in ACDOCA. Please verify. If this is the case, then you first run Realignment job to have these Consolidation Related fields populated in ACDOCA. Then do a Data Release to Group Reporting.

[VMSAPExplorer63]

Hello Allam, I have done the realingment of grpl but still have the same problem.

[Ameer_Muawia]

Hello @vmsapexplore63

[Ameer_Muawia]

Hello @vmsapexplore63

is your issue resolved? I am facing the same issue. Can you please tell me the tasks you performed to resolve this issue.

Your support will be highly appreciated.

Kind regards

[paulohsferreira]

Hello Vanessa

We have a similar issue in GR onprem version 2020. The solution was to implement note:

3207472 - Correcting the BCF behavior related to consolidation unit attributes time and version depe..., which was mentioned in note

3144152 - Group Reporting: Balance carry forward of released data is missing - SAP for Me

Hope this helps (if it is also your GR version)

[VMSAPExplorer63]

Hi Paulo, thank you a lot. Did you solve the problem implementing this sap notes?

[VMSAPExplorer63]

I don't understand this section: This problem can happen when there are two different consolidation unit attributes time and version dependent configuration at the same year.

[VMSAPExplorer63]

This problem can happen when there are two different consolidation unit attributes time and version dependent configuration at the same year.What operation I have to do about that?

[paulohsferreira]

Hi Vanessa. Yes, Implementing the SAP note solved the problem

[VMSAPExplorer63]

Hi Paulo, thank you a lot. Did you solve the problem implementing this sap notes? Just using the support package? I have checked all the configuration units attributes , they looks okay.

[VMSAPExplorer63]

these note aren't helpfull for my system, still have the problem

[Ameer_Muawia]

Hi @VMSAPExplorer63 

I faced the same issue.

After some analysis, testing and deep R&D, I was able to resolve the issue, and the data is now being successfully released and transferred from ACDOCA to ACDOCU.
Sharing with you the key checks and fix below in case it helps you facing a similar problem.

Prerequisites to Verify

• Consolidation Unit is configured to read from Universal Journal (Universal Journal Integration active)

• G/L Accounts are mapped to FS Items

• Fiscal Year Variant is the same in Consolidation Unit (FI-Company Code) and Version

• Currency is the same in Consolidation Unit and Version

• Data exists in ACDOCA

• Posting period of documents posted in ACDOCA matches the period selected in Set Parameters.

If All Above Are Correct

Check the posted documents in ACDOCA and verify whether the Consolidation Unit (CU) field is populated.

In my case, the CU was not appearing in ACDOCA. Because of this, the system could not pick up the data for release. As can be seen in the picture below.

Solution

Create a Substitution Rule in "Manage Substitution and Validation Rules" app to populate the Consolidation Unit in ACDOCA:

• in Precondition select your Company Code

• in Substitution

  • select your Consolidation Unit

  • Substitution Type: Substitute with Constant

  • Mark: Overwrite

Save and activate the rule.

After creating the substitution, post a new accounting document and confirm that the CU field is now populated in ACDOCA.

Once CU fields are populated, rerun Release Universal Journal task, and the data will be released successfully.

Hope this will you.

regards

SAP S/4HANA Finance for group reporting SAP Group Reporting Data Collection 

[finhead1]

@VMSAPExplorer63 

We had a similar issue , data was not being released by the Release task. We also noticed that any new journals we created didn't contain any values in the Consolidation relevant fields (Consol Unit, FS Item, etc.) in ACDOCA. We resolved this with this note: 3317403 - GRPL: Substitution is not working - SAP for Me

We then ran a realignment run which updated the consolidation fields in ACDOCA, afterwards the release task worked correctly.

Check if newly created journals have these fields populated or not, this note would resolve it.

Regards

Finbar