on 2018 May 25 1:23 PM
Hi Experts,
We have a business requirement to implement real time consolidation for e.g. 10 entities. Of these, 8 belong to S/4 where you have the corresponding company codes and company id associated with it. The remaining two entities are not in S/4 but they need to consolidated within RTC. The base data is to be uploaded using Flexible upload.
I need your suggestions on the approach that we are planning to take. We intend to create 2 model companies in SPRO (and not company codes). Then launch RTCENT to maintain the entities to be used in Real Time Consolidation. Here, create two new entities and associate the 2 model company ids to these entities.
Please suggest if this business requirement is valid and whether the approach is feasible.
Regards
Sushant Pradhan
Request clarification before answering.
Not sure if get what you're asking but here's how usually you'd handle companies not in S/4.
RTCENT will require that the entities exist in S/4 master data. Even the external ones. And as you already indicated you're going to use COMPANY (RCOMP), what you need to do is to maintain the non-S/4 companies as trading partners t-code OX15 (table T880). The S/4 company codes probably already exist as trading partners but if they don't you'll need to maintain those as trading partners as well.
A bit of background here: As you might have noticed the default entity field in RTC is RCOMP and not RBUKRS and the reason for that is exactly because of scenarios such as yours because to the trading partner allow this flexibility different than the company code field T001.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Lucas for your understanding. I tried this some hands on and faced few roadblocks.
Surprisingly, looking at the overall configuration, the HANA foundation view doesn’t have RBUKRS (company code), the BW virtual provider doesn’t contain company code, subsequently the BW composite provider does not contain this dimension. Now, the question is why the Flexible Upload still makes it mandatory to have the company code value in flat file.
In parallel, routed this question to SAP as well. Got the feedback that this scenario requires maintaining both company and company code. No need of all accounting configurations, only the basic configurations are required and the system will allow to perform this scenario.
Even without looking at details it seems incorrect for me. Setting up company code is not a "basic" configuration and should be taken very serious for audit purposes. If you're using RCOMP the write back logic will save the RBUKRS (if there is one in the system). If your flexible upload is requiring RBUKRS perhaps you should look at your flexible upload settings.
Thanks Lucas. However, if we download the Flex template from RTCFU, both RCOMP and RBUKRS are mandatory fields. Its highly unfortunate that we need to provide both in the Flex Upload file, even SAP has disregarded that field from all BW infoproviders. Not sure, which flexible upload settings you are referring to.
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 7 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.