What are PBCS and uses?

1) PBCS is a flexible application based on Oracle Hyperion Planning that supports enterprise-
wide planning, budgeting, and forecasting in a cloud-based deployment model.

2) PBCS provides a rich Web and Microsoft Office enabled planning and modeling framework
that supports driver-based planning to help connect operational assumptions to financial
outcomes.

3) It supports a hierarchical planning process that encompasses both corporate finance and
the lines of business within an enterprise.

Dimensions:
Dimension hierarchies define relationships and consolidations between members.

We have two types of Dimensions.

1) Standard Dimensions: - Standard Dimensions are automatically created

whenever we created the application.

2) Custom dimensions: - We can create custom dimensions as per based on

project.

In Oracle Planning and Budgeting Cloud (PBCS), there are seven dimensions out of the box
which are Account, Currency, Entity, Period, Scenario, Version, and Year

-> For Single Currency application we have 6 dimensions (Missing Currency Dimension).

->For Multi-Currency we have 7 Dimensions.

For adding standard dimensions we have 4 types of members

1) Parent

2) Child

3) Siblings

4) Level 0

Level 0 members: - Which member does not have children called as Level 0 member.

Smart View
1) Smart View is excel adding connect to the PBCS application using excel.

2) We can use Smart View for club dimension members.

3) We can enter the data only for Level 0 members in Smart View

4) We cannot enter the data for Parent members in Smart View

Consolidation Properties:
->Consolidation properties are used how the Level 0 member’s data will calculate and
aggregate to the parent.

->Consolidation properties are used for which mathematical operations will be calculated for
the Level 0 member’s data aggregate to the parent.

->We have 7 consolidation properties in EPM Cloud.

1) Addition (+) 5) Percentage (%)

2) Subtraction (-) 6) Ignore (~)

3) Multiplication (*) 7) Never (^)

4) Division (/)

Differences between Ignore and Never

Ignore:-If we give ignore as a consolidation property data will not aggregate to the parent
in that particular dimension.

Never: If we give never as a consolidation property data will not aggregate to the parent in
any dimensional level.

Storage Properties
Storage Properties are used for how data will store in database.

We have 7 storage properties.

1) Store

2) Dynamic Calc

3) Dynamic Calc and Store

4) Label Only

5) Shared

6) Never Share
Store:
->If we give store as a storage property the data will be stored in database. It will occupy
some space in database.

->Generally we will give it for Level 0 members only

->If we give store as storage property to parent member unnecessarily the data will occupy
some space in database. Database size will be increased.

->The Level 0 member’s data will not be aggregated to the parent automatically.

Dynamic Calc:-
->If we give Dynamic Calc as a storage property the data will not occupy any space in
database

->Generally we will give it for Parent members only.

->If we give Dynamic Calc to Level 0 members we cannot enter the data.

3) Dynamic Calc and store:-

-> It is combination of Dynamic Calc and store.

Note: We never used this as storage property

4) Label Only:-
->Label only storage property will be used for labelling purpose and heading purpose.

->Label only will not occupy any space any space in Database

->Label only will give it only for parent members

->In Label only member we can see immediate child data.

5) Shared:-

-> If the member already existed under one parent if we need to add that member to
another parent then give shared as a storage property to that particular member.

->It will not occupy any space in database

->It is sharing under multiple parents

->Under shared member we cannot add the child and siblings also.

->We cannot add the shared member before the base member.
Shared storage property example:
We have some entities like south entity and north entity but our requirement is that to
separate the taxable entities from those entities so we have to create separate entity under
the same parent and then separate with shared storage property for taxable entities from
those entities.

6) Never Share:-
->if the member is having single child, both are having store has a storage property the child
data will come to the parent automatically. This is called as Implied Sharing.

->To overcome this implied sharing we will use Never Share as a storage property to the
parent member.

->It will occupy some space in Database.

Data Forms:-
->Data forms are used to input the data and validate the data.

->Data Forms are used by the business users and planners to enter, update and analyze the
data.

->We are using Data forms instead of Smart View

