Validity for Condition type

Hi Friends,
We are using a delivery cost manual condition in MM Pricing. Presently there are many Open POs in which some of GRs were done and in some GR also not done. I want to change the condition validity so that in future no one can select that condition.
Since it is a manual condition there is no acess sequence or condition record. When I try to change validity period in condition type only (M/06), there is no impact. I can't change account assignment also since pending LIV / GRs will be impacted.
Is there any solution for this?
Regards
Sai Krishna

The dates you can see in M/06 only refer to the default validity dates proposed when maintaining the condition records. What you could do is to change the Manual entries field to "Not possible to process manually". Since there's no manual processing nor available access sequences, by that you'll eliminate the usage of this condition type.
Another way would be to remove the check marks (Man./Mdt.) from that condition in your calculation schema.

Similar Messages

Table containing validity periods for condition types in me12 transaction

Hi .,
      i need the name of the table which contains the Validity Start and Validity End dates for Condition type 'PB00' IN ME12 transaction .. kindly help me..
Regards.,
S.Sivakumar

hi,
we hav data in A018.
130     M     PB00     10011     30000102     XXXX     0     31.12.9999     03.09.2004     0000007715
130     M     PB00     10061     20000822     XXXX     0     31.12.9999     08.10.2006     0000011194
130     M     PB00     10061     30000436     XXXX     0     31.12.9999     21.01.2005     0000009793
130     M     PB00     10061     30000437     XXXX     0     31.12.9999     21.01.2005     0000009792
130     M     PB00     10065     80000414     XXXX     0     31.12.9999     30.07.2004     0000007487
130     M     PB00     10269     10004972     XXXX     0     31.12.9999     20.01.2007     0000011237
130     M     PB00     10482     30000129     XXXX     0     31.12.9999     16.07.2004     0000006911
130     M     PB00     18091     30001906     XXXX     0     31.12.9999     06.05.2006     0000011061
130     M     PB00     18091     30001912     XXXX     0     31.12.9999     06.05.2006     0000011059
130     M     PB00     18091     30001913     XXXX     0     31.12.9999     06.05.2006     0000011060

Unable to manually change the amount for condition type PB00

Hi Gurus,
My client is using ECC5.0.
Here when I try to change the amount for condition type PB00 using transaction ME22N, I am not able to change the value. I donu2019t get any error, but as soon as I change the value and press Enter the system replaces my entered value with the original value.
Confusing part is that I am able to change the amount of condition price PB00 manually using transaction ME22. I donu2019t have any such problems there.
Also I am able to manually change the amount of condition type PBXX using ME22N.
Only in the case of PB00, if I use ME22N to manually update the amount I am not able to change it.
Kindly help me, to find a reason as to why this could be happening, and correcting if possible?
Thanks in advance,
Imran

Hello Imram,
The purpose of maintaining 2 condition types ie PB00 and PBXX in a pricing procedure is that PB00 is automatic gross price determination and PBXX is manually giving gross price.
If you go to T.Code : M/06 and check the condition types, you can see that PB00 will be having an access sequence but not PBXX.
So if you have to manually give the gross price, you have to use PBXX.
Regards

Requirements not fullfilled for Condition type - Pricing Procedure

When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

Hi Sunil,
Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is, once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of ABAP'er regarding this requirement if it is customized requirement.
We should know the purpose of requirement in condition type.
Venkat.

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Authority check in for condition type

Hi
What do you mean by an authority check on condition type.. especially Pricing..
There are authority check that are embedded as Reqt and AltCTy in the IMG at the pricing procedure level for different condition type.
Could someone explain me what they are for..?
Thanks
Jac

Hi,
authority check is the std sap methodology of check the permitted authorisation values for every transaction and every user.
here in this example;authority object is used to maintain or change condition record for allowed condition types.
scenario eg;if we maintain create value for user mukund for pr00 condition type ,system allows me only for creating .if we maintain change value for user sherin for condition type,system allows to change the values.
net net i can create and u can change ,not visa-viz or any body else cannot do it.
hope this is clear.if it helps REWARD!!!!!!!

Restriction for condition type

Hi,
I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
regards,
sps.

The objects concerned have to be:
V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
V_KONH_VKO Condition: Authorization for Sales Organizations
V_KONH_VKS Condition: Authorization for Condition Types
But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
Object : V_KONH_VKS Condition: Authorization for Condition Types
Condition Type: PR00
Actvt : 03
Thanks & Regards
JP

Why not all billing documents are posted to CO-PA for condition types?

Hello!
I have following problem.
In transaction KE4I I have configured several condition types to post for specific value fields.
For some billing types it works but for some doesn't work.
For all domestic invoices it works but for abroad invoices it doesn't work.
Billing documents for abroad invoices are also posted to CO-PA but for another value fields, not for that I expect.
Where is problem?
I am waiting for help.
Best regards
Bogdan

Hi.
In both pricing procedures there are same condition types. The only difference was check box "Condition is used for statistics".
After marking this check box it still doesn't work.
There are placed the same condition types in all billing documents (domestic and abroad) . So I am supprised that for domestic billing documents field value in CO-PA is calculated for condition types placed in KE4I.
But for abroad billing documents the same field value is not calculated for the same condition types placed in KE4I.
Where is a problem?
I need help.
Best regards
Bogdan

