Agenda

 Customer Master Data

 Master material data
 Customer material info Record
 Customer Hierarchy

Why Master data

 Base of S&D process

 Pre-requisite before a sales process
 It avoids a lot of manual tasks (price, qty etc)
 Minimise manual entry
 Huge chunk of the system set up
 Setting up master data – huge chunk of the work as consultants – data migration/need t do
validations with approval from biz fields
 As we work with transactional data – ensures the data is authentic
 Eg:- Customer master, material master, vendor master
 Eg of transactional data – sales order PO, GRN etc
 Need to set up master correctly before moving to transactional data

Customer Master data

 First master data – biz partner

 ECC had separate for vendor and customer
 In HANA, its clubbed together and created as biz partner
 Capped BP
 BP will have a further drill down customer or vendor
 Benefits – now duplicate data, authentic data, min error, reporting is easier and more
efficient
 Biz partner can be individual person, individual org, group of org – called biz partnere role
categories
 3 categories
o Person – only contact person or general
o Org
o Group
 Multiple roles under each category
o General –
o Contact person
o Customer
o FI Customer
o Vendor
o FI Vendor
 FI customer – only company code relevant details – only finance relevant data will be stored
as a FI customer role
 Customer role- all sales relevant data required for the customer data will be added here
 BP role will have CVI integration (Customer vendor integration) which will have A/C group
and partner functions
 Customer will have 4 activities – partner function
o Places order
 o Receives order
o Pays for services
o Send the invoice
 One customer can play all the roles/ or multiple customers can play different roles
 Sold-to becomes mail client – can have diff payer details and bill to details
 BP role – customer/vendor
 BP role category – person/org/group
 Bp role grouping – a config we do so that when we select a group, all relevant bp roles are
automatically assigned – ends with ‘X’
 BP number range – unique number generated for a particular customer
 Master data synch – while creating a biz partner – will copy data from bp general role to the
customer role
 Account group –
o very specific to a customer
o need to set up ac group before setting up role
o for instance, can have a customer ac group that only acts as a ship to so will not
have finance related data
o helps us to derive the number of fields that will be displayed at company
data/general data level
o biz partner no range and ac group no range are the same
o makes creating transactions and reporting easier
o one time ac also present –
o can set up min 4 ac groups – can set up even more
 two types of customers
o external customer
o intercompany customer
 customer who belongs to same group of companies
 tata steel sales to tata motors
 tata motors is an intercompany customer to tata steel
 trading partner – company code to intercompany customer – code given to
tata steel – represents the entity – IC vendor code represents the vendor
 reconciliation ac- common for both – used for tracking financial transactions
or for ledger postings
 IC Vendor – tata steel is IC vendor to tata motors
 Biz partner config
o Enter transaction code spr
o SAP IMG ref
o Biz partner config ref
o Every arrow is a node
o Go to the correct node – which is the correct node?
o First set up the BP Role
o Std roles – FLCU00 – finance; FLCU01 – sales
o Std practice – Bp role and BP view are the same - can be customized with help of
technical resources
o BP role category – same naming convention
o To customize BP role category – naming convention begins with ‘Z’
o Create a number range – can be sys generated or external
 o Assign it – there’s something called BP grouping
o Customer a/c group -
o Partner determination - mandatory function is not editable
o CVI – cross application – Master data synch – setu up synch control – activate ppo
req – here BP is an object – check the PPO active check box
o Done to avoid technical dumps (what is technical dump?)
 Number range for biz partner and a another one for customer – if you want biz parter to be
customer – number ranges for bp groupin and account grouping
 Config before creating a business partner
 Company code data – purely from a financial perspective

Customer Hierarchy

 Normally used for a group of customers

 One parent customer – eg Tata sons, and multiple child customers – tata steel, TCS, tata
motors etc
 Used for order or billing doc, assign pricing procedures etc
 Each partner who uses hierarchy can use it for different purposes
 Can add and edit child customers

Material Master

 Service is also called a material master

 Every material is created with material type
 Material master controlled by master type – similar to account type controls customer
 Material can be physical goods or service
 Different depts will be involved to bring the whole material master into SAP
 Inputs will be given from diff depts to the person creating the material master
 Material type is important – different for finished material, services etc
 Material master from S&D POV
o Basic data – common across all areas
 Can see material group
 Gross weight/net weight
o Sales view - Sales org 1
o Sales view - Sales org 2
o Sales view - General/plant
 Valid for delivery team
 Item category group etc
o Foreign Trade Export – export/import, region of origin etc – available in purchase
view and S&D view
o Sales Text – keep info you want to convey to customer – for instance – Fragile, keep
in cool temp etc
 Material Master created through a transaction MM01
 Material type will control the behaviour of Material Master
 Nse 69 – table MVKE opens the sales master of the material
 Table name MARA – can see the basic data
 Basic data gets stored in MARA table – can filter by material we are looking for
 Sales org is the highest entity
 Sales area and sales channels comes under sales org
 Division – categorization of product – for instance, in supermarket – floor 1 has eatables
floor 2 has home appliances etc
 Sales area is backbone to create any transaction and is composed of sales org, channels and
division
 Material needs to be extended to sales org and division
 Views are the attributes of the different materials according to the depts
 Need to know where material group is captured during pricing
 Price gets maintained based on material group
 First step is to extend the material to Sales Org
 Sales unit is different from base unit of measure
 Sales unit comes under sales org 1
 Sales unit will come in transaction
 Conversion between sales unit and base unit is maintained in additional data
 For instance,
o Material – Pepsi
o Base unit – 1 bottle
o Sales unit – 1 Crate
o Conversion – 1 crate = 12 bottles – maintained in additional info
 X-distr. Chain status – maintains the status of the material – separate codes for separate
actions – eg – 01- material is discontinued
 Whenever order is processed in SAP SD module – material is delivered from Plant
 Delivery plant can be maintained at 3 levels
o Customer master (CM)
o Material Master (MM)
o Customer material info master (CMIR)
 but takes precedence form CMIR level
 if I place order for Activa and customer master says its available in Hyd, MM says its
available in CHN and CMIR says it is available in b’lore, it will take from CMIR level
 CMIR>MM>CM
 Need to maintain tax liability in material master sales view
 Account assignment group – very imp
 Need to recall this field during billing and sales and transaction sessions
 This field helps in account determination
 This field will help matching the revenue obtained to the customer
 Item category group – Helps determine the item category in the sales order
 General Item Category group
 Need to link the plant to sales org – only then will the material will be picked from the plant
 Availability check – very important metric
 Transportation grp and loading grp – used for shipping point determination –
 Profit centre maintained in general/plant
 Export tab – country of origin/ region of origin
 Sales text tab – text id is created to maintain the sales text
Customer material info record (CMIR)

 Maps the product name as the customer knows and the product name as maintained by the
org
 Used to convert customer language to org language
 Takes priority over plant while processing sales order
 Will determine the priority of delivery, shipping conditions, partial delivery etc
 Shipping info can also be maintained here
 Purpose is for cross-reference between customer and material
 Just maintaining CMIR record isn’t enough. Need to enable at document type level (later
sessions)
 CMIR created through VD51, change 52,
 Stored in KNMT Table
 Combination of customer and material but created on the basis of the customer
 Can config so that customer can call out the material by multiple names
 Delivery priority and min delivery qty – CMIR takes priority
 Can control partial delivery as well
