VOFM Pricing Requirement - Condition type at header

Hi Experts,
We have a new condition type, we want to use it in all our new invoices and has been made mandatory in the pricing procedure. Both the sales order and invoice have the same pricing procedure. I am using a requirement routine.
The code has to execute some logic for line items and pass the value to the new condition at the line item level. For new sales orders this is working absolutely fine as we have maintained a condition record and the condition exists. While creating any invoice from open sales orders which do not have this condition type, we are entering it at the header level.
I perform my logic and pass the value for the line items in TKOMV. These values do not get saved. Whereas, the values get saved when we have other condition types that are at the line item level.
The questions I would like to ask is:
1. Is requirement routine correct for this scenario? Or should I use condition value/condition base value routines to pass new values?
2. Is the method of changing the values in internal table TKOMV correct?
3. The value from this condition type has no financial impact on the FI documents, but it is mapped to COPA. Is there a way to write code to directly update the COPA value field in the COPA side without having to create a routine?
Thanks,
Abdullah Ismail.

You should not be facing this problem as system adjusts the difference in value for the last item. Try to update the prices in the doucment and check.
Regards,
GSL.

Similar Messages

Default Condition types in header of sales order

Hi
i have a requirement like this.
sales order should have default pricing Condition types in header details with amount(kbetr) field ready for input.
we have approched functional consultant he couldn't make the fields enabled but he couldnt .please give the solution approach.

Hi,
That is standard configuration. We should not make a any changes in that.
Regards,
Renuka S.

Same condition type on header and item level = printing problem

Hi
I have a customer using some condition types on both item level and header level in quotations, orders, invoices ...
In the pricing procedures it is customized (V_T683S-DRUKZ) that the conditions must be printed on header level (that is at the bottom of the documents).
My job is to make the Smartform to print the documents, and I want it of course to be as close to SAP standard as possible.
SAP standard will print these conditions on header level even if the conditions are at item level, but my customer wants the conditions created on header level to be printed on header level and conditions created on item level to be printed on item level.
I'm no pricing expert, so my question is:
Will it be fair if I tell the customer that using the same condition types on header and item level is bad practices - or at least bad karma?
Best regards
Thomas Madsen Nielsen

Hi Shiva Ram and Madhu
I have no problem understanding header vs. item conditions, so I really don't see anything in oss note 876617, that is relevant in this case.
Madhu - I do not agree that everything is fine. My issue is that I want to stick as closely to SAP standard customizing as possible. In SAP standard customizing of a condition type you can use the flag V_T683S-DRUKZ to determine if the condition should be printed on header OR item level - you can not choose both header AND item level.
I have a SAP standard smartform using two functions modules for reading header and item conditions. RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_HEAD. These function modules are based on the DRUKZ customizing flag and a condition marked for printing on header level will be supplied by RV_PRICE_PRINT_HEAD even when the condition is on item level.
My point is: SAP standard customizing does not support printing of same condition on both header and item level. I can of course write tons of code to work around this problem, but that would be bad practices

Pricing Error- Condition type not found.

Hi Gurus,
I have a issue with pricing.
Scenario :
For a pricing procedure i have 3 condition types ;
For example :
ZXED, ZXE1 & ZXE2.
Of these ZXED is Manual, Mandatory & Statistical in nature.
ZXE1 & ZXE2 are Manual.
When i create a sales order my pricing procedure is getting determined correctly.
The issue comes in when i try to key in the values at the item level condition in the sales order:
If i see the options(F4) available for me to select the condition types i get have see only one condition type i.e ZXE1. but esentially i should get to see all the 3 condition types as an choice of code(condition type).
Can any one help me to find out the possible reason why i get to have only one condition type for selection.
Your suggestion is highly appreciable.
Rgd
VIVEK.

Hi,
1. Understand onething that a particular condition type if maintained "mandatory" in the pricing procedure then you will have to create the condition record for it using transaction code "VK11". If it is manual then you can give the rate directly in the sales order after selecting it. Since you have maintained "manual", "mandatory" & "statistical" for the condition type "ZXED" at the same time that is why the system is giving you the error "Pricing error" Mandatory condition ZXED is missing."
2. Also you want the system to show you all threee condition types "ZXED', "ZXE1", "ZXE2" to choose manually as per your requirement. Do one thing go to transaction code "V/06" - select the required condition type say "ZXED" - double click on it - in the "changes which can be made" section you will see a field for "Manual entries" - in this select "no limitations" and save the condition type. Similarly do it for the other 2 condition types and save it.
I tell you you must have maintained there "D-not possible to process manually". If this is maintained then the system will never show you the condition type to choose from the condition type list in the sales order.
Note: You have maintained for "ZXED" manual/mandatory/statistical. Now as it is mandatory also you have to maintain the condition record for it in "VK11". Now if you change the rate of this condition type in the sales order then when you will create the invoice in "VF01" the system will show that value only which has been maintained using "VK11" because in billing also the system fetches the condition record from VK11 for the mandatory conditions.
Hope this clarifies and solves your doubt.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

