SAP BusinessObjects Planning and Consolidation, Version for SAP and Objects in BPC Administration BPC Figure BW and SAP. BPC SAP Business Planning and. Consolidation, Version for SAP. NetWeaver: Standard. Administration and Planning. Configuration.. COURSE OUTLINE. bpc - Download as PDF File .pdf) or read online. SAP BPC handbook version.
|Language:||English, Spanish, Hindi|
|Distribution:||Free* [*Register to download]|
Download Sap Bpc Pdf - ruthenpress.info sap bpc pdf streamlined planning and a faster. more compliant ruthenpress.info bpc - planning services yash. Download Sap Bpc free pdf, Download Sap Bpc Pdf, Read Online Sap pdf, Free Sap Bpc Ebook Download, Free Sap Bpc Download. Download Sap Bpc free pdf, Download Sap Bpc Pdf, Read Online Sap sap bpc pdf free download here sridhar srinivasan and kumar srinivasan.
Drill through Function: Drill Through function allows users to access source data from a report. Source data includes content that can be accessed from a URL. Example : Your company is doing a planning report based on regional data. During reporting, you need to have more information above the selected region. Document Types and subtypes: They categorize document view posting.
This is useful if you want to filter them to see only certain types. You can add document type and subtype to aid sorting and filtering. Document subtypes help you further categorize documents when you post them in the Content library. Properties define the behavior of members within the dimension.
By assigning properties to dimension, you can implement powerful features in your reporting, member lookup, formulas, Data Manager selection and so on. The following properties are generated for all dimension types, but are not displayed in the list of properties for a dimension. Description: Displays the name of the dimension CALC: Indicaes whether the member is calculated by means of formula or at parent level. Referential Integrity: This option validates the properties of the dimension with the dimension member IDs of a different dimension.
When you process the dimension, the system checks the values of Refrential integrity property. Validation does not complete if they do not pass validation. In Drivers and rates models support reporting models by holding data such as currency exchange rates and ownership percentages. You cannot define business rules to these models. Use of source data : You can use Use of Source of data for ExternalApplications checkbox to make data within the model available for evaluation through Process Control.
This flag would allow external applications to use this model as the source of data. This would generate a virtual provider on top of the cub model which enables the ODBO client to retrieve the data of the model There are 2 different types of optimization available: Light optimization: A.
Closes the open request. If the data model can be improved , Full will do so, and this could take a long time to run Denial of data access can be set only at user level These are words and characters that you enter in the system exactly as they appear in the documentation. Pointed brackets indicate that you replace these words and characters with appropriate entries. Icon Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures Indicates that the item is displayed in the instructor's presentation.
Contents Course Overview Navigating in the Interface for Excel Working with Logic Business Process Flows Administration optional Contents BPC Audits Data Management — Add-on Information Drill Through to ERP Concurrency Looking — Add on Information.. Work Status — Add on Information Course Overview Target Audience This course is intended for the following audiences: In addition, you will learn how to create application sets, applications and how to configure dimensions.
You will also get some information about the security concept. Unit Objectives After completing this unit, you will be able to: Unit 1: Application Set Management Dimension Management Creating Applications BPC Lesson: Lesson Objectives After completing this lesson, you will be able to: Figure 1: Publishing and Distribution to Aid Communication Figure 5: Automated Audit Trail Figure 9: Figure Business Process Flows guide and coordinate end users step by step toward a common performance management goal such as creating a forecast or reporting consolidated financial results.
Integration with BW Accelerator provides faster query read performance so you have quicker access to information within the planning application and can react faster to changing business conditions. This is critical particularly in todays volatile environment. Along with bit support, the result is faster performance even with more users accessing the system and a larger payload like a Porsche Cayenne Turbo. All structures they configure are automatically available in the related BW backend.
SAP BusinessObjects Planning and Consolidation is designed to be owned and maintained by the business finance user, empowering finance departments and reducing your reliance on IT. The application ships with a variety of prebuilt report templates and there is no data modeling required; simply add dimensions and dimension members on the fly so you dont have to wait for IT to modify the application.
Lower Maintenance Because SAP BusinessObjects Planning and Consolidation is designed to be owned and maintained by the business user, you IT will not be burdened with supporting yet another application. On the flip side for the end user , business users are empowered to run the application with minimal intervention from IT required.
Seamless integration with financial data from SAP ERP means you dont have to wait for IT to integrate 3rd party applications before you start planning, budgeting, forecasting and consolidation processes. There is no technical limit for the maximum number of Dimensions characteristics in an Application InfoCube ; however, best practices for the number of characteristics in a cube within SAP NetWeaver BW typically apply in this scenario. You are always working within an application set which is a data base.
The whole modelling of planning and consolidation scenarios is based on properties. Some properties are custom-created, others are system properties. Especially if you want to consolidate with BO PC you should know which properties are necessary and for what they are needed in the modelling of legal or management consolidation.
As you can see BO PC only supports one type of hierarchy that is a hierarchy based on one dimension. As a consequence of this hierarchy type in BO PC some dimension members are leaf members while others are node members.
N can be an integer number and allows you to have several hierarchies in parallel. As you can see from the upper graphic you can alwas plan on leaves but never on a node member. This is the case since node members in BO PC sum up the transaction data for the leaves beneath the relevant node. This summing up or aggregation is always automatically executed by the system when the end user saves data to the server. Business Planning and Consolidation — Some Modeling Aspects This slide shows you the first of three work arounds and it works with an Excel line which represents the node member.
Both EV functions need the information in which combination of dimension members the relevant amount is written. Here we work with a leaf member Budget per node member but since the new leaf member and the old leaf members are all beneath one common node member we must distinguish between the budget new leaf member and the distribution of values sum of old leaf members. When sending data to the server all members beneath a node are summed up so we would get double the budget after sending data.
To avoid this we introduce to versions, one for the new budget member and one for the distribution members and so when sending data a double summing up of budget and distribution isn't done. You can also use the 'top down allocation' solution as a way to disaggregate your data based on history. Below you can see the course exercise scenario. Terminology Lesson: Terminology Figure Properties In this example, the account Dimension has a member ExtSales with the property values: ApShell measures are: The accounts above are cumulative in nature since you can add up operating income over time.
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.
Every dimension in the cube has a dimension member posted in every record and each one is a base level member. Base level members don't have children. One type of InfoProvider is an InfoCube or just cube for short. Terminology Lesson Summary You should now be able to: Business Example You are currently using Integrated Planning and you need to know what the benefits are to migrate.
The upper slide is a high level analysis. Going Forward As you can see both planning tools will be available in the future. This is the workbench for BPC Administrators. Business Example Figure Application Set Management Figure The Admin Console — First Orientation Use the tree on the left to select which components to display or maintain.
The middle area displays the settings and metadata for the component you have selected in the tree. The action pane is on the right. Application Set Management Only a user with System Administrator rights can create a new application set. NET client will poll this background job until it is finished.
When you create a new AppSet, these steps get executed: Any error during a copy of an AppSet will result in a rollback to clear all created objects. A custom message can be created that will inform users that the AppSet is unavailable. It is recommended to include the date and time in the message which will indicate to the users when they can log back on. Application Set Management This slide contains information about the implication of an application set being offline for other modules.
Set Template Version Updating the template version number will force an update of the template files to the clients. The version number can be changed in the Admin Console as well as in the Application Set Parameters using the Web Administration interface.
The system will handle updating the clients with dimension changes automatically. This slides describes how to delete an application set. The delete is permanent and cannot be reversed. It logs all RFCs from the.
When viewing the User Activity report, you can refresh the report with the most recent activity or delete the old activity.
Application Sets: Dimension Management Lesson Overview Understand the possibilities of how to load master data. This opens the available Action Pane tasks. Dimension Management Figure They are added at the Application Set level in the dimension library folder. These then become shared dimensions that are available for use in any application in the application set.
Dimensions within one Application Set cannot be used within another Application Set. Some dimension types are required dimensions and must exist in all the applications within an application set. The dimension type determines the default properties to be included in the dimension. Add additional properties as needed. Dimension field names may ONLY be max of 20 characters. Each dimension built will walk through a series of steps via the Action Pane inside the Admin Console.
Remember, clicking the Left hand side pane will quit the activity or step in the process. All properties will get created as new InfoObjects. Internally they are stored as type string and linked to the star schema through the dimension member ID which is length This means that they will not be available for Advanced logic or rule based calculations. But we can store many more properties and longer lengths for storing important information, such as a Full Customer Address without using multiple properties.
To reduce the size, you will have to create a new property copy the values over from the old property, and delete the old property. Selecting a dimension will display a view that highlights the properties of the dimension, their system name and size of the property. Use of Dimension Properties Defining the right properties in a dimension support various functions from the users interface and make reporting much easier.
In addition, properties are often critical component used to evaluate expressions in advanced script logic and business rules. Remember, the value you place in a members property may be pulled to any applications BPC for Excel page, as is. Modify Dimension Modifying a specific dimension is limited to the specifics of the dimension, such as the description and reference dimension. Copy Dimension Use the copy process when you have an existing dimension type and design, including properties, that you want to leverage for a new dimension.
Concepts and Objects in BPC Administration BPC This is useful when building similar dimensions, such as Account or Entity, that already have several properties and members, but you need separate dimensions for different applications. Delete Dimension Only delete a dimension once you have removed it from any active application. Once it is deleted, all associated information is removed from the database. This file has the same name as the dimension.
You must add a new member and copy the data.
If you plan to delete a member, you will need to verify that all data related to that member is deleted, including across applications if the dimension is shared. Once you do delete the member, you may find that you will need to re-process the whole application to get everything back to order.
The sheets currently store all properties and members alphabetically. This has been noted as a possible area for improvement. Do not be surprised that what you saved, once re-opened has a whole new look to it. The data is correct, just re-organized. Modeling Hierarchies It is natural to have hierarchies for dimensions such as entity and time where the need for rollups is common.
Hierarchies also allow the use of multiple views from one dimension. For example the entity such as Store dimension can be used to view data by company code, plant, or region. Multiple Hierarchies A dimension can have more than one hierarchy. A parent in SAP Business Planning and Consolidation must have the same children if it is reused across multiple hierarchies. The option to process a dimension can be found in the Action Pane. Processing Dimensions Figure This means that when you process a dimension, the values to save back to the master data of the SAP NetWeaver B InfoObject are taken from the Excel sheet you currently have open on your client machine.
If you do not select this, it assumes you have already chosen to save the sheet to the server before processing, and therefore the BW master data is updated from the sheet on the server.
If you have manually built aggregates on your SAP Business Planning and Consolidation cubes, then this performance benefit of processing would be lost. The next slide indicates what may be changed and any changes outside of the ones herein will not be supported. If you use BW technique to load master data you will have to process the relevant dimension afterwards. If you use BW to load master data you will need to run the hierarchy attribute change run in BW manually as well as make sure the caching mechanisms in SAP Business Planning and Consolidation were updated correctly.
Creating Applications Lesson: Creating Applications Lesson Overview In this lesson we will discuss how to model and create application. Business Example You need to set BPC up to do expense planning and so you need the applications to store the transaction data. If you select the Application level on the left, the Action Pane will display tasks relevant for Applications: Create; Copy; Modify and Delete Applications.
Create vs. Concepts and Objects in BPC Administration BPC The major difference then is that Copy will actually copy the data, and you can not change the dimension assignments when copying, while Create allows you to change dimension assignments, but not copy data. When choosing Create, the documents stored in the file system from the Source application will be copied.
Technically the following operations are realized as Process Chains and will technically be executed in a Background Mode: You can use job log in transaction code SM37 to view the detailed log information and progress of these jobs. During execution the Admin Client will be locked and will constantly poll for the status of this background job every 20 seconds. Only when the job has finished, control will return to the client for these jobs. Creating a New Application By checking off the currency conversion rules, the system will create business rule tables to perform that function.
Planning applications must reference a rate application. One rate application can be referenced by multiple other applications.
Creating Applications Figure This slide contains a list of options available when an application is being created. Each application should have at least four dimensions; Category, Entity and Time, Account. To delete a dimension from an application, it is necessary to first delete all the dependencies of that dimension from the application. Creating Applications You can report on non-reporting application data, but you cannot assign work status codes to the data. In addition, you cannot define business rules to these application types.
Reporting applications require the four dimension-types: Entity, Account, Time, and Category but non-reporting types do not. Required Dimensions per Application Type This slide contains a list of required dimensions for each application type. It is important to note that every application can not have duplicate dimension types for these required dimensions.
There is no rule of thumb for how often to run optimizations, but as data volumes grow over time, it is recommended to run optimize periodically. There are two different types of optimization available: If the data model can be improved, Full Optimize will do so, and this could take a long time to run for cubes with large data volumes.
Both optimiziation options require that the application is offline. Be careful running a Full Optimize as significant system resources are used in the process. Specifically, it will check: If the cube structure can be optimized, then it will: These changes will be lost if the underlying technical InfoProvider is changed. What you can't do in RSA1 Partitioning is not available because we do not use the standard SAP time dimension, and that is all that NetWeaver supports for partitioning.
We will consider additional enhancements here in the future. However, most of these parameters are available when the cube contains no data.
Therefore, when you create a new cubes you could alter them, but when a shadow cube is created, these type of changes would be lost. Therefore, it is not really possible to configure these items. They are both constants in the data flow. The underlying Realtime InfoProvider is exchanged if you do a full optimize.
The new cube would then have to be added manually to the MultiProvider after the optimization. YTD vs. Its possible to use a preconfigured Data Management Package to convert from one time related view to another.