SD Creating Condition Records

This procedure explains how to create a condition record using, as an example, a condition record for a material price. You use the same procedure for condition records for other pricing elements.

Steps:

1. Choose Logistics
® Sales/distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Prices ® Material prices ® Create.

You reach the Create Price Condition (PR00): Fast Entry

3. Enter data in the Sales organization, Distribution channel, and Material fields.

Enter the pricing data for the material.

The following figure gives an example of the role of a condition record for a material price.

4. If you want to enter a pricing scale, choose Goto
® Scales. If you want to change the default validity period, select Validity periods.
5. To save the condition record, choose Save.

In the second step, you have the option to Create with reference. This lets you select an existing condition record and overwrite the material number with a different material number. This copies the data for the new condition record You would only use this procedure if you wanted to create identical or similar prices or pricing scales for several materials.

Creating tax condition records differs from creating other condition records in that you have to enter additional data. For further information, see Creating Tax Records.

Creating SAP SD Condition Records

This procedure explains how to create a condition record using, as an example, a condition record for a material price. You use the same procedure for condition records for other pricing elements.

Steps:

1. Choose Logistics
® Sales/distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Prices ® Material prices ® Create.

You reach the Create Price Condition (PR00): Fast Entry

3. Enter data in the Sales organization, Distribution channel, and Material fields.

Enter the pricing data for the material.

The following figure gives an example of the role of a condition record for a material price.

4. If you want to enter a pricing scale, choose Goto
® Scales. If you want to change the default validity period, select Validity periods.
5. To save the condition record, choose Save.

In the second step, you have the option to Create with reference. This lets you select an existing condition record and overwrite the material number with a different material number. This copies the data for the new condition record You would only use this procedure if you wanted to create identical or similar prices or pricing scales for several materials.

Creating tax condition records differs from creating other condition records in that you have to enter additional data. For further information, see Creating Tax Records.

SAP Steps For Creating Tax Records

Steps:

To create a tax condition record:

1. Choose Logistics
® Sales/distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Taxes ® Create.

You reach the data Select Countries for Maintaining Tax Conditions screen.

3. Position the cursor on the country for which you want to maintain a tax record and choose Tax records.
4. Enter the relevant data.
5. To save the tax record, choose
Save.

SAP SD How to Maintain Presentation in Table Form

Use

Data for rapid creation of condition records is arranged in table form.

You have the following options for influencing the presentation:

• Change to the column sequence

This is particularly helpful when a table contains a lot of fields and you want to have the most important ones at the beginning.

Position the cursor on the field and move it with the mouse to the required position.

• Change to the column width (until it can no longer be seen).

Position the cursor on the edge of the field and move the mouse until you have the required width.

Every user can define his own view on the data depending on his own individual way of working, whilst saving the settings as presentation variants.

Click on the upper right hand field of the table presentation, to create presentation variants.

An administrator can identify individual fields throughout the system as in the background.

For setting authorizations for table presentations, the authorization object S_ADM_FCD is available in the authorization class BC_A (Basic Administration).

What are Long Texts in SAP SD Conditions

Use

You can maintain long texts in the condition records for Pricing and for Agreements (Bonus, Sales deal and Promotion).

These give information, e.g. on the following:

• Information on the condition record system
• Information on licenses
• Information on invalidity

