Skip to Content
Product Information

Demystifying S4HANA Group Reporting

Group Reporting is the newest tool embedded in SAP S/4HANA providing statutory as well as managerial financial consolidation capabilities for both On-Premise and Cloud customers.

What you will learn from the Blog Post

Overview and Positioning of Group Reporting and know more about the basic building blocks.

Summary

The blog post covers the Rationale for Group Reporting, Product positioning and differentiation, and a detailed look at the key Building Blocks in terms of Key Configuration Elements and Master Data.

The focus is on On-Premise solution as of release 1809. This document touches on the pre-configured settings of the best practice content.

I will aim at covering the Consolidation Processes, Settings and Reporting in my subsequent blog post.

 

Why Group Reporting

Preparation of Consolidated Financial Statements is mandatory for Statutory compliance, example IFRS10. Applicable Accounting Principles outline the requirements for producing such statements.

SAP’s Group Reporting tool facilitates not just in the preparation Financial Statements as per Statutory regulations, but also has added capabilities for facilitating managerial consolidation and analytics.

 

Overview of Key Capabilities

  • Local and Group Close in the same tool
  • Flexible rules for Data Validation
  • Currency Translation
  • Inter-Unit Elimination
  • Consolidation of Investments
  • Data Collection options – Release from Universal Journal, Flexible Upload of Reported Financial Data, or Published APIs from Other SAP or Customer applications.
  • Possibility to perform Data entry at desired level within the consolidation system.
  • Record Ownership information using Journal entries on Statistical items.
  • Manual Top-up Adjustment for Elimination where ever needed

Details of these will be covered in a separate blog post.

 

Product Positioning

SAP S/4HANA for Group reporting is SAP’s strategic consolidation solution moving forward, in particular for customers implementing SAP S/4HANA irrespective of deployment option (cloud or on premise) as well as for customers looking for a public cloud stand-alone offering. Group reporting can be used independently from operational accounting or other ERP functions in SAP S/4HANA if desired.

The picture below taken from SAP’s presentation on product vision, explains how Group Reporting fits into the landscape.

Group Reporting vis-à-vis other Consolidation Products

The new Group Reporting Tool combines the best of the features and capabilities of existing tools, leveraging and well-integrated with Sap Analytics for Cloud.

  • Embedded in S4HANA, hence no need of an ETL or Data Warehousing Tool like BW to intermediate between the transaction system and the consolidation system. Data flow from transaction system to the Consolidation system is Realtime.
  • Fully enabled drill-through from Group Reporting to the line-items of the entity, leveraging all details of the underlying Universal Journal.
  • Introducing FS Items, replacing the Group CoA. The set up and maintenance of FS Items is managed inside Group Reporting, which means Operating Chart of Accounts are not disturbed.
  • Rule based Eliminations and Reports, with data generation by desired breakdown items.
  • Local close and group close share the same master data / rules.
  • SAP Group Reporting Data Collection is an additional Cloud-based Data Collection application delivered on the SAP Cloud Platform, with native integration to S/4 HANA Group Reporting
  • Roadmap for integration to Disclosure Management.

 

 

 

Building Blocks

Technical

A mandatory prerequisite for running S4H Group Reporting is to install the best practices configuration content for the solution. You can only make changes to consolidation-relevant settings in Customizing for SAP S/4HANA for Group Reporting afterwards. For more information on installing the best practices content, see the administration guide on SAP Help Portal

Relevant Scope Item in the Building Block Builder is XX_1SG_OP.

Functional

Key configurable Elements in Group Reporting are explained below

  1. Consolidation Ledger: A ledger to store documents generated by the consolidation tool.

A consolidation Ledger contains the Source Ledger and the Currency. So for consolidation as per differing accounting principles, you can create requisite number of consolidation ledgers.

Notes:

  • As of the current release, system allows creation of Consolidation Ledger code starting with “C”.
  • All Consolidation Groups should carry the same Ledger in one Version, to ensure consistency in Global parameters.

2.  Version: A consolidation version is used for identifying a separate data area in the consolidation database. Versions make it possible to consolidate different sets of financial data.

