on 2024 Oct 03 2:59 PM - last edited on 2024 Oct 07 7:31 PM by jerryjanda
Hello,
I was trying to create a Financial Statement Version in the production environment using the Manage Global Hierarchies app. At first I tried to import an existing Financial Statement Version, but I got the error that I don't have the authorization to do so. I have role BG_GL_ACCOUNTANT assigned with the business catalog 'SAP_SFIN_BC_GL_MD_COA' and there are no restrictions on this role.
Next I tried to create one from scratch so that I could try to use the import function. But here I see that the Financial Statement Version is not available as an option to create:
And the authorization should be correct for this.
So what I did instead is I converted the existing (and relevant) FSV to the Global Hierarchies using the 'Migrate Financial Statement Versions to Global Hierarchies' and I have transported this to the P system (2SL with CBC). I do now see the Financial Statement Version in the Global Hierarchies app, but I can't maintain it:
I did see this topic: https://community.sap.com/t5/enterprise-resource-planning-q-a/manage-global-hierarchies-financial-st... and this mentions Q2P being active and then you can't edit FSV in the P system and I found a note 3092272 which is about semantic tags but also mentions the Q2P. But here is where I'm confused, how do I know whether Q2P is active or not? And does this mean that if I make sure Q2P is not active for Financial Statement Versions that we can edit & create FSV in the P environment?
Because obviously I want the key user to be able to maintain the Financial Statement Version using the Global Hierarchies going forward and not to have this maintenance stuck in the Q/CBC environment. But now I can't create a Financial Statement Version nor edit an existing Financial Statement Version.
Hello,
the reason you had to do the conversion is FSVs defined in Define Financial Statement Versions (Classic OB58) is different and stored in different database tables than FSVs define in Manage Global Hierarchies.
Q2P is term more often refers to internal testing system, where there can only one client, Sandbox or testing system client. in customer use cases, Q2P should always be active, there is no setting to turn it off. there is always Quality system connected to P system( 2SL), or D system, Q system and P system(3SL).
As for FSVs maintenance in Global Hierarchies, unfortunately, it has to be maintained in Q and transported to P. refer to Manage Global Hierarchies | SAP Help Portal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Thank you for your answer. I don't quite understand why we need to go through the CBC to maintain the FSV, as I thought the whole point of the Global Hierarchies is to give the ability to maintain hierarchies to the key user.
Is is on the roadmap that this will be changed in the future? But for now, we will work with the CBC and transport this then.
User | Count |
---|---|
104 | |
10 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.