0% found this document useful (0 votes)
332 views7 pages

CFIN - Initial Load Approach For Review - Revised - V2.0

The document discusses options for the initial data load approach for a CFIN project. Option 1 is to use standard SAP programs for the initial load without an ETL tool to distribute year-to-date profit and loss balances at the cost object level. This would involve manual reclassification and reconciliation after the initial load. Option 2 is recommended which uses an ETL tool to distribute balances at the cost object level during the initial load in order to have full profit and loss visibility and avoid significant post-load effort.

Uploaded by

Gaurav Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
332 views7 pages

CFIN - Initial Load Approach For Review - Revised - V2.0

The document discusses options for the initial data load approach for a CFIN project. Option 1 is to use standard SAP programs for the initial load without an ETL tool to distribute year-to-date profit and loss balances at the cost object level. This would involve manual reclassification and reconciliation after the initial load. Option 2 is recommended which uses an ETL tool to distribute balances at the cost object level during the initial load in order to have full profit and loss visibility and avoid significant post-load effort.

Uploaded by

Gaurav Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Key Design Decisions

Initial Load Approach


Data Load - Summary options
2. Standard SAP & ETL tool
1. Standard SAP 3. ETL tool for P&L & BS
for P&L reclassification

GL balance* & Open item upload GL balance* & Open item upload GL balance* & Open item upload
Solution

P&L - GL and default CC P&L - GL and default CC P&L - GL ac by cost object


BS - GL ac and actual or default PC* BS - GL ac and actual or default PC BS - GL ac and actual or default PC
*If Imperial can provide actual PC split
Reclassification

Could be performed manually by To be performed by ETL tool for P&L None required*
Imperial after the upload (for cost centers only) after the initial Reclassification at PC level will be
High effort to reclassify high volume upload. needed if actual PC split can not be
objects as per slide 2 Others still need to be reclassified applied during the initial load
manually as per slide 2

● Full P&L cost object visibility


● Covers all reclassification
Pros

● SAP Standard ● Full P&L cost object visibility


objects (see next slide)
Cons

● Significant effort to reclassify P&L ● Cost/effort of ETL tool ● Cost/effort of the ETL tool
Reclassification
Required / ETL
Impact of not
Object Description Volume reclassification
Optional reclassifying (2)

Impacting in year b/f position,


no reporting view for the
uploaded data and year on
Cost objects Cost centers are the business functions Optional High year comparative reporting Yes
(wherever a comparison is
involve for cutover year))

Adjustment to correct the group IFRS ledger


Ledger and Local GAAP ledgers accordingly
Required Medium / Low N/A No

Trading Trading partners provide the link to


intercompany partner and associated balances
Required Medium N/A No
partner

Full Trial Balance at market


shall not be possible as many
Profit Center Profit Center (‘market’) Optional* Medium balances will lie in the default No
profit centre eg assets , bank
balances, inventories etc..

Where reclassification is optional; the business benefits of


*In order to have a full Trial Balance at market level(profit centre), the opening balance
reclassification visibility ‘v’ effort would need to be evaluated by Imperial
would need to be reclassified by actual profit center. Areas such a inventory/fixed assets
will always remain in default if not reclassified properly. As above the cost benefit would
need to be determined
KDD – XXX Initial Load Strategy
Do you agree with this recommendation? WORK IN PROGRESS

Owner: XXXXXXX Sponsor: XXXXXX This KDD is customized:


Option customized with : 

Decision Description & Background


The approach for the initial load was approved by the DA on KDDXXX, this KDD is to agree on the technical approach for the initial transaction data load during cutover for CFIN project.

Design Options Considered & Rationale


Option 1 – Initial Load using SAP Standard Program (One Step Process – No ETL to Distribute YTD P&L balance at Cost Object)

High Level Steps


1. Load – Automatic Using SAP Standard Programs
• Open Line Items (AP/AR/GL) : Company Code/Account/Sub Ledger Account/Document/Profit Centre (Default or Derived)
• GL BS Balances – @Go-Live Date Balances : Company Code/GL/Document Currency /Profit Centre (Default or Derived)
• P&L (Primary and Secondary Postings) - YTD Balances : Company Code/GL(Cost Element)/Document Currency /Profit Centre (Default or Derived)

