Steps for Variant Configuration and Pricing in SAP SD

I want to configer motercycle having differnt types of colour, each colour have varity of standered feature as wall as differnt CC. while want to create slaes order I want motercyle with speciefic colour, Cc feature. which is not possible while creating BOM it will only be configer by materiel Varient Configration.
-------------------------------------
Here are the Steps for Variant Configuration
1.Create a Material of your Motor Cycle using Material type KMAT(MM01).
2.Then create a characteristic called ZColour(SAP has a standard Characteristic for this but it has multiple values-i.e you can select more than one colour for your Bike.If you do not want that create your own)with character format and assign single value radio button on the initial screen.Go to values Tab and give the colours you need.save the characteristic.Similarly repeat for CC(I figure this CC as 100cc & 200cc kind of thing.If you want these as materials then it is a different story-I am taking this as feature as well)
3.Create a class called Zbike with the above 2 characteristics.save the class
4.Create a configuration profile Zbikeprof using Cu41 and assign the Kmat material to Class Zbike,
5.Then create the order and Enter the Kmat material you want in the Order.
John Devraj.
-------------------------------------
In variant configuration I have configured my material properly during sales order creation it is selecting proper characterstics. but my question is pricing should calculate at characterstics level not at header level.
Ugamesh.
-------------------------------------
Pricing in variant Configuration is done at the Header level only.The logic is that you create pricing variant keys for each characteristic Value.This will be done at the Header level using cond type VA00.based on the characteristic chosen the appropriate price according to the pricing variant key will be picked up.
John Devraj.
-------------------------------------
Here my question is with out creating the materials is it possible to get price based on the characterstics.
I am working on variant configuration here my product is 9-100. i have created characterstics for describing colours. this characterstics assigned to class, this class is assigned to 9-100(KMAT type). here i have not created amterial to describe each colour.
Now how I need to setup my system to calculate the price based on colour.
Ugamesh.
-------------------------------------
A cool Question. It will really get us into the thick of things in Variant Configuration.
Here are the steps.
1.Create a Characteristic called ZColour(Standard SAP has a characteristic called colour.I did not use it.)
Give your values.
Say, Red & Blue
2.Now create another characteristic called ZCol_surcharge
Give the description and go directly to Addnl Data Tab.Here in the table name Enter "SDCOM" and in the Field Name Enter "VKOND".The system will pick up the format from the Dictionary.
3.Now go to CT04 and change the Characteristic Zcolour.
Go to values tab and select RED.Goto Extras-> Object Dependencies->Editor and then select Procedure.
In front of 000010 Enter $self.ZCol_surcharge='RED'.
Similarly Select Blue and enter $self.ZCol_surcharge='BLUE'
3.Link both these characteristics to the Class(The class which you have attached the KMAT Material).
4.Go to VK11 and the Enter VA00.Then give the values RED and BLUE and enter the values.
5.Go to your order and Enter your material.
John Devraj.
-------------------------------------
Here are some clarifications required from you.
what is the significance of item category group 0002 and 0004. Apart from these are they any other item category groups are available for configurable materials ?
In BOM header material having components. is it possible to make the component as configurable material.
Ugamesh.
-------------------------------------
The difference b/w 0002 and 0004 is basically that of LUMF & ERLA.
In 0002 the pricing happens at the Header Item Level.
In 0004 the pricing happens at the Sub Item Level.
Check out the Item category Assignments and things will be Clear.
I think these two are the only ones used for Configuration.
Please let me know in which Scenario you would like to have the configurable material Inside a BOM(as it would help me in visualising thh Item Category Assignment).
John Devraj.
-------------------------------------
As you said I setup my system to calculate price based on colour.
ZCOLOUR contains all colours in values tab page.
ZPRICE contains table name and filed name in additional data tab page.
I went to ZCOLOUR characterstics I maintained (extras-object dependicies-editor-action) there I have given $self.ZPRICE = 'RED' for all the values.
when am creating the sales order price is coming only for RED colour not other colours. even price is maintained for all the colours.
Ugamesh.
-------------------------------------
Seems like there is a mistake in the line $self.ZPRICE = 'RED' (You have said you have given this for all the values- If I have not mistaken). This refers only to red colour.
In front of 000010 Enter $self.ZCol_surcharge='RED'.
Similarly Select Blue in the Values Tab and enter $self.ZCol_surcharge='BLUE'
All this is Case Sensitive. So please be careful.
John Devraj.
-------------------------------------
Now its coming any way thank you very much.
Ugamesh.
-------------------------------------
I have been reading your's and ugamesh's mails regarding the same but no where the sales doucments have been discussed as well as material master record and configuration in SPRO.
If you can kindly explain me the same as I was trying to do the same.
Reena
-------------------------------------
There is no need SPRO involvement in Variant Configuration.Everything happens in Easy Access.
As far as Material Master record is concerned you only need to use a KMAT Material type.
There is no need to assign any sales document to this material.
Follow the steps and you will get the result.
John Devraj.
-------------------------------------
I have gone thru the steps and created a sales order, but the pricing procedure is not coming proper. Also do we have to maintain the values for the ZCol_surcharge.
As I have already maintain the rates of the color in VK11 - VA00.
Reena
-------------------------------------
Have you maintained the Object Dependencies for the values in the characteristics class.
John Devraj.
-------------------------------------
Yes !
What I have done is created a customer with KMAT ( Car), without characteristics tab pg. After this I created 3 charateristics viz., zcolor, zengine & zcol_surcharge and assigned them to Class 300 ( Variant).
But I have maintained the dependencies only for Zcol_surcharge : $self.Zcol.surcharge='RED'
Then I assigned all these to a config profile and aslo added the condition VA00 in the pricing procedure, then maintained the same in VK11.
Now my problem is it is not coming in the SO
Reena
-------------------------------------
I think the problem is with the characteristics.
For the characteristics Zcolor and Zengine you must maintain some values in the Values Tab.
Ex:
Zcolor- Red
Blue
Zengine- V6(Right now you can use only one Characteristic for learning)
V8
The characteristic Zcol_surcharge(By name this suggests that it is applicable only to colour-Whereas you can use it for other characteristics as well) does not have any values.
For the values maintained in the Characteristics Zcolor and Zengine you have to go to each value(Go to values tab and select Red) and maintain the object dependency "Action" $self.Zcol_surcharge='RED'. Similarly maintain for Blue,V6,V8 for Example.
Then maintain the condition records for Va00(without any Case mismatch).
Use standard pricing procedure RVAA01.(or a copy- as it has provision for VA00).
This should solve your problem.
John Devraj.

