WRITTEN BY: supportmymoto.com STAFF
Though all the data for organising RTC is obtainable within the assist documentation it does typically assist to see a step-by-step instance of how it’s accomplished particularly if it’s the first time you’re organising an RTC answer or maybe you’re investigating using RTC and this instance will reply a few of your typical consolidation enterprise requirement questions.
Notice that there isn’t a answer structure on this information. It’s the fundamental minimal steps required to activate BPC Optimized for S/4 HANA 1709 and it was accomplished on a sandbox system. Your mannequin designs might differ considerably from this instance primarily based on your small business necessities.
The purpose sounds moderately easy…we need to activate and validate a BPC Consolidation Mannequin primarily based on S/4 grasp knowledge and S/4 transaction knowledge and we need to handshake the BPC Mannequin with the S/4 RTC Consolidation Mannequin. Inexperienced VALIDATION ticks on either side signifies success!!
The S/4HANA set up is full in addition to the post-installation steps. You’ve activated the embedded BW and you’ve got created a clean BPC Embedded Mannequin Surroundings from the BPC internet shopper.
A very powerful start line is to search out the SAP Assist information, and particularly the precise chapter within the assist information that pertains to the setup procedures.
To go on to the content material go…
The great distance round is as follows:
With respect to RTC there are two consolidation mannequin setups. One on the S/4HANA aspect and one on the BPC aspect. The 2 fashions have two completely different Mannequin ID’s and are setup in two completely different environments. The S/4HANA RTC mannequin is setup within the SAP GUI in S/4 beneath the ACCOUNTING menu choice and the BPC Mannequin is setup utilizing the BPC Net Admin Consumer and relies on the embedded BW and BW modelling instruments in Eclipse.
We begin by organising the RTC mannequin which varieties the premise for all of the objects and transaction knowledge we are going to use to create the BPC Mannequin after which as soon as the BPC Mannequin is full we return to the RTC mannequin and supply it with the BPC Mannequin ID and do the ultimate activation. On this method we handshake the 2 fashions collectively.
As a way to setup our BPC mannequin we want a minimum of 3 info-providers for CONSOLIDATION, OWNERSHIP and RATES with very particular dimensions comparable to Group, Account, Audit ID and so forth and every of those require particular attributes which aren’t essentially created inside the usual S/4HANA dimensions/fields which signifies that they need to first be prolonged earlier than they can be utilized for BPC consolidations.
There’s a seemingly catch-22 setup for RTC as a result of we’re unable to create the BPC Consolidation Mannequin with out the required dimensions from S/4HANA and we will’t full the S/4HANA mannequin beneath transaction code RTCMD with out realizing what the BPC Mannequin ID is.
Step 1 – Execute S/4HANA Monetary Accounting steps
We kick off the method by organising the basic constructing blocks of the accounting system because it pertains to consolidations.
- In my mannequin I assume the identical fiscal yr variant because the native fiscal yr variant
- In my mannequin I assume the identical fiscal yr calendar because the native fiscal yr calendar
- In my mannequin I assume the identical group chart of accounts because the native chart of accounts
- Prolong the S/4 attributes for GL Account, Transaction Kind (Stream), Class and Entity.
Outline the BPC CATEGORY from inside RTC Customising. What you’ll be able to see occurring right here is that since S/4 has a really completely different knowledge class idea utilizing variations, worth sorts, GL ledgers and so forth it has to create a mapping between the quite simple single BPC CATEGORY dimension idea and the complicated S/4 knowledge class idea. So further tables are added to S/4 to retailer the BPC design with the respective BPC CATEGORY ATTRIBUTES which can be linked/mapped within the RTC Consolidation Mannequin later and S/4 HANA Views will present this knowledge to BPC by way of digital InfoProviders. This method is utilized to the GL Account, Transaction Kind and Entity as properly.
Preserve Class attributes (RTCBCT)
Step 2 – Preserve the Entity Dimension
Preserve the Entity dimension which varieties the premise of the organisational construction used within the consolidation course of. In S/4 the organisational construction generally is a mixture of a number of fields whereas in BPC it’s a single dimension. An Entity Desk is created in S/4 to carry these two worlds collectively. Firstly an ENTITY DEFINITION describes the S/4 fields that are mixed to create the Entity dimension after which an S/4 program can mechanically populate the usual Entity Definitions. For customized Entity Definitions the desk have to be populated by a customized ABAP program.
Step 3 – Create the consolidation ledger
3.1 Create a consolidation ledger (RTCLM)
There’s a default CL ledger which I’ll settle for for my mannequin however you’ll be able to create as many as you need.
3.2 Create a consolidation variant (RTCVAR) to manage the best way knowledge is launched to the ledger
Step 4 – Create the RTC Consolidation Mannequin
The RTC Consolidation Mannequin is created in S/4 beneath the ACCOUNTING menu choice for REAL-TIME CONSOLIDATION, MODELING, MAINTAIN MODEL. By capturing an ID and urgent the CREATE icon the mannequin is created.
4.1 RTCMD – Enter a 6 digit alpha-numeric mannequin key, choose the CREATE icon, choose the “Combine with BPC” checkbox and choose the default movement kind.
4.2 On the primary tab seize a mannequin description and default settings as per the consumer information
4.3 Generate the consolidation views for the mannequin. These views present the grasp knowledge and transaction knowledge to BW to be used inside the BPC Consolidation Mannequin or for reporting functions. You’ll discover all through the naming conventions inside BW that “_VXX” sometimes means a digital supplier studying knowledge from S/4HANA Views whereas “_RXX” sometimes means a real-time InfoProvider persevered inside BW. You’ll additionally discover that the RTC Mannequin ID that you simply present, in my case RTC001, is used inside the generated view names.
Step 5 – Set up the BPC BW BI Content material if not already accomplished
Setup the BPC Mannequin utilizing the BPC Net Administrator
Up to now we’ve labored by way of the configuration information sequentially on the S/4 aspect up till the “MODEL SETUP” part. Now we’re going to bounce to the chapter entitled “INTEGRATION WITH SAP BPC” to finish the BW and BPC aspect after which return to S/4 to offer the ultimate BPC mannequin hyperlink to S/4 to finish the handshake.
Create BW info-objects which can type the traits and dimensions of the three principal consolidation info-providers i.e. CONSOLIDATION, OWNERSHIP, RATE cubes.
5.1 One downside you would possibly come up towards is that the usual enterprise content material for RTC has not been activated but so while you look RSA1, MODELING, INFO-OBJECTS, REAL-TIME CONSOLIDATION you discover no content material.
5.2 So activate this content material from RSA1, BI CONTENT, INFO-OBJECTS BY INFOAREAS, FINANCIAL MANAGEMENT & CONTROLLING, REAL-TIME CONSOLIDATION. Activate your complete Attribute and Key Determine catalogues.
5.3 Refresh your complete tree and it’s best to now see the RTC BW content material. A few of these objects are primarily based on S/4 HANA views and a few are BW objects however they supply all of the objects required for the consolidation cubes.
Step 6 – Create the three supply BW InfoProviders
Create a VirtualProvider for the CONSOLIDATION dice.
The minimal variety of InfoObjects required are these we want for the BPC Consolidation Mannequin’s required dimension sorts and these are all obtainable from the enterprise content material that we put in into /ERP/RTC. You’ll discover that we require the ENTITY dimension and it’s companion, normally dimension PENTITY, in addition to Inter-Firm and it’s companion for US Eliminations.
This screen-shot has jumped forward and been captured after the assignments so we will get hold of an inventory of the minimal variety of dimensions required for the CONSOLIDATION mannequin.
6. 1 Don’t create your content material beneath /CPMB/BPC which is reserved for the BPC normal mannequin. I created a brand new InfoArea for myself named BPC_C with description BPC RTC.
6. 2 Seize a ID and Description for the InfoCube (BPC_C1, BPC Consolidation in my case). You’ll discover it’s already flagged as a VIRTUAL PROVIDER. Choose the radio button for BASED ON A SAP HANA MODEL and choose the DETAILS button to seize the main points of your RTC mannequin. The Package deal identify and HANA Data Mannequin come immediately from the generated views created in step 7.3. We use the “<…>_BPCUNION” calculation view for the BW VirtualProvider. When you’ve captured the related entry fields choose the CREATE icon and create the supplier.
6.3 The subsequent step is to create the VirtualProvider that we require for the Consolidation Mannequin.
Keep in mind that we’re following the assistance information sequentially from high to backside and we’re on the part known as CREATING BW INFOPROVIDERS and particularly the primary sub-section known as CREAT A VIRTUAL PROVIDER. We get hold of the HANA Area Names from this part.
Proper-Click on the TIME dimension and choose INFO-OBJECT DIRECT INPUT.
Seize the InfoObjects 0FISCPER and 0FISCVARNT and choose enter. Repeat this for the Dimensions and Key Figures.
6.4 As soon as all of the InfoObjects are added, choose the ASSIGN SAP HANA VIEW FIELDS and match the HANA area identify to the InfoObject.
I chosen all of the fields after which tried to match them however discovered that the choice choices beneath every area didn’t all the time include the matching InfoObject so I accepted the fields that did match after which manually matched the person InfoObjects by right-clicking on the InfoObjects that weren’t but matched and choosing InfoProvider Particular Properties after which choosing the HANA Mannequin Attribute.
Choose the InfoObjects individually to pick the HANA Fields that weren’t capable of be matched within the mass choice.
In the event you attempt to activate the dice with out all of the HANA Mannequin matchings you’ll obtain an error.
Repeat the person InfoObject mapping till all of the errors are cleared after which activate the dice.
In case your activation was profitable it’s best to now have an energetic VirtualProvider and when you right-click on it, or on the MANAGE choice, you’ll be able to choose DISPLAY DATA from the menu choice and show any knowledge there may be within the S/4 ACDOCA desk.
Choose the FLD SELECTION FOR OUTPUT button
Choose all traits, execute and execute once more to run the number of the primary 200 data.
If there are any data in S/4 they are going to seem in your knowledge show.
6.5 Now we have to setup the OWNERSHIP and RATES cubes for the mannequin. These are thought-about supporting cubes and we are going to create real-time bodily cubes in BW for them utilizing the S/4 grasp knowledge InfoObjects.
In your InfoArea with RSA1 create an InfoCube.
Notice: Earlier than including the InfoObjects mark the dice as a REAL-TIME InfoCube in order that the write-back skill is added to the dice.
The OWNERSHIP dice InfoObjects.
The RATE dice InfoObjects.
6.6 The results of the work up till now’s to have the three obligatory BW InfoProviders created and activated.
Step 7 – Create a composite supplier for the CONSOLIDATION InfoProvider
The assistance documentation signifies that making a composite supplier is elective and it is possible for you to to activate your BPC Mannequin with out it however you’ll NOT be capable of activate your S/4 Mannequin until the CONSOLIDATION VirtualProvider is in a composite supplier. So this isn’t elective, it’s obligatory in 1709 to create a composite supplier on your CONSOLIDATION dice.
You possibly can create the composite supplier in Eclipse.
I used a UNION as I’ve no different modelling restrictions and the Digital InfoProvider would be the solely content material within the composite supplier.
Add all of the traits and key figures to the goal and activate the composite supplier.
Step 8 – Create the AGGREGATION LEVELS
Subsequent we have to create AGGREGATION LEVELS for every supplier. Even when the AGGREGATION LEVEL is a 1-1 mapping of the supplier they’re the buildings which type the bottom for all consolidation features and supply the write-back functionality of BW planning features. We use the HANA Studio in Eclipse with the BW Modelling Perspective to create them.
Notice that right-clicking immediately on the cubes opens a context delicate menu which DOES NOT embrace creating the aggregation degree. You need to right-click on the INFOAREA.
After capturing the ID and Description and choosing the InfoCube – create – choose the OUTPUT tab and right-click within the VIEW FIELD field. Then choose ADD CHARACTERISTICS after which ADD KEY FIGURES and add all of the obtainable InfoObjects to the aggregation degree.
Activate every AGGREGATION LEVEL
When you’re accomplished it’s best to have one aggregation degree for every dice. Notice that the CONSOLIDATION base degree have to be created on the COMPOSITE supplier and never immediately on the VirtualProvider however OWNERSHIP and RATE aggregation ranges don’t require a composite supplier.
Step 9 – Create the BPC Consolidation Mannequin
Now we will flip our consideration to organising the BPC Mannequin. Within the BPC Admin Net Consumer beneath ADMINISTRATION goto MODELS and choose NEW. Enter an ID and DESCRIPTION and choose CONSOLIDATION because the mannequin kind and press CREATE.
You’ll now be capable of assign the DIMENSION TYPE to the DIMENSION and utilizing the GO TO MAPPING button you’ll be able to map the attributes to the attribute sorts.
After all of the mappings are full every InfoProvider could have a inexperienced PROCESSED tick subsequent to it. The construction on the left ought to mirror that truth that you simply used the composite supplier for the CONSOLIDATION InfoProvider in any other case the S/4 Consolidation Mannequin will fail to activate. In the event you used the VirtualProvider immediately it can nonetheless SAVE AND VALIDATE right here in BPC however the S/4 Mannequin will fail.
Despite the fact that the MAPPING STATUS would possibly now be full with a inexperienced tick on PROCESSED it’s nonetheless doable that on SAVE AND VALIDATION you should still discover you’ve got an error. So choose SEE DETAILS to verify any remaining points however sometimes you’ll need to open the ADVANCED SETTINGS and do the ultimate COMPOUND MEMBER choices for the compounded traits.
Now on SAVE AND VALIDATION the mannequin ought to point out a profitable activation.
Step 10 – Activate the RTC Consolidation Mannequin
The final step is to finish the ultimate handshake with S/4 by informing the S/4 Consolidation Mannequin of the BPC Mannequin ID.
Within the S/4 menu beneath ACCOUNTING, REAL-TIME CONSOLIDATION, MODELING, MAINTAIN MODEL or transaction code RTCMD,
Choose the BPC INTEGRATION tab and full the BPC CONSOL ENVIRONMENT and BPC CONSOL MODEL fields and press the activate icon. It is best to then get hold of the kind after MODEL (XXXX) ACTIVATED IN THIS VERSION standing message!