Master DATA and Partner Determination
SD Master data
1. Genaral Data
1 Define Customer account groups - OBD2
2 Define Number ranges -88 XDN1
A. Inter Number range
B. External number Range
3 Assign number ranges to customer account Groups OBAR
Master Data in SD –
Customer master data- SD
Material master data- MM Consultant
Customer material info records- SD
Material master data- MM Consultant
Customer material info records- SD
Condition master records -SD
Overview of Customer Master data
Master data are constant, and they are use for business transaction as datasource.
Several sources of data can be copied into a sales order or into another SD document. Most of them are default values that you can overwrite in the SD document, if necessary.
(Note: Control over the master data record is vitally important to ensure consistency in reporting & usage, that is why it is advisable to have master data creation and maintenance centralized and done in the same way across an organization to avoid inconsistency of input and interpretations)
Customer Master data:
- Customer master contains 3 views as follows
2. Sales area data
3. Company code data
Note: Customer master data can not be deleted – It can only be marked for deletion, which is then archived, so system will delete from file after all dependent data has been deleted (Can be done for specific Sales area. To mark for deletion Tcode: VD05, To block customer Tcode: VD06)
Note: When you change a master data record after you have used it to created SD doc like order, the changes will not affect documents already created. But the exception is the address,. Address changes will affect all previously created documents.
Configuration of Customer Master Data: (Account groups customization as pre-requisite for creating customer master data records)
Typically SAP SD functional consultant will have to customize the customer master at least a little bit to suit the requirements of the project. SAP allows very little customization in terms of functionality to the customer master. Nevertheless, SAP allows full customization in the customer master in terms of fields (Hide, show, grey out fields, make fields mandatory, add fields etc). Also external interfaces like Interacting with external tax vendors like Vertex.
Note: For sales order processing, you need the mandatory partner functions sold-to party, ship to party, payer, Bill to party. They can differ from each other or can be identical (e.g.: sold to and ship to name & address can differ, also payment term fields for sold to & ship to can also differ)
Configuration inSPRO
Menu Path is [Spro-->IMG-->FA-->AP & AR--->Customer accounts--Master Data -->Preparations for Creating Customer Master Data---Define accounts grougs with screen layout
Steps Customer Master Configuration T Code1 Define Customer account groups - OBD2
2 Define Number ranges -88 XDN1
A. Inter Number range
B. External number Range
3 Assign number ranges to customer account Groups OBAR
Note: A partner can play many roles in a business transaction. E.g. a sold to party can also act as payer, ship to and bill to (Partner determination proc.)SAP allows you to use Z & Y to denote specific customer configuration in Table TDKZ. E.g. You can change sold to 0001 into Z001
Main Transaction Codes in a Customer Master
Transaction Codes | Description |
---|---|
XD01, XD02, XD03 | Used to create/change/display customer centrally |
VD01,VD02,VD03 | Used to create/change/display customer sales area |
FD01,FD02,FD03 | Used to create/change/display customer company code |
XD04 | Display change documents |
XD05 | Display change documentsUsed to block Customer − Global, order, delivery, billing, sales area, etc. |
XD06 | Used for deletion |
XD07 | Change Account Group |
VAP1 | Create Contact Person |
Key tables in Customer Master
Table Name | Description |
---|---|
KNA1 | General Information |
KNB1 | Company Code |
KNVV | Sales Area |
KNBK | Bank Data |
VCNUM | Credit Card |
VCKUN | Credit Card Assignment |
MASSKNVK | General Data in Customer Master |
KNVK | Contact Person |
KNVP | Partner Functions |
MASSKNVK | Contact Partner |
MASSKNVD | Rrecord sales request form |
KNVL | Customer Master Licenses |
KNVI | Tax Indicator |
KNVA | Unloading Points |
KNAS | VAT registration numbers general section |
Partner Determination in SAP Sales and Distribution
Purpose
This wiki page will discussion about basic function related to partners in SAP Sales and Distribution Module knows as Partner Determination
Overview
This a procedure by which system selects the assigned sales relevant partner function/functions to the object in Order to Cash process.
In brief, sales partner are business parties which are involve/relevant to a sales process/transaction. Each partner are defined/identified based on role & function they play in those sales process/transaction. These can internal or external to an organization. To setup, determine & copy these business partners in a sales process or specific sales process or master in SAP SD, we use a search technique, known as Partner Determination.
Main Components in Partner Determination
- Partner Function
- Customer Account Group
- Partner Determination Procedure
Partner Object
Following are the Partners object with respective key area for which partner determination can take place-
- Customer
- Sales Document Header
- Sales Document Item
- Delivery Document
- Shipment Document
- Billing Document Header
- Billing Document Item
SPRO path/Transaction Code
Transaction Code
|
VOPAN / VOPA
|
---|---|
SPRO Path
|
Sales and Distribution - Basic Functions - Partner Determination - Set Up Partner Determination
|
Configuration Steps
Let us go through the configuration steps involved in partner determination. Here we would take focus on partner determination for a customer master.
Existing Sales Partner in Customer Master Determination:
Partner Function
|
Language
|
Name
|
Language-specific
Partner Func. |
---|---|---|---|
AG
|
EN
|
Sold-To Party
|
SP
|
RE
|
EN
|
Bill-to Party
|
BP
|
RG
|
EN
|
Payer
|
PY
|
WE
|
EN
|
Ship-to Party
|
SH
|
The following are the steps involved in adding a new partner type, say, JP, for customer master for partner determination:
Step 1. Partner Functions
Maintain a new partner function, JP, under partner function node with respective partner type (KU for Customer, LI for Vendor) & indicator for Uniqueness in the master data.
Step 2. Assigned Partner Function to Account Group
Assigned newly created partner function JP to corresponding account group of your desire.
Step 3. Create Partner Determination Procedure
Select partner determination procedure if your requirement is met. Otherwise copy existing Partner determination procedure.
Step 4. Maintain relevant Partner to determine under Partner Determination Procedure
Under partner determination procedure sub-dialog, you assign required partners to partner determination procedure. Here you specify whether the assigned partner can be:
- modified in object or not
- whether it is mandatory
- sequence in which partners are determined (may differ with object).
Step 5. Assign Account Group to Partner Determination Procedure
Assign Partner determination procedure to account group. It is assumed that required account groups are available in the system.
In case of other objects same procedures can be followed. It differs at step 5, where you assign partner determination procedure to respective object.
Partner Object
|
Partner Determination
Procedure assigned to |
---|---|
Customer
|
Customer Account Group
|
Sales Document Header
|
Sales Document Type
|
Sales Document Item
|
Item Category
|
Delivery
|
Delivery Type
|
Shipment/Transportation
|
Shipment Type
|
Billing Header
|
Billing Type
|
Billing Item
|
Billing Type
|
Comments
Post a Comment