A Version may also be created if you want to perform separate methods of consolidation on the same set of underlying data.

For example – You create a version for consolidating Plan Data alongside one for consolidating Actual Data.

You may also create a new version for performing Restatement of Actual Data.

Notes:

  • Further specifications of Special Version allows you to use different methods or rules for achieving the specific Consolidation effect.

3.  Dimension : Dimension reflects the basis for consolidation. Default delivered dimension is Company. So as of the current release, Consolidation process happens at Company level.

 

4.  Financial Statement Items: This is the most crucial element in Group Reporting.

FS Items replaces the old world ‘Group CoA’. FS Items are linked to the Operating accounts in the Consolidation system. The basic accounting system (ex: SAP FICO) remains untouched by the FS Item.

SAP delivers a comprehensive set of FS items as part of the best practice content. FS items form the backbone of the consolidation process. Definition of FS Item contains:

  • Types of the Item – Classification on the basis of Nature of the Item
    • INC: Income items in P&L statements
    • EXP: Expense items in P&L statements
    • AST: Asset items in balance sheets
    • LEQ: Liabilities and equity items in balance sheets
    • STAT: Statistical items that can be used to record financial and non-financial data. This data is not directly linked into P&L statements or balance sheets, such as headcount information.
    • REPT: Reporting items that are used in reporting. Dedicated hierarchies can be defined for reporting items, and respective reporting rules can be defined to derive values of the reporting items.
  • Attributes relevant for automating the consolidation processes like Currency Translation, Elimination and Consolidation of Investment (CoI).
  • Controls input of further parameters such as consolidation transaction types, Functional Areas, Partner Unit etc – called Breakdown Category
  • Balance Sheet and P&L structure in hierarchical fashion

Notes:

  • Fiori App ‘Import Master Data for Consolidation Fields’ has predefined template of FS Items with all these associated attributes. Click on ‘Download Template’ and select ‘Financial Statement Item’ in the Master Data Type Selection dropdown.
  • Creation of New FS Items should carefully consider all parameters starting from transaction recording up until reporting.
  • Tagging FS Item to Operational Chart of Accounts is a prerequisite to read data directly from the Universal Journal. App ‘Assign FS Item Mapping’ can be used. For mass load, you can download the template and upload it with relevant data using App ‘Import Master Data for Consolidation Fields’.
  • There are separate settings to specify how the FS Items should be Carried forward to the next year.
  • Separate configuration setting is available to specify Automatic posting FS Items, like FS Item for P&L Net Income, FS Item for Rolling that up into a Balance Sheet, FS Items for posting Deferred Tax, etc.
  • Every newly created GL account should be mapped to an FS Item (existing or new FS Item). So the periodic Operating CoA maintenance activity should include this important step.

FS Items are grouped into Reporting Items, which in turn are grouped into reporting Hierarchies. ‘Manage Global Accounting Hierarchies’ App allows a quick look into understanding the construct, making edits or even creating your own Reporting Hierarchies.

On expanding an item, you see the details like below

Mass upload of mapping of FS Items to GL account is done using below app

The dropdown has the following options

 

5.  Sub items : Sub items help in getting a horizontal build of an account. Consolidation Transaction Types are for Balance sheet accounts and Functional Area are for Profit and Loss accounts.

It is possible to add more sub items by way of configuration.

The Sub items are largely organized into Categories.

SAP Best Practices provides the following two Sub item Categories –

  • Transaction Types
  • Functional Areas

At the Sub item level, some could be reserved for exclusive use in the consolidation system. This can be realized by checking ‘No Posting/Entry’ check box.

Notes:

  • Sub items are linked to the FS Items through ‘Breakdown Categories’. Breakdown categories define the status and permissible list of sub items for an FS Item, and are assigned to FS Item.

Example : For FS Item denoting ‘Provisions’, transaction types (Sub item category 1) are mandatory. So the Breakdown Category tagged to the FS Item should have Transaction type as mandatory and could additionally specify a set of permissible transaction types as well.

  • Default value assignment for sub items is possible too.

