Condition Type 0K07 not determined

Hi All,
I have defined two conditions records for 0K05 ( Customer/Material discount) and 0k07( Customer Discount).
In Sales Order in Conditions only 0K05 condition is calculating , but 0K07 is not determined.
in Pricing Procedure definition both the condition types are present.
Thanks,
Nagesh

Hi,
Have u maintained condition record for condition type 0k07 in BP??
Thanks & Regards,
Anirban

Similar Messages

Condition Type NAVS not determined for Goods PO

Hi all,
I am working on SRM 5.0 and R/3 4.6C.The problem im facing is for the tax condition determination for PO for Goods type which replicated from SRM to PO .
In case of Service PO,the conditions are determined correctly and can be seen in the PO print out.However In case of a goods PO,if i goto conditions tab in ME23N for the PO,the conditions (NAVs) are not determined as well as they cant be seen in PO print .
The config on R/3 side is Correct as in case of manual PO(PO created directly in R/3),the conditions are determined correctly.
Now when i debuuged the BAPi "BAPi_PO_CREATe1",i observed the following:
If i chnage the field PO_PRICE in the table POITEM to "1",then conditions are determined corretcly for the PO.However by dfault,the value for this field comes to "2".
This field is nothing but indicator of the price i.e. 1 for Gross and 2 for Net.
Can anybody explain me the link between this price and condition types determined in PO.
Thanks.

Check out SAP Note 580225 - Purchasing BAPIs: Conditions and pricing
Hope it helps

SHIPMENT OUTPUT TYPE AUTOMATICALLY NOT DETERMINED

DEAR SAP Gurus,
I got one issue i.e in shipment document the output type is not determined automatically.I checked the config settings , everything is ok and condition records are already maintained. Pl resolve this ASAP . I need to close this issue in 2 days..
Thanks in Advance...
Regards,
Rafiq

