Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 91

________________________________________________________________________________

Business Blue Print


Molson Coors International, India SAP
Implementation – Project Sunrise

MM-BBP
Module: Materials Management

March 31, 2019

STATEMENT OF CONFIDENTIALITY / DISCLAIMER


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

Vital Wires Confidential Page 1


Contents
Document History..........................................................................................................................13
Introduction....................................................................................................................................14
Implementation Team....................................................................................................................15
Sign-off (Approval) for this document:.........................................................................................16
Glossary.........................................................................................................................................17
Flow Chart Legend....................................................................................................................17
Shape legend..........................................................................................................................17
...................................................................................................................................................17
...................................................................................................................................................17
Text Legend...............................................................................................................................17
Materials Management– Organization Structure...........................................................................18
Business Case............................................................................................................................18
AS IS Process............................................................................................................................18
Core To-Be Process...................................................................................................................18
Purchasing Organization (BRD ID: 1)..................................................................................18
Purchasing Group..................................................................................................................19
Plant (BRD ID: 2 & 3)...........................................................................................................19
Storage Locations (BRD ID: 2 & 3)......................................................................................20
Organization elements involved............................................................................................20
SAP Code...............................................................................................................................20
Open points............................................................................................................................20
System Controls.....................................................................................................................21
RICEF....................................................................................................................................21
Gaps.......................................................................................................................................21
System Configuration Considerations...................................................................................21
File Conversion Considerations.............................................................................................21
Any Reports required related to current business process.....................................................21
Any Document / Output would be printed for this business process....................................21
Integration aspects.................................................................................................................21
Authorization Considerations................................................................................................21

Vital Wires Confidential Page 2


Materials Management– Master Data............................................................................................22
AS IS Process............................................................................................................................22
 Material Master:..............................................................................................................22
 Service Master:...............................................................................................................22
 Vendor Master:...............................................................................................................22
Core To-Be Process...................................................................................................................22
Material Master: (BRD ID: 5 – 5.1)..........................................................................................23
Industry Sector.......................................................................................................................23
Material Type.........................................................................................................................23
Material Group:.....................................................................................................................25
Product Hierarchy:.....................................................................................................................25
Number ranges.......................................................................................................................27
Open points............................................................................................................................27
System Controls.....................................................................................................................27
WRICEF/GAPS.....................................................................................................................27
System Configuration Considerations...................................................................................27
File Conversion Considerations.............................................................................................28
Any Document / Output would be printed for this business process....................................28
Integration aspects.................................................................................................................28
Authorization Considerations................................................................................................28
Vendor Master (BRD ID: 5 – 5.2).............................................................................................28
Vendor Account Group:........................................................................................................29
Partner Function.....................................................................................................................29
Number ranges.......................................................................................................................29
Open points............................................................................................................................29
System Controls.....................................................................................................................29
WRICEF/GAPS.....................................................................................................................30
System Configuration Considerations...................................................................................30
File Conversion Considerations.............................................................................................30
Any Document / Output would be printed for this business process....................................30
Integration aspects.................................................................................................................30
Authorization Considerations................................................................................................30
Service Master (BRD ID: 5 – 5.4).............................................................................................30

Vital Wires Confidential Page 3


Number ranges.......................................................................................................................31
Open points............................................................................................................................31
System Controls.....................................................................................................................31
WRICEF/GAPS.....................................................................................................................31
System Configuration Considerations...................................................................................31
File Conversion Considerations.............................................................................................31
Any Document / Output would be printed for this business process....................................31
Integration aspects.................................................................................................................31
Authorization Considerations................................................................................................32
Source List.................................................................................................................................32
Number ranges.......................................................................................................................32
Open points............................................................................................................................32
System Controls.....................................................................................................................32
WRICEF/GAPS.....................................................................................................................32
System Configuration Considerations...................................................................................33
File Conversion Considerations.............................................................................................33
Any Document / Output would be printed for this business process....................................33
Integration aspects.................................................................................................................33
Authorization Considerations................................................................................................33
Purchase Info Record.................................................................................................................33
Number ranges.......................................................................................................................33
Open points............................................................................................................................33
System Controls.....................................................................................................................33
WRICEF/GAPS.....................................................................................................................34
System Configuration Considerations...................................................................................34
File Conversion Considerations.............................................................................................34
Any Document / Output would be printed for this business process....................................34
Integration aspects.................................................................................................................34
Authorization Considerations................................................................................................34
Material Management – Business Processes.................................................................................34
Domestic Procurement (BRD ID: 5 – 5.1)................................................................................35
AS IS Reference....................................................................................................................35
TO BE Process:......................................................................................................................35

Vital Wires Confidential Page 4


Open points............................................................................................................................36
WRICEF/GAPS (BRD ID: 8.4 & 36)....................................................................................36
Flowchart of Domestic Procurement:....................................................................................37
Flow Chart for Domestic Procurement with Scheduling Agreement:...................................38
Import Procurement (BRD ID: 9)..............................................................................................39
AS IS Reference....................................................................................................................39
TO BE Process:..........................................................................................................................39
Open points............................................................................................................................40
WRICEF/GAPS (BRD ID: 8.4 & 36)....................................................................................40
Flowchart of Import Procurement:........................................................................................41
Asset Procurement Process (BRD ID: 47 – 47.2).....................................................................42
AS IS Reference:...................................................................................................................42
TO BE Process:..........................................................................................................................42
Ref. to Internal Order (CWIP)...............................................................................................42
WRICEF................................................................................................................................43
Flowchart for Asset Procurement:.........................................................................................44
Sub-Contracting Procurement Process (BRD ID: 11)...............................................................45
AS IS Reference:...................................................................................................................45
TO BE Process.......................................................................................................................45
Open points............................................................................................................................46
WRICEF/GAPS (BRD ID: 8.4 & 36)....................................................................................46
Flowchart of Sub-contracting Process:..................................................................................47
Non-Valuated Material Procurement (BRD ID: 13).................................................................48
AS IS Reference:...................................................................................................................48
TO BE Process:......................................................................................................................48
Open points............................................................................................................................48
WRICEF/GAPS.....................................................................................................................48
Flowchart of Sub-contracting Process:..................................................................................49
Vendor Return Process (BRD ID: 15).......................................................................................49
AS IS Reference:...................................................................................................................49
TO BE Process:......................................................................................................................50
Flowchart for Goods Return with ref. to GR document:.......................................................50
WRICEF/GAPS (BRD ID: 36)..............................................................................................51

Vital Wires Confidential Page 5


Flowchart for Return Order Process:.....................................................................................51
External Service Procurement (BRD ID: 10)............................................................................52
AS-IS Reference:...................................................................................................................52
TO BE Process:......................................................................................................................52
Open points............................................................................................................................53
WRICEF/GAPS (BRD ID: 8.4 & 36)....................................................................................53
Flowchart for External Service Procurement Process:..........................................................54
Materials Management – Purchase Requisition (BRD ID: 8 – 8.1)..............................................54
Business Case............................................................................................................................55
AS IS Reference........................................................................................................................55
Master data required..................................................................................................................55
TO BE Process...........................................................................................................................55
Changes to Existing System..................................................................................................56
Interface/Development Requirements...................................................................................56
System Configuration Considerations...................................................................................56
Number Range.......................................................................................................................56
Open Points............................................................................................................................56
Gaps.......................................................................................................................................56
File Conversion Considerations.............................................................................................56
Reports required related to current business process.............................................................56
Document / Output would be printed for this business process............................................57
Integration aspects.................................................................................................................57
Authorization Considerations................................................................................................57
SAP Transaction Codes.........................................................................................................57
Materials Management – Outline Agreement (BRD ID: 8 – 8.3).................................................57
Business Case............................................................................................................................57
AS IS Reference........................................................................................................................57
Master data.................................................................................................................................58
Org Structure data......................................................................................................................58
TO BE Process...........................................................................................................................58
Scheduling Agreement:.........................................................................................................58
Contracts................................................................................................................................59
Changes to Existing System..................................................................................................59

Vital Wires Confidential Page 6


Interface/Development Requirements...................................................................................59
System Configuration Considerations...................................................................................59
Number Range.......................................................................................................................59
Open Points............................................................................................................................59
Gaps.......................................................................................................................................60
File Conversion Considerations.............................................................................................60
Reports required related to current business process.............................................................60
Document / Output would be printed for this business process............................................60
Integration aspects.................................................................................................................60
Authorization Considerations................................................................................................60
SAP transaction codes...........................................................................................................60
Materials Management – Purchase Order (BRD ID: 8 – 8.3 & 8.4).............................................60
Business Case............................................................................................................................61
AS IS Reference........................................................................................................................61
Master data.................................................................................................................................61
Org Structure data......................................................................................................................61
TO BE Process...........................................................................................................................61
Changes to Existing Organization.............................................................................................61
System Controls.....................................................................................................................62
Interface/Development Requirements...................................................................................62
System Configuration Considerations...................................................................................62
Number Range.......................................................................................................................62
Open Points............................................................................................................................62
RICEFW/Gaps.......................................................................................................................62
File Conversion Considerations.............................................................................................63
Reports required related to current business process.............................................................63
Document / Output would be printed for this business process............................................63
Integration aspects.................................................................................................................63
Authorization Considerations................................................................................................63
SAP transaction codes...........................................................................................................63
Materials Management – Purchase Pricing Procedure (BRD ID: 8-8.5).......................................63
Business Case............................................................................................................................64
AS IS Process........................................................................................................................64

Vital Wires Confidential Page 7


TO BE Process...........................................................................................................................64
Condition Tables:...................................................................................................................64
Access Sequence:...................................................................................................................64
Condition Type......................................................................................................................65
Schema Group:......................................................................................................................65
Pricing procedure...................................................................................................................65
Schema Determination...........................................................................................................65
Changes to Existing System..................................................................................................65
System Controls.....................................................................................................................66
Interface/Development Requirements...................................................................................66
System Configuration Considerations...................................................................................66
Number Range.......................................................................................................................66
Open Points............................................................................................................................66
RICEFW/Gaps.......................................................................................................................66
File Conversion Considerations.............................................................................................66
Reports required related to current business process.............................................................66
Document / Output would be printed for this business process............................................67
Integration aspects.................................................................................................................67
Materials Management – Purchase Release Procedure.................................................................67
Business Case............................................................................................................................67
AS IS Reference........................................................................................................................67
TO BE Process...........................................................................................................................67
Release procedure Structure consists of:...............................................................................68
Changes to Existing System..................................................................................................70
System Controls.....................................................................................................................70
Interface/Development Requirements...................................................................................70
System Configuration Considerations...................................................................................70
Number Range.......................................................................................................................70
Open Points............................................................................................................................70
RICEFW/Gaps.......................................................................................................................70
File Conversion Considerations.............................................................................................70
Reports required related to current business process.............................................................70
Document / Output would be printed for this business process............................................71

Vital Wires Confidential Page 8


Integration aspects.................................................................................................................71
Materials Management – Gate Pass Process (BRD ID: 12)..........................................................71
Business Case............................................................................................................................71
AS IS Reference........................................................................................................................71
TO BE Process...........................................................................................................................71
Changes to Existing System..................................................................................................72
System Controls.....................................................................................................................72
Interface/Development Requirements...................................................................................72
System Configuration Considerations...................................................................................72
Number Range.......................................................................................................................72
Open Points............................................................................................................................73
RICEFW/Gaps.......................................................................................................................73
File Conversion Considerations.............................................................................................73
Reports required related to current business process.............................................................73
Document / Output would be printed for this business process............................................73
Integration aspects.................................................................................................................73
Material Management – Inventory Management..........................................................................74
Batch Management: (BRD ID: 17)............................................................................................74
AS IS Process:.......................................................................................................................74
TO BE Process:......................................................................................................................74
Batch Determination..............................................................................................................75
Changes to Existing System..................................................................................................76
System Controls.....................................................................................................................76
Interface/Development Requirements...................................................................................76
System Configuration Considerations...................................................................................76
Number Range.......................................................................................................................77
Open Points............................................................................................................................77
RICEFW/Gaps.......................................................................................................................77
File Conversion Considerations.............................................................................................77
Reports required related to current business process.............................................................77
Document / Output would be printed for this business process............................................77
Integration aspects.................................................................................................................77
Goods Receipt (BRD ID: 16 – 16.1).........................................................................................77

Vital Wires Confidential Page 9


AS IS Reference:...................................................................................................................77
TO BE Process:......................................................................................................................78
SAP transaction codes...........................................................................................................78
Movement Types:..................................................................................................................78
Goods Return Process: (BRD ID: 15).......................................................................................78
TO BE Reference:..................................................................................................................78
TO BE Process:......................................................................................................................78
Reservations:..............................................................................................................................79
AS IS Reference:...................................................................................................................79
TO BE Process:......................................................................................................................79
SAP transaction codes...........................................................................................................79
Goods Issue (BRD ID: 16 – 16.4).............................................................................................80
AS IS Reference:...................................................................................................................80
TO BE Process:......................................................................................................................80
SAP transaction codes...........................................................................................................80
Flow Chart for Reservation and Goods Issue:.......................................................................81
Transfer Posting (BRD ID: 16 – 16.3).......................................................................................81
AS IS Reference:...................................................................................................................81
TO BE Process:......................................................................................................................81
Physical Inventory (BRD ID: 16 – 16.5)...................................................................................82
AS IS Process:.......................................................................................................................82
TO BE Process:......................................................................................................................82
SAP transaction codes...........................................................................................................83
Materials Management – Inventory Operations............................................................................84
Goods Receipt (BRD ID: 16 – 16.1).........................................................................................84
Initial Stock Entry......................................................................................................................84
Reservation Process...................................................................................................................84
Goods issue (BRD ID: 16 – 16.4)..............................................................................................84
Physical Inventory (BRD ID: 16 – 16.5)..................................................................................85
Changes to Existing System..................................................................................................85
System Controls.....................................................................................................................85
Interface/Development Requirements...................................................................................85
System Configuration Considerations...................................................................................85

