Deep Dive Workshop MC4F - Model Company for Finance Scope … · 2020. 8. 21. · Intercompany) Source Application Treasury For Treasury and Risk Management we use: Flow Type, Product

Customer

Deep Dive Workshop MC4F - Model Company for FinanceScope Option 09 “Financial Planning & Analysis”

2CUSTOMER© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Contents

• MC4F: Scope options

• Master Data

• Scenario 1. Revenue Planning and Forecasting

• Scenario 2. Cost Center Planning and Forecasting

• Scenario 3. Purchasing Planning and Forecasting

• Scenario 4. Financial Deals Planning and Forecasting

• Scenario 5. Financial Planning and Forecasting

• Scenario 6. P&L Planning and Forecasting

• Scenario 7. Balance Sheet Planning and Forecasting

• Scope summary

MC4F: Scope options


SAP Model Company for Finance: Scope options

07 TreasuryManagement

Core Financial

Scope Options

Special products and

reporting solutions

Machine Learning

Solutions

01 Accounting& Financial

Close

05 ML BusinessAnalysis

04 ManagementAccounting

06 CashManagement

08 Real Estate & IFRS 16

02 ML ProcessEfficiency

10 CorporateClose

BPC solutions

09 FinancialPlanning

03 ML Compliance


02 Cash Management

Bank Account Management

Bank Communication Management

Cash & Liquidity Management

Bank Fee Management

02 ML Business Analysis

Real Spend

Financial Statement Insights

SAP Model Company for Finance: Scope options

Accounting & Financial Close

General ledger

Accounts payable/Accounts receivable

Asset accounting

Credit Management

Collections and Dispute Management

Period end closing, reporting

Accruals Management

Logistics Integration

Advanced Compliance Reporting

02 Management Accounting

Predictive Accounting

Profitability and Cost Analysis

Overhead Actual Costing

Product Costing by Order

Product Costing by Sales Order

Product Costing by Period

Plan integration with BPC

Financial Planning & Analysis

Revenue P+F*

Cost Center P+F*

Purchasing P+F*

Financial Deals P+F*

Financial P+F*

Profit & Loss P+F*/Balance Sheet P+F*

04

ML Process Efficiency

Cash Application

GR/IR Reconciliation

ML Compliance

Continuous Control Monitoring

Tax Compliance incl. Predictive analytics

Tax Compliance Smart Automation

Treasury Management

Financial Instruments

Treasury Analytics

Hedge Accounting for FX Forwards

02 Real Estate & IFRS 16

Contract Management

Notices and Renewals for Contracts

Resubmissions for Contracts

Periodic Postings for Contracts/One-Time Postings

Adjustment of Conditions

Sales-based Rent Agreements and Settlement

Contract Valuation (e.g. IFRS 16)

Revaluation after Contract Changes

Corporate Close

Group Reporting (Data Monitor, Consolidation

Monitor, Reporting)

* P+F - Planning and Forecasting

05

06

07

0801

10

09

02

03


SAP Model Company for Finance: Scope option 09

S/4 HANA BPC Optimized/Embedded

Revenue

planning

Cost center

planning

Financial deals

planningPurchase

planning

Financial

planning

P&L

Balance

sheet

planning

➢ Market segment

➢ Profit Center

➢ Sales

➢ Cost center planning

➢ Production

➢ G&A

AC

DO

CA

Production

orders

COSP_BAK

(Primary

costs)

Purchase

Order

Accruals

Cash

management

Treasury

management

Purchase

requisitions

Master Data


All Master Data are on-line from S/4 (scope option 01, scope option 04, scope option 06, scope option 07).

No local Master Data in BPCPurchasing

ManagementSales and Distribution Other ProcessesAccounting Treasury

Standardization

Normalized and standard master data

should be used. Any variation of

settings should be eliminated as the

interfaces.

Centralization

Master Data is managed centrally.

The list of general data,

organizational structure data and

responsible employees should be defined.

Integration

Master Data management processes

should be organized as end-to-end. All

