Condition Type dependant on Pricing Date

Hi,
I want to know how to make a particular condition type dependant on pricing date. e.g We have a pricing procedure where a couple of condition types are only displayed, when I go to the header details in VA01 and put the pricing date manually in the Sales Tab.
Thanks
Amol

Hi Amol,
Go to V/06 and goto perticular condition type detailes screen, At bottom there is control data 2 in that there is field called 'pricing date' you enter "B" in that field, I think it will fullfill your requirement.
If it is helpfull please reward me with points,
Regards,
Murali

Similar Messages

Problem of DIFF (Rounding Off) Condition Type in Sales Pricing Procedure

Hi All,
This problem is related to Sales Order. The system is not picking up a condition type in the pricing procedure.
For example when I am raising a sales Order where the Trade Price is being calculated with the help of a Alternative Calculation Type , Subtotal 1 , X in the the Print column and Posting Key ERL are assigned to it.Here in the end the condition type DIFF is not getting populated in the pricing though it is maintained in the pricing procedure. When I am checking in the pricing analysis the error message and its detailed description which is shown as follows -
DIFF 011 Condition ignored (requirement 013 not fulfilled)
The requirement 1. was assigned to this condition in the pricing procedure. This requirement was not met in the preliminary condition step, and so the condition was excluded from further processing.
You can use Additional information to display the requirements used.
Now considering the above scenario please suggest to attain my requirement.
Thanks & Regards
Priyanka

Dear Priyanka,
The "reqt" field in the pricing procedure basically tells d system that the routine mentioned in this field is a sort of prerequisite without fullfilling of which the associated condition type will not get xecuted.
In ur case u have selected "1" which is for condition types A001, B001 etc used in "material listing / xclusion" function.
For condition type DIFF, the correct value is "13" i.e "Rounding as per T001R".
So just replace "1" with "13", things will b fine.
Please close the thread if answered.
regards
Param

Use of MM condition type into Sales Pricing

Dear All
I am having two MM Condition types in STO pricing procedure which are statistical in nature. Condition type A is having condition category G (Cost) and B is having H (Base Price). I have created both the condition types in SD side using V/06 with dummy access sequence without maintaining condition record. Condition type having contion category G is getting populated in sales pricing automatically but second condition type having condition category H is not getting populated automatically from the MM condition records which was maintained in the MM side using MEK1.
Please advice whether I can populate the above condition records automatically from the MM side. If yes, then please guide me with steps to achieve the above requirement.
Thanks in advance....
Regards
Animesh
Edited by: Lakshmipathi on Oct 11, 2011 10:30 PM
Thread Locked as duplicate post is not allowed

Dear Shiva
Thanks for u'r prompt reply.
I will try the same as advised by you and confirm.
Regards
Animesh

Condition types for import pricing

hi,
     the conditions types for import pricing procedure are not appearing.
please suggest all the notes from where i can take reference and create the condition types for import process.
please also suggest what are they?
with regards

Hi anitha,
In case of import purchase. u have to configure the conditions in pricing procedure. The condition types are as follows:
1)jcdb               basic customs
2)jcv1               CVD
3) jec1               ECS on CVD
4)jed1              cess on customs
5) j1cv                secess on cvd
6) jsdb               secess on customs
Go to the master note no 1032295 for recent budget changes.
award points if found useful
chintu

Can anyone explain what a condition type means in pricing.

Hi,
Can anyone explain what a condition type means in pricing. And how to create condition type and how it effects Pricing conditions.
As I am new to this area. Detailed explanation is highly appreciated.
Thanks a lot,
Rasheed

Hello Rasheed,
Below mentioned are the few important things related to pricing.
- You first define Condition Tables .
- Define Access Sequence and assign condition tables to it.
- Define Condition Type and assign Access Sequence to it.
- Now define Pricing Procedure and assign Condition Type to it.
- Now you define Pricing Procedure Determination using Sales Org, Distribution Channel ,Division,Document Pricing Procedure and Customer Pricing Procedure which are the key fields.
The above steps can be done in SPRO.
-Now maintain the Condition Records(for eg:For the specific material what is the cost or for a specific customer what is the cost of the specific material etc) using Txn:VK11.
- Once you maintain the Condition Records , you can reflect the same values in Condition Type in SPRO.
Hope this information is helpful for you to relate Condition Type in Pricing,
Please reward with points if this information is helpful for you.
Regards,
Shanthala.

Including Condition type (JEXS) in Pricing PRocedure

All SAP Gurus,
I have included the condition type JEXS in pricing procedure since 01 May 2008.
But still while creting some POs this condition type is not picked up (although maintained in Pricing procedure), what may be the reason?
What can be done with the old POs when this condition thpy was not maintained?
Regards

Hi Raj,
Please check your PO link to pricing procedure as mentioned below,
1.What have schema group assigned in PO ventor master?
2.What have pricing procedure assigned in schema group?
MM > Purchasing > Conditions > Define price etermination process > Define schema determination.
3.Then check your condition type(JEXS) whether it is in that pricing procedure.
4.Also check your condition type(JEXS) validity period.
Please reward points if my information useful.
Best Regards,
Nagapandian.

Pricing condition in Billing document (Pricing Date)