Vital Wires Confidential Page 10


Number Range.......................................................................................................................86
Open Points............................................................................................................................86
RICEFW/Gaps.......................................................................................................................86
File Conversion Considerations.............................................................................................86
Reports required related to current business process.............................................................86
Document / Output would be printed for this business process............................................86
Integration aspects.................................................................................................................86
Materials Management – Vendor Invoice Verification (BRD ID: 43)..........................................86
Business Case:...........................................................................................................................86
AS IS Process:...........................................................................................................................87
TO BE Process:..........................................................................................................................87
Logistic Invoice Verification (BRD ID: 43 – 43.1)...................................................................87
Goods / Services Items:.........................................................................................................88
Planned Delivery Costs:........................................................................................................88
Goods / Services Items + Planned Delivery Costs:...............................................................88
Logistics invoice verification facilitates four different activities:.............................................88
Invoice...................................................................................................................................88
Credit memo (BRD ID: 43 – 43.5)........................................................................................88
Subsequent debit....................................................................................................................88
Subsequent credit...................................................................................................................89
Invoice reduction.......................................................................................................................89
Other features of Vendor Invoice Verification..........................................................................89
Tolerance...............................................................................................................................89
Unplanned Delivery Costs.....................................................................................................89
Changes to Existing System..................................................................................................89
System Controls.....................................................................................................................89
Interface/Development Requirements...................................................................................89
System Configuration Considerations...................................................................................90
Number Range.......................................................................................................................90
Open Points............................................................................................................................90
RICEFW/Gaps.......................................................................................................................90
File Conversion Considerations.............................................................................................90
Reports required related to current business process.............................................................90

Vital Wires Confidential Page 11


Document / Output would be printed for this business process............................................90
Integration aspects.................................................................................................................90

Vital Wires Confidential Page 12


Document History
Version Release Date Author Reviewed By Change Description /
Comment

1.0 Arminder Singh Sujit Suman Initial Draft

1.1 Arminder Singh Sujit Suman Revised Version after


Review on 23/04/2019

1.2 Arminder Singh Sujit Suman Revised with BRD ID on


06/05/2019

1.3 Arminder Singh Sujit Suman Revised with Org Structure,


Service Master on
03/06/2019

Vital Wires Confidential Page 13


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.

Vital Wires Confidential Page 14


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

Vital Wires Confidential Page 15


Sign-off (Approval) for this document:
Name of Team Member Organization / Role Signatures
Paul D'Silva CEO - Molson Coors India
Jeanne Cate 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
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

Vital Wires Confidential Page 16


Glossary

Flow Chart Legend

Shape legend

Decision
Box Start/Stop of Documents
Process Flow

Processes to be executed Sub Processes Comments / Details for the


process

Text Legend
Short Form Full Form
MM Materials Management
PO Purchase order
IBD Inbound Delivery
MAP Moving average price
STO Stock transport order
GR Goods receipt
GI Goods issue
IR Invoice receipt
SA Scheduling Agreement
PI Physical Inventory
PR Purchase Requisition
IV Invoice verification

Vital Wires Confidential Page 17


Materials Management– Organization Structure
TO-BE Document For SAP Implementation at Cosmetics Trading LLC
Name of Business Process: Organization Structure
Module: Materials Management 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 Arminder Singh 31.03.2019

Business Case
Molson Coors International, India Procures Raw Material, Packing, Spares, Consumable, etc.
from Principal, Import and Local Vendor. These Materials can be used for internal consumption
or sales.

AS IS Process
Molson Coors India head office is located in New Delhi, Procurement is done both centrally
from HO and as well as from Manufacturing Plants. There are two entities for MCI India, but
production and procurement generally happens in Molson Coors India Pvt. Ltd., other entity is
Molson Coors Cobra India Pvt. Ltd.

Core To-Be Process


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
are the organization levels in SAP

Purchasing Organization (BRD ID: 1)


Purchasing Organization is an organizational unit which is responsible for procuring Materials or
services for one or more Plants and for negotiating general conditions of purchase with vendors.
The purchasing organization assumes legal responsibility for all external purchase transactions.
 Purchasing Organization can be assigned to one or multiple Company Code
 It can also be assigned to different Sites within a Company Code

In case of MCI India we will be having Two purchase organizations one for Molson Coors India
and other for Molson Coors Cobra at the corporate levels.
Purchase Organization Description
3566 Molson Coors India
3565 Molson Coors Cobra

Vital Wires Confidential Page 18


Purchasing Group
A “purchasing group” in SAP is a key for a buyer or group of buyers responsible for certain
purchasing activities. The purchasing group is: (a) internally responsible for the procurement of a
material or a class of materials, and (b) the principal channel for a company's dealings with its
vendors.

In case of MCI India we will be having multiple purchase group created with respect to
department, the following purchase Group will be created and will be used for procurement
process.
S. Purchase Group Description
No.
1 I01 Finance
2 I02 Prod. Engineering
3 I03 Production
4 I04 Marketing
5 I05 Admin
6 I06 IT
7 I07 Miscellaneous
8 I08 Others

Plant (BRD ID: 2 & 3)


Plant is an organizational unit within Logistics, serving to subdivide an enterprise according to
production, procurement, maintenance, and materials planning.

A plant is a place where either material is produced, or goods and services are provided. The
plant is embedded in the organizational structure as follows:
 The plant is assigned to a single company code. A company code can have several plants.
 Several storage locations in which material stocks are managed can belong to a plant.
 A plant has its own material master data. You can maintain data at plant level for the
following views on a material master record in particular: MRP, Purchasing, Storage,
Production resources/tools, Forecasting, Quality management, Sales, Costing.

For MCI India, all Manufacturing Units, Head Office, Depots/Marketing Office will be created
as Plants.

Vital Wires Confidential Page 19


S. SAP Name Description Company
No. Code
1 3566 MCI Head Office 3566
2 3567 MCI Bhankarpur 3566
3 3568 MCI Punjab Depot 3566
4 3569 MCI Saha 3566
5 3570 MCI Haryana Depot 3566
6 3571 MCI UP Factory (Upcoming) 3566
7 3572 MCI UP Depot 3566
8 3573 MCI Delhi Depot 3566
9 3574 MCI Chandigarh Depot 3566
10 3575 MCI Himachal Pradesh 3566
Depot
11 3576 MCI J&K Depot 3566
12 3577 New Market 1 3566
13 3578 New Market 2 3566
14 3579 New Market 3 3566
Storage 15 3580 Micro Brewery 1 3566
16 3581 Micro Brewery 2 3566
17 3582 Tap Room 1 3566
18 3583 Tap Room 2 3566
19 3584 Contract Manufacturing 3566
20 3565 MCC Bihta Patna 3565
Locations (BRD ID: 2 & 3)
Storage Location is an organizational unit facilitating differentiation between the various stocks
of a material within a plant. These are the smallest unit in an organization hierarchy.

 There may be one or more storage locations within a plant


 Storage location is the place where stocks are physically kept within a plant.
 Stocks are managed only on a quantity basis and not on a value basis at storage location
level.
 Physical inventories are carried out at storage location level.

List of Storage Locations Plant wise has been attached.

Organization elements involved


 Purchasing Organization: responsible for procurement
 Plant: a physical location under a company code which can be a Manufacturing unit or a
Depot

Vital Wires Confidential Page 20


 Storage Location: The stock is Physically kept within Plant
 Purchase group: Individual or group of buyers
 Company code: Smallest independent legal entity for financial accounting

SAP 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
None

System Controls
 Transaction can be restricted to purchase organization and purchase group for which
the users are authorized.
 Purchase reports can be restricted based on Purchase organization, purchase group and
Plants for which the users are authorized.
 Inventory reports can be restricted based on the Plants for which the users are
authorized.
 Segregation of stocks with in the Plant possible.

RICEF
None

Gaps
None

System Configuration Considerations


Define Plant Codes.
Define Purchase Organization
Define Storage Locations for Plant code.
Assign Plant to Company code
Assign purchase organization to Plant & company code
Define Purchase Groups.

File Conversion Considerations


None

Any Reports required related to current business process


None

Any Document / Output would be printed for this business process


None

Vital Wires Confidential Page 21


Integration aspects
 None

Authorization Considerations
Will be finalized and handled during realization phase

Materials Management– Master Data


TO-BE Document For SAP Implementation at Molson Coors India
Name of Business Process: Master Data

Module: Materials Management Sub module: Purchase & Inventory Management

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 Arminder Singh 31.03.2019

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.

 Material Master: In MCIPL, Material master gets created by IT Team in IBMS system. Brand
and State wise material created at MCIPL. Some of the Key Materials used in MCIPL are
categorised as Raw Material (Malt, Broken Rice, Sugar, Rice Flex, Hops, Enzymes, etc.);
Packing Material (New Bottle, Cans, Market Return Bottle, Wrinkle Caps, Cartons, etc.);
Finished Goods (Miller Ace, Thunder Bolt, Carling, etc.)
 Service Master: In MCIPL, Service master gets created by IT Team in IBMS system and is
being used in service order to procure services.
 Vendor Master: In MCIPL, Vendor Creation process is centralized and maintained in IBMS
system
o Vendor Creation form filled by vendor was sent to Procurement team at HO.
o Risk analysis of vendor to be done through KROLL system, vendor receive the link
with the questionnaire and has to submit the answers, based on those answers,
vendor gets rating.
o If the Risk rating of the vendor is High, then legal department will cross check the
vendor and has to approve whether the purchase department can proceed with
the vendor creation or not.

Vital Wires Confidential Page 22


o If the Risk rating of the Vendor is low, then Procurement dept. is good to go with
the vendor for creation process
o Only vendor approved through KROLL system can be created in IBMS system

Core To-Be Process


Successful functioning of SAP are dependent on the most important part i.e. Master Data which
are broadly classified under

 Material Master
 Service Master
 Vendor Master
 Info Record
 Source List

Material Master: (BRD ID: 5 – 5.1)


The material master contains descriptions of all materials that an enterprise procures, produces,
and keeps in stock. It is the central repository of information on materials.
The material master is used by all components in the SAP Logistics System. The integration of
all material data in a single database object eliminates redundant data storage. In the SAP
Logistics System, the data contained in the material master is required, for example, for the
following functions:
 In Purchasing for ordering
 In Inventory Management for goods movement postings and physical inventory
 In Invoice Verification for posting invoices
 In Sales and Distribution for sales order processing

Material master has three characteristics.


 Industry Sector
 Material Types
 Material Groups

Industry Sector
Industry Sector in material master has specific importance. Industry Sector in material
determines:
 Which screen in material master need to appear in which order
 Which industry specific field appear on each screen
 The Industry sector you assign to material cannot be changed at any stage
 Industry Sector ‘C’ will be same as used in Global.

Material Type
Materials with the same attributes are grouped together and assigned to a material type .Any
material which is created in SAP will belong to a Material type.

Vital Wires Confidential Page 23


Material type controls following functions:
1. Number Ranges (Internal / External)
2. Field Selection Groups
3. Quantity / Value Update in different Plant
4. Internal / External Procurement
5. Views available (Purchase/ Sales /MRP/ Accounting etc.)

 Internal Material number range will be used for material code with Code length ‘7’
digits.

Following material types will be created for MCI India


Material Type Description No. Range (From / To) Qty./Val Update
ZFGS Finished Goods Both
ZSFG Semi-Finished Goods Both
ZRAW Raw Material Both
ZPKG Packaging Material Both
ZCON Consumables/Utility Both
ZSPC Spares & Components Both
ZSCR Scraps Both
ZOPS Operating Supply Both
ZMKT Promo Items Both
ZMSC Miscellaneous Items Both
ZNVM Non-valuated Materials Qty. only
ZCAP CAPEX Items Both

Material valuation is the determination of the value of a stock of materials. The valuation
relevant data on a material include:
 Valuation price
 Assignment to a valuation class, Valuation class is used to determine the G/ L account
during the material movement.
 Price Control: The price control of a material determines whether the material is
valuated at the standard price, the periodic unit price, or the moving average price.
These control parameters are in the Accounting view of the material’s master record.
You can specify the default price control that is used when a material is created in
material Type

Valuation using a standard price has the following features:


 All inventory postings are carried out at the standard price.
 Variances are posted to price difference accounts.
 Variances are updated.
 Price changes can be monitored.

Valuation using a moving average price results in the following:


Vital Wires Confidential Page 24
 Goods receipts are posted at the goods receipt value.
 The price in the material master is adjusted to the delivered price.
 Manual price changes are usually unnecessary. However, they are possible.

 Following Valuation Classes will be created for material types and all
material types will be valuated except Non-valuated material type.
 Valuation class code will be decided by configuration team
Material Type Price Control Valuation Class
Finished Goods S Finished Goods
Semi-Finished Goods S Liquid, Others
Raw Material S Raw Material
Packaging Material S Bottle New, Bottle Old, Can, Others
Consumables/Utility S Consumables
Spares & Comp. S Spares
Scraps S Scrap
Operating Supply S Operating supplies
Promo Items S Promo Items
Miscellaneous Items S Miscellaneous Items
Non-valuated
CAPEX Items S CAPEX Items

Material Group:
Materials which are having same characteristics are grouped together and assign to a material
group in SAP. Irrespective of the material type two materials can belong to same material group
if both have same characteristics.
 Material groups are defined at client level.
 Material group is basically used to classify materials for reporting/ classification
purposes. And is not a control function like material type.

List of Material Group to be created for MCI India will be provided by Business Team.

