VoIP Service and Marketing using Odoo and Asterisk PBX
How to Deploy & Integrate Oracle EPM Cloud Profitability and Cost Management (PCM) as an Allocations Sub-Ledger
1. Visit our virtual booth daily from 1:40 – 2:20 PM
Complete the
daily game
challenges
for Kscope
Kode to win!
2. How To Deploy & Integrate Oracle EPM Cloud Profitability and
Cost Management (PCM) as an Allocations Sub-ledger
Andrew Laferla
Product Manager – Profitability & Costing
Solutions
3. About the Presenter
> Andrew Laferla
> Alithya Product Manager – Profitability and Cost Management.
> Over 10 years of Enterprise Performance Management (EPM)
experience focusing on Profitability and Cost Management.
> Profitability and Cost Management and Essbase Certified.
> Hobbies: Any outdoor activity, sports (baseball, cricket and
esports), travel with family and cooking.
h_pcm in/andrewlaferla
Oracle Cloud EPM
Profitability
4. Agenda
What is Oracle EPM Cloud PCM? 01
Oracle Cloud EPM PCMUse Cases 02
Deploying Oracle PCM as a Sub Ledger 03
Integrating Oracle Financials Cloud with Oracle PCM 04
Q & A 05
5. What is Oracle EPM Cloud PCM?
Oracle EPM Cloud
Operations
Marketing
Sales
Finance
HR IT
Connected
Planning
Close with
confidence
Agile
analytics
and reporting
Outperform with
intelligence
Align enterprise
data
Analytics & Reporting
Management Reporting
External Reporting
Performance Reporting
Narrative Reporting & Disclosures
Profitability & Costing
Enterprise Data
Metadata Governance
Cloud Connectivity and Adapters
Traditional On-Premise Connectivity
& Adapters
Modern Data Architecture
Lights out Automation
Extensive ETL Capabilities
Connected Planning
Dynamic Planning
Strategic Modeling and LRP
Operational LOB Planning
Zero Based Budgeting
Driver Based Planning
Rolling Forecast
Adaptive Intelligent Planning
Comprehensive Financial Close
Financial Consolidation
Close Process Orchestration
Reconciliations & Compliance
Tax Provision & Reporting
Intelligent Process Automation
Transfer Pricing
EPBCS
FCCS
ARCS
TRCS
PCMCS
PCMCS
EPRCS
EDMCS
CDM
5
6. What is Oracle EPM Cloud PCM?
Oracle Cloud Profitability and Cost Management
Enable What-If Analysis
and Modeling
Enable Business Users to
take Ownership
Gain Insight Into Hidden Profit
and Cost
Create a Culture of
Accountability
Enable Automation to
reduce effort, risk and
reliance on IT
Oracle Profitability and Cost Management Cloud strikes the perfect
balance between a business-owned allocation engine and a rich
analytical tool to discover the fundamental drivers of cost.
6
7. What is Oracle EPM Cloud PCM?
Capabilities & Workflow
Published Reports &
Interactive Analytics
Model Development
Master Data & Data
Integration Management
Profitability & Cost Management
(PCM)
Financial Reports, Smart
View, Dashboards
Model Execution
Embedded
Intelligence
Mobile
Rule Transparency
Allocation
Engine
Integrations Dashboards &
Work Areas
7
8. Oracle Cloud EPM PCM Use Cases
A World of Calculation and Allocation Possibilities
SCENARIO
MODELING
Unlock the possibility, by
proactively managing swift
market change & evaluating
opportunities.
SHARED SERVICES
Reduce pushback from
division leaders with
transparency.
PROFITABILITY
Providing insight into
profit concentration, risks
and opportunities.
COSTING
Gain flexibility and consistency in
cost allocations.
INVESTMENT
ANALYTICS
Drive investment
strategy insight &
profitability.
INTERCOMPANY
Provide auditors with insight
and transparency needed into
intercompany allocations.
OPERATIONAL
TRANSFER PRICING
Monitor and manage
risk associated with
sender & receiver
entities.
ITSPEND
Better understand the
cost and effectiveness
of services & projects
delivered by IT.
8
10. Deploying Oracle PCM as a Sub-Ledger
• A subset of the General Ledger and provides additional details behind the
General Ledger entries
• General Ledger accounts only provide an ending balance for each Account, a Sub Ledger is
used to provide the details that result in that general ledger balance
• The total of the Subledger entry must match the line-item amount on the General Ledger
• Facilitates the creation of a “Thin Ledger”
What Is a Sub-Ledger?
Accounts
Receivable
Ledger
Accounts
Payable
Ledger
Fixed
Asset
Ledger
Inventory
Ledger
Purchase
Ledger
Sales
Ledger
Cash
Ledger
Project
Ledger
Fixed
Assets
Ledger
Common Types of Sub-Ledgers:
10
11. Deploying Oracle PCM as a Sub-Ledger
Characteristics of a Sub Ledger
11
General Ledger SubLedger
The General Ledger controls the Sub-Ledger, the Sub-Ledger is an extension of the General Ledger
Part of the Chart of Accounts (COA)
Integrates with the General Ledger, but does not have its
own Chart of Accounts
Provides a summaries of transactions and contains limited
volumes of data
Provides details of transactions and contains large
volumes of data
Master set of accounts where transactions are recorded Total must match with the line-item amount from the
General Ledger
Trail Balance is prepared in the General Ledger Trail Balance is not prepared in the Sub Ledger
12. Deploying Oracle PCM as a Sub-Ledger
Sub Ledger Use Cases
Use Case
Classification
Application Examples Description Pre-Allocated
Detail Example
Post Allocated Detail Key Challenges
Management
Reporting
Management Allocation
Fully Allocated P&L
PCM is deployed as a Sub Ledger to
facilitate the creation of Strategic
P&Ls, support Management Decision
making and drive organizational
behavior
Account
Department (Cost
Center)
Entity
Data Source
Account
Department (Cost Center)
Entity
Resource
Allocation Pool
Product/Service/Channel/Region/F
und/Client
High Visibility and Internal
Scrutiny
Flexibility and Rate of Change
Data Volume
Multiple Data Sources
Operational Profitability PCM is deployed as a Sub-Ledger to
preform detailed cost and revenue
calculations and allocations to
ensure appropriate and accurate
profitability reporting at Channel,
Client and Product level.
Account
Department (Cost
Center)
Entity
Data Source
Account
Department (Cost Center)
Entity
Resource
Allocation Pool
Product/Service/Channel/Region/F
und/Client
Flexibility and Rate of Change
Data Volume
Reporting Complexity
Multiple Data Sources
12
13. Deploying Oracle PCM as a Sub-Ledger
Sub Ledger Use Cases
13
Use Case
Classification
Application Examples Description Pre-Allocated
Detail Example
Post Allocated Detail Key Challenges
Financial Close
and Regulatory
Reporting
Intercompany Billing and
Charge Backs
PCM is deployed as a Sub Ledger to
calculated the charges and billing that
is appropriate between different
Responsibility Centers within an
organization
Account
Department (Cost
Center)
Entity
Data Source
Account
Department (Cost Center)
Entity (Sender)
Resource
Allocation Pool
Product/Service
Entity (Receiver)
Allocation/Calculation complexity
Flexibility
Scalability
Time Pressure
Regulatory Impact
Intermediate Journal Complexity
Operational Transfer Pricing PCM is deployed as a Sub Ledger to
calculated the charges and billing that
is appropriate between different
Multi-National Entities within an
organization
Account
Department (Cost
Center)
Entity
Currency
Data Source
Account
Department (Cost Center)
Entity (Sender)
Currency
Resource
Allocation Pool
Product/Service
Entity (Receiver)
Allocation/Calculation complexity
Flexibility
Scalability
Time Pressure
Regulatory Impact
Multiple Currencies
Multiple General Ledgers
High Journal Complexity
14. Deploying Oracle PCM as a Sub-Ledger
Common Architecture
Metadata Management – EDMCS
Oracle Financials
Cloud
Data
Warehouse
Other source data
Source Systems
Cloud
Data
Management
(CDM)
Integration
Engine Reporting and BI Engine
Smart View Reporting
Cloud Analytics
Financial reporting
Oracle
EPM Cloud
Oracle Cloud EPM
Calculation and Allocation Engine
PCMCS
Shared Service Cost Allocations
OTP Calculations
Product/Service/Channel/Region/Fund/Client
Calculations/Allocations
Journal Preparation
Pre-Allocated Data Preparation
Resource/AllocationPool/Activity Allocations
14
15. Integrating Oracle Financials Cloud with Oracle PCM
Two Way Integration with the General Ledger
Year Period Scenario Version Currency Department Account Entity Product Channel Client Rule Balance Amount
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 No Product No Channel No Client NoRule Input 27,871.00
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 No Product No Channel No Client NoRule Input 13,939.00
PCMCS Output
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 No Product No Channel No Client Calculation Rules Allocation Out (27,871.00)
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 No Product No Channel No Client Calculation Rules Allocation Out (13,939.00)
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_467 CLT_15828 Calculation Rules Alllocation In 7,220.26
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_372 CLT_30381 Calculation Rules Alllocation In 6,221.63
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_459 CLT_33406 Calculation Rules Alllocation In 7,374.72
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_299 CLT_30951 Calculation Rules Alllocation In 1,811.21
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_170 CLT_16961 Calculation Rules Alllocation In 1,689.47
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_391 CLT_32361 Calculation Rules Alllocation In 3,553.71
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_467 CLT_15828 Calculation Rules Alllocation In 3,260.82
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_372 CLT_30381 Calculation Rules Alllocation In 1,664.79
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_459 CLT_33406 Calculation Rules Alllocation In 1,091.98
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_299 CLT_30951 Calculation Rules Alllocation In 1,583.94
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_170 CLT_16961 Calculation Rules Alllocation In 2,923.96
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_391 CLT_32361 Calculation Rules Alllocation In 3,413.52
GL_EFFECTIVE_DATE CURRENCY_CODE COST CENTER GL CODE ENTITY PRODUCT EXPENSE CODE INTERCOMPANY FUTURE USE Debit Credit Line Description Operator GL_Operator Originating System
4/31/2021 USD 37500 463212 2221 - - - 27,871.00 FY21_Apr__Allocation Out TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 - - - 13,939.00 FY21_Apr__Allocation Out TPR_ADMIN n303452 PCMCS
4/31/2021 USD 37500 463212 2221 2207 - - - 20,816.61 FY21_Apr_2207_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 37500 463212 2221 3908 - - - 7,054.39 FY21_Apr_3908_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 2207 - - - 6,017.58 FY21_Apr_2207_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 3908 - - - 7,921.42 FY21_Apr_3908_Alllocation In TPR_ADMIN n303452 PCMCS
General Ledger Input
15
GL_EFFECTIVE_DATE CURRENCY_CODE
COST CENTER GL CODE ENTITY PRODUCT EXPENSE CODE INTERCOMPANY FUTURE USE Debit Credit Line Description Operator GL_Operator Originating System
4/1/2021 USD 37500 463212 2221 0 0 0 9,525.00 Transaction Detail 001 TPR_ADMIN n303452 TPR
4/1/2021 USD 10800 463233 2241 0 0 0 2,091.00 Transaction Detail 002 TPR_ADMIN n303452 TPR
4/3/2021 USD 37500 463212 2221 0 0 0 8,164.00 Transaction Detail 003 TPR_ADMIN n303452 TPR
4/3/2021 USD 10800 463233 2241 0 0 0 3,436.00 Transaction Detail 004 TPR_ADMIN n303452 TPR
4/6/2021 USD 37500 463212 2221 0 0 0 7,442.00 Transaction Detail 005 TPR_ADMIN n303452 TPR
4/6/2021 USD 10800 463233 2241 0 0 0 5,537.00 Transaction Detail 006 TPR_ADMIN n303452 TPR
4/7/2021 USD 37500 463212 2221 0 0 0 2,740.00 Transaction Detail 007 TPR_ADMIN n303452 TPR
4/7/2021 USD 10800 463233 2241 0 0 0 2,875.00 Transaction Detail 007 TPR_ADMIN n303452 TPR
Oracle GL Output
17. Integrating Oracle Financials Cloud with Oracle PCM
Inbound Integration Through Cloud Data Management
Year Period Scenario Version Currency Department Account Entity Product Channel Client Rule Balance Amount
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 No Product No Channel No Client NoRule Input 27,871.00
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 No Product No Channel No Client NoRule Input 13,939.00
PCMCS Input
GL_EFFECTIVE_DATE CURRENCY_CODE
COST CENTER GL CODE ENTITY PRODUCT EXPENSE CODE INTERCOMPANY FUTURE USE Debit Credit Line Description Operator GL_Operator Originating System
4/1/2021 USD 37500 463212 2221 0 0 0 9,525.00 Transaction Detail 001 TPR_ADMIN n303452 TPR
4/1/2021 USD 10800 463233 2241 0 0 0 2,091.00 Transaction Detail 002 TPR_ADMIN n303452 TPR
4/3/2021 USD 37500 463212 2221 0 0 0 8,164.00 Transaction Detail 003 TPR_ADMIN n303452 TPR
4/3/2021 USD 10800 463233 2241 0 0 0 3,436.00 Transaction Detail 004 TPR_ADMIN n303452 TPR
4/6/2021 USD 37500 463212 2221 0 0 0 7,442.00 Transaction Detail 005 TPR_ADMIN n303452 TPR
4/6/2021 USD 10800 463233 2241 0 0 0 5,537.00 Transaction Detail 006 TPR_ADMIN n303452 TPR
4/7/2021 USD 37500 463212 2221 0 0 0 2,740.00 Transaction Detail 007 TPR_ADMIN n303452 TPR
4/7/2021 USD 10800 463233 2241 0 0 0 2,875.00 Transaction Detail 007 TPR_ADMIN n303452 TPR
Oracle GL Output
17
Cloud Data
Management
1a
2a
3a
4a
5a Map the Oracle GL Account to the appropriate PCMCS Account and prefix if necessary
6a
Transformation Requirements
Consolidate and Map the GL_EFFECTIVE_DATE to the Year, Period, Scenario and Version
Map Oracle GL Currency to PCMCS Currency
Map the Oracle GL Cost Center to the appropriate PCMCS Department and prefix if necessary
Map the Oracle GL Entity to the appropriate PCMCS Entity and prefix if necessary
Map "Input" as the Balance Member
Map "NoRule" as the Rule Member
Map dimensions not available in Oracle GL to the "No_..." of each appropriate dimension
18. Integrating Oracle Financials Cloud with Oracle PCM
Executing Oracle PCM Allocations – Creating the Detail!
Input Financial Data Data that does not change from one
allocation step to the next
Data that changes from one allocation
step to the next
18
Entity Account Department Product Channel Client
Source Expense
Financial Data
Entity Account Department
Shared Services
Allocations
Entity Account Department
Shared Services Allocation Drivers
Product
Allocations
Entity Account Department Product
Product Allocation Drivers
Channel
Allocations
Entity Account Department Product
Channel Allocation Drivers
Channel
Client
Allocations
Entity Account Department Product
Client Allocation Drivers
Channel Client
Revenue
Financial Data
Entity Account Department Product Channel Client
Driver Data (Input or Calculated)
19. Integrating Oracle Financials Cloud with Oracle PCM
Journal Process Requirements by Model Classification
Use Case Classification Application Examples Journal Requirement Journal
Complexity
Journal Description
Management Reporting Product Profitability Possible – Reporting Low Consolidated Allocation results by Account, Entity and Product.
Possible Due To and Due From requirements if Shared Services costing was
required.
Management Allocations Possible – Reporting Low Consolidated Allocation results by Account and Entity
Possible Due To and Due From requirements if Shared Services costing was
required.
* Regulatory requirements do not apply to all clients but those within specific industries and involves the tracing of dollars
between entities and validation of results.
Financial Close and
Regulatory Reporting
Intercompany Billing Yes – Regulatory* Medium Consolidated AllocationCalculation Results by Account, Sender and
Receiver Entity Intersections.
Journals must accommodate the Due To and Due From requirements of the
destination Ledger.
Intercompany billing can come under scrutiny in regulated industries (such
as utilities).
Operational Transfer Pricing Yes – Regulatory* High Multi-national implication and complexity
Consolidated Expense, Base Revenue and Mark-Up Revenues by Sender and
Receiver Entity Intersections.
Highly regulated with intense scrutiny on the journal output.
Journals must accommodate the Due To and Due From requirements of the
destination Ledger.
Multiple Ledgers (Oracle, PeopleSoft etc) must often be supported.
19
20. Integrating Oracle Financials Cloud with Oracle PCM
Journal Classifications and Challenges
SingleLedgerJournalw/o
intercompanyorshared
servicesbilling
SingleLedgerJournalwith
intercompanyorshared
servicesbilling
Multi-LedgerJournalwith
intercompanyorshared
servicesbilling
Characteristics:
• Low Complexity
• P&L impact Only
• Expense Accounts Only
Challenges:
• Mapping Requirement of fields in Ledger.
• Mapping Requirement of fields not in the Ledger.
• Balanced entry
SINGLELEDGERJOURNALW/OINTERCOMPANYORSHARED SERVICESBILLING
SINGLELEDGERJOURNALWITHINTERCOMPANYORSHARED SERVICESBILLING
Characteristics:
• Medium Complexity
• P&L and Balance Sheet
• ICP Expense and Revenue Accounts
Challenges:
• Mapping Requirement of fields in Ledger.
• Mapping Requirement of fields not in the Ledger.
• Balanced entry on both Income Statement and Balance Sheet.
MULTI-LEDGERJOURNALWITHOPERATIONALTRANSFERPRICING
Characteristics:
• High Complexity
• P&L and Balance Sheet
• ICP Expense and Revenue Accounts
• Multi-Currency
Challenges:
• Mapping Requirement of fields in Ledger.
• Mapping Requirement of fields not in the Ledger.
• Balanced entry on both Income Statement and Balance Sheet.
• Multi-Ledger environment.
• Multi-Financial Standard Environments.
• Accommodation for balancing of different currencies in the P&L and Balance Sheet.
20
22. Integrating Oracle Financials Cloud with Oracle PCM
• The following example is a Retail client who is performing Operational Profitability.
• In the example, the client is allocated costs associated with specific Departments, Entities and Accounts
to Product, Channel and Client level of detail.
• A single ledger, Oracle GL, is utilized as the General Ledger and no specific Journal preparation
calculations are preformed in PCMCS.
• The following integration is required:
• Extract of post allocated results from PCMCS.
• Mapping of PCMCS output to GL fields.
• Creation of the GL Control file.
• Ability to view and validate the prepared Journal file prior to posting to the Ledger.
• Key Challenges:
• Population of GL Fields not available in PCMCS
• Force Rounding of the PCMCS Output
Outbound Integration (PCMCS -> Oracle GL) – Low Complexity
22
23. Integrating Oracle Financials Cloud with Oracle PCM
Outbound Integration (PCMCS -> Oracle GL) – Low Complexity
Year Period Scenario Version Currency Department Account Entity Product Channel Client Rule Balance Amount
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 No Product No Channel No Client NoRule Input 27,871.00
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 No Product No Channel No Client NoRule Input 13,939.00
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 No Product No Channel No Client Calculation Rules Allocation Out (27,871.00)
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 No Product No Channel No Client Calculation Rules Allocation Out (13,939.00)
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_467 CLT_15828 Calculation Rules Alllocation In 7,220.26
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_372 CLT_30381 Calculation Rules Alllocation In 6,221.63
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_2207 CHN_459 CLT_33406 Calculation Rules Alllocation In 7,374.72
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_299 CLT_30951 Calculation Rules Alllocation In 1,811.21
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_170 CLT_16961 Calculation Rules Alllocation In 1,689.47
FY21 Apr Actuals Final USD DPT_37500 ACCT_463212 ENT_2221 PRD_3908 CHN_391 CLT_32361 Calculation Rules Alllocation In 3,553.71
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_467 CLT_15828 Calculation Rules Alllocation In 3,260.82
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_372 CLT_30381 Calculation Rules Alllocation In 1,664.79
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_2207 CHN_459 CLT_33406 Calculation Rules Alllocation In 1,091.98
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_299 CLT_30951 Calculation Rules Alllocation In 1,583.94
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_170 CLT_16961 Calculation Rules Alllocation In 2,923.96
FY21 Apr Actuals Final USD DPT_10800 ACCT_463233 ENT_2241 PRD_3908 CHN_391 CLT_32361 Calculation Rules Alllocation In 3,413.52
PCMCS Output
GL_EFFECTIVE_DATE CURRENCY_CODE COST CENTER GL CODE ENTITY PRODUCT EXPENSE CODE INTERCOMPANY FUTURE USE Debit Credit Line Description Operator GL_Operator Originating System
4/31/2021 USD 37500 463212 2221 - - - 27,871.00 FY21_Apr__Allocation Out TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 - - - 13,939.00 FY21_Apr__Allocation Out TPR_ADMIN n303452 PCMCS
4/31/2021 USD 37500 463212 2221 2207 - - - 20,816.61 FY21_Apr_2207_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 37500 463212 2221 3908 - - - 7,054.39 FY21_Apr_3908_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 2207 - - - 6,017.58 FY21_Apr_2207_Alllocation In TPR_ADMIN n303452 PCMCS
4/31/2021 USD 10800 463233 2241 3908 - - - 7,921.42 FY21_Apr_3908_Alllocation In TPR_ADMIN n303452 PCMCS
General Ledger Input
23
Cloud Data
Management
1a
2a
3a
4a
5a
6a
7a
8a
9a
9b
9c
Map the PCMCS Account to the GL Account
Transformation Requirements
Mapping of the PCMCS Year, Period and Scenario members into the Effective Date GL Field
Map PCMCS Currency to Currency_code GL Field
Map the PCMCS Department to the GL Cost Center
Map the PCMCS Entity to the GL Entity
Map the PCMCS Product to GL Product.Unspecified Product is mapped to NULL.
If the PCMCS Balance member is "Allocation In" load amount as a Debit.If the PCMCS Balance member is "Allocation Out" load amount as a Credit.
Populate the Line Description GL Field by concatenating the first three characters of the PCMCS Scenario with the PCMCS Year, PCMCS Period, PCMCS Product and PCMCS
Balance
Populate the Originating System GL Field with the appropriate value
Populate the Operator GL Field with the appropriate GL Operator User
Populate the Operator GL Field with the appropriate GL Operator
24. Integrating Oracle Financials Cloud with Oracle PCM
• The following example is a Financial Services client who is implementing Operational Transfer Pricing
(OTP) with a requirement to produce Journals for Multiple Ledgers (PeopleSoft and Oracle GL).
• In the below example, the client is charging their London and Mexico Branches with services rendered by
their US Bank Entity. Their US Bank Entity is currently utilizing Oracle Cloud Financials while their
Branches are on a separate PeopleSoft General Ledger.
• In order to accommodate the requirement two separate Journal files are prepared in the Integration
process.
• Revenue and Account Receivable Journals are loaded to the Oracle GL.
• Expense and Account Payable Journals are loaded to the Peoplesoft GL.
• Because of the complexity, Journal preparation calculations are executed in PCMCS to prepare the post
allocated results prior to their export to the Journal. These steps include:
• Mapping of the Post Allocated results onto the appropriate PeopleSoft ICP Expense and Payable
Accounts
• Mapping of the Post Allocated Results onto the appropriate DataSource (AccountingView) to
facilitate the creation of the various Journals
Outbound Integration (PCMCS -> Multiple Ledgers) – High Complexity
24
25. Integrating Oracle Financials Cloud with Oracle PCM
• The following integration is required:
• Extract of post allocated results from PCMCS
• The preparation of separate Journal files with different specifications and fields
• Mapping of PCMCS output into the appropriate fields for each destination ledger
• The creation of the Balance Sheet entries
• Creation of the GL Control files
• Ability to view and validate the prepared Journal file prior to posting to the Ledger
• Key Challenges:
• Journal preparation calculations must be preformed in PCMCS
• Ability to create dual General Ledger Journals (Expense and Revenue movements within a single ledger) and
one-sided ledger entries(Expense/Revenue on one ledger and the corresponding Revenue/Expense on the
other ledger).
• Creation of the Balance Sheet Journals in the General Ledgers to map the appropriate Receivable and Payable
Accounts based on the PCMCS Account, DataSource and Balance member.
• Force Rounding of the PCMCS Output
Outbound Integration (PCMCS -> Multiple Ledgers) – High Complexity
25
26. Integrating Oracle Financials Cloud with Oracle PCM
Outbound Integration (PCMCS -> Oracle GL) – High Complexity
GL_EFFECTIVE_DATE currency_code COST CENTER GL CODE LOCAL CODE
ENTITY EXPENSE CODE INTERCOMPANY FUTURE USE Debit Credit Line Description Operator GL_Operator Originating System
4/2/2020 USD 37500 903212 771230 BNK_002 0 BR_001 0 177.04 ACT_2019_12_A-115-e2_Revenue TPR_ADMIN n303452 TPR
4/2/2020 USD 37500 193212 781230 BNK_002 0 BR_001 0 177.04 ACT_2019_12_A-115-e2_Receivable TPR_ADMIN n303452 TPR
4/2/2020 USD 10800 903233 771230 BNK_002 0 BR_003 0 1991.55 ACT_2019_12_A-120-a1_Revenue TPR_ADMIN n303452 TPR
4/2/2020 USD 10800 194412 781230 BNK_002 0 BR_003 0 1991.55 ACT_2019_12_A-120-a1_Receivable TPR_ADMIN n303452 TPR
Oracle GL Journal File
Cloud Data
Management
Year Period Scenario Version Currency Sender Entity Account AllocationPool Receiver Entity DataSource Resource Rule Balance Amount
YR2020 Dec Actuals Final USD SE_37500 ACCT_463212 A-115 RE_31532 DT_JournalPrep_Revenue Total Resource Calculation Rules Allocation Out -177.04
YR2020 Dec Actuals Final USD SE_10800 ACCT_463233 A-120 RE_31533 DT_JournalPrep_Revenue Total Resource Calculation Rules Allocation Out -1991.55
YR2020 Dec Actuals Final USD SE_37500 ACCT_903212 A-115 RE_31532 DT_JournalPrep_Expense_Base Total Resource Calculation Rules Allocation In 166.4176
YR2020 Dec Actuals Final USD SE_37500 ACCT_493212 A-115 RE_31532 DT_JournalPrep_Expense_MarkUp Total Resource Calculation Rules Allocation In 10.6224
YR2020 Dec Actuals Final USD SE_10800 ACCT_903233 A-120 RE_31533 DT_JournalPrep_Expense_Base Total Resource Calculation Rules Allocation In 1872.057
YR2020 Dec Actuals Final USD SE_10800 ACCT_493233 A-120 RE_31533 DT_JournalPrep_Expense_MarkUp Total Resource Calculation Rules Allocation In 119.493
PCMCS Output
1a
2a
3a
4a
4b
4c
5a
6a
7a
8a
9a
9a
10a
11a
12a
13a
Map Expense and Revenue Accounts
Remove Account Prefix
If the DataSource is "DT_JournalPrep_AllocOut" create a Account Payable Row entry map the applicable Payable Account.
If the DataSource is "DT_JournalPrep_AllocIn" create a Account Receivable Row entry map the applicable Payable Account.
Map the Local Code GL Field from the Account Field
If the DataSource is "DT_JournalPrep_Expense" then map the Receiver Entity to the Entity GL Field.
If the DataSource is "DT_JournalPrep_Revenue" then map the Sender Entity to the Entity GL Field
Transformation Requirements
Mapping of the PCMCS Year, Period and Scenario members into the Effective Date GL Field
Map PCMCS Currency to Currency_code GL Field
If the DataSource is "DT_JournalPrep_Revenue" then map the Sender Entity to the Cost Center GL Field
If the DataSource is "DT_JournalPrep_Expense" then map the Receiver Entity to the Cost Center GL Field
Populate the Originating System GL Field with the appropriate value
If Account is a Receivable Account then map the GL Intercompany Field from the PCMCS Receiver Entity.
If Account is a Payable Account then map the GL Intercompany Field from the PCMCS Sender Entity.
If the DataSource is "DT_JournalPrep_AllocIn" then map the Sender Entity to the Intercompany GL Field
If the DataSource is "DT_JournalPrep_AllocOut" then map the Receiver Entity to the Intercompany GL Field
Map "0" to the Expense Code and Future Use Fields in the GL.
If the PCMCS Balance is "Allocation Out" map the value to the Credit GL Field.
If the PCMCS Balance is "Allocation In" map the value to the Debit GL Field.
Populate the Line Description GL Field by concatenating the first three characters of the PCMCS Scenario with the PCMCS Year, PCMCS Period, PCMCS Allocation Pool and PCMCS DataSource.
Populate the Operator GL Field with the appropriate GL Operator
Populate the Operator GL Field with the appropriate GL Operator User
For Accounts Payable and Accounts Receivable, map to the correct Debit/Credit GL Fields based on the corresponding PCMCS Expense Accounts, DataSource and Balance.
26
27. Integrating Oracle Financials Cloud with Oracle PCM
Outbound Integration (PCMCS -> PeopleSoft) – High Complexity
Cloud Data
Management
Year Period Scenario Version Currency Sender Entity Account AllocationPool Receiver Entity DataSource Resource Rule Balance Amount
YR2020 Dec Actuals Final USD SE_37500 ACCT_463212 A-115-e2 RE_31532 DT_JournalPrep_Revenue Total Resource Calculation Rules Allocation Out (177.04)
YR2020 Dec Actuals Final USD SE_10800 ACCT_463233 A-120-a1 RE_31533 DT_JournalPrep_Revenue Total Resource Calculation Rules Allocation Out (1,991.55)
YR2020 Dec Actuals Final USD SE_37500 ACCT_903212 A-115-e2 RE_31532 DT_JournalPrep_Expense_Base Total Resource Calculation Rules Allocation In 166.42
YR2020 Dec Actuals Final USD SE_37500 ACCT_493212 A-115-e2 RE_31532 DT_JournalPrep_Expense_MarkUp Total Resource Calculation Rules Allocation In 10.62
YR2020 Dec Actuals Final USD SE_10800 ACCT_903233 A-120-a1 RE_31533 DT_JournalPrep_Expense_Base Total Resource Calculation Rules Allocation In 1,872.06
YR2020 Dec Actuals Final USD SE_10800 ACCT_493233 A-120-a1 RE_31533 DT_JournalPrep_Expense_MarkUp Total Resource Calculation Rules Allocation In 119.49
PCMCS Output
1a
2a
3a
4a
4b
5a
6a
6b
7a
8a
9a
10a
10a
If Account is a Receivable Account then map the GL Affiliate Field from the PCMCS Receiver Entity.
If Account is a Payable Account then map the GL Affiliate Field from the PCMCS Sender Entity.
If the DataSource is "DT_JournalPrep_AllocIn" then map the Sender Entity to the Affiliate GL Field
If the DataSource is "DT_JournalPrep_AllocOut" then map the Receiver Entity to the Affiliate GL Field
Map PCMCS Currency to Currency_code GL Field
Swap sign and populate the Amount Column with the Values as extracted from PCMCS.
Populate the Line Description GL Field by concatenating the first three characters of the PCMCS Scenario with the PCMCS Year, PCMCS Period, PCMCS
Allocation Pool and PCMCS DataSource.
If the DataSource is "DT_JournalPrep_Expense" then map the GL Legal Entity to the Sender Entity's Legal Entity.
If the DataSource is "DT_JournalPrep_Expense" then map the PCMCS Receiver Entity to the mirror PeopleSoft Department Field.
If the DataSource is "DT_JournalPrep_Revenue" then map the PCMCS Source Entity to the mirror PeopleSoft Department Field.
If Accounts is Expense Account, map to corresponding PeopleSoft Mirror Expense Account
If Accounts is Revenue Base Account, map to corresponding PeopleSoft Mirror Revenue Base Account
If Accounts is Revenue Mark-Up Account, map to corresponding PeopleSoft Mirror Revenue Mark-Up Account
If the DataSource is "DT_JournalPrep_Expense" create a Account Payable Row entry map the applicable PeopleSoft Mirror Payable Account.
If the DataSource is "DT_JournalPrep_Revenue" create a Account Receivable Row entry map the applicable PeopleSoft Mirror Payable Account.
If the DataSource is "DT_JournalPrep_Revenue" then map the PCMCS Source Entity to the PeopleSoft Entity Field.
If the DataSource is "DT_JournalPrep_Expense" then map the PCMCS Receiver Entity to the PeopleSoft Entity Field.
Remove Department Prefix
Transformation Requirements
Mapping of the PCMCS Year and Period into the Begin Date, End Date and Period.
Populate the Originating System GL Field with the appropriate value
Create Journal ID
If the DataSource is "DT_JournalPrep_Expense" then map the GL Legal Entity to the Receiver Entity's Legal Entity.
Originating System Begin Date End Date Period Journal ID Legal Entity Department Account Entity Affiliate currency_code Amount Line Description
TPR 03312020 04302020 4 1 BRCH 28222 75001 LON_BRCH BNK_002 USD 166.42 ACT_2019_12_A-115-e2_Expense_Base
TPR 03312020 04302020 4 2 BRCH 28222 75009 LON_BRCH BNK_002 USD 10.62 ACT_2019_12_A-115-e2_Expense_MarkUp
TPR 03312020 04302020 4 3 BRCH 28222 990012 LON_BRCH BNK_002 USD (177.04) ACT_2019_12_A-115-e2_Payable
TPR 03312020 04302020 4 4 BRCH 28223 903233 MEX_BRCH BNK_002 USD 1,872.06 ACT_2019_12_A-120-a1_Expense
TPR 03312020 04302020 4 5 BRCH 28223 903239 MEX_BRCH BNK_002 USD 119.49 ACT_2019_12_A-120-a1_Expense_MarkUp
TPR 03312020 04302020 4 6 BRCH 28223 994412 MEX_BRCH BNK_002 USD (1,991.55) ACT_2019_12_A-120-a1_Payable
PeopleSoft GL Journal File
27
28. Closing
ENTERPRISE CLOUDLICENSING
Companies who have already invested
in Oracle Cloud can leverage their
existing investment
ORACLE PCMUSE CASES
Oracle PCM can be used for multiple
Use Cases across different industries
INTEGRATING INBOUND DATA
Leverage CDM and its myriad of
capabilities to integrate, and
automation the extraction, mapping
and import of data into Oracle PCM
JOURNAL REQUIREMENTS
Different PCM Use Cases have different
Journal Requirements and Challenges.
Knowing them upfront can avoid
serious complications during
development.
PRODUCING JOURNALS
Utilize Oracle PCM and CDM
capabilities to produce Journals that
can be loaded to Oracle Financial
Cloud
DEPLOYING ORACLE PCMAS A SUBLEDGER
Create Efficiency while driving detailed
analytics and intercompany billing
28