necessary mappings and characteristic

inheritances should be prepared and maintained in SAP

Master Data Management

Principals

List of analytics in BPC:

Chart of Accounts

G/L Account

Controlling Area

Cost Center

Plant

Certainty Level

Ledger

Project Definition

Profit Center

Material

Material Group

Product

CustomerWBS ElementCategoryCompany Code

Etc.

Deep Dive

* - Specific info-object in BPC

No reference - Best Practice (standard info-object)

Customer Group

Segment

Devision

Liquidity Item

Purchase Requisition

Number*

Source Document ID*

Arrangement TRM*

Flow TRM*


Master Data Management Deep Dive


Master Data Management Deep Dive


Master Data and Organizational Structure Deep Dive


Master Data and Organizational StructureLiquidity Items

Material Management

For Material Management we use:

✓ Material (Inventory/Service)

✓ WBS element (CAPEX/OPEX)

Sales and Distribution

For Sale and Distribution we use:

✓ Planning group (Domestic, Foreign,

Intercompany)

✓ Source Application

Treasury

For Treasury and Risk Management

we use:

✓ Flow Type, Product Type

✓ Transaction Type

✓ Internal Reference (for Short and

Long Terms)

Finance

For Finance we use:

✓ GL accounts

✓ Advance Payment

✓ Etc.

Treasury Transactions

Spot Deals

Loans

Receivables & Payables

Down Payments Request

Payment Request Down Payment

Purchase Request and Orders

Sales Orders

Liquidity Forecast

Memo Records

Key features

Liquidity items represent the source and use of cash flows in your company

It serves as an import dimension for financial planning and reporting in SAP Cash Management

Data for Liquidity Forecast based on

different sources in SAP

assigned by the special rules to

Liquidity Items.

Deep Dive


Master Data and Organizational StructureLiquidity Items. Hierarchies Definition

SAP S/4HANA

Mid-term

forecast

Short-term

forecast

Cash

Balance

Annual

PlanningActual

Liquidity Items Hierarchy

OPERATIONAL

- Revenue domestic

- Dividends

Cash receipt

….

Cash payment

- ….

FINACIAL

INVESMENT

1.900

1.200

400

300

Users can view budget amounts and actually consumed amounts of unified Liquidity Hierarchy

SAP BPC SAP BPC

Unified Liquidity Items Hierarchy

SAP provides the unified and transparent Liquidity Items

Hierarchy for MC4F.

Liquidity Items Hierarchy

Liquidity Items can be built in Liquidity Items Hierarchy.

Hierarchy defined can be used by:

• Annual Planning form for Budgeting

• Cash Management applications

• Plan/Actual reporting



Deep Dive



Deep Dive



Currency

Company Code

Currency

▪ is the currency in which the local

ledgers are managed in external

Accounting. It is already predefined

in the system and is the national

currency of the company code.

Group

Currency

▪ is used as the global currency for

all ledgers and company codes,

thereby achieving a uniform

currency with comparable currency

amounts

Transaction

Currency

▪ is currency in which a document is

posted.

For MC4F

▪ It possible to plan data in three hard currencies. Each key figure is saved with transaction, company and group currency. If a

query assumes manual input, e.g. planning key figure in transaction currency, translation to other currencies executes while

saving using a callback. System uses callback “BeforePlanDataSave”. Using of this callback defines the logic that should be

executed every time a user saves plan data.

For Planning

Deep Dive



Currency

Deep Dive

Scenario 1

Revenue Planning and Forecasting


Scenario 1 Revenue Planning and ForecastingProcesses and Values

Deep Dive

• Copy Last Year Actuals

• Plan Market Segment

• Copy Plan to Forecast

• Forecast Market Segment


• Plan Profit Center


• Forecast Profit Center

• The Revenue planning process will consist of inputting data, via an input template.

• Market segment and profit center planning differs with analytic, but the processes look very similar – either zero-based planning or copying

the previous year’s actual data with adjustments for current year.

• Sales planning is carried out from last year’s actual data, but only copied quantities and prices could be adjusted. Amount key figure is always

