functions which uses condition technique in SD

[Former Member]

Hai Guys,

Do help me out in getting informations about the

following.

pls tell the functions which uses condition technique in SD

detailed answers or links for this pls...

Thanku

Regards

Jino

[Former Member]

Hi Jino,

ntroduction to the Condition Technique Locate the document in its

Use

This section describes the elements within the condition technique. It is organized to reflect the likely sequence of events that you go through when you implement pricing in Customizing. The standard R/3 System includes predefined elements for routine pricing activities. For example, the standard system includes condition types for basic pricing elements, such as material prices, customer and material discounts, and surcharges such as freight and sales taxes. In the case of each element, you can use the standard version, modify the standard version, or create entirely new definitions to suit your own business needs. The sequence of activities is generally as follows:

1. Define condition types for each of the price elements (prices, discounts, and surcharges) that occur in your daily business transactions.

2. Define the condition tables that enable you to store and retrieve condition records for each of the different condition types.

3. Define the access sequences that enable the system to find valid condition records.

4. Group condition types and establish their sequence in pricing procedures.

For more information about implementing and customizing pricing in sales order processing, see Customizing for Sales and Distribution.

For a more technical description of how the condition technique works, see the Business Workflow documentation for Message Control.

Elements Used in the Condition Technique

Condition Types

Condition Tables

Access Sequences

Pricing procedures

Condition Types Locate the document in its SAP Library structure

Use

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

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.

This graphic is explained in the accompanying text

In the example in the preceding figure, two discounts apply to the item in the sales order. The first discount is a percentage discount based on the quantity ordered. The second discount is a fixed discount based on the total weight of the item.

Note

You determine the calculation type for a condition type in Customizing. This determines how the system calculates prices, discounts and surcharges for a condition. When setting up condition records, you can enter a different calculation type than the one in Customizing. At present all available calculation types are permitted. The field ‘Calculation type’ can however not be accessed if this field is left empty. After the data release has been printed, if the field has not been completed manually, the proposal is automatically taken from Customizing. After this it is no longer possible to make manual changes.

If you use different calculation types for what are otherwise the same conditions (for example, percentage, as a fixed amount or quantity-dependent), you do not have to define different condition types in Customizing. You can set a different calculation type when maintaining the individual condition records.

Condition Types in the Standard R/3 System

The standard system includes, among many others, the following predefined condition types:

Condition type

Description

PR00

Price

K004

Material discount

K005

Customer-specific material discount

K007

Customer discount

K020

Price group discount

KF00

Freight surcharge (by item)

UTX1

State tax

UTX2

County tax

UTX3

City tax

Creating and Maintaining Condition Types

You can change and maintain condition types provided in the standard version of the SAP R/3 System or you can create new condition types to suit the needs of your own organization. You create and maintain condition types in Customizing.

To reach the condition type screen from the initial Customizing screen for Sales and Distribution:

1. Basic Functions

® Pricing ® Pricing Control ® Define condition types.

A dialog-box appears, listing the transaction options. Select the corresponding transaction for defining the condition types.

2. In the Conditions: Condition Types view, you can change existing condition types or create new ones.

Leaving content frame

Condition Tables Locate the document in its SAP Library structure

Use

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

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.

The following figure illustrates the connection between the condition table and the subsequent condition records.

This graphic is explained in the accompanying text

Condition Tables in the Standard Version

The standard system includes predefined condition tables and specifies them for each access in each predefined access sequence.

Creating or Maintaining Condition Tables

You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.

From the initial screen of Customizing for Sales and Distribution, you reach the condition table screens by choosing Basic functions ® Pricing ® Pricing Control ® Define condition tables. Then select the mode you want to work with (create, change, display).

Information About Fields

The fields that you choose to make up the key are called the selected fields. The fields from which you can make your selection are called the allowed fields.

Selected Fields

The preceding figure shows the fields that make up the key for condition table 005 (the table for customer/material condition records in Sales). The selected fields show organizational data, such as Sales organization.The fields Customer and Material define the relationship between a particular customer and material.

Field Catalog (Allowed Fields)

When you select fields for the key, you must choose the fields from the list of allowed fields.