Product Hierarchy:
Product hierarchy is an alphanumeric character string used for grouping materials. The product
hierarchy groups materials by combining different characteristics & each level signifies a certain
characteristic of the product.
 At MCI India, Product hierarchy level to be used will be same as used globally.

Following Structure/levels will be used for Product hierarchy at MCI India.


The structure is                                                             Example
        Level1 Family BLUE MOON FAMILY
        Level 2 >> Brand  BLUE MOON BELGIAN WHITE ALE
        Level 3 >>> Container BOTTLE 330ml
        Level 4 >>>> Size  12 OZ
        Level 5 >>>>> Retail Wrap 06PK CARRIER

Vital Wires Confidential Page 25


        Level 6 >>>>>> Alcohol Content >4.0% BY WEIGHT

List of Product Hierarchy to be created for MCI India to be provided by Business Team

Detail of Material Master View


Material Master View Fields
Material Description
Basic Unit of Measure
Material Group
Basic Data 1 Old Material Number
X- Plant Material Status- Blocking option
General item category
Gross Weight, Net Weight, Volume
Basic Data 2 Contains Design Drawing information
Basic unit of measure
Purchasing Group
Plant – Specific – Material Status - Blocking option
Source list
Batch Management – Automatic PO
Purchasing Purchasing Value Key
GR Processing time (number of days required after receiving a
material for inspection & then placed into the storage location)
Critical Part
Manufacturer Part Number
Manufacturer
Sales Refer Sales BBP
MRP Refer PP BBP
Basic Unit of measure
Temperature conditions
Storage Conditions
General Plant Data Storage 1 Container Requirements
Hazards Material Number
Batch Management
SLED (Shelf Life Expiration Date)
Plant
General Plant Data Storage 2 Gross Weight, Net Weight
Profit Centre
Valuation Class
Price control
Accounting 1 Price Unit, Valuation Category
Moving & Standard Price
Total Stock, Total Value
Tax Price 1,2,3
Accounting 2 Commercial Price 1,2,3
LIFO Pool
Costing 2 Planned Price 1 (Moving average Price)
Planned Price date 1

Vital Wires Confidential Page 26


Planned Price 2 (Latest Price)
Planned Price date 2

Following views will exist for each material type:

Material Views Material Types


Basic Data View All Material Types
Purchasing All Material Types
Classification FG/SFG/RM/PM/Consumables
Purchasing View All Material Types
MRP View For RM/PM/FG/SFG/Spares
Sales View For All Material Types except SFG
Work scheduling View For FG / SFG
General Plant Data View All Material Types
Quality View
Accounting View All Material Types except Non-
valuated
Costing View All Material Type except Non-
valuated

Standard field status group will be used as of now, changes to Field Status group will be
finalized at time of testing.

Changes to existing organization


 New Material type will be created
 New Material groups will be created in SAP
 New Product hierarchy will be created for material master
 Reporting can be done based on product hierarchy assigned to material master

Number ranges
Number ranges to be assigned to Material Types will be decided by Configuration team at time
of Realization.

Open points
None

System Controls
 Only authorized personnel can create Master Data.
 Material can be procured only if it is created for Plant.
 The system will not allow the user to save the material master, vendor master, purchase
info record if mandatory fields are not filled.

Vital Wires Confidential Page 27


WRICEF/GAPS

S. No. Description of RICEFW Object


1 LSMW to upload 2 additional fields in Material Master Conversion

System Configuration Considerations


 Creation of Account Cat. Ref.
 Creation of Valuation class against Acc. Cat. Ref.
 Creation of Material Types
 Maintenance of Qty./Value update for Material Type
 Material Specific Views to be maintained.
 Making the necessary fields mandatory for the material type
o Control code for materials other than FG, SFG & Non-valuated
o Material Tax Indicator other than FG, SFG & Non-valuated
o Additional field to be identified for VAT commodity code
 Creation of material groups
 Creation of Product Hierarchy for all defined levels
 Creation of Brand codes for material master if any.
 Creation of material Tax Indicators (GST Configuration)

File Conversion Considerations


 Material Master Upload

Any Document / Output would be printed for this business process


None

Integration aspects
Material Master Integration with APO as product master.
Valuation classes used in material master will have integration with FI as GL for business
transaction will be assigned based on valuation classes.

Authorization Considerations
Will be handled during realization phase

Vendor Master (BRD ID: 5 – 5.2)


Vendor Master Data is the enterprise main source of vendor-specific data. It includes information
on vendors from which a company can procure, or can sell.
 A vendor master record contains information such as vendor's name, address,
reconciliation account, Purchase related data, etc.
 The vendor master record is maintained both by Accounting & Purchasing.

Vital Wires Confidential Page 28


Vendor registration process currently being followed at MCI will remain out of SAP and
approved vendor code will be created in the SAP.
Vendor master has two Pre-requisites:
 Vendor Account Group (Mandatory)
 Partner Function (Optional)

Vendor Account Group:


Vendor Number Ranges: When we create a vendor master record, every vendor is recognized
by a unique number known as the vendor number. Number ranges are assigned to vendor groups,
so each vendor group can only have one number range and all vendors created for that group will
share same number range.
 Vendor Number will be internal and will be of “10” characters.
Vendor Master views, and key fields

 Following Vendor Account Groups will be used for MCI India


Vendor Account Group Description Number Range (From / To)
ZDMG Domestic Goods Vendor
ZDMS Domestic Service Vendor
ZIMP Import Vendor
ZIMD Import Deemed Vendors
ZPLN Plant Vendors
ZTPV Transport Vendors
ZEMP Employee Vendors

Partner Function
Business Partner "vendor" can assume different roles in its dealings with another enterprise.
Accordingly, in a procurement transaction, the vendor is first the ordering address, then the
supplier of goods, then the invoicing party, and finally the payee. For this reason, several partner
roles (partner functions) can be assigned to the vendor.

One or more of these roles can also be assumed by other vendors. This data is used in the
associated downstream logistics and accounting functions.
 Standard Partner roles will be used at MCI India

Changes to existing system.


 New vendor Account groups will be created

Number ranges
Number ranges to be assigned to Vendor Account Groups will be decided by Configuration team
at time of Realization.

Vital Wires Confidential Page 29


Open points
None

System Controls
 Only authorized personnel can create Vendor Master Data.
 The system will not allow the user to save the vendor master if mandatory fields are not
filled.

WRICEF/GAPS

S. No. Description of RICEFW Object


1 LSMW to be used for Vendor Master Upload Template Conversion

System Configuration Considerations


 Creation of Vendor Account Group
 Number ranges to account group to be maintained.
 Creation of Payment terms
 Making the necessary fields mandatory for the Vendor Account group.
o Tax Number 3 field for India Vendor Groups

File Conversion Considerations


 Vendor Master Upload

Any Document / Output would be printed for this business process


None

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

Service Master (BRD ID: 5 – 5.4)


Service master record contains the details of all the services that can be procured from an
external vendor within an organization. It contains the description of services along with their
unit of measure.

Vital Wires Confidential Page 30


Service master record serves as a reference for creating service purchase order, but it is not
necessary.

Pre-Requisite for Service Master:


Service Category:  The service category is the most important criterion for structuring service
master records. The service category defines certain attributes of the service and has a following
control functions:
Service Category to be discussed with business
Valuation Class: valuation class is used for auto account determination and default valuation
class can be assigned to Service category.

Service Category Description No. Range (From / To) Valuation Class


ZCPS Consulting & Professional Consulting &
Services Professional Fees
ZRMS Repair & Maintenance Repair & Main.
Services Charges
ZMKT Marketing Services Marketing Fee
ZHKS Housekeeping Services Services others
ZOTH Other Services Services others

Changes to existing system


 New Service categories will be created

Number ranges
Number ranges to be assigned to Service categories will be decided by Configuration team at
time of Realization.

Open points
None

System Controls
 Only authorized personnel can create Service Master Data.
 The system will not allow the user to save the service master if mandatory fields are not
filled.

WRICEF/GAPS

S. No. Description of RICEFW Object


1 LSMW for Service Master Upload Template Conversion

Vital Wires Confidential Page 31


System Configuration Considerations
 Creation of Service Category
 Number ranges to Service Category group to be maintained.
 Creation of valuation class and there assignment to account category ref.
 Assignment of account category ref. to service category.
 Enable the SAC code at PO line item (GST Configuration)

File Conversion Considerations


 Service Master Upload

Any Document / Output would be printed for this business process


None

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

Source List
In industry, a particular material can be ordered from different vendors in different time
intervals. This information can be maintained in a list that is called as the source list.
 Source list includes a list of possible sources of supply for a material with Validity.
 Source list is maintained at Material/Plant level and can be copied from one plant to
another plant.
 Source list also ease the process of procurement, you can also list the scheduling
agreement of Vendor in source list and make it relevant to MRP. So, when MRP run
happen and auto schedule lines get created and materials can be received against
agreement, no need to create Purchase Order for same.
 Source list is also required for Auto PO creation process, as existing Contract can be
assigned to source list and when MRP runs, same agreement will be auto assigned to
Purchase Requisition and Auto PO can be then created based on the details in Agreement.
 Source List will be used by procurement team at MCI India

Changes to organization
 If made mandatory purchase order can be placed only after source listed.
 Can block purchase or article from specific vendor.

Vital Wires Confidential Page 32


Number ranges
Number ranges to be assigned to Source List will be decided by Configuration team at time of
Realization.

Open points
None

System Controls
 Only authorized personnel can create Master Data.
 The system will not allow the user to save the Master if mandatory fields are not filled.

WRICEF/GAPS
S. No. Description of RICEFW Object
1 BDC/BAPI for Source list upload Conversion

System Configuration Considerations


 Source List Number range to be maintained

File Conversion Considerations


 Source List Upload

Any Document / Output would be printed for this business process


None

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

Purchase Info Record


 Purchasing info record is maintained at the vendor/material/plant/Purchase Org. level.
 We can either maintain the Info Record manually or we can enable auto info update.
 It stores information like Order unit (if differ from base unit for that vendor), purchase
