Master Data

Master Data:
Master data is pool of data which are created centrally in the system and available for every document whenever they want to access the data.

Data origin in Sales documents:
- Customer Master
- Material Master
- Customer-material info record
- Conditions Records (Pricing, Output, Cross Sales, Free Goods, Material determination,

Customer Master:
General Data: Relevant for SD and accounting. Tabs:
- Address
o Title, Name, Search term, Street, City, Pincode, country, Region, timezone, transportation zone, Language,
- Control data
o Vendor, VAT reg no
- Payment Transaction
o Bank details
- Marketing
o Nielson ID, Customer class, Industry, annual sales, no of employee, Legal status, fiscal year variant,
- Unloading Points
o Unloading point, Receiving point, Calendar, Customer calendar, goods receiving hours
- Export data
- Contact Persons
o Name, home address, visiting hours, Partner function
Sales Area data:
- Orders
o Sales district, Sales office, Sales grp, customer grp, Order probability, Item proposal, currency,
o Price grp, customer Pricing procedure, Price list, Customer statistic grp,
- Shipping
o Delivery priority, Order combination, Shipping condition, Delivering plant, Completer delivery req, max partial delivery, Tolerance,
- Billing document
o Rebate, Price determination, Invoicing dates, Invoicing list dates, Inco terms, Terms of Payment, Credit control area, Acc assignment group,
o Country, Tax category, tax classification
- Documents
- Partner functions.

Company Code Data:
- Account Management
o Reconciliation account, Cash management grp,
- Payment Transaction
o Terms of Payment, Payment History record
- Correspondence – dunning prcedure
- Insurance

Effects of changes in Customer Master data:
When you change the master data after having used it for creating document, its changes do not affect the document created. However Address is an exception. Means new address will be reflected in the old documents also.

Account groups in customer Master:
It determines which fields are to be used in defining customer master. Depending upon the partner function and transaction, we assign or change the field status(Optional, Mandatory, Display, Suppressed) . Depending upon the field status system prevents the particular field in the customer master while maintaining customer master.

Mandatory Business Partners:
Sold-to-Party
Bill-to-Party
Ship-to-Party
Payer

Organization unit in customer Master:
- Company Code
- Sales Organization
- Distribution channel
- Division

Material Master:
It is grouped in several views. Like
- General data 1 and 2
o UOM, Gross Weight, Net weight, division, Gen Item cat grp, Weigh unit
o xPlant material status
- Classification
- Sales – Sales org - 1
o Basic UOM, division, Material group, Sales unit, Delivering plant, sales discount
o Country, tax category, Tax classification(liable or except)
o Mini Order qty, Min Deli qty, Delivery unit, Dist channel specific status
- Sales – Sales org - 2
o Material Statistic grp, Material Pricing grp, Volume Rebate grp, acc assignment grp, Item category Grp
- Sales : General/Plant Data
o Base unit, Gross Weight, Net weight, Avail. Check, Batch management,
o Transportation grp, Loading grp.
- Foreign trade/Export
- Purchasing
- MRP 1 – 2 - 3 – 4
o MRP grp, MRP Type, MRP controller, Lot size
o Procurement type, In-house production time, Planned delivery days, SchMargin Key
o Strategy grp, Availability check, Total RLT time
- Accounting 1 -2
o Valuation category, Valuation class, Price control, Price unit, Moving price, Standard price,
- Costing

Organization unit in Material Master:
- Plant
- Storage Location
- Sales Organization
- Distribution channel
-

Cross-division sales:
Here header division can differ with division of other material entered in sales order. We can control this in customization of sales document :
- Check division – Whether it is possible to enter multiple material with different division(different then the header division). We can set it in document type whether it should show error message, dialog or no dialog.
- Item division - whether the division in material master is copied in the document or the division in header also copied in to the item level. If we select this checkbox, then division from material master will be proposed in the item.

Division specific sales: If you set the Check Division for Error message, then it becomes division specific sales, and we can n not enter material from different division and which differs from the header division.

Condition Master:

Pricing condition:
For Pricing component – Price, Discount & Surcharge, Freight and Tax.
The condition type defines multiple use of condition.
You can have a percentage, a quantity dependent or an amount dependent surcharge or discount.
By specifying validity period, you can restrict a price agreement to a certain period.
We can maintain values within a condition record according to a scale.

Shared Master data Concept:
We define common DS and DIV to share master data of common DS and DIV with other DS and DIV.

On the sales org/Distribution channel level we can define which distribution channel should be used to accessing the condition records and which should be used for customer and material master.

On the Sales org/Division level, we can define which division should be used to accessing the condition record and which should be used for customer master.(not material master)

It is not possible to define shared master data for sales organization.

Shared Master data and SIS:
Even if you are using shared master data, the data values transferred to SIS comes from values in sales documents.
For multi-division sales you must specify the correct source field for the division in SIS so that this setting affects the updating rules in the SIS. i.e. MCVBAK-SPART or MCVBAP-SPART.