Mandatory condition type in PIR

Hello expert,
I want to set two conition type(Duty:ZOA1 and Freight:FRA1) in purchsing info record as mandatory input, but it seemed impossible till now.
Could you suggest how to do it?
What I have done:
1.     I created the two new condition type and add it it all the schema and set required flag.
2.     I created new schama and do necessary custimizing for purchase, and it work well in purchase order, but not in info record and scheduling Agreement.
3.     I add the new schema in condition type PB00 as reference schema.
Best Regards,

Hi,
    As of my knowledge, the "required" flag in the pricing procedure will be effective only in purchasing documents where the pricing procedure is determined through schema determination. In case of info record, which is a master data, the pricing is the supplementary schema which is assigned to PB00.
    Anyway, you can make the condition type as mandatory in the pricing procedure, which will effect while creating the PO. You can maintain the condition type manual entries as D (Not possible to process manually) in M/06. Also maintain the access sequence accordingly.
     In this case, system wont allow to save the PO without entering the condition type and the condition type cant be entered manually (as per configuration in above screenshot). The only option would be to maintain the condition record in MEK1 or maintain the condition in info record.
Regards,
AKPT
Message was edited by: AKPT MM

Similar Messages

Urgently need solution for Pricing Error: Mandatory condition type missing

Hello, All
I am working on CRM 5.0 service module and I am facing a problem while creating a service order.
When I enter the product in the service order it gives me an error
"pricing error: mandatory condition type Z### is missing" even though I maintained the customer pricing procedure, the pricing procedure determination, and the condition record. The error shows that the pricing procedure is determined as the error shows the mandatory condition is determined but what I think is that it cant find the condition record.
I already maintained the condition table and the condition record in the product master data but it does not pick the price, kindly help. Deserving points will be rewarded.
Regards
Jacopo François

Hi,
Open u r transaction which u r getting the error, Double click on product u ll get the item level info, Select condition there u click on create icon, there u can define the condition.
OR
While creating a sold to party check whether u r entered a sales area data properly or not.
Hope it helps u
Gentila

FM for creating / maintaining condition types of PIR ( info record)

Hi Exparts,
I required mass creation / updation of condition types of PIR or info records ( in ME11/ ME12 transaction). I tried BDC but it is getting very complex. Is there any FM / BAPI that could be used for this purpose.
Thanks in advance.
Regards,
abhishek

Purchase Info records data are updated in EINA & EINE Tables and even it updates in A017 (Plant Specific) or A018 (Without Plant Specific) which is called as Material Info record.
To identify the Condition Types in info records, below are the steps.
Step 1: Record all the u201Cconditions Records Nou201D from A017 (Plant Specific) or A018 (Without Plant Specific) for the given Info Records.
Step 2: Based on this u201CStep 1 - condition record nou201D, Search the required u201CCondition Typeu201D in KONP Table by inserting the Cond. Record No and Cond. Type.
If it is helpful, reward points.
Regards,
Muralidharan

Manual and mandatory condition type??

Hi
What happens when you do not enter a value for a manual and mandatory condition type?
What are the difference between these two?

Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Hope it helps you.
Regards
AK
Please reward points if helpful

Mandatory Condition Type

Dear Gurus,
I have a condition type PROO at order level, but it will confirm at delivery level. Its a header level condition type apply on all the material at order or delivery level, i want that i cant fullfill the record on order level, and save the order and when this mandatory condition type is missing at delivery same "missing condition type message" is appear at delivery level so user can fill it.
Yes this message "Missing mandatory contion type" is appear at order level but i save it and when goes to delivery system propose that order is missing some value. but i dont want that..
Pls provide if there is any solution.
i can make this condition type at delivery level, but there is only procedure for value contract. etc.
Regards,
Imran

Issue resolve through mandatory conditions.
Regards,
Imran

Mandatory condition type error

Hi All,
We have a mandatory condition type for freight. During order processing, the system should not allow to save the order - an error message should appear. I know this is possible in standard SAP but we are not able to work this out. At the moment the order is getting saved without any error even if the condition type is marked as mandatory.
Thanks,
Raj.

Hi
Pls. check for your freight condition type whether is it checked as Header conditon & if no access sequence is maintained, then while processing sales order even if you dont maintain manually the freight charges & the freight condition type is checked as Required entry in your pricing procedure, the document will be saved without any error message.
Hope this will help you.
Regards
PVV Krishna mohan

Itemization for Material from PIR- Display all condition types

