Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Hi experts--
For subject matter(we are facing this issue in our organisation) I did my search and found the below threads but conversation did not provide what solution is to be implemented. Can someone help?
Currently we are using two unique vendor codes for tiding over our MM/SD problem even though vendor is same with same address,PAN & service tax registration.
We are a LSP and only recently went live on ECC 6.0 EnP4
warm regards--
A.VENKAT KRISHNAN
Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Posted: Aug 19, 2011 7:04 AM
Click to report abuse...
One vendor is providing service & material to the same Pur Org
Is it anyway to handle with only one vendor code for service & material procurement in same vendor account group with only one pricing procedure(calculation schema)?
Ramesh Babu Nag... [Active Contributor Silver: 500-1,499 points]
Posts: 535
Registered: 5/29/09
Forum Points: 1,380
Re: Same Calculation Schema/Pricing Procedure- Same Vendor - Material & Service
Posted: Aug 19, 2011 7:16 AM in response to: ARUL MURUGAN1 in response to: ARUL MURUGAN1
Yes, you can do it. There shouldn't be any issue
Hi,
Yes its possible.
you can use the same calculation schema for both so that with one vendor you can handle both material as well as service purchase.
Please revert if you face any difficulties.
Thanks & Regards,
Similar Messages
-
Accounting Key & Accruals Key in Calculation Schema (Pricing Procedure)
Hi Freinds,
I have a query regarding use of Accounting Key & accruals key in the Calculation Schema (Pricing Procedure).
What is the significance of Accounting key & accruals key in the calcuation schema? Which Accounting & Accruals keys have to be used for Gross price,Discount,Freight, tax etc in the Calculation schema? Please post your precious threads.
Thanks & Regards
Saeed Arifhi
AcyKy - Account Key/ Accrls - Accruals:
for SD module
u2022 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.
u2022 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
u2022 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.
u2022 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.
u2022 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.
Similarly for MM Module
Account keys are EIN, FR1, FR2, FR3, FRE, etc...
And in OBYC, we do necessary account determination for the same.
For e.g. Freight Posting in GR
Condition type FRA1, Accrual FR1 and in OBYC, assign Freight Clearing A/c to FR1
During GR;
Stock Account - Dr - 110 INR
GR/IR Clearing A/c - Cr - 100 INR
Freight Clearing A/c - Cr - 10 INR
transaction event key is the Key that identifies different types of G/L account.
The account key enables the system to post amounts to certain types of
revenue account. For example, the system can post freight charges
(generated by the freight pricing condition) to the relevant freight
revenue account.
use
To enable the system to find the relevant account for provisions (for
accrued delivery costs or miscellaneous provisions, for example), you
must assign a transaction/event (internal processing) key to each
condition type that is relevant to provisions in the step Define
Calculation Schema.
if u search on SDN or GOOGLE u will get many threads for this
hope it helps
regards
kunal -
Pricing Procedure for Imported Material purchased from local vendor
Dear SAP Experts,
I have a scenario, where the Imported material is purchased from a local vendor.
The local vendor passes on all the customs duty, CVD and all the related duties to the customer (us).
All the duties including CVD in the form of Excise duty etc. have to be inventorized.
How to map this in SAP?
Thanks In Advance.
Regards,
Muthuraman.KHI,
I have given the pricing procedure for TAXINN
100 0 BASB Base Amount 362
110 0 Calculated Call 100
120 0 Sub total
250 0 JSRT Service tax set off 100 VS7
251 0 JEC3 A/P Ecs for Serv tax 250 VS8
253 0 JES3 A/P SE cess serv tax 250 VSE
258 0 Total Sevice Tax 250 253
260 0 JSVD IN:Service tax debit 250 ESE
560 0 JMOP IN: BED setoff % 120 X VS1
561 0 JMOQ IN: BED setoff Qty 120 JI2
564 0 JSOP IN: SED setoff % 120 VS1
565 0 JSOQ IN: SED setoff Qty 120 JI2
570 0 JMIP IN: BED inventory % 120 X
571 0 JMIQ IN: BED inventory Qt 120 NVV
574 0 JSIP IN SED inventory % 120 NVV
575 0 JSIQ IN SED inventory Qty 120
578 0 JMX1 IN: A/P BED setoff 560 561
580 0 JSX1 IN: A/P SED setoff 564 565
581 0 JMX2 IN: A/P BED inventor 570 571
583 0 JSX2 IN: A/P SED inventor 574 575
584 0 Total excise duty setoff 578 580
585 0 Total excise duty Inventory 581 583
586 0 Total Excise Duty W/O ECess 584 585
587 0 JECP A/P Ecess set off % 584 VS2
588 0 JECI ECS inventory % 585 NVV
589 0 JSEP IN:A/P SEcess setoff 584 JI6
590 0 JSEI IN:A/P SEcess inv 585
591 0 Price 120 120
600 0 JAOQ IN: AED setoff Qty 120 VS2
601 0 JAOP IN: AED setoff % 120 VS2
605 0 JAIQ IN AED inventory Qty 120 NVV
606 0 JAIP IN AED inventory % 120 NVV
U have to setup ur taxprocedure like this.In this the acct key is the main.IN OBCN ucreate the acct key & give them as non cenvatable.Then assign this acct key against the condition type in the TAXIIN.
Then in FV11 create the condition records for the cond type.For the cond type the access sequence should be JTAX -
Condition type date should be same to the pricing procedure date
hi
i have an problem
the problem is that condition type date is not same to the pricing procedute date
details of the problem
1. created a sales order the pricing date is 01.04.2006
2. when i go conditions in the sales order, as i go for details of the condition type date the is 04.04.2006
this date should be same ie 01.04.2006
give the solutions and relevant fields or procedure for this i will be greatful to all of u
byeBraja,
Check this
Goto the billing plan tab in the corresponding line item and check the rule that is determined. Now go to the configuration of this rule table by using the path
SPRO>SD> Billing> Billing Plan> Define rules for determining dates and choose your Applicable rule and click on the details.
There you will see the Calendar ID field where you will have to maintain the applicable factory calendar. I think this should work and your billing date on the item relevant for billing plan should be the same as the other item.
Hope this helps,
Ravin -
Copy Control Different Pricing Procedure same condition statistic
Hi Guys,
I have the following issue perhaps someone outhere can support me.
I have customized a copy control from Sales Order to another Sales Order(Credit Memo). For both sales orders I customized an own pricing procedure determination. For sales order A pricing procedure A is found, for sales order B pricing procedure B is found. That is working fine. Now my problem. The values of my conditions must be copied 1:1 from Sales order A to Sales Order B. In Pricing Procedure B is the same condition as in pricing procedure A only with the difference that this condition is customized in pricing Procedure B as STATISTIC, in pricing procdure A as non STATISTIC
I tried different settings for pricing type in copy control (VTAA)
C Copy manual pricing elements and redetermine the others
Result: My condition gets determined again but the problem is that now the condition has a negative value.
G Copy pricing elements unchanged and redetermine taxes
Result: Condition is copied 1:1 but also the NON STATISTIC sign is copied from Sales Order A
I want to copy the value of one conditon from Sales Order A to Sales Order B, but it should be (as customized in pricing procedure B) set in Sales Order B as STATISTIC.
Thanks for your help,
MatthiasHi,
I found the solution myself. If you have anytime same problem go to V/08 and tick TSPP for your second pricing procedure.
Regards,
Matthias -
Reverse Calculation in Pricing Procedure
Hi All,
My client requirement is to calculate the PR00 from the TOTAL and TAX
i.e. If we enter the TOTAL some amount and TAX 12.5% VAT in the Pricing Condition then it should calculate the d Basic Price PR00 .
Tanks and regards,
BalaHi
Thanks for understanding the explanation given earlier and this an interesting qn
I am giving herewith a document on MRP pricing procedure (you need to understand this and make the settings)
This is same as your requirement but additionally it has an discount which you can ignore for yours
Go through the following:
I will brief your requirement in short
MRP = 1012.5/-
VAT = (1012.5/1.125) = 900/-
so price before discount will be = 900/-
discount given at the rate of 10% = 100/-
Initial Price = 1000/-.
1. Create condition types as below:
ZR00 for price
Condition class = B
Calculation type = C
Plus/minus = A
ZSET for settlement (to knock off the effect of ZR00)
Condition class = A
Calculation type = C
Plus/minus = X
ZWST for tax
Condition class = A
Calculation type = H
Condition category = D
Plus/minus = X
Z007 for discount
Condition class = A
Calculation type = H
Plus/minus = A
ZDUM for net price
Condition class = A
Calculation type = A
Plus/minus = A
YWST for tax (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
YOO7 for discount (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
2. The following will be the pricing procedure configuration:
Step......No........Cond Type........... From.........to..........Man.........Req........Sta................Acc Key
10........0..............ZR00..................--..........--..........-...........-........---.................ZDU
20........0..............ZWST..................10............19...........----.............X............X...................
30........0.............text.......................10...........29...........---...........----.........X
40........0.............Z007.....................30...........39...........-----.............X............X
50........0..............text.....................30............49...........---...........-----.........X
60........0............ZSET.....................10...........19...........----............X............--.................ZDU
70........0............ZDUM....................50...........59...........----............X............---...............ERL
80........0............Y007.....................40...........49...........----.............X...........---...............ERS
90.......0..............YWST..................20...........29...........-----............X...........---................ZWS
ZDU - dummy account key for posting extra not required items.
ERL - account key for price
ERS - account key for discount
ZWS - account key for tax.
3. Condition records in VK11
Condition type----
Condition record.......
ZR00........................................1012.5.....................INR will be positive
ZSET.......................................100%...............................will be negative
ZWST.......................................10%................................will be negative
Z007.........................................12.5%.............................will be positive
ZDUM.......................................100%..............................will be positive
Y007.........................................100%.............................will be negative
YWST.......................................100%.............................will be negative
Condition records for Z007 & ZWST will be decided as per the conversion required. You will first have to manually calculate the amount for the condition type.
4. I create a sales order for single quantity for an item & the pricing will be as under:
ZR00 = 1012.5 (dummy account) - positive
ZSET = 1012.5- (dummy account) - negative will knock off effect of ZR00
ZWST = 112.5- (negative & no posting)
Z007 = 100 (positive & no posting)
ZDUM = 1012.5 (positive & posting)
Y007 = 100-(negative & posting)
YWST = 112.5 (positive & posting)
If still your scenario is not getting mapped then you can go to your ABAPer and he will develop a alternate base value formula to correct the calculations
Regards
Raja -
Tax calculation in Pricing Procedure
Hi Guys,
I have a pricing procedure setup to be modified for calculation of surcharge. The current pricing procedure calculates surcharge based on total price. Needs to change it to calculate on Unit price.How to achieve this?
Current Setup
Price Unit Price Qty. Net Price
PR00 655.55 5 3277.75
ZSUR = 3277.75*12/100 = 393.33
Required setup
Price Unit Price Qty. Net Price
PR00 655.55 5 3275
ZSUR = 655*12/100 = 78.666 = 78.67
Then this should be multiplied with the qty. 78.67*5 = 393.35
How to achieve this.
ThanksI solved this same issue by doing the following.
When determining ZSUR, create a Condition formula for alternative calculation type in VOFM.
calculate the 12% off of the PR00 each price and round this result to 2 decimals. In your example you would get .12 * 655.55 = 78.666 commercial rounded to 78.67, then multiply this rounded result with qty to get your extended amount 78.67 * 5 = 393.35 and put the result in XKWERT for ZSUR.
With this type of calcualtion you will always get consistant pricing regardless of qty. When you are finished with your formula assign it within config of the pricing procedure on your ZSUR
line. Hope this helps.
When calculating .12 * 655.55 , create a working data field and do a 'like' to netpr in your formula:
eg DATA: ZZEA LIKE KOMP-NETPR. ( netpr is curr dec 2)
when calculating zzea = .12 * 655.55 since the field is defined as 2 decimal, commercial rounding will be the default calculation(round up if >= .005, down if < .005). So in your example 78.666 = 78.67
Code looks like(had to deal with floating decimals):
DATA: ZZEA LIKE KOMP-NETPR.
ZZEA = KOMP-NETPR * XKOMV-KBETR / 100000.
XKWERT = ZZEA * KOMP-MGAME / 1000. -
VAT calculation through Pricing Procedure of MM
Hello gurus,
I have a doubt can we calculate and post the vat thru purchase condition type in pricing procedure, for excise and cess we are using Tax code with tax procedure TAXINJ, we are trying hard for it., we have even created new transactiion key and assign GL account to it, but still it is not posting at the time of MIGO.
your urgent help required,
AnandHi Anand
I too develop a new condition type for Vat in mm pricing procedure.
Our business process is as follows
We r transferring material to one depot to another to UK. we are doing STO through SD route. i created a vat condition type which is non inventorised and subsequently refund will be received.
Problem is that Accounting entries are not generating after doing PGI. Plese give your inputs on this.
I created a new gl accouts and assigned to posting keys.
Thanks
sitaram -
Agent's Commission calculation in pricing procedure only for NEW Saleorders
Hi Guys,
In a pricing procedure, .the base for agent commission was calculated on cost + markup price and freight and this base for commision + commision + insurance gave the base price.But now client wants to calculate commision from cost + mark up + freight + insurance + packing charges
So, the steps are changed in pricing and it is working perfectly. While checking the billing documents and open orders, it is showing new pricing procdure.
The pricing procedure should take its effect from now only and not for old billing documents I mean the open orders, open deliveries and open items.
I understand that in open sales orders, if update button is pressed on condition tab and carry out new pricing only changes will occur. Otherwise it will NOT happen
If I goto VF02 and take a billing documen, it is having the new pricing procedure
I didnot maintain new condition types. Only the steps were changed.
Please help me in this regard by suggesting a suitable solution.
Regards,
AnbuThanks a lot for your suggestion. i had already made the changes in the existing procedure and given them.... then only we realized the problem....they created around 15 billing documents that day and all showed the changed pricing procedure( these were open orders). but my client doesn't want to revert back to the old procedure and as a solution to the change in value for the newly billed documents they have issued the debit note.... now everything is ok( except that the changed procedure is seen in the old documents too. but the values haven't changed) so client is happy this way... hope there wont be any issue regarding this in future...
Thanks a lot for your advice.... -
Assinment of pricing procedure to doc type
Hi friends,
I am new to MM , how the pricing procedure is assigned to doc type, or how the pp is triggered in PO.
Thanks
madhuHi Madhu Sudan,
Pricing Procedure as you know is one and the same as calculation schema.
To administer the PP i.e. Determination of Calculation Schema for PO you will have to go to the transaction SPRO---SAP Reference IMG
Follow the node
Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema.
Once you are there In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence
Now coming to your query,
1) Assignment a Calculation Schema (PP) to Doc type
-- Remember It is not possible to assign PP to Doc type
2) Trigerring of PP in PO
-- Follow these underwritten simple steps:
i. Define a schema group for vendor under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. You will have to assign this same schema group in the relevant vendor master record.
ii. Define a schema group for Purchasing organisation under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. & assign it to the relevant Purchasing Organisation in the same step.
iii. Once this is done you have to Determine Calculation Schema for Standard Purchase Order under the node>Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination. In this step you assign Calculation Schema to a combination of Schema Group (Purchasing Organisation) & Schema Group (Vendor).
iv. Conclusion: During the time of making a PO; Shema Group of Vendor is picked from the relevant Vendor Master Record, Schema Group of Purchasing Organisation is picked from Customisation (where you assigned it) & A Calculation Schema is triggered for the combination of these two Schema Groups (PP that you defined in step iii)
Hope this explains it, for better understanding please read the IMG activity documentation for each activity.
For any further doubts please reply.
Regards,
Prithviraj -
Work flow process and pricing procedure
Hi All,
I want to know the process of workflow including the configuration.
Also i want to know the pricing procedure on how to do the pricing procedure config in purchasing i;e the calculation schema and all the detailed config.
Thanks
KennyHi,
Path: IMG -- Material management -- Purchasing -- Condition -- Define price determiantion procedure.
1. Crate the condition type (Copy from the standard one)
2. Create the calcualtion schema (Pricing Procedure) using the condition type wat u have created
3. Create the schema vendor and schema purchasing organisation
4. Assign the schema pur.org to your pur.org
5. Assign the schema vendor to your vendor
6. Assign the calculation schema (Pricing procedure) to your scheam purchase org and schema vendor combination.
At the time of creating PO system will find the price based on the below steps
1. First it will search the is there any schema pur.org assigned to the pur.org
2. Then it will search is there any schema vendor assigned to the vendor
3. Then it will serach is there any Pricing procedure linked to it.
4. Then it will serach is there any Access seq assigned to that condtion
5. Then it will search the condtion record created for this condition type
6. From the condition type it will pick the price.
Regards
Karthick -
Schema Group Vendor - Pricing procedure
Hi Experts,
My predecessors have defined a Schema for a vendor (say ZP). Now this vendor schema along with the std. pur org schema is assigned to a pricing procedure (say ZP0001).
we have condition type, and access sequence.
When I try to create a Po against a PR for that vendor then the PO is not picking up the price for that material from the pricing procedure.
However, if I change the 'Schema Group Vendor' by removing the user defined schema (ZP) and use the standard schema, the price is prompted normally.
Please advise as to what has been missed out in the pricing procedure.
This is very very urgent.. Pleaese help..
Thanks,
ManjuHi,
Check the following?
1. Are your condition types are assigned to Calculation Schema, Access Sequence ?
2. Did Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema is done?
3. Did you maintained Condition record(MEK1)
Note:
Just check again these below steps:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (Xk02)
11.Maintain Condition record(MEK1)
Regards.
BIju K -
VAT/Excise calculation - map pricing & tax procedures
Dear,
Pls tell me how to map my blw senerio;
In pricing procedure, i have
A- Gross price
B- Handlying charges
C- Excise on A+B,
here i need to calculate my exise on A+B values and it flows (C) frm tax procedure (taxinn). until here i'm ok.
D - A BC
E - Insurance (defined in pricing proce) on D value,
here i'm unbale to map my price, since the sytem taking A+ B price only, its not taking my D values... I need to map pricing & tax procedures, since Gross price, Han. charges and insurance flows frm pricing proce and Excise frm tax procedure.
Anyone has right solution, pls guide me...Hello sapjj
Here in your issue, u have to maintain a dummy condition type for excise calculation in your pricing procedure. The excise on A+B will be calculated in pricing procedure itself and not it flows from tax procedure.You have to make a condition type in pricing procedure and mark it as statistical in the procedure so that it doesn't get added to material value.
you are ok till gross price and handling charges, right?
Then you include your dummy condition type for excise amount calculation.Then in the next step calculate a subtotal without giving any condition type and maintaining 'S' in the subtotal field in the pricing procedure.
In the next step include the insurance condition type and calculate it on the subtotal.
This will help
Regards
Gregory Mathews -
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 -
Pricing procedure for Service PO and Service Entry Sheet
Hi
Can the same pricing procedure be used for Service PO and Service Entry Sheet? What is the purpose of creating a seperate pricing procedure for service entry sheet?
Regards
SoumenThere is no separate pricing procedure for Service Entry Sheet. Whatever the schema is determined in Service PO, the price is calcuated during service entry sheet. However you can maintain separate calculation schema for service purchase orders.
This schema will be determined based on the schema group assigned in Vendor Master.
Maybe you are looking for
-
I opened Firefox this morning and it told me I needed to download a newer version. I downloaded the new version. I got the image prompting me to drag Firefox to the applications folder. When I do that, it asks if I want to replace the old Firefox, I
-
How to create a 'window' in AE CS3
Hello, I have a video of a LED scroll sign and I am making it look like my own text scrolls across. I have text I created in Photoshop, saved as a ' .tiff ' , and imported into After Effects. I have put the text in the video and gave it a starti
-
I keep getting an Installer failed to initalize error
I am trying to install the trial version of Adobe CS 6 and I keep getting this error: "Installer failed to initialize. Please download Adobe Support to detect the problem". I did that and the Adobe Support Advisor says there are no problems. I tried
-
Flash Player Reading VideoGlide
I use a Kworld USB 2.0 to convert my analog video signal. I have a Mac mini so I use VideoGlide to convert the 2.0 signal. I stream live on UStream which runs its video camera input through Flash. I can't get Flash to recognize the "camera" i.e. the
-
Purchase requisition with MRP controller
Hi everybody, I need support because I have to control during purchase requisition to block users with specific MRP controller. I mean, user A only have permission to create purchase requisition with MRP controller Z and user B only have permission t