Highlights M1 Support Ahh, yesssss. Alert Moderator. Alerting is not available for unauthorized users. Assigned Tags. Similar Blog Posts. Related Questions. You must be Logged on to comment or reply to a post. Alexandre Giguere. Hi Marco, great right now my client don't want moving forward with changing all navigation bar to white and using big titles, how can prevent this not using the new v6 color palette? Like 0 Share.
Right click and copy the link to share this comment. Marco Eidinger Blog Post Author. Hi Alex, Happy New Year! All applications require at least the four main dimension-types: Entity, Account, Time, and Category. All consolidation postings such as eliminations, minority interest calculations etc are posted in this application Ownership Used to manage the organization structure and ownership percentages Rate Contains all currency exchange rates for the different rate types like average, sport rate etc Currency Translation can run on any type of reporting application.
Currency conversion applies to both Financial and Legal Consolidation Applications to which a corresponding Rate Application has been referenced and that the reporting application must contain a currency type R dimension. Rate application: A rate application is a supporting application for financial and consolidation reporting applications.
It is used to store exchange rates that support currency conversion in Consolidation applications. The time dimension must be identical to the dimension used by the applications using the rate application to store their foreign currency exchange rates and must have the same category member IDs. This application must include a currency dimension detailing the exchange rates by each input currency. The Currency conversion process makes use of a RATE application, where the appropriate exchange rates will be searched for each relevant currency.
This cube can be named as desired. But we will refer to it as the RATE application, in this document. Please refer to the How to guide on this topic that shows the entire process in detail.
Note: The master data dimension can be shared by application within an application set. For example if you have an entity C for which a special exchange rates needs to be applied, then it will be defined here and the special rates need to be applied. Currency dimension is utilized to store for each applicable local currency.
Time and Category dimensions can be shared by all the application involved in consolidation. As mentioned before Apshell comes only with Planning and Rate application, the ownership application needs to be created before we can create the Consolidation application. Please refer to the steps wizard of creation process.
The business rule process makes use of an Ownership type application when calculating the ultimate ownership or during the minority interest calculation. This application must be associated to a Consolidation type application. The ownership application will contain the values of each consolidation parameter.
In particular, such definitions may include: The list of companies being consolidated in each group Their consolidation method Their consolidation percentage Their ownership percentage how much they are owned by the group Their control percentage how much they are controlled by the group Ownership application can be named as desired, but we will refer to it as the Ownership application, in this document.
Select Ownership as Non-Reporting Type as shown below. Then click on Add a New Application. In order to pass the information, we have to set up several required members, which include, 1.
Method, defines consolidation method 2. Set the Application Set to the name of your Appset and the application to the name of the Ownership application in the top right corner of the Action Pane.
Here are the relevant application parameters and the recommended values that should be set through the Web Admin. Please refer to the Admin guide on how to set these values. The name of the Ownership application. This parameter is used with dynamic hierarchy statutory applications when defining fixed hierarchies.
The value must match the value in the ParentProperty property value of entities in the statutory application's supporting ownership application. Going forward we will use the ones created in the previous step.
Figure Naming the Consolidations application Figure selecting the right application type: Consolidations Figure 3: associating the desired Rate and Ownership application with the new consolidation application In step 3, select all the consolidation business rules need to be implemented.
Here is the list of Business Rule that is available for selection: Currency conversion: Conversion of local currency data in the desired reporting currencies. Calculations: T o calculate and store amounts which are required for purposes of account transformation. Intercompany bookings: Matching of inter-company transactions. US Eliminations: Specifically designed to address the posting of inter-company eliminations in simpler scenarios where a full legal consolidation application is not required.
Opening Balance: Initialization of beginning balances when a new fiscal cycle starts. Validation: Validation of input data. Intercompany Eliminations: Generation of all the consolidation entries for the desired groups of entities eliminations, adjustments, re-classifications, minority calculations, etc.
Consolidation business rules allow the automated processing of data to render a consolidated set of financial statements. This is commonly thought of as eliminations of investments in subsidiaries, adjustments of minority interest, reclassifications and any other postings depending on the nature of the consolidation methodologies required.
The enabling of this functionality is done through a combination of ABAP and business rule tables. Before the consolidation type application is created, from UI of BPC, the user will not be able to display the rules and the pre-delivered library tables content are stored in following ABAP database table.
Figure 4: De-select the dimensions box to allow you to specify the relevant dimensions for your consolidations application In this step, set dimensions to be included in the consolidation application and also set the secured dimension to control the security via BPC member access profiles.
Figure 5: Selecting the dimensions for your consolidations application Normally the Entity and Category dimension are set as secured dimension for member access control.
For Group dimension here, it stores both group currency and reporting currency and also consolidation groups. In other words the Entity details are either in local currency - LC - or in a reporting currency — say USD — or are consolidated into a given GROUP — say G1 - in which case specifying the group is enough to identify its currency. Any additional dimension is optional in the MAIN cube, as far as the currency translation is concerned.
For consolidation purposes however, some other requirements come into play, as described below: The application may have an INTCO dimension, but it is not required for the Consolidation procedure to work, unless some elimination rule makes an explicit reference to this dimension.
The application may have a FLOW dimension. This dimension is optional, but, if it exists, it can be used 1 By the currency translation procedure, to detail the changes in the balance sheet generated by fluctuations in the exchange rates 2 By the consolidation procedure to detail the eliminations applied to the movements of the balance sheet accounts.
If it exists, however, the currency translation will be able to recognize which members of such dimension should be translated and which ones should be just copied as they are into the destination currency.
On the other hand, this dimension is required for the consolidation procedure to work. Additional user defined dimensions can be added to the MAIN cube like product, market, division, etc. The Consolidation Engine will be able to recognize their existence and take them into account in the process, and even apply some custom behavior to their members.
Here is the Legal Application created with all the dimensions shown. Figure The dimensions of the consolidation application we just created. Set the Application Parameters Application parameters provide a nice collection point for properties that affect how applications are used.
The Legal application is an excellent example because it requires quite a few settings. In this case, some of the more important parameters are used to determine how organizational information from the ownership application is used.
You can define only one hierarchy for each application within an application set. If this field is blank, work status tracking is disabled. You can use this information to monitor system performance. The default is Group. If Group, then there is no need to modify the account dimension. Name of the linked Ownership application. The 3rd party member in the Intercompany dimension to which all ownership calculations are posted. Member id of the ownership account that specifies the Position of a consolidation entity within the group.
These will appear in the dynamic hierarchy editor. The property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor. The Group property that will contain the legal rollup members. The value must match the value in the ParentProperty property value of entities in the statutory application's supporting Ownership application.
The consolidation logic requires the Ownership application to be listed here as well. This parameter controls whether data is input in year-to-date format. Valid options are 1, which means YTD format; or 0, which means periodic format. This parameter plays important role since it controls how the data is stored in the cube. Most source systems store balances on a periodic basis whether it is daily, weekly, monthly, fiscal periods, etc.
With this method, periodic data must be accumulated for year-to-date reporting except for Balance Sheet accounts, which gets the value from the last period. However, in some business cases, calculations should occur on a year-to-date basis.
When data is entered into YTD, its periodic values used for reporting purposes, are calculated as the difference between the current period and the last period again, Balance Sheet accounts would simply take the value from the last period.
Business Rules Interface SAP Business Planning and Consolidation delivers pre-defined functions designed to calculate and post amounts required supporting common accounting activities such as: Currency translation Matching and elimination of inter-unit balances. The complete list of functions will be discussed in the next section. Here is an example of the currency conversion business rule table shown below: To run these programs, you must use of the designed Data Manager Packages through SAP BI Process Chains to invoke the Programs directly from the K2 scripts logic file and pass the appropriate parameters to the data package.
LGF US Elimination For each process, the pre-defined Data Manager Packages with their associated logic scripts and rule tables are executed, performing the consolidation task according to the business rule customization. Any specific business requirement needs to be configured in corresponding Business Rule Tables. We will be showing how to take a peek inside the IPC. To debug the IPC, a couple of prerequisites are required as described in the pricing userexit manual in note In order to debug the code running on the VMC using your Eclipse environment, the following steps can be followed:.
Receive our weekly blog by email? Subscribe here:. Benefits of good design in business apps. An organized ? A screen Containing help information is displayed to the right. You can use edit change settings or display see settings mode in XCM. You use the button in the top right hand corner of the screen to change between modes. When you switch to edit mode a DB lock is set meaning that only this user can edit the settings at one time.
Once you have created the application configuration, you need to configure it by changing the parameter values. This process gives you an overview of all the settings that you need to make in Extended Configuration Management XCM for the product configuration interface.
0コメント