on 11-20-2008 5:13 AM
Hi,
I am new to SD. Could anyone explain me the important fields in the create customer transaction and sales order creation transaction.
Thanks and regards
Aparna
2 Process & Configuration
2.1 Customer Master
2.1.1 Account Group
2.1.1.1 Maintain Number Range for Account Group
Use
The purpose of this activity is to control number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
Transaction Code: SPRO
Data to be maintained:
No | From | To | Current No | Ext (Tick in Check Box)
01 | 0000000001 | 0000099999 | 0 | No
02 | 0000100000 | 0000299999 | 0 | No
XX | A | ZZZZZZZZZZ | Yes
2.1.1.2 Assign Number Range to Account Group
Use
The purpose of this activity is to maintain number range of Account Group.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
Transaction Code : SPRO
Data to be maintained:
Group | Name | Number Range
0001 | Sold-to party | XX
0002 | Goods recipient | XX
0003 | Payer | XX
0004 | Bill-to party | XX
2.1.1.3 Define Account Groups with Screen Layout (Customers)
Use
In this step, you determine the account group of the customer.
Procedure
Access the activity using one of the following navigation options:
IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Define Account Groups with Screen Layout (Customers)
Transaction Code : SPRO
The groups indicated below are a few examples. There are many groups in Standard SAP & if we require additional Group, it can be copied from appropriate group & maintained.
Group | Name
0001 | Sold-to party
0002 | Goods recipient
0003 | Payer
0004 | Bill-to party
0005 | Prospective customer
0006 | Competitor
Select Sold-to-party > go to Details > Double Click on General data / Company code data / Sales data. It will take to next screen which details Tab Pages of General data / Company code data / Sales data. Double Click on Tab Page for example: Address, Control, Marketing & so on. Here you can maintain whether the field is to be Suppress, Req. Entry, Opt. entry or Display
2.1.2 Process to Create Customer Master
2.1.2.1 Initial Screen of Customer Master Maintainance
Use
The purpose of this activity is to maintain Customer Master Data. Customer Master Can be created for Sales & Distribution, in which it will be possible to maintain General Data Tab & Sales Area Tab. Alternatively it is also possible to maintain Complete / FI, in which it is possible to maintain General Data, Company Code Data & Sales Area Data (Complete) or General Data & Company Code (F1)
Procedure
Access the activity using one of the following navigation options:
SAP Easy Access > Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Create > Sales and Distribution / Complete
Transaction Code : VD01 / XD01
Fields to be maintained in Initial Screen (referring Complete):
Field - Functionality
Account Group - Take a drop down & select appropriate Account Group
Customer Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
A Customer can be created with reference to an existing Customer & necessary data can be changed.
Reference
Field - Functionality
Customer - Enter manually
Company Code - Take a drop down
Sales Organization - Take a drop down
Distribution Channel - Take a drop down
Division - Take a drop down
2.1.2.2 General Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain General Data. General Data is applicable to the customer centrally. Incase of extending Customer to another Sales Area, General data will remain the same.
Procedure
Fields to be maintained are as under:
ADDRESS
Field - Functionality
Title - Take a drop down
Name - Enter manually
Search Term - Enter Manually (Optional)
Street - Enter Manually (Optional)
House No - Enter Manually (Optional)
Postal Code - Enter manually
City - Enter manually
Country - Take a drop down
Region - Take a drop down
Control Data
Field - Functionality
Vendor - Enter Manually (Optional) u2013 To establish Customer Vendor Relationship.
Trading Partner - To be maintained incase of Inter-company Customer,
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.3 Company Code Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Account Management
Field - Functionality
Recon. Account - Take a drop down (Mandatory)
Payment Transaction
Field - Functionality
Terms of payment - Take a drop down.
The above is for Illustration purpose. Please ensure to maintain the fields required.
2.1.2.4 Sales Area Data of Customer Master Maintenance
Use
The purpose of this activity is to maintain Company Code Data. This is maintained by an FI person.
Procedure
Fields to be maintained are as under:
Sales
Field- Functionality
Sales Office - Take a drop down & maintain the appropriate SBU
Currency - Maintain the local / export currency.
Exch. Rate Type- Maintain u2018Mu2019, incase of export / inter-company(if required) only.
Cust. Pric. Proc -This is maintained to pick the pricing procedure in Sales Order & Billing Document. It should always be maintained.
Customer Stat. Gr - This is recommended to be maintained to enable the data to flow to SAP standard report.
Shipping
Field -Functionality
Delivery Priority - Take a drop down & maintain the appropriate for Delivery purpose.
Order Combination - Maintain the tick
Shipping Condition -Take a drop down & maintain the appropriate for Delivery purpose.
Delivery Plant - Take a drop down & maintain the appropriate Plant.
Billing
Field - Functionality
Incoterm - Take a drop down & select. Maintain the Description manually.
Terms of payments -Take a drop down & select.
Account assignment Group -Take a drop down & maintain the appropriate. This is very important to be maintained, else it will give an error to release the billing document to accounting.
Tax - Take a drop down & select u20180u2019 or appropriate.
The above is for Illustration purpose. Please ensure to maintain the fields required.
Sales Order Creation
First Screen: Input Fields
Order Type
Sales Organization
Distribution Channel
Division
>>>>> Enter
Sales Order: Overview Screen
Sold to Party
PO Number
Required Delivery Date (Default)
Material
Quantity
Assuing that all Master Data in place, such as Customer Master, Material Master, Pricing Condition Record and basic setting in place.
Write-Up SD Configuration:
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure (T.Code: OVKK). Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
Note: Ensure that Copy Control settings are done
Sales Order to Sales Order (QT --> OR): VTAA
Sales Order to Delivery (OR --> LF): VTLA
Sales Order to Billing (OR --> F1): VTFA
Delivery to Billing(LF --> F2): VTFL
Billing to Sales Order (F2 --> RE): VTAF
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
The mandatory fields are decided based on the requirement of those details in processing of different activities in different areas. The data from the fields in Sales Area Data are important in SD point of view for processing of different activities of SD like Sales, Shipping and Billing. If those values are missing, the processing cannot be done and hence to avoid those problems, the fileds are made mandatory.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aparna,
By using the T.Code-XD01,we can create the customer.
In this transaction you have to select Account group.If you want to enter the company code then enter the company code and sales area too.
In this in standard SAP some fields are defined as required entries as we can find as mandatory fields.We can customize this one also.
For this follow the path as:
IMG>Logistics-General>Customers-->Define accountgroups and field selection for customers.
By using this we can create our own account groups and select what are all the fields required for us.Among all the fields,Country field is always a mandatory field which you cannot find in the fields.Because we have to select the country as it is useful for tax classification.Different countries have different taxes just like in Indis there is Excise duty etc...
Now fill all the mandatory fields in all the tab pages.
VA01 is the t.code we r using for creating a sales order.
In this one mainly customer,material,price etc... are the mandatory fields.
First fill customer and material press enter.
then goto Edit-->Incompletion log,select all the fields and complete data.
All the mandatory fields will apppear in this incompletion log.
Thanks,
Phani.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks for the prompt reply.Think you dint get my question. I saw the mandatory fields, but I want to know what are they for.
For example, what does trading partner mean in control data.
Thanks and regards
Aparna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
The important fields are made as mandatory fields through the customisation of Account Group, which controls the views and fields of the customer master record. You can check the relevant Account group (SP,SH etc.,) using the Tcode OBD2, where you can see the fields marked as mandatory for different views of the customer master.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Aparna,
while creating Customer-Master (XD01) or Sales Order (VA01); important fields are already kept as "Mandatory" in to the Standard SAP.
Best Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.