Hi,
I have 4 condition types in Purchase info record (PIR), when I do CK11n-Material Cost estimate for this material, in the Cost Component view ->Cost of Goods manufactured->Itemization for Material - I only see one line with total of the 4 condition types in the PIR.
But I would like to see all the 4 lines (Condition Types from PIR) in the Itemization for material. Can I achieve this with any configuration settings?
I would appreciate any response on this.
Thanks
Sree

I think you can do this if you map the purchasing condition types to origin groups. Try doing the following:
1. Use t-code OKZ1 to create the needed origin groups (one for each pricing condition type).
2. Use t-code OKK4 to map the pricing condition types to the origin group. To do this, select the valuation variant you are using and click on the delivery cost button.
3. Also in the valuation variant, change your sub-strategy sequence setting for material valuation to A (Quote price via condition table).
4. In t-code OKTZ you will probably need to assign these origin groups to one or more of your cost component.
Give this a try and see if it works for you.
Thanks,

Requirement Routines & Mandatory Option for condition type

Hi All,
A tax condition type is being setup as mandatory in the pricing proecdure.
It has a requirement routine associated to it. If the requirement routine is not satisfied, sy-subrc is 4 and hence, no tax is calculated for it but mandaotry setting demnds it to have some value. In such situations, will it over-ride the config. setting of mandatory condition type & if not so, how can I over-ride. It is compulsory to have the mandatory option ticked but its ok to over-ride it for some conditions specifed in the requirement routine.
Please advice.
Thank you,
Shiv

Hi Shiv,
Any critial configuration related information is available in internal tables based on which standard SAP does validations. So mandatory property of the condition type as configured in the pricing procedure, would also be available in some internal table of KOMV (KOBLI is the field indicating whether it is mandatory or not)
So in your requirement routine you can code so as to make KOBLI blank whenever the tax condition type is being deactivated by setting SY-SUBRC to 4.
Please reward if helpful.
Regards,
KC

Sales order cannot be saved if mandatory conditions are missing.

We have a senario here,
Basically, It has been configured that sales order should not be saved without mandatory conditions like Price(ZPRC), Tax(VAT), Min and Max values and MRP(ZMRP). Also, tested on various servers. Everything was and is working fine.
But currently in our production server, sales order is saved without tax condition. Which should never happen. But it took place?
Now, I'm confused how to track the error ? I mean to ask why sales order got saved, even if the check was kept.....
Where can we check that ?
And, also tested the same scenario in the production server without tax condition, but cannot save the sales order(acc. to our requirement).
Also, asked the user (who created this sales order) but the user says , he didn't remember what he did while creating ?
Waiting eagerly for reply.
Thanks & Regards,
Shriannd G Shirwal

Hi,
Do the following.
1. First test this case in your test system. If this is working fine in test system but not in production do the following.
a. Go to table T683S and find out the table entries for each step for your pricing procedure. I am sure there will be difference. If there is any difference, then either find out the missing transport and retransport the same to the production system, else create the configuration as per your test system and then move it across upto the production system. This will solve the problem.
2. If the test system is also not workign properly then there is something wrong with the design of the pricing procedure itself. Check if you have configured all necesary condition types as mandatory condition types.

Pricing Condition Type PR00.

Hi experts,
I have a scenario where condition type PR00 shoul be mandatory in sales order and document should not proceed further unless the basic price is put while creating sales order. Also, system should not allow double entry of PR00.
I have already marked condition type PR00 as manadatory (still document is precceding in absence of any value ) and incompletion procedure log is applied.
Pl guide on same at the earliest.
Regards,
Pallavi

Hi
Check following points :
1. Check for the properties of condition type. It should has BASE PRICE as the property. And Access sequence should have to be there.
2. Mark check for Mandaotory in the Pricing procedure.
3. Check for your calculation. Your Net value should come as zero- if the PR00 is missing.
So when you will process any sales order it will, give you a incompletion log error as net value is zero- or pricing is missing for the item. And also Mandatory condition type PR00 is missing.
Thanks
Rishi

Condition Types and Records

Hello,
I wanted to bring few condition types as a mandatory condition types with default values(Rates) in CRM contract transaction.
These condition types are maintained in Group Condition Maintence. When i create a conditon record for these condition types, in Menu-> Masterdata->Prices & Conditions ->maintain conditions, i 'm getting this error ' incorrect Values in interface parameters'.
Can some one help me to resolve this error. Also system should determine these condition types automatically when entering a product in CRM contract transaction.
Regards
Kamalesh