Default Sub Item assignment ensures population of default values for the data in consolidation system

 

6.  Document types : Like in the SAP transaction system (SAP FICO), document types are used to segregate operations within the consolidation system.

Controls within Document Type –

  • Posting level – indicates the type and level of consolidation adjustment. Posting level enables a selection of data by content.
  • Data Source – manual or automatic posting, file upload, or API
  • Automatic Reversal and Reversal spilled over to next year– whether the document is valid only for one period of the current year, and whether the reversal should be restricted to the current year alone.
  • Currencies – Control on the currency relevant for the posting
  • Deferred Income Tax – whether the document type is relevant for deferred tax posting
  • Balance check – whether the document needs to balance to zero and consequent reaction if it doesn’t.

List of pre-delivered document types –

Controls provided in the Document Type definition

 

7.  Selection IDs : Selections are a group or set of consolidation master data like FS Items, Sub items, Document types etc to be used in consolidation-related settings.

They resemble the “set” in the SAP FICO system, just that Selection IDs can contain more than one field parameter.

Example : For a requirement where Opening balances on certain Balance sheet items are to be translated at Average Rate – you would define a Selection ID with the specific FS Items representing the Balance sheet items and add the transaction type that denotes Opening balance. Now this Selection ID could be called inside the Currency Translation Method and tagged to the Average Rate.

 

Selection ID with more than one field parameter, namely FS Items and Transaction type is shown below

Selection ID with single field parameter – Transaction Type is shown below

Where-used list helps in tracing down the usage of a particular Selection ID

Roadmap

Below interesting features part of the product vision will simplify complex and advanced processes in Consolidation :

Matrix Consolidation

Group Structure and Ownership Manager

Multiple subgroup currencies

Integration into Financial Closing Cockpit,

Automated InterUnit Profit Elimination from Inventory

Integration Scenarios with planning applications

Advanced Intercompany Reconciliation

Intelligent Data Validation leveraging Machine Learning

Some of these features are already available in the Cloud Edition, for instance Matrix Consolidation, Group Structure & Ownership Manager.

 

Further References

SAP Help

SAP Best Practice

 

This post intends to give a round up on Group Reporting and the basic elements.

Thank you for going through the post.Your feedback and comments will help me make it more relevant to the community.