payment terms, Purchase group, and specifically Net Price of the material (and also price
structure if required.
 Standard info record will be used for MCI India

Changes to existing organization

Vital Wires Confidential Page 33


 Vendor and material can be linked.
 Order price history can be tracked
 List price can be maintained in the info record.
 Can be used for source determination.
 Pricing condition types can be defaulted during Purchase order creation.

Number ranges
Number ranges to be assigned to Purchase Info records will be decided by Configuration team at
time of Realization.

Open points
None

System Controls
 Only authorized personnel can create PIR Master Data.
 The system will not allow the user to save the purchase info record if mandatory fields
are not filled.

WRICEF/GAPS
None

System Configuration Considerations


 Number range for PIR document to be maintained.

File Conversion Considerations


 PIR Master Upload

Any Document / Output would be printed for this business process


None

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

Vital Wires Confidential Page 34


Material Management – Business Processes
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: MM – Business Processes

Module: Materials Management Sub module: Purchasing Process

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 Arminder Singh 31.03.2019

Domestic Procurement (BRD ID: 8)


Most of the Procurement in MCI India happens in Domestic, This Process will explain the flow
of the transaction need to be performed in SAP system for the Procurement of following
materials:
 Raw Material / Packaging Material / Consumables / Spares / Capital Items / Promo, etc.

AS IS Reference
 Domestic procurement at MCI India as is happens with Indent Raised by User Dept. as per
planning based on the AOP data, indent form filled manually after approval from dept.
head, Indent form sent to Store department for approval based on current available stock.

Vital Wires Confidential Page 35


 Quotations received from all vendors are compared, Competitive sheet created by Purchase
officer for vendor selection manually in Excel; and approved by 14 different approvers.
 In case of procurement of goods /services is of recurring nature and is being procured over
a period generally exceeding two months with similar terms and conditions, the
procurement shall be on the basis of a contract.
 Gate pass created for the vehicle when reached plant, If weight measure to be required,
Vehicle will be sent to weighment.
 Quality Inspection of the Goods will happen at un-loading point, documents will be
submitted to Quality Team, If Quality 'OK', Store will un-load the Goods and create a
Material Receipt Note (MRN) and receive the goods in IBMS
 Store will then Submit the MRN along with gate pass to the User dept. for verification and
validation, Once Approved, Store will the then lock the MRN in the system
 Once goods Received store will attached the MRN with Vendor Invoice and submit the
document to Finance Team for Payment Processing
TO BE Process:
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of all materials, Purchase Requisition can either be created manually for some
of the materials for which planning has not been done or for other RM/PM & other
materials it will be created through APO as per planning data.
 Create Scheduling Agreements / Contract: for most of the key materials, contracts will be
created and for some of the materials that are procured on regular basis from fixed vendors
where again and again PO needs to be submitted for ordering qty., scheduling agreement will
be used and vendor will be provided the schedule of delivery instead of PO. Contract will be
used for key materials and annual maintenances.
 Create Purchase Orders: PO will be used for ordering the Qty., no PO will be created
without reference document. All delivery costs can be entered in PO at time of creation.
 Gate Entry Process: Gate Entry Process will be used for tracking of the incoming and
outgoing material from the manufacturing plant, when material will reach at plant, user will
capture the vehicle details and other details like PO number and vendor invoice number, and
gate pass slip will be generated. This gate pass will be linked to Goods receipt note and user
will not be able to do goods receipt without gate pass number in manufacturing units.
Gate Pass is required as a statutory requirement also because, government official at
manufacturing plant can ask for the data of material goes in and out of plant anytime.
 Quality Inspection (manual-out of system): QI will happen manually as of now on phase I,
out of SAP. Some key quality parameter will be captured in material batch characteristic.
 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system.
Accounting Entry: INV stock acc. Dr.
GR/IR Clearing Cr.
Delivery Cost clearing Cr.
 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entry: Vendor Account Cr.

Vital Wires Confidential Page 36


GR/IR Clearing Dr.

Open points
 Gate Pass Process with weighment integration
 Scheduling Agreement Process
 Invoice Reduction Process

WRICEF/GAPS (BRD ID: 8.4 & 36)


S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Contract / Agreement Print Layout Forms
3 Delivery schedule Print Forms
4 Gate Pass Process Interface
5 Auto E-mail functionality to send documents to vendor Report
6 Purchase Register Report
7 User Exit for Ref. document in Purchase Order Enhancement
8 Gate Pass Print Forms

Vital Wires Confidential Page 37


Flowchart of Domestic Procurement:

Vital Wires Confidential Page 38


Flow Chart for Domestic Procurement with Scheduling Agreement:

Vital Wires Confidential Page 39


Import Procurement (BRD ID: 9)
Import Procurement in MCI India happens for few key materials,
 In Import purchase multiple vendors are involved at multiple stages like Goods
supplier (main vendor), overseas freight vendor, Custom vendor, custom clearing
agent, local freight vendor, etc.
This Process will explain the flow of the transaction need to be performed in SAP system for the
Procurement of following materials:
 Consumables
 Spares

AS IS Reference
 Import procurement at MCI India as is happens with Indent Raised by User Dept. as per
planning based on the AOP data, indent form filled manually after approval from dept.
head, Indent form sent to Store department for approval based on current available stock.
 RFQ to be created for the either MOLSON Coors own entity or globally approved vendor or
OEM (Materials can only be imported either from Molson Coors entity or globally approved
vendor or OEM); and approved by 14 different approvers.
 In case of procurement of goods is of recurring nature and is being procured over a period
generally exceeding two months with similar terms and conditions, the procurement shall
be on the basis of a contract. Purchase Order with reference to Contract can then be issued
to vendor for the delivery of the goods. Materials codes needs to be mentioned as per
FSSAI, Approval from Govt. to be taken regarding specific material which are not listed with
Govt. Or, directly Purchase Order can also be issued by the Purchase dept.
 Custom clearance of goods received will be done by third party carrier agency on behalf of
MCIPL and was later paid after delivering goods. Any additional charges bourn by
inadequate documents that cause delay in custom clearing of goods will be paid MCIPL
 Gate pass created for the vehicle when reached plant, If weight measure to be required,
Vehicle will be sent to weighment.
 Quality Inspection of the Goods will happen at un-loading point, documents will be
submitted to Quality Team, If Quality 'OK', Store will un-load the Goods and create a
Material Receipt Note (MRN) and receive the goods in IBMS
 Store will then Submit the MRN along with gate pass to the User dept. for verification and
validation, Once Approved, Store will the then lock the MRN in the system
 Once goods Received store will attached the MRN with Vendor Invoice and submit the
document to Finance Team for Payment Processing

TO BE Process:
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of all materials, Purchase Requisition can either be created manually for some
of the materials for which planning has not been done or for other RM/PM & other
materials it will be created through APO as per planning data.

Vital Wires Confidential Page 40


 Create Contract: for most of the key materials, contracts will be created and for some of the
materials that are procured on regular basis from fixed vendors. Contract will be used for key
materials.
 Create Purchase Orders: PO will be used for ordering the Qty., no PO will be created
without reference document. All the delivery costs like Custom, CVD, Certificate charge and
other import duties paid can be listed/mention in the PO itself, those duties can then be
loaded on material at time of receipt.
 Gate Entry Process: Gate Entry Process will be used for tracking of the incoming and
outgoing material from the manufacturing plant, when material will reach at plant, user will
capture the vehicle details and other details like PO number and vendor invoice number, and
gate pass slip will be generated. This gate pass will be linked to Goods receipt note and user
will not be able to do goods receipt without gate pass number in manufacturing units.
Gate Pass is required as a statutory requirement also because, government official at
manufacturing plant can ask for the data of material goes in and out of plant anytime.
 Quality Inspection (manual-out of system): QI will happen manually as of now on phase I,
out of SAP. Some key quality parameter will be captured in material batch characteristic.
 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system.
Accounting Entry: INV Stock Account Dr.
GR/IR Clearing Acc. Cr.
Custom/Freight Clearing Cr.

 Custom Payment to Third party agency: Custom clearance is done by third party agency
responsible for clearing the goods and delivered to Plant, custom MIRO will be entered in
system after the receipt of the goods.
Accounting Entry: Custom Vendor Cr.
Custom Clearing Dr.
Import GST Dr.

 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system for main vendor who supplied the goods. Maker
and checker (park & post) will be used for better control purpose.
Accounting Entry: Vendor Account Cr.
Gr/IR Clearing Dr.
Open points
 Gate Pass Process with weighment integration
 Scheduling Agreement Process

WRICEF/GAPS (BRD ID: 8.4 & 36)


S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Contract / Agreement Print Layout Forms
3 Gate Pass Process Forms
4 User Exit for Ref. document in Purchase Order Interface
5 Gate pass print

Vital Wires Confidential Page 41


Flowchart of Import Procurement:

Vital Wires Confidential Page 42


Asset Procurement Process (BRD ID: 47 – 47.2)
Most of the Asset Procurement in MCI India happens in Domestic, This Process will explain the
flow of the transaction need to be performed in SAP system for the Procurement of Assets:
Asset can be procured in two ways:
 Ref. to Internal Order (CWIP)
 Direct Consumption on Asset Account

AS IS Reference:
 Asset procurement at MCI India as is happens with Indent Raised by User Dept. as per
asset requirement, indent form filled manually after approval from dept. head.
 Quotations received from all vendors are compared, Competitive sheet created by
Purchase officer for vendor selection manually in Excel; and approved by 14 different
approvers.
 Purchase Order will be issued to vendor for procurement of Asset, PO to be created with
account assignment either ‘A’ or ‘F’.
 Gate pass created for the vehicle when reached plant.
 Quality Inspection of the Goods will happen and create Material Receipt Note (MRN)
and receive the goods in IBMS.
 Store will then Submit the MRN along with gate pass to the User dept. for verification
and validation, Once Approved, Store will the then lock the MRN in the system
 Once goods Received store will attached the MRN with Vendor Invoice and submit the
document to Finance Team for Payment Processing

TO BE Process:
Ref. to Internal Order (CWIP)
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of all materials; Purchase Requisition will be created manually with account
assignment ‘F’.
 Create Purchase Orders: PO will be used for ordering the Qty., no PO will be created
without reference document. Account assignment to be used in PO will be ‘F’
 Gate Entry Process: Gate Entry Process will be used for tracking of the incoming and
outgoing material from the manufacturing plant, when material will reach at plant, user will
capture the vehicle details and other details like PO number and vendor invoice number, and
gate pass slip will be generated. This gate pass will be linked to Goods receipt note and user
will not be able to do goods receipt without gate pass number in manufacturing units.
 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system.
Accounting Entry: Internal Order Dr.
GR/IR clearing Acc. Cr.
 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entry: Vendor Account Cr.
GR/IR Clearing Dr.

Vital Wires Confidential Page 43


Direct Consumption on Asset Account
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of all materials; Purchase Requisition will be created manually with account
assignment ‘A’.
 Create Purchase Orders: PO will be used for ordering the Qty., no PO will be created
without reference document. Account assignment to be used in PO will be ‘A’
 Gate Entry Process: Gate Entry Process will be manual and not in SAP system until BPO
decision on same. Gate Entry Process will be used for tracking of the incoming and outgoing
material from the manufacturing plant, when material will reach at plant, user will capture
the vehicle details and other details like PO number and vendor invoice number, and gate
pass slip will be generated. This gate pass will be linked to Goods receipt note
 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system.
Accounting Entry: Asset Account Dr.
GR/IR clearing Acc. Cr.
 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entry: Vendor Account Cr.
GR/IR Clearing Dr.

WRICEF
S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Gate Pass Process Forms
3 User Exit for Ref. document in Purchase Order Interface
4 Gate Pass Print

Vital Wires Confidential Page 44


Flowchart for Asset Procurement:

Vital Wires Confidential Page 45


Sub-Contracting Procurement Process (BRD ID: 11)
Sub-Contracting Procurement also called Job Work Order in MCI India happens for one Key
material as of now, but same can be extended in future for FG, This Process will explain the flow
of the transaction need to be performed in SAP system for the Procurement of:
 Malt (Sub-con Material)

AS IS Reference:
 Raw Material gets procured through order from vendor and directly delivered to Sub-
contractor location, MCIPL does not receive the raw material at their own location
 Contract done between MCIPL & Sub-contractor regarding the raw material yield to be
supplied for the processing of sub-contracting material that to be received by MCIPL
 Sub-Contracting order issued to vendor with reference to contract for the receiving of semi-
finished Material (ex: Malt)
 If Over consumption of the raw material happen and desired qty. of processed material not
received, store will inform the Finance team & vendor will be sent a Credit Note for same.

TO BE Process
 Procurement of Barley: Barley will be procured using Domestic Procurement process, as
stock needs to be delivered directly to vendor, Sub-contracting Vendor will be entered at
item level and SC flag will be checked so, when GR for same will happen stock will appear as
Stock provided to vendor in system.
o If barley procured need to be delivered to more than one Sub-contracting vendor,
then multiple PO line item will be created with Qty. to be delivered to each vendor
and respective vendor code will be entered as SC Vendor at each line item of PO
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of sub-contracting material, Purchase Requisition can either be created
manually or through APO as per planning data.
 Create Scheduling Agreements / Contract: for the key materials like Malt, Contracts will
be used for procurement of malt, agreement created with vendor for the processing or Barley
into Malt. Item category ‘L’ will be used.
 Create Purchase Orders: PO will be used for ordering the Qty. and will be created with
reference to Contract; no PO will be created without reference document. Item category ‘L’
to be used in PO.
 Gate Entry Process: Gate Entry Process will be used for tracking of the incoming and
outgoing material from the manufacturing plant, when material will reach at plant, user will
capture the vehicle details and other details like PO number and vendor invoice number, and
gate pass slip will be generated. This gate pass will be linked to Goods receipt note and user
will not be able to do goods receipt without gate pass number in manufacturing units.
Gate Pass is required as a statutory requirement also because, government official at
manufacturing plant can ask for the data of material goes in and out of plant anytime.
 Quality Inspection (manual-out of system): QI will happen manually as of now on phase I,
out of SAP.

Vital Wires Confidential Page 46


 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system. At time of
Goods receipt, Sub-con material stock gets available and RM stock gets consumed.
Accounting Entries: Stock of Malt Dr.
Change in Stock Cr.
External service charge Dr.
Gr/IR clearing Cr.
RM stock Inv. Cr.
Sub-con con. RM Dr.

 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entries: Sub-con vendor Dr.
Gr/IR Clearing Cr.
Open points
 Gate Pass Process with weighment integration
 Scheduling Agreement Process
 Subsequent adjustments

WRICEF/GAPS (BRD ID: 8.4 & 36)


S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Contract / Agreement Print Layout Forms
3 Schedule Line Print Forms
4 Sub-contracting Challan Forms
5 Gate Pass Process Interface
6 User Exit for Ref. document in Purchase Order Forms
7 Auto E-mail functionality to send documents to Vendor
8 Purchase Register
9 Gate Pass print

Vital Wires Confidential Page 47


Flowchart of Sub-contracting Process:

Vital Wires Confidential Page 48


Non-Valuated Material Procurement (BRD ID: 13)
AS IS Reference:
Non-valuated materials are procured, user raise the indent manually requesting the material,
procurement team then issue the order to the vendor in IBMS system and when goods are
delivered, store dept. receive the material into store and then issue the material to the respective
dept.

TO BE Process:
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of all non-valuated materials; Purchase Requisition will be created manually
with account assignment category ‘K’.
 Create Purchase Orders: PO will be used for ordering the Qty., no PO will be created
without reference document. All delivery costs can be entered in PO at time of creation.
 Gate Entry Process: Gate Entry Process will be used for tracking of the incoming and
outgoing material from the manufacturing plant, when material will reach at plant, user will
capture the vehicle details and other details like PO number and vendor invoice number, and
gate pass slip will be generated. This gate pass will be linked to Goods receipt note and user
will not be able to do goods receipt without gate pass number in manufacturing units.
Gate Pass is required as a statutory requirement also because, government official at
manufacturing plant can ask for the data of material goes in and out of plant anytime.
 Goods Receipt at Plant: Goods Receipt note will be posted in SAP system.
Accounting Entry: Consumption acc. Dr.
GR/IR Clearing Cr.
Delivery Cost clearing Cr.
 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entry: Vendor Account Cr.
GR/IR Clearing Dr.

Open points
 Gate Pass Process with weighment integration

WRICEF/GAPS
S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Gate Pass Process Interface
3 Auto E-mail functionality to send documents to vendor Report
4 Purchase Register Report
5 User Exit for Ref. document in Purchase Order Enhancement

Vital Wires Confidential Page 49


Flowchart of Sub-contracting Process:

Vendor Return Process (BRD ID: 15)


The process of returning to the Vendor starts from the need to return an item to a vendor for any
reason, for example, defective quality.

AS IS Reference:
 When material received at plant, it goes to Quality check, if the Quality of material
received is “not OK” or as per agreed terms with vendor, Store creates a Material
Rejection Note (MRN) and returns the goods to vendor.
 Sometimes Material received by the store with quality OK, but later at time of Production
execution during the packaging process, materials seems to be of poor quality & online
rejection happen for that material, Vendor will be called for inspection of rejected material if
required.

Vital Wires Confidential Page 50


 If Vendor required the defected material to be returned, then MCIPL used to crush the
material before returning to vendor in order to avoid the re-delivery of defected material.
 Credit memo will be sent to vendors for rejected quantity.

TO BE Process:
Most of the Vendor Return in MCI India happens for Raw and Packaging Materials only, Vendor
credit memo to be raised in case of returns, In MCI, goods need to be received completely once
and then return need to be processed. This Process will explain the flow of the transaction need
to be performed in SAP system for the Vendor Return of following materials:
 Raw Material / Packaging Material / Consumables / Spares
Materials can be retuned in two ways:

With Reference to Goods Receipt Note:


At MCI India, if quality rejects the material due to reasons like poor quality, defective material,
etc.; Store user needs to return material to vendor with Material Reject Note. So store block the
Qty. and then return it to vendor against Material document. Credit note can be raised to vendor
for same.

Flowchart for Goods Return with ref. to GR document:

Return Order Process:


 In case the defective/damaged/poor quality stock is identified at a later stage but vendor
payment has been cleared in the system by that time, now user needs to return the stock
and raise the credit memo to vendor. In those cases, Return order will be created to vendor
for the damaged good.

Vital Wires Confidential Page 51


 Return delivery will be created against the return order to send the goods back to vendor.
Store location from where the goods will be picked for return will be entered in the delivery
and stock will be issued against the delivery.
Accounting Entry: INV Stock Account Cr.
GR/IR Clearing Dr.
 Gate Pass Process will be manual and not in SAP system until BPO decision on same. Gate
Entry Process will be used for tracking of the incoming and outgoing material from the
manufacturing plant, when material will reach at plant, user will capture the vehicle details
and other details like PO number and vendor invoice number, and gate pass slip will be
generated. This gate pass will be linked to Goods receipt note and user will not be able to do
goods receipt without gate pass number in manufacturing units.
Gate Pass is required as a statutory requirement also because, government official at
manufacturing plant can ask for the data of material goes in and out of plant anytime.
 Vendor Credit Memo will be then created after return delivery is posted and goods issued
to vendor, credit memo will be created against the return order, and amount will be
debited to vendor account
Accounting Entry: Vendor Account Dr.
GR/IR Clearing Cr.

WRICEF/GAPS (BRD ID: 36)


S. No. Description of RICEFW Object
1 Purchase Register
2 Gate Pass print

Flowchart for Return Order Process:

Vital Wires Confidential Page 52


External Service Procurement (BRD ID: 10)
External Service Procurement at MCI India happens for the Annual Maintenances, contract
labors, and other services.
This Process will explain the flow of the transaction need to be performed in SAP system for the
Procurement of following Services:
 Annual Maintenances
 Contract labours

AS-IS Reference:
 Indent Raised by User Dept. for the services required, indent form filled manually after
approval from dept. head
 RFQ creation and sent to respective vendors (RFQ need to be send to minimum 3 vendors),
Quotations received from all vendors and compared (quotations can be sent by vendors
again and again during negotiations)
 Comparative sheet created by Purchase officer for vendor selection; Choosing the right
supplier depends upon a wide range of factors such as value for money, quality, reliability
and service.
 In case of procurement of services is of recurring nature and is being procured over a period
generally exceeding two months like AMC with similar terms and conditions (e.g.; price,
scope of work etc.), the procurement shall be on the basis of a contract.
 Purchase Order with reference to Contract can then be issued to vendor for the delivery of
the goods
 Vendor Invoice will be submitted to Purchase, then purchase will submit the same to User
dept. for validation & User department approved service consumed as per checklist,
Attendance will be taken from Gate to validate.
 Service consumed entered in IBMS system and get approved from Dept. HOD
 User Dept. will then submit the Vendor Invoice and service receipt document to Finance
Team for Payment Processing

TO BE Process:
 Create Purchase Requisition: in SAP Purchase Requisition will be created for the
procurement of any type of services, Purchase Requisition will be created manually for
procurement of services, Item category “D” will be used and account assignment category
(‘K’, ‘F’, ‘A’, etc.) has to be selected while procuring the Services
 Create Contract: for most of the services, contracts will be created. Contract will be used
for annual maintenances and labors.
 Create Service Orders: Service Order will be used for ordering the Qty., no SO will be
created without reference document. All Planned costs can be entered in SO at time of
creation.
 Service Receipt (Service Entry Sheet): Service Entry sheet will be posted in SAP system
for the services consumed/availed by the user and will get approved from HOD
Accounting Entry: Consumption Acc. Dr.

Vital Wires Confidential Page 53


SR/IR Clearing Cr.
 Vendor Invoice Entry/verification: After goods have been received, Finance team will
enter the vendor Invoice in to SAP system. Maker and checker (park & post) will be used for
better control purpose.
Accounting Entry: Vendor Account Cr.
GR/IR Clearing Dr.

Open points
 Service Procurement Process

WRICEF/GAPS (BRD ID: 8.4 & 36)


S. No. Description of RICEFW Object
1 PO Print Layout Forms
2 Contract Print Layout Forms
3 User Exit for Ref. document in Purchase Order Enhancement
4 Auto E-mail functionality to send documents to Vendor Report
5 Purchase Register Report

Vital Wires Confidential Page 54


Flowchart for External Service Procurement Process:

Vital Wires Confidential Page 55


Materials Management – Purchase Requisition (BRD ID:
8 – 8.1)
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Purchase Requisition

Module: Materials Management Sub module: Purchasing

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 Arminder Singh 31.03.2019

Business Case
Purchase Request is created by respective department in case of any internal requirement arises
such as RM/PM Material, Fixed Asset, and Service Request from store or Consumables. The
Purchase Requisition will be converted to Purchase Document.

AS IS Reference
 In current system, Indent is created as per the AOP forecast for the material
requirement; Indent is then submitted to stores to check the available stock against
requirement before procurement process begins.
 Indent is created for procurement of all materials, Assets, Consumables and services.
Master data required
 Material Master
 Vendor master (in case of fixed or desired)

TO BE Process
A purchase requisition is a request or instruction to Purchasing department to procure a certain
quantity of a material so that it is available at a certain point in time. This is an internal document
and not used for outside communications.
 A purchase requisition is a request that is made to the purchasing organization to
procure a certain list of materials.
 It is an internal document and remains within the organization.
Purchase Requisition for MCI India will be created in two ways:
 Material Requirement Planning:
Purchase Requisition will be created automatically when MRP run will happen based on the
forecast/planning, system will consider the available stock, safety stock; reorder point, etc.
while creating the Purchase Requisition
 Manual Purchase Requisition:

Vital Wires Confidential Page 56


User can also create a Purchase Requisition manually for material required on urgent basis
or for whom MRP is not enabled.

Key Data to be entered while creating Purchase Requisition:


 Account Assignment Category: The account assignment category determines which
category of account assignment is to be debited and which account assignment data like
the cost centre or the asset number to be entered,
 Item category: Item category defines how the procurement of a material item is
controlled like, stock transfer, standard or consignment.
 Material Code: Number of the material required, user can search the same using help.
 Quantity: Quantity of the Material required, user needs to mention the Qty. as per the
unit in the material. If Order unit is different, unit conversion needs to be defined.
 Plant/Storage location: Code of the plant where material is required. Also if known user
can mention the Store where the material will be kept once received.

Changes to Existing System


Purchase Requisition is optional for creating import or local Purchase.

Interface/Development Requirements
None

System Configuration Considerations


 Define Document Types for Purchase Requisition
 Maintain Account assignment & Item Categories for Purchase Requisition
 Define Number ranges for Purchase Requisition

PR Doc No. Range


Description Acc. Assign. / Item Category
Type (From/To)
ZMR Material PR ‘ ‘ ; ‘K’, ‘M’, ‘P’, ‘Q’ / All except ‘D’
ZSR Service PR ‘K’, ‘M’, ‘P’, ‘Q’ / ‘D’, ‘B’
ZCAP CAPEX PR ‘A’; ‘F’ / All item category

Number Range
Number Ranges will be decided by configuration team at time of Realization.

Open Points
None

Gaps
None

Vital Wires Confidential Page 57


File Conversion Considerations
None

Reports required related to current business process


 ME53N: Display Purchase Requisition
 ME5A: List Display Purchase Requisition

Document / Output would be printed for this business process


None

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

SAP Transaction Codes


Description T. Code
PR creation ME51N
PR change ME52N
PR display ME53N
PR mass maintenance MEMASSRQ
PR individual release ME54N
PR collective release ME55

Materials Management – Outline Agreement (BRD ID: 8 –


8.3)
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Outline Agreement

Module: Materials Management Sub module: Purchasing

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 Arminder Singh 31.03.2019

Business Case
In case of procurement of goods /services is of recurring nature and is being procured over a
period generally exceeding two months with similar terms and conditions (e.g.; price, product

Vital Wires Confidential Page 58


specification, scope of work etc.), the procurement shall be on the basis of a contract. Contract
gets created for most of the key materials.

AS IS Reference
Currently Contracts are being used for the procurement of key materials; IBMS system is being
used for contracts creation. Purchase Orders are then created against contracts as per material
requirement.
Master data
 Vendor master
 Article master
 Purchase Info record

Org Structure data


 Plant Code
 Purchase Organization
 Purchase Group
 Tax Code

TO BE Process
Scheduling Agreement:
A scheduling agreement is a long-term agreement between the vendor and the ordering party
over a predefined material or service, which are procured on predetermined dates over a certain
period of time.
 With Scheduling Agreement we don’t need to create PO additionally each time material
is required, A schedule of the required Qty. with the delivery date/time can be generated
& provided to vendor.
A scheduling agreement can be created in the following way –

Creating a Scheduling Agreement:


Scheduling Agreement can either create with reference to Purchase Requisitions or RFQ
(Quotations).
Key data to be enter while creating SA.
 Organization Data, Master Data, Account Assignment {for direct consumption of
material other than stock (ex: for cost center use ‘K’ & for Asset use ‘A’ or ‘F’, etc.)},
Item Category, Quantity, Net Price, Collective number (can be used if created with ref. to
Quotation), Tax Details, Pricing (Base Price, discount, delivery costs), Incoterms (ex:
FOR, FOB, CIF, CFR)
Maintaining Scheduling lines for Agreement:
Once the scheduling Agreement is created, its delivery schedule is created in the system. There
are two ways to create the schedule lines:
 Automatically schedule lines will be created by system based on the forecast/planning,
for this we need to have Source list created for vendor and scheduling agreement

Vital Wires Confidential Page 59


assigned, Schedule lines will be generated directly from MRP (no Purchase Requisition
will be created).
 Manual schedule lines need to be generated by user, where Qty., delivery date/time need
to be specified manually to generate schedule.

Contracts
The contract is draft agreement, and they do not include delivery dates for the material. Contract
is two types:
 Quantity Contract: In this agreement Qty. to be procured is known but value may
vary at time of ordering the goods. Qty.in this contract is mandatory field.
 Value Contract: This contract  considered to fulfilled when the company supplied
agreed total value of material against the contract. In this type of agreement price is
negotiated with the vendor for a period of time but Qty. will be order as per the
requirement. Net price field is mandatory.
 Contracts can either created with reference to Purchase Requisitions.
 Purchase Order has to be created against the contract for the delivery of the goods.

Key data to be enter while creating Contracts.


 Organization Data, Master Data, Account Assignment {for direct consumption of
material other than stock (ex: for cost center use ‘K’ & for Asset use ‘A’ or ‘F’, etc.)},
Item Category, Quantity, Net Price, Collective number (can be used if created with ref. to
Quotation), Tax Details, Pricing (Base Price, discount, delivery costs), Incoterms (ex:
FOR, FOB, CIF, CFR).

Changes to Existing System


 Online processing of RFQ’s Process in SAP system.

Interface/Development Requirements
None

System Configuration Considerations


 Define Document Types for Contracts & Scheduling Agreements
 Define Number ranges for Document types created
 Output determination for agreement
 Assignment of Ref. Document type to new document types created.
RFQ Doc. Type Description Ref. Doc Type (PR)

ZLPA Scheduling Agreement ZMR, ZSR, ZCAP


ZWKI AMC / Value Contract ZMR, ZSR, ZCAP
ZMKI Quantity Contract ZMR, ZCAP

Vital Wires Confidential Page 60


Number Range
Number Ranges will be decided by configuration team at time of Realization.

Open Points
None

Gaps
Auto e-mail functionality to send Contracts to vendors;
Auto e-mail functionality to send Scheduling Agreements & Delivery schedule to vendors.

File Conversion Considerations


None

Reports required related to current business process


 ME33K/ME33L: Contract & Scheduling agreement display
 ME3N: Purchasing Document per Vendor
 ME3M: Purchasing document per Material
 ME3K: Purchasing Documents per account assignment
 ME80FN: Purchasing Documents list

Document / Output would be printed for this business process


Contract & Scheduling Agreement Print Layout to be developed as per the format shared by
MCI India business team.
Print Layout of Delivery schedule to be decided by MCI India business team.

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

SAP transaction codes


Description T. Code
Agreement creation ME31K/ME31L
Agreement change ME32K/ME32L
Agreement display ME33K/ME33L
Agreement mass maintenance MEMASSPO
Agreement individual release ME35
Print Agreement ME9K

Vital Wires Confidential Page 61


Materials Management – Purchase Order (BRD ID: 8 –
8.3 & 8.4)
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Purchase Order

Module: Materials Management Sub module: Purchasing

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 Arminder Singh 31.03.2019

Business Case
A purchase order is a formal request or instruction from a company/purchasing organization to
a vendor or a plant to supply or provide a required quantity of goods at or by a defined period of
time.

AS IS Reference
Currently Purchase Orders are issued to vendor for procurement of material/service; IBMS
system is being used for PO creation and Print. Purchase Order approvals happen outside the
system. Purchase Orders are created against contracts or RFQ as per material requirement.

Master data
 Vendor master
 Article master
 Purchase Info record

Org Structure data


 Plant Code
 Purchase Organization
 Purchase Group
 Tax Code

TO BE Process
The Purchase Order can be used for a variety of procurement purposes. User can procure
materials for direct consumption or for stock. User can also procure services. Furthermore, the
special procurement types "Subcontracting", "Third-Party" (involving triangular business deals)
are possible.

Vital Wires Confidential Page 62


Purchase order is a formal request to the vendor to supply material or perform services at defined
terms & conditions. It is possible to create purchase order directly (without reference) or with
reference to a PR, RFQ, Agreement or another purchase order.

Changes to Existing Organization


 Approval of purchase order in the system through release strategy.
 3 way match between PO, goods receipt and vendor invoice for local vendors
 Provision to post subsequent credit/debit memo for the articles received
 Inbound delivery has to be created for import vendors and Goods Receipt performed
against inbound delivery.

System Controls
 Purchase order can be printed only after approval.
 Goods receipt quantity cannot be more than the PO quantity unless tolerance is given
for the item.
 Invoice verification is based on the goods received for vendors.

Interface/Development Requirements
None

System Configuration Considerations


 Define Document Types for Purchase Order
 Define Number ranges for Document types created
 Assignment of Ref. Document type to new document types created.
 Output determination for purchase order.
 Set Tolerance Limits for Price Variance
 field selection of Standard document type to be used for Interco. STO
PO Doc. Description Ref. Doc Ref Doc Type Item Category/Acc. Assign.
Type Type (PR) (Con/SA) Allowed
ZDOM Domestic PO ZMR ZLPA, ZWKI, ZMKI All except ‘L’; ‘D’ / ‘A’, ‘F’
ZIMP Import PO ZMR, ZSR All except ‘L’; ‘D’ / ‘A’, ‘F’
ZWSO Service Order ZSR ‘D’, ‘B’
ZCAP CAPEX PO ZCAP All item /‘A’; ‘F’
ZRET Return PO
ZFR Freight PO ‘D’
ZJOB Job Work ZMR ZLPA, ZMKI ‘L’
Order
ZSTO Stock Transfer ZMR ‘U’
Order
ZSTC Interco. STO ZMR ‘U’

Vital Wires Confidential Page 63


Number Range
Number Ranges will be decided by configuration team at time of Realization.

Open Points
None

RICEFW/Gaps
S. No. Description of GAP/RICEFW Object

1 PO Print Layout Forms


2 Auto e-mail to send PO to vendor Report
3 Purchase Register Report

File Conversion Considerations


None

Reports required related to current business process


 ME23N: Purchase Order display
 ME2N: Purchasing Document per Vendor
 ME2M: Purchasing document per Material
 ME2K: Purchasing Documents per account assignment
 ME80FN: Purchasing Documents list

Document / Output would be printed for this business process


Purchase Order Print layout as per format shared by MCI India business team.

Integration aspects
None

Authorization Considerations
Will be handled during realization phase

SAP transaction codes


Description T. Code
PO creation ME21N
PO change ME22N
PO display ME23N
PO mass maintenance MEMASSPO
PO individual release ME29N
PO collective release ME28
Print PO ME9F

Vital Wires Confidential Page 64


Materials Management – Purchase Pricing Procedure
(BRD ID: 8-8.5)
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Purchase Pricing

Module: Materials Management Sub module: Purchasing

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 Arminder Singh 31.03.2019

Business Case
When material is procured different delivery charges other than base price are incurred by the
logistics team to ship the goods from the vendor location to Warehouse. These additional charges
incurred should add to the cost of item and liability should be created for the service provider.

AS IS Process
Vendor sends the invoice before receiving the material at plant and the freight vendors sends the
freight invoice. If there is any change in the cost prices then inventory cost is posted based on
vendor invoice and delivery cost.
In case of Old Bottle purchases, margin money concept is being used and tax calculation happens
on same. Currently Pricing in IBMS system has limited or few components to capture cost.

TO BE Process
Condition Tables:
Condition Table is the combination of Fields based on which the Price for the particular
condition will be determined.
 for ex: if we have condition table with fields Plant & material, so we can maintain a rate that
for Plant P1 and Material M1, discount will be 5%
 We can create condition table with any number of fields, basis which we want the system to
derive the rate for particular conditions. Number of Condition tables can be created as per the
business requirements.
 Condition Records are maintained on the basis of fields available in Condition Table.
Following condition table to be created for MCI India:
o Material/Plant/Vendor
o Material/Plant
o Material

Vital Wires Confidential Page 65


Access Sequence:
The main concept of Access sequence is it’s the combination of condition tables, it searches
condition record for condition type from condition table. One access sequence can contain one or
multiple condition tables.
 Suppose we maintain 4 condition tables in one access sequence. Then when a condition
type will search for condition record via this access sequence, the access sequence will
allow searching only these 4 condition tables.
 Access Sequence is assigned to Condition Type.

Condition Type
 The individual conditions are described by means of condition types. There are condition
types for the gross price, various discounts and surcharges, freight charges, fixed costs, etc.
 The plus/minus sign determines whether a condition is treated as a negative or positive
amount. Negative amounts are discounts (deductions), positive amounts are surcharges
(additions).
 Item conditions are conditions relating to a single item of a document.
 Header conditions are entered in the header of a document and relate to all the items of that
document.
 No automatic price determination process is carried out for header conditions

Schema Group:
Schema Group is defined for Vendor and Purchase Organization to link the Pricing Procedure.
 It is then assigned to our vendor and Purchase Organization; it helps the vendor and
purchase organization to choose pricing procedure.
 One schema group will be assigned to vendor and one schema group will be assigned to
Purchase organization. With this combination, system will fetch the pricing procedure.
 Each Pricing Procedure should have a separate Vendor schema group.

Pricing procedure
 A pricing procedure groups together all condition types that play a part in calculating the
price. It sets out the order in which the condition types are taken into account in the
calculation. In addition, the calculation schema specifies the following:
 Which subtotals are arrived at
 To what extent the price determination process can be carried out manually
 The basis upon which the system calculates percentage discounts and surcharges

Schema Determination
We maintain calculation schema with the combination of schema group and purchase
organization schema group.
 Vendor Schema Group is assigned to each vendor created in SAP.
 Purchase Organization schema group is assigned to Purchase Organization.

Vital Wires Confidential Page 66


 So, when we select the vendor in the Purchasing document and enter the Purchase
Organization, based in the combination of schema groups mapped, system will determine the
Pricing procedure for the document.

Changes to Existing System


 Conditions can be given in purchase order
 Standard freight and delivery charges to be maintained during purchase order creation
 If delivery costs are known landed cost can be calculated in PO
 Custom duty to be entered in PO and can also be defaulted per material

System Controls
 Conditions can be automated
 Certain conditions can be made mandatory.
 Condition types that are populated by the system can be restricted to manual changes.
 Conditions cannot be changed during GR.

Interface/Development Requirements
None

System Configuration Considerations


 Creation of condition tables
 Creation of Access sequence for MCI India
 Creation of Condition type and assignment of access sequence in same.
 Creation of Transaction Event Keys
 Creation of required routines for assignment to respective condition types
 Creation of Pricing Procedure using the condition types and accrual keys created
 Creation of Vendor schema and Purchase Org. schema
 Schema determination to be configured to determine the pricing procedure during
purchase order creation.

Attached pricing procedure for MCI India

Number Range
None

Open Points
None

RICEFW/Gaps
S. No. Description of GAP/RICEFW Object

Vital Wires Confidential Page 67


1 Volume based freight calculation Routine Routine
2 Req. routine for Overseas insurance condition based on Routine
Inco terms

File Conversion Considerations


None

Reports required related to current business process


 ME23N: Purchase Order display

Document / Output would be printed for this business process


Purchase Order Print layout will have some of the condition value printed.

Integration aspects
Accruals keys to be used will be assigned with GL accounts for FI postings

Materials Management – Purchase Release Procedure


TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Release Procedure (BRD ID: 8)


Module: Materials Management Sub module: Purchasing

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 Arminder Singh 31.03.2019

Business Case
Each Purchase orders created by Procurement department should be approved by the respective
managers or finance manager. Any changes to approved PO will require approval from same
authorities again.

AS IS Reference
Cost Comparative sheet & orders are manually signed by General Manager or Finance Managers
for Service, Consumables and Inventory orders.
Release Procedure at MCI India plays an important role in Procurement of Material & Services,
as different approval matrix has been defined based on Purchasing values.

TO BE Process
Release Procedure is the Approval Matrix used in the company for the approval of the key
documents. Releasing a document means approving it digitally.

Vital Wires Confidential Page 68


Release Procedure will be used for all following documents:
 Purchase Order,
 Contracts & Scheduling Agreements,
 Purchase Requisition,

Release procedure Structure consists of:


Release Characteristics:
Release Characteristics are the set of field in purchasing document based on which the system
decides to whom this document will go for approval.
Characteristics are generally the key fields in documents, like document type (domestic, import),
Purchase Groups (buyers), Net value of Purchasing document, Purchase Organization, Plant, etc.
Purchase Requisition will be approved at header level. Following three characteristics will
be used for purchase requisition:
 Document Type
 Purchase Group
 Plant

Existing PO characteristics will be used for PO Release Strategy.

Following three characteristics will be used for Service Entry sheet approval:
 Purchase Group
 Plant
 Value

Release Class
Each release procedure has certain characteristic based in which system determines it, those
characteristics are contained in a Class.
 All the characteristics created for Release procedure are grouped together in the
Release Class.
 Only the characteristic available in release class will be considered in the determination
of release procedure.
 Following Release Class already exist in the SAP system for purchasing documents.
PO_APPROVALS

 Existing Release Class will be used for Purchasing Documents - PO_APPROVALS.


 Following PR Release class will be used for PR Release Strategy
PR_APPROVALS

Rel. Class Char. 1 Char. 2 Char. 3


PR_APPROVALS Document Purchase Group Plant
Type
SES_APPROVAL SES Value Purchase Group Plant

Vital Wires Confidential Page 69


Release Groups:
 Release Groups defines the group of approvers for the documents subject to release
procedure.
 Release groups help to identify and differentiate the Set of Approvers in the
organization. For ex: we have different set of approver for RM procurement purchase
and Finished Goods procurement.
 We can create multiple release groups in the system. Release group code is of ‘2’
characters.
 Release class is assigned to Release Group. There can be only one Release class for all
Release groups.

Release Codes:
 The release code in SAP is the electronic signature replacing the handwritten approval
on a paper based process. Release Codes are created release group wise.
 Release Code in release procedure defines the approver of the document. Each
approver has a separate Release code.
 Release code is also an authorization control, as the user to whom the Release code has
been assigned will only be able to release the document. We can also assign one code to
more than one person if both of them have equal authority to approve.

Release Indicator:
Indicates release id for initial and released status whether document is blocked or in process of
release or Released.
SAP standard Release ID 0 indicates Blocked status and with release ID 1 it is Released status. 
Release Indicator has a Control function:
 The Changeability indicator contains the parameter which will define how the system
reacts if a purchasing document is changed after the start of the release procedure.
Means once the order is released, whether we can still change the values in purchase
order which will trigger a new release status. If the field is allowed to change, we can
define the % of change allowed.
 Release indicator ‘1 - no changes allowed’ will be used at final release for MCI India.

Release Strategy
Release Strategy is the actual structure where we define the Levels of approvers; in release
strategy we define which Approver will first approve the document and which after.
 SAP Standard system allows only ‘8’ levels of release codes i.e. documents can have max
‘8’ number of approvers.

Release Strategy to have some control functions like:


 Pre-requisites: This defines the functioning of approver levels, here you can allow if the
next level of approver can only approve the document after its preceding approver has

Vital Wires Confidential Page 70


already approved it. Or also, you can allow if any two or more of the approvers can
approve the document on same level.
 Release Status: This defines at what level of approval the document will be considered
to be status Final Release.

 2 levels of Approvers will be there in Purchase requisition Release Strategy.


 8 Levels of Approvers will be there for purchasing documents.
 1 levels of Approvers will be there in Service Entry Sheet

Changes to Existing System


 All Purchase Documents have to be approved in the system through release strategy
 External Service Entry sheet have to be approved in system
System Controls
 Conditions can be automated
 Certain conditions can be made mandatory.
 Condition types that are populated by the system can be restricted to manual changes.
 Conditions cannot be changed during GR.

Interface/Development Requirements
None

System Configuration Considerations


 Creation of Characteristics
 Creation of Release Class (class type 032)
 Release group configuration and assignment of Release class to same.
 Release Indicator with changeability indicator ‘1’
 Creation of New Release Codes
 Creation of new Release Strategy with release codes and release indicator.
 Maintenance of Release Strategy.

Attached Release Codes & Group need to be created for MCI India

Number Range
None
Open Points
None
RICEFW/Gaps
None

Vital Wires Confidential Page 71


File Conversion Considerations
None

Reports required related to current business process


 ME23N: Purchase Order display
 ME2N/ME3N/ME3LRelease Status of Purchasing Document
Document / Output would be printed for this business process
None
Integration aspects
None

Materials Management – Gate Pass Process (BRD ID: 12)


TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Gate Pass Process

Module: Materials Management Sub module: Inventory Operations

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 Arminder Singh 31.03.2019

Business Case
Gate entry is very critical in MCI India business as all the vehicles whether coming into plant or
goes out of the plant has to be recorded, at each plant excise officer can ask for the reporting of
vehicles goes in and out of the plant and Brewery team has to provide the same within certain
time period which is a statutory requirement. Also before dispatching the finished goods out for
Sale or stock transfer, permission from excise officer is required.

AS IS Reference
Gate Entry is being done manually on register, vehicles when reach plant, gate entry for same
has been done and vehicle goes for weight at weighbridge and weighbridge slip issued. Stock is
unloaded and vehicle has to return to weighbridge for tare weight and then while returning, gate
out entry will be done against same number.

TO BE Process
 Custom Solution of gate entry will be provided; user will capture all the required details of
gate entry into the custom screen against the Order number, and user can mention the Invoice
number and Qty. in the Gate entry screen.
 Gate Entry number will be generated and user can print the Gate pass slip from the system
and provide the same to the driver.

Vital Wires Confidential Page 72


 Store dept. can link the gate entry number to the Material Receipt document, for
manufacturing plant, gate entry number will be mandatory while goods receipt process
against purchase order.
 Gate Entry report will also be available to check the Open gate entries for which goods
receipt/issue has not been done.

Two different gate pass processes will be followed:


Inbound Process:
Details of vehicle will be captured into the system; user will enter the Order number against
which goods has been delivered, also vendor invoice number and qty. will be captured in the gate
pass, gate entry number will be generated. Status of gate entry will be open.
Slip will be printed and can be provided to the driver for further reference. Gate entry for
manufacturing plant will be mandatory.
Store dept. can link the same number while receiving goods into system, posting GRN.
Gate out will be captured once vehicle leaves the plant against same number and gate entry status
will be closed.
User can track the open gate entries from gate entry report.

Outbound Process:
Details of vehicle will be captured into the system; user will enter the permit/order number
against which goods need to be sent out of Plant. Gate entry number will be generated. Status of
gate entry will be open.
Slip will be printed and can be provided to the driver for further reference. Gate entry for
manufacturing plant will be mandatory.
Dispatch team will be able to link the gate pass number to the delivery and post goods issue
Gate out will be captured once vehicle leaves the plant against same number and gate entry status
will be closed.
User can track the open gate entries from gate entry report.

Integration to Weighbridge:
Gate pass process can also be integrated to weighbridge to capture the gross and tare weight of
the vehicles while coming in to plant and going out of the plant against the gate pass number

Changes to Existing System


 All vehicle details going in and out of plant will be captured in system
 Link of the gate pass number to the reference document for better tracking
 Reporting of each vehicle w.r.t. to purchase, sale or transfer of stock is available in system.

System Controls
 GR/GI of manufacturing plant will not be possible without gate pass number.

Interface/Development Requirements
 None

Vital Wires Confidential Page 73


System Configuration Considerations
 None

Number Range
 Number range for Gate pass will be decided by realization team

Open Points
 Gate Pass Process

RICEFW/Gaps
 Gate Pass Process
 Enhancement in MIGO for gate pass number field and making gate pass number
mandatory for India manufacturing Plants.
 Integration of Gate Pass with weighbridge

File Conversion Considerations


 None

Reports required related to current business process


 Gate Pass report

Document / Output would be printed for this business process


 Gate Pass Slip as per MCI India defined format

Integration aspects
 Weighbridge Integration

Vital Wires Confidential Page 74


Material Management – Inventory Management
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: MM – Business Processes

Module: Materials Management Sub module: Inventory Management

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 Arminder Singh 31.03.2019

Batch Management: (BRD ID: 17)


Batch Management incorporates the entire logistics process, from procurement to sales.  In a
process manufacturing environment, production is usually executed in batches. In addition, many
materials entering the process are managed separately in batch stocks with different
specifications.
Every batch of material in stock can be assigned with unique batch numbers and related
information can be stored and retrieved for reporting purposes.

AS IS Process:
 Currently in MCIPL, stock is managed as per the Material Receipt number, Store manage the
stock with respect to the material receipt number,
 Store assigns the MRN number to each lot in store location and with same they ensure the
FIFO consumption.
 When material is requested from store, store check the stock availability and then against
that the very first available Material receipt number to ensure FIFO consumption.
 With material receipt number, India business team is also managing the cost of the material
consumed.

TO BE Process:
A batch is a quantity of the material produced during a given production run. A batch represents
a homogeneous unit with unique specifications. A Batch is a subset of the total quantity of a
material held in stock. The subset is managed from all other subsets of the same material.
 Batch Management will be used for materials like Raw Material, Packing Materials, Spares,
Finished Goods and Semi-Finished Goods.
 Batch Management will be at Plant Level.
 The batch number can be reassigned for a material with a different specification in each
plant

Vital Wires Confidential Page 75


 Stock can be transferred from one plant to another between batches with the same
number, even though the batches do not necessarily have the same specification. In such
cases, the batch quantity transferred assumes the specification of the destination batch.
 Batch will be created at time of
o Goods Receipt from Purchase Order
o Goods Receipt from Production/Process Order
o Other Goods Receipt
o Transfer of Stock from one location to another
o Manual Batch record creation.
 Batch will be used for following reasons
o Traceability in case of complaint and recall issue.
o Shelf Life management of materials
o Search via manufacturing / expiration date
o Usage of batch characteristics to manage which batch fits to a specific requirement

Batch Characteristic:
Characteristics of batches are the features of the materials which differentiate the same materials
like variety, moisture, volume, etc.
These characteristics can be maintained at time of receiving the goods into inventory either from
vendor or from Production, these characteristics contain value that differ same materials with
different batch numbers
Batch characteristics will also be used to capture some key quality parameters at time of batch
creations, these parameters will be used for quality data analysis. Batch characteristics will be
material type wise.
 List of Batch characteristic material type wise will be provided by MCI India business
Team

Batch Classes:
Batch Class consists of the characteristics that need to be maintained at time of receiving the
materials. Multiple characteristics to be maintained in batch classes.
We can create number of classes as required for the materials (ex: production class, raw
materials class, packaging material class, etc.)
Batch Class type “023” will be used
Number of Batch classes to be created will be decided once list of batch characteristics are
received from MCI India Business team.

Batch Determination
Batch determination process is to identify the Batch in relevant area by using strategy types,
search strategies and search procedures. Batch determination procedures works similar to the
pricing procedure.
Batch determination will happen automatically in SAP, different search strategies will be created
for auto determination of Batch.
In order to have the batch determination in sales, we have to define following:
Vital Wires Confidential Page 76
 Condition Table: In Batch determination process, condition table consists of number
of field. Among those fields particular fields are selected and assigned to the
condition table.
o Condition table required for Material Type
 Batch determination access sequence: For each strategy type, there is a batch
determination access sequence. The main function of the access sequence is to allow
the strategy type to access the condition tables in the sequential manner.
 Access sequence will be created with condition tables defined
 Batch Strategy type: It is the procedure to select what type of criteria to be used
during batch determination process. Batch strategy can be defined for various
parameters like Movement type, Plant, storage location
Create a Batch strategy type and assign class to same. Number of strategy type as per
batch class
 Batch search procedure: Batch search procedure defines how the search procedure
is defined for the batches. Once you define the Search procedure you have to assign
the Strategy type. Batch search procedure is created to carry out the step by step
procedure to find out the particular batch
 Batch search procedure activation.

Batch determination will happen for following operations:


 Goods Issue of RM/PM/others at time of Production process
 Goods Issue of Finished Goods at time of Sales process
 Goods Issue of Material against Cost centre, other cost objects, etc.

Batch determination will happen automatically as per the batch search strategy maintained and
batch search records, Batch records will be determined based on FIFO/FMFO basis.

Changes to Existing System


 Batch will be created for the material and material will be managed in system generated
batches instead of MRN numbers
 FIFO consumption of batches will be ensured through automatic batch determination

System Controls
 Batch Conditions will be automated
 Some key batch characteristics will be mandatory for batch record creation.

Interface/Development Requirements
None

System Configuration Considerations


 Batch Activation at MCI India Plants
 Creation of Batch Characteristics
 Creation of Batch Class (class type 023)
Vital Wires Confidential Page 77
 Number ranges for Batch creation.
 Create Batch condition table
 Create batch access sequence
 Create batch search strategy type
 Assign batch strategy type to search procedure

Number Range
 Internal Number range will be used for batch number creation for Raw Material, Packaging
Material, and Spares & Semi-finished Goods/WIP Materials
 External Number range will be used for Batch creation of Finished Goods.
Below logic will be used to create External Number range for Finished Goods:
o Brand Code (2digit) / Excise Batch Code (2digit) / Production Date (6 digit, ex:
12032019)
o Finished Goods for Delhi will have excise batch code changed month wise for other
state it changes year wise and same to be incorporated for FG batch creation logic.
 Internal number ranges will be decided by configuration time at time of realization phase

Open Points
None

RICEFW/Gaps
Enhancement for automatic creation of Batch number for FG as per the logic defined by business

File Conversion Considerations


None

Reports required related to current business process


 MSC3: Batch record display
Document / Output would be printed for this business process
None

Integration aspects
None

Goods Receipt (BRD ID: 16 – 16.1)


Goods receipt is the phase where the material is received by the ordering party and its condition
and quality are verified.

AS IS Reference:
Goods Receipt at MCI India happens after quality team approved the material for receiving,
Quality team provides the certificate of approval to store for receiving of goods. Goods receipt is

Vital Wires Confidential Page 78


done in IBMS system, and store user lock the Material receipt note after manual (paper) approval
from User dept. who requested the goods.

TO BE Process:
Goods Receipt Note will be posted in SAP system after the manual approval from quality team.
Goods receipt will be done against the Purchase Order or Scheduling agreements or delivery.
Depending upon the movement type, stock is posted in inventory. Goods receipt has two
scenarios −
• Creation of Goods Receipt: GR will be done against the Purchase Order or Scheduling
agreements & will show the increase in warehouse stock
Accounting Entry: INV Stock Account Dr.
GR/IR clearing Cr.
• Cancellation of Goods Receipt: In case if some data at time of GR creation in system is
entered incorrectly, user can do the cancellation of GR note and re-post the same.
Accounting Entry: INV Stock Account Cr.
GR/IR clearing Dr.
SAP transaction codes
Description T. Code
Good Movement MIGO
Post Goods Receipt for PO MB01
Other Goods Receipt MB1C
Printout MB90

Movement Types:
Description Mov. Typ.
Good Receipt for Purchase Order 101
Goods Receipt for Process Order 131
Other Goods Receipt 501

Goods Return Process: (BRD ID: 15)


TO BE Reference:
The process of returning to the Vendor starts from the need to return an item to a vendor for any
reason, for example, defective quality. Most of the Vendor Return in MCI India happens for Raw
and Packaging Materials only. Credit notes are raised for vendor and goods are returned against
delivery challan immediately or sometimes later on when vendor ask.

TO BE Process:
Materials can be retuned in two ways:
 With Reference to Goods Receipt Note: At MCI India, if quality rejects the material
due to reasons like poor quality, defective material, etc.; Store user needs to return

Vital Wires Confidential Page 79


material to vendor with Material Reject Note. So store block the Qty. and then return it to
vendor against Material document. Credit note can be raised to vendor for same.
 Return Order Process: In case the defective/damaged/poor quality stock is identified at
a later stage but vendor payment has been cleared in the system by that time, now user
needs to return the stock and raise the credit memo to vendor. In those cases, Return
order will be created to vendor for the damaged goods and return delivery will be created
and Goods will be issued to vendor against delivery.

Movement Types:
Description Mov. Typ.
Good Return with ref. to Material document 122
Goods Return for Return Order 161
Goods Return from Blocked Stock

Reservations:
Sometimes, stocks are to be blocked in advance so that they can be made available at a particular
point of time or need to be requested from stores. This requesting the stock or blocking is known
as reservation. Reservation ensures that availability of stock at a particular time.

AS IS Reference:
Manual request forms are filled by the user dept. as per the material requirement and submitted
to store for the issuing of the goods, currently user only enters the material description in most of
the cases and stores looks up the material code created in IBMS system.

TO BE Process:
 Reservations can either create automatically (through process/production orders) or can
be created manually.
 For manually creating the Reservation, user needs to select the respective movement
type, Plant and Store location, Material and Qty. to be reserved.
 Open reservations are also considered while Planning run happen and system excludes
the Reservation Qty. from the available Qty. at time of Planning.
 Key control functions like Movement allowed indicator can also be used for planning
reservations for future, user can set the movement allowed indicator for the items which
are required with certain period of time. To allow issue of goods for those reservation
items and can deselect the Movement allowed indicator for items that required in far
future.
 A program can be used to set the movement allowed indicator for the reservations
created till defined period of time in system.
 Reservation process will be used for issuing material at MCI India.

SAP transaction codes


Description T. Code
Create Reservation MB21

Vital Wires Confidential Page 80


Change Reservation MB22
Display Reservation MB23
Reservation List MB24
Reservation List MB25

Goods Issue (BRD ID: 16 – 16.4)


Goods issue means moving a stock out of inventory that may be due to several reasons like
withdrawing of material for consumption or for sampling or returning the goods back to the
vendor. A goods issue results in a decrease in quantity in the warehouse.
AS IS Reference:
At MCI India currently goods are issued against the manual request for submitted by user, goods
are issued from IBMS system against the cost center, each department is a cost center and even
different production departments are created as cost center against which goods are issued.
TO BE Process:
Goods Issue can be done against Reservation, Cost Center, Production/ Process Order,
Internal Order, Asset, Scrap, etc.
Goods issue will be posted for the consumption of material for production, internal consumption
other activities, etc. depending on the movement type, system will determine the consumption
account automatically i.e. if for internal consumption, Sub-con consumption or production.
Goods will be issued mostly against reservations at MCI India in SAP system.
Accounting Entry: Goods issue against Cost center
INV Stock Account Cr.
Mat Con. Acc. Dr.

Accounting Entry: Goods issue against Process Order


INV Stock Account Cr.
Process Order Dr.

Accounting Entry: Goods issue against Internal Order


INV Stock Account Cr.
Internal Order account Dr.

SAP transaction codes


Description T. Code
Good Movement MIGO
Goods Withdrawal MB1A

Movement Types:
Description Mov. Typ.
Good issue against cost center 201
Goods issue against Process Order 261
Goods issue against Sales 601

Vital Wires Confidential Page 81


Flow Chart for Reservation and Goods Issue:

Transfer Posting (BRD ID: 16 – 16.3)


Goods Transfer/Transfer Posting means removing materials from one storage location and places
them in another storage location. This can occur either within one plant or between two plants.
A transfer posting also refers to a change in a material’s stock. For example, release from quality
inspection, release from blocked stock, accepting consignment material, etc. In a transfer
posting, the material can remain in its original storage or be transferred.

AS IS Reference:
 Store to store transfer is being used at MCI India in IBMS system; currently stock is
transferred from main store to production floor and back in IBMS system,
 Also other than store to store; material to material transfer is also being used at MCI India,
where material code for chipped and odd bottles has been created and material to material
transfer happens in order to track the chipped and Odd bottles in system.

TO BE Process:
Following activities will be performed at MCI India with Transfer Posting
 Store location to Store location Transfer (within plant): Storage location to storage location
transfers is used to transfer materials from one storage location to another within the same
plant.
 Material to Material Transfer: A transfer posting from material to material results in the
transferred quantity being managed under another material number. A prerequisite for
posting a transfer from material to material is that both materials be managed in the same
stock-keeping unit.

Vital Wires Confidential Page 82


Accounting Entry for material to material transfer depends on the Price control of both
the materials. In case of Standard price maintained on any of the material, Price
difference account may determine while qty. transfer.
 Stock Type to Stock Type (ex: Quality to Un-rest. stock, Available to Blocked stock)

Movement Types:
Description Mov. Typ.
Store to Store Transfer 311
Material to Material Transfer 309
Stock type to Stock type (quality to unrest.) 321
Stock type to Stock type (block to unrest.) 343

Physical Inventory (BRD ID: 16 – 16.5)


Physical inventory is a process of determining that the inventory quantities are exact, or if there
are differences in quantity mentioned physically present and that mentioned in the system.

AS IS Process:
Physical inventory for the key materials happen every month and for other materials it happens
once in a year. Physical Inventory is done manually; store takes print of the existing stock in
IBMS system and count the stock available physically. If there is any mismatch stock qty. same
is updated in IBMS system.

TO BE Process:
 Physical Inventory of materials will be done in System against the system available stock.
Two different methods will be used for the materials PI at MCI India, for key materials cycle
counting method will be used and for other materials periodic inventory will happen.
 We can also freeze the inventory books so that movement of goods can be stopped until
physical inspection finishes. Basically, after you finish with physical inventory, your system
and physical stock levels must be the same.
Physical Inventory process in SAP will be as follows:
 Creating Physical Inventory Document: First step to do physical inventory is to list the
material in the storage location for which Physical Inspection need to be done, this can be
done by creating a physical Inventory document. Physical Inventory document should be
created Plant and Store location wise and also batches wise and stock type (quality,
blocked) wise. Multiple materials can be listed in one document.
 Entering the Counting Results: Once the Physical Inventory document is created, process of
physical counting of those material stock starts by warehouse executives manually with PI
document print with system stock on it, after counting has been completed, count need to
be entered against the physical inventory document created in SAP system. In case the
entered count seems incorrect, recounting of the material stock can be re-initiated and
count can be re-entered into system.

Vital Wires Confidential Page 83


 Posting the Differences: After you have possibly recounted and reentered quantity
information for problematic materials, if the physical inventory is different from the book
inventory, it has to be corrected by posting the differences. This would complete the
physical inventory cycle. You can post the differences in the system. Key data to be entered
are physical inventory and fiscal year. Posting date (Goods posting will be done according to
this date)

SAP transaction codes


Description T-Code
Physical inventory document: Create MI01
Physical inventory document: Change MI02
Physical inventory document: Display MI03
Physical inventory document: Print MI21
Inventory Count Document: Create MI04
Inventory Count Document: Change MI05
Inventory Count Document: Display MI06
Inventory Difference: Post MI07
Physical inventory document: Recount MI11

Movement Types:
Description Mov. Typ.
Goods Receipt for unrestricted stock 701
Goods Issue for unrestricted stock. 702
Goods Receipt for quality inspection stock 703
Goods Issue for quality inspection stock 704
Goods Receipt for blocked stock 707
Goods Issue for blocked stock 708

Vital Wires Confidential Page 84


Materials Management – Inventory Operations
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Inventory Operations

Module: Materials Management Sub module: Inventory Management

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 Arminder Singh 31.03.2019

Goods Receipt (BRD ID: 16 – 16.1)


A goods receipt (GR) is a goods movement with which the receipt of goods from a vendor or
from production is posted. A goods receipt leads to an increase in warehouse stock.
The System distinguishes between the following types of goods receipts:
 Goods Receipts with reference to an order
 Goods Receipt with reference to shipment
 Goods Receipts with reference to a Purchasing Document. (Purchase Order/Scheduling
Agreement)
 Other Goods Receipts.
 Goods Receipts for Initial Stock Balances.
 Goods Receipt against outbound delivery

Initial Stock Entry


The goods receipt for initial stock entry is to be performed as part of the data conversion
procedure. This process is used to load the inventory balances, both quantity and amount, into
SAP. This is done only at the time of Data Migration.

Reservation Process
Reservation is the request to warehouse or stores to keep a material ready for issue at a future
date for certain purpose. The purpose of creating reservation is to insure that a material is
available when required. A material can be reserved either automatically (Process order) or
manually (For Cost centre, for an asset, for an internal order).

Goods issue (BRD ID: 16 – 16.4)


A goods issue (GI) is a goods movement with which a material withdrawal or material issue, a
material consumption, or a shipment of goods to a customer is posted. A goods issue leads to a
reduction in warehouse stock.
The Inventory Management system supports the following types of goods issues:

Vital Wires Confidential Page 85


 Goods Issue against reservations
 Withdrawal of material for production orders
 Scrapping and withdrawal of material for sampling
 Return deliveries to vendors
 Other types of internal staging of material
 Deliveries to vendors without the involvement of the SD Shipping component

Goods Issue postings result in the removal from inventory of a quantity of a material or
materials.

Physical Inventory (BRD ID: 16 – 16.5)


The physical inventory is carried out on the basis of stock management units. A stock
management unit is a non-divisible part of stock of materials for which a separate book inventory
exists.
The stock in a warehouse can be divided into stock types. In the standard system, a physical
inventory can be carried out for the following stock types:

 Unrestricted-use
 Quality inspection stock
 Blocked stock

Changes to Existing System


 Reservation will be created in system
 Goods can be issued against various cost objects

System Controls
 Only authorized person can post goods receipt and issue goods
 Material movement type wise authorization can be provided.
 Price conditions cannot be changed during GR.

Interface/Development Requirements
None

System Configuration Considerations


 Define Plant Parameters
 Define/check Number ranges for Material receipt and issue documents
 Define/check Number ranges for Material Reservations.
 Define/check Number ranges for Physical Inventory documents
 Field selection for MIGO; enable Supplier batch field as optional
 Output determination settings

Vital Wires Confidential Page 86


Number Range
Will be decided by configuration team at time of realization

Open Points
None

RICEFW/Gaps
None

File Conversion Considerations


None

Reports required related to current business process


 MMBE: Stock Overview
 MB52Warehouse Stock Report
 MB5B: Stock on Posting date
 MB5T: Stock in transit

Document / Output would be printed for this business process


None

Integration aspects
None

Materials Management – Vendor Invoice Verification


(BRD ID: 43)
TO-BE Document For SAP Implementation at Molson Coors India

Name of Business Process: Logistic Invoice Verification

Module: Materials Management Sub module: Vendor Invoice Verification

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 Arminder Singh 31.03.2019

Business Case:
Goods delivered from vendor came along with the bill/invoice; company has to pay the amount
mentioned on the invoice to the vendor. Goods qty. and value is mentioned on the invoice, based
on same, company pays the vendor his dues.

Vital Wires Confidential Page 87


AS IS Process:
 Currently Invoice when received with delivery of goods, Store along with Quality team check
and confirm the Qty. to be accepted, if the Qty. accepted is within the tolerance or as per
agreement with vendor, complete invoice Qty. is billed and entered in IBMS system.
 In case Goods received are damaged, shortage or not accepted due to poor quality, debit
note is raised to vendor for the qty. and goods returned back.
 Maker checker is followed for booking vendor invoice, one person enter the invoice and
other person checks same and sometimes third person post the invoice.
 Vendor invoices are entered only against the purchase orders in system.
 Payment is then done to vendor against entered invoices and debit note.

TO BE Process:
 Vendor Invoice will be received with goods delivered by vendor, Store will accept the Qty.
and invoice will be entered only for the Qty. received by store.
 In case of breakage, shortage of goods received, for which credit memo will be sent to
vendor. If there is a shortage in goods received, vendor has not delivered the Qty. ordered,
credit memo will be issued through invoice reduction process.
 In case of damaged goods or goods with poor quality, that needs to return to vendor, first
full qty. will be received by store in system and then after entering vendor invoice, credit
memo will be raised against the same order.
 Park and Post functionality will be used for entering the vendor invoice, one person will
enter the vendor invoice and then the other person will verify the same and post the
vendor invoice.

Vendor invoice will be booked with reference to following documents:


 Purchase Order
 Bill of landing
 Delivery note number
 Goods receipt number

Logistic Invoice Verification (BRD ID: 43 – 43.1)


In Materials Management, Logistics Invoice Verification has the following features:

It completes the material procurement process, which has started with the purchase requisition
and resulted in a goods receipt.
It allows invoices that do not originate in materials procurement (such as services, expenses) to
be processed.
It allows credit memos to be processed, either as invoice reversals or return deliveries.

The Invoice Verification procedure in SAP encompasses the matching of invoices, purchase
orders and goods receipts and the reversal of invoices and entering of credit memos. The Invoice

Vital Wires Confidential Page 88


Verification procedure is commonly termed a three-way match as it allows comparison between
the purchase order, goods receipt and the invoice receipt. Any subsequent credit memos or
invoices can be linked to the original purchase order so that they appear in purchase order
history. Any variances reported can cause the invoice to be blocked for payment. This speeds the
process of auditing and clearing invoices for payment.

Invoice verification can be processed in three ways

Goods / Services Items:


System will allow only the payment entry of the goods or services received from vendor, it will
not allow payment of any addition delivery cost for receiving those goods and services.

Planned Delivery Costs:


Planned delivery costs are entered in the purchase order on an item basis. Provisions are set up
for the relevant costs at goods receipt. The delivery costs planned in the purchase order are
referenced when the invoice is entered. The provisions are cleared. The values proposed for the
items come from the purchase order history.

Goods / Services Items + Planned Delivery Costs:


In case the main vendor is also responsible for the planned delivery of the goods and services or
any other planned delivery costs like insurance, etc. and same components has been maintained
in purchase order, then you can select this option at time of vendor invoice entry and system will
allow you to book all the costs goods cost + planned delivery cost against the vendor at same
time. Provisions will be created separately for the planned delivery costs.

Logistics invoice verification facilitates four different activities:


Invoice
The vendor invoices for the goods that have ordered from the company. Passing the same bill
submitted by him.

Credit memo (BRD ID: 43 – 43.5)


The vendor has invoiced too much for the last delivery, for example, less than the agreed
quantity was delivered and that at the agreed total price, or returned part of a delivery to the
vendor due to quality problems.

Subsequent debit
Already received & posted an invoice from vendor for all the goods received. Subsequently,
freight costs are to be taken into account; however, the invoice quantity remains the same.

Subsequent credit
Already received credit memo from vendor for all the goods received. Subsequently, freight
costs & rate difference are to be credited to company; however, the credit memo quantity
remains the same.
Vital Wires Confidential Page 89
Invoice reduction
Invoice Reduction is used to correct errors (price or quantity variance) in vendor invoice. Enter
invoice qty. (as per vendor invoice) in invoice quantity according to vendor filed & invoice
amount (as per vendor invoice) in invoice amount according to vendor filed. The invoice posting
creates two accounting documents; first document contains account postings for actual qty &
amount while second document contains difference in between invoice qty & value & proposed
qty. & value. Invoice reduction posting creates a message record which is used to generate a
complaint letter to the vendor.

Other features of Vendor Invoice Verification


Tolerance
When the system performs the three-way matching it also takes the tolerance limits into
consideration if variances occur. The tolerances, which can be defined, are listed below.
Tolerances can be defined as Upper and Lower percentage values as well as Upper and Lower
Absolute values. Both % and absolute values can be defined, such that if either of these tolerance
limits is triggered, the invoice is blocked.

Unplanned Delivery Costs


Unplanned delivery costs are only entered when the invoice is entered. No provision is made at
goods receipt. Provisions can be made at time of invoice entry by specifying the ledger account.
Cost will be uploaded to material.

Changes to Existing System


 Vendor Reduction process can be used to handle credit notes in case of shortage at time
of goods received
 Vendor invoice can be entered against different documents

System Controls
 Only authorized person can park & post vendor invoice
 Three-way matching of invoice will be done; invoice cannot be entered for qty. more
than the received qty.

Interface/Development Requirements
None

System Configuration Considerations


 Define/check number ranges for Vendor Invoice entry
 Maintain default value for tax codes
 Define/check tolerance
 Settings for invoice reduction process

Vital Wires Confidential Page 90


Number Range
Will be decided by configuration team at time of realization if any

Open Points
None

RICEFW/Gaps
None

File Conversion Considerations


None

Reports required related to current business process


 FBL1N – Vendor line items display / vendor reconciliation report

Document / Output would be printed for this business process


None

Integration aspects
None

Vital Wires Confidential Page 91

You might also like