Use of Condiition Type JEXT in Pricing Procedure

Hi !
Can anybody tell me what is the use of Condiition Type JEXT in Pricing Procedure ?

Dear Indrajit,
JEXT - Total BED value and generally it will be 100% maintained in VK11. and more over if there are any discrepancies in the JBED -% condition type or some changes, then you also go with JMAN-Manual excise duties.
Ex:
Item   Condition type                Value
10             JBED(10%)                100( calculated on Assessable        value 1000)
20             JMAN (1%)                  10 (calculated on Assessable value 1000)
Then
30           JEXT                       110
and if there is no JMAN then JEXT value will be 100.
Generally if there is no JMAN , then JBED will be linked to Account key and JEXT will be treated as Statistical condition type.
And more over in the CENVAT Credit JEXT if offset against the JMOP( Purchases BED Value)
BEST REGARDS
SRI

Similar Messages

The use of Cond type tab in Pricing procedure determination

Hi Guys,
In T-code:OVKK we are doing the pricing procedure determination. But ther is one tab called as :CType(Cond Type) there in that screen after our pricing procedure. Could you please some one tell me what is the use of this cond type and where it's reflecting in SAP.
Regards,
Kumar

Hi,
It is very useful to avoid Data entry work Pricing Conditiontype for example: PR00.
Ex: When your creating Sales order by using Item proposal there may be 100 item
if you maintain this in OVKK you no need enter the price for each item when ever your process sales order just creat condition record by using VK11 and condition type PR00.
Proposed condition type for fast entry
The condition type that the system automatically proposes in the double-line entry screen during sales order processing.
ProcedureEnter a condition type. If you leave the field blank, the system displays the active price condition during sales order processing.
ExceptionIf you change a condition manually, this will be displayed in the double-line entry screen.
Regards,
MH
Edited by: Mohammad Minahazoddin on Nov 22, 2010 9:54 AM

Invoice pricing procedure not using alt calc type from the pricing procedur

The sales order has the same pricing procedure as the invoice but when the invoice is created it is not using the alt calc type that is on the pricing procured like it is on the sales order. This is causing one of the condition types to have different values on the sales order vs. invoice.
I am not sure what other areas to check to see why this is happening. Any thoughts?

I have checked and in the copy controls for Delv type = LF and target Bill type = F2 the Pricing Type = G (copy pricing elements unchanged and redetermine taxes). Condition types such as ZPR2 where there is condition record copy in correctly to the invoice. It is condition type ZZIF where it is determined from a routine, not a condition record, where I am having this issue.
Is there another place in config that I should be making a setting so that condition types determined by routines are copied to the invoice without being redetermined at invoice create?

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 to assign a pricing type to the pricing procedure ?

Business Scenario : When the prices change from the time the order is taken to the time the invoice is created, how can setup the system to handle the changes automatically ?
I would like to know How to create a pricing type and How to assign a pricing type to the pricing procedure so that I can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document.
Thanks for your input in advance.
Oscar

Hi !! Oscar,
1) For pricing type definition you would require the help of a developer.
2) However, most of the commonly occuring requirements are supplied with standard SAP.
You can assign a pricing type to pricing procedure as follows:-
IMG>S & D >Basic Functions>Pricing>Pricing Control>Define & Assign pricing procedures>Maintain pricing procedure> Here, locate your pricing procedure , in the fourth coloumn using the drop down list, you can assign a pricing type to the pricing procedure.
Now you can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document !
Regards,
PATHIK
Message was edited by:
Pathik Pandya

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.

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 type EK02 In pricing procedure

I'm having a problem with theis condition type as follows:
Create sales order
Add material A to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
Delete material A from line item
Add material B to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
I'm not sure where this value is coming from at this point. Can anyone point in the right direction?
Thanks, Mark

Hi mark
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
It has the condition category Q ( costing )
Now when you go to VOV8 , in the condition type field you can see the option EK02. because this condition type when used will be flowing to the controlling .That is the reason we assign EK02 to our sales doc type
Check in V/06 and select EK02 and go to its condition type details and check the calculation type field wheather it is in fixed value or not
Regards
Srinath

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

Use of subtotal column in MM pricing procedure

Dear experts,
Please tell me the use of subtotal in MM pricing procedure.
Regards,
ABHI

Subtotal is
u2022 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 vendor discount or the cost of a material) are stored.
u2022 If the same fields are used to store different condition amounts, the system totals the individual amounts.
u2022 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 order.
Hope this can assist you.
Thanks & Regards
JP

Tax codition type in purchase pricing procedure

Dear Sir,
My scenario is like that I want to define a tax condition in purchase pricing procedure which is paid to a differnet vendor, other than material vendor , I want the in system , In GR this value does not loaded on inventory value , But during vendor invoice this will appear as separete line item & goes to differnt vendor .
this is possible or not , if yes how what is done so that whenever this condition in Purchase order is there , in doing vendor invoice paid to different vendor
condition will not look like a delivery cost , It is cost paid to differnet vendor that material
thanks & regards
Shailendra

hi
for this u have to create a transaction event type and a new ondition
goto spro>Materials Management>Purchasing>Conditions>Define Price Determination Process>Define Transaction/Event Keys
here create a new key say ABC
now goto M/06 here copy the condition of freiight FRA1 ,say xyz
now goto M/08 here in ur pricing just add this condition and give the acct kay and accrual as ABC
now in OBYC u have to define a separate G/l acct for the key ABC
now when u create PO add condition XYZ now select this condition and click on deatails here u can change the vendor
regards
kunal

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

Output types assigned to Pricing procedures?

Hello,
Is there any transaction code / navigation to see list of output types (fax, print, edi etc,.) are assigned to pricing procedures?.

Hi,
You can see the list of output types assigned to a particular OUTPUT procedure in the database tables.
Go to SE16---Give the table name as T683S. In the table, give the usage as B and other selection criteria.
Now you can get the list of procedures to which your desired output types are assigned.
Hope this helps you

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

Use of Condiition Type JEXT in Pricing Procedure

Similar Messages

Maybe you are looking for