Types of Data forms:

1) Simple Data form:- Simple data form has a single-grid structure

2) Composite Data form:-Composite data form can have multiple data forms
together in single display.

Differences between the POV (Point Of View) and Pages:

->If the Dimension in POV we can select only one member from each dimension.

-> If we select any dimension in pages we can select multiple members in dimensions.

Substitution Variable:
1) Instead of changing the periods, years and scenario in the form every time we can
use substitution Variable.

2) Substitution Variable is created based on Cube.

Cube:
Cube is nothing but Database to store the data

Data Maps:

 Data Maps are used to push the Data from one cube to another cube

Unmapped dimension-if we have one dimension in source cube but not in target
cube

Smart Push:
Instead of running data push manually we are tagging Data maps to the forms by using
Smart Push Option.

Hierarchy: Functional
Income statement

NetIncome

Expenses

Revenues

Balancesheet

Assets:Ex:Land,Building….etc

Liabilities:Ex:Loans,Bad debts…..etc

Cashflow:How Cash will go out and comes in

Account Types:
Based on account we will give account type

Expenses(Ex:Grocery shopping expenses)

Revenues(Ex:Salary)

Assets(Ex:Building,Land,Furniture,Machinary)

Liability(Ex:Bad Debts,Loans)
Equity(Ex:All shares)

Saved Assumption

Data Types:
Unspecified : All types of Data

Currency : We are giving Currency Values

Non-Currency : We are giving Non-Currency Values

Percentage : We are giving percentage type of Data

Smart List : Smart Lists are using to create the drop downs in forms

Date : Date Type of Data

Text : Normal Alphabets or Text Data

Data Management:
Data Management is used to pull the data the from source application and Load the Data to
our PBCS application.

Source System : Source System is nothing but from where we are

getting the data

Target Application : Target application is nothing but to which

application we are loading the Data.

Import Format : It is used to map the dimensions between source

and target applications.

Period Mapping : It is used to mappings the periods and years between the
source and target applications.

Category Mapping : It is nothing but Scenario mapping.

Data Load Mapping : It is used to map the members between source and
target applications from each dimension.

Types of Mappings:

Explicit : If source members and target members are

different then we will use Explicit Mapping.
  It is also called as One to One mapping.

Between : The Range of source Values is replaced with a single target value.

In : Enables a list of non-sequential source values to be mapped to one

target value.

Multi Dimension : Enables you to define member mapping based on multiple

source column values.

Like : If Source members and target members are same then we

will use Like Mapping.

 It is also called as star to star mapping.

Data Load Rule : It is used to execute the data in Data Management.

Multi column Data Loading : If the Data file is having data in multiple
columns then we will use Multi Column Data Load.

 In Data Load Mapping file should be in Source,Target,,,

Data Load Workbench

Import : Data will be load from Source to Data Management.

Validate : Data will be validate for Data Load Mappings.

Export : Data will load from Data Management to our target

application.

Security:
Security is used to restrict the user’s access.

Access Levels in Security

Power user

Service Administrator

User

Viewer

User Login Report : We can see the all user’s login details.

User Group report : We can see the all group’s details

Migration:
Development : It is used to develop the application or develop the
any artifact

Test : It is used to testing the newly developed artifacts.

Production : It is live environment which is using by end users.

Migration : Migration is used to move the artifacts from one

Environment to another environment.

Artifact Migration : Migrating separate artifacts.

Snapshot Migration : Migrating entire application.

Clone Environment : It is used to copy entire application from one

environment to another environment using target application URL username and password

Dense and sparse:

Based on usage of the dimensional members we have segregate into two types.

Dense : Which dimensional members are using high those

dimensions are comes under Dense.

Account and Period

Sparse : Which Dimensional members are using less those

dimensions comes under Sparse

Entity, Currency, Version, Scenario and years

Blocks and Cells:

 Based on Dense dimension stored members under cells will be created in Database.
 Based on Sparse dimension stored members under Blocks will be created in
Database
 Each Cell we can enter 8 bytes of Data.

