Description of the role of 16 fields in the sap sd Pricing Process, sapsd

Description of the role of 16 fields in the sap sd Pricing Process, sapsd

Description of the functions of 16 fields in the Pricing Process
Define Pricing Procedure
Select the pricing procedure which is the standard and copy it andcreate our own pricing procedure.
Highlight it and double click the Control icon in the LHSscreen.
We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the conditiontypes.
The detail description of each column is given below.

Step:
Number that determines the sequence of the conditions with in aprocedure.
It indicates the position of the condition type in pricingprocedure.
Ex.: 10, 15 etc.

Counter:
System uses the counter to count the steps and also it can be usedto count mini steps of same condition types. So that number ofsteps can be forced ced in the pricing procedure and hence enhancingthe system performance.
Access number of the conditions with in a step in the pricingprocedure.
During automatic pricing, the system takes into account thesequence specified by the counter.

Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. in pricing, forexample, the condition type lets you differentiate specify kinds of discount; in output determination, output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00-Price
K004-Material Discount
K005-Customer/Material Discount
K007-Customer Discount.

Description:
System copies description of condition type from its description (V/06 ).

From and:
From: This can be used as a base to the condition type forcalculating further value.
{+} From and To: + The range between the steps from and to can beused to specify the range between same condition types. so thatdepending upon the condition type, the system deducts or adds thetotal value of those condition types from specific commonsource.

Manual:
This indicator specifies whether the specific condition type can bedetermined manually during sales order processing.
If we check the box then the entry is going to be manual, if weuncheck it, it is going to be automatic.
For Base Price and Taxes, the entry shoshould be automatic.
For Discounts and Freights, The entry shoshould be manual.
If we check the box, in VA01 when we go to conditions at theheader/item level, the condition type will not be listed. If werequire we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at theheader/item level, the condition type will be listed.

Mandatory:
This indicator specifies that participates condition type ismandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in theconditions tab, if we delete the value in the condition type andtry to save the document then system will not allow us to do it andthrows an error.
If we uncheck the box, then in VA01 at the header/item level in theconditions tab, if we delete the value in the condition type andtry to save the document then system will allow us to save it, without giving any error.
Mandatory check box shocould be checked in condition types which arecompulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then valueshoshould be maintained for that condition type, otherwise the systemwill not allow the user to process the document.

Statistical:
This indicator if it is activated will not allow the value of thecondition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in thedocument statistically (that is, without altering the value ).
This is commonly used for condition types
SKTO-Cash Discount
VPRS-Cost (Moving average price/Standard Price ).

Print:
The value of this field specifies whether line item can be printedor not in the sales document and at what level it is to beprinted.

Subtotal:
The value of this field determines where the values of subtotals tobe captured I. e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) arestored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting pointfor further calculations. You may, for example, want a subtotal ofall the discounts encoded in the pricing of a sales order.

Requirement:
It is a routine that is written by an ABAP consultant according tothe business requirement.
By defining Requirement in condition technique we can restrict theaccess of condition type.
To understand the concept, we will take the example of the Rebates. rebates are to be attached ded during the billing document processingand not in the sales document processing. as rebates are given onthe delivered quantity and not on the ordered quantity (in case ofcut-off period for rebates ).
For rebates we use the condition types BO01 to BO05, and in theRequirement column we give the value 24 which is "Only in BillingDocument ".
This Requirement will ensure that these condition types will appearonly during the billing document processing.
If new Requirements are to be defined we follow the procedure givenbelow.
Go to T. Code: VOFM.-Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing ".
We have a list of requirements, we can ask ABAP consultant tocreate new requirement based on the client requests.
And we assign the application type like V-Sales/Distributionetc.

AltCty-Condition formula for alternative calculationtype:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can beused instead of standard formulas.
For example, let us take the Profit Margin which can be both +/-, so here this routine will help us in generating the value whichcan be either + or -. profit margin is not a condition type so itcannot be classified as + ve or-ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11-Profit Margin.
If new routines are to be defined we follow the procedure givenbelow.
Go to T. Code: VOFM.-Maintain Requirements & Formulas

Click on the "Formulas" and then on the "ConditionValues ".
We have a list of routines, we can ask ABAP consultant to createnew routines based on the client requests.
And we assign the application type.

AltCBV-Alternative formula for condition base value:
Formula for determining the condition basis as an alternative tothe standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition typeinstead of using it from the "FROM" column.
Ex.: Freight-KF00.
Freight is calculated based on weight, volume etc. and not on thebase price. in pricing there is no entry of weight from which thevalue can be referred like we do for discounts using base price. wehave to get the value from the Material master.
In this column we can mention the value as 12-Gross Weight or 13-Net Weight.
During pricing, the system will consider the value that ismentioned in this column and determine the freight based on thisvalue.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. Andif we mention 13 in this column then the Freight condition KF00will be calculated using the weight as 100 kgs.

AcyKy-Account Key/Accrls-Accruals:
The values of the Sales Revenues, Sales Deductions, FreightRevenues, Tax Revenues, and Rebate Accruals etc. are going to beposted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/accruals to thedifferent condition types based on their classification. Theclassification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex .,
For all Price condition types like PR00 etc. we assign ERL-Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS-Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF-FreightRevenues.
For all Rebates condition types BO01 to BO05 we assign in Accountkey ERB-Rebates Sales deductions and for Accruals ERU-RebateAccruals.
This account keys and accruals are in turn assigned to respectiveG/L accounts. So the system posts respective values in respectiveG/L accounts in Fi-Co Module.
This also one of the areas of SD-Fi Integration. SD consultantsassign the account keys and Fi Consultants assign the respectiveG/L accounts in T. Code: VKOA.