If you wish, long texts in the rebate agreement can also be transferred into documents (e.g. into the credit memo request for a rebate payment and from there into the rebate credit memo.

For texts in Price Conditions, transferring to documents is not supported.

Texts are not copied over when creating condition records with references.

The following text types are set up in the standard system:

• 0001: Opening comments
• 0002: Licenses
• 0003: Closing comments
• 1000: Bonus payment

There are some buttons in the condition record for text maintenance.

In addition you can use an editor for a text type in the detail screen of the condition record, which allows you to create body text.

Customizing

In Customizing for Text Determination you can set up your own text types.HyperLink: SIMG.SIMG_XXMENUOLSDVOTX2 "Create text types" v>

For an agreement type decide which text type should appear in the agreement for maintenance with "Text Edit Control". SIMG.SIMG_CFMENUOLSDVOK0 "Maintain condition types" v>

When text is transferred from the bonus agreement to the bonus documents, the document pricing procedure ‘B3’ is set up in the standard system with the text type 1000.

HyperLink: CHAP.SIMG_CFMENUOLSDVOTX "Maintain text determination" v>

Working with the Copying Function for SAP SD Condition Records

Use

The copying function allows you to create multiple condition records at one time. You can either copy one or more existing condition records into new records or you can create a new record and use it as the basis for copying additional records, all in one step. You can copy condition records even when the source and target records have different condition types, condition tables, or key field values. However, copying between different condition types or condition tables is subject to certain prerequisites and rules.

Prerequisites for Copying

The following general prerequisites apply to copying condition records:

• If the condition tables differ between the source and target condition records, then:

• Only one field may differ between the two condition tables
• The condition tables must contain the same number of fields

• If the condition types differ between the source and target condition records, then each condition type must have the same calculation rule, scale type, condition class, and plus/minus indicator.

Understanding Copying Rules

Copying rules determine which condition types and condition tables you can use for copying between source and target condition records. The rules are defined in Customizing for Sales and must meet the prerequisites listed above. The standard R/3 System standard copying rules. If required, your system administrator can modify the standard copying rules or add new ones to meet your requirements. During processing, you can select from alternative copying rules, depending on what you are trying to copy.

Examples of Different Copying Scenarios

The following three scenarios describe how you can copy condition records.

Scenario 1: Same Condition Types/Same Condition Tables

You offer a special discount to a particular price group (a group of customers defined in the customer master record). You want to make this discount available to other price groups by copying pricing details from the existing record. In this type of copying, the condition types (K020) and the condition tables (table 20) are identical for both source and target condition records. The only thing that varies in this case is the value of one of the key fields (the Price group field).

Scenario 2: Same Condition Types/Different Condition Tables

The access sequences for a particular condition type can be defined in Customizing for Sales so that it accesses more than one condition table. This means condition records with the same condition type can have different keys. You can also copy condition records where the condition type is the same but the condition tables are different. Say you offer a material-specific discount to a particular price group (condition type K032, condition table 32). You can copy this material discount and create a new condition record for a specific customer (condition type K032, condition table 5).

Scenario 3: Different Condition Types/Different Condition Tables

You can also copy condition records even when both condition types and condition tables are different. Say you offer a special discount to a particular price group (condition type K020, condition table 20) as you did in the first scenario. Here, however, you want to copy this condition record not to another price group but to a new customer-specific discount (condition type K007, condition table 7). In this case, both condition types and condition tables are different.

Copying Process

You can call up the copy function from the Edit menu in any of the following condition record screens:

• Create
• Creating With Reference
• Change
• Overview

There are several typical scenarios for using the copying function. You may want to copy an existing condition record into a number of new condition records. In this case, you use the change condition record function. Alternatively, you may want to create a new condition record and copy it to other records all in one step. In this case, you use the create condition record function. In both cases, you can change the copied data before you save the new condition records.

SAP Copying SD Condition Records

Using the Copy Function

In this example, you have an existing condition record that specifies a material discount for a particular customer. You want to offer the same discount to other customers by copying the data from the existing condition record into new records for each additional customer.

Steps:

To copy the existing condition record into the new records:

1. Choose Logistics
® Sales and Distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Discount/surcharges ® Customer/material ® Change.
3. Enter the selection data to select the existing condition record.

The system displays the existing condition record(s) in the fast change screen.

4. Select the condition record that you want to copy and choose Copy. If you want to select from alternative copying rules, see
Selecting From Alternative Copying Rules.

You reach the selection screen. In this example you choose from a list of customers, for whom you would like to copy reference condition record data.

5. Enter your selection data and choose
Execute.

The system displays a list of the customers who meet your selection criteria.

6. Mark the customers for whom you want to create copies of the reference condition record and choose
Continue.

The system displays the overview screen for condition records and lists the new condition records you have just created, as well as the existing condition record you used as a reference.

7. In the overview screen, you can change the data for individual condition records by branching to the various views (Validity periods, Condition rate, Terms of payment, and so on).
8. Save the condition records.

Displaying the Copy Log

After you have copied something, the system advises you if there are error messages in the copy log. You can see the log by going to Extras ® Copy log condition The error messages in the copy log refer to the most recent copy transaction you carried out. With every new copy transaction, the log is automatically updated with only the current data.

Selecting From Alternative Copying Rules

More than one copy rule may exist during a particular copy procedure. For example, if you are copying an existing condition record for a material price, the standard version includes two possibilities: the target condition record may be either a material or a material pricing group.

Steps:

Choose between alternative copying rules:

1. Choose Logistics
® Sales/distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Discount/surcharges ® Customer/material ® Change.
3. Enter the selection data to select the existing condition record.

The system displays the existing condition record(s) in the fast change screen.

4. Mark the condition record that you want to copy and choose Edit
® Copy ® Select rules.

The Copy Condition Rules dialog box appears.




If you are copying condition records in a sales promotion or from the overview screen and you have selected records with different condition tables, the Copy Condition Rules dialog box includes a separate entry for each different condition table. Otherwise, the dialog box contains a single line.

5. To display the copy rules, place the cursor in the Number field and choose Possible entries.

The system lists the alternative copy rules that have been defined.

6. Select the copy rule that you want to apply.
7. Choose Continue to copy the item using the alternative copy rule you selected.

How to Change SAP SD Condition Records

When there are price changes, you have the option of changing individual condition records manually. Using the function Price change, several condition records can be changed automatically. Both procedures are described below.

In the standard system most condition types are configured so that during sales document processing you can overwrite many of the automatically determined condition amounts (in the sales order, for example). However, these changes are only one-time changes and do not affect the corresponding condition records. To make lasting changes in automatic pricing, you must the change the condition records.

Making Changes in Individual Records

Steps:

To change to a condition record:

1. Choose Logistics
® Sales and Distribution ® Master data.

You reach the Sales Master Data screen.

2. Choose Pricing
® Prices, the kind of pricing element (price, discount, and so on) you want to work with, and Change. Then choose Change.

You reach the screen where you can select the condition record you want to change. You can also select a number of individual condition records which you can then change one after the other.

3. Enter your selection criteria and choose
Execute.

The system displays a list of the condition records that meet your selection criteria.

4. If a condition record does not include a pricing scale, you can make your changes on this screen. If the condition record does contain a pricing scale, mark the condition record you want to change and choose
Scales.
5. Enter the changes you want to make.
6. Choose
Save to save the changes and repeat the process if you want to change further condition records.

Making Automatic Changes

If you want to apply the same price change (for example, a 5% increase) to a number of different condition records, you can make the change globally.

Steps:

To make a global change to more than one condition record:

1. Choose Logistics
® Sales/distribution ® Master data from main menu.

You reach the Sales & Distribution Master Data screen.

2. Choose Conditions, and then the price, discount, or surcharge you want to change. Then choose Change.

You reach the screen where you can select the condition records to change.

3. Enter your selection criteria and choose Edit
® Start selection.

The system lists the condition records that meet your selection criteria.

4. Select the condition records you want to change and choose Change amount.

The system prompts you to enter the change. The price change can be a percentage or a fixed amount. If the change is a fixed amount, you can specify the currency. If the change is a price reduction, you enter a minus sign after the amount. If necessary, you can also specify a rounding rule.

5. Choose
ENTER to carry out the changes.

The system carries out the changes (including changes to pricing scales) and displays a log of the changes you made.

6. To save the amended log, choose Back to leave the log and then Condition
® Save.

Change Documents for SAP SD Condition Records

As of Release 3.0C, change documents for condition records are available. Using the new display report, users can display and monitor all changes made to condition records, including those used in pricing, rebate agreements, and sales deals.

Displaying Change Documents

You can display change documents during condition record maintenance. Just select the condition record or records whose change documents you wish to display.

Steps:

There are two possible methods of displaying change documents:

• Choose Environment
® Changes ® For condition record.

Change data for the selected condition record(s) will be displayed.

• Choose Environment
® Changes ® Report.

A selection screen will appear where you can choose multiple criteria for displaying change documents. The result of the selection report is displayed in three hierarchy levels.

Hierarchy Levels in the Selection Report

You can display three levels of data in this hierarchical style report:

• Level 1 data:

Date and time the change was made

Condition type, condition table, and variable key for the condition record changed

Transaction code and user who made the change

Validity period of the condition record at the time the change was made

• Level 2 data:

Description of the change that was made

Old (before) and new (after) values

Name of the field that was changed

• Level 3 data:

Automatic changes made to condition records by the system due to a change in validity period are displayed on the third level. Condition records here have been split from records on the second level and are therefore related.

When a condition record is split into two records due to a change in validity period, it is displayed on the third hierarchy level with the relevant changes.

You display changes in old and new values just as you would for the second level.

Change Documents - Special Features

1. Changes to validity periods

When a condition record is created or the validity period of an existing condition record is changed, the system may automatically adjust the validity period of other condition records that have the same variable key. The reason for this is that at any one point in time, only one condition record with a particular condition type and variable key may be valid. All changes that the system makes automatically to existing condition records are displayed in level three of the change document display report.

If the validity period of a new condition lies within the validity period of an existing condition record, the system automatically splits the condition record into three different validity periods.

2. Changes to scales

When condition scales are changed, all condition scale entries (not just those that have been changed) are recorded as change documents. In this way, you have a complete overview of condition scales before and after any changes.

3. Changes to condition supplements

The system displays all changes made to condition supplements (including their scales) along with any changes made to the condition record. These changes are identified by the word Supplement followed by the condition supplement type changed, and finally, by the description of the change made. For example, if you create the condition supplement KA00, the description would be: "Supplementary condition (KA00): Condition record was created".

SAP How to Display a SD Condition Record

You can display condition records in master data maintenance or directly from the pricing screens in a sales or billing document.

• In master data maintenance, you display a condition record by choosing Pricing
® Prices ® Material price ® Display. You can then select the condition records you want to display.
• In the pricing screen of a sales or billing document, you display a condition record by selecting the pricing screen, marking the specific condition record, and then choosing Condition record.

Displaying Detailed Information

The overview screen of a condition record displays detailed information, such as: The following overview tells you what detailed information you can display for a condition record or individuatl items.

• Header data (for example, person who created the condition record and when)
• Item details (for example, different amounts such as the condition amount, the upper and lower limit)
• Status information (whether, for example, the condition is active or is marked for deletion).
• Conversion factors (which units of measure the material is available in).
• Condition information (to list all condition records for a particular condition type).
• Display key (shows organizational data)

SD How to Delete a Condition Record

You can delete condition records that are no longer valid. The condition record becomes inactive after it is deleted, the system does not take it into account during automatic pricing. Nevertheless, it remains in the system until the next reorganization run. This means you can reset a deletion and reactivate a condition record.

If a condition record was deleted, the system displays this fact in two places in the condition record:

• The system automatically marks the deletion indicator on the overview screen of the condition record.
• The status information says that condition record was deleted.

Steps:

This procedure describes how to delete a material price. The procedure is the same for any condition record. To delete a condition record:

1. In the overview screen of the condition record, select the material whose condition record you want to delete.
2. Choose Edit
® Delete.
3. The system automatically marks the deletion indicator for the selected material.You can see the indicator in the last column (L).
4. Choose Save to save the deleted condition record.

Resetting a Deletion

You can reactivate a deleted condition record until the next reorganization run. To reset a deletion, choose Edit ® Reset deletion. The deletion indicator diSAPpears.

SAP SD Condition Index

Use

You can create and use condition indices. You can use these indexes to search for condition records that were created for a variety of condition types and condition tables. For example, you can use a condition index if you want to see all condition records that apply to a particular product regardless of whether the records are prices or discounts. In this case, you can use one of the standard condition indexes. Or if you want to see a list of condition records that contain a particular sales deal and a material from a user-specified list of products you can create your own condition index.

Defining an Index

Creating a condition index is similar to creating a condition table. In Customizing for Sales, you select the combination of fields that you want in the index key. The system automatically proposes a list of allowed fields from which you can choose. The fields you specify for the key can have a maximum combined length of 100 characters. For more information about setting up condition indexes in Customizing for Sales, see the online Implementation Guide.

Reorganizing an Index

Reorganization means updating an index with current data. There are different occasions when this makes sense.

• For example: After you create a new index and generate it, you want to fill the index with the current data in your system. (This also applies if you choose to activate one of the standard condition indexes).
• After you specify that condition indexes should be updated for a particular condition type, you want to fill the indexes with the corresponding condition records that already exist.

Please note that since the system has to read all the relevant condition records, reorganization is automatically submitted as a background task.

Activating an Index

The activation function displays a list of all available condition indexes and indicates which are active. The system can use a condition index only when it is activated. Before you can use the indexes that are delivered in the standard version, you must first activate them in Customizing for Sales. However, if you create your own indexes, the system automatically activates each new index when you generate it. In addition, you must specify an update setting for each condition index. You can choose from the following standard settings:

• Requirement 1: The index is updated when the user provides data for all fields in the index key
• Requirement 2: The index is updated when the user provides data for at least the first field in the index key

Controlling Index Update by Condition Type

You can specify for each condition type whether or not the system updates the condition indexes when you post condition records. In cases where updating condition indexes may not be necessary - for example, with freight- and tax-related condition records - you can leave the condition index indicator blank.

Selecting Condition Records Using an Index

After you have defined a condition index and the system has updated it with current data, you can use it to search condition records.

Procedure

To select condition records using an index:

1. Choose Logistics
® Sales/distribution ® Master data from the main menu.

You reach the Sales Master Data screen.

2. Choose Pricing
® Select using index and specify whether you want to change or display condition records.

A dialog box displays the condition indexes that are currently available.

3. Select the condition index you want to use and choose
ENTER.

You reach the screen where you enter selection criteria.

4. Enter your selection criteria and choose Execute.

The system displays a list of the condition records by condition type for the selection criteria you entered.

SD Creating Condition Records Within a SD Sales Deal

You can create condition records for a sales deal in the following ways:

• At the same time as you enter the master data for the sales deal in the system. (In this case, the system automatically creates the link between the condition records and the specific sales deal.)
• By creating a new sales deal with reference to an existing sales deal and copying some or all of the condition records over
• By adding new condition records into an existing sales deal.(In this case, you enter the number of the sales deal manually.)
• By copying existing condition records into a sales deal you have already created.

For further information about copying condition records, see Copying Condition Records.

Steps:

To create condition records directly from within a sales deal:

1. Choose Pricing in the overview screen of the sales deal.

The system displays a list of valid condition types for this type of sales deal.

2. Select the condition type for which you want to create a condition record and enter your data.
3. If you want to create additional condition records for the sales deal, choose Back to return.

The system returns you to the dialog box that lists the valid condition types you can use.

4. After you have created the condition records you want, choose Back and save your data.

SD Pricing And Conditions Release Status

Use

The release status for condition records in a sales deal enable you to limit the use of records that have already been created.

Release status has the following characteristics:

• no entry: released
• A: Blocked
• B: Released for price simulation
• C: released for price simulation and planning

The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.

Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.

When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.

A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.

The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.

The release status for condition records in a sales deal is displayed in the status information and on the detail screens for condition maintenance.

If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.

Awarding release status is only possible for sales deals and not for bonus agreements or individual record levels. Maintenance of the status for individual condition records is not implementable for the current status of the condition master records. This is connected with the overlapping of validity periods in combination with the release status, which does not occur in sales deals, as you can not create a condition record with the same key in another sales deal.

SD Pricing And Conditions Budget Assignment

Use

During market segment planning and sales and profit planning, you can create budgets for sales support measures (e.g. sales promotions) and related special offer discounts. This budget is then used in the sales and distribution system (SD) when conditions (special offer discounts) are maintained for the customer agreement. You can monitor the budgetting process from assignments within the customer agreement to the billing document in CO-PA. This is because the budget assignments are transferred to CO-PA when you maintain the conditions.

You can keep checking the budget assignments by carrying out variance analyses of the planned and available budget. This allows you to monitor sales promotions in detail right from the early stages of profitability analysis.

Process Flow

The process flow for SD-promotion budgets withing sales and profitability planning could appear as follows:

1. In sales and profitability planning you can create budgets for individual sales support measures.
2. Budget assignmets are created in SD for the conditions to be granted for the customer agreements.
3. In reporting, you can control the availability of funds for sales promotion by market segment.
4. The data flow at the points of "condition maintenance", "create sales order" and "billing document" makes it possible to carry out reporting in the profitability analysis with maximum precision all along the business process chain.
5. Based on the planned structure, you can use a hierarchical representation to specify the market segments for which budgets can be created. This ensures consistency during planning, because budgets can then only be created in the allowed market segments.

SD What is Budget Assignment

Working with sale promotion and SD budgets can be split up into three stages:

1. Budget planning in CO-PA
2. Budget assignments in SD (condition record maintenance)
3. Passive availability check in CO-PA

Prerequisites

You must activate transferal of assignments to CO-PA per condition type. You carry this out in Customizing for CO-PA, under Flow of actual values ® Transfer of sales agreements.

Activities

1. Budget planning in CO-PA

A budget is planned within manual planning. You can use several planning functions to help you carry out manual planning. It is a good idea if you define your own plan version for a budget.

2. Budget assignments in SD (condition record maintenance)

Budget assignments can be made during condition record maintenance, as well as within sales promotions, sales deals and rebate agreements.

To maintain a budget assignment, select Logistics ® Sales and distribution ® Master data. Under Agreements, select either Rebate agreements, Promotion or Sales deal. Go to the condition screen for the required condition and display the detail screen for the required characteristic.

This is where you enter the Condition amount and the Planned basis. The system uses this to calculate the value that is filled in the relevant field in CO-PA.

Rule	Condition type	Planned basis
A	percentage	planned sales volume
B	fixed amount
C	quantity-dependent	planned quantity
etc.




You want to maintain a budget assignment, in which you grant a price reduction of 20% of the planned sales revenue of 100,000 USD for material A1.

In SD sales deal maintenance, you select the condition screen for the ‘price reduction’ screen. You then select the detail screen for material A1. Calculation rule ‘A’ - percentage is maintained. You enter 20 in the condition amount field and 100,000 in the planned basis field. Save your entries.

The system automatically calculates a planned value of 20,000 USD. This value is transferred (according to value field assignment) to the corresponding value field in CO-PA ‘Sales deductions’.




You can also maintain the planned values for all conditions in an agreement. You do this in the overview. In the agreement, select: Goto ® Overview ® Planned values.

3. Passive availability check in CO-PA

Using reporting in CO-PA, you can carry out a passive availability check. During this check, the planned version in which the budget was planned (in manual planning) is compared with the assignments from SD (via transaction type G).

SD Using Variable Views of SD Condition Record Data

Use

The functions for maintaining condition records have been extended to include variable views. This means, for example, that condition record maintenance is no longer limited to just one condition type and condition table. The screen that presents the variable views is organized in three parts:

• Static data
• Dynamic data
• Dynamic push buttons

Static Data

The static part of the screen consists of the condition type and fields that make up the condition table key.

Dynamic Data

The screen also contains a dynamic part where the data changes according to the view you select.

The standard version includes the following sample views:

• Sales deal
• Administrative data (creator and creation date)
• Condition amount
• Terms of payment
• Validity period

In addition, you can create your own variable screen in Customizing using the data fields you want. Users can maintain data in the fields in the dynamic part of the screen.

Dynamic Push Buttons

You use the dynamic push buttons to select a particular view of the condition record data. In addition to the push buttons in the standard version, you can define your own buttons in Customizing according to the data you want to view.

SAP SD Selecting Variable Views of SD Condition Records

Steps:

To select the variable views of condition record data:

1. Choose Logistics
® Sales/distribution ® Master data in the main menu screen.

You reach the Sales Master Data screen.

2. Choose Conditions and select the change or display mode for the type of condition record (price, discount, surcharge) you want to work with.

You reach the selection screen for the condition records.

3. Enter your selection data and choose
Execute.

The system displays a list of the condition records which meet your selection criteria.

4. Choose Goto ®
Overview ® Condition Records.

You reach the condition record overview screen.

5. Choose one of the dynamic push-buttons at the bottom of the screen.

Additional Functions

You can branch into individual records to display or change them. You can also select records for collective change. For example, you can select a number of records and change the validity period for all the selected records in one step.

SAP SD What is Customer Expected Price

Use

Resolving disputed invoices costs some industries (for example, the consumer packaged goods industry) a great deal of time and money. Customers deduct disputed invoices from payments and staff members spend valuable time investigating and researching the reasons for the disputed payment. In addition, prolonged disputes can endanger supplier-customer relations. The extended pricing functions introduced in Release 2.2 enable you to take into account the customer's expected price. By entering the expected price during sales order processing and comparing it with your price, you can help avoid disputed invoices later.

During Order Entry

You can enter customer expected price data manually during order entry in the double-line overview screen of the sales order. Alternatively, you can enter the expected price data directly in the pricing screen, using one of two new condition types:

Condition type	Description
EDI1	Customer expected price
EDI2	Customer expected value

System Reaction to Price Variation

If, during order entry, the expected price and the actual price differ beyond a specified amount (according to the formula you specify in the pricing procedure), the system assigns an incompletion status to the order. The sales order cannot be processed for delivery or billing until the discrepancy is resolved.

Controlled Through Pricing Procedure

You control customer expected price functionality in the pricing procedure in Customizing for Sales. The pricing procedure must include the new condition types, EDI1 and EDI2. In addition you can specify a formula for each condition type. The formula enables you to specify different criteria for comparing expected and actual prices. The standard R/3 System includes two formulas:

Formula	Expected price may not deviate over...
8	expected price may not vary more than 1.00 of the currency unit
9	expected price may not vary more than 0.05 of the currency unit

You specify the formula in the Alternative calculation type field of your pricing procedure.

In addition, you can modify the standard formulas or create your own. For more information about working with formulas, see the online Implementation Guide.

Processing Sales Orders With Customer Expected Price

The following procedures show you how the customer expected price is entered during sales order processing and also how to process sales orders in which discrepancies between expected price and actual price have occurred.

Entering Customer Expected Price in the Sales Order

Processing Lists of Orders With Price Discrepancies

SAP Entering Customer Expected Price in the SD Sales Order

Steps:

To enter a customer's expected price in a sales order:

1. Within the sales order, choose Overview
® Double-line entry.

You reach the double-line entry overview screen.

2. If the customer-expected price refers to the net price per item, enter EDI1 in the Condition type field and the price in the Rate field.

If the customer expected price refers to the value of the item (net price times quantity), enter EDI2 in the Condition type field and the value in the Rate field. The data you enter appears as a new line in the pricing screen.

If the customer expected price varies from the automatically determined net price or value, the system marks the sales order as incomplete.

3. Either resolve the price discrepancy in the sales order or save the order as an incomplete document for processing later.

SAP Processing Lists of Orders With Price Discrepancies Pricing And Conditions

Depending on your sales order entry policy, you may want specialized staff to process sales orders with price discrepancies. In this case, you can create work lists of incomplete documents after order entry.

Steps:

To create a list of incomplete documents where the price varies from the customer expected price:

1. In the initial screen, choose Logistics
® Sales/distribution ® Sales.

You reach the Sales screen.

2. Choose Order
® Release CustExpPrice.

You reach the screen where you can enter selection criteria for your list.

3. Enter your selection criteria and choose Execute.

The system displays a list of incomplete documents that match your selection criteria. The list includes overview information for each document, such as the customer expected price and the net price.

4. If you want to release sales orders directly from the list, mark the documents and choose Release.

The system assigns a status indicator to each released document in the list.

5. If you want to make changes to pricing in a sales order, mark the document, then choose Environment
® Document.

You reach the respective document.

6. After you have finished processing documents in the list, save your work.

The system displays a summary of the released documents with their status.

SAP Pricing And Conditions Cost

Use

In Pricing, you may want to compare the prices with costs or even implement contribution margin accounting.

To do this, you can use the condition type VPRS as the cost price.

The condition type VPRS goes into the valuation segment in the material master and determines from this the standard price or average price.

Settings in Customizing

• The condition type VPRS is labeled as a statistical condition in the pricing procedure.
• Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
• The condition category S always accesses the standard price whereas condition category T always accesses the average price.
• The profit margin is determined using the calculation formula 11 assigned in the pricing procedure. In this calculation formula the cost price is subtracted from the subtotal of net value 2.

For Pricing, the costs from a calculation can also be determined:

Sales order calculation for pricing

For a third-party business transaction, the costs are determined from the purchase order:

Cost

SAP Condition Exclusion Pricing And Conditions

Use

During pricing in sales and billing documents, more than one condition record may apply to a particular item at any one time. You can use the condition exclusion process to compare possible conditions in order to determine such things as the best price for a customer.

The Condition Exclusion Procedure

First of all, you create exclusion groups. An exclusion group is a list of condition types that is identified by a three-digit number. Exclusion groups are defined in Customizing for Sales. You also assign exclusion groups to a pricing procedure and to determine how the condition exclusion is to be carried out.

You then assign the exclusion groups to a pricing procedure, thus defining the condition exclusion.

Depending on how you configure exclusion groups in the pricing procedure, the system can use condition exclusion to select the best price or discount in six different ways:

• Selecting the best condition record of a particular condition type from within one exclusion group
• Selecting the most unsuitable condition from within one exclusion group
• Selecting the best condition record for a condition type
• Selecting the most unsuitable condition record for a condition type
• Selecting the best conditions from different exclusion groups
• Excluding all condition types in the second exclusion group if a particular condition type in the first exclusion group exists in the document

Determining Best Price Across Condition Types

During automatic pricing for a sales order item, the system may find a number of valid condition records that apply to the same item. If the competing condition records belong to a variety of condition types, the system selects the record with the best price and excludes the other condition records. Condition records that the system ignores are not deleted from the sales order but are simply deactivated. You can still see the excluded condition records on the pricing screen in the sales order.

Determining Best Price Within One Condition Type

If the access sequence for a particular condition type does not specify exclusive accesses, it is possible for the competing condition records to exist within the same condition type. For example, the system may find two valid condition records for a material discount (K004) - one a material discount, the other a customer-specific material discount. The system determines the record with the most favorable discount for the customer.

If the Exclusive access indicator is set, the system looks no further after it finds the first valid condition record. In this case, the system cannot determine a best price.

Determining Best Price from Different Exclusion Groups

This method allows the system to check between exclusion groups for the most favorable price or discount. In this case, the system totals the condition values for each group, compares them, then selects the most advantageous group for the customer.

Excluding the Conditions in an Exclusion Group

In the fourth alternative when the system selects one particular condition type which exists in the first exclusion group, it excludes all the conditions in the second exclusion group from pricing.

After you have defined the exclusion groups you want to use, you can enter them in the pricing procedure. The following example shows how exclusion groups can be used in the pricing procedure. In this case, the exclusion procedure selected is the best condition type within one exclusion group.

Pricing procedure	Exclusion group	Condition type
RVAA01	001	KA00 Sales promotion
RVAA01	001	K005 Cust/mat. discount
RVAA01	002	KF00 Freight
RVAA01	002	KF01 Freight
RVAA01	002	KF02 Freight

You process a sales order item to which the following condition records apply:

Condition type	Rate	Value	Currency
PR00	100 USD/EA	100	USD
KA00	20%	20	USD
K005	10%	10	USD
KF01	1 USD/EA	1	USD
KF02	2 USD/EA	2	USD

In this example, exclusion group 001 deactivates condition type K005. (The system determines that the KA00 condition record is the best discount and ignores the other condition types defined in the group.) Exclusion group 002 deactivates condition type KF02 for the same reason.(The system determines that the KF01 condition record has the lowest freight cost and ignores the other condition types defined in the group.) The final price in this example is calculated this way:

100 USD - 20 USD + 1 USD = 81 USD/EA

See also:

Implementation Guide, Section Condition exclusion

SAP Pricing And Conditions Variant Conditions

Definition

You can use variant conditions to influence the price of a configurable material depending on the characteristic values assigned.

Use

You can use variant conditions in Sales and Distribution and Purchasing to define surcharges and discounts for the basic price.

Structure

Variant conditions consist of a variant key and an amount that is identified by the variant key.

SAP Minimum Order Value Pricing And Conditions

Use

You can specify a minimum order value for sales order processing. The following example illustrates how this function is used:

• You specify a minimum order value of USD 200.
• During sales order processing, the net value (after discounts and freight, before taxes) of an incoming order is USD 190.08.
• During pricing, the system determines that the net value falls below the minimum order value and calculates a minimum-order-value surcharge. In this example, the surcharge equals USD 9.92.
• The minimum order value and the surcharge appear as separate lines in the pricing screen. The minimum value is for information purposes only, and does not affect pricing. The system automatically adjusts the net value of the order (before taxes) to the minimum value allowed.

Condition Types for Minimum Order Value

The standard R/3 System includes two condition types for processing minimum value requirements:

Condition type	Name
AMIW	Minimum order value
AMIZ	Minimum value proposal

Creating Condition Records for Minimum Order Value

If you use minimum-order-value requirements, you must create condition records for condition type AMIW. In these condition records, you specify customers and the corresponding minimum order values. During pricing, the system automatically uses these condition records as a reference for determining the relevant minimum order surcharges (condition type AMIZ). In the standard version, condition type AMIZ refers to AMIW. This means that the system automatically calculates values for AMIZ conditions; you do not need to create separate condition records.

You may want to specify minimum order values by sales organization or division instead of by customer. In order to do this, your system administrator must define a new condition table with the appropriate fields in the table key. The condition table can then be included in the access sequence for condition type AMIW.