Pricing Procedure : wanted to add one discount

Hi ,
We have a requirement to add one more discount which will be applicable on Final NET Price (Inclusive of tax) at Item level.
Like Gross price was 110 , Item discount 9 % , excise 16% , VAT 4% , Therefore the caculation would be
Gross 110
Discount = 10 (Approx)
NET PRICE = 100
Excise on NET = 16
VAT = 4.64
Total Actual price = 120.64
NOW on this amount vendor is giving me additional discount of Rs. 10 and therefore my net liability would be 110.64 but pls note that all TAXES (EXCISE and VAT) are required be calculated on NET PRICE i.e Rs. 100
I hope i could explain my issue
Regards
Shrey

Hi,
You may not be able to add discount condition calculated based on total inclusive of Tax
Since you can not calculate condition value based on the steps below the condition type line
May be you can make it possible by a routine for alternate base value or for calculation
Diwakar

Similar Messages

Want to add one new column in Report form

Hi all,
I have searched in forum but not able to find the answer.
I want to add one new column in form 12KST1C. I have added one column PR commitment in left and saved the form, it is showing in form but when i am running the report again then pr commitment column which i have added in form is not coming in report.
How to activate this form or column?
Help me....in doing so...

If you are copying the 12KST1C to Z12KST1C and executing the s_alr_8701333 report, you will not see the new column added to Z12KST1C
With the new Form Z12KST1C, create a new Report Z12KST1C and assign a new TCODE. Also you have to select all rows and column of form Z12KST1C
TCODE CJE5
Select the form Z12KST1C
Extras--Drildown display --Select Rows and columns
Select the all colhmns by F9
Hope this helps.
Edited by: psconsultant on May 20, 2011 8:42 AM

Want to add one more field in the standard transation xk02 : screen exit

Dear All ,
I want to add one field in transation in Xk02 in withholding tax check box.
run the transation xk02 and select check box Withholding tax and press enter after that you will get the screen having field
WH Tax Country in parellel to this i want one more field Country .
Is there any screen exit available fot this or any other way to proceed .
Please provide any solution .
Regards
Aryan

use an iplicit enahnecemnt to call a function module in which you can call a screen popu up with the fields you want update them in the database and return back to the main program. If the the two exits available are not helpful to you.
RFKRRANZ
SAPMF02K.

Want to add one more link in the first screen when user gets into EBP

Hi All,
I want to add one more link to the template WELCOME in Internet Service BBPGLOBAL. This is the first screen that the user gets when he logs into EBP.
The issue is the same screen is different in DEV and TEST environment.
I verified the code in the template in both systems but they are exactly the same.
Also, checked the Parameters in the Templates and they too match.
While going through the code, I found out that MENU_NODE_TAB is used in a repeat loop to verify user has access to the further links.
But the surprising thing is the code is same in both the systems, but Test evnironment is reflecting the link I want to add in DEV environment.
Am I missing something??
Pls let me know.
Thanks in advance.
I will reward full points for helpful answers!!
Regards,
Sanaa

Hi,
In welcome.html there is a ITS code to initialize array with information about transaction (line 87).
This code is in the loop:
repeat with idx from 1 to MENU_NODE_TAB-TEXT.dim;
if( (MENU_NODE_TAB-S_IDENT[idx] == "BBPSC01" && A_GEN_URL == "") ||
 (MENU_NODE_TAB-S_IDENT[idx] == "BBPSC03" && A_GEN_URL == "") ||
 (MENU_NODE_TAB-S_IDENT[idx] == "BBPSC02") );
 A_S_IDENT = MENU_NODE_TAB-S_IDENT[idx];
 A_GEN_URL = MENU_NODE_TAB-GEN_URL[idx];
 A_OBJECT_ID = "parent.launchpad.menu.M" & MENU_NODE_TAB-OBJECT_ID[idx] & ".root.name + parent.launchpad.menu.M" & MENU_NODE_TAB-OBJECT_ID[idx] & ".path";
 A_TEXT = quotFilter(MENU_NODE_TAB-TEXT[idx]);
 A_INTRODUCTION = #WELCOME_SENTENCE6;
 found = 1;