hi,
You will resolve it following this:
o Start Transaction VL10CUC ("Parameter per Profile in Delivery
   Process") in the change mode.
o Goto the detail screen of profile '2000'.
o Check the status of parameter 'No OutputDet.' and correct the
   setting of the parameter:
   - If parameter 'No OutputDet.' is active, the output
      determination is not executed for the process.
   - If parameter 'No OutputDet.' is not set, the output
      determination is executed for the process.
Regards,
david

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

CONTITION TYPE 0K07 Not detected

Hi All,
I have maintained conditions for condition 0k05 and condition 0k07.
My pricing procedure 0crm2 has both condition types, but in conditions tab only 0k05 discount is appearing , but not 0k07 , have give 5% discount for 0k07.
Thanks,
Nagesh

Hi,
Have u maintained condition record for condition type 0k07 in BP??
Thanks & Regards,
Anirban

Expense condition type does not transfer to CO-PA

Dear guru,
My client would like to post expense (ex. promotion expense) via sales order, then SD consultant create condition type and assign expense G/L to this condition type and I assign this condition type to value field via tcode KE4I. When we create sales order and use this condition type, value of this condition type is not transfered to the value field. I set cost element with category '1'. I know standard is not support for this situation. Please kindly to suggest me for solve the problem 'How do expense value of condition type from sales order will be transfered to CO-PA', example user exit or others.
Thanks in advance.
Regards,
Nattakarn.

Hi
Changing the cost element category to 12 can be done only at the begining of the fiscal year as follows
But if promotional expenses is already created as a cost element with say category 1, now if you want too change it you might get an error KS134 Field change CElem Category is not possible (transaction data already exists)
Hence use TCode KA02, Edit->Analysis Period, Click other analysis period provide from begining of fiscal year to 12/31/9999.
You might have to create a new GL Account cost element if you want to go ahead with the changes in middle of the fiscal year
Regards,
Suraj

Condition type is not get in the PO output

Hi,
I have defined a new condition type ZRA0- Discount as discount charges .
The condition type is not getting print out in PO copy.
The vendor wants to see in the PO copy.
Pls suggest how to configure
Regards
Sp

Hi,
If i understood your problem, you would like to print the discount in PO print copy along with price.ok.
then check with your Abaper,he can fetch the Discount value for that perticular condition type(ZRA0) & print in the PO copy.Its depends on the print programme to get the data from the document to the print out.
Regds

ZPRS- Cost(data source H) condition type is not visible in CRM sales order

Hi Colleagues,
I created a sales order in ERP. In the sales order the condition type ZPRS- Cost(data source H) is available. I downloaded the this sales order to CRM i can able to see the ZPRS condition type in sales order.
But when i create a new sales order with the same data (BP, Material,Sales organization) the condition ZPRS is not visible in the sales order. When i checked the PRC_TRACE it is showing the error as "Condition with external datasource has not be found".
Can any body help me in this issue.
Tanks and Best Regards,
Rajeswari

Hi Michael ,
Thank you very much for your answer. I just require one more confirmation from you.
Could you please confirm If we post a returns document in CRM system directly the "ZPRS or VPRS - Cost" Condition type will not appear in the return document condition types.
Untill and unless it is a billing document in CRM system the "cost" condtion wont appear rt?
Could you please confirm it.
Thanks in advance for your help.
Best Regards,
Rajeswari

Condition type is not reflecting in sales orders

hi,
i have created two condition type like jser (service tax) and other one is jste(service tax +cess) but in pricing procedure jfact it is reflecting but while making contract order these two condition type is not accessing.
please help in this connection.

Hi,
After Creating the CONDITION TYPES you need to assign the condition types in the PRICING PROCEDURE
goto the
SPRO->FINANCIALACCOUNTING>FINANCIAL ACCONTING& GLOBAL SETTINGS>TAX ON SALES /PURCHASE>BASIC SETTINGS--->CHECK CALCULATION PROCEDURE.
Here select you procedure and assign the CONDITION TYPE
regards,
santosh

Additional VAT condition type is not flowing to PO

Dear All,
            An additional tax of 1 % is levied in State of gujurat and for this we can take the credit . It behaves exactly like VAT like it calculates its value as 1% of base amount and excise duty levied on it . But this condition is not available in standard TAXINN procedure . So we created a new procedure copying from TAXINN .We created a condition type copying from standard condition type JVRD that is for VAT on which we take credit .Then we assign this condition type to tax procedure immediately below condition type JVRD and it should calculate the value in the same way as that of VAT .Then we assigned this procedure to India , assigned all the condition types in CIN config and maintained default condition types for this procedure copying from TAXINN .
            But while we are creating a PO after that ,this additional tax condition type is not flowing in it .
Can anybody let me know where is the missing link in this customisation .
Regards
Abhijit Das

Hi AP ,
         The condition type is Valid from : Todays Date and valid to 31.12.9999 . Is there any problem with this ?
Abhijit

Deilivery type is not determining in PO for the STO transaction

Hi All,
I maintained the condition record for a material A if 10 quantities are ordered, 2 are free. when I am creating the PO for inter company stock transfer, I entered material A with 10 Quantity & in the second line item it displaying automatically free qty (2 Nos). but for the free goods the system is not determining the delivery type in the shipping tab and also not allowing to save the PO?
Hope I am clear.
Please suggest.
Regards,
C S Javali

hi,
Pls check configured stock transfer process with pricing proceudre also defined shipping data for plant.
check material assinged for that divsion with plant confirm.
sans.

Error Message : Condition type is not maintained in the schema RM0002

HI Gurus,
I have created a new purchasing procedure as follows.
ZVATV : Condition Schema
VATV : Condition Type
VA : Sch.Grp Vndr
When I create the Purchase order, the above mentioned schema, ZVATV is automatically determined.
But when I create Contract, system throws an error message saying condition type VATV is not maintained in the schema RM0002.
I am very new to SAP, Kindly explain in very detail about this error message and ways to get rid of it.
If u have got any very detailed material about pricing kindly forward it to my mail id: [email protected]
Thanks in advance.
~Gokul.

Hi,
The new condition type you are specifing is the gross price condition (PB00). for PB00 condition type a supplementary pricing procedure is assigned as RM0002. u may have copied the PB00 and changed it to VATV, but with out changing the RM0002. copy the RM0002 and in that also change the PB00 to VATV. after this go to VATV condition type control data (M/06) and assign the new supplementary pricing procedure instead of RM0002.
The supplementary pricing procedure is required to have the condition types for which no access seqeunce is mentioned. All the condition types in main pricing procedure with out access sequence needs to be mentioned in supplementary pricing procedure.therefore all these condition types will have the same validity periods as PB00.
Regards,
Ramakrishna

JMIP Condition type is not Replicated from Po to MIGO excise tab

Dear Experts
I Maintained inventorized excise condition types in the Purchase order . Like JMIP, JEC2, JSEI .
while doing the GR , Excise values are not coming in the excise Tab.
Please help me.
Thanks
Reddy
Edited by: Subbas on Aug 4, 2010 2:56 PM

hi
chekc following
path: spro>logistic general >tax on goods movements>india >basic settings>determination of excise duty >maintain excise defaults >
here give appripriate conditions for ur procedure as per BED cess and other
regards
kunal

Condition type JEXP not picking in sales order

hi
i was working with all configuration of TAXINN
i am facing with a problem
when i am running mine sales order i am not able to see condition type JEXP(BED) , JEAP (AED)
can i now where i am gng wrong
whereas i can see all the other condition in sales order
but when i enter it manually JEXP it is taking but in again in billing it is not showing
can u plz help me
Regards
Vini

Dear Vini,
Please Check the configuration settings through IMG path
SPRO>IMG>Logistics general-->Tax on Goods movements >India>Basic settings-->Determination of Excise Duty -->Maintain Excise defaults here you check JEXP condition type is maintaining for A/R BED or not if not maintain then try.
Also check the condition record maintanance for the JEXP condition type through VK12 transaction.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Oct 1, 2008 6:51 AM

Error while posting in accounts: Condition type does not exist in COPA

Hi,
I'm trying to post an invoice into accounts but I'm constantly encountering a Error message as : Assign condition type in COPA.
This error is appearing whenever I'm assigning the pricing procedure and KOFK account entries to a new sales organization.
The error does not appear for my previous Sales org. Also I check with the COPA settings, it does not allow us to enter the condition type mentioned in the error.
Could anyone suggest a solution
Regards
Rasheed

Dear Customer,
To solve error KE391, the corresponding value field assignment
must be done in transaction KE4IM.
Currently, the value field assignment is available for this
condition type in transaction KE4I (SD conditions assignment).
In this case you have to maintain the assignment to a value field in
transaction KE4IM. After including the corresponding assignment in
KE4IM, the error KE391 should not come anymore.
Please, check this.
I hope that the information are helpful.
With best regards
Claudia Neudeck

Condition Type 0K07 not determined

Similar Messages

Maybe you are looking for