Hi,
The configurations regarding Order Types are done under VOV8, but once you have created/saved an Order Type during VA01 then you can't change it.
If you want to change Standatd Order to Rush Order then you need to have the Shipping Condition as "As soon as possible" with "Immediate delivery" marker as 'X' which will create the delivery as soon as Order os saved. Since these settings results from configuration in VOV8 and I don't thnk that it can be changed mid-stream.
Regards
SD

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Pricing error - Mandatory conditions ZMWS DIFF are missing.

Hi All,
We have the error in package quotation Mandatory condition types (ZMWS) & (DIFF) is missing. We check randomly with some customers error is not appearing.(Error is occurring only for particularly ONE customer.)
Initially while entering the details in document (customer no., material, sales areau2026) before saving the document the error message is u201CInternal Error during Pricingu201D.
After saving the document error is occurring as mentioned below.
Error messages:
1. Pricing error: Mandatory condition MT Output Tax (ZMWS) is missing
2. Pricing error: Mandatory condition Rounding Off (DIFF) is missing.
Error message is clearing after some work around in the documents.
1. At header level, change the currency from CHF to EUR and then back to CHF.This will get rid of Round condition(DIFF).
2. And to get rid of out put tax, Ship to address (at header partner tab) by change the country from CH to DE, and changing Transportation zone and Post code country specific to DE. Close the address window and open it again. Change back the address to the original CH and close the window. Out put tax (ZMWS) error will go away.
Kindly any one can give your valuable inputs on this issue. Your help will highly appreciate.
Thanks in advance.
Regards
Bala

Hi Michael
   CRM are dtermined using the condition technique(E.g.condition type MWST or UTXJ).Have you assisgned the Business partenr Tax Classification?.If the billing is carried out in the CRM system,tax determination will be accomplsihed by using the TTE.The condition typeOTTE triggers the call of the TTE.Maintenance will take place in CRM.
PLEASE CHECK
Business Partner Classification
*Assignment of tax types and groups
*Tax Calculation per country and Region.
*Tax numbers for NATURAL PERSON
Product Tax Classification.
*Assisgnment of tax types and Groups
*Tax Calculation per country and Region
Organisational Unit-Business place
Customizing of Tax Types and Tax Groups for BP and Products.
I hope this helps!!

Pricing: Provide override for mandatory condition

Dear All.
We have a mandatory condition in our pricing procedure. And we would like it to be Mandatory some 99% of the time.
However, in rare cases with approval we would like it to not be mandatory for a specific sales order. Probably based on manager approval.
Has anyone done anything like this?
Any ideas?
The field comes from T683s-kobli.
Not sure if there's any standard configuration that would let us do this?
But possibly we could use a pricing requirement or other? Or user exit?
A manager could add some value to the sales order that we could key off of, and check which would allow the mandatory check to be skipped?
Thoughts?
Many Thanks.

You need to identify one field in the sales transaction which will not consider the Condition to be Mandatory in that particular business scenario. Let say you create a Price Group (Manager override - 03). In this particular business scenario the Manager will give the price group as 03 i.e. Manager Override @ the Header Level. This price group will ensure not to trigger that particular condition type. Create a requirement routine & assign it in the pricing procedure for that mandatory condition type.
Try this pseudocode in the requirement routine:
sy-subrc = 4.
if komp-kposn ne 0.
    check: komk-konda ne '03'. (*Create a price group 03 as mentioned above)
    endif.
sy-subrc = 0.

Condition Type VPRS to br made as mandatory and Non Zero

Dear Experts,
In the pricing procedure i want to make condition type VPRS (Stansard Price) as mandatory and non Zero. It means system should give an error message if the value for condition tye ZPRS is either blank or Zero. I know how to make this condition ZPRS as mandaory but dont know how to mark as non zero.
Pl guide on the same.
Thanks in advance.
Pallavi

Hello,
Please ensure to have the below setting in place as far the pricing condition type ZPRS is concerned.
Subtotal will be "B" and Requirement should be "4".
"Condition category" of the Pricing Condition Type should be G.
Maintain the Price values at Accounting tab 1 of the Material Master record so that when Sales Order is processed the value will be picked from Material master.
There should not any access sequence assigned to this Pricing Condition Type.
Kindly update this thread based on above suggestion so this issue can be resolved.
Regards,
Sarthak

Mandatory condition type in PIR

Similar Messages

Maybe you are looking for