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.

[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