Difference b/n Condition Table , Condition Record and Condition Type

[Former Member]

What is the difference between: Condition Table , Condition Record and Condition Type....<b></b>

[Former Member]

<b>Condition Table</b> - A combination of fields that defines the key of a condition record.Table that defines the structure of condition record keys.The key consists of a variable part which represents one or more fields and of a fixed part which is identical for all condition records

When you create a condition table, you specify one or more target fields as the table key. You must also tell the system where to find the value for each target field. You do this by specifying source fields. The source fields are usually the same as the target fields, but they can differ.

<b>Condition type</b>

The key that uniquely identifies the condition. A condition is an Agreement defining prices, surcharges/discounts, tax, and other costs according to the influencing factors selected (such as vendor, customer, customer group, vendor sub-range, material, and service). It remains valid for a specified period.

The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system.

<b>Condition Records</b>

It is the values maintained against the condition types with a validity period. Condition types that have a access sequence ( which are cluster of condition tables arranged in a sequence according to some logic) can only have condition records. Condition types without access sequence cannot have condition records.

For each condition type in a pricing procedure, you define an access sequence. The access sequence tells the system where to look for relevant condition records for a particular condition type (a rebate for a specific customer, for example). Each access in the access sequence refers to a condition table. The fields defined in the table (the key) help the system to locate valid condition records.

[Former Member]

Hi Raghavendra nazare,

<b>Condition Types </b>

A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.

Example of a Condition Type

You define the condition type for a special material discount. You specify that the system calculates the discount as an amount (for example, a discount of USD 1 per sales unit). Alternatively, you can specify that the system calculates the discount as a percentage (for example: a 2% discount for orders over 1,000 units). If you want to use both possibilities, you must define two separate condition types. The following figure illustrates how condition types can be used during pricing in a sales document.

<b>Condition Tables </b>

A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.

Example of a Condition Table

A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:

• Sales organization

• Distribution channel

• Customer

• Material

The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record

<b>Access Sequences </b>

An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record. You specify an access sequence for each condition type for which you create condition records.

There are some condition types for which you do not create condition records (header discounts that you can only enter manually, for example). These condition types do not require an access sequence.

A sales department may offer customers different kinds of prices. The department may create, for example, the following condition records in the system:

• A basic price for a material

• A special customer-specific price for the same material

• A price list for major customers

The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:

• Which sub-totals appear during pricing

• To what extent pricing can be processed manually

• Which method the system uses to calculate percentage discounts and surcharges

• Which requirements for a particular condition type must be fulfilled before the system takes the condition into account

Example of a Pricing Procedure

If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use

Reward if useful

Regards

Adarsh Mathur

[Former Member]

Hi,

<b>Condition Tables</b>

A table where the key fields are data combinations for which messages are triggered (and offered for processing).

For each data combination, there is a condition record in the table. The data part contains the actual message.This means, table which has the parameters determines pricing

A data record that stores a condition or condition supplements.

<b>Condition Record</b>

Conditions include:

Prices

Discounts and surcharges

Taxes

Output

Data record whose key fields display the requirement (condition) under which the message is found.The value for the condition table is stored in condition record.

<b>Condition Type</b>

A characteristic of a condition.

For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.

Price elements are represented in the SAP system byg condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.

You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.

You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.

regards,

Arun prasad

[Former Member]

Hi

Condition table is the combination of the fields from more generic to specific

By using the condition table u can create the access sequence which is the search strategy for the condition records

Condtion records is the value of the pricng elements that is designed by the company

condition type is the basic pricing elements whcih we are used for the pricing procedure

for example if te company needs to give the pricing based on the sales organisation and the customer number and the materia number

then the condition table should be defined in that format in the tcode v/03

and the condition types are the basic elements wuch as the base price and the discounts and the frieght and taxes

we can define the condtion types in the tcde v/07 ad the condtition recordsa are maintained in the tcde vk11

[nisha_sharma1]

hello,

<b>Condition table:</b> The definition of the key of the condition record.

<b>Access sequence:</b> A search strategy to locate the proper condition

record.

<b>Condition types:</b> A calculation or formula to calculate a component

of pricing.

Represents the properties of the pricing conditions.

The condition type determines the category of a condition and describes how

the condition is used.

The calculation type and the scale base type can be controlled for each condition

type.

Possible scale base types Possible calculation types

Value :Percentage from an initial value

Fixed amount :Quantity Amount per unit of measure

Weight :Amount per unit of weight

Volumes: Amount per unit of volume

Time period :Quantity per unit of time

<b>Pricing procedure:</b> A sequential list of condition types and subtotals.

<b>Condition records:</b> The data used by condition types to calculate

pricing.

Award pts if helpful.

regards,

Nisha

[Former Member]

Hi Raghavendra

A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.

Example of a Condition Table

A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:

Sales organization

Distribution channel

Customer

Material

The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record.

Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business - the prices, discounts, and surcharges for freight and taxes - that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.

You create condition records for all the pricing elements that the system takes into account during automatic pricing. During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the sales document.

A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.

Example of a Condition Type

You define the condition type for a special material discount. You specify that the system calculates the discount as an amount (for example, a discount of USD 1 per sales unit). Alternatively, you can specify that the system calculates the discount as a percentage (for example: a 2% discount for orders over 1,000 units). If you want to use both possibilities, you must define two separate condition types. The following figure illustrates how condition types can be used during pricing in a sales document.

The link will help u

http://help.sap.com/saphelp_47x200/helpdata/en/dd/5616a5545a11d1a7020000e829fd11/frameset.htm

Reward if useful to u

Message was edited by:

narendran vajravelu