VOFM - pricing requirements ( abaper require some functional assistance)

HI,
I had written the required code in one of the customer routines in the transaction: vofm.
to change the tax code according to the country of destination.
I was given information that this will be triggered during the sales order change..(va02)..
When i put a break point in that include it is not triggering..
Can anyone tell me how to trigger (either std include or customerized include) of transaction: vofm (pricing requirements) in the sales order change tranx (VA02).
thanx

Hi there,
Once the routine is configured in VOFM, it has to be activated for eg using RV80HGEN. Only then you can apply that routine.
Also when the logic is not getting triggered in debug, then it means that either the logic is wrong, code has been put in a wrong location or tables / fields are called wrongly.
Ask the ABAPer to check points & then try.
Also changes in VA02 is captured by function V & new entry by H.
Regards,
Sivanand

MM Pricing procedure - Condition type post to different GL account in MAP

Hi All,
We have a requirement for posting intercompany Stock transfer between Company A and B, and the transfer price will be Moving Average Price (say $ 100) + Mark up (say 25% i.e., 25) of supplying plant.
Created a new PO pricing procedure, and created a new Accrual condition type ZMRK for markup and made it statistical posting. Also in the pricing procedure the Condition type we assigned an Account key ZM1 and Accrual Key ZMA. we tried posting the Goods receipts in the receiving Company B, and it is posting the following entry :
Invetory A/C DR 125 (note: Account key ZM1 was not considered for debit account for markup)
GR/IR A/C CR 100
Markup Accrual A/C CR 25
REQUIREMENT: Our requirement is that the Mark-UP condition should not hit Inventory Account and should be debited to I/C Mark Up account (assigned to Account key ZM1) and entry should be as below:
Inventory A/C DR 100
Markup A/C DR 25
GR/IR A/C CR 125 (accrual is not required, if we can include the markup into GR/IR account)
OR
Inventory A/C DR 100
Markup A/C DR 25
GR/IR A/C CR 100
Markup Accrual A/C CR 25
NOTE: The Material is maintained as Moving Average Price and we dont want to add the Mark Up cost into the MAP of the receiving plant.
Please check and let me know if there is a way to do a condition type in PO pricing procedure to solve the issue of not hitting the inventory posting for condition record or any other way to handle this requirement.
Thanks in advance,
Surya

Hey surya,
I am also facing the same issue. Can you pls let me know whether you achieved this using any standard configuration.

Pricing requirement: condition to be in(active) linked to another condition

Hi,
I have created 2 new conditions type YR05 and YR06 in pricing procedure.
I would like that the second one (YR06) is considered as active only if amount of condition type YR05 is different from 0. (KOMV-KEBTR and KOMV-KWERT different from 0)
Could you please advise how I should handle it as I am not so familiar with requirements and Condition base value.
In addition, I created an additional line in pricing procedure to sum the amount (condition value) of these 2 conditions (to be printed on the billing document).
Any idea of the code to put in requirement and calculation type ?
Thanks for help,
Brgds,
VM

Hi,
In pricing procedure, you can put a subtotal for YPR5 (like D for XWORKD).
Then, in new routine (basis or formula), you can check if XWORKD <> ' '.
If yes, xkomv-kinak = ' ', if no, xkomv-kinak = 'X'.
This is just an idea.
Regards,
Lionel

Pricing - Requirment / calculation type / base value

Dear Friends,
Thnaks for the support and guidance provided by you for my previous posts
In Pricing Procedure we give Requirment, Calculation type and Alternative formula for condition base value, I would like to know where do we exctly define all this?
Or are they standard? If standards where we can see how they works?
Regards
Vishal

Hi,
go through the below Examples for better understanding ..
Example: 1
Condition Type: PR00
Requirement 2 Item with Pricing
Purpose:
This is an example of a pricing requirement. This requirement is met if the document item category is relevant for pricing and no previous condition in the pricing procedure has set the condition exclusion flag. This requirement can be assigned to condition types in the pricing procedure to avoid unnecessary accesses to the database when an item is not relevant for pricing or a condition exclusion indicator has been set.
Example: 2
Condition Type: Net value
Calculation Type: 2 Net value
Purpose:
This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.
Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing procedure. It contains the amount excluding taxes.
Example: 3
Condition Type: R100
Alt.Condition Base Value: 28 (100% Discount)
Purpose:
This is an example of a condition base value formula. A condition base value formula can be used to influence the basis the system uses when computing a pricing value. A condition base formula is assigned to a condition type in the pricing procedure.
Formula '28' sets the rate of the condition to a 100% discount. This formula was delivered with condition type R100 to support free goods functionality.
Reward if it is useful,
Chandramohan

Pricing schema condition type

How to substract two condition types to get another condition value.
ZD01 contion type value-200
ZD02 contion type value-500
ZD03 Condition type value= 500-200
How to map this in the pricing schema
Regards
Umapathy.M

