cancel
Showing results for 
Search instead for 
Did you mean: 

Condition Types

Former Member
0 Kudos

Hello Guys,

In Pricing Procedure there are many Condition Types

Some are Header Condition Types and Some are Item Conditions.

There are some Condition Types which are both at Header and Item

but they still dont have access sequence.

There are 2 condition types EDI1 and EDI2 which are Item Conditions but still they dont have access Sequence.

Please can you exlpain me why is it so?.

Regards,

Farhan.

Accepted Solutions (0)

Answers (4)

Answers (4)

manoj_mahajan2
Active Contributor
0 Kudos

Farhan,

In normal business process, business charges certain price for particular material but customer expects certain price. Customer expected price can be entered manually or through EDI (Electronic Data Interchange). Someone in the business may accept or reject customer expected price. So that system has to block the billing document by considering sales document as a incomplete one so that the document can be released by using transaction code V.25 by accepting or rejecting customer expecting price.

Condition type “EDI 1” is used to compare the net price for each item whereas condition type “EDI2” is used to compare the overall item value (net price * quantity)

REWARD IF U FINDS THIS AS USEFUL....

Regds

MM

former_member227476
Active Contributor
0 Kudos

dear farhan

EDI1 AND EDI2 (Customer expected price):

In normal business process, business charges certain price for particular material but customer expects certain price. Customer expected price can be entered manually or through EDI (Electronic Data Interchange). Someone in the business may accept or reject customer expected price. So that system has to block the billing document by considering sales document as a incomplete one so that the document can be released by using transaction code V.25 by accepting or rejecting customer expecting price.

Condition type “EDI 1” is used to compare the net price for each item whereas condition type “EDI2” is used to compare the overall item value (net price * quantity)

For EDI1, calculation is = 8; for EDI2, calculation is = 8 make it as a manual/statistical.

In “V/08”, include EDI1 and EDI2 as last steps.

Go to VA01, raise the sales order

Go to item condition screen, now include EDI1 as 40/- and EDI2 as 40/-

Raise delivery and invoice. System block invoice

Now go to V.25 and click on release and now raise the invoice

The customer expected price is differ from the automatically determined price or value by more than the maximum difference allowed then the system will look this order as incomplete when it is saved .

The blocked sales order should be released by concern person through work list traction code: “V.25”

 logistics

 S d

 sales

 Information. System

 Work list—V.25 –release customer expected price.

Select the sales order click on release, save and exit.

rewards if it helps

siva

Former Member
0 Kudos

hi,

like other condition there are special condition type which donot uses access seq. This condition will use routine program for determining it. This routines will be stored either in requirements. alt cal type, alt base value. If u see EDI1 & EDI2 has alt calculation type has "8"= whichis a formula

This is an example of a condition value formula . This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.

Formula '8' provides an example of how the system can compare the customer expected value of a line item with the net value computed by the system. If the system net value is not within a value range of 1 of the customer expected value, than the item is blocked. Formula '8' was delivered along with the condition type EDI2 for customer expected value. Users can copy this formula and specify their own value range tolerance in the field MAXIMUM.

This has got program=RE FV64A008

regards,

Arunprasad

Former Member
0 Kudos

EDI1 and EDI2 are not used for automatic pricing determination, in other words, they don't need condition record. They are customer expected price retrieved from idoc or manual entry to compare with net prices of order line item. They are assigned formulas routines 8 or 9. ( VOFM ->formulas->condition value)

When difference is not in the deviation range between EDI1( EDI2 is to compare net price * qty) and net price, system marks this order as incomplete.