Number of Blocks = No of stored members in one sparse dimension *

No of stored members in another sparse dimension
 Block Size = No of stored members in one Dense dimension *
No of stored members in another dimension * 8

Difference between Attribute Dimension and UDA:

1) Attribute will be used to overcome the disadvantage of the shared Hierarchy
2) UDAs are used to overcome the disadvantage of the attribute dimension.

3) Attribute is a virtual Dimension

4) UDA is the property of the member

5) Attribute will create in dimensional Level

6) UDA will create in member level

7) Attribute is used only for Sparse dimension

8) UDA is used for both Dense and Sparse dimensions.

Differences between Dashboards and Infolets

1) Dashboards are used to combine the multiple forms.
2) Dashboards are also called as Composite forms
3) We can combine up to 6 forms only
4) In Dashboards we can see direct data and in any mode like
graph,chart,pie,percentage…etc

5) Infolets are also used to combine the multiple forms.

6) In infolets we can see the data only in graphical mode.

Member formula : We can use member formula to calculate one

member data from other members using mathematical operations.

EX: - “1005” = “1001” + “1002”;

Variance Analysis:
->Variance analysis is used to calculate the variances between prior period data and current
period data.

Note: - Current period forecast data is nothing but prior period actual data

Formula: @Var (“Actual” , “Forecast”);

Note : Expenses = Forecast-Actual

Revenues=Actual-Forecast
Business Rules:
Business Rules are used to calculate the data for all the dimensional members in simple way
using some logic.

In Business rule we will use below some DataFlow commands.

DataCopy

ClearData

AGG

CalcDim

CalcAll

Functions

@Fix - Common Combination

@Relative - Copy multiple member’s data

@IDescendants

@Remove

@LIST

@UDA

@substitution variable rule

-> (Cross Dimensional Operator): To separate the members in Rule

AGG Rule:
 If the parent is having store as a storage property if you want to aggregate to parent
for child’s data then we will use AGG rule
 In AGG command we have to write only Dimension Name.
 In AGG command we will use for only sparse dimension.

Currency Translation Business Rule:

 It is used for translate the currency from input to reporting.
 For this rule we can use Exchange Rates form and we can enter the values for FX-
Rates-Ending and FX-Rates-Average
 Exchange Rates should be enter in NO level like No entity, No currency, No
employee….etc
Movement Business Rule:
 Current Period opening Balance will come from Prior period closing balance. This is
called Movement.
 We can use below functions in movement business rule.
@Prior
@ISMBR

CALC ALL:
It calculates and aggregates entire outline database based on Outline.
Order of the calculation depends upon the characteristics of the dimensions in the outline.

Syntax: CALC ALL;

CALC DIM:
It calculates and aggregate values for all members in the specified dimensions.
Order of the calculation based on the Sparse and Dense types.

Ex : CALC DIM(dense1,sparse2,dense3,sparse4) then the order of the calculation is

dense1,dense3,sparse2,sparse4.
If at all you want to specify your own order use separate function for each dimension.
CALC DIM(dense1);
CALC DIM(sparse2);
CALC DIM(dense3);
CALC DIM(sparse4);

Syntax: CALC DIM(dimension);

Financial Reports:

Reports are using to validate the high level data of the business or Organization.

Differences between Reports and Data Forms

1) In Data forms we can enter the data

2) In Reports we cannot enter the data

3) In Data forms we can see the function option along with dimension
4) In Reports we can see the function option separately

5) In Data forms we can see only one preview

6) In Reports we can see 3 previews like HTML,PDF and XLS
 We cannot enter the data in forms for below
scenarios

1) If the form is in Read Only access

2) If the member is Parent we cannot enter the data
3) If the member is having Dynamic Calc storage property we cannot enter the
data
4) If we use valid intersections
5) Read access to the forms
6) Access is not provide to dimensional Member
7) If user is in reviewer section we cannot enter the data.

Valid Intersection:
 Valid intersections are using for cross dimensional security.
 If the form is in invalid intersection we cannot submit any data in that form.