end;
end;
If You want to add this 4 links on begining - extend this array (in line 87):

A_S_IDENT[1] = "custom_link1"; A_GEN_URL[1] = "www.google.com"; A_OBJECT_ID[1] = ""; A_TEXT[1] = "google"; A_INTRODUCTION[1] = "google link";
A_S_IDENT[2] = "custom_link2"; A_GEN_URL[2] = "www.rediffmail.com"; A_OBJECT_ID[2] = ""; A_TEXT[2] = "rediffmail"; A_INTRODUCTION[2] = "redi link";
A_S_IDENT[3] = "custom_link3"; A_GEN_URL[3] = "www.yahoo.com"; A_OBJECT_ID[3] = ""; A_TEXT[3] = "yahoo"; A_INTRODUCTION[3] = "yahoo link";
A_S_IDENT[4] = "custom_link4"; A_GEN_URL[4] = "www.greetings.com"; A_OBJECT_ID[4] = ""; A_TEXT[4] = "greets"; A_INTRODUCTION[4] = "greeting link";
A_S_IDENT[5] = ""; A_GEN_URL[5] = ""; A_OBJECT_ID[5] = ""; A_TEXT[5] = ""; A_INTRODUCTION[5] = "";
A_S_IDENT[6] = ""; A_GEN_URL[6] = ""; A_OBJECT_ID[6] = ""; A_TEXT[6] = ""; A_INTRODUCTION[6] = "";
etc.

repeat with idx from 5 to MENU_NODE_TAB-TEXT.dim;
Regards,
Marcin

Creation of a new pricing procedure by copying existing one (for sale order

Hi,
Existing pricing procures are here below:
1000     10     00     1     1     ZBRI01     Pricing Proc_Under Con                            1000     10     00     1     2     ZBRI02     Pricing upgradationFlat
Now I need to create a new pricing procedure for the following combination :
1000     10                 00                 1                     3                   ZBR103        Pricing_single sale
Please let me know the steps to follow.
With regards,
Parijatha

Dear JP,
Based on your last direction, I created a pricing procedure. It is hitting the right GL and everything looks ok. My problem is " ZCAR (car park value which is a ZFREE item should get added to the "Net value" which is not happening.    Control data -reference step overview is herebelow.   From step 50 to 300 all are ticked for Statistics.
50     0     ZBAV     Base Value for Calc     0     0               0     0     0
110     0     ZTCO     Apartment Value     0     0               0     0     0
115     0     ZDSQ     Discount on ApT     0     0               0     0     0
120     0     ZDVA     Discount on ApT_Lump     0     0               0     0     0
150     0     ZTGR     Terrace/garden Stat     0     0               0     0     0
160     0     ZDTG     Discount on Terrace     0     0               0     0     0
210     0     ZCAR     Car Park (booking)     0     0               0     0     0
250     0          Total Consideration     110     210               0     0     0
270     0     ZGOV     Govt Rate_Reg     0     0               0     0     164
300     0          Upgradation Value - Billing     250     270               0     0     0
310     0     ZBLD     Building - For Bill     270     0               0     0     164     ZBB
320     0     ZSDT     Reg and Stamp Duty     0     0               0     0     0     ZSD
330     0     ZSDA     Stamp duty-Agr-Sell     0     0               0     0     0     ZSA
340     0     ZECH     Power Consump. Chgs     0     0               0     0     0     ZEC
350     0     ZLFE     Legal Fees     0     0               0     0     0     ZLF
360     0     ZPTX     Property Tax     0     0               0     0     0     ZPT
Can you please help me what should I do to add ZCAR (item category is ZFREE) value to Net value.
With regards,
Parijatha

Oracle apex how the region title i want to add one items

hi :
i have one page .this is page have 1)search region 2) report
in search region have the one select list contains the datas like a,b,c,d,e,f etc..
if i selectd the a and click query button in the report region page title ..i want add like REPORT ON a ..if i selected b and click the query it should display the REPORT ON b ....like this i want out put pls ..tell me how will do as soon as possible...

