enfrdeitptrues

Group Reporting : Limitations and Restrictions

Details
Category: SAP Group Reporting Articles
  1. [ Version 1909: 2841647 ] : The usage of SAP S/4HANA Finance for group reporting in conjunction with the component Enterprise Controlling - Consolidation (EC-CS) in the same system / client is only supported in the context of the transition from EC-CS to S/4HANA Finance for group reporting (see note 2833748).
  2. [ Version 1909: 2841647] : Only one dimension can be used and it must be the delivered dimension Y1-Companies. The dimension Y1 is defined for the consolidation type Company. Only this consolidation type is supported.[ Version 1909: 2841647] : It is not supported, within one version, to assign different ledgers to the different consolidation groups. When multiple group currencies are required for consolidation groups, the corresponding ledgers must be assigned to the consolidation groups in different versions. For example, in the version Y10, it is not possible to assign the ledger Y1 to the consolidation group CG1, and to assign, in the same version Y10 the ledger Y2 to the consolidation group CG2.
  3. [ Version 1909: 2841647] : The deletion of version is not supported.
  4. [ Version 1909: 2841647] : The period category 9 (Months) is delivered. Additional period categories can be defined but only for the purpose of assigning different validation methods to different period categories. Other period categories than the delivered 9 (Months) cannot be used to assign tasks groups to the dimension.
  5.  [Version 1909: 2841647] : SAP delivers a set of FS items attributes (elimination, currency translation, role, target...). Adding new values for the delivered attributes is possible. Creating new attributes is not supported. There is one selection attribute “Other Selection” which is delivered without any semantic and attribute values. It is possible to add values for this attribute and use it for user specific purpose.
  6. [Version 1909: 2841647] : Automatic postings of the Annual Net Income and Deferred Tax posted to the B/S and I/S (selected FS items) do not inherit additional fields such as Profit Center or Segment from the triggering data. This statement is valid both for journal entries and Retained Earnings calculation task.
  7. [Version 1909: 2841647] : The option (field FOCTR) to force the currency translation when the local currency is the same as the group currency is not supported.
  8. [Version 1909: 2841647] : With the rules-based approach, the consolidation adjustments required for the consolidation of units according to at-equity method must be posted manually (no automatic adjustments for accounting technique 4 (Equity method)).
  9. [Version 1909: 2841647] : New Group Reporting Logic is only activated by default when release 1909 is installed. To activate the New Group Reporting Logic after a system upgrade to 1909 you must open a customer message on SAP Service Marketplace on the FIN-CS-COR-MD component. SAP strongly recommends this upgrade. Future feature enhancements might only get supported when New Group Reporting Logic is active.
  10. [Version 1909: 2841647] : When the New Group Reporting logic is active, the App Interunit Reconciliation - Group View is not supported.
  11. [Version 1909: 2841647] Only one unit of measure can be assigned to a breakdown category. Data cannot be reported with a different unit of measure for the FS (Financial Statement) items using this breakdown category.
  12. [Version 1909: 2841647] : Usage of fiscal year variants: restrictions and additional information are collected in note 2775445.
  13. [Version 1909: 2841647] : Consolidation of investments (Activity-based): restrictions and additional information are collected in note 2813262.
  14. [Version 1909: 2841647] : In the reports available in the tile group Group Reports that are based on the old queries for consolidated data ( <rel 1909), the drill-through to consolidation reports shows a technical integration document, and not the document of origin.
  15. External APIs always write reported financial data to a unique document type with Business Application E.
  16. [Version 1909: 2841647] : The SAP Group Reporting Data Collection Application on the SAP Cloud Platform cannot be used with the on-premise version of SAP S/4HANA Finance for group reporting. SAP plans to remove this restriction in a future release of SAP Cloud Platform.
  17. [Version 1909: 2841647] : In 1909 FPS1, when using custom fields in Group Reporting, following types of a custom field are not supported: Amount with Currency, Number, Quantity with Unit, Timestamp. The following functionality does not display custom fields:
    • Task Log
    • Analytical buttons in Release Universal Journals:
      • Universal Documents (Totals)
      • Universal Documents (Difference)
      • Data from Prior Periods Without Release
  18. As a workaround, you can display desired data including custom fields via Display Group Journal Entries application.
  19. [Version 1909: 2775445] : Maximum number of periods: The number of periods in S/4HANA for group reporting is limited to a maximum of 16 periods (12 normal periods, 4 special periods). As a consequence:
  20. In the Global Parameters it is not possible to select a period higher than 16
  21. In the Manage Group Structure App, when a consolidation unit is divested, the last period for the assignment to the group is set to 16
  22. The fiscal year variant assigned to the consolidation units must include a maximum of 12 normal periods and 4 special periods.
  23. [Version 1909: 2775445] : Execution of Reclassification tasks : When a Reclassification method includes, in the Trigger tab and Percentage tab, a Selection with nodes from a time-dependent hierarchy, the system date is used to select the hierarchy (and not the date which corresponds to the period / year execution of the task).
  24. [Version 1909: 2775445] : Execution of Validation tasks / App : When a Validation rule includes a Selection with nodes from a time-dependent hierarchy, the fiscal year variant K4 is used to translate the period / year of the execution into the calendar date for the selection of the hierarchy.
  25. [Version 1909: 2775445] : Execution of Release Universal Journals Task: When data transfer method "Read from Universal document" is used, the posting period in Group Reporting is derived from the Accounting posting date and not from the Accounting posting period. The fiscal year variant from the consolidation unit master data is used to translate the posting date to the period, and special periods are not supported. Hence, accounting documents in special periods are assigned in Group Reporting to the period of the Posting date.
  26. [Version 1909: 2775445] : Value lists :
    1. In the prompt of Local Reports, the value list for the field Posting Period shows values #, and from 1 to 366. Only values #, and from 1 to 16 can be used.
    2. In the prompt of Group Data Analysis reports, the value list for the field Fiscal Year Period shows in the text column the names of the months aligned with the calendar. For example the text for 007/2018 is JUL 2018.
    3. In the Task Log App, the value list for the field Fiscal Year Period only shows the values for the fiscal year variant K4.
    4. In the Post Journal Entry App, the value list for the field Posting Period shows the periods defined in the fiscal year variant K4.
    5.  In the Assign Reporting Rules App the value list for the field Period / Year shows the months aligned with the calendar. For example, March corresponds to period 03.
    6.  For a lean adoption of possible future enhancements in S/4HANA for group reporting SAP strongly recommends to assign to the consolidation unit the same fiscal year variant which is assigned to the corresponding Company Code in the source ledger which contains the group valuation.