calculated. These variants are interchangeable, only one of them can be chosen.

• Forecasting process is based on copying the plan data and further adjustments.

This scenario is end-to-end and has following values for a Client such us …

Market segment planning Profit center planning Sales planning


• Plan Sales


• Forecast Sales


Scenario 1 Revenue Planning and ForecastingMarket segment planning


Deep Dive


Scenario 1 Revenue Planning and ForecastingProfit center planning


Deep Dive


Scenario 1 Revenue Planning and ForecastingSales planning


Deep Dive


Scenario 1 Revenue Planning and ForecastingProcesses and Integration

▪ BEA Revenue Planning

This E2E scenario is based on scenarios from

Best Practice:

• Outgoing Invoice (actual in the previous year)

• P&L Planning and Forecasting

Integration with:

Market segment planning Profit center planning Sales planning

Deep Dive


Scenario 1 Revenue Planning and ForecastingRevenue Planning and Forecasting. Extensions

Key features:

• Market segment planning

o manual planning

o starting point - previous year's actual revenues

o using for planning on material (or product) group and

customer group level

• Profit center planning

o manual planning


o using for planning on segment and profit center level

• Sales planning

o manual planning

o starting point - previous year's actual expenses

o using for planning on material (or product) group and

customer group level

Primary objects:

• DataStore Objects (advanced)

o MC4Finance: Revenue Plan Data /MLC/FINA6

• Composite Provider

o MC4Finance: Revenue Plan and actual data

/MLC/FINC3

• Calculation views

o FCO_C_IBP_ACDOCA

Deep Dive


Scenario 1 Revenue Planning and ForecastingRevenue Planning and Forecasting. Extensions

Deep Dive


Scenario 1 Revenue Planning and ForecastingRevenue Planning and Forecasting. Benefits and Capabilities

Benefits

This process have the ability to retrieve both master

and transactional data on a “Real-Time” basis

Plan data is saved in Info-Provider with selected

category value meaning single version of plan data.

This guarantee, that whereas plan documents in S4

can be changed, but current budget figures will

remain constant

Optimized workbooks with proper analytics for

selected planning process

Key Capabilities

Manual planning different parts of revenue by

using appropriate analytics: market segment,

profit center, sales

Actual data is retrieved in real-time mode

The user creates a snapshot of current S4

data via standard Copy planning function

The system has additional category type for

forecasting

Once the data has been collected in company

currency, it will be executed through the

currency translation process in order to

generate group currency

Ensure convenient data planning in three variances

Deep Dive

Scenario 2

Cost Center Planning and Forecasting


Scenario 2 Cost Center Planning and ForecastingProcesses and Values


• Plan Cost Centers

• Copy to ERP (Primary costs)


• Forecast Cost Centers

• Copy Plan from S4

• Copy Forecast from S4

• In the Cost center planning, planning is done manually. Planning is based on the previous year’s actuals, the data is copied into the selected plan version, and

then can be adjusted. The data should be submitted in the company currency. Forecasting process for cost center planning is based on copying the plan data

and further adjustments.

• The starting point for planning production costs are documents from S/4HANA system – production orders. Production order contains information about

components, it's quantities and required dates. The main prerequisite of this subprocess: production orders should be in released state. When a user releases

production order, the system creates reservation document. The data from a set of reservation documents is retrieved to planning form via CDS view.

Planning is done in transaction currency.

• The General and administration costs (G&A) planning process is divided into 2 parts: S4-related planning – for Services, BPC-related planning – for Materials.

Purchase Order Accrual functionality is used for S4-related planning.

• To segregate actual data between Production costs and G&A, the Functional Area and G / L Account type restrictions are used.


Cost Center Planning and

ForecastingProduction Cost Planning and

ForecastingG&A Cost Planning and Forecasting



• Plan G&A Material Quantities

• Plan G&A Material prices

• Plan G&A Material costs

• Copy Plan to Forecast G&A Material Quantities

• Forecast G&A Material Quantities