Sure it is possible. See this example:
http://htmldb.oracle.com/pls/otn/f?p=31517:99
There you have a select list and if you click on the button after choosing a value, you will
get a report on it.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://htmldb.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

Want to add one more table in Inner join

Hi all,
my code is show below.
SELECT a~budat a~mblnr b~matnr b~menge b~bwart
         INTO CORRESPONDING FIELDS OF TABLE it_rawmat
         FROM mkpf as a inner join mseg as b on a~mblnr = b~mblnr
         where b~bwart = '261' and b~werks in werks and b~matnr in matnr and a~budat in budat.
this code is get two table with inner join.
But now i want to get BOM quantity from Mast and stpo so can u please help me how can i add this both table in this
select statement.
i describe stlnr,menge,idnrk,matnr this four field in it_rawmat table.
now how can i fetch value MENGE from stpo throw mast .
Thanks in Advance
keyur

Here is sample example where more then two tables are join.
SELECT p~carrid p~connid f~fldate b~bookid
INTO CORRESPONDING FIELDS OF TABLE itab
FROM ( ( spfli AS p
            INNER JOIN sflight AS f ON p~carrid = f~carrid AND
                                       p~connid = f~connid    )
            INNER JOIN sbook   AS b ON b~carrid = f~carrid AND
                                       b~connid = f~connid AND
                                       b~fldate = f~fldate     )
WHERE p~cityfrom = 'FRANKFURT' AND
        p~cityto   = 'NEW YORK' AND
        f~seatsmax > f~seatsocc.

I want to add one Continuous function in Producer consumer event??

Hello,
producer consumer event vi is base example for me ,I have design my system according to it.
Now I am dealing with photo sensor in that its measure continuous data according to intensity of light,for continuous function I have make while structure for photo sensor but the problem is that I don't know how to add this while loop in producer consumer event ,if I add then its run continuously and then my operation is stuck there.
Will you please guide me that how can I add this continuous function in this structure so simultaneously I can do other function like pause reset..Etc...
Here in attachment I have attaché one example regarding to this in that I have add simply increment function in case structure and when I execute my vi then execution is stuck at while loop until it manually stop.
Thank you very much...
Attachments:
ProducerConsumerEvents 1.vi ‏15 KB

Hi AnkitRamani,
I made a simple example with a UI queue and a second producer which is pushing data into its own consumer, displaying the signal and its spectrum.
Maybe this is what u need.
Marco Brauner NIG
Attachments:
ProducerConsumerEventsData.vi ‏70 KB

Want to add new ICON to PPOME transaction plz suggest the procedure

Hi friends,
In my requriement, I want to add one ICON to PPOME transaction, in Basic Data tab section. I want some user action also to be performed.
Please suggest me how to tackle this issue.
Thanks in advance,
Phani Shankar.K

Please check Hararkey frame work in IMG
SPRO> Personnel Administration> Organizational Management>harrekey frame work.

Standard Pricing Procedure Control Options

Hi,
Need to know the use of columns in control tab of the pricing procedure like: counter, From & To with an example.
Say i have 10 - 100 steps ....
In the 50th step i have From as 10 and To as 40......what will happen for the 50 th step condition value....Also, in the 50 th step you have condition type and condition records are maintained.......
Regards

Hi,
Hope the below reply helps you.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence 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, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different 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 To:
1. From: This can be used as a base to the condition type for calculating further value.
2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition 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 the document 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 printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be 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) are stored.
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 point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
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 to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used 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 which can be either + or -. Profit margin is not a condition type so it cannot 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 given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new 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 to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have 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 is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification 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 - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