How To Add New Fields To Field Catalog in SAP SD

I have to add new field "Profit Center(Design ID)" to the field catalog first and then create new condition table for pricing using this field.
1. How to add new field to field catalog?
2. How to create condition table using that new field?
For adding field into Field catalogue:
I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:
For example if you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
To solve the problem, proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'. Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition
Technique) -> New Fields for Pricing' and Note 21040.
For creating a condition Table:
1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.
See what best you can use the Standard Tables to avoid further errors.
2) In case you should define the new condtion Table,
a) Goto TCode: V/03
b) Give a Table any number from 501-999
Press execute and reach to next screen.
c) Check up whether the field you are looking is already added in Field catalogue.
d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..
Eample : Sales Org, DC, Division, Customer and then Material etc..,
e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.
7) Check which key should be in header and which key should be footer. Use check and uncheck functionalities there..
8) Once you are through with all the above steps ..click on generate button.
Check the Table is generated or not.
You can check it at V/04 or V/05 or in SE11.
Tips by : Ajay Kumar Veeranki

Tcodes To Configure The SAP SD Sales Tax Determination

Billing
SAP Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.

Sales Tax Determination
OBQ1 - Maintain/Create Condition Type

• Double click on the Condition Type for more control

OBQ3 - Tax Pricing Procedures
OBQ2 - Tax Access Sequences
OBBG - Assign Tax Country to calculation procedure
OVK3 - Define the Customer Tax category
OVK4 - Define the Material Tax category
OVK1 - Define Tax determaintion rules