• Copy Plan to Forecast G&A Material Prices

• Forecast G&A Material Prices

• Forecast G&A Material Costs

Deep Dive


Scenario 2 Cost Center Planning and ForecastingCost Center Planning and Forecasting. Transfer plan data to CO

▪ One of the major step of Cost

center planning sub-process is a

retraction of results into CO

(primary costs – table

COSP_BAK).

▪ Process of plan activity quantity

and calculating plan activity price

is a process in CO.

▪ Only G/L Accounts with cost

element type 1,4,11,12 and 90 are

relevant for retraction. And cost

element types 43 and 21 are for

secondary costs – we don’t use

these accounts for retraction from

BPC.

▪ Only debit postings are retracted.

Version in CO for retraction – 0

(Plan/actual version).

▪ We retract key figures in company

currency because in Cost Center

planning we plan in company

currency and translate data in

group currency and transaction

currency while saving data.

Deep Dive



We use Virtual Info Provider /ERP/COOM_V04 for retraction plan data from BPC to CO. This is the Virtual provider which doesn’t physically

contain data, it is only combine data (by union) from aDSO /MLC/FINA1 «MC4Finance: Cost Center Plan» and standard virtual Info Provider

/ERP/COOM_V04 «Cost Center: Cost Element Planning».

Deep Dive



In Type/Attributes of Virtual InfoProvider /ERP/COOM_V04 in Data Warehousing Workbench (transaction RSA1) you will

see that retraction is done through the write interface CL_FCOM_IP_IPROV_WRITABLE.

Deep Dive



Deep Dive

▪ Write interface

CL_FCOM_IP_IPROV_WRITABLE calls

BAPI

BAPI_COSTACTPLN_POSTPRIMCOST.

▪ This is a standard SAP BAPI to write back

planned costs and revenues to ERP.

▪ You can’t see target table COSP_BAK in the

BAPI because posting is capsuled, which

means that all transactions don’t post by

themselves but call the posting

interface/function module

K_DOCUMENT_UPDATE which executes

the CO posting.

▪ All transactions automatically write back to

table COSP_BAK (as well as to

COSS_BAK) using this central posting

interface.



“Copy to ERP” button uses the planning

function /MLC/FINL25_PF01 “Plan Data

Transfer for Cost Centers: BPC to ERP”

within planning sequence

/MLC/FIN_CC_PS07 “Cost Center Plan

Data Transfer: BPC to ERP” which

provides copying of plan data from aDSO

/MLC/FINA1 “MC4Finance: Cost Center

Plan” back to ERP table COSP_BAK (and

COSS_BAK).

Deep Dive

Cost Center Plan Data Transfer: BPC to ERP

/MLC/FIN_CC_PS07

/MLC/FINL25 /MLC/FINL25_FIL01 /MLC/FINL25_PF01


Scenario 2 Cost Center Planning and ForecastingProduction Cost Planning and Forecasting

Deep Dive


Scenario 2 Cost Center Planning and ForecastingG&A Cost Planning and Forecasting. Capabilities

The General and administration costs (G&A) planning process is divided into 2 parts:

S4-related planning – for Services BPC-related planning – for Materials

Plan amounts

on periods are

calculated on

the fly in S4

Deep Dive


Scenario 2 Cost Center Planning and ForecastingProcesses and Integration

▪ BEX General Cost Center Planning


Best Practice:

• Incoming Invoice (actual in the previous year)

• Create order, Approve order, Accruals Management (Accruals

Management)

• Create Production/Shop Order, Release Production Order

(Procurement of Goods (Production))


Integration with:

Cost Center Planning and

Forecasting

Production Cost Planning and

ForecastingG&A Cost Planning and Forecasting

Deep Dive


Scenario 2 Cost Center Planning and ForecastingCost Center Planning and Forecasting. Extensions

Key features:

• Cost Center Planning and Forecasting

o manual planning


o using for planning on cost center level

• Production Cost Planning and Forecasting

o automated planning

o prerequisite – released production orders