Action Menus:
Action menus are used to navigate the one form to another form, form to business rule and
form to dashboards also.

Ex: We have to create the one source form and then give action menu name, Label
and browse the source form in Action menus. Once created the menu we have to
tag the action menu to form and then open source form, right click on source form
then we can see the action menu for that form. Click on created the action menus
form and we can see the source with source form name.

Task List:
Task lists are used to arranging the tasks in an order.

Ex: - Clear the exp data (exp_india) data with business rule

Input the data and push the data to target cube (EXP) in Data forms

Validate PUSH ran successfully or not in JOBS

Validate the data in target cube in Data forms

Create the task lists as above and then go to tasks-> run the tasks one by one.

Users will run the tasks in an order.

Smart List:
Smart Lists are using to create the dropdowns in Data forms

Ex: - we have to create the employee form and then set some employees are active and
some employees are inactive so we can create active/inactive drop downs in forms for
employee information by using Smart List and then give evaluation order for member as
account.

Evaluation Order : Evaluation order is define which data type should be

display in Forms.

Difference between User Variable and Substitution

Variable
3) User Variable is used to segregate the dimensional Hierarchy
4) Instead of changing the periods, years and scenario in the form every time we can
use substitution Variable.

5) User Variable is created based on dimension

6) Substitution Variable is created based on Cube.

SET Commands:
 SET Commands are used to optimize the Business Rule.
 SET Commands are also called as House-Keeping commands
 SET Commands are used in Application Optimisation Techniques

SETCACHE HIGH|DEFAULT|LOW;
 If SETCACHE value is HIGH 10L bytes of data will calculate.
 If SETCACHE value is DEFAULT 3L bytes of data will calculate
 If SETCACHE value is LOW 1L bytes of data will calculate

SET CALCPARALLEL; 6,8

 It indicates how many processes will run while running in the business rule.

SET COPYMISSINGBLOCK ON|OFF;

 If it’s OFF missing blocks data will not copy

SET AGGMISSG ON|OFF;

  If the parent is having store and if you want to see the child’s data aggregate to the
parent we have to run AGG business Rule
 If you clear your child data and run the AGG rule then also we can see the parent
Data will not clear to avoid this issue we will use AGG MISSG ON SET command.
AGG MISSG ON - #Missing values also aggregate to the parent.
 If OFF #Missing values not aggregate to the parent.

SET UPDATECALC ON|OFF;

 If you mentioned SET UPDATECALC command intelligent calculations will happen.
 Intelligent Calculation means only dirty blocks will calculate.
Dirty Blocks : Which blocks are update with Data
Clean Blocks : Which blocks did not update with Data

Differences between BSO (Block Storage Option) and

ASO (Aggregate Storage Option)
1) BSO will support all storage properties
2) ASO will Support Store Data,Label Only and Never Share

3) BSO will support all consolidation properties

4) ASO will support only Add and Ignore

5) BSO will support Business rules and Member Formulas

6) ASO will use MDX formulas

7) In BSO we have Dense and Sparse Dimensions

8) In ASO we don’t have any Dense and sparse dimensions

9) In BSO Data will be stored in blocks and cells

10) In ASO We have aggregated the data.

 ASO is used to reporting purpose only.

 We will input the data in BSO and run the aggregation and calculations we will push
the data from BSO to ASO by using Data Maps.
 We cannot push the data from ASO to BSO by using Data Maps.

Workforce Planning:
 Workforce planning is one of the module in our PBCS application
 Workforce planning includes employee salaries,benefits,new hires and transfers.

Gross Salary = Basic Salary+Medical+LTA+TAX+PF

Net Salary = Gross Salary – PF-TAX
Workflow (Approval Unit):
 Workflow is used to move the data from one user to another user to review and
approve the data.
 We cannot add more than one user in owner section
 If you want to add multiple users in owner section you have to create a group and
add these users to that group then tag that group to owner section.
 Owner only can able to enter the data.
 Reviewers can only review the data
 Admin will only start the approval unit