• Define the links between the Tax Country and Tax conditions type

OVK6 - Assign delivery plants for Tax determination (locally which Tax country category to use)
VK13 - Maintain Tax Condition Rate (e.g. 1%, 2% etc...) by Tax Country
SM31 - Table View V_T001 - Maintain default country, currency for Company Code.
Material and Customer Tax Master Maintenance must be equal
e.g. 0 = tax 1 = no tax both Material and Customer master must be 1 and 1
Search for the Tax Classification field
MM02 - Sales Organization data
XD02 - Tick Billing

To create a discount on payer level on billing type LR in SAP SD

Billing
SAP Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.


Tested in 4.6x
This will not have any affect on the sold-to-party price.
If you want a payer based discount on invoice list only. This is what you will need to do:
1. Check out the pricing procedure RVAA01 and condition type RL00. This pricing procedure is for Germany and the
discount is factoring discount. But it is payer based discount.
IMG - Sales and Distribution -> Billing -> Billing documents -> Maintain conditions for invoice lists ->
Maintan pricing procedures
2. RL00 uses access sequence RL00 and condition table 7 which is sales organization/distribution channel/divison/customer
(payer). If that fits your needs, use it. Otherwise, do the usual create condition table, access sequence and condition type
configuration.
3. In the appropriate place in your pricing procedure, add in condition type RL00(or one you created). Be careful to copy the
requirement routine and condition base value assignments from pricing procedure RVAA01.

Configuring Intercompany Billing in SAP SD

Billing
SAP Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.


How to configure Inter Company Billing

INTERCOMPANY BILLING

Business case: - Customer orders goods to company code/Sales organization A (Eg.4211/4211). Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an inter-company billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.
SPRO Customization required:-
1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)
2. Maintain intercom any billing type as IV for sales document type OR
3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)
4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)
5. Automatic posting to vendor account (Optional)
6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing
Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For inter-company billing
Master data to be maintained:-
1. Create end customer master in company code/sales org 4211/RT/11
2. Create customer master for 4211 company code/sales org in 4436/RT/11
3. Maintain PR00 as price for end customer-Active in RVAA01
4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01
5. Maintain IV01 as inter-company Price-Active in ICAA01
Process:-
1. Create OR with sold to party as end customer.
2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as inter-company sales.
3. Pricing procedure is RVAA01
4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
6. Delivering sales org will create inter-company billing IV with reference to delivery document.

A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group. To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B. It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
Sales organizations and plants assigned to each other need not belong to the same company code.
In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
PARTIES INVOLVED
1) End Customer 2) Ordering Company code 3) Supplying Company Code.
End customer:
Customer who orders goods from the ordering company code.
Ordering Company Code:
Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
Supplying Company Code: Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
CONFIGURATION SETTINGS
Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
Assign Organizational units by Plant:
Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
Define Internal Customer Number By Sales Organization:
Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
Transaction Code: XD01
The ordering sales organization is represented as Internal customer of Supplying company code.
We need to create customer master in Account Group – Sold to Party and maintain minimum required financial & Sales Area data.
This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
PRICING:
We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.
We maintain PR00 condition type to represent the ordering company code’s price to the end customer.
Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
Eg: Sales Org. of Ordering company code + End customer + Material.
We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
Pricing Procedure ICAA01is determined at Intercompany billing processing level.
Pricing Procedure ICAA01 – Pricing Procedure for Inter company billing is assigned to the combination of:
1) Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).

Explain What and How To Configure Debit Memo in SAP SD

Billing
SAP Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.


Debit Memo Request:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:DR is the sales document type for Debit Memo Request. 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
Step 2:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: L2 is standard Billing Type for Debit Memo. If possible use Standard Billing Type. In case 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.
Note: Ensure that Copy Control settings are done
Sales Order to Billing (OR --> F1): VTFA

