Config required for EK02 condition type in Sales Pricing procedure

Dear friends,
I am trying to derive a costing run for sales order. I would like to know what are the config steps required to arrive a percentage factor for GP.
Kindly guide me in this regard,
Thanks in advance,
Vinayak

Hi,
If you are doing sales order costing then you will have to define the condition type EK02. Go to V/08. Select the Procedure used in SD. Click on Control. Enter the condition EK02 - Calculated Cost and mark it as statistics.
You sales order cost will be stored in such condition type.
Regards,
Jigar

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

How can we create new pricing requirement for a condition type

Hi All,
I am in urgent need of creating new pricing requirements for a condition type.
Or if there is already a conditin type existing and we want to make changes in the pricing requirements of that condition type, How can we do so ?
In short if you can let me know how does pricing get impacted by the condition types.
Thanks
Mark

Hi!
The common transactions for condition mantaining are VK11, VK12, VK13.
In SPRO - Sales and distributoin - Basic function - Pricing - Pricing control - *.
Is this what you want?
Regards
Tamá

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

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.

Default Currency for freight condition type in sales order

Hi Gurus,
I have Freight condition type, maintained condition record with combination of Customer, Incoterms & Material Group.
In Customer Master Currency is USD or EURO.
When we create Export sales order, so by default currency should come INR, not USD or EURO for Freight condition type from Customer master.
How to get this requirement.
Regards,
Rakesh

Hi Rakesh,
I think you need a revision on condition table and access sequence for frieght condition records from SD >> basic functions >> pricing >> pricing control >> follow standard pricing configs. Actually, you need to add country ( ALAND ) and destination country ( LLAND ) fields to your table and access sequence for export sales.
After those configs, you can create records in USD or EURO for domestic sales and create records INR currency for export processes.
I hope you can neet your requirement by using this way.
Regards,

Issue regarding condition pricing date as system date for some condition types in sales order

Hi
I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
Regards
prashant

Hi
When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
Regards
PK
Sales order header change mode VA02
Here pricing date VBKD-PRSDT = 04.06.2016
Item change mode
I have added new line item 150 on 14.06.2014
Changed the condition pricing date to 14.06.2014 & saved
After saving I have gone to Va02 screen of line item 150
& there I have gone to condition pricing date field from item condition tab
for JEX2 condition type but still here condition pricing date is showing as
04.06.2014 as below.
Condition pricing date
My requirement is like this
For some particular conditions like JEX2 condition pricing date will take as system
date instead sales order creation date when I will add a new item 150 on
14.06.2014.but for other conditions it will show as order creation date for the
same line item 150 .

Can we attach requirement for manual condition type

Hi,
Pricing question....
ZOTH is the manual condition type
(The condition type configuration: - Manually editable, no access sequence attached )
(Pricing procedure : - No alternative calculation type attached)
Can I attach a requirement to ZOTH in the pricing procedure?
Laxman

hi,
we can very well have requirements for manual conditions also. Like we have standard requirement "2" Item with pricing and this is assigned to PN00 ( Net price ) condition which is a manual condition.
you can check in RVAA01 pricing proc. also
regards
sadhu kishore

Authorization object for manual condition type in sale order

Hi experts
I want ask them, If exist an authorization object for manual Condition type (KOMV-KSCHL) in the sales order (VA01/VA02), that the user don' t can create neither modify the sale orden with a specific manual condition type (payment term) by stardard way.
Best regards
John Angulo

HI John,
I would be surprised to know that someone uses the Payment terms as a condition in the Pricing procedure for sales orders. The payment terms define when the customer agrees to pay, (15, 20, 45 ,....days or 5 years or 10 years....whatever it be)
this detail for what i know is in the sales order header,and ideally has nothing to do with the Item level material price conditions.
its ok, If you mean something else by payment terms.....in principle you can have a conditon type restrcited such that manual entries on the condition are not possible. this cane be done in SPRO customizing, i am sure your functional consultants would know what to do (SPRO->Sales and Distribution->Basic Function->Condition Types), in the tab "Changes that can be made" have a value that says manual Processing is not allwowed
The ABAP route mentioned above is for a different scenarion and i dont think it is necessary for your requirement

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.

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]

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

Consignment process and Condition types in Export Pricing Procedure

Hi,
Can any body tell me the
1. consignement process i.e which document are used at which level
2. when we are going for exports sales then which condition types are used and on which calulation is based on.
thanks
harmeet singh

Hi there,
Consignment is a business process where the goods are stored at the customer / consignee location but are billed only when they are actually consumed.
It has 4 processes:
Consignment Fillup: order type KB, item catg KBN, Schedule line catg E0 or E1. This is when the stocks are moved from the plant stock to the consignee location.
Consignment Issue: Order type KE, item catg KEN, Schedule line catg C0 or C1. This is when the customer actually uses the goods for cunsumption.
Consignment Return: order type KR, item catg KRN, Schedule line catg D0. This is when the customer puts back the goods into the consignment stock (returns to condignee location)
Consignmnet pickup: order type KA, item catg KAN, schedule line catg F0, F1. This is when the stocks are put back into the plant stock from the consinment special stock. That is from the consignee location to the plant.
For all the above order types it has standard delivery LF & returns delivery LR delivery types.
Stocks at the consignee location are maintained as consignment special stock. Controlled by indicator W in item catg KEN.
Regards,
Sivanand

Condition type MWST in Pricing procedure US

Hi ,
I have added the MWST condtion type in pricing procedure for US .This condition type is not appearing in pricing procedure.This condition type has an access sequence MWST.Can anybody guide me on this how to correct this
Thanks in advance
Regards,
Nitin Amritkar

HI,
The MWST condition typeeither has 'manual tick ' in the pricing procedure.If that has u have to enter the condition type by F4 selection only.Otherwise u remove that tick and ckeck u can get MWST condition type automatically in all condition types.
Regards,
Andra

EK02 condition type on quotation

We currently see and utlize the EK02 condition type on sales orders for configured parts (assembly order creates).
However, when creating a sales quotation (VA21), the EK02 condition is not active/not populated.
Is there a way to get the EK02 condition to calculate on a quotation? Like maybe some way to attach a simulation production order to it that doesn't really create demand in the system? Would I need a new production order type for this?
Gina Feldner

Hi Gina,
First check whats the requirment type for quotation in your system. You can check this by clicking on shipping tab in the overview screen. Then go to the Transaction" OVZH" and see whats the requirment calls associated with it. Once you identify the requirment class, check If you have the entry "EK01" at the condition type line items field in the requirment class. Transaction code for this is "OVZG". If it is not there maintain that. Then go to the conditions screen and see whats the pricing procedure. In V/08 , Check if the condition type "EK02" is maintained there. If it is not ,Maintain the condition type in the procedure .This would resolve the problem. Other wise you can maintain the "EK02" in the sales document cofinguration (VOV8) at condition type lie items and maintain the same in the pricing procedure. Only difference is If you maintain this condition in the sales document type this is valid for all the items in the sales order and If you maintain this in the requirment class, this is valid for only the documents which have this requirmanet type. Kindly please let me know If you need any more help on this.
Regards.
Ram Pedarla

Config required for EK02 condition type in Sales Pricing procedure

Similar Messages

Maybe you are looking for