EPM Automate:
 EPM Automate is one of the Add-In to run the task without login into the
application.
 Using EPM automate we can run the business rules,we can copy snapshot from one
environment to another environment,We can download and upload the
snapshots,we can import and export the data and we can import and export
dimensional members.

Login Command:
EPMautomate login username password application URL

Business Rule:
EPMautomate RunBusinessrule Incrementrule

Time Balancing Property (TB Property):

We have 4 time balancing properties.

Flow

First

Balance

Average

Flow: If you give Flow as a TB property all the periods data will add and display in
Quarter.

EX:- Expenses, Revenues

First: If you give First as a TB property First period data will display in quarter.
 EX:-Employees, Assets

Balance: If you give balance as a TB property Last period data will display in Quarter.
EX: Opening Balance

Average: If you give Average as a TB property all the periods data will get average
and displays in Quarter.

EX: Exchange Rates.

Modules Type application:

We have to create the new application with Type as Modules. Then it is called as EPBCS
application.

Differences between PBCS and EPBCS

1) PBCS cube names can be defined during application/plan type setup.
2) EPBCS framework cube names cannot be changed.

3) In PBCS, additional dimensions can be added later in the game provided all artifacts
are updated.
4) In EPBCS, dimensions can only be added when configuring each framework for the
first time.

5) All artifacts in PBCS are created as custom development.

6) Forms, dashboards, business rules, data integration between plan types, etc. are
pre-built in EPBCS, and more can be added

7) PBCS can always be edited due to its custom nature.

8) While most EPBCS artifacts can be edited, as a general rule it is recommended that
all pre-built content be left as is to avoid dependency issues. However, new artifacts
can always be added.

Validation Rules:
 Validation Rules are using to colour the cells in Data forms.

Types of Plans:
1)Trend Based Planning : If you copy same data from one scenario to
another scenario.Then that type of planning is called TBP.

EX: Finance Planning

2)Driver Based Planning : While we are copying the data from one scenario to
another scenario if we use any percentage and increase the data then that planning is called
as DBP.

EX:Workforce Planning

Drivers are Rates in WFPlanning

Application Optimization Techniques:

 Reduce the store members in application.
 Our dimensional structure should be in Hour Glass Model

Hour Glass Model

High Dense

Low Dense

High Sparse

Low Sparse

Re-structuring the Database:

 Removing unused cells and blocks

Business Rules Optimization techniques:

Using SET Commands SET UPDATECALC ON|OFF;

SET AGGMISSG ON|OFF;

SET COPYMISSINGBLOCK ON|OFF;

Two Pass Calculation:

 Two pass calculation is a member property
 If you enable two pass calculations, calculation will happen 2 times in that particular
member.
Ex: Profit Percentage
Sales Percentage

Navigation Flows: (Restrict the view of the Homepage)

Navigation Flows are using to arranging the cards and clusters to avoid the user confusion

Cluster: group/combination of cards

Card: All these single options are called cards

Rolling Forecast:
Normal Forecast: Planning for coming months and it is a short term planning

FY24

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Actual Actual

Rolling forecast:
Rolling Forecast means your forecasting periods will be added automatically.

FY24

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Actual Actual FY25

Jan Feb Mar

FY24 FY25

Q1 Q2 Q3 Q4 Q1 Q2

Example1:If Jan is my actual period other 11 periods will be the forecasting periods in FY24 if
we move Feb as a actual period then FY25 Jan will be added as a another forecasting
period.If we Mar as a actual period FY25 Feb will be added as a forecasting period.

Example2:Q1 is the actual quarter Q2,Q3,Q4 as the forecast quarters if we move to Q2 as

actual quarter then FY25 Q1 will be added as a another forecasting quarter.

Period Open and Close:

In Scenario, Actual->Edit->We can set start and end period &year and then Refresh
Database.

->If the period is not open, we are unable to enter the data.

->Main Month end Activity

Parent Location: Instead of giving same mapping to another location we can use
parent location option.

Schedule DLR: In Data Management, We can schedule in Data load Rule.