Making Changes to Condition Tables

You can make limited changes to existing condition tables. For example, you can change the name of the table or the format of the fast entry screens for the condition records. (Fast entry screens are screens where you can quickly, on a single screen, create and maintain the condition records that refer to the condition table).

Format of a Fast-Entry Screen

The screen consists of header and item lines. Each item line represents a separate condition record. The header lines include the fields that are general to all item lines. When deciding on the format of the fast-entry screen, you can determine whether each field in the key appears as a line in the header or as an item line.

Changing the Format of a Fast-Entry Screen

To change the format of the Fast-Entry screen, choose F6 (Technical View) on the screen where you create or maintain a condition table.

When you determine the format, you have the following possibilities:

If you want the...

Do the following...

Field to appear as a header line

Leave the line field blank

Field to appear as an item

Mark the line field

Text for an item line to appear

Mark the text field

After you make changes to a condition table, choose F16 Generate) to regenerate the table.

Creating a New Condition Table

You can create new condition tables to meet the pricing needs of your organization. When you create a new condition table, you select a combination of fields from the list of allowed fields. The selected fields define the key for the subsequent condition records.

Before you select the fields for the key, there are two things to consider:

• The sequence (or hierarchy) of the fields

• Which fields you want to appear in the header and item areas of the corresponding fast-entry screens

Important Fields

In sales, the fields you should take into consideration are Sales organization and Distribution channel. The sales organization is nearly always used as a criteria in pricing, because different sales organizations often want to use their own prices, discounts, and surcharges. If you use the sales organization as a criterion in pricing, you should also use the distribution channel. If you do not want to establish different prices, discounts, and surcharges for each distribution channel, use the field anyway. In Customizing for Sales, you can use one distribution channel as a reference for all others (thereby sharing the same pricing data).

Deciding the Sequence of Fields

The order of the fields in a condition table affects the performance of the system during pricing. Two general guidelines will help you create an efficient condition table:

1. If you select fields that are connected to the structure of your organization (for example, sales organization and distribution channel), assign the fields according to the level of general applicability: Put the most general field, for example, the sales organization in the highest position and the most specific field in the lowest.

2. After organizational fields, place fields from the document header before those that come from the item level. (For example, Customer comes before Material)

After you have selected the fields for the key on the screen where you maintain and define condition tables, choose F16 Generate to generate the table in the system. Generation prepares the condition table for storing condition data.

Access Sequences Locate the document in its SAP Library structure

Use

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.

Note

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.

ExampleA 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

During sales order processing, a customer may, in theory, qualify for all three prices. The access sequence enables the system to access the data records in a particular sequence until it finds a valid price. In this example, the sales department may want to use the most favourable price for a certain customer. For this reason, it ensures that the system searches for a customer-specific price. The following figure shows how the system searches for the relevant record.

This graphic is explained in the accompanying text

Access Sequences in the Standard R/3 System

The standard R/3 System contains access sequences that are predefined for each of the standard condition types. The names of the access sequences often correspond to the condition types for which they were designed. For example, the access sequence for a material discount (condition type K004) is also called K004.

Creating and Maintaining Access Sequences

You create and maintain access sequences in Customizing. For more information, see the online Implementation Guide for Sales and Distribution.

To reach the access sequence screen, go to the initial screen for Sales and Distribution Customizing and choose:

1. Basic Functions

® Pricing ® Pricing Control ® Define access sequences

Select the transaction that you want to execute (Maintain access).

Leaving content frame

Pricing Procedures Locate the document in its SAP Library structure

Use

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

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.

Pricing Procedures in the R/3 System

The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.

Creating and Maintaining Pricing Procedures

You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.

To reach the pricing procedure screen from SD Customizing:

1. Choose Basic Functions

2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

Thanks&Regards,

Phani,

Points If helpful.

[Former Member]

Condition Technique is used in:

Pricing Procedure

Test Determination

Output Determination

Regards,

Rajesh Banka

[Former Member]

Following things will follow condition technique

Free Goods

Material Determination

Inclusion/Exclusion

Revenue Account Determination

Tax determination

Rebates

Pricing

Output Determination

Text Determination

etc