BBP Fi Mci VW V1.3

Project Sunrise
________________________________________________________________________________
`1``
Business Blue Print

Molson Coors International, India SAP
Implementation – Project Sunrise
Module: Finance
March 31, 2019
STATEMENT OF CONFIDENTIALITY / DISCLAIMER

This document is the property of Vital Wires Consulting Pvt.
Vital Wires Consulting Pvt. Ltd. Ltd. and is produced in response to your request. No part of
301 Palm Court Building, MG Road, this document shall be reproduced, stored in a retrieval
Sector 16, Gurugram system, or transmitted by any means, electronic, mechanical,
PO Box: 122001, Haryana, India. photocopying, recording, or otherwise, to parties outside of
Tel: +91124-4958460 your organization without prior written permission from Vital
www.vitalwires.com Wires
Vital Wires Confidential 1

Project Sunrise
________________________________________________________________________________
Contents
Document History................................................................................................................................9
Introduction........................................................................................................................................10
Implementation Team........................................................................................................................11
Sign-off (Approval) for this document:.............................................................................................11
Glossary..............................................................................................................................................13
Flow Chart Legend.........................................................................................................................13
Color Legend..............................................................................................................................13
Shape legend..............................................................................................................................13
Text Legend....................................................................................................................................13
Finance– Organization Structure........................................................................................................14
Business Case.................................................................................................................................14
AS IS Process.................................................................................................................................14
Core To-Be Process........................................................................................................................14
Organization elements involved.................................................................................................14
Operating Concern.........................................................................................................................14
Controlling Area.............................................................................................................................15
Company........................................................................................................................................15
Company Code (BRD ID: 1.1, 1.2)................................................................................................15
Profit center Accounting (BRD ID: 40.1)......................................................................................16
..........................................................................................................................16
Profit center assignment.................................................................................................................16
xSAP Code.................................................................................................................................17
Open points................................................................................................................................17
System Controls.........................................................................................................................17
RICEF.............................................................................................................................................17
Gaps................................................................................................................................................17
System Configuration Considerations........................................................................................17
File Conversion Considerations.................................................................................................17
Any Reports required related to current business process.........................................................17
Any Document / Output would be printed for this business process.........................................17
Project Sunrise
________________________________________________________________________________
Integration aspects......................................................................................................................18
 Logistics, Finance activities are get integrated.......................................................................18
Authorization Considerations.....................................................................................................18
Finance– Master Data.........................................................................................................................18
AS IS Process.................................................................................................................................18
General ledger (BRD ID: 6)...........................................................................................................19
General Ledger Account Group.....................................................................................................19
General ledger master.....................................................................................................................19
Number ranges...........................................................................................................................21
Open points................................................................................................................................22
System Controls.........................................................................................................................22
System Configuration Considerations............................................................................................22
Bank Master...................................................................................................................................22
Number ranges...........................................................................................................................23
Open points................................................................................................................................23
System Controls.........................................................................................................................23
Asset master...................................................................................................................................23
Number ranges...........................................................................................................................24
Open points................................................................................................................................24
System Controls.........................................................................................................................24

Project Sunrise
________________________________________________________________________________
Profit Center...................................................................................................................................24
Number ranges...........................................................................................................................25
Open points................................................................................................................................25
System Controls.........................................................................................................................25
Tax master Data.............................................................................................................................25
Number ranges...........................................................................................................................25
Open points................................................................................................................................26
System Controls.........................................................................................................................26
Finance – Business Processes............................................................................................................26
Finance: Global settings.....................................................................................................................26
Special Purpose Ledger (BRD ID: 41.1)........................................................................................26
Currencies (BRD ID: 39.1)............................................................................................................27
Company Code Currency...............................................................................................................27
Exchange Rate (BRD ID: 39.1)......................................................................................................28
Fiscal Year Variant (BRD ID: 39.1)..............................................................................................28
Field Status Variant........................................................................................................................28
Posting Period Variant...................................................................................................................31
Account types.................................................................................................................................31
Document Types............................................................................................................................32
Posting Keys...................................................................................................................................34
Chart of Accounts...........................................................................................................................35
As-Is...............................................................................................................................................35

Project Sunrise
________________________________________________________________________________
Definition of Chart of Accounts.....................................................................................................35
Group Chart of Accounts...............................................................................................................35
Operating Chart of Accounts..........................................................................................................36
Interface/Development Requirements........................................................................................36
System Controls.........................................................................................................................36
Finance: General Ledger Accounting (BRD ID: 42.1)......................................................................37
As-Is Process..................................................................................................................................37
Recurring Entry..............................................................................................................................37
Provisional JV Entry......................................................................................................................38
Finance –General Ledger Account Clearing Process.........................................................................39
AS IS Process.................................................................................................................................39
TO BE Process...............................................................................................................................39
Accounting entries..........................................................................................................................39
Finance-Foreign Currency Revaluation.............................................................................................40
AS IS Process.................................................................................................................................40
TO BE Process...............................................................................................................................41
System Controls.........................................................................................................................41
Finance-Accounts payable (BRD ID: 43.1).......................................................................................43
Vendor Advance Payment Processing...........................................................................................43
AS IS Process.................................................................................................................................43
TO BE Process (BRD ID: 43.2).....................................................................................................43
Accounting Entries.........................................................................................................................44
Finance: Accounts Payable (BRD ID: 43.1)......................................................................................45
Invoice receipt................................................................................................................................45
AS IS Process.................................................................................................................................45
TO BE Process...............................................................................................................................45
Credit Note (BRD ID: 43.5)...........................................................................................................46

Project Sunrise
________________________________________________________________________________
Finance- Accounts Payable (BRD ID: 43.3)......................................................................................48
Vendor Payments...........................................................................................................................48
AS IS Process.................................................................................................................................48
TO BE Process...............................................................................................................................48
Payment Methods (BRD ID: 43.4).................................................................................................50
Ranking Order (BRD ID: 45.1)......................................................................................................50
System Controls.........................................................................................................................51
Finance – Bank and Cash Accounting (BRD ID: 46.1).....................................................................52
AS IS Process.................................................................................................................................52
TO BE Process...............................................................................................................................52
Petty Cash Accounting (BRD ID: 46.1).........................................................................................53
AS IS Process.................................................................................................................................53
TO BE Process...........................................................................................................................53
Accounting Entry...........................................................................................................................54
Cash Management (BRD ID: 51.1)................................................................................................54
Finance – Bank Reconciliation (BRD ID: 45.3)................................................................................56
AS IS Process.................................................................................................................................56
TO BE Process...........................................................................................................................56
Electronic Bank Reconciliation......................................................................................................56
Manual Bank Reconciliation..........................................................................................................57
Post Processing...............................................................................................................................58
Finance-Taxes on Purchase and Sale (BRD ID: 48.1).......................................................................59
AS IS Process.................................................................................................................................60
TO BE Process...............................................................................................................................60
Tax Procedure (BRD ID: 48.1)......................................................................................................60
Tax Codes.......................................................................................................................................60
Region Code...................................................................................................................................61
TDS / With-holding Taxes (BRD ID: 48.2)...................................................................................61
Withholding Tax Internal Challan and payment to bank...............................................................62
Withholding tax returns (BRD ID: 48.4).......................................................................................63

Project Sunrise
________________________________________________________________________________
Tax collected at source (BRD ID: 48.2).........................................................................................63
Finance –Asset Organization Structure (BRD ID: 47.1)....................................................................65
AS IS Process.................................................................................................................................66
TO BE Process...............................................................................................................................66
Chart of depreciation......................................................................................................................66
Asset Class.....................................................................................................................................66
Depreciation areas (BRD ID: 47.4)................................................................................................67
System Controls.........................................................................................................................67
Finance –Asset Transaction Process..................................................................................................68
Asset Procurement (BRD ID: 47.3)...............................................................................................69
AS IS Process.................................................................................................................................69
TO BE Process...............................................................................................................................69
Asset Retirement(BRD ID: 47.6)...................................................................................................70
Sale of Fixed Assets.......................................................................................................................70
AS IS Process.................................................................................................................................70
To-Be Process................................................................................................................................70
Asset Write off...............................................................................................................................71
AS IS Process.................................................................................................................................71
To-Be Process................................................................................................................................71
Transfer of Assets(BRD ID: 47.5).................................................................................................71
AS IS Process.................................................................................................................................71
To-Be Process................................................................................................................................71
By changing the Cost center and location details in Asset master data.........................................72
Finance –Depreciation of Assets(BRD ID: 47.4)...............................................................................74
AS IS Process.................................................................................................................................74
TO BE Process...............................................................................................................................74

Project Sunrise
________________________________________________________________________________
Finance-Account Receivable (BRD ID: 44.1)...................................................................................76
AS IS Process.................................................................................................................................77
TO BE Process...............................................................................................................................77
Customer Down payment (BRD ID: 44.2).....................................................................................77
Credit Note (BRD ID: 44.5)...........................................................................................................78
Incoming Payment (BRD ID: 44.4)...............................................................................................78
Manual Clearing.............................................................................................................................79
Finance-Automatic Account Determination (BRD ID: 44.2)............................................................80
AS IS Process.................................................................................................................................80
TO BE Process...............................................................................................................................80
Valuation Grouping Code..............................................................................................................81
Valuation Class..............................................................................................................................82
Account modifier............................................................................................................................82
Account receivable.........................................................................................................................82

Project Sunrise
________________________________________________________________________________
Document History
Version Release Date Author Reviewed By Change Description /
Comment
1.0 Kanishk Sujit Suman Initial Draft

Kashyap
1.1 Kanishk Sujit Suman Revised version after review

Kashyap on 26/04/2019
1.2 Kanishk Sujit Suman Revised version after BBP

Kashyap discussion on 02/05/2019
1.3 Kanishk Sujit Suman Revised version after BBP

Kashyap discussion on 02/06/2019

Project Sunrise
________________________________________________________________________________
Introduction
This document contains the proposed blueprint for the SAP Implementation at Molson Coors
International, India; it outlines all the major processes associated within the scope of the
implementation project. The intent of the document is to define the to-be model for some of the
process that have been covered as part of the as-is study conducted during the knowledge
gathering phase.
If there are any functional elements or sub components which are incidental and critical to the
business scenarios of Molson Coors International, India and which is not reflected in this blue print
document, it shall later be added as version changes to this document provided these
changes/functional elements are within the processes mentioned in the original blueprint
document. Those changes will be incorporated if identified by the end of completion of unit testing
phase.
If the changes are identified after the unit testing phase, these would be taken up with the Steering
Committee and evaluated there and will not get included automatically. Please also note that if
there are any additional efforts required to incorporate any such changes that affects the project
timelines or which is outside the scope of the project, the same needs to be mutually discussed
and agreed upon as per the Change Order Terms and Conditions.
This document also highlights the Organization structure that would be mapped to the SAP
system.
The entire document establishes the format for the final blueprint, which would be subjected to
audit by the business representatives for their assessment and approval.
The document is a collaborative effort between the implementation team, business team and the
core team. The document also represents the agreement of the core team to the proposed
processes in individual modules of the project and also of the deviations, where an agreement
needs to reach on the process change.
The process of arriving at the blueprint is as below:
Arrive at “AS-IS” process.
Propose “TO-BE” process, these would either be the Core Business Model (CBM) itself or would
be a deviation from CBM.

Project Sunrise
________________________________________________________________________________
Implementation Team
Name Role Module Organization
Sachin Selot Chief Financial Officer SAP Business Lead MCI India
Trent Krause Head of IT - MCI SAP Project Head MCBC IT
Ramendra Choudhary IT Business Partner SAP Project Lead MCBC IT
Deepak Jammula Tech Lead SAP Tech Lead MCBC IT
Serge Nimmegeers Solution Architect Solution Architect MCBC IT
Nathalie Gendron SAP FICO Lead SAP FICO MCBC IT
George Puscu SAP MM/PP Lead SAP MM/PP MCBC IT
Mihail Dinu Project Manager Project Manager MCBC IT
Dragos Zvincu BI Reporting Lead Reporting Lead MCBC IT
Amit Saini (CC) Core Team Member Finance (FI) MCI India
Manoj Jha Core Team Member Controlling (CO) MCI India
Gordon D’Souza Key User Finance (FI) MCI India
Vivek Sinha Core Team Member Controlling (CO) MCI India
Digvijay Yadav Core Team Member MM & PP MCI India
Manish Saxena Core Team Member Sales & Distribution MCI India
Yogesh Sahni Key User Finance (Brewery) MCI India
Chandershekhar Sawant Key User SAP MM MCI India
Barinder Singh Rana Key User SAP MM (Brewery) MCI India
Shakti Yadav Key User SAP MM (Brewery) MCI India
PK Rajiv Key User SAP FI SD MCI India
Balwinder Sidhu Key User SAP MM (Stores) MCI India
Sujit Suman Project Manager SAP Vital Wires

Arminder Singh Consultant MM Vital Wires
Kanishk Kashyap Consultant FICO Vital Wires
Kamlesh Arya Consultant SD Vital Wires
Sign-off (Approval) for this document:

Name of Team Member Organization / Role Signatures
Paul D'Silva CEO - Molson Coors India
Jeanne Kate Snr. Director Supply Chain APACA
Daniel Story Finance Director, APACA
Gary Froehlich Hd of Global G&A Sourcg & Proc Dev
Sachin Selot Chief Financial Officer - MCI India

Project Sunrise
________________________________________________________________________________
Trent Krause Head of IT - MolsonCoors International
Ramendra Choudhary IT Business Partner - India
Amit Saini (CC) DGM - Finance
Manoj Jha Sr. Manager - Finance
Digvijay Yadav Manager - Supply Chain
Chander Shekhar Sawant Sr. Manager - Logistics and Procurement
Vivek Sinha Sr. Manager - Finance
Manish Saxena Manager - Sales
Deepak Jammula Tech Lead

Project Sunrise
________________________________________________________________________________
Glossary
Flow Chart Legend
Color Legend
SAP foreground SAP background SAP Sub process-

Non SAP process
proces process mandatory
SAP Sub process

optional
Shape legend
Start/End
Decision Document Process
event
Sub -Process
Text Legend
Short Form Full Form
FI Finance
CO Controlling
PO Purchase order
GL General ledger
GR Goods receipt
GI Goods issue
IR Invoice receipt
IV Invoice verification

Project Sunrise
________________________________________________________________________________
Finance– Organization Structure
TO-BE Document For SAP Implementation at Molson Coors India
Name of Business Process: Organization Structure

Module: Finance Sub module: Organization Structure
Version Management: This Document is subject to change control. Every change of the document has to
Undergo change control procedure and has to be registered in the following table
Version Change Prepared By Date
1 Initial Kanishk Kashyap 31.03.2019
Business Case
AS IS Process
Molson Coors India head office is located in New Delhi (HO), It is having one corporate Finance department
in HO and each in manufacturing Plant .
There are two legal entities two in MCI India. Molson Coors India Pvt. Ltd and Molson Coors Cobra India
Pvt. Ltd.
Core To-Be Process

In SAP, the organization structure of MCI India is framed with the SAP defined
Organizational units. The organization structure is the basic skeleton frame in SAP which
structures the company, Organizational units, and all other departments essential in running
the business. The following organizational elements are used
 Operating Concern
 Controlling Area
 Company
 Company Code
 Business area
Organization elements involved

Operating Concern
An operating concern is the highest organizational unit in the Controlling module. It is commonly
used for profitability analysis of products and regions. It is the valuation level for Profitability
Analysis (CO-PA).
Company Description
1000 Molson Coors Brewing Co.

Project Sunrise
________________________________________________________________________________
Controlling Area
Controlling area is an organizational unit, used to represent for cost accounting purposes. A controlling
area may include single or multiple company codes that may use different currencies. These company
codes must use the same operative chart of accounts. (Detailed information included in CO BBP)
Company Description
1000 Molson Coors Brewing Co.
Company
Company means an organizational unit in SAP Basic data such as company ID, name& address, language &
currency are stored under the definition of company. Group Accounting is possible at Company Level.
All company codes for a company must work with the same operational chart of accounts and
fiscal year. The currencies used can be different.
In order to facilitate the intercompany transactions via trading partner, all the below entities would
be created as companies.
Company Description
3565 Molson Coors Cobra India Private Limited
3566 Molson Coors India Private Ltd
Company Code (BRD ID: 1.1, 1.2)

Definition: The company code is the smallest organizational unit of external accounting in which a
complete financial accounting can be created. All events that affect the company code and the
creation of all financial statements, like balance sheet, profit and loss are calculated at the
company code organizational unit level.
Company Code Description


Project Sunrise
________________________________________________________________________________
Profit center Accounting (BRD ID: 40.1)

SAP Profit center accounting provides the information of an organization’s profit and loss. The method which
can be utilized for profit center accounting is period accounting. Profit centers can be set-up to identify
product lines, divisions, geographical regions, offices, production sites or by functions.
Profit center Accounting helps to determine profits and losses by profit center using either period accounting
or the cost-of-sales approach. All profit-relevant business transactions are updated in the profit centre
hierarchy according to G/L account at the same time they are processed in the original module of the SAP.
This ensures that the entire flow of goods and services within a company are aligned to profit centres
The SAP profit center accounting allows an organization to route all profitability and balance sheet related
information to a profit center.
For MCI India all manufacturing units, head office, Depot/marketing office will be created as profit centers.
MCI India requires to generate plant wise trial balance that will be fulfilled by profit center accounting.
Profit center for MCI India company code will be assigned to Molson coors standard profit centre hierarchy
that is also assigned to the existing controlling area 1000.
Profit center assignment
These assignments automatically transfers the data to Profit center accounting when it is posted to the
original object.
Revenues and cost of good sold - through assignment of sales document items to profit centre
Direct costs - through assignment of process orders and cost centres.
Profit centre is assigned to material and asset master.
Overhead costs - through assignment of account assignment objects from Overhead Cost Controlling (cost
centers, orders etc.)
Profit and loss statement by profit centre

Data that can be transferred to Profit Center Accounting
All postings affecting revenue and cost elements
 P&L postings directly posted to a cost/profit center
 P&L accounts maintained with automatic account assignment in PCA customizing
Project Sunrise
________________________________________________________________________________
 P&L accounts related to transactions in Logistics.
 The data is posted to other objects and passed on from there to a profit center in Profit Center
Accounting. This makes it possible to display the company’s results by profit center based on the
original postings.
Balance sheet by profit center

 Balance sheet items like AR/AP materials , assets can be analysed by profit centre .
 Other Balance Sheet accounts can be maintained with automatic account assignment in PCA
customizing.
 Balance sheet items can be transferred periodically or online in real time.
 AR/AP balance are PCA Periodically as month end process
 Other balance sheet items can be transferred in Real time.
xSAP Code
SAP Code of Org structure has been finalized with business but final Code for Organization
structure will be approved by Global Master Data Team,
Open points
Business area concept is not used in MCBC landscape. Business owner to decide if it can be used in
MCI India
System Controls
RICEF
None
Gaps
None
System Configuration Considerations

 Define Business Area
 Assign Business Area to Plants
File Conversion Considerations

None
Any Reports required related to current business process

None
Any Document / Output would be printed for this business process

None

Project Sunrise
________________________________________________________________________________
Integration aspects
 Company code assigned to existing controlling area.
 Logistics, Finance activities are get integrated
Authorization Considerations
Will be finalized and handled during realization phase
Finance– Master Data

Name of Business Process: Master Data
Module: Finance Sub module: Master Data
AS IS Process
Various masters are used by the MCIPL. These masters are available in various formats. All masters are
maintained either in system or as soft copy in MS Excel files.
 General ledger master: Approved General Ledger accounts are created by HO finance and plant
team respectively. Nearly 250 General Ledger accounts are available.
 Bank Master: In MCIPL, bank master gets created by finance Team in IBMS system and is used for
payments.
 Asset master: In MCIPL, asset creation process is decentralized and maintained in IBMS system by
HO and respective plant teams.
 Tax master: Tax master are maintained by Finance team in IBMS
Core To-Be Process

Successful functioning of SAP are dependent on the most important part i.e. Master Data . SAP FI broadly
master data is classified under
 General ledger master

 Bank Master
 Asset master
 Tax code master
 Profit Center

Project Sunrise
________________________________________________________________________________
General ledger (BRD ID: 6)

General Ledger Account Group
The account group is a classifying feature within the records. Account Group determines the
fields for the data entry while creating or changing a Master record in company code specific
area.
Account groups Control the field status at the time of creation of Master data and checks
whether the General Ledger account number is in the range given for that group.
Existing account groups will be used in MCI India.
Account Description From TO

Group
A100 Cash & Bank 1000000 1050399
A110 Trade Accounts Receivable 1100000 1109999
A112 Non-Trade Receivables 1120000 1158999
A120 Inventory 1200000 1249999
A130 Prepaid & Current Asset 1300000 1499999
A150 Capital Assets 1500000 1719999
A175 Other Long-term Assets 1750000 1999999
B200 Trade Accounts Payable 2000000 2059999
B210 Accrued Salaries and Related E 2100000 2129999
B220 Accrued Expenses 2200000 2209999
B222 Other Payables 2210000 2499999
B250 Bank Indebtedness 2500000 2659999
B270 Taxes 2700000 2719999
B272 Long Term Liabilities 2720000 2789999
C279 Equity 2790000 2899999
D300 Revenue 3000000 3099999
D310 Revenue Deductions 3100000 3929999
E400 Costs and Expenses 4000000 7999999
F800 Secondary cost elements 8000000 8999999
G900 Other Income and Expense 9000000 9999999
SAKO General Ledger Accounts 1000000 9999999
Z100 Recon.account ready for input 9999999
Z999 Special Accounts Z000000 ZZZZZZZ
ZMOL Molson Canada 100000 Z99999
General ledger master

G/L account master records contain the data that is always needed by the General Ledger to determine the
account's function. The G/L account master records control the posting of accounting transactions to G/L
accounts and the processing of the posting data.
Each general ledger account within the operating COA has two views i.e., Chart of account
view and Company code view

Project Sunrise
________________________________________________________________________________
Chart of accounts view – This view is shared by all company codes. Any changes to this view will
impact all company codes within chart of accounts.
This view contains the basic information:

 Description of the general ledger account maintained in multiple languages
 Nature of the account (balance sheet vs. profit and loss account)
 Group account number
Company code view – This view is specific to the individual company code for which the general
ledger is maintained. Any changes to this view will not affect other company codes. However, to
standardize the subsequent accounting processes across different company codes, MCI India
should maintain strict internal controls over the general ledger account maintenance process.
General Ledger code can be created with reference to existing Company code General Ledger
information, if the data is same.
Currency
The account currency indicates the currency in which this account is held. All accounts are defaulted by
company code currency. During Creation User can manually change the currency.
If a currency other than the company code currency is specified, users can only post items in that
currency to this account.
Bank/cash accounts usually need to be managed in the bank account currency. If the GL currency and
company code currency are same, then foreign currency transactions can be posted to this account. If
they are different only the General Ledger currency transactions can be posted.
Only Manage Balances in Local Currency

Indicates that balances are updated only in local currency when users post item to this account. This indicator
has to be set for accounts in which we do not want the system to update transaction figures separately by
currency. Set the indicator in cash discount clearing accounts and GR/IR clearing
Open item management

Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of
these accounts is always equal to the balance of the open items. Postings to these accounts represent
incomplete transactions.
Examples of accounts that are managed on an open item basis include: Clearing
accounts:

Project Sunrise
________________________________________________________________________________
 Bank clearing account
 Payroll clearing account
 Cash discount clearing account
 GR/IR clearing account
Open Item Managed accounts need to be maintained on a periodic basis failing which the system
performance decreases over the usage of the system. Usually this is part of the period end process.
Accounts that are not managed on an open item basis:
 Main Bank accounts.
 Reconciliation accounts (These are managed implicitly using the sub ledger
open item function).
 Profit and loss accounts.
 Materials Management (MM) accounts posted with a posting key that has
account type 'M'
Line item display
If a G/L account is set the "Line item display" indicator in the master record for an account, all line items that
have been posted to this account are displayed if they have not been archived.
Field status group
You use this field to define which fields are displayed when you post accounting transactions to a G/L
account. A field may have one of the following statuses:
 Hidden (suppressed)
 Entry required (required field)
 Ready for input (optional field)
Reconciliation account
You use this field to indicate G/L accounts as being reconciliation accounts. For each sub ledger account,
there must be at least one reconciliation account in the general ledger. When we post to an account in the
sub ledger, the system automatically posts to the corresponding reconciliation account. Using the
reconciliation account procedure, it is possible to view trial balance at any time, since the amounts posted
to sub ledger accounts are also posted automatically in the general ledger.
 Sub-ledger integration information – such as asset account, customer account,

vendor account
For MCI India, business will share finalized list of GL account.
Changes to existing organization

Centralized master data team will be maintain the GL account master data.
Number ranges
Number ranges assigned to existing account group will be used.

Project Sunrise
________________________________________________________________________________
Open points
Business team to share finalized list of GLs.
System Controls
All company codes will have unified accounting structure.
WRICEF/GAPS
GL upload template
GL Accounts will be created

Need to evaluate existing upload program

None
Integration aspects
All company codes will have unified accounting structure
Will be handled during realization phase
Bank Master
House bank is the bank with which a company code maintains a bank account. The bank is defined
in the system under a house bank key. The individual accounts within the bank are maintained as
house banks. For each bank account, a separate GL account is created in the system. The bank
details are stored in house bank which are required for printing payment forms.
Bank keys contain the details of house bank. These can be used as a key wherever required. It is not
required to enter bank details manually.
Payments and receipts through Bank are made by Cheque and Transfers. Vendor payment process
and Customer receipt process will be handled as mentioned in Accounts Receivable and Payables
documents respectively.
Account ID Every account at a house bank is represented by an account ID.
In SAP three different GL accounts are to be maintained for a single bank account. These accounts
are the main bank account, the incoming bank accounts and the outgoing bank accounts.
Every bank account will be identified by a combination of a House Bank (Determines the Bank) and an
Account ID (Determines the Account maintained with the bank).
MCI India has account in 7 banks but only two are used for transaction
 Bank of America
 State Bank of India(For duty payments)

Centralized master data team will be maintain the bank master data.

Project Sunrise
________________________________________________________________________________
Number ranges
None
Open points
System Controls
All company codes will have unified accounting structure.
WRICEF/GAPS
Bank upload template
Bank master will be created.


None
Integration aspects
Asset master
The Asset master record contains all information related to an Asset that remains unchanged over a long
period. There are two major categories of information that can be stored on an Asset master data:
a) General master data:

 General information (description, quantity, and so on)
 Account assignment information
Posting information (such as, capitalization date)

Time-dependent assignments (such as, cost center)
Information on the origin of the Asset
Physical inventory data
b) Data for calculating Asset value:

 Depreciation key
 Useful life
 Ordinary depreciation starts
The Asset master numbering assignment by Asset class is company code dependent. In other words, each
company will have its own independent number range per each Asset class’s numbering assignment.
The Asset main number represents an Asset that is to be evaluated independently. The Asset is viewed as a
single unit for evaluation. It contains information for the valuation of the Asset, as well as organizational
information.

Project Sunrise
________________________________________________________________________________
There are two ways to create an Asset master:
a) Create an Asset by using the Asset class, so that default values from the Asset class will be taken over to
the new Asset master
b) Create and Asset by “copying” an existing Asset, so that values from the existing Asset will be taken over
to the new Asset master

Centralized master data team will be maintain the Asset master data.
Number ranges
Existing asset class and assigned number will be used.
Open points
Business team to share finalized list of Asset master.
System Controls
All Asset masters are created in SAP
WRICEF/GAPS
Asset upload template

Asset master will be created.

None
Integration aspects
Finance and Assets ledgers will be integrated by asset classes
Profit Center
A profit center is a management oriented organizational unit used for internal controlling purposes. Dividing
company up into profit centers allows to analyze areas of responsibility and to delegate responsibility to
decentralized units, thus treating them as “companies within the company”.
The essential difference between a profit center and a business area is that profit centers are used for
internal control, while business areas are more geared toward an external viewpoint.
The master data of a profit center includes the name of the profit center, the controlling area it is assigned to,
and the profit center’s period of validity, as well as information about the person responsible for the profit
center, the profit center’s assignment to a node of the standard hierarchy, and data required for
communication (address, telephone number and so on).

Project Sunrise
________________________________________________________________________________

 Centralized master data team will maintain the master data.
Number ranges
To be finalized at realization phase.
Open points
System Controls
Controlling and Finance activities are get integrated.
WRICEF/GAPS
 Profit center will be assigned to existing standard hierarchy.

None

None
Integration aspects
Controlling and finance will get integrated
Will be handled during realization phase.
Tax master Data

Tax code are two digit alphanumeric that represents a tax category which must be taken into consideration
when making a tax return to the tax authorities. Tax codes are unique per country.
The tax rate calculation rules and further features are stored in a table for each tax code. For tax-exempt or
non-taxable transactions, we use tax codes with a 0 percentage rate if the corresponding transactions are
to be displayed in the tax returns.
 Tax code is specified to:

 Check the associated transaction is related input or output tax.
 Check if a tax account with tax type (input or output tax) can be posted to
 Check the tax on revenue amount in the document
 Calculate the amount of tax on sales automatically on request
 Determine the tax account

Centralized master data team will be maintain the Tax master data.
Number ranges
None

Project Sunrise
________________________________________________________________________________
Open points
Business team to share finalized list of Tax master
System Controls
All Tax master are created in SAP
WRICEF/GAPS
Evaluate existing tax upload template
Tax master will be created.

None
Integration aspects
None
Finance – Business Processes

Finance: Global settings
Name of Business Process: FI – Global Settings
Module: Finance Sub module: Global Settings
Special Purpose Ledger (BRD ID: 41.1)

In the application Special Purpose Ledger we can define ledgers for reporting purposes. The special purpose
ledgers enables to report at various levels using the values from the various application components. The
functions available in the special purpose ledgers enable to collect and combine information, create and
modify totals, and distribute actual values.
For MCI India special purpose ledger will be used to maintain separate ledger to meet fiscal year followed in
India that is April-March.

Project Sunrise
________________________________________________________________________________
Currencies (BRD ID: 39.1)
The Currencies for MCI India company codes will be as below.
Company Description Country Local Parallel

Code Currency Currency
3565 Molson Coors Cobra India Private IN INR USD
Limited.
3566 Molson Coors India Private Ltd. IN INR USD
Company Code Currency

Company code currency is referred to the local currency with which the company is dealing
with. Any financial transactions posted in currencies other than local currency is automatically
converted to local currency. The currency used for any posting will be called as the
“Transaction Currency”
The financial statements for the company code can be taken at company code currency.
Set Decimal Places for Currencies

In the SAP System tables currency fields are stored as decimal figures with a variable number
of decimal places. The decimal point is not stored in the field in the database. Instead, each
currency field refers to a currency key field. In transaction you assign the number of decimal
places to this currency key uniquely.
For Currencies INR, USD SAP standard decimal is 2 places.
Group Currency
This currency is used for viewing the Trial Balance and Profit or Loss Account at parallel
currency-1 or group currency. Each company codes can have different local currencies. The
transactions posted in these company codes are automatically converted to its group currency
assigned.
For MCI India , it’s discussed and finalized that group currency will be converted based on local
currency and not based on document currency.
Client currency is defined as Group currency.
Group currency is tagged to company code as Parallel Currency-1.
Hard Currency
This currency is used for viewing the Trial Balance and Profit or Loss Account at parallel
currency-2 or hard currency. Each company codes can have different local currencies. The
transactions posted in these company codes are automatically converted to its hard currency
assigned.
For MCI India, it’s discussed and finalized that hard currency will be converted based on local
currency and not based on document currency.
Hard currency is defined at country level.

Project Sunrise
________________________________________________________________________________
Exchange Rate (BRD ID: 39.1)
This component enables to manage the exchange rates for each currency pair using Direct or
Indirect quotation method. Direct quotation is where the cost of one unit of foreign currency is
given in units of local currency, whereas indirect quotation is where the cost of one unit of local
currency is given in units of foreign currency. The system will use the monthly average rate
for day to day posting of foreign currency transactions.
Standard Exchange Rate Type “M” will be used for Local Currency, Parallel Currency- 1(Group
Currency) and Parallel Currency-2 (Hard Currency)
In case of foreign currency revaluation a same exchange rate type (Standard rate type-M
average rate) will be used and the corresponding rates are maintained in the table.
MCI India will be using the direct exchange rate method, which will be maintain by Bloomberg
rate and when r. Revaluation of currency will be process on monthly bases and Forex
currency loss/gains will be recorded in financials.
Note: Exchange Rate for Parallel Currency 1 and 2 or Local currency must be maintained
properly otherwise the system look for exchange rate based on posting date, if rate is not
available for the date then its picks the previous rate which is maintained.
Fiscal Year Variant (BRD ID: 39.1)

Fiscal year is the accounting period for which the operating results and balance sheet is drawn
every year. Fiscal year variant is used to define fiscal year. Fiscal year variant is created
at client level. Each company code is assigned to a fiscal year variant.
The MCI India Company codes will use the fiscal year variant which is a calendar year
(January- December) with 1 special posting period.
Special periods represent an extension of the last normal posting period. Special posting
period is used to post year end accounts finalization entries after closure of regular posting
period. When the posting date falls within the last normal posting period, then during
document entry one can specify that the transaction figures be updated separately in one of
the special periods.
MCI India Company codes Year Variant- C4
.
Fiscal year variant Company Code
C4 Molson Coors Cobra India Private Limited
C4 Molson Coors India Private Ltd
Field Status Variant

The field status group determines which fields are ready for input, which is required during
entry, and which are suppressed or displayed during document entry. This specification is
known as the field status. A field status variant contains several field status groups which is
assigned to each company code. Field status groups are defined in the company code-
specific area of each G/L account.
It is self-explanatory from the below table that, the cost center is a required entry while posting
documents using P & L accounts. Plant and Sale order may not be required for all kinds of
postings; hence they can be made option. System will allow the user to post transactions
with/without plant and sale order for that particular GL account.

Project Sunrise
________________________________________________________________________________
Optional
Object Suppress Required Entry entry
Cost center Y
Plant Y
Quantity Y
Sales order Y
Profit Center Y
For MCI India since business area field is required at document level a new field status variant 3566 will be
maintained.
Field Status variant Company Code

Note: Field status groups used for MCI India company codes are few listed below for reference.
They are group used by existing company codes Field. The below Field status groups will
be assigned to the above mentioned Field status variant so that assigned company codes can
use them.
G001 Petty Cash Y016 A/P (Non-Control) - Inter-Company

G002 Cash and Investment Y019 thr LT Liab-Order, PrfCtr 'REQUIRED'
Copy of Z020 w/ Profit Ctr
G003 Accounts Receivable (Control) Y020 'Required'
G004 Accounts Receivable (Non-Control) Y021 Inter-Company Sales Revenue
Copied from G002 w/ TransTpe
G005 Inventory (Non-Control) Z002 'Required'
G006 Inventory (Control) Z004 'Required'
G007 Inventory (Non-Control) Materials Z005 'Required'
G008 Prepaid Expenses Z007 'Required'
G009 Fixed Assets (Control) Z008 Prepaid Expenses (Plant optional)
G010 Fixed Assets Adjustments Z009 'Required'
G011 Accumulated Depreciation Z010 'Required'
G012 Investment in Subsidiary Z011 'Required'
G013 A/R or A/P Advance (Control) Z012 'Required'
G014 Other Non-Current Assets Z014 Copied from G014 w/ TransTpe
Project Sunrise
________________________________________________________________________________
'Required'
Accounts Payable MCI Partner Bank
G015 Accounts Payable (Control) Z015 Option
Accounts Payable Other (Plant
G016 Accounts Payable (Non-Control) Z017 optional)
G017 Accounts Payable Other Z019 Other Long Term Liabilities-Order
Copy of G020 w/ TransactionType
G018 Goods Received Not Invoiced Z020 'Req'
G019 Other Long Term Liabilities Z021 Sales (Non-Control) used w/COPA
G020 Capital/Retained Earnings Z022 Sales - Non Control PA required
Sales (Control used w/COPA
G021 Sales (Non-Control) Z023 assignment)
Production Cost (Non MM
G022 Integrated) Z024 Z_Taxes
Production Cost -Freight(Non MM
G023 Sales (Control) Z025 Intgrtd)
G024 Taxes Z026 Unbilled Shipments
Production Cost (Non MM
G025 Integrated) Z027 Sales (N/C) w/COPA + IO optional
Production Cost (Non MM Int) w/
G026 Production Cost (MM Integrated) Z030 opt. CC
G027 Sales & Margin Z031 'Required'
Prd Cst-Frt(Non MM Intgrtd, cctr
G028 PA Settlement Z032 option)
Production Cost (Non MM (CC & Sales and Marketing COPA
G029 ORDER) Z099 Attributes
G030 Order Settlement ZIO Internal Order
Fixed Assets Construction in
G031 Process ZTES Internal Order not required
Process Order (PP-PI/CO
G033 Integrated)
Fixed Assets (Control)-reconc.
G034 Accts
Prepaid Expenses (Stat IO and Pctr
X008 Rqrd)
Cash and Investment - Inter-
Y002 Company
Y004 I/C A/R (Non Control)
Y008 I/C Prepd & Accr.
Y012 Copy of Z012, PrfCtr 'Required'

Project Sunrise
________________________________________________________________________________
Posting Period Variant
A posting period is a self-contained part of a year. Every business transaction is allocated
to a posting period. The monthly debits and credits of the different business transactions are
accumulated per posting period.
Posting period variant is used to determine periods for which accounts are available for
posting. This is used for closing completed period and open new periods. Posting period
variant is assigned to company code which enables to control opening and closing posting
period. The posting date of financial documents derives the corresponding period. (Period
need not be entered during document posting)
Posting
Period Account From From Fro To To
Variant Types A/c To A/c Period m Period year
3566 + 1 Year 2019 1 2019
3566 A ZZZZZZ 1 2019 1 2019
3566 D ZZZZZZ 1 2019 1 2019
3566 K ZZZZZZ 1 2019 1 2019
3566 M ZZZZZZ 1 2019 1 2019
3566 S ZZZZZZ 1 2019 1 2019
The periods can be opened and closed separately for account types in order to control the
month close activities. We propose to create one posting variant per country, so that
individual legal entities can manage their financial posting periods.
MCI India will use the posting period variants as mentioned below.
Posting period Company Code

Variant
Account types
Account types are used to differentiate the opening and closing of posting period to certain
set of accounts. It plays an important role in period closing by allowing posting only to defined
accounts whereas other accounts can be restricted for posting. It also controls the financial
postings.
Account types in SAP are as below.
Type of Account Description

A Assets accounts
D Customer accounts
K Vendor accounts
M Material accounts
S G/L accounts
Posting period for account type S may be kept open to allow posting to GL Account after
Project Sunrise
________________________________________________________________________________
closure of fiscal year whereas posting to customer and vendor account can be restricted by
closing posting period for account type D and K. In Production Environment, Variant for S will
be further sub-divided into categories like Bank, Revenue accounts etc, based on business
requirement. Different range of GL’s can be opened and closed.
Document Types
The document type is used to differentiate the business transactions to be posted. The
Document Type determines where the document is stored as well as the account type to be
posted, e.g. customer invoice, vendor payments, etc. and controls the document header data of
a financial documents. Document types are defined at the client level and are therefore valid
for all company codes. The standard system is delivered with document types which can be
used, changed, or copied.
For example, document types started with K is for creditors
KZ – for vendor payment

KG – for vendor credit memo
In financial transaction posting, we use posting keys from which these account types are
determined. For this reason we use different posting keys in SAP to post different financial
transactions into a company code.
The document type will determine account types allowed, Number Range, Used for Batch
input process only, Intercompany transactions allowed or not header text is mandatory or
not and posting key will determine the account type for the transaction and the filed status
group
Major controls of document types are:
 The number range of document numbers for posting
 The field status of the header fields “Text” and “Reference Number” of a financial
document.
 Document Type allows you to differentiate between the business transactions to be
posted. The document type tells you what sort of a business transaction it is. This is
useful, for example, when displaying line items for an account.
 It allows you to control how postings are made to account types (vendor,
customer, or G/L accounts). The document type determines the account types to which
postings can be made with that document type.
 For posting customer entry, the document type DA, DR DG and DZ must be used and
not others.
 For posting vendor entry, the document type KA, KR KG and KZ must be used and not
others.
 For posting Asset entry the document type AA and for depreciation AF must be used
and not others.
 Document type ”SA” must be used for manual Journal entry comprises of profit & loss or
Balance sheet and not others.
 Document type “AB” will be used by SAP for Clearing line item and it must be used for
manual posting.
 Bank statement posting Documet type “ZR” will be used.
Number ranges for document types along with any new document types that emanate due to process
authorizations, will be decided during realization phase. Please find below sample template for reference

Project Sunrise
Posting Keys
Posting keys are used to determine the account types permitted for postings. This helps
restricting users to post incorrect business transactions. The posting key also controls the
fields in the line items that are required while posting. The standard posting keys would
be used for MCI India.
Posting Account
Key Description Debit/Credit Type
01 Invoice Debit Customer
02 Reverse credit memo Debit Customer
03 Bank charges Debit Customer
04 Other receivables Debit Customer
05 Outgoing payment Debit Customer
06 Payment difference Debit Customer
07 Other clearing Debit Customer
08 Payment clearing Debit Customer
09 Special G/L debit Debit Customer
11 Credit memo Credit Customer
12 Reverse invoice Credit Customer
13 Reverse charges Credit Customer
14 Other payables Credit Customer
15 Incoming payment Credit Customer
16 Payment difference Credit Customer
17 Other clearing Credit Customer
18 Payment clearing Credit Customer
19 Special G/L credit Credit Customer
21 Credit memo Debit Vendor
22 Reverse invoice Debit Vendor
24 Other receivables Debit Vendor
25 Outgoing payment Debit Vendor
26 Payment difference Debit Vendor
27 Clearing Debit Vendor
28 Payment clearing Debit Vendor
29 Special G/L debit Debit Vendor
31 Invoice Credit Vendor
32 Reverse credit memo Credit Vendor
34 Other payables Credit Vendor
35 Incoming payment Credit Vendor
36 Payment difference Credit Vendor
37 Other clearing Credit Vendor
38 Payment clearing Credit Vendor
39 Special G/L credit Credit Vendor
40 Debit entry Debit G/L account
50 Credit entry Credit G/L account
70 Debit asset Debit Asset
75 Credit asset Credit Asset
Vital Wires Confidential Page 33

Project Sunrise
80 Inventory taking Debit G/L account

81 Costs Debit G/L account
82 Inventory difference Debit G/L account
83 Price difference Debit G/L account
84 Consumption Debit G/L account
85 Change in stock Debit G/L account
86 GR/IR debit Debit G/L account
89 Stock inward movement Debit Material
90 Inventory taking Credit G/L account
91 Costs Credit G/L account
92 Inventory difference Credit G/L account
93 Price difference Credit G/L account
94 Consumption Credit G/L account
95 Change in stock Credit G/L account
96 GR/IR credit Credit G/L account
99 Stock outward movement Credit Material
Chart of Accounts
As-Is
All the master data such as GL Account, Vendor Account and Customer account are
maintained at company level. (Customer and vendor accounts are created, sub ledger
concept is followed). General Ledger Accounts are six digits and first three digits hold the
group of General Ledger Accounts.
Number of G/L accounts in current System is 250+
Core To-Be Process

Definition of Chart of Accounts
The Chart of Accounts is a classification scheme consisting of a group of general ledger
accounts. A chart of accounts provides a framework for the recording of values, in order to
ensure an orderly rendering of accounting data. The general /L accounts are used by one
or more company codes. For each G/L account, the chart of accounts contains the account
number, the account name and other, technical information.
Chart of accounts must be assigned to each company code. This chart of accounts is the
operative chart of accounts and is used in both financial accounting and cost
accounting.
Group Chart of Accounts

The group chart of accounts contains the G/L accounts that are used by the entire
corporate group. This allows the company to provide reports for the entire corporate group.
The use of group chart of account is not mandatory. Group account is mapped to
operating General Accounts. During posting the operating General Ledger is entered or
determined. Based on the operating general ledger group account is automatically
determined .The trial balance and profit & loss can be viewed based on Group account.

Project Sunrise
It’s decided that Existing Group Chart of accounts will be used MCI India.
Operating Chart of Accounts

The operating chart of account is also known as “chart of accounts”. Each company code
needs to be assigned to an operating chart of accounts for recording the day to day
transactions. Financial Accounting and Controlling use this chart of accounts. Company
codes will be assigned to operating chart of account. In order to handle cross company
code business transactions, it is mandatory that all company codes use the same
operating chart of accounts.
The length of General Ledger Account will be “7”.
New Operating chart of accounts for MCI India will be created-

Operating Chart of Description
Account
MCOA Molson Coors Brewing Company
Once the master is created then existing General Ledger account can’t be changed. To change the
length of General Ledger account it can be done by SAP SLO.
Interface/Development Requirements
None
 Additional local currencies for company code
 Creation of Field Status Group
 Creation of Posting Period Variant and assign to Company code
System Controls
Logistics, Finance activities are get integrated
Number Range
Number range will be finalized at Realization Phase
Open Points
None
Gaps
None

Project Sunrise
Document / Output would be printed for this business process

None
Integration aspects
Logistics, Finance activities will get integrated
Finance: General Ledger Accounting (BRD ID: 42.1)
Name of Business Process: General Ledger accounting
Module: Financial Accounting
Version Management: This Document is subject to change control. Every change of the
document has to Undergo change control procedure and has to be registered in the following
table
Version Change Prepared By Date:
1.0 Initial Document Kanishk Kashyap 31/03/2019
As-Is Process
Approved General Ledger accounts are created by HO and plant team finance team separately in
legacy system. Nearly 250 General Ledger accounts are available.
Core To-Be Process

General Ledger account master records contain the data that is always needed by the General
Ledger to determine the account's function. The General Ledger account master records
control the posting of accounting transactions to General Ledger accounts and the processing of the
posting data. General Ledger Accounts needs to be entered manually by the user at the time of data
entry.
Recurring Entry
The monthly expenses are posted using a recurring entry document .
Recurring entries are business transactions in Financial accounting that are repeated regularly, such as

Project Sunrise
rent, expense off prepaid balances (AMC) etc.
Provisional JV Entry
Accruals/deferrals are part of the income calculation. The function recognizes expenses and revenues
related to the accounting period just ended (such as the last fiscal year).
To reflect expenses and revenues correctly in the balance sheet, they have to be assigned to the correct
accounting period, regardless of when they are due for payment. Expenses and revenues are therefore
accrued /deferred on a specific key date (e.g. end of a fiscal year).
(BRD ID: 42.2)
All Journal vouchers will be booked in SAP through Black Line interface. This includes journal approval
creation and posting.
MCI Business requires predefined approval matrix. Currently in black line user assign document to
checker for approval. For MCI India business team requires user could only assign document to
predefined authority.
Integration with Black Line interface.

GL account groups will be created.
System Control
Number Range
Existing GL account Groups number ranges will be used.
Open Points
Business to share list of GLs
Gaps
None

None
Integration aspects

Project Sunrise
Finance –General Ledger Account Clearing Process

Name of Business Process: General ledger Account Clearing Process
Module: Finance Sub module: Finance
AS IS Process
Manual clearing process is followed in the current system.
TO BE Process
Clearing can be manual or automatic. In case of manual clearing, the user has to select the open debits
and credits. In case of automatic clearing, the system can determine the open debits and credits using
assignment fields for the respective GL accounts.
For general procurement, the landed costs clearing General Ledger like Insurance, Freight, Customs, the
assignment field would be Purchase order number (for both Goods Receipt and Invoice Receipt posting).
The automatic clearing program can clear these two entries automatically.
The above clearing GL accounts cannot be posted manually. They can only be posted through Materials
Management module.
Accounting entries
Goods receipt
Dr. Inventory 1000
Cr. GR/IR Clearing 1000 PO-5400000001
Invoice receipt
Dr. GR/ IR Clearing a/c 1000 PO-5400000001
Cr. Vendor a/c 1000
When the automatic clearing process is carried out system will match the debits and credits in the GR/IR
clearing account using the PO number 5400000001 in the assignment field and clear the above two
entries.
Dr. GR/IR Clearing 1000 PO-5400000001
Cr. GR/IR Clearing 1000 PO-5400000001
None
 Configuration of open item clearing based on assignment field

Project Sunrise
 Number range maintenance for clearing transactions
Number Range
 Number Ranges for document type AB will be decided by configuration team at time of
Realization.
System control
 Only authorized persons can clear the GL transactions
Open Points
None
Gaps
None
None
Document / Output would be printed for this process
None
Integration aspects
Finance-Foreign Currency Revaluation

Name of Business Process: Foreign Currency Revaluation
Module: Finance Sub module:Finance
AS IS Process
Manual clearing process is followed in the current system.
TO BE Process
The exchange rate has to be maintained between currency pairs, before running the forex revaluation
program.

Project Sunrise
The program calculates the difference between the previous and current exchange rate and posts the
entry. The forex revaluation posting is always unrealized; hence the program posts the entries at the last
day of the month and reveres the entry on the 1st day of subsequent month.
Accounting entries
a) When revaluation is done for Accounts Receivable/Accounts Payable transactions (in case of loss)
Dr. Unrealised gain/loss account (P&L)

Cr. Forex revaluation adjustment account (Balance Sheet)
b) When revaluation is done for GL transactions
Dr. Unrealized gain/loss account (P&L)

Cr. Respective balance sheet account (same Balance Sheet account that is revalued)
c) When revaluation is done for Accounts Receivable/Accounts Payable transactions (in case of gain)
Dr. Forex revaluation adjustment account (Balance Sheet)

Cr. Unrealized gain/loss account (P&L)
When revaluation is done for GL transactions

Dr. Respective balance sheet account (same Balance Sheet account that is revalued)
Cr. Unrealized gain/loss account (P&L)
The exact opposite entry would be passed on the first day of subsequent month.
None
 Exchange rate type to derive current exchange rates
 Automatic account determination for exchange gain / loss posting after GL are finalized
System Controls
 Exchange rate will be determined by system.
Number Range
 Standard document type SA will be generated. Number range will be decided by configuration
team at time of Realization.
Open Points
 Any new GL to be maintained for foreign exchange gain/loss will be finalized after complete list of
GL is shared by business.
Gaps
None

Project Sunrise

None
None
Integration aspects
 The exchange gain/loss is calculated by the system
Finance-Accounts payable (BRD ID: 43.1)

Vendor Advance Payment Processing
Name of Business Process: Supplier advance

Project Sunrise
Module: Finance Sub module: Accounts payable
Version Management: This Document is subject to change control. Every change of the document has
to Undergo change control procedure and has to be registered in the following table
AS IS Process
In Molson Coors India amount is payable to the contractors as per the signed contract terms. Such
advance paid is recoverable from running bills on a pro rata basis.
Department head/ commercial head authorize if any advance payment is to be made to vendor.
TO BE Process (BRD ID: 43.2)
Down payment request will be created against PO. Business user will update percentage of advance to
be paid to vendor.
Down payment will be posted by finance user and same will be cleared after posting vendor invoice.
The standard SAP functionality of Special G/L transactions can be used for this scenario. Special GL
transactions are transactions in accounts payable that are displayed separately in the general ledger and
the sub-ledger. This may be necessary for reporting, tracking or for internal control purposes.
During invoice verification system automatically alerts the user if any advance payment exists against the
same vendor. It is possible to extract vendor wise advance payments made.
For advance payment existing special GL indicators will be used.

Project Sunrise
Any postings to this indicator will be recorded in that GL account. When the advance payment is cleared
against vendor invoice, the amount will be transferred from the special GL to the regular reconciliation
account and the liability is automatically cleared.
Special GL
Indicator
A
B
F
I
M
O
V
Accounting Entries
a) Accounting entry for advance payment request (special GL indicator A)
Advance payment request are noted items. No accounting document is generated.

b) Accounting entry during Manual Entry
Dr. Vendor a/c (with Special GL indicator - A)

Cr. Outgoing cheque clearing A/c
c) Accounting entry during Invoice verification
Dr. GR/IR A/c

Cr. Vendor A/c
d) Accounting Entry during clearing advance payment
Dr. Vendor A/c

Cr. Vendor a/c (with special GL indicator - A)
None
None
Number Range
Standard document type KZ will be generated. Number range will be decided by configuration
Open Points
None
Gaps
None
Project Sunrise
None
Vendor payment advice
Integration aspects
 Amount posted to special GL transactions are captured in a separate GL account
 Clearing Invoice against advance payment will automatically clear the special GL transaction and
the amount is transferred to the original reconciliation account.
Finance: Accounts Payable (BRD ID: 43.1)

Invoice receipt
Name of Business Process: Invoice Receipt
Module: Finance Sub module: Accounts payable

AS IS Process
Accounting is maintained at head office, bhankapur plant and Saha plant. Separate ledger accounts are
created by respective finance department. Direct expenses are booked through journal vouchers.
Procurement at plant is done with reference to PO and without PO at head office. Department head/
commercial head authorize if any advance payment is to be made to vendor.
TO BE Process
 Purchase orders will be created for procurements in the SAP system.
 Direct Vendor invoice will be booked for some process like – electricity, small overheads.
 GR based IV will be done for all PO Procurements.
 When goods/services are received, the Goods Receipt Note has to be recorded in the system
with reference to the respective Purchase Orders. Then the invoice will be booked.
 Invoice verification is the process of booking vendors invoice in the system by capturing the
vendors invoice date, invoice reference and invoice amount.
 An option is available for the user to clear the advance payment against the invoice received.
 The payment terms assigned in the vendor master are inherited in to Purchase order and Invoice
document.

Project Sunrise
 The due date calculation will be based on the base line date populated in the invoice and
payment term.
 Baseline date will be document date.
 Wherever there is a business transaction in currency other than local currency, system defaults
the exchange rates as per table maintenance. However, the exchange rates can be overridden
during invoice posting.
Below Tax code for accounts payable will used

V0- Non-taxable transactions
V1- Taxable transactions
Business user to share direct FI Tax code.
Credit Note (BRD ID: 43.5)

Debit memo- A debit memo is a transaction that reduces Amounts Payable to a vendor because of
returning damaged goods back to vendor.
In SAP there is no concept of debit memo .vendor credit memo works as debit memo and debits vendor
A/C.
For MCI India as invoices are booked through PO reference.

For Credit note
 Return order from MM
 Standard SAP process of invoice reduction will be followed
Invoice reduction The system enables you to reduce the invoice amount due to a vendor error
When you post an invoice with a reduced amount at item level, the system:
Generates a credit memo, As a result, the vendor is only paid for the invoiced amount minus the reduced
amount.
Creates two accounting documents for:
 Normal accounting
 Credit memo
Accounting Entries
Goods Receipt
Dr. Inventory
Cr. GR/IR Account
 Accounting entry during invoice verification towards material cost
Invoice Receipt
Dr. GR/IR Account
Cr. Vendor Account
All input tax will be a cost to MCI India as no input tax credit is available.
 Accounting entry during invoice verification towards delivery cost (No difference)
Dr. Freight clearing accounts
Cr. Freight Vendor Account

Project Sunrise
 Invoice reduction
Vendor DR
GL account CR
Note: Once the Goods receipt is done, Invoice receipts must be done in order to reflect the balance in
vendor account.
Above accounting entry remains same for all Local procurement.
Z table to capture tax line items at invoice booking (BRD ID: 48.3)
 Exchange rate type to default the exchange during invoice posting
 Automatic GL determination for procurement
 Configuration of payment terms to calculate due date
Number Range
Standard document type KR and RE will be generated. Number range will be decided by configuration
Open Points
 Payments terms will be shared by business.
 Automatic account assignment to be finalised after GLs list is shared by business
Gaps
 Invoice reduction

None

None
Integration aspects
 Invoices posted in Material Management module are automatically integrated to Financial
Accounting module. This ensures that the MM and FI are always in sync.
 While posting the invoices, the system prompts the value and quantity of Goods Receipt.
 GL account determination is done automatically for unplanned delivery cost

Project Sunrise
Finance- Accounts Payable (BRD ID: 43.3)
Vendor Payments
Name of Business Process: Vendor payment
Module: Finance Sub module: Account Payable
AS IS Process
The supplier statement of accounts is received and reconciled with the books of accounts and suppliers
are paid as per due date. Major vendor payments are done through bank transfer. Cheque is prepared
manually and necessary approval and signatures are obtained.
TO BE Process
Vendor Payments can be manual or automatic. The general aspects related to vendor payment are
Terms of Payment and Payment Method. While doing manual payment, the cheque number can also be
assigned manually.
Supplier Payments
Start
Automatic
PaymentY
Create Payment
Proposal
Edit Proposal

N
Execute automatic End

Vendor Collects
payment run
Cheque
Print Cheque
(Outside SAP)
Proposal
Execute manual Approved
payment
Project Sunrise Cheque

Signed
Automatic payments run can be used for making payments for invoices due to payment. When automatic
payment program is triggered, the system proposes the invoices that are due on that date.
The payment proposal list can be edited on line. If the user decides that the payment should not be made
for a particular invoice, it can be blocked and removed from that payment run. This does not block the
original invoice for next payment run.
While running the automatic payment run, system has the functionality to propose the list of
exceptions i.e. invoices due but blocked for payment due to various reasons. The user can review the
exception list and release the invoices for payments on a case to case basis.
The payment would be made from the house bank of the company code. Transactional banks will be
created as house bank in a company code.
It is possible that the vendor master can contain more than one bank account. In such cases, the
user must select the bank to be used for payment. Else the first bank will be defaulted for payment.
MCI India will be using manual payment and automatic payment run.
Creating Payment proposal and executing payment run will be done by different business user.
For Cheque standard SAP functionality will be used.

a) Defining the cheque lots for each and every house bank.
b) Entering the vendor invoice.
c) Entering the vendor payment by clearing the open item created by invoice.
d) Cheque will be automatically or manually attached to the
payment document number generated in step (c).
e) Check the cheque register to see the cheque updation
Name Variant
ZUK01 MCBC Standard

Project Sunrise
Payment Methods (BRD ID: 43.4)

For MCI India are below payments methods will be maintained.
Payment method Name
C Cheque
R RTGS
N NEFT
D Demand Draft
Ranking Order (BRD ID: 45.1)
Payment Curre Rank Name of Min Max

method ncy Order House Bank bank Amount Amount
Business to share bank 9,999,999,9
C INR 1 master data SBI 1 99.00
Business to share bank Bank of 9,999,999,9
C INR 2 master data America 1 99.00
R INR 1 master data America 200000 99.00
R INR 2 master data SBI 200000 99.00
Business to share bank Bank of
N INR 1 master data America 1 200000
Business to share bank
N INR 2 master data SBI 1 200000
D INR 1 master data SBI 1 99.00
D INR 2 master data America 1 99.00
Payment advice generated from payment run and the same will be forwarded to treasury team.
Cheque printing will be done manually out of SAP on stationary provided by Bank.
Foreign currency payment will be handled out of SAP.
Accounting entries
a) Accounting entry during payment
Dr. Vendor A/c
Cr. Outgoing Bank a/c
b) Accounting entry on reconciliation

Project Sunrise
Dr. Outgoing cheque issue a/c

Cr. Main bank account
System Controls
 The system will not allow the users to make payments unless the invoices are posted and due.
 Once payment is done, the item is marked as cleared. This ensures that the same invoice is
not paid twice.
 If the vendor account is having debit balance, the program considers this as exceptions and
does not allow payment for rest of the invoices.
 Payments to vendors can happen via manual or automatic payment run.
 Creation of payment proposal and payment run will be with different users.
Bank integration for Bank of America
Vendor Advice
 Automatic payment program configuration
 Payment method
 House Bank configuration
 Maintain Check lot
Number Range
Standard document type KZ will be generated. Number range will be decided by configuration team at
time of Realization.
Open Points
Business to share vendor advice template
Gaps
None
None
Vendor payment advice
Integration aspects
 The payment entry clears the vendor open items automatically.
 House bank details are automatically derived by the system based on payment method.
 Will be handled during realization phase
Finance – Bank and Cash Accounting (BRD ID: 46.1)


Project Sunrise
Name of Business Process: Bank and Cash Accounting
AS IS Process
All bank transactions and reconciliation are done in HO. Control account is used as clearing AC to
reconcile with Plant transactions.
Majorly operations are under taken in Bank of America except for Inward and outward duty payments.
Major duty payments are done State bank of India
TO BE Process
Each Bank Account number will be created as house bank and separate General Ledger
account will be mapped.
Each Loan and Deposit account will be created as General Ledger.
For each operating General Ledger Accounts below accounts will be created.
 Bank Main Account
 Bank Incoming Account / Collection (Clearing Account)
 Bank Outgoing Account / Payment (Clearing Account)
Payment Entry:
Vendor Dr
To Bank Outgoing Account Cr
Collection Entry with reference to Customer

Bank Incoming Account Dr
To Customer Cr
Petty Cash Accounting (BRD ID: 46.1)
AS IS Process
Petty cash is maintained at HO and at plant level. Upon receipt of expenses invoice and subject to
approval of plant/unit head petty cash expenses is paid.

Project Sunrise
TO BE Process
Cash journal is a sub ledger of Bank Accounting. It is used to manage a company's cash
transactions. The system automatically calculates and displays the opening and closing balances,
and the receipts and payments totals. You can run several cash journals for each company code.
You can also carry out postings to G/L accounts, as well as vendor and customer accounts.
A separate cash journal for HO and manufacturing plants
Posting to GL account, vendor and customer accounts are possible.
For MCI India separate cash journal for HO and each manufacturing plants
Cash Journals (Petty Cash Books) will be created as below
Description Document
S.No Sap name
Type
01 1000 HO CO
02 2000 Bankapur CB
03 3000 Saha CS
04 4000 Bitha CI
Business transaction type and name define nature of expense or revenue against which cash is utilized
For MCI India below mentioned business transaction will be used.
Name
S.No Business
Transaction
type
01 C Receipt from bank
02 B Payment to bank
03 E Expense
04 V Paid to vendor
A separate petty cash GL account has to be created and post automatically indicator has to be selected
for this GL account, which ensures that no manual JV’s are posted to this account. This account can
be posted only via petty cash module.
The cash payments for expenses can be recorded with assignment to cost center.
After closure of the business day at Head office, the cashier will check and close the cash ledger for
the day.
The transactions recorded can be saved in real time.

Project Sunrise
Accounting Entry
Petty Cash expenses booking
Dr. Expense account a/c

Cr. Petty Cash a/c (through cash journal)
Receipt of cash by cashier

Dr. Petty cash a/c
Cr. Central Treasury a/c
Cash Management (BRD ID: 51.1)

The Cash Management field in SAP FI is used to manage cash flows and to ensure sufficient liquidity to
cover payment obligations.
Cash management is used monitor payment flows and safeguard liquidity, so that you can meet your
payment commitments.
SAP Cash Management enables an organization’s cash or treasury department to manage bank
accounts centrally, overview the cash daily operations and long-term liquidity trends accurately and
precisely. Cash managers can easily and intuitively get a high-level overview and detailed insight into
bank accounts, cash position and cash flows, enabling them to make decisions and take actions directly.
The major features include:
1. Bank Account Management
Bank Account Management allows you to manage your bank account master data centrally, using a
process in place to govern the opening, closing, and changing of bank accounts. The streamlined
workflow also helps improve user efficiency in accomplishing compliance-related tasks.
2. Cash Operations
Cash Operations allows you to review the cash position to understand cash distribution, whether bank
accounts have sufficient funding (or a surplus) for the day’s payment obligations, and whether to invest
free cash in the short term.
3. Liquidity Management
Liquidity Management allows you to analyze the past actual cash flows and forecast the medium-term
liquidity trends. It also provides rolling plan cycle management and planning status monitoring with
variance analysis on plan, actual and forecast data.
Integration: cash management is a subcomponent of treasury.
This means it is closely linked with treasury management (TR-TM) and market risk management (MRM).
Cash management offers the functions described above for liquidity analysis purposes while MRM offers
methods and process of assessing risks positions.
Cash Position
Cash position supplies information on the current financial situation in your bank and bank clearing
accounts. Integration with payment advices means that cash position can give you an Overview over
Short-term liquidity movements.
Integration:--The cash position reproduces the activity in your bank accounts. It is derived from the prompt
entry (on their value date). of all payments made within a short period of time.
System Controls

Project Sunrise
 Persons with authorization can record/post cash transactions

 Cash transactions are recorded only through cash journal module. No manual entries can be
posted to cash on hand account.
 GL accounts for business transactions are automatically determined
None
 Required Cash journal will be created.
 Separate document type for each journal.
 Number range for Bank Account for technical IDs
 Number range for change request
 Bank Account types
 Planning level and planning groups

Number Range
Number range will be decided by configuration team at time of Realization.
Open Points
 Business will share existing cash flow template
 Treasury Cash management activation
Gaps
Treasury Cash management activation
None
None
Integration aspects
The Cash journal posting in financial accounting is done in real time.
Finance – Bank Reconciliation (BRD ID: 45.3)

Name of Business Process: Bank Reconciliation
Module: Finance Sub module: Bank


Project Sunrise
table
AS IS Process
As part of bank reconciliation will be carried out for all the bank accounts, on monthly basis. The bank
GL transactions are cross checked against the respective entries in the bank statement.
TO BE Process
MCI India will have both manual and electronic bank reconciliation.
Bank Reconciliation
Manual Bank Electronic Bank

Statement Statement
Enter bank
Download file from
statement items
Bank site (MT940)
manually
Execute Bank Financial

recon. transaction
Document posted
Financial Cheque register
updated by system
Document posted
Upload into SAP
Clear through post
Un cleared items processing screen
existY Clear through post
Un cleared items processing screen
exist
Y End
N
N
Electronic Bank Reconciliation

 The electronic bank statement (EBS) can be used for bank reconciliation. The
bank has to provide the file in the prescribed format (MT940) which can be uploaded
in the system.
 All bank accounts will be linked to a separate GL account.
 Based on the house bank configuration, system will validate the bank key in the
statement and posts entries into the respective company codes automatically. No
user intervention is required for selecting company code.
 The external business transaction like incoming payment, outgoing payment, bank
charges, direct credit/debit etc., would be configured in the system. Based on the
business transaction in the bank file, system automatically posts the entries. Posting
rules and posting type determine how the posting should happen.
 Based on external business transaction, MCI India decided to handle payment and
collection as below

Project Sunrise
a. Payment entry will always clear the open item based on the bank reference number.
b. Collection entry will always post the document.
 For vendor payments, the cheque number/amount would be used as criteria for
clearing the outgoing cheque clearing account. All the outgoing payments would
be initially posted to outgoing cheque clearing account. Once the encashment is
done by the vendor, it can be transferred to the main bank account via EBS upload.
If the payment amount/cheque/reference in bank statement and general ledger account (outgoing
account) matches, the posting happens automatically. Else it will be logged in the post processing
screen and has to be cleared/ posted manually. The un-posted transaction can be seen in the post
processing screen which can be posted manually.
 The upload of statement and posting to general ledger can happen simultaneously by choosing
post immediately indicator. The un-posted transaction can be seen in the post processing
screen which can be posted manually.
 Posting of bank charges requires an assignment of cost center. The cost center for individual
company codes towards bank charges need to be configured (automatic account determination).
It required as there is no provision to manually enter the cost center during bank reconciliation
posting. (although this can be done through post processing option)
 The open items in the respective GL accounts (incoming /outgoing cheque clearing accounts)
are considered to be reconciliation items.
 Bank statement in MT940 format will manually uploaded in SAP by user.
Note: If MT940 statement is provided in SAP format then the above EBS process will
be followed, if MT940 statement is not available or not in SAP readable format or Field
mapping in MT940 is incorrect then we need to follow the Manual Bank Statement.
Manual Bank Reconciliation
 The entries in the statement have to be entered manually (copy and paste template) and
the posting can be done automatically.
 Manually bank statement has to be entered by the user with transaction type.
 Process related to bank charges and clearing of payment / collection will be same as
of Electronic Bank Statement.
List of account symbol and transaction type
Post Processing
 Post processing of bank statements function can be used to process in a timely and
straightforward way any bank statements that could not be posted by the system

Project Sunrise
automatically.
 The single screen transaction for post processing bank statement items supports the user
with information and functions needed in the day-to-day work to be able to post the
open bank statement items in the system manually.
 Wherever the reconciliation process could not automatically clear the clearing account
and post to main bank account, the post processing can be used to choose those items
and do the clearing.
 The reconciliation may not be successful for various reasons like wrong data in the
electronic/manual bank statement provided. The assignment field of the bank clearing
account entries may not match hence the reconciliation may not be successful.
 For this reason post processing is very helpful to complete the reconciliation quickly.
Accounting Entry
For customer payments
Dr. Main bank a/c Dr. Bank charges a/c

Cr. Incoming cheque clearing a/c
For Vendor payments

Dr. Outgoing cheque clearing a/c
Dr. Bank charges a/c
Cr. Main bank a/c
System Controls
 Only authorized persons can access EBS/Manual bank statement transactions
 Entries are automatically posted using normal/external business transactions
 GL accounts for business transactions are automatically determined
None
 Create Account symbols
 Assign GL accounts to account symbols
 Create business transactions
 Create external business transactions
 Posting rules for bank statement upload

Project Sunrise
Number Range
 Number range will be decided by configuration team at time of Realization.
Open Points
 Business to share bank GL for mapping with account symbols
Gaps
None
None
None
Integration aspects
 Reconciliation document will be posted in general ledger.
Finance-Taxes on Purchase and Sale (BRD ID: 48.1)

Name of Business Process: Taxes on Sales and Purchase
Module: Finance Sub module: Tax
AS IS Process
In Molson Coors India all tax on purchase is added to cost of inventory.
At time of Sales tax is charged to customer
TO BE Process
All the taxes that are related to purchases are termed as input tax and all those taxes that are related to
sales are termed as output tax.
The Tax Calculation Procedure will be adapted from standard SAP, delivered specific to country India

Project Sunrise
and will be configured to suit the business.
Tax Procedure (BRD ID: 48.1)

A calculation procedure is defined for each country, each containing the specifications required to
calculate and post tax on sales/purchases. Each calculation procedure contains several tax types, which
are called condition types in the procedure.
The system defaults condition types when you define a tax code. The condition type (such as input or
output tax) specifies the base amount on which the tax is calculated and the account key that is used to
post the tax. The specifications necessary for calculating and posting tax is to be defined for the condition
type and account key.
TAXINN is a tax calculation procedure for country version India and it supports condition-based tax
determination.
TAXINN will be assigned to country India for the purpose of tax on sale and purchase.
Condition type: SAP uses condition type to calculate Taxes. Tax calculation procedure along with
condition type and Tax code are used in calculating Taxes.
Indicates how the tax calculation model will work (whether the records are for fixed amount or
percentages and whether the records can be processed automatically.)
Access Sequence: This is the search strategy, which is used by the system to find valid data for a
particular condition type. It tells about the order in which a system searches for the data. An access
sequence consists of one or more access sequences. It helps the system to search first, second and so
on until it finds a valid record. An access sequence is defined for each condition type where a condition
record is created.
Account Key: Determines if tax is inventorised or posted to separate GL account.
List of condition type and access sequence for MCI India
Tax Codes
Tax codes are used to:
 Check the tax on sales/purchases amount in the document
 Calculate the amount of tax on sales/purchases automatically on request
 Calculate the non-deductible input tax portion
 Check if a tax account with tax type (input or output tax) can be posted to
 Determine the tax account
We define a tax code by entering a two-digit code to represent a tax percentage rate.
Tax Codes will be created which will then be adopted while entering tax relevant documents.
For e.g. Tax items are included in purchase invoice and sales invoice.
Region Code
For GST new region code have to be defined to match with Indian government state codes.

Project Sunrise
List of state codes
TDS / With-holding Taxes (BRD ID: 48.2)

Taxes deducted at source as per the Income Tax Act 1961 India are termed as with-holding taxes (WHT).
Extended With-holding Taxes (EWT) will be configured to suit the requirements of business.
The recipient types will be configured which along with the WHT code will ensure the calculation and
posting of the WHT. Multiple WHTs can be mapped with a single vendor and system will give a pop-up
during invoice verification/advance payment and ask to select the relevant tax.
Relevant with-holding tax code will be configured which will then be assigned to the vendor/ customer
master for accounting purpose.
Withholding Tax Type (WHT)

In one business transaction, several kinds of withholding tax may have to be withheld. The SAP System
uses withholding tax types to reflect this. Several withholding tax types can be defined in the system;
one or more can be assigned in the vendor master record.
The withholding tax type governs the way in which extended withholding tax is calculated and is defined
at country level. As far as the time of posting for withholding tax amounts is concerned, there are two
different categories of withholding tax types:
Withholding tax type for posting at time of invoice

Withholding tax type for posting at time of payment
Withholding Tax Code

Defining the tax base and rate for the calculation of withholding tax is maintained in the withholding tax
code. You make the settings for each country and withholding tax type. You can therefore define as many
withholding tax codes as required for each withholding tax type.
Recipient Type
A system objects that you use to classify payment recipients according to their taxpayer status, for the
purposes of withholding tax certificates.
Whenever you enter a document that includes a withholding tax item, the system automatically assigns
the item a withholding tax code, as normal. Since each tax code is also associated with a recipient type,
the withholding tax item is also automatically classified.
Business Place & Section Code

In India, the business place represents a tax withholding entity as identified by a tax deduction account
number (TAN).In India, the business place is the level at which income taxes are collected and reported.
In all SAP System transactions that involve income taxes, therefore, you must specify a business place.
This ensures that your business reports the income tax to the right tax office.
Note: If you fail to enter a business place in a line item that is relevant to withholding tax, then the line

Project Sunrise
item will not be seen in W/H Tax Reports.
Withholding Tax Internal Challan and payment to bank

When we have remitted the deducted TDS to the government, we are sent a challan confirming that
payment has been received.
The system allows to record the number of the challan in the invoices from which the TDS had been
deducted and paid.
 Withholding Tax Internal Challan

 Internal Challan number
 Clearing document will be posted
Withholding Tax Bank Challan: Link internal challan number and clearing document with bank challan.
• Withholding Tax certificates for vendor: We have already remitted the TDS to the government and
recorded the challan number in the transactions concerned. Only transactions with a challan
number can be included in certificates.
At MCI INDIA
The withholding tax type, code and GL relationships will be maintained for automatic TDS GL
determination.
Recipient Type will be defined:
25 Companies (CO)
26 Other
Witholding tax challan and payment to bank will made from system
The system allows to record the number of the challan in the invoices from which the TDS had been
deducted and paid.
TDS deducted DR
Bank CR
Later business will Link internal challan number and clearing document with bank challan
Withholding Tax certificates for vendor: We have already remitted the TDS to the government and
recorded the challan number in the transactions concerned. Only transactions with a challan number can
be included in certificates.
Withholding tax returns (BRD ID: 48.4)

Returns Form
TDS returns for payments 26Q
other than salaries to
residents
TDS returns for payments 27Q

to non-residents

Project Sunrise
The standard reports for Extended Withholding Tax that are available in the Standard SAP system would
be made available.
Business Place to be defined: User team to provide
Section Code to be defined: User team to provide
Accounting Entries
Vendor a/c (SplGL) Dr 1000 (Base Amount: 1000)
Bank a/c Cr 990
TDS Liability Cr 10 (Base Amount: 1000)
Accounting Entry at the time of Invoice:
Expense a/c Dr 2000

Vendor Cr 1980 (Base Amount: 2000)
TDS Liability Cr 20 (Base Amount: 2000)
Advance clearing
Vendor a/c Dr 990
TDS Liability Dr 10
Vendor a/c (Spl GL) Cr 1000
Tax collected at source (BRD ID: 48.2)
TCS or Tax Collected at Source is the income tax collected in India, that is payable by the seller who
collects in turn from the buyer and it is provided under section 206C of Income Tax Act, 1961 at the sale
of some goods which are specified. The rate at which TCS is collected differs as per the category of
goods.
TCS will be controlled by output tax.
Returns Form
TCS returns under 27EQ
section 206C

 Configuration of complete tax procedure including condition type, access sequence and
accounting key.
 Copy Routine 363 at base condition of price in tax procedure for margin money.
 Configuration of business place ,section code and receipt type.
 Configuration of withholding tax type for invoice and payment.
 Configuration of withholding tax code.
 Determination of tax accounts

Project Sunrise
Number Range
None
Open Points
 Business to share complete list of indirect tax code
 Business user to share complete list of withholding tax details.
 Business to share complete list of business place and section code
Gaps
None

None

None
Integration aspects
 Invoices posted in Material Management module are automatically integrated to Financial
Accounting module including tax component. This ensures that the MM and FI are always in
sync.
 While posting the invoices tax code can be changed.
 GL account determination is done automatically for tax accounts.
Will be handled during realization phase.

Project Sunrise
Finance –Asset Organization Structure (BRD ID: 47.1)

Name of Business Process: Fixed Asset accounting
AS IS Process
Fixed Assets are procured against purchase order. Purchase for asset under construction is made
against CWIP asset and upon completion CWIP is settled on main asset
Monthly, finance department posts depreciation run for IGAAP and USGAAP. All depreciation posting is
done manually. For Companies Act depreciation is calculated by Straight line method on basis of useful
life. For Income tax depreciation is posted on written down value for group assets.
TO BE Process
The Asset Accounting component is used for managing and supervising fixed Assets in SAP System. In
SAP, it serves as a subsidiary ledger to the FI General Ledger, providing detailed information on
transactions involving fixed Assets.
The change brought by implementation of Asset accounting is the integration of the fixed Asset module
with general ledger accounting. All transactions posted within the SAP fixed Asset module will instantly
update their respective general ledger account balances. As a result of the integration Asset Accounting
(FI-AA) can transfers data directly to other SAP components. It is possible to post from the Materials
Management (MM) component directly to FI-AA.

Project Sunrise
Asset can be procured through Purchase module with an integration to Controlling and Asset accounting
through a Purchase order in SAP.
Chart of depreciation
Chart of Depreciation contains the list of defined depreciation areas arranged according to the
business and legal requirements. Chart of Depreciation enables us to manage all rules for the
valuation of Assets.
In general, its required to calculate values for assets for different needs, both internal and external
(such as book depreciation and cost depreciation). The chart of depreciation, therefore, is a directory
of depreciation areas organized according to business management requirements.
SAP recommends one chart of depreciation based on country of operations. As all changes to
depreciation posting is envisaged by a legal change only, which is at country level, it is suited to have
one chart of depreciation per country.
Any changes to configuration at a future date, the changes are applicable across all company codes
using the same chart of depreciation.
Chart of depreciation for MCI India

Company Code
ZIN MCBC IN Chart of Depreciation
Asset Class
Asset classes are the most important means of structuring fixed Assets. You use the Asset classes to
structure Assets according to the requirements of the enterprise. Asset class is used to classify the Asset
into buildings, plant & machinery, vehicles etc. An Asset class is a client level data element, which means
it will be shared by all chart of depreciations.
Existing asset classes will be used for MCI India
Depreciation areas (BRD ID: 47.4)

Depreciation areas are used to calculate different values in parallel for each fixed Asset for different
purposes. For example, it may be required that different types of values are reported in the balance
sheet for tax purposes. The depreciation terms and values necessary for this valuation are managed
in the depreciation areas of each Asset
Following depreciation areas will be configured
Nature of posting
Depreciatio Description
n Areas
01 Book Depreciation in US Real Time Posting to FI
10 Book Depreciation in India Do not post
20 Depreciation as per Income Tax Do not post
ACT

Project Sunrise
Depreciation key (BRD ID: 47.4)

The depreciation key contains the value settings which are necessary for determining depreciation
amounts. It represents a combination of calculation rules, which are used for the automatically
calculated depreciation types
SAP Depreciation Key ‘LINK’ will be used, which will be calculating the depreciation on Straight Line
Method, additionally for depreciation area 20 WDV method will be used, Depreciation keys will be
created, if required.All Business will confirm depreciation percentage.
None
System Controls
 No manual posting can happen to depreciation accounts. They can always be posted through
fixed Asset module.
 Planned depreciation cannot be executed twice within a month.
 Only authorized personnel can run the depreciation run.
 In case the depreciation was not run in the previous cycle, system will not allow running the
depreciation for the current cycle.
Sub-ledger and general ledger is integrated through Asset reconciliation accounts

 Country specific Chart of Depreciation will be created
 Creation of depreciation key
 Depreciation area in asset class.
Number Range
Standard document type AA will be generated. Number range will be decided by configuration team at
time of Realization.
Open Points
Business to share complete asset master list along with asset class and depreciation rate.
Gaps
None
None
None
Integration aspects
 Will be handled during realization phase

Project Sunrise
Finance –Asset Transaction Process

TO-BE Document For SAP Implementation at
4Molson Coors India
Asset Procurement (BRD ID: 47.3)
AS IS Process
Fixed Assets are procured against purchase order. Purchase for asset under construction is made
against CWIP asset and upon completion CWIP is settled on main asset
TO BE Process
 Purchase Request(optional) will be created by the concern department, requesting for Asset
procurement
 Procurement team will create Purchase Order.
 Purchase Order should be created with account assignment category “A” (Asset).
 As Goods receipt is posted, the value is updated to Asset (AUC).
 Upon AUC Asset settlement, the AUC Asset is considered as settled and the useful life of the
main Asset starts which means depreciation calculation will start from this date onwards

Project Sunrise
Asset needDownMain
to bePaymentAsset
Creat e
AUC / Post Closing Maintena nce
Asset Invoice of Settleme
Post Down Post Down Clear Down

Payment Payment Payment
Request
Accounting Entry
1) CWIP Asset procurement
At the time of Goods Receipt
Dr. Asset (CWIP - General Ledger)

Cr. GR / IR Clearing Account
2) At the time of Invoice Verification
Dr. GR/IR Clearing Account

Cr. Vendor Account
At the time of settlement to Asset

Dr. Asset
Cr. CWIP account
Asset Retirement(BRD ID: 47.6)

Asset retirement is removal of an Asset or part of an Asset from the Asset portfolio. This removal of an
Asset (or part of an Asset) is posted from a bookkeeping perspective as an Asset retirement. Depending
on organizational considerations, or the business transaction which leads to the retirement, they can be
classified as

Project Sunrise
 Asset sale with/without Revenue with Customer

 Asset Sale without customer
 Asset Scrapping
All the above retirements can be made using different transaction types in Asset accounting.
Sale of Fixed Assets

AS IS Process
The sale of Asset happens after obtaining the necessary approvals from management towards sale of
fixed Assets. The sale will be recorded and the Asset is delivered to the buyer.
Such sale can happen during the useful life of an Asset or after the useful life of an Asset, it can be sold
to affiliated companies or any third parties with revenue.
 Presently retirement process is maintained legacy system.

 Asset retirement can be scrapping or sale.
To-Be Process
The system enables to post the revenue and the Asset retirement in one step. In this transaction, all the
entries related to asset will deposited including the gain or loss on sale of asset. The system automatically
adjusts the accumulated depreciation and the acquisition value.
User can choose as complete or partial retirement.

 Approval from Management ( Outside SAP)
 Negotiating best price and accepting the price (Outside SAP)
 Asset movement from physical location (Outside SAP)
Asset retirement with customer and revenue in SAP (Covered in Sales and distribution BBP )
Asset Write off

AS IS Process
The custodian of Asset will propose for write off of Asset to management for approval in line with internal
policy for Asset disposal. Fixed Assets team along with management representatives would inspect and
concurrence the disposal.
After obtaining the management approval, Assets are written off and scrapped.
To-Be Process
The scrapping process is same for all the legal entities in scope. Asset scrapping transaction creates a
loss on sale of Asset in case it is having useful life.
Example:
The acquisition value is 10000 INR, Accumulated Depreciation is 9800 Net book value is 200

Project Sunrise
INR
Accounting Entry
Dr. Loss on disposal of Asset account 200

Dr. Accumulated Depreciation account 9800
Cr. Main / Sub Asset account 10000
Transfer of Assets(BRD ID: 47.5)
AS IS Process
Intra-company transfer is handled in legacy system. For Inter-company transfers financials are also
transferred to their respective entities
To-Be Process
Inter Company
 This process is applicable for all legal entities in scope.
Process 1
 Approval to transfer assets (out of SAP)
 Use intercompany transfer of assets – ABT1N
Sending Asset Values to be transferred can be based on Gross or Net book value
Process 2
Intra company asset transfer
 An Asset or its component can be transferred to a different Asset. The company

code should be same for both the sending Asset and receiving Asset.
 An asset was created in the wrong asset class. Since we cannot change the asset
class in the asset master data, we have to transfer the asset to a new master
record.
Accounting Entry
Asset Capitalization Date is 01 Jan 2018
Depreciation 10%
Asset Value 12000

Project Sunrise
Accumulated Depreciation as on 31 Oct 2018 2200

Depreciation for the Year as on 31 Oct 2018 1000
Selling Price at 15000
 Transfer within company code
The transfer can be between Asset Class or Cost Center

For the above scenario the entry will be as for transferring from plant 1001 (cost Center /Profit
Center) to 1010 (Cost Center /Profit Center)
Furniture Cr 12000 1001

Furniture Accumulated Depreciation Dr 2200 1001
Fitting Dr 12000 1010
Fitting Accumulated Depreciation Cr 2200 1010
By changing the Cost center and location details in Asset master

data
The Cost center and location can be changed in the Asset master data whenever there is a need. No
documents will be posted in SAP.
Based on the time dependent data in asset master record users will be able to identify that asset
under evaluation is existing in different locations in different periods
System Controls
 Materials management module is integrated with fixed Asset account module. Hence
capitalization entries are directly posted to Fixed Asset account from material management
module.
 All Asset procurements will be process using the Purchase Order.
 Sub-ledger and general ledger is integrated through Asset reconciliation accounts
 Usage of transaction type ensures that correct business transaction is posted
 The retirement date is automatically updated in the Asset master based on the asset value
date.
 Accumulated depreciation and acquisition accounts are reconciliation accounts. So no manual
posting is possible.
 Asset transactions can be reversed only within Asset module
 Only authorized personnel can do an Asset transfer
 The Asset transfer documents can only be carried through Fixed Asset module and no direct
posting/adjustments in Finance module can be done.
None

Project Sunrise
 Country specific Chart of Depreciation will be created.
 Account determination keys to post similar Assets into a specific general ledger account
 Account determination keys to post gain or loss on disposal of Assets.
 Asset number range for Company codes
Number Range
Open Points
None
Gaps
None
None
None
Integration aspects
 The Materials Management module is integrated with Finance-Asset Accounting module. Hence
the Goods receipt in MM module posts Assets transactions in Finance- Asset Accounting
automatically. Finance-GL is also posted simultaneously.
 The integration is based on account assignment category and the related Purchase Order
assignments
 Different account determination keys ensures that similar Assets are posted to the same general
ledger accounts
 Sub-ledger and general ledger is integrated through Asset reconciliation accounts.
 Retirement transactions determines the acquisition value and accumulated depreciations
 The related transactions are automatically posted in Finance-GeneralLedger (FI- GL) using
reconciliation accounts
 No Asset related transactions can be reversed directly in FI-GL module. They have to be
reversed only within Finance-Asset Accounting (FI-AA) module
 Sub-ledger and general ledger is integrated through Asset reconciliation accounts.
 Automatic transfer posting when Assets are transferred between company codes

Project Sunrise
Finance –Depreciation of Assets(BRD ID: 47.4)

TO-BE Document For SAP Implementation at Molson and Coors India
AS IS Process
Assets are depreciated using straight line method and written down method. Presently depreciation
is being calculated in legacy system and if the depreciation is not matching as expected then
manual depreciation adjustment entry is posted.
TO BE Process
 Straight line method and written down value method of Depreciation will be used for MCI India.
 When the Asset is capitalized, the system automatically plans the month wise depreciation to be
posted till the end of its useful life. When the depreciation is run, the system uses that information
to post depreciation.
 When depreciation is run, the Asset explorer in Asset accounting module is updated and
corresponding financial posting is done within financial accounting.
 The depreciation key assigned in the Asset master determines the amount of depreciation to be
posted to that particular Asset based on the useful life of the asset.
 Depreciation will be executed monthly, as part of period end activity
 Asset value date is the key for calculating the depreciation. This is updated with the posting date
of capitalization

Project Sunrise
Depreciation Run
Month close
Set Depreciation Execute

parameters Depreciation in
Test mode (fore
ground)
Event
N Errors found Y
Execute
depreciation in
back ground
Fix errors
without Testmode
Accounting Entry
Depreciation Dr
To Accumulated Depreciation Cr
System Controls
 No manual posting can happen to depreciation accounts. They can always be posted
through fixed Asset module.
 Planned depreciation cannot be executed twice within a month.
 Only authorized personnel can run the depreciation run.
 In case the depreciation was not run in the previous cycle, system will not allow running
the depreciation for the current cycle.
 Sub-ledger and general ledger is integrated through Asset reconciliation accounts
None
 Maintaining depreciation keys
Number Range
Standard document type AF. Number range will be decided by configuration team at time of Realization.
Open Points
None
Gaps
None

Project Sunrise
None
None
Integration aspects
 The depreciation posting in financial accounting is Assets wise posting.
 The Asset explorer is automatically updated which enables comparison of present and previous
periods postings
 Change in depreciation keys in the Asset master automatically recalculates the planned
depreciations for the future periods.
Finance-Account Receivable (BRD ID: 44.1)

Name of Business Process: Account Receivable
Module: Finance Sub module: Account Receivable

table
AS IS Process
State wise sales accounting is maintained at plant level and billing from brewery / depot is done to
individual customer
TO BE Process
No sales will be done through direct Finance module. Complete Sales process is covered under SD
Module.
Accounting Entry
 Post Goods issues ( PGI ) is process of delivery and it will update material document
and Accounting document is created in the background.
Dr. COGS
Cr. Inventory

Project Sunrise
 Billing is created with reference to the delivery document and invoice printout will be
generated automatically. Once the billing document saved, accounting documents
generated in the background
Dr. Cash account
Cr. Revenue account
Below Tax code will be used for accounts receivable
A0 – Non-taxable transactions
A1- Taxable transactions
Customer Down payment (BRD ID: 44.2)

Down payment is used to process and post advance payments, which are made by party’s for future
services, as down payments. Down payment for sub-ledger will post to alternative reconciliation account
rather than in normal reconciliation. Once the billing is done, same is cleared against the invoice. The
identification of down payment transaction is identified by Special GL Indicator which needs to be entered
while posting the down payment transaction.
Existing special GL indicator will be used .
description
Special GL Name
Indicator
A
Dwn pmt Down payment (Other)
F
Pmt req Down payment (request)
G
Guaran. Guarantee
 Down payment request will be generated by sales team.

 Down payment processing will be done by finance team.
Accounting Entry
At the time of advance received:
Bank a/c Dr 1000

Customer a/c (Spl GL) Cr 1000
At the time of billing
Customer a/c Dr 5000

Sales Cr 5000
At the time of clearing the down payment:
Customer a/c (Spl. GL) Dr 1000

Customer a/c Cr 1000

Project Sunrise
Credit Note (BRD ID: 44.5)

A transaction that reduces amounts Receivable from a customer is a credit memo. For eg. The customer
could return damaged goods.
For MCI India credit note will be used for primary scheme and in case of any damage to goods during
shipping.
For primary scheme statistical condition type and condition record will be maintained and same will flow
into sales order and billing document. Value of discount type will not add to net value.
Discount value will be posted to provision account.
Custom program will be developed to reverse provisional accounting entry and subsequently issue credit
note for respective invoice and allocate primary discount to customer.
Accounting Entry
At the time of billing
Customer a/c Dr 5000

Sales Cr 5000
Provision Dr 1200
Discount primary Cr 1200
At time of credit note

Discount primary Dr 1200
Customer Cr 1200
Incoming Payment (BRD ID: 44.4)

Incoming payments are receipts that are received by the company which are mostly from customers.
Upon receipt of money from Customer the entry is passed into the customer account by way of partial
payments or full payment.
Accounting entry for incoming payments:
Bank a/c Dr xxx

Customer a/c Cr xxx
For MCI India incoming payment can be cheque/bank transfer .
Manual Clearing
Clearing of open items can be done at a later stage when the same is not carried at the point of posting
the transaction. The open items for a customer can be viewed as on a particular date and can be cleared
off against any other line item or balance
System Controls
 Sub-ledger and general ledger is integrated through reconciliation account.
Reconciliation account is assigned to all customers
 Customer reconciliation account is linked with Special GL account to post down payments to
FI

Project Sunrise
 Custom Program to post customer credit not
 General Ledger Account Mapping during Billing Document posting.
 General Ledger Account mapping during post goods issues.
Number Range
Open Points
 Business to share payment terms for customer.
 If Credit note process for primary schemes can be processed through sales & distribution
process.
WRICEF
 Consolidated state wise debtor ageing
 State wise provision report for schemes
Gaps
None
None
None
Integration aspects
 Goods consumption document will be posted in Finance.
 At time of billing accounting document will be generated.
 Credit note document will be posted in Finance.

Project Sunrise
Finance-Automatic Account Determination (BRD ID:

44.2)
Name of Business Process: Account determination
Module: Finance Sub module: Inventory movement

table
AS IS Process
GL accounts are manually entered for every material movement, Invoice posting and billing..
TO BE Process
When a goods movement is entered, the G/L accounts need not be entered manually since SAP
automatically determines the correct accounts.
For every goods movement created for a valuated material, the SAP system can create two types of
documents: a material document and an accounting document. The SAP system follows the accounting
principle that for every material movement, there is a corresponding document that provides details of that
movement. In addition, an accounting document is produced that describes the financial aspects of the
goods movement.
The settings for this automatic account determination & material valuation are done by using “Valuation &
Account Assignment”.

Project Sunrise
Valuation Grouping Code

It is the group of valuation areas having same account determination process.
For MCI India new valuation grouping code will used as per existing system design.
Valuation Grouping
Code
IN01
Valuation grouping code IN01 will assigned for MCI India valuation areas.
Valuation Class
The combination of material type, account category reference, valuation class determines the G/L
accounts updated for valuation relevant transactions.
The valuation class is a key to group materials with the same account determination. The valuation
classes depend on the material type. Several valuation classes are generally allowed for one material
type. A valuation class can also be allowed for several material types.

Project Sunrise
The valuation class makes it possible to:

 Post the stock values of materials of the same material type to different G/L accounts
 Post the stock values of materials of different material types to the same G/L account
Account modifier
Using this function, you can assign an account grouping to movement types.
The account grouping is a finer subdivision of the transaction/event keys for the account determination.
For MCI India below matrix of valuation class and account modifier will be maintained. GLs accounts will
be mapped once finalized.
Account receivable
The accounting entries with respect to the billing will generally result in
 Debit Customer account
 Debit Freight-out account
 Credit Revenue account
 Credit Tax Payable account
Hence, primarily, one side of the account is a Customer and the other is a revenue account. The
customer account gets picked up from the customer master data and the revenue account is configured
based on certain inputs so that correct account is hit during FI posting. This automatic account
determination is configured not only for revenue, but also, other elements like Freight, surcharges, sales
deductions etc.
The account determination can be done to be based on the following criteria:

Application
 Condition Type
 Chart of Accounts of Company Code
 Sales Organization
 Customer Account Assignment Group
 Material Account Assignment Group
 Account Key
For MCI India following account determination will be maintained.
System Controls

Project Sunrise
 MM and FI documents are integrated through transaction types.

 Postings are made to G/L accounts automatically in the case of Invoice Verification and
Inventory Management transactions relevant to Financial and Cost Accounting.
 SD, PP and FI documents are integrated through condition type
 None
 Creation transaction event key.
 Assignment of valuation grouping code to valuation Area.
 Maintaining GL account for valuation class and account modifier
 Maintaining account key for SD
 Assign GL to access sequence in SD
Number Range
None
Open Points
 Automatic account assignment matrix to be finalized after list of all GLs is provided by business.
WRICEF
None
Gaps
None
None
None
Integration aspects
 Transaction key are used for different transactions (for example, goods issue, scraping, physical
inventory), which are assigned to different accounts (for example, consumption account,
scrapping, expense/income from inventory differences),
 Valuation class allows to define automatic account determination that is dependent on the
material.

BBP Fi Mci VW V1.3

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BBP Fi Mci VW V1.3

Uploaded by

Copyright:

Available Formats

Project Sunrise

Business Blue Print

March 31, 2019

STATEMENT OF CONFIDENTIALITY / DISCLAIMER

Vital Wires Confidential 1

Vital Wires Confidential 3

Vital Wires Confidential 4

Vital Wires Confidential 5

Vital Wires Confidential 6

Vital Wires Confidential 7

Vital Wires Confidential 8

1.0 Kanishk Sujit Suman Initial Draft

1.1 Kanishk Sujit Suman Revised version after review

1.2 Kanishk Sujit Suman Revised version after BBP

1.3 Kanishk Sujit Suman Revised version after BBP

Vital Wires Confidential 9

The process of arriving at the blueprint is as below:

Arrive at “AS-IS” process.

Vital Wires Confidential 10

Sujit Suman Project Manager SAP Vital Wires

Sign-off (Approval) for this document:

Vital Wires Confidential 11

Vital Wires Confidential 12

Flow Chart Legend

SAP foreground SAP background SAP Sub process-

SAP Sub process

Vital Wires Confidential 13

Name of Business Process: Organization Structure

Core To-Be Process

Organization elements involved

Vital Wires Confidential 14

3566 Molson Coors India Private Ltd

Company Code (BRD ID: 1.1, 1.2)

Company Code Description

3566 Molson Coors India Private Ltd

Vital Wires Confidential 15

Profit center Accounting (BRD ID: 40.1)

Profit center assignment

Profit and loss statement by profit centre

Balance sheet by profit center

System Configuration Considerations

File Conversion Considerations

Any Reports required related to current business process

Any Document / Output would be printed for this business process

Vital Wires Confidential 17

 Logistics, Finance activities are get integrated

Finance– Master Data

Module: Finance Sub module: Master Data

Version Change Prepared By Date

1 Initial Kanishk Kashyap 31.03.2019

Core To-Be Process

 General ledger master

Vital Wires Confidential 18

General ledger (BRD ID: 6)

Account Description From TO

General ledger master

Vital Wires Confidential 19

This view contains the basic information:

Only Manage Balances in Local Currency

Open item management

Vital Wires Confidential 20

 Sub-ledger integration information – such as asset account, customer account,