Validation for Document Type

Hi,
I want make a validation for document type wise posting for particular users like user ABC only post JV doc.type document. Please suggest me how I will make it.
Thanks & Regards,
Hemant Kumar Maurya

Hello Hemant,
You can manage this with authorization or validation (T Code OB28 or GGB0), for validation:
1 - Create a validation at document header level.
2 - You can create a set (table BKPF and filed - user name) with T code u2013 GS01 wherein you can give list of users for which you want to restrict posting only with document type u201CJVu201D. Attached this set or a single user in u201CPrerequisiteu201D section of validation.
3 - In u201CChecku201D section of validation validate the document type u201CJVu201D syntax u201CBKPF-BLART <> JVu2019
4 - Create and attach error message for above validation.
5 - Attach this validation to your company code in OB28
Since i donu2019t have SAP log on credential therefore cannot give you exact validation code syntax.
Please try, hopefully this would help.
Regards,
Parag

Validation for doc type for f-43

Hi,
I Have created a validation for document type sk for t.code f-43, while creating validation i have taken fb01 it is working fine for f-43 at the same time which is working for f-02 also it should not work for f-02.what to do please help me
Thanks and Regards
Radha

Hi,
Almost all FI transactions other than the clearing transactions, may apparently have different names like F-02, F-43 etc, but at the backend there is only one mother transaction code FB01. So any validation on FB01 will impact all FI t-codes.
I would suggest that you use document type in the validation, if you can have clear demarcation between the doc type used for different transactions.
Cheers.

Provision account key missing for condition type FRA1 in schema ZIMPOR

Hi,
While maintaining the condition value in PO, the below message displayed.
"Provision account key missing for condition type FRA1 in schema ZIMPOR"
Thanks and regards
Murugesan

Go to
Spro>MM>Pur>Conditions>Define Price Determination Process>Define Calculation Schema
here select ZIMP and click control data
in that maintain "Account key" for FRA1 cond type in the Account key Column..
(Second column from right side)

Account determination for condition type

Hi Guru,
I have requirement where I need to assign G/l account in VKOA for condition type used for discount and markup same time. I know I can aasign trade discount to this condition type but how about markup. can we assign two diffeent account to same condition type based on uses.
Thanks

This is pricing conditions not condition type like KOFI. The pricing condition are like base price, discount , markup, special custmer discount, ect. You can see these contions in sales order under condtion tab. My issue is there one condtion that user use some time for discount and some for mark up and requirement is when this condition is used for discount, it post to one account and if used for mark ,should go to different accoount. In VKOA sequence 501, we can only assign one account to one condition. if some one know how to assign two G/Ls to one condition .

Provision account key missing for condition type ZPFV in schema ZUELOC

Hi
We have defined the condition type ZPFV for freight value & mentioning the same while creating po and in past we had prepared so many po by using this.
we hv not change any thing & today we are getting message " Provision account key missing for condition type ZPFV in schema ZUELOC"
What to do???????
Thanks
Ketan Vala

hi..
If the accrual is ticked in condition type in M/06, it should have an account key assigned to the condition type in the pricing procedure in M/08.
Go to your contion type ZPFV and check whether you have checked Accrual or not..
then go to ur pricing procedure ZUELOC and check the last two colums for your condito type i.e. Account Key and Accrual Key.
Maintain these..
try this if it works.
Thanks...

Change accural key for condition type

Hi,
The accural key for condition type " special addition custom duty" is maintained wrongly in our Prd system .As a result wrong GL is getting posted.
We want to change the accural key for this condition type.
Not sure of the implications....
There will be a problem with the existing Purchase Orders for which GR posted and Invoice pending.
If the new PO is created, the condition type may be fetched through the Info records. Info records will fetch the last purchase order and if the last PO is created before the changes done then the old accural key may appear in the new PO.
How to handle this...?
What is the standard process to handle the mistakes in the condition types?
Regards,
Rajesh Satope

Hi Rajesh Satope,
For "clean" open PO's (no GR or invoice) you can obtain the new codition type settings by applying "Update prices" at the bottom of the conditions screen. I am not sure though how can you do it for many PO's at once.
For PO's with partial transactions posted, I believe you will have to complete them with the old setting, i.e. the balance on the accrual account booked via the GR shall be cleared on the same account by the invoice - so you shouldn't run "Update prices" for such PO. I think even SAP standard prohibits this.
BR
Raf

Provision account key missing for condition type FRB1 in schema

Provision account key missing for condition type FRB1 in schema is the error coming while i enter freight value at PO
how to set this
krishna

Hi Krishna,
Go to Pricing procedure using M/08 , here against the Freight condition type ( FB1), enter the accrual key ( ex. FRE)and account key ( ex. FR1 or FR2).
After saving to the customizing request, again create the PO.
Thanks & Regards,
Amjad

Validity for Condition type

Similar Messages

Maybe you are looking for