BPC Logics allows us to perform calculations on BPC data. BPC comes with three different types of logic (1) Worksheet logic, (2) Dimension logic and (3)Advanced (Script) logic. Normally we use one or more, or all of them is our BPC environment. Usage of these scripts depends on many factors, for example (1) performance issue, (2) complexity, (3) user preferences, etc. each of these script has its own its own advantages and disadvantages. Among the logics, script logic is much loved and widely used logic. Refer the embedded slide for more information. Hope you will enjoy it. Thanks, Surya Padhi
The purpose of this document is to demonstrate the implementation of script logic in reallife
projects, which includes designing, creating, executing and debugging Script Logic in a
SAP BPC 10. /7.5 NW environment. This document educates the user only the essential
topics that are required to solve practical problems and it expose the user to the Script
Logic commands that are widely used in any business process automations such as
Budget Allocation
Revenue Distributions
Cost Calculations
Revenue and Cost Implementation Impact of Financial Statements
Scenario (“What If”) Analysis
Adjustment to plan to formalizing forecasting
It is assumed that the user has basic knowledge/understanding about SAP BPC NW
10.0/7.5 version.
• Jothi Periasamy
• SAP GL ,
• SAP ECC ,
• BPC,
• BI ,
• Conversion file ,
• Transformation file ,
• Data File
• SAP BPC Data Manager
• SAP BPC Data Load
Technical Overview of CDS View - SAP HANA Part IIAshish Saxena
It is very important that a developer understands that technically, CDS is an enhancement of SQL which provides a Data Definition Language (DDL) for defining semantically rich database tables/views (CDS entities) and user-defined types in the database. Unlike the SAP HANA CDS, ABAP CDS are independent of the database system. The entities of the models defined in ABAP CDS provide enhanced access functions compared with existing database tables and views defined in ABAP Dictionary, making it possible to optimize Open SQL-based applications. And it is because of these unparalleled advantages that ABAP CDS is the most preferred form of methodology when it comes to Code to Data paradigm.
Step by step guide to formatting the SAP BPC EPM SheetCloneskills
EPM Formatting Sheet can be used to format your Reports and Input Forms. There are
various options for formatting.
You can do simple formatting, lock the cells that are not input ready, use the format by
property using multiple criteria, or use a new cell-based formula delivered with the EPM
add-in to override the data range formatting.
Dynamic formatting is defined in a dedicated sheet. Formats can be applied to levels of a
hierarchy, types of members, odd/even rows, or columns and page axis dimensions. Since
the EPM Formatting Sheet is an excel sheet, it can be copied and changed to be applied to
other reports, worksheets.
There are various sections on the EPM Formatting Sheet
• Hierarchy Level Formatting
• Dimension Member/Property Formatting
• Row and Column Banding
• Page Axis Formatting
The purpose of this document is to demonstrate the implementation of script logic in reallife
projects, which includes designing, creating, executing and debugging Script Logic in a
SAP BPC 10. /7.5 NW environment. This document educates the user only the essential
topics that are required to solve practical problems and it expose the user to the Script
Logic commands that are widely used in any business process automations such as
Budget Allocation
Revenue Distributions
Cost Calculations
Revenue and Cost Implementation Impact of Financial Statements
Scenario (“What If”) Analysis
Adjustment to plan to formalizing forecasting
It is assumed that the user has basic knowledge/understanding about SAP BPC NW
10.0/7.5 version.
• Jothi Periasamy
• SAP GL ,
• SAP ECC ,
• BPC,
• BI ,
• Conversion file ,
• Transformation file ,
• Data File
• SAP BPC Data Manager
• SAP BPC Data Load
Technical Overview of CDS View - SAP HANA Part IIAshish Saxena
It is very important that a developer understands that technically, CDS is an enhancement of SQL which provides a Data Definition Language (DDL) for defining semantically rich database tables/views (CDS entities) and user-defined types in the database. Unlike the SAP HANA CDS, ABAP CDS are independent of the database system. The entities of the models defined in ABAP CDS provide enhanced access functions compared with existing database tables and views defined in ABAP Dictionary, making it possible to optimize Open SQL-based applications. And it is because of these unparalleled advantages that ABAP CDS is the most preferred form of methodology when it comes to Code to Data paradigm.
Step by step guide to formatting the SAP BPC EPM SheetCloneskills
EPM Formatting Sheet can be used to format your Reports and Input Forms. There are
various options for formatting.
You can do simple formatting, lock the cells that are not input ready, use the format by
property using multiple criteria, or use a new cell-based formula delivered with the EPM
add-in to override the data range formatting.
Dynamic formatting is defined in a dedicated sheet. Formats can be applied to levels of a
hierarchy, types of members, odd/even rows, or columns and page axis dimensions. Since
the EPM Formatting Sheet is an excel sheet, it can be copied and changed to be applied to
other reports, worksheets.
There are various sections on the EPM Formatting Sheet
• Hierarchy Level Formatting
• Dimension Member/Property Formatting
• Row and Column Banding
• Page Axis Formatting
Sap bpc nw 10.0 consolidations ( ic elimination) implementation guide v1 pJothi Periasamy
During period close or month end close or quarterly close the accounting concepts, the revenue generated within the group by exchanging the goods and services with affiliated companies needs to be eliminated.
All Inter-Company activities and balances should be eliminated within in a group when the group reports the financial results of entities within the group. In any given group, the entities and the partner doing business with should only be present. For this unique requirement, the IC Elimination process follows the concept called “posting at first common parent”.
Jothi Periasamy
GIve differences in 4 unique and basic terms of UML, classification , definitions ,frameworks. understandable through diagrams. Some similarities / Trade-off are also for more detailed knowledge.
Beginner's Guide: Programming with ABAP on HANAAshish Saxena
The focus of this blog is to present an overview of the new programming techniques in ABAP after the introduction of HANA database. The focus will be towards providing a guideline on why and how an ABAP developer should start transitioning its code to use the new coding technique’s.
SAP BPC NW 10.0 on HANA - Consolidation Business Rules- Implementation GuideJothi Periasamy
1. Executive Summary:
The purpose of this article is to provide enough functional and technical details to implement SAP BPC NW 10.0 business rules on a consolidation model. Users will learn the business rules that are required to implement financial close process solution. In this article we are explaining the mandatory required steps to implement business rules in detail.
This document explains the [a] objective of each business rule, [b] educates you to understand the table fields/columns for each business rule, [a] explains the business purpose of each column in the business table and then [d] explains the value stored in each column along with sample values. Ultimately we are showing you to implement the business rules step by step.
In this article, we cover the following business rules on a SAP BPC NW 10.0 platform for a consolidation implementation:
Methods
Methods Based Multipliers
Eliminations and Adjustments
Carry Forward
Account Based Calculations
Intercompany Bookings
Currency Translation
Equity Pickup
US Eliminations
In SAP BPC 10.0 Configuration and User Guide we attempted to cover various aspect of BPC 10.0 net weaver version including definition, subject, configuration and use.
Sap bpc nw 10.0 consolidations ( ic elimination) implementation guide v1 pJothi Periasamy
During period close or month end close or quarterly close the accounting concepts, the revenue generated within the group by exchanging the goods and services with affiliated companies needs to be eliminated.
All Inter-Company activities and balances should be eliminated within in a group when the group reports the financial results of entities within the group. In any given group, the entities and the partner doing business with should only be present. For this unique requirement, the IC Elimination process follows the concept called “posting at first common parent”.
Jothi Periasamy
GIve differences in 4 unique and basic terms of UML, classification , definitions ,frameworks. understandable through diagrams. Some similarities / Trade-off are also for more detailed knowledge.
Beginner's Guide: Programming with ABAP on HANAAshish Saxena
The focus of this blog is to present an overview of the new programming techniques in ABAP after the introduction of HANA database. The focus will be towards providing a guideline on why and how an ABAP developer should start transitioning its code to use the new coding technique’s.
SAP BPC NW 10.0 on HANA - Consolidation Business Rules- Implementation GuideJothi Periasamy
1. Executive Summary:
The purpose of this article is to provide enough functional and technical details to implement SAP BPC NW 10.0 business rules on a consolidation model. Users will learn the business rules that are required to implement financial close process solution. In this article we are explaining the mandatory required steps to implement business rules in detail.
This document explains the [a] objective of each business rule, [b] educates you to understand the table fields/columns for each business rule, [a] explains the business purpose of each column in the business table and then [d] explains the value stored in each column along with sample values. Ultimately we are showing you to implement the business rules step by step.
In this article, we cover the following business rules on a SAP BPC NW 10.0 platform for a consolidation implementation:
Methods
Methods Based Multipliers
Eliminations and Adjustments
Carry Forward
Account Based Calculations
Intercompany Bookings
Currency Translation
Equity Pickup
US Eliminations
In SAP BPC 10.0 Configuration and User Guide we attempted to cover various aspect of BPC 10.0 net weaver version including definition, subject, configuration and use.
Administrators load data from various source GL systems in to a Model. Accounting team will review the data and should there be discrepancy in balancing accounts/amounts, the team will create Journal (s) to balance the amounts for reconciling. This is necessary since correcting the source system and reloading may take significant amount of down time. This process is typically done after month-end and quarter-ends.
Clone skills,inc. sap bpc on hana data modeling v9 11282013Jothi Periasamy
The purpose of this article is to provide adequate instruction to implement any complex SAP HANA data model. Users will learn various building blocks that are required to implement any SAP HANA data model.
SAP HANA data model is not just creating an attribute view, analytical view and calculation view, and also it is not a technical implementation, it is an “Art”. SAP HANA data model is the foundation for any SAP HANA enabled business transformation initiatives.
SAP HANA data model and data architecture should be driven from business process and the model should fully leverage SAP HANA’s in memory computing power and also the build in out of the box SAP HANA functionality such as stored procedures, functions, database triggers, hierarchies, calculated measures, restricted measures, calculated attributes, dynamic currency conversions, input parameters, and much more. Consider all of these key capabilities of SAP HANA while transforming business problems into a SAP HANA enabled solutions.
In this document we are explaining the objective of each data model building block, and also its implementation steps. Users should be able to follow this guide and implement any SAP HANA data model.
SAP HANA enabled EPM and BI solutions
SAP BPC integrated financial planning with the power of in-memory computing
Predictive analytics
Financial predictive
Healthcare predictive
Advanced analytics
Smart Grid
etc
1.1. SAP HANA Data Model Key Building Blocks
Attribute view
Analytical view
Calculation view through scripts
Stored procedure
Functions
Database triggers
Variables
Input parameters
Hierarchy
Decision tables
Dynamic currency conversion
Data Import
The presentation helps to introduce the key aspects of the Oracle Optimizer and how you find out what it's up to and how you can influence its decisions.
PHP UK 2020 Tutorial: MySQL Indexes, Histograms And other ways To Speed Up Yo...Dave Stokes
Slow query? Add an index or two! But things are suddenly even slower! Indexes are great tools to speed data lookup but have overhead issues. Histograms don’t have that overhead but may not be suited. And how you lock rows also effects performance. So what do you do to speed up queries smartly?
Workload Management with MicroStrategy Software and IBM DB2 9.5BiBoard.Org
This paper describes the best practices for configuring MicroStrategy software to use the workload management (WLM) features of IBM DB2 9.5 for Linux®, Unix®, and Windows. Source: ftp://ftp.software.ibm.com/software/data/sw-library/db2/papers/wlm_msi_db29.5.pdf
Mail & call us at:-
Call us at : 08263069601
Or
“ help.mbaassignments@gmail.com ”
To get fully solved assignments
Dear students, please send your semester & Specialization name here.
Dear students get fully solved assignments
Send your semester & Specialization name to our mail id :
help.mbaassignments@gmail.com
or
call us at : 08263069601
CONFIGURING GROUP REPORTING WITH S/4 HANA 1909.Surya Padhi
With S/4 HANA Finance 1809, SAP has introduced group reporting, a SAP’s consolidation solution. Group reporting’s innovations expose the new consolidation solution, which is a hybrid of SAP’s EC-CS, BCS and BPC functionalities. You’ve heard about Universal Journal, single source of truth, real-time processes, and UI improvements, in group reporting, you can leverage all these functionalities without additional acquisition of the software cost. SAP group reporting facilitates continuous accounting and consolidation in a single instance, thus reduces the financial closing manhours. With the tight integration of ACDOCA table and flexible upload functionalities help smooth transition of consolidation unit’s local data to consolidation data for financial consolidation. With the S/4 HANA 1909 release, SAP enhanced group reporting functionalities with new fiori tiles.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
De-mystifying Zero to One: Design Informed Techniques for Greenfield Innovati...
01 surya bpc_script_ppt
1. BPC 10.0 NW
Script Logics
Disclaimer: This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding
upon SAP to any particular course of business, product strategy, and/or development. SAP and author assume no responsibility for errors or
omissions in this document. This preview is provided without a warranty of any kind, either express or implied, including but not limited to the
implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP and author have no liability for damages of any kind
including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.
Author: Surya Padhi
Mail : SuryaPadhi@Gmail.Com.
SAP Certified Application Associate - Financial Accounting
SAP Certified Application Associate - SAP BusinessObjects Planning and Consolidation 10.0
2. Objectives
www.suryapadhi.com suryapadhi@gmail.com
In SAP BPC, we use script logics to copy, calculate and write data based in selection. On
several occasions I have seen, functional consultants find it difficult to understand. In this
presentation I will cover following topics relating to BPC 10.0 NW script logic for
simplification and easy understanding.
1) Definition;
2) Functionalities
3) Syntax
4) Testing of script logics.
3. Definition
www.suryapadhi.com suryapadhi@gmail.com
Script Logic – enables calculations on base-level cells that result in data stored within an
application. The results are aggregated up the dimensional hierarchy, without being re-
calculated at upper levels. SAP has provided two types of scrip logics syntax , these are (1)
SQL based syntax and (2) MDX based syntax . I will cover in detail above syntax in more
details in the next few slides.
4. Functionalities:
www.suryapadhi.com suryapadhi@gmail.com
The script logic;
1) Reads a specific data selection from the model.
2) Applies to it a set of user-defined formulas (stored in a logic file).
3) Derives the values.
4) Writes those values back to the application.
Results are written directly to the model as base data, and are aggregated up the
dimensional hierarchy as they are, without being recalculated at upper levels.
1) All dimension logic formulas are applied to these results.
2) This process allows you to perform calculations.
Script logic can be run in any of three ways:
1) Automatically after data is sent to the database from BPC for Excel using the Default.LGF
file.
2) After Journal data send using either Default. LGF, or if present, Journal. LGF files.
3) Through Data Manager as a batch processing event to call Script Logic formulas.
5. Functionalities:
www.suryapadhi.com suryapadhi@gmail.com
Advantages of BPC script logics
1) Model dependent calculation, not at a member level of the dimensions;
2) BPC scripts can be called from different places, for example default logic, data manager
package etc.
3) With the help BPC logics, we can perform different type of calculation with or without
calling business rules;
4) In SAP BPC script logics, we can choose desired dimensions with the help of dimension
properties.
Disadvantages of BPC script logics
1) BPC script can’t handle very complex calculation processing or bigger data volume. In
case of a complex calculation, ABAP-BADI comes into the picture. We can call ABAP-BADI
codes within the script logics.
6. Syntax
www.suryapadhi.com surya@suryapadhi.com
There are two Syntax options in SAP BPC Script Logic. These are:
1) SQL based syntax: SQL syntax gives better performance.
2) MDX based syntax. MDX syntax is used in record level specific calculations).
Multidimensional expressions abbreviated as MDX.
While choosing script logics, you need to consider following points for performance
consideration,
1. Use fewer commits statements;
2. While developing complex calculation, choose ABAP-BADI.
3. Scoping uses memory, hence scoping should be precise.
4. MDX syntax causes performance issues, so use SQL logics as far as possible.
5. Use limited looping to improve performance.
7. Syntax
www.suryapadhi.com surya@suryapadhi.com
STRUCTURE OF SCRIPT LOGIC: Script logic structure is divided in three parts.
1) SCOPING – In this section we define the scope of data to which calculation will be
applied.
2) BODY – In this section, we tell to the system what to be done I.e. perform calculation,
Transformation, Aggregation etc.
3) COMMIT – In this section we tell to section to save the calculated result to the
database.
*XDIM_MEMBERSET Category = PLAN
*XDIM_MEMBERSET Entity = C3000
*XDIM_MEMBERSET P_DataSrc = MANUAL
*XDIM_MEMBERSET RptCurrency = LC SCOPING
*XDIM_MEMBERSET P_Activity = EMPL1
*XDIM_MEMBERSET P_ACCT = CE0004220
*XDIM_MEMBERSET TIME = 2007.JAN
*WHEN P_ACCT
*IS CE0004220
*REC (EXPRESSION = 901) BODY
*ENDWHEN
*COMMIT COMMIT
8. Syntax
www.suryapadhi.com surya@suryapadhi.com
Script Logic can be broken down into 3 components:
• Scoping- What am I running the data on?
• Data manager scoping
• Input schedule scoping
• Scope control
• Body / Code - What do I want to do with the scoped record?
• *IIf Statements
• *REC
• [#] based MDX statements
• *WHEN / *IS / *ENDWHEN
• Allocation Logic
• Writing the records
• *COMMIT
9. Syntax
www.suryapadhi.com suryapadhi@gmail.com
Due to performance issue MDX syntaxes are less favorite among BPC developers. In this
section l will cover commonly used SQL based syntax;
1. *ADD / *ENDADD = Add set of values members (i.e. accounts) to another set of values (
i.e. account).
2. *INCLUDE = With this syntax, you can include multiple Script Logic files in a script.
Included scripts carry different calculation once you execute the main script. During LGX
generation, all codes are combined into one big piece of code and executed during runtime.
3. *REC = This statement generates a record / modifies a record that to be posted in the
database. Even if it is for the same destination cell, a source record can generate as many
destination cell records. Multiple REC statements possible between *END/*ENDWHEN
statement.
Example: -*REC (FACTOR = 0.9,ACCOUNT="DISCOUNT_EXTSALES"). Which means multiply by 0.9 to
current scoped record and replace account with DISCOUNT_EXTSALES write values to DISCOUNT_EXTSALES.
4. *XDIM_MEMBERSET = It restricts the data, filters the source dataset to the required
dataset for specific calculation, intended in the script logic. For each restriction using a
dimension, there can be a separate XDIM statement. Generally it is followed by the
Dimension name & Member value/value set.
10. Syntax
www.suryapadhi.com suryapadhi@gmail.com
5. *XDIM_ADDMEMEBERSET = This statement is used to add more member values to the
scope of member value already defined with the XDIM statement for conditional
calculations.
6. *XDIM_FILTER = Filters the members of the scope of that dimension. It does not filter the
scope of data, rather filters from available scope.
Example - *XDIM_FILTER ACCOUNT = [account].properties(ACCTYPE='AST'). In this case system will select
account members which contains ACCTTYPE property value as “AST”
7. XDIM_MAXMEMBERS = Specifies the maximum number of members that should be
included in one query.
8. XDIM_PACKAGEBY = This syntax is used for parallel processing. However, configuration
needs to be done in SPRO need to be done before using this.
9. *SELECT / *ENDSELECT = Like any other SQL statement, this syntax helps to retrieve a list
of values from the master data table (Dimension) and store them in a defined variable. Can
be written in any part of the logic and the resultant value can be used in any part of the logic
as well. Generally better to write in the beginning of the logic structure.
10. *WHEN / *ENDWHEN = *WHEN/*ENDWHEN can be used with property values of the
dimension; to further create conditions for data processing / transformation / modification /
manipulation, for the REC statement. Ex: *WHEN ACCOUNT *IS “XY00001234”. Same as
SELECT/ENDSELECT statement, but this it used when different transformation is needed for
different type of field values in a record. Hence multiple *WHEN/*ENDWHEN statements
possible within a script logic. It works as a loop statement.
11. Syntax
www.suryapadhi.com suryapadhi@gmail.com
11. *DESTINATION_APP = Use to make the datasets of one model available for other. It
transfers the data from one model to another. Between Dimension “Category” values.
12. *LOOKUP / *ENDLOOKUP = Similar to “*DESTINATION_APP” but this does not transfer
the data between the model, rather looks up for the required calculation. It is acts like a
“READ” statement in traditional ABAP. Example: While doing currency translation of a value,
it will be required to look into the EXCHANGERATES model.
13. *TMVL = This is used to retrieve a time value after taking into consideration an offset
value from a given time period. REC(FACTOR=1.1, TIME=TMVL(12,2006.APR)). In this case the
time value is 2006, Apr + 12 months = 2007,Apr.
14. *COMMIT = Saves/stores the calculated values in the database. In case of two dependent
calculations, resulting value of the first calculation must be saved into the database with a
“*COMMIT” statement, before its value is used in another calculation formula within the
script logic.
12. Syntax
www.suryapadhi.com suryapadhi@gmail.com
15. *ADD_DIM = While copying data between two models, if source model does not
contain all the dimensions as the destination model, missing dimensions in the source
model can be created/added using this syntax before data copy. Possible to use this for
multiple dimensions in one statement.
16. *RENAME_DIM = While copying data between two models, if dimension names
between the models do not match; then mismatching dimension names can be renamed to
be the same before copy process. Possible to use this for multiple dimensions in one
statement.
17. *SKIP_DIM = While copying data between two models, if the destination model does
not contain all the dimensions as the source model, some of the destination models can be
skipped from copying process using this syntax. Possible to use this for multiple dimensions
in one statement.
18. *SELECTCASE / *ENDSELETC = This is a select statement with a CASE together to
encourage conditions within. Works as IF, ELSEIF & ENDIF statement in traditional ABAP.
19. *START_BADI / *ENDBADI = This script helps in calling BAdIs within the script logic to
perform an endless variety of functions.
20. *RUNALLOCATION = This syntax help execute SAP delivered allocation logic.
13. Syntax
www.suryapadhi.com suryapadhi@gmail.com
21. *BEGIN / *END = These syntaxes are used with Boolean Expressions (YES / NO). Similar
concept, as may have seen in BW-BEX formulas. The individual conditions will be enclosed in
parenthesis. If the condition is true, the return value will be 1, else 0.
22. *IIF = These syntaxes work, just as IF, ELSEIF, ENDIF statements in traditional ABAP. If the
condition satisfies, then it directs the record to undergo a calculation.
23. *FOR / *NEXT = This syntax is used with a variable, which returns/contains multiple
values. This syntax then helps to process individual variable values, one by one. It works like
FOR EACH statement in FOX formula.
24. *GET = Retrieves the value from the memory
25. *FUNCTION / *ENDFUNCTION = This syntax is very often used in MDX. Function is used
in BPC to enhance readability.
26. *WHEN _REF_DATA = It sets the focus to either master data or transactional data. When
is set to master data, it loops through all the master data values of the dimension. And
when set to transactional data, it loops through all transactional data, which uses the
dimension/values in its scope. Without an explicit definition, the transactional data mode is
selected by default.
14. Variables
www.suryapadhi.com suryapadhi@gmail.com
Variable allows to enter values in runtime. In BPC we use two types of variables (1) user
defined variables and (2) system variables.
In case of user defined variables;
• We will have variables in script, for example $PERCENT$
• Then we define variable for prompt in the data manager package, for example
%PERCENT%.
• In run time system will replace $PERCENT$ with values we are passing via %PERCENT%.
For example *XDIM_MEMBERSET TIME = $DIM_INP$ in script logic and a prompt %DIM_INP% in DM
package will prompt the user to enter a time dimension member while running that script logic. If the user enters
2009.JAN, the package will run only for January 2009. If he/she enters BAS(2009.Q1), the package will run for Jan,
Feb, Mar of 2009
System defined variables are;
1. %USER% - Returns current Planning and Consolidation User
2. %APPSET% - Returns current Planning and Consolidation AppSet
3. %APPLICATION% - Returns current Planning and Consolidation Application
4. %YEAR% - Returns current calendar year.
15. SAP Delivered Logics
www.suryapadhi.com suryapadhi@gmail.com
Allocation.lgf - Allocation executes a distribution of values based upon a defined basis. This
functionality does not require any additional business rules to function. There are two
methods to call the allocation engine:
*RUNALLOCATION - The *RUNALLOCATION format is commonly used when an
allocation is to be performed once in the script logic file
*RUN_ALLOCATION - The *RUN_ALLOCATION format can be used when an allocation
is to be performed multiple times in the same script logic file. In the following example,
the allocation called DIST2 is first defined, and then the allocation is called multiple
times later in the code by the RUN_ALLOCATION command
Calcaccount.lgf - Calcaccount is used to prepare Cash Flow and must be executed along
with appropriately defined Account Calculation Business Rules.
Consolidation.lgf - Consolidation is used to perform legal consolidation and must be
executed along with appropriately defined Legal Consolidation Business Rules.
Copy_Opening.lgf - COPYOPENING is used to transfer ending balances from one time period
to starting periods in a subsequent time period. COPYOPENING must be executed with the
appropriate Balance Carry Forward business rules.
FX_Trans.lgf - Currency Conversion is used to translate existing records into alternative
currency views. Currency Conversion must be executed with the appropriate Currency
Conversion business rules.
16. SAP Delivered Logics
www.suryapadhi.com suryapadhi@gmail.com
ICDATA.LGF - ICDATA is used to perform intercompany reconciliation activities. ICDATA must
be executed with the appropriate ICBOOKING business rules.
ICBooking.lgf - ICBooking is used to perform intercompany reconciliation activities with
difference postings. ICBooking must be executed with the appropriate ICBOOKING business
rules.
ICElim.lgf - ICElim is used to perform intercompany reconciliation. ICElim must be executed
with the appropriate ICElim business rules.
Validation.lgf - Validation is used to perform validation activities define within the
validation business rules.
MDXlib.lgf - The MDXlib file provides examples of pre-delivered MDX financial functions.
System_Constants.lgf - The system constants file is the logic file that maps your dimension
names for an application to the standard (delivered) BPC logic. For example, the file maps
the name of the category dimension to the dimension to be used as the category.
System_Library.lgf - The System Library includes basic examples of delivered keywords and
functions.
17. Testing and Debugging
www.suryapadhi.com suryapadhi@gmail.com
To test and debug script , we can use program UJK_SCRIPT_LOGIC_TESTER or Transaction
Code: UJKT
1
2
3
4
19. Testing and Debugging
www.suryapadhi.com suryapadhi@gmail.com
1
2
3 4
The DATA REGION section allows definition
of the initial scope. Use the format
dimension=dimension_member, for
example: CATEGORY=ACTUAL.
22. Testing and Debugging
www.suryapadhi.com suryapadhi@gmail.com
The script can be executed, and all results saved to the
database, by clicking on the EXECUTE button. The
resulting system log will display the compiled code, the
number of records processed and the time to execute.
23. Few of My Contributions.
www.suryapadhi.com suryapadhi@gmail.com
Contact information:
• www.SuryaPadhi.Com
• Mail: SuryaPadhi@Gmail.Com.
My Publications
Other White Papers
• Lock Box
• Credit Card functionality in SAP
SAP Press Publications
• Explore the Payment Currency Option in Accounts Payable