2. Reclassification (if required) – Manual Entries using SAP Standard Transactions


• Reclassification Entries – Cost Object /Ledger/Profit Center*/Trading Partner
Impact on:
3. Reconciliation/Validation – Manual
- Commercial
• Technical - Field level Reconciliation
- Source/Get Ready
• Business - Source Vs CFIN Trial Balance at different reporting GAAPs
- Customization
- No Impact
Pros –
• Use of SAP standard program - SAP support shall be available during preload and post load
• Standard SAP process will support any reset/reverse of the cleared items at the time of Initial load at source

Cons –
▪ No granularity of P&L balances at Cost Object (e.g., cost center) contra to approved KDD 172b ( balances loaded at cost object)
▪ Ledger determination design (KDD 043) will not work. May lead to additional reclassification workload.
▪ Additional Enhancement to derive the Initial Load document types (Default for YTD balance load and Mapping as per KDD 064 for Open Item loads)
▪ Reclassification of YTD Intercompany GL balances at Trading Partner level
* Enhancement to derive the correct profit center may be written subject to logic
▪ Default Movement Type hence no movement visibility for the Initial Load Balances
availability else default as per approved KDD 172b
▪ Unavailability of COPA Reporting Dimensions for initial balances
▪ Re assessment of ECC/Production system sizing (Transfer tables are populated with the Initial load data prior to transfer to CFIN)
KDD – XXX Initial Load Strategy
Do you agree with this recommendation? WORK IN PROGRESS

Owner: XXXXXXX Sponsor: XXXXXX This KDD is customized:


Option customized with : 
Decision Description & Background
This KDD is to agree on the approach for doing the initial transaction data load during cutover for CFIN project.

Design Options Considered & Rationale


Option 2 – Initial Load (as on cutover date) using SAP Standard Program (2 Step Process – ETL to Distribute YTD P&L balance at Cost Object)

High Level Steps –


1. Load –
Step 1 Load using SAP Standard Program
• Open Line Items (AP/AR/GL) : Company Code/Account/Sub Ledger Account/Document/Profit Centre (Default or Derived)
• GL BS Balances- @Go-Live Date Balances : Company Code/GL/Document Currency /Profit Centre (Default or Derived)
• P&L (Primary and Secondary Postings)- YTD Balances : Company Code/GL(Cost Element)/Document Currency /Profit Centre (Default or Derived)
Step 2 Extraction , Transformation and Load (Using Tool) for distributing YTD P&L Balance at Cost Object
• Extraction of Source P&L data summarized at Cost Object
• Transformation of data
• Load of transformed data in CFIN
• Reconciliation Activities
Impact on:
2. Reclassification – Manual Entries using SAP Frontend Transactions - Commercial
• Reclassification Entries – Ledger/Profit Center*/Trading Partner - Source/Get Ready
- Customization
3. Reconciliation/Validation – Manual - No Impact
• Technical - Field level Reconciliation
• Business - Source Vs CFIN Trails Balance at different reporting GAAPs

Pros –
• Use of SAP standard program hence SAP support shall be available during preload and post load
• Standard SAP process will support any reset/reverse of the cleared items at the time of Initial load at source
• Break of P&L balances at Cost Object (e.g., cost center) as per KDD 172b
Cons –
▪ Ledger determination design (KDD 043) will not work. May lead to additional reclassification workload. * Enhancement to derive the correct profit center may be written subject to logic
▪ Reclassification of YTD Intercompany GL balances at TP level availability else default as per approved KDD 172b
▪ Default Movement Type hence no movement visibility for the Initial Load Balances
▪ Unavailability of COPA Reporting Dimensions
• Higher Risk Profile on cutover timelines with a 2-step process
• Re assessment of ECC/Production system sizing (Transfer tables are populated with the Initial load data prior to transfer to CFIN)
• Cost/Resource Implication
KDD – XXX Initial Load Strategy
Do you agree with this recommendation? WORK IN PROGRESS

Owner: XXXXXXX Sponsor: XXXXXX This KDD is customized:


Option customized with : 

Decision Description & Background


This KDD is to agree on the approach for doing the initial transaction data load during cutover for CFIN project.

Design Options Considered & Rationale


Option 3 – Initial Load using 3rd party ETL tool (e.g., Magnitude etc )

High Level Steps –


