on 2022 Jun 16 5:44 PM
Hi all,
I am facing this issue:
In S4HANA ACDOCA the company and the trading partner don't have the same ID, for example the consolidation unit has the code “300” and the trading partner of the same legal entity has the code “TP300”
For example:
Company code trading partner
300 TP300
400 TP400
…. ….
Does anyone knows how can I manage this different code in Group reporting?
Thank you in advance for your help!
Request clarification before answering.
I think you would have to use TP300 and TP400 as your cons units. It should map the company code --> company --> consolidation unit. I'm not sure if in the recent release with the Group Reporting Preparation Ledger concept in the GL if you can derive something different; that might be a possibility, though.
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is an issue for our implementation as well. The mapping offered in the latest release (for both Cloud and on-Prem) is that Cons Unit is a separate entity within GR; the Company value from T880 is mapped to the Cons Unit. However, the company code values cannot be mapped to Cons Units. The company value is the important parameter here; so this is an issue. If the company value is TP300 then that is what will be mapped to the Cons Unit - but the ACDOCA balances are held against company code 300. So I am not sure what data the Release Univ Journals step will pull into ACDOCU.
Thanks,
Sri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Florian,
Why within Group reporting there always is the same ID in the consolidation unit and in the partner unit, but in ACDOCA is it possible to have different code between company and trading partner without any custom settings?
The ACDOCU is a copy of ACDOCA, so it should be possible to manage in Group reporting different code in the consolidation unit and in the partner unit as managed in S4/HANA ACDOCA (accounting).
Thanks
Kind regards
Chiara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
thanks Christopher for your reply. Adding to what you mentioned already the roadmap item which is planned to offer the flexibility of Consolidation Unit definition in the accounting integration case. With this the consolidation unit will be able to carry a different ID than the company ID in accounting.
Note that within Group Reporting there always is an ID identity between the entity and partner for all objects (cons unit - partner unit; profit center - partner profit center; segment - partner segment, etc.)
Kind regards,
Florian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chris,
Thanks, so it means that the solution should be to create the consolidation unit with code TP300, but the customer's requirement is to keep the code 300 for the consolidation unit and the code TP300 for the partner unit.
The recent release (GR Preparation Ledger concept in the GL) is available only for SAP S4 HANA CLOUD GR 2202, but we have the group reporting only on premise, so I cannot explore this possibility,
Best Regards
Chiara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 29 | |
| 14 | |
| 14 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.