o plan data is retrieved from reservation documents

• G&A Cost Planning and Forecasting


o prerequisite – purchase orders for services

o plan amounts on periods are calculated on the fly and

copied from S/4 using planning function

Primary objects:

• DataStore Objects (advanced)o MC4Finance: Cost Center Plan /MLC/FINA1

o MC4Finance: Purchase budget /MLC/FINA9

o MC4Finance: G&A and Production cost Plan data /MLC/FINA7

• Composite Providero MC4Finance: Plan and actual cost center data /MLC/FINC1

o MC4Finance: Cost Center Plan Data Transfer to CO /MLC/FINCR

o MC4Finance: Plan and actual purchasing data /MLC/FINC4

o MC4Finance: Plan and actual G&A costs /MLC/FINC9

• Virtual Providero MC4Finance: Plan and actual cost center data /ERP/COOM_V04


o FCO_C_IBP_ACDOCA

o ZMLC_FIN_CLVPURREQ

o ZMLC_FIN_CLMATDOC

o ZMLC_FIN_CLVPURCOST

Deep Dive


Scenario 2 Cost Center Planning and ForecastingCost Center Planning and Forecasting. Retraction

Deep Dive

Scenario 3

Purchasing Planning and Forecasting


Scenario 3 Purchasing Planning and ForecastingProcesses and Values

• Copy Plan from S4 and G&A

• Copy Forecast from S4 and G&A

• Reservation documents for materials are generated from production orders and purchase requisition. These reservation documents and stocks are

considered when determining missing quantity for purchase. System generates purchasing requisitions on missing quantity using standard MRP

functionality. All these documents must be released.

• Plan data from the relevant documents retrieved via CDS view. Planning is done in transaction currency.

• General and administration costs are copied from G&A costs planning aDSO using planning function.

• Forecasting process is based on the same approach.



Deep Dive


Scenario 3 Purchasing Planning and ForecastingBenefits and Capabilities

Ensure unified Purchasing Plan form S4/HANA and BPC

Purchase requisitions

and purchase orders.

Run MRP

General and

administration costs are

from G&A costs planning

aDSOS4/H

AN

A

BP

C

BPC

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~

Deep Dive


Scenario 3 Purchasing Planning and ForecastingProcesses and Integration

▪ BEU Internal Order Planning


Best Practice:

• Run MRP (Procurement of Goods (Production))



Integration with:


Deep Dive


Scenario 3 Purchasing Planning and ForecastingPurchasing Planning and Forecasting. Extensions

Key features:

• Purchasing Planning and Forecasting


o prerequisite – released purchase requisitions (accruals)

for G&A and requirement planning has been carried out

o plan data is retrieved from purchase requisitions, also

including projects requisitions

Primary objects:


o MC4Finance: G&A and Production cost Plan data

/MLC/FINA7


• CompositeProvider

o MC4Finance: Plan and actual purchasing data /MLC/FINC4


o FCO_C_IBP_ACDOCA

o ZMLC_FIN_CLVPURREQ

o ZMLC_FIN_CLMATDOC

o ZMLC_FIN_CLVPURCOST

Deep Dive


Scenario 3 Purchasing Planning and ForecastingPurchasing Planning and Forecasting. Extensions

Deep Dive

Scenario 4

Financial Deals Planning and Forecasting


Scenario 4 Financial Deals Planning and Forecasting Processes and Values



• The usual starting point for planning investments and borrowings is the information about a deficit or a surplus of funds for the current or next year.

• As a prerequisite, manager creates financial transaction documents in Treasury management. These transaction documents are retrieved into

Financial deals budget.

• Planning is done in transaction currency.




Deep Dive


Scenario 4 Financial Deals Planning and ForecastingProcesses and Integration

• Deposits, Loans, Spot/Forward FX (Financial Instruments)

• Investment Loan (Loans for Investment Projects)

• Interest Rate Swap (Budgeting for Interest Costs)

• Shares Investment (Shares and Bonds)


Integration with:


Deep Dive