Columns in Pricing Procedure

Hi..
What is the meaning of this column in the pricing procedure?
Regds
Shriniwas

hi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/16FieldsDescriptioninPricing+Procedure&
16 columns - Define Pricing Procedure
 Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
 Highlight it and double click the Control icon in the LHS screen.
 We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
 The detail description of each column is given below.
Step:
 Number that determines the sequence of theconditionswithin a procedure.
 It indicates the position of the condition type in pricing procedure.
 Ex.: 10, 15 etc.
Counter:
 System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
 Access number of the conditionswithin a step in the pricing procedure.
 During automatic pricing, the system takes into account the sequence 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, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different 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 To:
1. From:This can be used as a base to the condition type for calculating further value.
1. {}From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
 This indicator specifies whether the specific condition type can be determined manually during sales order processing.
 If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
 For Base Price and Taxes, the entry should be automatic.
 For Discounts and Freights, The entry should be manual.
 If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
 If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
 This indicator specifies that particular condition type is mandatory in the pricing procedure.
 If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
 If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
 Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
 If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
 This indicator if it is activated will not allow the value of the condition 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 the document statistically (that is, without altering the value).
 This is commonly used for condition types
o SKTO - Cash Discount
o VPRS - Cost (Moving average price/Standard Price).
Print:
 The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
 The value of this field determines where the values of subtotals to be 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) are stored.
 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 point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
 It is a routine that is written by an ABAP consultant according to the business requirement.
 By defining Requirement in condition technique we can restrict the access of condition type.
 To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
 For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
 This Requirement will ensure that these condition types will appear only during the billing document processing.
 If new Requirements are to be defined we follow the procedure given below.
o Go to T.Code: VOFM. - Maintain Requirements & Formulas
o Click on the "Requirements" in the top menu and then click on "pricing".
o We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
o And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
 It is again a Routine that is written by ABAP Consultant.
 It is an alternative formula for the condition type that can be used 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 which can be either + or -. Profit margin is not a condition type so it cannot 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 given below.
o Go to T.Code: VOFM. - Maintain Requirements & Formulas
o Click on the "Formulas" and then on the "Condition Values".
o We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
o And we assign the application type.
AltCBV - Alternative formula for condition base value:
 Formula for determining the condition basis as an alternative to the standard.
 It is again a Routine that is written by ABAP Consultant.
 It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
 Ex.: Freight - KF00.
 Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have 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 is mentioned in this column and determine the freight based on this value.
 Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
 The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
 In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
o ERB Rebate sales deduct.
o ERF Freight revenue
o ERL Revenue
o ERS Sales deductions
o ERU Rebate accruals
 For Ex.,
o For all Price condition types like PR00 etc. we assign ERL - Revenue.
o For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
o For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
o For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
 This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
 This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
Reward if USeful
Thanx & Regards
Naren..

Pricing procedure(Condition technique)

Hi All
Can someone provide me all the configuration steps in pricing procedure in MM...

Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
Highlight it and double click the Control icon in the LHS screen.
We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
The detail description of each column is given below.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence 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, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different 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 To:
1.From: This can be used as a base to the condition type for calculating further value.
1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition 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 the document 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 printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be 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) are stored.
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 point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
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 to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used 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 which can be either + or -. Profit margin is not a condition type so it cannot 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 given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new 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 to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have 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 is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification 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 - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
or
Hi,
Pricing Procedure in MM
The steps are:
SPRO->MM->Purchasing->Conditions->Define Price dertermination process
1. Define Condition Table:
2.Define Acces Sequence,
3.Define Condition Type,
4.Define Claculatin Schema,
5.Assign Calulation Schema,Acces Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organisation,
8.Assign Schema Group Of Vendor to Purchasing Organisation,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

Replacing of the pricing procedure by a different pricing procedure .

