sample workshop for blueprint session slides - design
TRANSCRIPT
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
1/54
4/26/2012
CONSOLIDATION
BUSINESS BLUEPRINT WORKSHOP11/08/2010
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
2/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
2
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
3/54
What is Blueprint?
The Business Blueprint concentrates on four key elements:
Events (WHEN should something be done?)Tasks or Functions (WHAT should be done?)
Organization (WHO should do WHAT?)
Communication (WHAT information is required to do the right task?)
The blueprint model defines who must do what, when, and how to complete
relevant business tasks
3
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
4/54
What happens during Blueprint phase?
Purpose
Requirements gathering for all business processes in scope
Process design to the lowest level so that these requirements are met
Identify SAP capabilities to address these requirements and document gaps in SAPcapabilities to meet these requirements
Process
Holistic, iterative, multi-faceted series of interactions
All requirements will be documented and incorporated into the design
Functional
Technical
Reporting
Organizational change
Internal Control
Deliverables
Signed-off Process Definition Document (PDD)
The document describes the business processes (process flows), their requirementsand how they will be met in SAP, including functional and technical requirements, andorganizational impacts
4
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
5/54
5
Overall approach to Global Template Blueprinting
Key business
imperatives
Stakeholdersinputs
SAP and CPGbest practices
Inputs frommarkets
BusinessArchitecture &OperatingModeldecisions
Infosys Repository
Inputs from Clorox
process team
SAP and CPG bestpractices
VRM repository
Initial CloroxReference Model
Draft process
maps
Value diagram
Initial RICEF list
Pre-configuredScenarios
Formalblueprintworkshops
SAPFit-Gapanalysis
RICEFW
identification
Draft Clorox Global Template
Detailed processmaps - global
Businessrequirements
global
Complete RICEFWlist
Gap list andrequests forcustomization
Data Requirements master data, datacleansing, data migration
Approval Process
Finalized GlobalTemplate1
1 Finalized global template will include approved process flows, approved gaps/ approved RICEFW, approvedapplication landscape and approved data requirements
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
6/54
How Will We Work Together?
Formal and structured blueprint workshops
Functional and cross-functional workshop topics Identification of key participants well in advance
Mail out agenda in advance
Distribute minutes, action items and other information back to attendees in a timely manner
Schedule the optimal group of participants
Right number of participants to make sure that markets are adequately represented
Keep number of participants to a reasonable level to make sure workshops are productive Resolve scheduling conflicts as they arise
Gathering information and follow-ups can be done outside of formal blueprint sessions
Live meeting and conference calls
E-mail
Work environment conversations
Document the results of blueprint sessions Leverage Sharepoint, ARIS and Solution Manager for documentation as per agreed
documentation standards for Atlas
Assign responsibilities and expected timelines for closure of issues, action items etc
6
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
7/54
Blueprint phase outputs
OrganizationImpacts
Inputs to End-UserTraining andKnowledge Transfer
SAP BaselineConfiguration
Identification ofSAP capabilities tomeet requirements
List of potentialgaps
Reports, Interfaces,Conversions,Enhancements and FormsInventory
Process Flows and
Definitions
7
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
8/54
8
Blueprint session key tasks
Review draft process flows and identify what works and what does not for your markets Identify gaps in the proposed process flow and document action items
For every business scenario/process, do the following:
Step 1:Identify the tasks involvedWORK PROCESS MAPPING andKey requirements
Step 2:
For each task, identify thedata used as input orrequired output.DATA MAPPINGIdentify Reportingrequirements
Step 3:For each task, who is
responsible forexecuting/owning the tasks.ROLE MAPPING
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
9/54
Blueprint Steps
Define Organization Structure
Document organization hierarchy
Define legal reporting structure
Define Business Process Flows
Document process levels
Build global end to end process model
Identify component sub-processes
Define Other Business Elements
Define policies for each process area
Define business rules for processes, sub-processes and activities
Define security roles
Define workflow routing and approvals
Identify technical requirements (Reporting, Interfaces, Conversions, Enhancements, Forms,Workflow)
Define master data elements Document internal controls
Validate Business Process Design
Review end to end process will all participating departments
Document any issues, concerns, etc.
Update process documentation, as needed
Obtain consensus and validation
9
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
10/54
Workshop Expectations
What they are:
Interactive
workshops with a clear objective, deliverable and agenda Some part of the process may be explained vs. demonstrated
Ensure functionality exists to support business process requirements
A place to participate
What they are NOT:
Training sessions
General group meetings
SAP presentation/demonstration
Fixed in duration
10
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
11/54
Participants Expectations
What do we expect from Clorox?
Give insight to the specific organizational processes you are currently using Identify potential gaps
Identify impact areas that will be affected with the to-be processes
Be a vocal and active participant in the workshop discussions
Ask questions
What can you expect from Infosys?
A thorough understanding of SAP functionality and best practices
A foundation to understand SAP terms
Prompt follow up on any outstanding questions or issues
11
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
12/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
12
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
13/54
Key objectives of the session
To discuss, define and agree on global template for Consolidations.
Review the existing Processes Analyze the Requirements
Define the future (TO-BE) Business Process
Reports
RICEF
Understand capabilities of SAP ECC in facilitating the Consolidations inHFM & EssBase
Gather feedback and agree on next steps.
13
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
14/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
14
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
15/54
Ground Rules
Demonstrate Respect and Courtesy
Cell phones should be kept in silent mode, and please only take emergencycalls
Limit engagement in side conversations during the workshop
Silence is consent to decision: speak up!
Ask Questions!
Start/end on time and allow for breaks Define common terminology - make sure the discussion is based on common
understanding of terms
1515
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
16/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
16
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
17/54
Project Atlas Solution Design Principles
Business Architecture is the foundation of next-level process and system solution design Harmonized and standardized with SAP-CPG during BA project
Stakeholders aligned to recommendations; no design changes without elevation
Drive to maximize harmonization during next-level solutioning Business process design System capability design Avoid country bias, design globally
Drive to standard SAP-CPG design and configuration choices
All customizations to be pre-approved Focused on legal/regulatory
Develop the right, rationalized set of KPIs and streamlined reports: one version of the truth Business results Process effectiveness Data accuracy System reliability
Design for future agility Business portfolio evolution, scale, operating model reconfigurations Ability to adapt to anticipated external change (customer, vendor consolidation, etc.)
Design for simplicity with appropriate international scope in mind Consider solving unique demands/requirements through process solutions rather than
just technology solutions Existing solutions do not equal business requirements (international or North Am.)
Foundation
GlobalHarmonization
Reporting & Data
Standardization
Agility
Simplicity
17
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
18/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
18
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
19/54
Record to Report Value Diagram
19
Double click on the document above to open PDF document
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
20/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutesReview of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
20
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
21/54
4/26/2012 21
DISCUSSION POINTS
Here let us review the existing processes and understand how they will change with
the implementation of SAP.
1. International P&A Audience Reports2. Current Consolidation Process3. Possible changes in HFM after SAP implementation (Traslation in SA
Journal Entries:i. US GAAP adjustments
ii. Historical Account Adjustmentsiii. Intercompany Profit in Inventory (IPI) Eliminations (PY & FY)iv. Management Adjustments (Exports, Markup Elim & X-Charges)
4. Leading Ledger vs Non leading Ledger5. Inter-company Eliminations
6. Financial Reports (FX Exposure, Local Currency Reports, Feed Data forms)7. Consolidation Close Calendar8. Pain points9. Summarization of probable Value Gains
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
22/54
4/26/2012 22
1.International P&A
1. The needed information is mainly taken from HFM and from the Int l Essbase database2. Any additional information is pulled from HFM throught Smartview tool (Manage data
directly from HFM using Excel application).3. The P&A Group, uses all the reports in USD currency.4. The mainly reports used in HFM are:
a. SBU-02 Schedule II-Profit & Loss Statement by Quarterb. INL-06 Legal to Management Transformation- P&L
Possible changes after SAP implementation(to define)
a) Automatic Interface between SAP and Essbase (Base Profit & Admin)b) Local Essbase cubes go away replaced by new International cube
c) Should we move Essbase allocation of Admin to SAP? Still needed for forecastprocess?d) Any changes you would like to see in Essbase?e) Allocation of International & Corp expenses maintain in HFM/Essbase
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
23/54
4/26/2012 23
2.Current Consolidation Process
Takes place in HFM, with a cycle of 3 stages:
a. Data loadb. Corporate consolidation and
c. Reporting
ConsolidatedReporting
Allocations
Foreign CurrencyTranslation
Intercompany
Reconciliation/Eliminations
ManagementAdjustments
ConsolidatedEntries
Data LoadLocal to US GAAP
TransformationData Mapping Data Validation
Data LoadCorporate
ConsolidationReporting
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
24/54
4/26/2012 24
Local US GAAP
Adjustments
Foreign Currency
Translation
ConsolidationAllocations
Inter-Company
Profit in InventoryEliminations
Management
Adjustments
Inter-company
Eliminations
A. Consolidation Entries:1. Recurring Topside Entries (made at the Corporate Level)2. Late Entries (> US$100K P/L impact )3. Consolidating Entries
B. Consolidated Information & Reports:1. Consolidated financial statements (P&L, BS, Equity)2. Legal Entity Reporting3. Segment reports and analysis4. Management Reporting5. Financial footnotes
2.Current Consolidation Process
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
25/54
4/26/2012 25
3.Possible changes with SAP implementation
ConsolidatedReporting
Allocations
ForeignCurrencyTranslation
IntercompanyReconciliation/
Eliminations
ManagementAdjustments
ConsolidatedEntries
Data LoadLocal to US
GAAPTransformation
Data Mapping Data Validation
Data LoadCorporate
ConsolidationReporting
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
26/54
4/26/2012 26
3.Possible changes with SAP implementation
Data Load
Local to USGAAP
Transformation
ForeignCurrencyTranslation
ManagementAdjustments
The data will be loaded in US GAAP in LC
Could be perfomed in SAP, but we need to ensure thatthe final result be the same as HFM
Explore the options to make management adjustementsin SAP
This step will no longer be required after SAPimplementation.
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
27/54
4/26/2012 27
In SAP ECC 6.0 we have the option to maintain different ledgers for a legal entity. TheseLedgers are classified into, Leading ledger & Non-leading ledgers. Each of the ledger can
be maintained for a specific accounting policy.
It has been decided that the Leading ledger will be as per US GAAP and Non-leadingledgers as per local GAAP & Tax rules for all SAP legal entities.
A.Leading Ledger
1. This ledger will be common to all legal entities.2. This ledger will be interface to HFM & Essbase for consolidated reporting
3. Maintained as US GAAP rules
4. Maintained in Local functional currency & USD.
5. Fixed assets configured to run depreciation & amortization for US GAAP
B. Non-Leading Ledgers
1. More than one Non-leading ledger can be maintained for a legal entity and these are legalentity specific
2. These ledgers will facilitate local statutory & tax reporting
3. Maintained as per Local GAAP rules.
4. Maintained in Local functional currency & USD
5. Fixed assets configured to run depreciation & amortization for Local GAAP
6. Manual adjustments from US GAAP to local GAAP for most other Local GAAP & Taxadjustments.
4.Leading Ledger vs Non Leading Ledger
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
28/54
4/26/2012 28
HFMs elimination logic is based on entity structure and ICP dimensions(defined as trading partner in SAP)
1. The Entity dimension represents the legal entity structure of the company
2. The ICP dimension provides the ability to match IC accounts by trading
partners thus enabling the IC elimination functionality in HFM. If anaccount is not properly tagged with an ICP, the IC elimination will not beperformed properly.
This process will continue taking place in HFM as of today without any changes.
Any country which has multiple entities need as legal requirement will generate
local consolidated financial information.
5.Intercompany Eliminations (Trading partner)
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
29/54
4/26/2012 29
A. All consolidated reports will be generated in HFM system as of today.
[LC (local currency) and USD].
B. SAP will provide reports to help the countries make the following adjustments:
1. Inter-company Stock Transfer,
2. Drop shipment (customers) & Services
3. Inventory Profit Elimination Adjustment
4. Management Adjustments (Exports, Markup Eliminations, etc)
C. Operational reporting for day to day management will be covered in a
separate workshop.
6.Financial Reports
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
30/54
4/26/2012 30
The close calendar is expected to remain same for most part except forthe following changes.
a) US GAAP Adjustments will be made in SAP in leading ledger. which will beinterfaced to HFM and EssBase for automated data flow.
b) Management adjustments will be made in local SAP Ledgers for localconsolidations.(in case of multiple legal entities within a country).
7.Consolidation Close Calendar
8 P i i t /
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
31/54
Pain Points Addressed
# Pain PointLevel
Addressed inCLEAR
PotentialLevel
AddressedAtlas
How Could Atlas Address this Pain Point?
SL3Mapping and manipulation of data is performed inExcel resulting in little control over thetransformation of data
Mapping from Atlas to HFM will be simplified viastandardization of chart of accounts and load will beautomated
SL1Process for generating a load file is highly manualand is not performed consistently by each country
Mapping from Atlas to HFM will be simplified viastandardization of chart of accounts and load will be
automatedME3
Frequent changes in country and/or SBUorganizational structures require significantmaintenance in multiple systems
Standardization of International Essbase platform andflexible hierarchies in Atlas. Implement Data RelationshipManager (DRM) for maintenance
ME8Flow back of data (e.g. IPC) into the localledgers/Essbase for management reportingpurposes
Principle is to house management adjustments in Atlas toflow into Essbase and HFM to maintain alignment
ME10KPIs not supported by Essbase and BW (EBIT,
EP vs. Mgmt Profit)
Build EBIT & EP into reporting requirements
ME5
Consolidated management results depend on
disparate feeder systems including multiple
Essbase instances. There are several levels of
mapping and translation which create additional
risk of time lag, validation effort and failure
Standardization of Intl Essbase, enable translationcapabilities in Atlas
8. Pain points /CLEAR Identified Pain Points to be Consideredin Atlas Scope
SL = SAP Financial Load File
ME = Management Entity Data Load and Systems
8 Pain points / CLEAR Id ifi d P i P i b C id d
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
32/54
Pain Points Addressed
# Pain Point
Level
Addressed inCLEAR
Potential
LevelAddressed
Atlas
How Could Atlas Address this Pain Point?
AC1
The system is not configured to provide thesufficient level of details to support reportingrequirements of certain consolidated reports,such as P&L, BS, OINC, and segment results.
Global chart of accounts (COA) will be configured to providesufficient level of detail
AC6Inability to identify F/X impact on variances Atlas will enable FX variance analysis at G/L level
CF1
Separate schedules/additional information isneeded because the system does not capturecash movements of long term assets andliabilities within balance sheet accounts norprovide working capital balances (USD andnon-USD).
Design Atlas to provide cashflow information more efficiently
CF3Cash flow analysis requires additionalinformation request to the SBUs and countries.
Design Atlas to provide cashflow information more efficiently,however variance explanation is still a manual process
CF4Inability to easily identify drivers of variances Design Atlas to provide cashflow information more efficiently
SR6
Analysis of segment variances is very time-
consuming, primarily due to multiple data
sources and insufficient level of detail available
in ECCS.
8. Pain points /CLEAR Identified Pain Points to be Consideredin Atlas Scope
Legend: SR = Segment Reporting
AC = Analysis of Consolidated Reports (for External Reporting)
CF = Cash Flow
8 P i i /
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
33/54
Pain Points Addressed
# Pain PointLevel
Addressed inCLEAR
PotentialLevel
AddressedAtlas
How Could Atlas Address this Pain Point?
CM2
Multiple management reporting data sources are inuse (Excel templates, Essbase, BW); withsometimes conflicting data. Significant time spentvalidating data between systems.
Principle is to house management adjustments in Atlas toflow into Essbase and HFM to maintain alignment
CM5
Country/SBUs often asked to accommodate
multiple redundant data requests, reports,questions. Requests for information at too low alevel of detail to be supported by all countries.
Business architecture recommendation was to align on
common KPIs and reporting requirements withinInternational. Global data alignment should enableconsistent reporting.
CM7
Takes significant effort to deliver ad hoc reportingrequests of consolidated management data.Unable to obtain reliable information withoutrouting requests to each country/SBU.
Business architecture recommendation was to align oncommon KPIs and reporting requirements withinInternational. Global data alignment should enableconsistent reporting. Standardized Essbase.
CM8Manual consolidation of Admin by function. Align Admin structure within Atlas
FN2
The ECCS chart of accounts does not providesufficient level of detail required for reporting
purposes, especially as related to international
activities; therefore, resulting in additional requests
and further manual data accumulation.
Global chart of accounts (COA) will be configured toprovide sufficient level of detail
8. Pain points /CLEAR Identified Pain Points to be Consideredin Atlas Scope
Legend
CM = Consolidated Management Reporting
FN = Footnotes
8 P i i t /
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
34/54
Pain Points Addressed
# Pain PointLevel
Addressed inCLEAR
PotentialLevel
AddressedAtlas
How Could Atlas Address this Pain Point?
IC1Out of Balances exist that create churn both duringthe intercompany reconciliation period as well asduring the consolidation process
Within Atlas instance double sided entries will beemployed. Considering cross instance bridge.
IC2Manual process of IC notes between SAP and Non-SAP entities as well as between countries
Within Atlas instance double sided entries will beemployed. Considering cross instance bridge.
IC3Inability to view transactional level detail to facilitatethe reconciliation process
Within Atlas instance double sided entries will beemployed. Considering cross instance bridge.
LG1The local to US GAAP adjustments are manuallycalculated
Principal is to automate and design for efficiency ofretrieving the data
LM3
Highly manual processes are used to track,
calculate and load adjustments into Essbase/ Excel,
creating potential failure/error points
Principle is to house management adjustments in Atlas toflow into Essbase and HFM to maintain alignment
LM5
Creation and consolidation of BTM schedule is
manual and challenging to understand and
reconcile, in part because BTM serves two
purposes: explaining true other income & expense
activity and tracking management adjustments
Break out and capture more OINC through a more detailedchart of accounts (like the US did) however there will stillbe some manual effort and analysis
8. Pain points /CLEAR Identified Pain Points to be Consideredin Atlas Scope
Legend: IC = Intercompany
LG = Local to US GAAP
LM = Legal to Management Transformation
8 Pain points / CLEAR ERP D Li i i P i P i NOT
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
35/54
Pain Points Addressed
# Pain PointLevel
Addressed inCLEAR
PotentialLevel
AddressedAtlas
How Could Atlas Address this Pain Point?
FN1Several footnotes require manual accumulation ofdata.
Due to the nature of this information, it is typically notincluded in the financials i.e. future lease payments
IC4Inability to understand the nature of IPC chargeswhich results in delayed resolution
International Profit Center (IPC) is not in Atlas scope
LM10Manual allocation and capture of interest expenseassociated with Burts Bees
Burts Bees US is not in Atlas scope
LM2Lack of understanding and significant time spentanalyzing transactions posted to IPC
International Profit Center (IPC) is not in Atlas scope
SR3
Certain information required for footnotes is
gathered offline via email/phone calls and
compiled in excel.
8.Pain points /CLEAR ERP Data Limitation Pain Points NOTConsidered in Atlas Scope
Legend
FN = Footnotes
IC = Intercompany
LM = Legal to Management Transformation
SR = Segment Reporting
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
36/54
4/26/2012 36
The following value gains are expected, however these will be clearlyquantified once the final design for consolidation process is finalized.
1. Automated Data flow from SAP to Other system (similar to Domestic)
2. Visibility of Transactional system to Consolidation team.
3. Possible shorting of Consolidation closing calendar.
4. Data for Management Adjustments is generated from SAP in the form ofdifferent reports.
5. Eliminate excel and improve internal controls and protect data integrity.
6. Option to move below listed management adjustments to SAP, this can helpreduce closing cycle time and help in local consolidations.
a) US GAAP
b) Exports
c) Mark-up Eliminations
9.Summarization of Value Gains
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
37/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutes
Review of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
37
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
38/54
Reporting
38
All consolidation reporting will continue to be generated from the HFMand EssBase.
SAP will facilitate through reports the management adjustments.
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
39/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutes
Review of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
39
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
40/54
40
Data elements/field selection
Fields are classified in three ways
Required :
mandatory entry is required to process the document
Optional :
can be populated or left blank
Suppressed:
not visible in the transaction, but can be used for statistical purposes
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
41/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutes
Review of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
41
RICEF - Reports Interfaces Conversions
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
42/54
RICEF - Reports, Interfaces, Conversions,Enhancements and Forms
Which Reports are in use / necessary to support the process?
General Reporting.
- HFM & EssBase
Specific reports per region?
Deterimine local reporting? TBD
42
RICEF Reports Interfaces Conversions
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
43/54
RICEF - Reports, Interfaces, Conversions,Enhancements and Forms
Which interfaces are in use / necessary?
In general? SAP to BW, EssBase & HFM
Specific interfaces per region?
TBD
43
RICEF - Reports Interfaces Conversions
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
44/54
4/26/2012 44
RICEF - Reports, Interfaces, Conversions,Enhancements and Forms
SAP Finance (FICO)(Atlas)
PCA
(Category/Entity)
HFM
BW(Reporting)
IntlEssbase
Internal Orders
Cost Centers
Controlling (CO) Area
Month-End Cost Assessments Month-End Order Settlements
CO-PA(Brand /Country)
Daily Loads
Budget,Forecast,
ActualVolumes
PlanData ??
Actual Data
US SAP(IPC
Actuals)
EssbaseFAR-IPC
ExcelLoad FileCountries
Future Interfaces SAP to EssBase / HFM
RICEF - Reports Interfaces Conversions
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
45/54
RICEF Reports, Interfaces, Conversions,Enhancements and Forms
Which enhancements are in use / necessary?
In general? TBD
Specific interfaces per region? TBD
Which forms are in use / necessary?
In general?
TBD
Specific interfaces per region? TBD
45
A d
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
46/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutes
Review of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
46
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
47/54
4/26/2012 47
TBD
Review of Key Action Items
D il N d R d d Ch
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
48/54
48
Daily Notes and Recommended Changes
Key decisionsmade
Key actionitems
Recommendedchanges to
Global
Template
R i f i t f ti
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
49/54
Review of minutes of meeting
Identify key action items, assign responsibilities and agree on a closure
date for these
49
Key action items Priority Responsibility Resolution date
Location for meeting minutes, change tracker and
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
50/54
50
g , gaction item tracker
This is where you need to go to review and update the status of differentitems -
Meeting Minutes Sharepoint URL (To be defined)
Change Tracker
Sharepoint URL
Action item tracker Sharepoint URL
A d
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
51/54
Agenda
Key topics Facilitator Duration
Introduction to Blueprint phase Doug Bozick / Ram Karanam 5 minutes
Key objectives of the session Doug Bozick / Ram Karanam 5 minutes
Rules of engagement during session Doug Bozick / Ram Karanam 5 minutes
Design principles Doug Bozick / Ram Karanam 5 minutes
Value diagram Doug Bozick / Ram Karanam 5 minutes
Discussion points Doug Bozick / Ram Karanam 60 minutes
Reporting Doug Bozick / Ram Karanam 30 minutes
Key data elements Doug Bozick / Ram Karanam 5 minutes
RICEF identification Doug Bozick / Ram Karanam 30 minutes
Review of key action items Doug Bozick / Ram Karanam 15 minutes
Wrap-up Doug Bozick / Ram Karanam 10 minutes
51
W
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
52/54
Wrap - up
Describe salient point of the discussion
Key decisions made Key action items
Big roadblocks
Describe next steps
Thank everyone and close the workshop
52
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
53/54
Thank You
53
Appendix
-
8/3/2019 Sample Workshop for Blueprint Session Slides - Design
54/54
Appendix