Scenario 4 Financial Deals Planning and ForecastingFinancial Deals Planning and Forecasting. Capabilities

Spot Deals


Key Capabilities

New planning process. Not existing in

Best Practice

Financial transaction documents are

retrieved in real-time mode from

Treasury management

Treasury Transactions data are

copied into Info-Provider from S4.

Plan data are lock for changes

The interests of these deals (loans

and deposits) are transferred into the

according interest accounts in P&L

budget, using a developed CDS to

determine the G/L account through

linked tables.

Loans Spot/Forward FX Investment Loan Shares Investment

Treasury Transactions

Deep Dive


Scenario 4 Financial Deals Planning and ForecastingFinancial Deals Planning and Forecasting. Extensions

Key features:

• Financial Deals Planning and Forecasting


o prerequisite – financial transactions has been created

o G/L accounts are determined from

TRACC_ACCSYMBREP table

Primary objects:


o MC4Finance: TRM plan data /MLC/FINA8


o MC4Finance: Plan and actual TRM data /MLC/FINC5


o ZMLC_FIN_CLTTRMTD01

Deep Dive


Scenario 4 Financial Deals Planning and ForecastingFinancial Deals Planning and Forecasting. Extensions

Deep Dive

Scenario 5

Financial Planning and Forecasting


Scenario 5 Financial Planning and Forecasting Processes and Values


• Payment conditions

• Calculate plan Cash flow


• Plan Cash Flow


• Calculate Forecast Cash flow


• Forecast Cash Flow

• Managers plan ingoing and outgoing cash flows. The usual starting point for this process is the data from revenue, purchasing, financial deals, costs

planning budgets for the current or next year.

• The financial planning process is divided into 2 subprocesses: S4-related planning & BPC-related planning

• Cash Management functionality is used for S4-related subprocess. Plan data is retrieved from FQM_FLOW table into the different versions of planning

process. The system marks the source of data with Certainty Level analytics. The prerequisites for this process are existing in S/4HANA purchase

requisitions, purchase orders, vendor open items (including down payment requests) and financial transactions.

• Liquidity Item derives from G/L account. Payment conditions are planned manually as a shift of the period of payment and percent of payment. And then

cash flow is calculated based on the revenue plan and payment conditions.

• To plan other costs, plan data can be carried from the actual data for the previous year, and then can be adjusted. Planning is done in transaction currency.

• There is an additional report/workbook which displays combined plan data from both subprocesses.


Financial Planning and Forecasting

• Financial Plan on Periods

• Financial Forecast on Periods

Analytics

S4-related planning

BPC-related planning

S4-related planning

BPC-related planning

Deep Dive


Scenario 5 Financial Planning and ForecastingBenefits and Capabilities

Ensure unified Financial plan form S4/HANA and BPC

Copy of S4/HANA plan data

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~Manual planning

Copy of S4/HANA actual data

and manual adjustments

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Revenue plans

Cash flow calculation

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~

Deep Dive


Scenario 5 Financial Planning and Forecasting Processes and Integration

• TRM deals

• Vendor open Items (including Down payment requests)

• Purchase requisitions, Purchase orders

• Revenue plan and forecast


Integration with:

Financial Planning and Forecasting Analytics

Deep Dive


Scenario 5 Financial Planning and Forecasting Financial Planning and Forecasting. Extensions

Key features:

• Financial Planning and Forecasting


o prerequisite – purchase requisitions, purchase orders,

vendor open items (including down payment requests)

and financial transactions has been created

o restrictions for actual and plan certainty levels must be

added in T811FLAGS table

o plan data is retrieved from FQM_FLOW table

o revenue cash flow is calculated via planning function

using Liquidity item attribute value from G/L Account

Primary objects:


o MC4Finance: Revenue cash flows /MLC/FINA0

o MC4Finance: Financial Plan data /MLC/FINA2



o MC4Finance: Plan and actual financial data /MLC/FINC2

o MC4Finance: Revenue cash flows /MLC/FINC8