Hi,
You have to store value of ZD01 and ZD02 inn 2 variant (using column sub to) in pricing procedure. Then, you have to create 1 new routine to determine condition value for ZD03 using T-code: VOFM and assigned it in condition type ZD03 in pricing procedure.
(Subtract is done in new routine using ABAP Coding)
Regards,
Pavin

Pricing: New condition type not getting listed in options in product master

Hi,
I have created a new pricing procedure and also created a new condition type for it. I am trying to create a condition record in the product master for this condition type but the condition is not there in the list of conditions. How can I inlcude it in the condition list?
Even the new condition type I have created by copying 0PR0 is not getting listed in the options, whereas 0PR0 is getting listed.
Regards,
Meenakshi
Edited by: Meenakshi Sawhney on Sep 9, 2010 8:27 AM
Edited by: Meenakshi Sawhney on Sep 9, 2010 8:29 AM

Hi Meenakshi,
you need to enhance the condition maintenance group in the customizing, which is assigned to the product master. Please check: IMG: Customer Relationship Management -> Master Data -> Products -> Special Settings for Sales Operations -> Assign Condition Group to Application CRM and IMG: Customer Relationship Management -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Maintenance Group.
Best Regards,
Michael

Manual Pricing for Condition type pricing

Hi experts,
I am changing the price in sales pricing of cj20n transaction manually and it get updated, working good.
Is it possible to get the updated manual pricing in all the transactions related to CJ20N transaction.
Thanks&Regards,
Vino

Hi..,
Yes. Its possible.
I want give some function support on this as worked on condition types in another transaction.
You needs to be check that if your pricing procedure is having that condition type or not and also you have to check that condition type is mannual or not.
First get your pricing procedure...
For this goto V/08 transaction code and select your pricing procedure there -> double click on control folder-> there you can get all condition types for that procedure -> and check ur condition type is mannaul or not.
Thanks,
Naveen.I

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

Pricing Procedure Condition Type EK02

Dear, Gurus
I have an MTO scenario. All is working I mean from the production order the cost is coming to my sales order in condition type EK02. But that is making all other condition types as inactive.
current pricing schema
Pr00 Price it is manual.
Other Z condition types which are also manual.
Then EK02.
Gross Sales
K005
K007
Net Sales
MWST
ZSED Sales excise duty
Value after Tax
VPRS
also, at the top the net value does not change at all it stays constant and seems to pick up the EK02 price.
I want all other condition types to be manual but active even if EK02 price is picked up from Production Order.
How can I set it up to make them all green as active?

Previously all my condition types were manual entry so all were green.
Pr00   manual
Zman manual
Zsat   manual
Zetc   manual
Also, in PR00 class is B=Prices       Calc Type = C for qty
All the ZMan, etc is A=discount/Surcharge   calc type=B fixed amount.
To be scenario all I added was condition type EK02 in pricing procedure and by standard it is in class B=prices     calc type=C for qty, and cond cat=costing
When production cost transfer to EK02 lets say example 500. All those previous cond are yellow inactive. and then net price equals 500!
In terms of my terminology and basic understanding you can only have one cond type function as price in class B=prices.
So either the EK02 or the Pr00 needs to have cond type B for Price. If I make the Pr00 a discount/Surcharge nothing changes in respect to updating the price in sales order. Lets say even if its all corrected and I have lets say EK02 function as price the Zman and Z condition types are under discount surcharge, that at least should not be inactive?
Please help
thanks

Scaling in case of Pricing Procedure Condition Types

Hi,
I want to maintain Scaling in Condition Types of the Pricing procedure. Please guide me to maintain it.
Thanks & Regards
Saeed Arif

Hi,
If you have maintained Purchasing Info Record: In ME12 transaction go to Conditions tab. Select the Condition Type 'PB00' and click the Scales icon (F2) on top of the screen. Here, maintain the Scales.
First decide the Scale Type, Scale Basis and Validity periods for which you want to maintain the Scales. Save your changes and you can see the effect on Price, while creating the PO for the quantity mentioned as per the Scales.
Regards,
Narayana.
Edited by: Narayana Ghanta on Oct 13, 2008 3:43 PM

Priceing procedure - condition type - number of units

Hi, I have a condition type in my pricing procedure. When I display item conditions for an item in a sales document I can see that my condition applies to 1000 units of measure. How do I change my condition so that the calculated amount applies to only 1 unit of measure?
Thanks

Hi Marko
Go to VK12 and change the UoM . Change the UoM and maintain the base unit of measure (ex:pc) that you have maintained in MMR . Provided you have not maintained Sales unit of Measure.
Also check wheather you have maintained any alternative UoM or not and that alternative UoM has been maintained in VK12 or not
Also check in V/06 in that condition type details wheather any UoM has been maintained or not. If it has been maintained then make the UoM feild blank by removing the UoM that has been maintained in V/06 and then check
Regards
Srinath

VOFM Pricing Requirement - Condition type at header

Similar Messages

Maybe you are looking for