Hi
We are process of changing the pricing procedure of the particular sales process.
In case of old open sales order after changing pricing procedure if i update it in VA02 mode then also ...it is not picking the current sales order ...
Again in case of sales order where deivery has been done ...for them while creating billing ...it is taking current pricing procedure so that there is a mismatch of sales order amount and billing amount .
Again while creating return order w r t old sales order ...it is taking current pricing procedure in return order instead of taking the original one ....
Pls advice how to rectify this problem .
Thanks in Advance
Regards
Mrinal

Dear Lakshmipati,
I told I am in process of changing pricing procedure .
Currently normal pricing procedure is configured in the system. Now business wants to change it in list price pricing procedure ( i.e base price with tax pricing procedure ) . And new pricing procedure has some extra automatic discount value also .
My question was
1) There is no change in open sales order ....IT is OK
2) But for sales order where already delivery has been done then after changing pricing procedure it is taking new pricing procedure so that ..sales value and billing amounts are getting different . How to restrict this .?
3)For return order also ...it is taking new pricing procedure ... How to restrict the same ?
Regards
MKC

Step for Adding new condition in Pricing procedure

Hi,
We have different pricing procedure with different condition , in this procerdure i want to add one new condition at 2 position and the requirement is that if system found the value with this condition it should skip the 3 step and directly go to 4 step can u give the step for this how to add new condition to this procedure.
regards,
zafar

I think you need to use condition exclusion so if the condition at step 2 is found then step 3 becomes inactive if it is also found.
Depnding on your pricing keys, you might be able to add a step in the access sequence on step 3 and only use a single condition (V/07) and marking that step exclusive if a record is found.

Pricing procedure- vendor??

hi all
The how to configure this pricing procedure and this pricing procedure is only for one vendor ., how it can be done ??
At present taxes are calculated on Basic price.
We need like this ..
Pricing Step 1 :we want to calculate Taxes on the Total of 'Basic price + freight amount - Special discount " = Rs XYZ value.
Now on Rs XYZ , the entry tax has to be calculated??? = Rs ABC
Pricing Step 2 : Now Value Rs XYZ + ET = Rs ABC
Now On Rs ABC VAT has to be calculated .
For above requirement i need Pricing steps in detail and Tax code (In TAXINJ procedure).
Thanks
SAP-MM

Hi
Following steps for pricing procedure as,
1. Define conditions.
2. Define pricing procedure.
3. Define virtual purchase organization and vendor.
4. Info Record.
Customization for Pricing Procedure :
1. Definition of Conditions :
/NMEK0-condition typeu2026condition types- definition (define for basic price, net price, discount, surcharge, tax etc.)
2. Defining pricing procedure :
/NMEK0- calculation schema-calculation schemasu2014New entries (Define procedure and put the conditions like formula so that final price will be net price / total value as per company requirement)
3. Linking pricing procedure to independent condition types.
/NMEK0-condition typeu2026condition types- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions u201CPricing Procedureu201D box)
4. Defining Schema group for Vendor :
/NMEK0- calculation schema-schema groupsu2014vendoru2014New Entries.
5. Defining Schema group for Purchase Organization--- New entries.
/NMEK0- calculation schema- schema groups---- purchasing organization--- new entries.
6. Linking Virtual Purchase Organization to actual Purchase Organization.
/NMEK0- calculation schema- schema groups----- Assign P.Org. (in actual P.Org, enter virtual P.Org)
7. Linking Pricing procedure to virtual P.Org and virtual vendor :
/NMEK0- calculation schema- Determine Schema--- -Standard --- New entries (Enter virtual schema and P.Org. along with pricing procedure)
8. Linking virtual vendor to actual vendor-- /NXK02 then enter schema group vendor in Purchasing Data )
go this link
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
http://www.sap-img.com/sap-sd/creating-new-pricing-procedure.htm
Regards
MK

Pricing Procedure : wanted to add one discount

Similar Messages

Maybe you are looking for