63 Comments
You must be Logged on to comment or reply to a post.
  • Hi Gayathri,

    Your blog is really helpful for us at a time when we are looking for precisely the right solution on the development of reports on consolidated financial statements.

    Please refer to the link https://answers.sap.com/questions/12673188/how-to-develop-consolidated-financial-statements-i.html

    where I posted few questions on how to do develop reports on consolidation of financial statements in the absence of BPC. Please note that I am a BW and HANA consultant and not a FI functional consultant.

    I know you have mentioned that you will cover consolidation process in subsequent blog but I have few questions for which I’ve been looking for answers for a while now.

    1. In our current project we only have S/4HANA Embedded Analytics and BW/4HANA in scope. We are on S/4HANA 1809 On Premise. The client has not bought license for Group reporting. BPC is also not in scope here.
    2. I see the following CDS views in Fiori (Image attached) but I see that in the description of each Consolidated CDS view the word cloud appears within square brackets [Cloud]. So my question is, can we use these CDS views to consolidate the data and develop the reports in Webi? Please note we are on S/4HAN1809 On Premise not on cloud.
      1. Our client has two company codes, and 1 chart of accounts. From the requirements gathered the client is looking to consolidate data between their two entities, one in Middle East and the other in Europe and report it in USD. They are also looking for intercompany elimination.
      2. So can all these be achieved using the standard CDS views mentioned below?
      3. If these are not the right ones can you please let me know the correct ones?

        C_CNSLDTDTOTALS11Q – Consolidated Balance Sheet [Cloud]

        Consolidated Balance Sheet – Year Comparison [Cloud]

        Consolidated Balance Sheet – By Subgroups [Cloud]

        Consolidated Balance Sheet – By Movements [Cloud]

        Consolidated P&L by Nature [Cloud]

        Consolidated P&L by Nature – Year Comparison [Cloud]

        Consolidated P&L by Nature – By Subgroups [Cloud]

      4. Or do we need to customize these CDS views?
      5. What are the functional steps need to be completed by the FI consultant before the analytics team can start using these CDS views to consolidate the data?
      6. Actually where does the consolidation take place? Is it within the CDS views or should it be done as part of the FI activity and then we report using the CDS views?

    Please explain.

    Thank you.

    Regards,

    Pavan.

    • Hi Pavan

      Glad to note that the blog was of some help to you.

      I would take your last question first – you need a tool like Group Reporting or BPC for Consolidating Financial Statements. It cannot happen just using CDS views, since it is not just a report, but there are series of steps posting adjustments to the data.

      If client chooses Group Reporting tool, the database table for all the consolidation reports would be ACDOCU.

      Few quick facts on Group reporting that might be of key help to you:

      • You wont need BW for Consolidation and Reporting since Group Reporting is part of the S4H.
      • Most used key reports for consolidation like Consolidated Financial Statements, Cash Flows, Statement of Changes in Equity, Statement of Comprehensive Income are pre-delivered !
      • Tweaking these reports is possible for a functional consultant, while I hear creating new ones basis ACDOCU table is easy.

      The help link below talks specifically about the Reporting capability of the tool –

      https://help.sap.com/viewer/4ebf1502064b406c964b0911adfb3f01/1809.000/en-US/1790118335a04f2b92a581ad1563f12c.html

      Hope this help.

       

      Thanks

      Gayathri

       

  • Hi Pavan

     

    Your requirement is met with S4H 1809 version in  S4 GROUP REPOTING Module which is  on SAP Road map instead of BPC tool. Even if you go by BPC one point of time you have to go to Group Reporting or Cloud based Consolidation.

    ” Any customer wants to implement Consolidation/Budgeting/Planning(Managerial Consolidation not Actual Planning) can be achieved  from S4H1809(OP)

     

    • S4H 1809 only supports Legal Consolidation based on Company/Co Code basis of FI *** NO MATRIX Consolidation***
    • There is no Profit Center based Consolidation in 1809
    • Prebuilt reports are available what you have requirement will be met, I am pretty sure 95% of reports in SAP Analysis( Excel)
    • You  have option of FS Items of FI – GL side and or GROUP ACCOUNT  which is Now as FS Items(Financial Statement Items) either 1:1 and or M:1
    • Fully Integrated Company/Co Code from FI
    • You can do multi ledger Consolidation(ME/Europe)
    • All  RFD(Reported Financial Data) in LC will be readily available in ACDOCA table and S4Grp will access instantly ie. NO NEED to Load/Customize Cubes like in BPC
    • Any Given a Day during normal month and not even closing dates of Accounting dept, can be run Consolidation by simply executing the Task of ” DATA LOAD”
    • For reporting all your Consolidation data is available in ACDOCU – Consolidation Universal table from LC to USD/EUR/ etc
    • You can plan Consolidation numbers for short range and or Long range ie Feature year and Years
    • You can do Matrix Consolidation FROM S4H1902( release 1902 -OP in SEPT of 2019 +/- of Month)
    •  
    • In Matrix Consolidation: you can do Consolidation in a single shot and Reports for Legal and Management Consolidations
    •  
    • You want to go for Prebuilt system then OPT for S4Cloud 1905 has Matrix Consolidation also

    Hope this will help you

    Thanks

    Venkat

  • Hi Gayathri, Venkat,

    Thanks a lot for your replies. Really appreciate it. But is it true that Group Reporting requires a separate license in addition to the standard S/4HANA 1809 On Premise license? Not sure if you are the right person to answer this.

    We are at a stage where we can not push the client to obtain an additional license for Group Reporting. We need to consolidate data with out Group Reporting and BPC. 🙂

    So we are working on a probable solution to achieve the consolidation by customizing the standard CDS views available for consolidation.

    Any additional inputs would really be appreciated.

    Thank you.

    Pavan.

    • Hi Pavan

      Yes, Group Reporting requires additional license in addition to S4H OP license.

      Sales team will be in better position to answer you on how to approach & couple the cost.

      And Financial Consolidation cannot be achieved just by CDS views or info-cube modelling.

      Thanks

      Gayathri

  • Hi Pavan

     

    Please come out of your CDS views and etc. Because it is required additional server like BPC where you integrate via BW/BI – Embedded

    All data including Flat files are including in CONSOLIDATION UNIVERSAL Journal

    Thanks

    Venkat

     

     

     

  • Hi Ms. Gayathri

    You are a fabulous blogger. Thanks for sharing great deal of information

    One Q – Can you help me join the JAM group please for Group Reporting. My S User is S0020268226

    Regards

  • Dear Mr. Ajay

    I have been your avid follower especially on SCN. You have been a guiding light to say the least, and this encouragement from you means a lot to me 🙂

     

    The Private JAM Group is administered by core group people and I am not one of them. You can request for access by emailing the owner of the FAQ note 2659672.

    Hope this helps.

    Thanks

    Gayathri

  • Hi Gayatri,

     

    This Blog was very informative. Thanks.

    We will be implementing Group Consolidation on S4 Hana Public Cloud 1905 for a  very big group of Companies in the Middle East.

    We have just Kicked started the Project & I will need your advice and tips along the way.

    Thanks in Advance.

    Regards,

     

    Randal

     

  • Hi Gayathri,

    Thanks for this excellent blog.

    Since this looks like the way forward for consolidation, what does it mean for BPC as a product? Will it be deprecated at some stage by SAP?

    Looking forward to your next blog (with process and settings)

    Reg

    Abhinav

     

     

     

  • Hi Gayathri,

     

    Thank you for the excelent post in this Blog.

    I have a question. We are working for a scenario where the customer is running on SAP ECC 6.0. They don’t have S/4 Hana implemented yet.

    They want to implement S/4Hana Group Reporting on Cloud using FI-GL data from SAP ECC.

    Is this a feasible scenario ? As S/4 Hana Group Reporting use ACDOCA (universal Journal table), how can we use it if the customer is still running on ECC 6.0 ?

    In this scenario, should we suggest them to implement Central Finance ?

    Thank you

     

    Regards,

     

    William Terceiro

    SAP Brasil

     

     

     

     

     

     

     

     

    • Hi William

       

      I believe that you can use  ECC to S4H Grp Reporting only on Cloud based and as you mentioned correctly  that Customer should be using FI-GL module/scenario.

      1.Customer can utilize Cloud based application for Data Collection(FI-GL) – “SAP GROUP REPORTING DATA COLLECTION ” Application to load data

      Link:

      https://help.sap.com/viewer/4ebf1502064b406c964b0911adfb3f01/1809.000/en-US/c27c73226dac4e07ac8aa59a45f92fd8.html

      2. If not then , they can use Flat File upload methodology(Not sure how big is the customer SAP environment)

      3. Master data either you can MAP or create their own FS Items etc  in Consolidation > Customer own MD will be time consuming ( Create from scratch)

      4. Better to have latest version S4C 1905 where you will get MATRIX CONSOLIDATION  feature as Legal and Management Consolidation

      5. S4C1905 will have all latest and most advanced Consolidation features compare to S4H1809(OP)

      Hope this will helps you

      Thanks

      Venkat

       

       

       

       

       

       

       

    • Hi William

      Yes,  there are multiple options to implement Group reporting in such a scenario:

      1. The Data Collection App on cloud should work in this case.
      2. You can also explore Published APIs to load data from other SAP systems into Group Reporting
      3. Central Finance could also be an option, as it will help the client unleash S4 innovations in the longer run. While at it, please also evaluate the other options on moving to S4.

      Thanks

      Gayathri

       

  • Hello Gayathri Krishnamachary,

    Thanks for providing the configuration details. Can you also please let me know the report execution / generation using the FIORI apps or GUI along with App name and Transaction code for the above configuration.

    Waiting for your response.

    Regards

    Ranjit

     

    • hi Saida

      the best practice content 1SG for Group Reporting can help you on this question. Please refer to the Implementation Guide there.

      OSS Note 2659672 also has link to some documentations.

       

      thanks

      Gayathri

       

  • S4H GRPTING is an new Consolidation tool for Legal and Management Consolidation with full functionalities/regular activities of Consolidation as of S4H 1809 and where as S4H 1909 will have more advanced Consolidation features and also MATRIX Consolidation

    where as IC Recon tool is only applicable to one element of Intercompany Accounts and nothing else out of that for final reporting

    IC Recon tool assists to any Consolidation process to speed up the IC Tasks and eliminate time consumption when you have un recon IC transaction which will be any customer’s nightmare

     

    Hope this will help you

     

    Thanks

    Venkat

  • Hi Gayathri,

    Thanks for sharing the inputs on Group reporting!

    I have a question not related to GR. My client is having S4H1809 . Is it possible to implement Standard BPC Consolidation on S4H1809.

    Thanks

    Kishore V

    • hi Avinash

      as of 1809 OP there are 37 fields available in GR and you can adjust these fields as input fields, master data fields, or hierarchical master data in your consolidation process and related analysis reports.

      There is no possibility to add new fields as of now. We may expect this in future – please refer to roadmap for indicative timelines.

      Hope this helps.

      thanks

      Gayathri

  • Hello Gayathri,

    Thanks for excellent blog. It does really give a lot of insights in Group reporting

    As SAP’s Group Reporting tool facilitates not just in the preparation of Financial Statements as per Statutory regulations but also has added capabilities for facilitating managerial consolidation and analytics.- Does it support Multiple Valuations too { for example We have Profit Center valuation (for inventory processes) activated where we do an internal transfer between two BUS (PC1to PC2) to get the correct internal profitability for the management view. Does Group reporting supports multiple Valuation (Currency Type 32).

     

    Thanks

    Regards

    Ketan

    • hi Ketan

      thanks for the note. The Cons. Ledger in Group Reporting provides you the flexibility to choose the Consolidation currency – which could be defined same as your PC Val Currency.

      You can then choose to pick data in this currency from ACDOCA for each of the Cons. Unit. So yes, the basic premise is that the currency is present in ACDOCA.

      Hope this helps.

      Thanks

      Gayathri

      • Hello Gayathri,

        Thanks for your reply, is it not possible to have both Legal valuations ( Say Currency 1) and Profit Center Valuation( Currency 3) at the same time.

        Thanks

        Ketan

        • hi Ketan

          your question was on possibility to read PC val currency – and I do not think why that should be blocked if its available in ACDOCA.

          as of ‘using at the same time’ – please clarify the requirement.

          BR

          Gayathri

        • Hi Ketan

          1. Your Legal valuations ( Say Currency 1)  is your Company Code Currency ie. LC
          2. Profit Center Valuation( Currency 3), Can be Group Currency 30(USD) which is based on US Companies
          3.    or   You can do 3 rd Currency (Other than Group Currency)also but you have to some additional settings/ to better understand.

          Thanks

          Venkat

  • Hi Gayathri,

    I am about to start a new implementation of Group Reporting  and a question came out:

    We may need to bring fields from acdoca to support some transactions that need to be eliminated at the consolidation level in acdocu

    Can fields in acdoca that are not in acdocu be added in acdocu ?

    We will be implementing Group Reporting 1909.

    Any thoughts are very much appreciated.

    Thank You!

     

     

  • Hi Gayathri Krishnamachary, and thank you for your great blog post.

     

    We are implementing GR 1909 on S/41909 with joint venture accounting and I have a couple of questions.

    Does Group reporting use the traditional Group Chart of accounts from SAP FI or will the operating chart only be required?

    Is there an option to extend ACDOCU to include joint venture accounting fields or is the recommendation to define another elimination object (e.g. Profit centre) to represent the Joint ventures?

    Many thanks!

    Phil

    • Hi Phil

       

      Group Reporting doesnot need or use Group CoA. It has a different Chart of Accounts.

      so all it needs from the operating system is the Operating CoA and certain other master data like Cons ttype.

      The Op CoA is mapped to Consolidation chart of Accounts inside of the GR module.

      Reg extensibility of ACDOCU – you may wait until FPS1 for this.

      As of now, please check the Additional Characteristics available in GR and backwork in the accounting system to use these to capture all relevant financials.

      Since you mention JV – I assume you explored the Equity Method of Accounting.

      thanks

      Gayathri

  • Hi, Gayathri,

    I have working on this feature following the blogs https://blogs.sap.com/2018/09/29/s4hana-1809-bp-activation-process-with-errors-encountered-solution/ , to prepare a demonstration to my customers. However, there are still some issues.

    From notes 2659672 – FAQ About SAP S4HANA Finance for Group Reporting (On Premise) section 1.1, “Note for SAP S/4HANA 1809, for running Group Reporting it is a mandatory prerequisite to install the BP content (scope item 1SG) for the solution”

    However, when I try to activate the 1SG the scope item, the system prompt the message.

    And my system version info is that.

    Please give me some suggestions, as I want to use this function in customer OP environments, thanks!

    Flex Yang

  • Hi Gayathri

    Blog followed by your detailed answers to multiple queries is much appreciated. I have following queries about GR

    1. If customer is already using EC-CS, What are additional functionalities offered by GRP ?
    2. Can EC-CS and GRP co-exist in same system ? If Yes, are there any limitations.

    Regards

    Kapil

      • hi Gayathri,

        Currently im checking the configuration in our sandbox which EC-CS and GRP co-exist.
        I cannot access/use function “Configuration of Additional Characteristic” in Group Reporting. The note 2833748 given shown the process steps to solve the issue, but if i install SAP best practice content or or initialize the global settings for consolidation, will it help resolve this issue? or i still need to go through the note.

        Thanks for your reply and great post!

         

         

        • Hi Hafizah

          The note details out on what needs to be done to activate GR if EC-CS is already active.

          There are prerequisites like the ‘From year’ considering the desired system state.

          GR config will not be enabled till the pre-requisites are met.

          Suggest you to take a closer look of the note.

          If a migration of production system is the final goal, please raise an OSS incident to SAP support.

          thanks

          Gayathri

  • Hello Gayathri,

    First of all, nice post. With the context of this, would like to ask a question on version 1909.

    I am using this version and have created CUs with respect to companies. Let’s talk about 2 of them.

    1. CU X – Company X – ‘Release Universal Journal’ active on Data Monitor.
    2. CU Y – Company Y – ‘Release Universal Journals’ NOT active/enabled on Data Monitor.

    Both of the CUs are having same setting – with reading from universal document selected as data collection method and difference in local currency(for CU X: HRK and for CU Y:EUR). Both of them are having exactly same setting under FINSC_LEDGER, with respect to local and global currency types.

    With your experience in GR and with this limited information. do you suspect any missing element or misalignment?

    Regards & all the best for your future explorations !

    • Hi

      Hope the issue is solved, if not try by changing the CU Y data collection method (again bring it back to Read from UJ).

      The reset the data monitor – the issue should be solved.

       

      thanks

      Gayathri

  • Hi Gayathri,

     

    Based on your GR implementation experience, will business focal configure the Special Version assignment, or still the consultant will perform this activity?

    Thank you.

     

     

    • Hi Hafizah

      Special Version and assignment is part of IMG.

      Anything with IMG is mostly dealt with by the functional consultant, should be no different in here as well.

       

      thanks

      Gayathri

  • Hi Gayathri,

    Good blog. Do you have any information on how to transport Group reporting objects. For eg. global setting objects like: Consolidation COA- Y1, Consolidation Ledger-Y1, Dimension-Y1. There is no option to transport them. There is no clear information available anywhere on SAP help or other document on what can be transported or what needs to be maintained directly in target system?

    Why doesn’t SAP provide access to URLs in section 1.17 on transport in SAP note 2659672 (FAQ about S/4 HANA for Group Reporting): Master data and configuration settings ?

    Appreciate your response.

    Kind Regards,

    Manish