Incompletion procedure: [30] = Delivery relevant schedule line.
Incompletion procedure has been defined and assigned to the schedule line category CP. System follows this incompletion procedure and remains the end user if do not maintain any values in schedule line category fields before saving the document.
Check transfer of requirements (Req. / Assembly): Requirements of sales document whether individual or
summarized should be transfer to MRP by system automatically to create demand.
Check availability check: If the system has to carryout availability check for materials and quantities in the sales
order it should be checked.
Product allocation: Through product allocation we can allocate products for customers evenly.
Save the Schedule line category and Exit
91
PricingPricing is the combination of creating correct pricing procedures that map the business needs and processes such as correct pricing and discounting, and keeping to the legal requirements placed on the business, such as adhering to the tax laws of the respective country.
A pricing procedure consists of a list of condition types in defined orders, such as price, less (–) discount, plus (+) tax. Some controls exist in the pricing procedure.
Pricing is the calculation of costs (for internal purpose) and revenues (for external purpose) by following tax class of a particular country.
The pricing procedure is also used in account determinations. This determines the general ledger (GL) accounts to which type prices, discounts, and taxes must be posted. The condition types in the pricing procedure are linked to an account key. This key in turn is linked to the GL Accounts. This shows the integration between the pricing in the invoice and the Financial Accounting (FI) Module.
Pricing Procedure
Availability check/TOR
Free – of – charge goods
Material determination Material Pricing Route determination Output determination Partner determination Text determination Customer Account determination Credit management Sales document IN OR Header + Item + Schedule line
Condition record Condition table
Value Combination Access sequence
Base price [PR00] xxx (–) Discounts (KF00) xxx (=) Net value per item xxx (+) Freight (KF00) xxx (+) Taxes [MWST] xxx Net price xxx
Optional pricing elements Condition types
Mandatory
Input tax = MM Output tax = SD
92
1 Pricing procedure PR00 , etc like 2 Pricing elements Base price, etc like
Condition type Access sequence 3 Combination of data Condition tables
4 Access sequence Condition records
FAQ: How system determines pricing procedure? ANS: Sales area (that the end user enters) plus
Document pricing procedure (Ex: OR Pricing procedure = PR00) plus Customer pricing procedure (Ex: Whole seller, etc).
Define pricing procedure: Transaction code: V/08 Path:
IMG
Sales and distribution Basic functions Pricing Pricing control
Define and assign pricing procedure Maintain pricing procedures Click on position button
Choose standard pricing procedure RVAA01 form position button Select it and click on copy icon on the application tool bar
Rename it and press ENTER till we get a message that is 72 entries has been copied Save and select our pricing procedure
Click on control data icon under dialog structure Select all conditions types by clicking on select all icon Click on delete icon and save it (do not forget to save it) Go to new entries and maintain values like below:
Step Cntr Ctyp Description From To Man Mdt Stat Print Subto Reqt Altcty Altcbv Actkey Accrls
10 0 PR00 ERL 20 0 Gross value 10 X 1 30 0 K004 20 ERS 40 0 K005 20 ERS 50 0 K007 20 ERS 60 0 Tot. discount 21 59 X 2 Sales organization Customer pricing procedure Division Distribution channel Document pricing procedure Pricing Procedure
93
70 0 KF00 12 ERF
94
Step: It indicates the step number of condition type in pricing procedure. Ex: 10, 20, 30, and etc. It is possible to
number the steps in intervals of 1, but this can make changing the procedure in the future very difficult.
Counter: System uses the counter while accessing the condition types in our pricing procedure. This is used to
show a second mini – step within an actual step. For example, you may have all your freight surcharges assigned to step 100; however, there may be three condition types, each representing a different freight surcharge. Thus, you8 can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3; and so on.
Condition type: The condition type is the link from the access sequence all the way to the actual condition record.
We specify condition types (pricing elements) that are participating to calculate net value in our pricing procedure.
Ex: PR00, K004, K005, K007, and etc.
Description: System copies the description of the condition type from definition of condition type (V/06). From and To: These two columns serve two purposes.
(A) As a range between the condition types of some conditions we can specify the same condition type with in one range. So that all values of condition types added together and deducted or added to the base value. (B) As a base to calculate further value of condition type. We can specify the base for condition type. So that
system takes the base (step).
Manual: It determines how the condition type is going to be determining in our pricing procedure manually or
automatically. Ex: Some condition types that do not have any access sequence should/can be determined manually. That means they do not directly come to the pricing procedure automatically. Ex: Condition type PR00 can be determined automatically and condition type HA00 (header condition) should be defined manually.
Mandatory: Mandatory indicates that the particular condition type is mandatory in pricing procedure. So that the
end user should maintain the value of a particular condition type in condition records or at least during sales order processing. Otherwise system will not allow the document to be process for further move. Ex: Condition types PR00 and MWST are mandatory conditions.
95
Statistical: It indicates the purpose of condition type is only for information purpose. The value of condition type
will not be taken into consideration in the net value calculation.
Ex: Condition type VPRS (cost)
As this VPRS copies cost of the material from the material (master) and deducts the value from not value for items to calculate profit margin. So the purpose of having VPRS is only to copy the cost of the material and it is not at all participating in calculation of net value. So that it should be a statistical.
Print: It indicates the value of the condition type can be printed in a document. Ex: X
Sub – total: The value of this field determines where the value of the sub – totals is going to be stored in the
database. Sub – total 1 = KOMP – KZWI 1 and Sub – total 2 = KOMP – KZWI2
Requirement: Requirement is nothing but a routine that has been written by ABAPers according to the client
requirement. Requirement is used for condition type that excludes particular condition type while determining the net value.
Ex: Routine No: 23 and 24 can be used only in billing document with condition type BI01, BI02, and BI03
(condition types for rebates) as these condition types should be activated only in the billing document level. We include these condition types in our pricing procedure and system deactivates at sales order level and activates in billing document level. System takes this requirement into consideration and activates or deactivates accordingly.
PR00: As it is quite possible some items are not relevant for pricing, it is advisable to assign a requirement
indicating this condition type is not necessary for items not relevant for pricing. Assigning the requirement 002 to the requirement column can do this.
K004, K005, K007: These condition types are only valid should the item in the sales order be relevant for pricing;
thus assign requirement 002 to the tree new discounts.
Alternative formula for calculation type: We can specify the alternative formula instead of standard one as a
condition type in the form of routines. Ex: Routine No: 11 profit margins can be used as a alternative formula for condition type to calculate profit margin as there is no standard condition type to calculate profit margin.
Alternative formula for condition base value: Instead of using from column as a basis to calculate further value
for particular condition type we can use a formula in the form of routine to use base.
Ex: Routine No: 12 or 13 gross weight or net weight can be used with condition type KF00 to calculate fright
charges. As for freight charges always weight of the material taken as a base.
Accounting keys and accruals: We can define and assign accounting keys for each and every pricing element
groups. So that, the values of the pricing elements (condition types) can be posted in the respective G/L accounts, through this accounting keys.
Ex: ERL = Sales revenues (Ex: PR00)
ERS = Sales deductions (Ex: K004, K005, K007, and etc) ERF = Freight revenues (Ex: KF00)
MWS = Tax revenues (Ex: MWST)
ERU = Rebate accruals (Ex: BI01, BI02, and BI03) Save the pricing procedure and Exit
Define determination of pricing procedure: Transaction code: OVKK Path:
IMG
Sales and distribution Basic functions Pricing Pricing control
Define and assign pricing procedure Define pricing procedure determination
96
Sales organization Distribution channel Division Customer pricing procedure Product pricing procedure Pricing procedure Condition typeSREENU SRI CNU A 1 SRINU PR00
Save and Exit
Maintain condition record: Transaction code: VK11 Path:
Logistics
Sales and distribution Master data
Conditions
Select using condition type VK11 – Create
Specify the condition type PR00 and click on key combination (access sequence) Choose first condition table (© Customer/material with release status)
Click on continue button
Specify sales organization, distribution channel, and customer number. Specify material number and pricing amount
97
NOTE: Every condition record maintained with specific to sales organization and distribution channel.
Maintain condition records for remaining condition types K004, K005, K007, and KF00 etc by repeating the same above process.
Go to VA01 and raise the sales order
Select line item and go to Go to Header Sales and Check our pricing procedure determine or not
Select line item and go to Go to Item Conditions in the condition screen In the condition screen ANALYSIS and UPDATE
ANALYSIS: By using this analysis option we can analyze our pricing procedure like how many base prices,
discounts freights and taxes are taken into consideration to determine net value for line item.
UPDATE: We can carryout new pricing procedure at sales order, delivery and billing level. System does not
change the old values in the condition master records. Eg: When we raise the billing with reference to delivery document there may be a chance to change the tax rates. Then we have to carry out new pricing procedure by re-determining taxes.
FAQ: How you can carry out new pricing within the validity periods of condition records? ANS: By carrying out new pricing option in UPDATE in pricing condition screen at item level.
Define our own pricing procedure:
Pricing procedure
Condition tables Condition type
OVKK
Access sequence
Sales area + Document pricing procedure + Customer pricing procedure
Condition records
VK11 V/03 Condition table
V/07 Access sequence key V/08 Pricing procedure PR00 K004 K005 K007 V/06 Condition type PR02 Material
Customer/Material with release status
Price list category/Currency/Material with release status
20/307 10/306 30/308 100 300 200 Condition records