In what situation do we use a debit memo request and a debit memo?
Debit memo is used in below scenarios:
1) When you have charged the customer less then actual due to reason like selection of wrong scales or you have not checked the actual Market price.
2) When there is an over delivery and customer agrees to pay for it.
Debit memo request is an order type which is referred to create a debit memo there can be release procedure in-between depending on the business process.
Also note that our FI counter parts can create standalone DEBIT MEMOS.
There are a lot of scenarios we create debit memo request and debit memo against a customer. I am giving a couple of scenarios:
In repair processing the material has come back to our premises, we repaired the same and send it back to the customer. The charge for repair and the parts consumed has to be billed to the customer. We normally use resource related billing in such cases, through RRB we generate a debit memo request and followed by a debit memo.
We have sold one equipment (material) to a customer, it is having some issue, the customer wants an immediate replacement. We send the replacement immediately, expecting the customer to return back the faulty one. But the customer is not returning back the equipment. After many follow-up, we create a debit memo request and debit him with a debit memo.

SAP Spools Configuration for Sales/Distribution

Shipping
SAP Shipping is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.


SAP Spools Configuration for Sales/Distribution
SAP Printers outputs

• Create/Change the shipping loading point (VV22) and (OVX7)
• Create/Change the billing output (VV32)

Sales Document Output Control

• transaction /NVV12
• Input the Output type e.g. BA00 - Order Confirmation then hit enter
• Input the Sales document type e.g. OR - Standard Order and click Execute
• Under the Output Conditions Section, you must know which Sales grp. you used. Look at the Tim Column. Option 4 indicates an immediate printout once the user save its data.
• To check which SAP printer the sales document print to, tick the desired Sales grp. and click Communication button.

SAP SD Enterprise Structure Configuration

Enterprise 
Structure:

1 Edit, Copy, Delete, Check Company Code(T001)
Company is created by FI Consultant.
The company code is an organizational unit used in accounting. It is used to structure the business organization from a financial accounting perspective.
IMG -> Enterprise Structure -> Definition -> Financial Accounting -> Define, copy, delete, check Company Code

2 Define Credit Control Area(T014)
Company is created by FI Consultant.
The credit control area is an organizational unit that specifies and checks a credit limit for customers.A credit control area can include one or more company codes. It is not possible to assign a company code to more than one control area. Within a credit control area, the credit limits must be specified in the same currency.
IMG -> Enterprise Structure -> Definition -> Financial Accounting-> Define Credit Control Area

3. Maintaining Sales Organization(TVKO)
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

4. Assigning Sales Organization to Company Code(TVKO~BUKRS)
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

5. Maintaining Distribution Channel(TVTW)
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

6. Assigning Distribution Channel to Sales Organization(TVKOV)
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

7. Maintaining Division(TSPA)
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check division

8. Assigning Division to Sales Organization(TVKOS)
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

9. Setting up Sales Area(TVTA)
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

10 Maintain sales office(TVBUR)
you define the sales offices in your company. The definition of sales offices is optional.
For each sales office, you can determine the printer for output based on the sales documents in different ways
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Maintain Sales Office

11 Assign sales office to sales area(TVKBZ)
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales Office to Sales Area

12 Maintain sales Group(TVKGR)
company. The definition of sales groups is optional. You can use the SD system without creating sales groups.

13 Assign sales group to sales office(TVBVK)
you can assign as many sales groups as desired to the sales offices. Any one sales group can belong to several sales offices.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales group to sales office

14. Define Shipping Points(TVST)
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

15 Define, copy, delete, check plant(T001W)
Plant is created by MM Consultant.
IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check plant

16 Assigning Shipping Point to Plant(TVSWZ)
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

17. Assigning Sales Organization- Distribution Channel- Plant(TVKWZ)
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization – distribution channel – plant

Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

18. Defining Common Distribution Channels for Master Data(TVKOV-VKWKO TVKOV~VTWKU)
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

19. Defining Common Divisions for Master Data(TVKOS-SPAKO TVKOS~SPAKU)
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 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. 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.

The configuration differs from scenario to scenario & requirement of the client.