o ZMLC_FINCLCASHFLOW

Deep Dive


Scenario 5 Financial Planning and Forecasting Financial Planning and Forecasting. Extensions

Deep Dive

Scenario 6

P&L Planning and Forecasting


Scenario 6 P&L Planning and ForecastingProcesses and Values

• Since data has planned in S4 system or via BPC input forms, P&L budget displays functional budgets data on the fly. P&L values must be equal to the

revenues and expenses from functional budgets:

• Revenue Planning on Periods: Market Segment

• Revenue Planning on Periods: Profit Center

• Revenue Planning on Periods: Sales

• Cost Center Planning on Periods

• Production Cost Planning on Periods

• G&A Cost Planning on Periods

• Treasury Planning on Periods

• Purchase Planning on Periods (in case of Services)



Analytical reports:

• P&L Plan On Periods

• P&L Forecast On Periods


Deep Dive


Scenario 6 P&L Planning and ForecastingBenefits and Capabilities

Ensure unified Profit and Loss Plan as result of previous planning processes

Revenue plans

Cost center plans

Treasury plan

Purchase plan (only Services)~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

~~

Deep Dive


Scenario 6 P&L Planning and ForecastingProcesses and Integration

• Revenue Planning and Forecasting


• Purchasing Planning and Forecasting

• Financial Deals Planning and Forecasting

Integration with:






Best Practice:

Deep Dive


Scenario 6 P&L Planning and ForecastingP&L Planning and Forecasting. Extensions

Key features:


o reporting on fly

o actual data are from ACDOCA

o plan data are from functional budgets (Revenue Planning,

Cost Center Planning, Treasury Planning, Purchase

Planning)

Primary objects:


o MC4Finance: Cost Center Plan /MLC/FINA1


o MC4Finance: G&A and Production cost Plan data

/MLC/FINA7

o MC4Finance: TRM plan data /MLC/FINA8



o MC4Finance: P&L /MLC/FINC6


o FCO_C_IBP_ACDOCA

Deep Dive


Scenario 6 P&L Planning and ForecastingP&L Planning and Forecasting. Extensions

Deep Dive

Scenario 7

Balance Sheet Planning and Forecasting


Scenario 7 Balance Sheet Planning and ForecastingProcesses and Values

• The Balance sheet planning is done manually – in the same way as it is in standard IBPF content. Planning is based on the actuals of the past year, data

copied into the selected plan version, and then can be adjusted.

• Once the data collected in company code currency, it will be executed through the currency translation process in order to generate group currency figures.

• Forecasting process is based on copying plan data.



• Plan Company


• Forecast Company


Deep Dive


Scenario 7 Balance Sheet Planning and ForecastingPlanning form

Ensure standard planning form for Balance sheet on Periods

Manual planningCalculated dataS4/HANA Data (ACDOCA) Calculated data

Deep Dive


Scenario 7 Balance Sheet Planning and ForecastingProcesses and Integration

Integration with:






Best Practice:

Deep Dive


Scenario 7 Balance Sheet Planning and ForecastingBalance Sheet Planning and Forecasting. Extensions

Key features:

• Balance Sheet Planning and Forecasting

o manual planning

o actual data are from ACDOCA

Primary objects:


o MC4Finance: Balance Sheet Plan data /MLC/FINA4


o MC4Finance: Plan and actual balance sheet

/MLC/FINC7


o FCO_C_IBP_ACDOCA

Deep Dive


Scenario 7 Balance Sheet Planning and ForecastingBalance Sheet Planning and Forecasting. Extensions

Deep Dive

Scope summary


SAP Model Company for Finance: Scope summary

Functional Scope Assets

1. Business Blueprint

2. TestScript

3. Configuration Guide

71CUSTOMER© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀInternal© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Thank you.

Contact information:

F name L name

Title

Address

Phone number

Documents

Deep Dive Workshop MC4F - Model Company for Finance Scope … · 2020. 8. 21. · Intercompany) Source Application Treasury For Treasury and Risk Management we use: Flow Type, Product