Requirements not fulfilled for EK01

[Former Member]

Hi

I'm trying to invoice some travel expenses (costs) in DP90 and i'm getting a message 'Requirements are not fulfilled for condition EK01' can anyone help.......

Thanks

Sara

[jpfriends079 · Accepted solution]

It may be b'coz..

A pricing procedure is defined with condition EK01 for a sales document. The condition has requirement 2 (item with pricing). If a material is entered with assembly order and the item category is set to 'free of charge', the following error occurs:

When you edit the production order from the sales document and then return to the sales document, error message V1215 "Requirements are not fulfilled for condition EK01" is issued. The error message now appears for all further processing of the assembly order.

Check SAP Note 60307 - 3.0E: Item without pricing in assembly order.

Kindly mention error no for the error, it will assist us in understanding & serving the issue better & quickly.

Thanks & Regards

JP

[Former Member]

Removed the requirements field against the condition in the pricing procedure.

[sherifwafa]

Thanks Sara toooooooooooooooooooooooooooooo much

[Former Member]

The error/message number is V1215

[jpfriends079]

Refer & Check SAP Note 30903 - V1215: Requirements not fulfilled

If a condition is entered manually and its requirement is not fulfilled, error message V1215 appears: Requirements are not fulfilled for condition Example: Inserting a condition type manually which is not used during automatic pricing due to the requirement not being fulfilled.

Cause and prerequisites

Change in function PRICING_CHECK (LV61AU08): * Bedingungen prüfen

IF KOMT1-KOBED NE 0 AND INCL_KONDITIONEN NE NO.

BEDINGUNG_PRUEFEN-NR = KOMT1-KOBED.

PERFORM (BEDINGUNG_PRUEFEN) IN PROGRAM SAPLV61A.

IF SY-SUBRC NE 0.

MESSAGE E215 WITH KOMT1-KSCHL RAISING CONDITION. "<-- Reason

ENDIF.

Solution

Workaround solution: Since it mostly concerns conditions to which an access sequence is assigned but which is still to be entered manually, you should create an identical condition (apart from the name) which is only to be maintained manually and does not have this requirement. The source code should not be modified for reasons of consistency.

OR

Refer & Check: SAP Note 102060 - Exclusion when changing conditions manually

Symptom

If an exclusion indicator is set for a condition with a condition record and this indicator is called in a requirement assigned to it, the following procedure can cause the condition to exclude itself so that as a result of the error message no further processing is possible: After you manually change the condition affected on the condition screen, you carry out a new pricing and afterwards you change the condition again manually.

Cause and prerequisites

Field KOMP-KZNEP is not initialized correctly in function module PRICING_CHECK.

Solution

The error is corrected in Release 4.5A, an advance correction is attached.

OR

Refer & Check: SAP Note 668362 - Expected customer price /value with IDoc

Symptom

When you create a sales order via IDoc, the expected customer price or customer value can be assigned in segment E1J3P01. For this, condition types JED1 or JED2 are used. These condition types are set as dimension-dependent conditions by default (T685A-J_3ASZCO) and are thus created on schedule line level.

If you change this setting in Customizing, these condition types are created on item level (see Note 191742). Now, if the price or the value have different values within one item in entry segment E1J3P01, it is not possible to create this condition on item level. The system generates error message V1215 'Requirements are not fulfilled for condition JED1/2'.

Reason and Prerequisites

The system behaves correctly. In this case, condition JED1 or JED2 would have to be created explicitly for the respective schedule lines because different values are assigned in entry segment E1J3P01. However, as Customizing was changed for these condition types, this cannot occur. Error message V1215 displayed in this case is, however, incorrect.

Solution

After the implementation of the advance correction, the system does not display error message /AFS/IDOC021 'Item condition JED1/2 for nnn is not identical in all schedule lines'.

Hope it will solve your requirement.

Thanks & Regards

JP

Edited by: J Prakash on May 20, 2010 9:23 AM

[Former Member]

Hi JP

Thanks for the help. The requirement class is 4 for costs, as i actually want it to pick up the costs from the cost elements i have defined in the DIP profile....

Thanks

Sara