Hi Gurus,
I have a sales order which is created on 10.01.2012, the pricing date in the sales order is the same (10.01.2012). The Delivery was created on 22.02.2012 and Actual GI date is also 22.02.2012.
Now when I am creating the billing document, the pricing condition value is showing as '0'. I checked the pricing analysis and found that the validity of the base price condition Z001 was from 10.01.2012 till 14.01.2012 in the sales order.
As the Actual Goods Issue date is taking as the 'Billing date' as well as 'Pricing Date' , the system is not able to find a valid condition type as on 22.02.2012 (GI date). The pricing type in copying control of Delivery to Billing is 'C - Copy manual pricing elements and redetermine the others'.
So I would like to know your opinion on the following.
1) Can I create the billing document using VF01, manually change the pricing date as 10.01.2012 and do the price update using rule C? Will it fetch the price based on the pricing date?
OR
2) Maintain the condition type Z001 for the GI date and do the billing?
Please let me know which is the best way to adopt?
Regards,
SAM

Hello,
If you have necessary authorization to change the Pricing Date in Invoice, please go ahead.
Change the Pricing date in Invoice, go to Conditions tab & update the Pricing. System will fetch Condition Records as on that date.
Hope this helps,
Thanks,
Jignesh Mehta

Pricing Conditions and how the pricing date is determined

Hi all,
Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
Hope i have expplained this ok, if not and you need more info let me know.
Regards
Steve

Hi
There is a difference between Service Rendered Data and Pricing Date.
Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
Regards
Amitesh

How to rescrict the user to enter a manual condition type once in pricing

Hi All,
We are using a condition type ZSP1 in our pricing procedure. I want that the user should be able to enter the condition type only once during pricing.
eg Suppose the user has entered ZSP1 as 100 in the sales order , then he should not be able to enter ZSP1 again in the pricing. Only one entry should be allowed for the condition type ZSP1
Please respond if you need any further clarification.
Regards
Adity

Hi,
you can Restrict the entry of Condition type Twice with Following User Exit
USEREXI
USEREXIT_PRICING_PREPARE_TKOMK
USEREXIT_PRICIN
we have Implemented for one our Client

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Condition types substraction in pricing schema

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

Can you try making the 2nd condition as a discount condition and then create a subtotal from 1st to 2nd.
ZD01 contion type value-200
ZD02 contion type value-500 >> make this a discount (negative) Copy std condition R002 for absolute discount.
ZD03 Condition type value= 500-200 >> Subtotal 1 to 2 will give the results you want.

Access for Condition Type of a Pricing Procedure

Dear CRM Gurus,
I have a scenarion whereby we have replicated the pricing procedures of ECC in CRM. In ECC I controll the activity of display of a condition type through the step no. Similar access control is desired in the CRM too.
I was advised for an object in CRM but that works best if the pricing procedure is of CRM origin only, as mine is from ECC it is non editable in CRM.
Would request kind guidance on this please.
Regards,
Tariq

Hi Try this.
CALL FUNCTION 'RV_PRICE_PRINT_REFRESH'
TABLES
    tkomv = tkomv.
g_komk-mandt = sy-mandt.
    g_komk-belnr = itab_disp1-vbeln.
    g_komk-knumv = itab_disp1-knumv.
   g_komp-matnr = itab_disp1-matnr.
    g_komv-zaehk = '01'.
    g_komv-kappl = 'V'.
    at end of knumv.
      call function 'RV_PRICE_PRINT_ITEM'
        exporting
          comm_head_i       = g_komk
          comm_item_i       = g_komp
     LANGUAGE          = ' '
   IMPORTING
     COMM_HEAD_E       =
     COMM_ITEM_E       =
        tables
          tkomv             = g_komv
          tkomvd            = g_komvd
      append g_komv.
    endat.
endloop.

Manual change of condition types in a pricing procedure

Hi,
I want to know the difference between
a) Setting value as C (Manual entry has priority) in the Manual Entry field of the condition type (transaction V/06) and
b) Setting the checkbox of "Condition determined manually" checked in the pricing procedure screen (transaction code V/08) aginst a specific condition type.
Please let me know in case of any other details.

Dear Christino
a) Let us assume, your pricing condition is PR00 and you set this as Manual entry has priority. You are maintaining some value in VK11. While creating sale order, system will pick from VK11 but however, you can change manually which will over write the system generated price.
b) Let us assume, for your pricing condition PR00, in V/08, you set the box Manual and also you have maintained in VK11. When you create sale order, in the condition tab, you wont see any condition value and all values will be zero. Once you input PR00 manually, other conditions will flow.
thanks
G. Lakshmipathi

Delete Condition Type Depending on Item category Va01

HI all,
I wan to delete condition record depending on item category. I have a good link from sap.This link explains how to hide the condition but i want the delete the condition. was badly struck here.
http://wiki.sdn.sap.com/wiki/display/ABAP/ManipulatingPricingconditionsdisplayinSalesdocumentwithUserExit-LV69AFZZ
Regards,
madhu
Edited by: madhurao123 on Mar 24, 2011 2:19 PM

Hi,
We had a similar requirement once, and towards the end we realised that deleteing rather than hiding it was a bad idea.
Think beyond the scope, that if a future sales order created with reference needs this condition record; manual entry will again be dependent on your pricing procedure and is a mess.
But if you do want to delete it; go into debugging and decide which user exit you would want to use and delete that line of the condition record from XKOMV table for that Sales Order

Condition type value in Pricing

Hi
i've maintained my condition type selling price in my pricing procedure and i've given the value in my conditon record for the same but it's not getting determined automatically in my sale order level but it takes the value manully in the sale order
Vinz

Hi,
Go to V/06 >>> Select you condition type >>> Details
In front of Manual entries - B (Automatic entry has priority) or make it blank (No limitations),
Once you maintain condition record in vk11, it will flow in sales order automatically
Kapil

Condition Type dependant on Pricing Date

Similar Messages

Maybe you are looking for