1. Extraction, Transformation and Load using 3rd party tool
• Open Line Items (AP/AR/GL) : Company Code/Account/Sub Ledger Account/Document/Profit Centre (Default or Derived)/Trading Partner Impact on:
• GL BS Balances- YTD Balances : Company Code/GL/Document Currency /Profit Centre (Default or Derived)/Trading Partner - Commercial
• P&L (Primary and Secondary Postings)- YTD Balances : Company Code/GL(Cost Element)/Document Currency /Cost Object/Trading Partner - Source/Get Ready
- Customization
2. Reclassification – Manual Entries using SAP Frontend Transactions - No Impact
• Reclassification Entries – Profit Center*

3. Reconciliation/Validation – Manual
• Technical - Field level Reconciliation
• Business - Source Vs CFIN Trails Balance at different reporting GAAPs

Pros –
• Flexible in terms of defining custom transformation logics
• No Additional enhancement (Ledger/Document Type) to be brought in CFIN. Reliant on the 3rd party tool to build all the transformation logic
• No Additional Reclassification for Ledger/Trading Partner**/Cost Object
• One Time Trial Balance Reconciliation Activity
• Single step process provides reduction in time/effort in compared to 2 step process
• No additional ECC system sizing is required
• Same tool/logic may be applied to extract , transform and load from the non sap system *Enhancement to derive the correct profit center may be written subject to logic availability
else default as per approved KDD 172b
Cons – ** Get Ready activity defined against KDD046 to be implemented
▪ SAP support might not be available due to custom load approach
▪ Default Movement Type hence no movement visibility for the Initial Load Balances
▪ Unavailability of COPA Reporting Dimensions
▪ Standard SAP process will support any reset/reverse of the cleared items at the time of Initial load at source (refer appendix for the detailed scenarios). This might be reduced by putting a SOP on the reset/reverse pre initial load cleared items in source.
▪ Cost Implication
KDD – XXX Initial Load Strategy
Do you agree with this recommendation? WORK IN PROGRESS

Owner: XXXXXX Sponsor: XXXXXX This KDD is customized:


Option customized with : 

Design Options Considered & Rationale


Reporting SAP Field Mandatory/Optional Use Case Option 1 Option 2 Option 3
Dimensions/Requireme * Enhancement to derive the correct
nt
profit center may be written subject to
logic availability else default as per
Full Financial Statement Company Code Mandatory Will help to prepare the full year financial Cutover Cutover Cutover approved KDD 172b
at Legal Entity position at legal view
** Get Ready activity defined against
Full Financial Statement Profit Mandatory Will help to prepare the full year financial Reclassification* Reclassification* Reclassification* KDD046 to be implemented
at Market Center/Profit position at managerial view
Center Hierarchy *** Transactional Currency and Local
Currency shall be absolute value from the
Full Financial Statement Ledger Mandatory Will help to prepare the full year financial Reclassification Reclassification Cutover source.
at Different Reporting position at statutory view Group currency and Hard Currency shall
GAAPs be translated in CFIN based on the rate
maintained on the cutover date.
Intercompany Balances Trading Partner Mandatory Intercompany Balance Reconciliation Reclassification Reclassification Cutover**
**** Reporting available only for the
Realtime replicated data and not for the
P&L at Business Cost Center, Optional (Depends on Reporting of total cost incurred at different Reclassification Cutover Cutover initial load.
Function e.g., cost Internal Order, the Imperial business functions
objects WBS/Projects requirement)

Reporting Currencies Currency Type Mandatory Reporting at different Currency Types .e.g., Cutover*** Cutover*** Cutover***
Transactional Currency, Local Currency, Group
Currency , Hard Currencies

COPA Dimensions COPA Not Available Reporting at different dimensions like product Not Not Available**** Not Available****
Characteristics hierarchy, customer hierarchy etc. Available****

Volume Reporting Reporting UOM Not Available Overview of sales volume periodically or total Not Not Available**** Not Available****
sales volume as on cut off date Available****

Reporting Based on Movement Type Not Available Movements of fund e.g. Cashflow Not Not Available**** Not Available****
Movement Types Available****

Tax Reporting VAT Tax Not Available VAT / WHT Reporting Not Not Available**** Not Available****
Codes/WHT Tax Available****
Codes

You might also like