Master Data Configuration Flashcards
Customer Master Records
Basis for all sales transactions as well as deliveries and payments
• can represent different entities based on the role they play in the transaction
• Ex: SP, BP, P, inter-company customers, one-time customer
Sold to party
Partner/customer that places the sales order request
Ship to party
The partner/customer that receives the delivery of the goods or services
Bill to party
The partner/customer that receives the invoice
Payer Party
The partner/customer that is responsible for the payment of the invoice
VA—
Sales order
VL—
Delivery
VT—
Shipment
VF—
Billing
“—01”
Create
“—02”
Change
“—03”
Display
“GB10”
Company Code
“GB01”
Sales Organization/Plant
“10”
Distribute
“01”
Division
“000001”
Sales Office
“001”
Sales Group
“GB02”
Plants/Sales Organization
“0001”
Loading point
Creating Customer Master Data
• Assigned account group(SP, BP) is used and dictates which fields are needed • Structure - General Data - Company Code Data - Sales and Distribution Data
General Data
- Address
- Telephone number
- Identified by customer number only, not specific to company code or sales area
- Can be maintained from CC view or SD view
Company Code Data
Data of interest to the accounting department
• Info on reconciliation account, dunning procedures and withholding tax
• Applies to only one company code
Sales and Distribution Data
Data of interest for the sales and Distribution area
• Data on pricing or shipping
• only applies to one sales area
Material Master Data
• Material type is a mandatory field, similar to account group in Customer Master in that it dictates which fields are relevant • Common material types - HAWA-Trading good - NLAG- Finished product - FERT- Finished product - VERP- Packaging material - DIEN- Service
Material Master Views
- Accounting 1,-2
- Material Requirements Planning (MRP) 1-4
- Purchasing
- General Plant Data Storage 1, 2
- Sales Org 1, 2 and Sales—General/Plant data
Material Master: Accounting Views 1-2
Valuation and costing info
Ex: standard price, past and future price, and moving average cost price
Material Master: Material Requirements Planning (MRP) 1-4
Information for material requirements planning and consumption-based planning/inventory control/availability check.
Ex: safety stock level, planned delivery time, reorder level for a mater, MRP Type
Material Master: Purchasing View
Data provided by purchasing for a material
Ex: purchasing group responsible for a material, over- and under-delivery tolerances, and the order unit
Material Master view: General Plant Data Storage 1-2
Information relating to the storage/warehousing of a material.
Ex: Unit of issue, batch management, and storage conditions
Material Master view: Sales Org Data 1-2, and Sales—General/Plant Data
Info pertinent to sales orders and pricing. Views relevant for SD team.
Ex: delivering plant, taxes, pricing reference material, and item category group.
• Availability check indicator, controls how the system determines if stock is available for a sales order and when it will be available
Pricing reference material field
Used for a material that already has a material master record and prices in the system, which is being used as a reference for a material being created
Item category group
- Covers how a material behaves in all SD document formats (quotation to the invoice)
- All sales documents are dependent on the value in this field
Base Unit of Measure
Unit of measure used for all transactions of a material
Ex: Cleats base unit of measure would be pairs, shipment of 10 pairs
Alternative unit of measure
A product is managed in the base unit of measure but is sold in a different unit type
Ex: a pair of cleats is sold in a box, 5 boxes of 5 pairs of cleats
Sales unit
The unit or measure in which materials are sold is referred to as a sales unit.
The value you define in the material master record is proposed during business transactions relevant for sales
Ex: you sell cleats in boxes, so the box unit is the sales unit
Delivery unit
The unit in which materials can be delivered
Only exaxt multiples of the delivery unit can be delivered.
Ex: a delivery of 30 bottles, can have 60, 90 bottles delivered but not 100
Minimum order quantity
Minimum order quantity a customer must order
• a warning message appears during delivery processing if the minimum order quantity is not reached during order entry
Minimum delivery quanity
The minimum quantity you must deliver to the customer
• automatically checked during delivery processing
• a warning message appears during delivery processing if you enter a delivery quantity lower than the minimum delivery quantity
Customer-Material info records
Information on a material that applies to a specific customer when buying a specific material
Ex: a customer may have its own description for your material
•customer-material info record takes priority over material master data when copied into a SAP transaction
Ex: you create a sales order, default material will be from customer-material info record. If no such record exists, SAP will use material data for the sales area.
•Dependent on sales area
Delivery priority
Used as a selection parameter when creating the delivery
• also used for rescheduling
Sharing Master data, Common distribution channels and common divisions
Possible for all master-relevant data and all condition-relevant data. Used when you don’t want to differentiate the master data based on the sales Organization
Ex: you define sales divisions for reporting purposes, you would have to create customer master sales screens for every combination of sales org, DC, and division. So you make the division common, then you only have to maintain the customer master sales screens for the various sales orgs, DCs and the sole common division
Sharing Master data, Common distribution channels and common divisions part 2
You can group the distribution channel and division separately, for either master data(which combines customer master and material master records) or group the distribution channel and division separately for condition records, or both the master data and condition records
Ex: You have a product range that is not different for 4 different distribution channel that you have. Neither is there a difference in the customer’s details when they purchase through one channel or another. Thus, you do not wish to create four views of customer master and material master records, based on the 4 sales areas. Select 1 distribution channel and division to use as the common one. Create the customer master records and material master records in the common distribution channel. Then assign the other distribution channels you created to this one.
Sharing Master data, Common distribution channels and common divisions part 3
If conditions are shared, you only create a condition in the distribution channel or division you are using as the reference(common)
Customer groups field
Grouping of customers that is configured under master data
• copied into the header and item level of a SD document
• can generate statistics
• can create condition records
Ex: you want to offer discounts per wholesale customer group, but not per retail customer group
Sales districts, Sales offices and sales groups fields
These can refer to differing geographical areas or regions or as a grouping term on the customer master record
• sales office refers to a sub-group of the sales district, and the sales group is a sub-group of the sales office
• the sales group is often used to represent a sales team or sales person
• these fields are copied into the header and item data of a sales order
• fields can be used for statistical purposes as well as pricing
Master Data tables
Master data is stored in the database in tables and fields.
Data is populated into these tables after a transaction has been saved
This master data is copied into the transaction data whenever a new transaction is created
Ex: the customer master data is copied into the sales order when a sales order is created
Partner Determination
Happens in the sales document, delivery, billing documents, sales activities, and customer master record
This feature is configurable
• Each partner(customer) master record is created on the basis of a specific account group
• each partner function may be assigned a partner type, which specifies whether this partner is a customer, contact person, vendor
Partner Determination Procedures
Ex: AG is the partner function, AA is the partner function in procedure
In-completion procedure field
Used by the system to register partner fields that are not filled at the time of creating the sales order.
The in-completion procedure then prompts the user to complete these fields with missing values
Unique in customer master indicator
Indicates that the system must allow only one entry of this partner function in the customer master record
