condition table

[Former Member]

please gurues

suggest me how condition table works for MM. what is the main theory working behind it?

Thanks in advance

[pankaj_singh9 · Accepted solution]

Hi,

Condition Table: - A condition table contains price information on a master data type, for example, on a product master. If you define a product price or a special discount, for example, you create condition records in the relevant condition table.

Access Sequence: - An access sequence is a search strategy with which the system looks for valid data for a specific condition type. You can define an access sequence for each condition type. In Enterprise Buyer the access sequences are predefined, changes are not intended to be made by customers.

Condition Type: - A condition type serves to differentiate between prices in the system. You can define a separate condition type for each type of price, surcharge or discount that may arise in your business transactions. The condition type defines, for example, a discount as a fixed amount or as a percentage.

Calculation Schema: - The calculation schema describes a sequence of condition types that are used to determine prices. In Enterprise Buyer the calculation schema 0100 is defined as default. You can modify this if you wish and you can, for example, add your own condition types.

[Former Member]

hi,

the conditons like price ,freight ,discount ,surcharges ...etc, are maintained with some value with a combination of certain parameters like material, pur org ,vendor ,plant... etc .

when we use this conditon in PO , outline aggrement , sales order ... etc , the corresponding value will be picked automatically based on the parameters . ( no need to enter the value manually )

regards

venga

[former_member529134]

Hello

The technical definitions of the terms are given by Pankaj. I will explain how it works.

Access sequence is the path through which the condition type fetches the value from the condition records.

Condition table is nothing but it just acts as the framework to hold the condition values.

When the condition values are maintained in the condition tables, it is called a condition record.

At the time of condition type creation, we give an access sequence for it.So when the access sequence is called at the time of the use of that condition type, the system checks the value for those condition type in the condition records maintained in the condition tables.

Hope it is clear till now.

We define a pricing procedure and assign it to a combination of vendor schema group and purchase organization schema group.

Also we will assign the vendor to vendor schema group and pur. org to pur org schema group.

So when this combination comes in the purchase order, the pricing procedure is hit.

Regards

Gregory Mathews