251
SCM620 Pricing in Sales Order Management mySAP ERP Sales and Services Date Training Center Instructors Education Website Participant Handbook Course Version: 2006/Q2 Course Duration: 3 Days Material Number: 50078011 An SAP course - use it to learn, reference it for work

mySAP ERP Sales and Services - saphelp.it - Pricing in Sales... · Tools → Customizing → IMG → Edit Project→ SAP Reference IMG → Sales and Distribution → Basic Functions

Embed Size (px)

Citation preview

SCM620Pricing in SalesOrderManagement

mySAP ERP Sales and Services

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2006/Q2Course Duration: 3 DaysMaterial Number: 50078011

An SAP course - use it to learn, reference it for work

Copyright

Copyright © 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. Additionally this publication and its contents are providedsolely for your use, this publication and its contents may not be rented, transferred or sold withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

� IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

� ORACLE® is a registered trademark of ORACLE Corporation.� INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.� UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.� Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

� JAVA® is a registered trademark of Sun Microsystems, Inc.� JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.� SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2006/Q2 © 2005 SAP AG. All rights reserved. iii

About This Handbook SCM620

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor�spresentation.

iv © 2005 SAP AG. All rights reserved. 2006/Q2

ContentsCourse Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: Condition Technique in Pricing ..... . . . . . . . . . . . . . . . . . . . . . . . . . . 1Pricing Fundamentals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Introduction to Condition Technique .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Unit 2: Pricing Configuration..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Overview of Pricing Configuration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Customizing Pricing Components .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Unit 3: Working with Condition Records ..... . . . . . . . . . . . . . . . . . . . . . . 79Pricing Reports and Maintenance .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Unit 4: Special Functions ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Special Pricing Functions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Hierarchy Pricing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Data Determination in Access.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Unit 5: Condition Types ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Special Condition Types .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Statistical Condition Types... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Unit 6: Taxes, Pricing Agreements, and Rebates..... . . . . . . . . . . . 183Taxes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Pricing Agreements.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Rebates .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Appendix 1: Appendix ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Appendix 2: Exercise Data ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Index ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

2006/Q2 © 2005 SAP AG. All rights reserved. v

Contents SCM620

vi © 2005 SAP AG. All rights reserved. 2006/Q2

Course OverviewThis course gives an introduction to the system configuration for pricing in SalesOrder Management.

Target AudienceThis course is intended for the following audiences:

� Project team members responsible for pricing

Course PrerequisitesRequired Knowledge

� Good knowledge of the processes and functions of Sales Order Mamagement

Course GoalsThis course will prepare you to:

� Define the necessary system settings for pricing in Sales Order Management

Course ObjectivesAfter completing this course, you will be able to:

� Describe the elements of the pricing condition technique and the relationshipsbetween them

� Convert your pricing requirements to the necessary pricing strategy� Make the necessary Customizing settings to implement your pricing strategy

SAP Software Component InformationThe information in this course pertains to the following SAP Software Componentsand releases:

2006/Q2 © 2005 SAP AG. All rights reserved. vii

Course Overview SCM620

viii © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 1Condition Technique in Pricing

Unit OverviewThis unit provides an overview of pricing and gives an introduction to conditiontechnique.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain how to use conditions in pricing� Demonstrate how to use condition records� Locate condition types in customizing� Use pricing procedures in pricing� Describe pricing procedures and access sequences� Explain header conditions� Control new pricing using the pricing type

Unit ContentsLesson: Pricing Fundamentals ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Exercise 1: Condition Records .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Exercise 2: Condition Type Configuration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Lesson: Introduction to Condition Technique... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Exercise 3: Condition technique terms ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Exercise 4: Adding and Changing Conditions ... . . . . . . . . . . . . . . . . . . . . . . . . 29Exercise 5: Conditions in the Document Header... . . . . . . . . . . . . . . . . . . . . . 33Exercise 6: New Pricing and Pricing Types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2006/Q2 © 2005 SAP AG. All rights reserved. 1

Unit 1: Condition Technique in Pricing SCM620

Lesson: Pricing Fundamentals

Lesson OverviewThis lesson describes the conditions used in pricing. It also explains how to usethe condition records and locate the condition types in customizing.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain how to use conditions in pricing� Demonstrate how to use condition records� Locate condition types in customizing

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP System must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements. In pricing, conditions, such as prices, discounts, surcharges, freight,and taxes, must be determined automatically for business transactions.

Pricing Components

Figure 1: Groups of Conditions

Data about conditions is stored in condition records.

2 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

You can determine conditions at any level you require.

The levels at which pricing is most commonly carried out have been predefinedin the standard version.

You can add additional levels, if required. A standard field catalog containingthe fields commonly used in pricing is provided within customizing. You canmake conditions dependent on any document field(s) but you may have to addthese fields to the field catalog.

Figure 2: Condition Records

You can limit a pricing agreement to a certain period by specifying a validityperiod, as shown:.

For example:

� Different price lists for different years� Discounts given only for the duration of a special offer

The values in a condition record, such as price, surcharge, and discount, can bedefined according to a scale. You can specify an unlimited number of levels in ascale.

You can specify an upper and lower limit for each condition record. Manualchanges to pricing elements determined by the system can be made only withinthese limits.

2006/Q2 © 2005 SAP AG. All rights reserved. 3

Unit 1: Condition Technique in Pricing SCM620

Figure 3: Condition Types

The condition type determines the category of a condition and describes howthe condition is used.

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

Possible scale base types Possible calculation typesValue Percentage from an initial value

Fixed amountQuantity Amount per unit of measureWeight Amount per unit of weightVolumes Amount per unit of volumeTime period Quantity per unit of time

4 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

Figure 4: Condition Maintenance

Since SAP R/3 Release 4.6A, an additional maintenance interface is providedfor condition maintenance.

The new interface allows mass maintenance of conditions based on characteristics,for example, for customers.

This means that condition records can now be maintained across all conditiontypes and condition tables. For example, you can display and maintain thematerial prices and the discounts and surcharges for a customer in one step.

You can also call up the previous maintenance transaction for conditions bychoosing Select using the condition type.

2006/Q2 © 2005 SAP AG. All rights reserved. 5

Unit 1: Condition Technique in Pricing SCM620

6 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

Exercise 1: Condition Records

Exercise ObjectivesAfter completing this exercise, you will be able to:� Check pricing data and understand system messages� Create and use condition records with and without scales

Business ExampleYou will be testing the basic pricing concepts dealing with the creation and useof condition records. In addition, you need to gain familiarity with the pricingdata shown in the order.

Task 1:You need to create a simple order to determine what happens when pricinginformation is missing from the system.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-1Requested delivery date: In one weekMaterial T-AT1##Quantity 10

2. Why does this cause an error message?

3. What needs to be done to correct the error?

4. Exit without saving the order.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 7

Unit 1: Condition Technique in Pricing SCM620

Task 2:To supply the missing pricing information, you need to create a price conditionrecord, test the record by entering the same order as before, and check the pricinginformation in the order.

1. Create a material price condition record (PR00) for material T-AT1## foryour sales organization and distribution channel. The price is 280 EUR. Usethe default validity period.

Hint: In this introductory unit, use the maintenance transaction thatis called through the Select using condition type node.

2. Save the condition record.

3. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-2Requested delivery date: In one weekMaterial: T-AT1##Quantity: 10

4. Display the pricing conditions for the order item and record the gross pricedetermined automatically during pricing.

5. Can you save the order now?

Task 3:Occasionally, your company gives special prices and discounts to particularcustomers. You need to create condition records, which include the scale valuesfor your customers. Then, you need to test these new records by creating theorders and viewing the results.

1. Create a customer-specific price condition record (PR00) for materialT-AT1## and customer T-L67A## for your sales organization anddistribution channel. Use the default validity period.

Use the following scale values for the condition record:

Continued on next page

8 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

from 1 piece 250 EUR10 pieces 240 EUR100 pieces 230 EUR

2. Save the condition record.

3. Create a customer-specific discount condition record (K007) with scalevalues for customer T-L67A## for your sales area. Use the default validityperiod.

Use the following scale values for the condition record:

from 100 EUR 2 %1000 EUR 3 %5000 EUR 5 %

4. Save the condition record.

5. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-3Requested delivery date: In one weekMaterial T-AT1##Quantity 10

6. Display the pricing condition for the order item and note all the conditionsdetermined automatically during pricing.

7. Save the order and record the document number.

2006/Q2 © 2005 SAP AG. All rights reserved. 9

Unit 1: Condition Technique in Pricing SCM620

Solution 1: Condition RecordsTask 1:You need to create a simple order to determine what happens when pricinginformation is missing from the system.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-1Requested delivery date: In one weekMaterial T-AT1##Quantity 10

a) To create a standard order, select

Logistics→ Sales and Distribution→ Sales→ Order→ Create.

Order Type: OR

2. Why does this cause an error message?

a) The system displays an error message because the mandatory pricingcondition record PR00 is missing for the material.

3. What needs to be done to correct the error?

a) To correct the error, you need to create a material price conditionrecord for the material.

4. Exit without saving the order.

a)

Continued on next page

10 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

Task 2:To supply the missing pricing information, you need to create a price conditionrecord, test the record by entering the same order as before, and check the pricinginformation in the order.

1. Create a material price condition record (PR00) for material T-AT1## foryour sales organization and distribution channel. The price is 280 EUR. Usethe default validity period.

Hint: In this introductory unit, use the maintenance transaction thatis called through the Select using condition type node.

a) To create a material price, select:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Select Using Condition Type→ Create.

Choose condition type PR00.

Choose the key combinationMaterial with release status.

2. Save the condition record.

a) Choose Save

3. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-2Requested delivery date: In one weekMaterial: T-AT1##Quantity: 10

a) To create a standard order, select:

Logistics→ Sales and Distribution→ Sales→ Order→ Create.

4. Display the pricing conditions for the order item and record the gross pricedetermined automatically during pricing.

a) Select the item and choose Item conditions. Pricing automaticallydetermined the material price PR00 as EUR 280 per piece.

5. Can you save the order now?

a) Yes, you can now save the order.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 11

Unit 1: Condition Technique in Pricing SCM620

Task 3:Occasionally, your company gives special prices and discounts to particularcustomers. You need to create condition records, which include the scale valuesfor your customers. Then, you need to test these new records by creating theorders and viewing the results.

1. Create a customer-specific price condition record (PR00) for materialT-AT1## and customer T-L67A## for your sales organization anddistribution channel. Use the default validity period.

Use the following scale values for the condition record:

from 1 piece 250 EUR10 pieces 240 EUR100 pieces 230 EUR

a) To create customer-specific price condition records, select:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Select Using Condition Type→ Create.

Choose condition type PR00.

Choose the key combination Customer/material with release status.

To enter the scale values, select the condition line and choose Scales.

2. Save the condition record.

a) Choose Save

3. Create a customer-specific discount condition record (K007) with scalevalues for customer T-L67A## for your sales area. Use the default validityperiod.

Use the following scale values for the condition record:

Continued on next page

12 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

from 100 EUR 2 %1000 EUR 3 %5000 EUR 5 %

a) To create a customer-specific discount condition record (K007), select:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Select Using Condition Type→ Create.

Choose condition type K007.

Choose the key combination Division/Customer.

To enter the scale values, select the condition line and choose Scales.

4. Save the condition record.

a) Choose Save

5. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67A##PO number: ##-1-3Requested delivery date: In one weekMaterial T-AT1##Quantity 10

a) To create a standard order, select:

Logistics→ Sales and Distribution→ Sales→ Order→ Create.

6. Display the pricing condition for the order item and note all the conditionsdetermined automatically during pricing.

a) Click the Item Overview button. Select the item and choose Itemconditions. Pricing automatically determined the material price PR00as EUR 240 per piece and the customer discount (K007) as 3%.

7. Save the order and record the document number.

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 13

Unit 1: Condition Technique in Pricing SCM620

14 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

Exercise 2: Condition Type Configuration

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use the IMG to access pricing settings in Customizing� View the Customizing settings for a condition type

Business ExampleAs a member of the pricing implementation team, you will be using the IMG toview all forms of pricing configuration.

Task:You must verify that the configuration settings for certain condition types areappropriate.

1. Display the settings for condition type K007 in Customizing. Whatcalculation type and scale base type are assigned to this condition type?

2. What effects do these settings have?

2006/Q2 © 2005 SAP AG. All rights reserved. 15

Unit 1: Condition Technique in Pricing SCM620

Solution 2: Condition Type ConfigurationTask:You must verify that the configuration settings for certain condition types areappropriate.

1. Display the settings for condition type K007 in Customizing. Whatcalculation type and scale base type are assigned to this condition type?

a) Calculation type: A Percentage

Scale base type: B Value scale

Tools→ Customizing→ IMG→ Edit Project→ SAP Reference IMG→ Sales and Distribution→ Basic Functions→ Pricing→ PricingControl→ Define Condition Types.

Choose Maintain Condition Types.

Select K007 and click the Details button.

2. What effects do these settings have?

a) Effects:

The discount is calculated as a percentage of the item�s value and thediscount scale entries are based on the value of the order item, insteadof its weight or volume.

16 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Fundamentals

Lesson Summary

You should now be able to:� Explain how to use conditions in pricing� Demonstrate how to use condition records� Locate condition types in customizing

2006/Q2 © 2005 SAP AG. All rights reserved. 17

Unit 1: Condition Technique in Pricing SCM620

Lesson: Introduction to Condition Technique

Lesson OverviewThis lesson provides an introduction to the pricing procedure used in pricingand enables you to understand the task of the access sequences. It also explainscondition handling in the documen header and describes how to use pricing types.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Use pricing procedures in pricing� Describe pricing procedures and access sequences� Explain header conditions� Control new pricing using the pricing type

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements. Because requirements differ from one company to another, pricingmust be configurable.

18 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Pricing Procedure Overview

Figure 5: Pricing Procedure

All condition types permitted in pricing are available in the pricing procedure.

You need to determine how the system should use conditions by specifying therequirements for each condition.

The sequence in which the system accesses the conditions in the businessdocument is also determined in the pricing procedure.

The reference level provides a method to specify a different basis to calculate thecondition type and to group conditions for subtotals.

The pricing procedure can contain any number of subtotals.

You can mark a condition type in the pricing procedure as being:

� a mandatory condition� a manually entered condition� for statistical purposes only

2006/Q2 © 2005 SAP AG. All rights reserved. 19

Unit 1: Condition Technique in Pricing SCM620

Access Sequence Overview

Figure 6: Access Sequence

An access sequence can be assigned to a condition type (except for conditiontypes configured as a header condition).

This search strategy defines the sequence in which the system reads the conditionrecords for a condition type.

Each access performed during the access sequence is made using a condition table.

A condition table is a combination of fields, which form the key for a conditionrecord.

You can make an access dependent on certain requirements.

Pricing Overview

Figure 7: Pricing Overview (1)

In this example, an order for 120 pieces of a material is created. The system mustdetermine the price automatically.

20 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Figure 8: Pricing Overview (2)

First, the relevant pricing procedure is determined based on the sales area,customer, and sales document type.

Figure 9: Pricing Overview (3)

The system reads the condition type of the first step and then determines theassigned access sequence for this condition type.

Figure 10: Pricing Overview (4)

The system reads the access sequence. The sequence of the condition tablesrepresents the search strategy to find the relevant condition record.

Each condition table represents one access, which can be made for a conditionrecord with the specified key.

2006/Q2 © 2005 SAP AG. All rights reserved. 21

Unit 1: Condition Technique in Pricing SCM620

Figure 11: Pricing Overview (5)

The system searches for valid condition records with the key specified by thecondition table (accesses).

If the first access does not find a valid condition record, then the system searchesfor the next access using the next condition table.

Figure 12: Pricing Overview (6)

After the system finds a valid condition record for an access, the system readsthe condition record and copies the value that corresponds to the scale into thesales document.

22 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

The whole process is repeated for each condition type until the system has finishedthe entire pricing procedure.

Changing Prices Manually

Figure 13: Changing Prices Manually in Documents

The prices, surcharges, and discounts determined automatically by the system canbe changed manually and are then marked as such.

In the condition records, you can specify limits within which a manual change canbe made, for example, making a discount, which could only be changed betweenthe range 1% and 3%.

In addition to determining conditions automatically, conditions can be enteredmanually in the sales document. Conditions are marked as having been enteredmanually.

You can change or create conditions on the condition screen.

You can prevent one condition type from being changed manually by makingthe appropriate settings in customizing.

2006/Q2 © 2005 SAP AG. All rights reserved. 23

Unit 1: Condition Technique in Pricing SCM620

Maintaining Header Conditions

Figure 14: Conditions in the Document Header

Conditions can also be entered at the document header level. These are known asheader conditions and are valid for all items.

These header conditions are automatically distributed among the items based onnet value. The basis for distributing the header conditions can be changed in thepricing procedure by selecting the appropriate routine, for example, weight andvolume, in the Alternative formula for Condition Base Value (AltCBV) field.

Figure 15: Creating Conditions in the Document Header (1)

In this example, the header condition amount is copied into each item of the order.

24 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Figure 16: Creating Conditions in the Document Header (2)

In the second example, the header condition amount is distributed among the itemsbased on its portion of the total net value.

New Pricing and Pricing Types

Figure 17: New Pricing and Pricing Types

You can configure the pricing behavior in the Pricing type.

2006/Q2 © 2005 SAP AG. All rights reserved. 25

Unit 1: Condition Technique in Pricing SCM620

You have two options to control the New pricing function in the sales document:

� Update prices on the condition screens is available at the header and itemlevels. You can choose the pricing type in the dialog box that appears.

� To use the new pricing document function for the sales document (→ Edit→ New pricing document), assign a pricing type to the pricing procedure incustomizing. If you do not maintain an entry, the system uses pricing typeB (Carry out new pricing).

These functions are supported for both the sales and billing documents.

Figure 18: Pricing in the Billing Document

Copying control makes it possible to handle repricing of billing documents basedon several different scenarios. While all customers will not use every possiblepricing type, the ability to specify what will happen to pricing calculations duringbilling is a decision each customer must make

26 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Exercise 3: Condition technique terms

Exercise ObjectivesAfter completing this exercise, you will be able to:� Differentiate the use of some important condition technique terms

Business ExampleAs a member of the project team, you have been given the task of examining thepricing configuration options.

Task:Before viewing several configuration tables in this unit, review the use of thesecondition technique terms.

1. In pricing, what object stores the condition types and the sequence in whichthey are executed in the sales document during pricing?

2. What criteria influence pricing procedure determination during pricing?

3. What pricing element is used to control pricing so that you can specify thata customer-specific price rather than a material price is to be used duringautomatic pricing?

2006/Q2 © 2005 SAP AG. All rights reserved. 27

Unit 1: Condition Technique in Pricing SCM620

Solution 3: Condition technique termsTask:Before viewing several configuration tables in this unit, review the use of thesecondition technique terms.

1. In pricing, what object stores the condition types and the sequence in whichthey are executed in the sales document during pricing?

a) The pricing procedure.

2. What criteria influence pricing procedure determination during pricing?

a) The following criteria influence how pricing procedures are determined:

� The sales area, which includes the sales organization, distributionchannel, and division

� The document pricing procedure code in the document type� The customer pricing procedure code in the customer master

record

3. What pricing element is used to control pricing so that you can specify thata customer-specific price rather than a material price is to be used duringautomatic pricing?

a) The access sequence determines the sequence in which the conditionrecords for a condition type are found and read.

28 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Exercise 4: Adding and ChangingConditions

Exercise ObjectivesAfter completing this exercise, you will be able to:� Explain how the system records new order conditions� Change existing order conditions

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP R/3 Enterprise Sales and Distribution (SD) module must meet thecompany�s pricing requirements. As a member of the project team, you have beengiven the task of examining the pricing configuration options to provide solutionsfor your company�s pricing requirements. To meet these requirements, thecondition technique combines certain elements, which also perform various tasks.

Task:Occasionally, order entry personnel need to manually adjust the pricing onan order. You can add additional conditions manually and change automaticconditions at the item level of the order.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAX

Customer: T-L67A##

PO number: ##-2-3

Requested delivery date: In one week

Material Quantity

T-AT1## 10

2. Go to the condition screen for the item and manually add a quantity discountof EUR 10- per piece. Use condition type RC00.

3. In the order, change the K007 customer discount manually to a rate of 4%discount.

4. View the item condition detail screen for K007. How can you determinewhether or not the condition has been edited manually?

5. Save the order and record the document number.

2006/Q2 © 2005 SAP AG. All rights reserved. 29

Unit 1: Condition Technique in Pricing SCM620

Solution 4: Adding and ChangingConditionsTask:Occasionally, order entry personnel need to manually adjust the pricing onan order. You can add additional conditions manually and change automaticconditions at the item level of the order.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAX

Customer: T-L67A##

PO number: ##-2-3

Requested delivery date: In one week

Material Quantity

T-AT1## 10

a) To create a standard order, select:

Logistics→ Sales and Distribution→ Sales→ Order→ Create.

2. Go to the condition screen for the item and manually add a quantity discountof EUR 10- per piece. Use condition type RC00.

a) Click the Item overview button.

Select the line item and click the Item conditions button.

Click the Insert line button.

After entering the values, activate the condition by clicking the Enterbutton.

3. In the order, change the K007 customer discount manually to a rate of 4%discount.

a) To determine manually changed values:

Select the K007 line on the item condition screen and click the Detailsbutton.

On the Item Condition Detail screen, the Condition control field is setto C if the condition has been changed manually.

4. View the item condition detail screen for K007. How can you determinewhether or not the condition has been edited manually?

a)

Continued on next page

30 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

5. Save the order and record the document number.

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 31

Unit 1: Condition Technique in Pricing SCM620

32 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Exercise 5: Conditions in the DocumentHeader

Exercise ObjectivesAfter completing this exercise, you will be able to:� Enter header level conditions and see their effect on the line items of an order

Business ExampleWhen pricing conditions apply to all the items of an order, these conditions canbe entered in the header of the order. You need to test how header conditions areentered and how they are distributed among the line items of a sales document.

Task:Header level pricing conditions apply to all the items in the order. You can createheader discounts and view their effect at the item level of the order.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAX

Customer: T-L67A##

PO number: ##-2-4

Requested delivery date: In one week

Material Quantity

T-AT1## 10

T-AT2## 10

2. Go to the header condition screen of the order and create two discountsmanually. The first discount is condition type HB00 with a rate of 100-. Thesecond discount is condition type RB00 with a rate of 100-.

3. Activate the header pricing. Record the results at the item level.

Hint: Click the Next item button to see line item 20 withoutreturning to the Overview screen.

4. Save the order and record the document number.

2006/Q2 © 2005 SAP AG. All rights reserved. 33

Unit 1: Condition Technique in Pricing SCM620

Solution 5: Conditions in the DocumentHeaderTask:Header level pricing conditions apply to all the items in the order. You can createheader discounts and view their effect at the item level of the order.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAX

Customer: T-L67A##

PO number: ##-2-4

Requested delivery date: In one week

Material Quantity

T-AT1## 10

T-AT2## 10

a) To create a standard order, select:

Logistics→ Sales and Distribution→ Sales→ Order→ Create.

2. Go to the header condition screen of the order and create two discountsmanually. The first discount is condition type HB00 with a rate of 100-. Thesecond discount is condition type RB00 with a rate of 100-.

a) Click the Display document header details button at the top right ofthe screen.

Select the Conditions tab.

Click the Insert line button.

Enter the condition types and their rates.

3. Activate the header pricing. Record the results at the item level.

Hint: Click the Next item button to see line item 20 withoutreturning to the Overview screen.

a) Activate the new header conditions by clicking the Activate button.

Go back to the Overview screen and select both the line items.

Go to the item condition screen. Absolute discount RB00 was copieddirectly into each item. Absolute discount HB00 was distributedproportionally between the items because it is a group condition.

Continued on next page

34 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

4. Save the order and record the document number.

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 35

Unit 1: Condition Technique in Pricing SCM620

36 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Exercise 6: New Pricing and Pricing Types

Exercise ObjectivesAfter completing this exercise, you will be able to:� Check the copy control tables to locate the pricing type field and examine

its effect on pricing during billing

Business ExampleIn your business environment, prices for many materials change frequently. Youwill need to verify how you can adjust the pricing during billing to meet variousrequirements.

Task:When prices or discounts change from the time the order is taken to the time theinvoice is created, you require the system to handle the changes automatically inan appropriate way. You will test the effect of pricing types on pricing and viewthe related tables in Customizing to learn where this function is controlled.

1. From the customer purchase order shown below, create a standard sales order.

TELEFAX

Customer: T-L67A##

PO number: ##-2-5

Requested delivery date: In one week

Material Quantity

T-AT1## 10

2. Enter a manual discount at item level using condition type RC00 for a rateof 100-.

3. Save the order and record the document number.

4. Create an outbound delivery for this order, pick the entire quantity, and thenpost goods issue. Note the document number. Use shipping point 1200 and aselection date of 10 days from today. When creating the transfer order forpicking, choose warehouse number 012.

5. Create an invoice for this outbound delivery, but DO NOT SAVE IT. Whatbilling type is used by default?

6. Examine the pricing details in the invoice and determine what conditionswere used to arrive at the net price. Note the net price.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 37

Unit 1: Condition Technique in Pricing SCM620

7. You will implement new pricing for the item using pricing type B.

Hint: You can choose entries for your personal list of values fromthe variety of pricing types proposed in the dialog box.

This allows the selection screen to be structured more clearly.

8. Examine the pricing details again and note the difference in the conditiontypes that are used now. What is the effect on the net price of the invoice?What caused this to happen? Save the invoice and record the documentnumber.

9. In the IMG, view the Pricing type field in the copying control table forbilling types F1 and F2. View the entries for these billing documents whenthey are created with reference to an LF delivery document and an itemcategory of TAN. Record your answers.

38 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

Solution 6: New Pricing and Pricing TypesTask:When prices or discounts change from the time the order is taken to the time theinvoice is created, you require the system to handle the changes automatically inan appropriate way. You will test the effect of pricing types on pricing and viewthe related tables in Customizing to learn where this function is controlled.

1. From the customer purchase order shown below, create a standard sales order.

TELEFAX

Customer: T-L67A##

PO number: ##-2-5

Requested delivery date: In one week

Material Quantity

T-AT1## 10

a)

2. Enter a manual discount at item level using condition type RC00 for a rateof 100-.

a) Select the line item and click the Item conditions button.

Click the Insert line button.

Enter the condition type and rate.

3. Save the order and record the document number.

a)

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 39

Unit 1: Condition Technique in Pricing SCM620

4. Create an outbound delivery for this order, pick the entire quantity, and thenpost goods issue. Note the document number. Use shipping point 1200 and aselection date of 10 days from today. When creating the transfer order forpicking, choose warehouse number 012.

a) Creating an outbound delivery, a transfer order to do the picking, andthen posting goods issue.

Logistics→ Sales and Distribution→ Shipping and Transportation→ Outbound Delivery→ Create→ Single Document→ WithReference to Sales Order.

To pick the required quantity from directly within the delivery, choose:

Subsequent functions→ Create transfer order.

Enter the warehouse number 012.

In the Adopt picking quantity field, choose function 2 (copy the pickingquantity to the delivery and post goods issue).

Save the transfer order.

5. Create an invoice for this outbound delivery, but DO NOT SAVE IT. Whatbilling type is used by default?

a) Creating a billing document:

Logistics→ Sales and Distribution→ Billing→ Billing Document→ Create.

Enter your delivery document number and click the Execute button.

An F2 invoice document is created. You can see the document typein the title bar.

6. Examine the pricing details in the invoice and determine what conditionswere used to arrive at the net price. Note the net price.

a) Select the line item and click the Item conditions button.

The condition types PR00, K007, and RC00 are shown.

Continued on next page

40 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Introduction to Condition Technique

7. You will implement new pricing for the item using pricing type B.

Hint: You can choose entries for your personal list of values fromthe variety of pricing types proposed in the dialog box.

This allows the selection screen to be structured more clearly.

a) Select the line item and click the Item conditions button.

Click the Update prices button at the bottom of the screen.

Choose pricing type B (carry out new pricing).

8. Examine the pricing details again and note the difference in the conditiontypes that are used now. What is the effect on the net price of the invoice?What caused this to happen? Save the invoice and record the documentnumber.

a) Select the line item and click the Item conditions button.

Only condition types PR00 and K007 are used to calculate the netprice. The RC00 discount entered manually is not used becausepricing type B discards manual discounts when recalculating pricing.

9. In the IMG, view the Pricing type field in the copying control table forbilling types F1 and F2. View the entries for these billing documents whenthey are created with reference to an LF delivery document and an itemcategory of TAN. Record your answers.

a) Checking the copying control:

Tools→ Customizing→ IMG→ Edit Project→ SAP ReferenceIMG→ Sales and Distribution→ Billing→ Billing Documents→ Maintain Copying Control For Billing Documents→ Copyingcontrol: Delivery document to billing document.

Select the line with F1 as Tgt and LF as Source and double click theItem node in the overview tree.

Select item category TAN and click the Details button.

Pricing type C (copy manual pricing elements and redetermine thoseremaining) is used.

Repeat the process for F2 as Tgt and LF as Source with itemcategory TAN. Pricing type G (copy pricing elements unchanged andredetermine taxes) is used.

2006/Q2 © 2005 SAP AG. All rights reserved. 41

Unit 1: Condition Technique in Pricing SCM620

Lesson Summary

You should now be able to:� Use pricing procedures in pricing� Describe pricing procedures and access sequences� Explain header conditions� Control new pricing using the pricing type

42 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Unit Summary

Unit SummaryYou should now be able to:� Explain how to use conditions in pricing� Demonstrate how to use condition records� Locate condition types in customizing� Use pricing procedures in pricing� Describe pricing procedures and access sequences� Explain header conditions� Control new pricing using the pricing type

2006/Q2 © 2005 SAP AG. All rights reserved. 43

Unit Summary SCM620

44 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. You can limit a pricing agreement to a certain period by specifying a.

Fill in the blanks to complete the sentence.

2. With the additional maintenance interface since SAP R/3 Release 4.6A,condition records can be maintained across all condition types and conditiontables.Determine whether this statement is true or false.□ True□ False

3. You can mark a condition in the pricing procedure as being:Choose the correct answer(s).□ A A mandatory condition□ B A manually entered condition□ C For statistical purposes only□ D An automatically entered condition

4. A condition table is a combination of fields, which form the key for a.

Fill in the blanks to complete the sentence.

5. The header conditions are manually distributed among the items based onthe net value.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2005 SAP AG. All rights reserved. 45

Test Your Knowledge SCM620

Answers

1. You can limit a pricing agreement to a certain period by specifying a validityperiod.

Answer: validity period

2. With the additional maintenance interface since SAP R/3 Release 4.6A,condition records can be maintained across all condition types and conditiontables.

Answer: True

With the additional maintenance interface since SAP R/3 Release 4.6A,condition records can be maintained across all condition types and conditiontables.

3. You can mark a condition in the pricing procedure as being:

Answer: A, B, C

You can mark a condition in the pricing procedure as being a mandatorycondition, a manually entered condition, and for statistical purposes only.

4. A condition table is a combination of fields, which form the key for acondition record.

Answer: condition record

5. The header conditions are manually distributed among the items based onthe net value.

Answer: False

The header conditions are automatically distributed among the items basedon the net value.

46 © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 2Pricing Configuration

Unit OverviewThis unit discusses how to change and add to the different pricing elements andimplement customizing settings for pricing.

Unit ObjectivesAfter completing this unit, you will be able to:

� Change and add to different pricing elements� Explain pricing configuration� Implement customizing settings for pricing

Unit ContentsLesson: Overview of Pricing Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Lesson: Customizing Pricing Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Exercise 7: Pricing Procedure Determination ... . . . . . . . . . . . . . . . . . . . . . . . . 57Exercise 8: Controls in Pricing Elements... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Exercise 9: Comprehensive Pricing Exercise ... . . . . . . . . . . . . . . . . . . . . . . . . 65

2006/Q2 © 2005 SAP AG. All rights reserved. 47

Unit 2: Pricing Configuration SCM620

Lesson: Overview of Pricing Configuration

Lesson OverviewThis lesson enables you to change and add to the different pricing elements. It alsoexplains pricing configuration.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Change and add to different pricing elements� Explain pricing configuration

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements. In pricing, price discounts, surcharges, freights, and taxes must bedetermined automatically for business transactions. You must also be able toalter these conditions manually.

Condition Table

Figure 19: Overview: Pricing Configuration (1)

The condition table contains the keys that can be used to create dependentcondition records.

You can add your own condition tables using tables from 501 through 999.

48 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Overview of Pricing Configuration

Figure 20: Condition Tables

Condition records are always created using a specific key.

Condition tables are used to define the structure of the keys of a condition record.

The most important fields used in pricing at the header and item levels areavailable in the standard system.

Since SAP R/3 Release 4.5, you can also add non-key fields to the conditiontables. This is explained in condition table 144, which is used in the price book(condition type PBUD).

The key fields of a condition table must appear at the start of the table.

In the condition table you can determine whether a field appears in the header or inthe item of the generated fast entry screen for the maintenance of condition records.

Access Sequence

Figure 21: Overview: Pricing Configuration (2)

An access sequence consists of one or more condition tables.

2006/Q2 © 2005 SAP AG. All rights reserved. 49

Unit 2: Pricing Configuration SCM620

Figure 22: Creating an Access Sequence

You can define prices, discounts, and surcharges at various levels.

Each level is defined by a condition table.

The order of the entries in an access sequence defines the hierarchy of the variouslevels.

The system determines the condition records in the sequence specified.

Figure 23: Determining Source Fields for Access Sequences

Within each access of an access sequence, you can specify the document field orsource field with which an access is performed.

50 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Overview of Pricing Configuration

Examples:

� Material or pricing material?� Document currency or local currency?� Sold-to party or ship-to party?

Figure 24: Access Requirements

You are able to make accesses dependent on requirements to avoid unnecessaryaccesses. This reduces the system load.

Condition Type

Figure 25: Overview: Pricing Configuration (3)

After the access sequence is created, it is assigned to a condition type.

2006/Q2 © 2005 SAP AG. All rights reserved. 51

Unit 2: Pricing Configuration SCM620

You can also create your own condition types. You can determine thecharacteristics of each condition type, for example, whether or not the conditiontype represents surcharges or discounts and whether or not the condition typeshould be dependent on values or quantities.

Pricing Procedure

Figure 26: Overview: Pricing Configuration (4)

The condition types are combined in the required sequence in the pricingprocedure.

52 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Overview of Pricing Configuration

Procedure Determination

Figure 27: Overview: Pricing Configuration (5)

Finally, you need to maintain the determination of the pricing porcedure. Thepricing procedure is determined according to the following factors:

� Sales area� Customer pricing procedure field in the customer master� Document pricing procedure field that is assigned to the sales document type

2006/Q2 © 2005 SAP AG. All rights reserved. 53

Unit 2: Pricing Configuration SCM620

Lesson Summary

You should now be able to:� Change and add to different pricing elements� Explain pricing configuration

54 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Lesson: Customizing Pricing Components

Lesson OverviewThis lesson provides an overview of how to implement pricing strategies.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Implement customizing settings for pricing

Business ExampleYour company produces consumer goods. The project team that implements theSAP system must meet the company�s pricing requirements. As a member of theproject team, you have been given the task of examining the pricing configurationoptions to provide solutions for your company�s pricing requirements.

Customizing Pricing Components

Figure 28: Adding New Fields for Pricing

The information required to add new pricing fields is available in the IMGdocumentation. Search for Create new fields using the condition technique.

� To solve particular problems, you need to build and link all the pricingcomponents creatively.

� Condition table � Defines the key fields of the condition records.� Access sequence � Contains the hierarchy for condition record access.� Condition type � Represents the properties of the pricing conditions.� Pricing procedure � Defines how the condition types are linked.� Procedure determination � Selects the correct pricing procedure.

2006/Q2 © 2005 SAP AG. All rights reserved. 55

Unit 2: Pricing Configuration SCM620

Meeting particular pricing requirements may require one or more new pricingcomponents. Understanding the purpose and capabilities of each componentand the relationships between pricing components is critical to meet pricingrequirements.

� The following elements may be necessary to implement complex scenarios:

� Adding new fields for pricing � Creates new fields to meet customerrequirements.

� Requirements � Defines dependencies and improves performance.� Formulae � Enables expanding the limits of standard configuration.

New fields may be added to the pricing field catalog. This allows you to use thenew field to define condition tables.

Requirement routines and formulae provide a method to modify the standardpricing logic to meet unique user requirements.

SAP provides tools to create these pricing elements. These tools are accessedthrough the IMG.

56 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Exercise 7: Pricing ProcedureDetermination

Exercise ObjectivesAfter completing this exercise, you will be able to:� Check all the fields that are used to determine the pricing procedure� Understand the table to determine the pricing procedure in the IMG

Business ExampleYour company uses several pricing procedures, depending on the combination ofcustomer, order type, and organizational units. You need to verify whether or notthe proper pricing procedure is used in all the cases.

Task:As a team member of the project, you need to ensure that the correct pricingprocedure is being used in all cases. You need to access all the relevant data usedin this process and use the IMG to view the pricing procedure determination tables.

1. In the table in exercise 1-1-3, note the value of the Customer pricingprocedure field found in the sales area data of the master record for customerT-L67A##.

2. In the table in exercise 1-1-3, note the value of the Document pricingprocedure field for document type OR using the IMG.

3. What pricing procedure does the system determine if you create a standardorder for the following values?

Sales organization 1000DistrChannel 10Divis. 00Document pricing procedureCustomer pricing procedurePricing procedure for the order

2006/Q2 © 2005 SAP AG. All rights reserved. 57

Unit 2: Pricing Configuration SCM620

Solution 7: Pricing ProcedureDeterminationTask:As a team member of the project, you need to ensure that the correct pricingprocedure is being used in all cases. You need to access all the relevant data usedin this process and use the IMG to view the pricing procedure determination tables.

1. In the table in exercise 1-1-3, note the value of the Customer pricingprocedure field found in the sales area data of the master record for customerT-L67A##.

a) To find the customer pricing procedure, select:

Logistics→ Sales and Distribution→ Master Data→ BusinessPartner→ Customer→ Display→ Sales and Distribution.

Enter the customer number and the sales area.

Click Continue.

Choose Sales Area Data.

The Customer pricing procedure field is on the Orders tab and has avalue of 1.

2. In the table in exercise 1-1-3, note the value of the Document pricingprocedure field for document type OR using the IMG.

a) To find the document pricing procedure, select:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define And Assign Pricing Procedures.

Choose the Assign document pricing procedures to order types.

Place the pointer on document type OR.

The document pricing procedure field (DoPr) has a value A.

3. What pricing procedure does the system determine if you create a standardorder for the following values?

Sales organization 1000DistrChannel 10Divis. 00

Continued on next page

58 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Document pricing procedureCustomer pricing procedurePricing procedure for the order

a) Pricing procedure determination:

Sales organization 100DistrChannel 10Divis. 00Document pricing procedure ACustomer pricing procedure 1Pricing procedure for the order RVAA01

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define And Assign Pricing Procedures.

Choose Define Pricing Procedure Determination.

Click Position and enter the appropriate data using the values in thetable above.

Pricing procedure RVAA01 is determined.

2006/Q2 © 2005 SAP AG. All rights reserved. 59

Unit 2: Pricing Configuration SCM620

60 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Exercise 8: Controls in Pricing Elements

Exercise ObjectivesAfter completing this exercise, you will be able to:� Check the various control fields in each element of the pricing condition

technique

Business ExampleTo meet the pricing demands of your business, you need to identify and use thecontrol fields within each pricing element.

Task:You can view the various control fields in a pricing procedure, condition type, andan access sequence to learn what control is possible at this level.

1. How can you control whether or not a condition is determined duringautomatic pricing or whether or not the condition is entered manually?

2. How can you configure a condition type so that it can no longer be editedmanually in the document?

3. How can you configure a condition type during Customizing so that onlydiscount condition records and not those yielding surcharges can be entered?

4. Which access sequence is assigned to condition type PR00?

5. Which condition tables are used by access sequence PR02?

6. What is the difference between the second and third access in the accesssequence PR02?

2006/Q2 © 2005 SAP AG. All rights reserved. 61

Unit 2: Pricing Configuration SCM620

Solution 8: Controls in Pricing ElementsTask:You can view the various control fields in a pricing procedure, condition type, andan access sequence to learn what control is possible at this level.

1. How can you control whether or not a condition is determined duringautomatic pricing or whether or not the condition is entered manually?

a) In Customizing, when defining the pricing procedure, you can marka condition type as manual only (Man). As a result, the condition isnot determined automatically during pricing but can only be enteredmanually.

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define And Assign Pricing Procedures.

Choose Maintain pricing procedures.

Choose the standard pricing procedure RVAA01 and select the Controldata node in the overview tree.

2. How can you configure a condition type so that it can no longer be editedmanually in the document?

a) During Customizing, you can specify whether or not a condition typecan be edited manually in the Changes which can be made fields.

If theManual entries field is set to D, then the condition type cannot bemanually edited in the sales document.

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define Condition Types.

Choose Maintain Condition Types.

Select the K007 condition type and click the Details button to viewthe field.

3. How can you configure a condition type during Customizing so that onlydiscount condition records and not those yielding surcharges can be entered?

a) In Customizing for condition types, you can enter X in the Plus/minusfield to indicate that only discounts can be created with this conditiontype.

4. Which access sequence is assigned to condition type PR00?

a) In the details screen of condition type PR00, access sequence PR02 isassigned to condition type, PR00.

Continued on next page

62 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

5. Which condition tables are used by access sequence PR02?

a) Access sequence PR02 uses the condition tables, 305, 306, and 304.

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define Access Sequences.

Choose Maintain Access Sequences.

Select PR02 and choose the Accesses node in the overview tree.

6. What is the difference between the second and third access in the accesssequence PR02?

a) The document fields for the two accesses are different.

In access 20, the document currency WAERK is the source field for theaccess and in access 30, the document currency is the local currencyHWAER.

In addition, access 30 is performed only if there is a foreign currencydocument. This requirement (3) improves performance by eliminatingunnecessary accesses.

Select access 20 and double-click the Fields node to view thedocument fields. Repeat this process for access 30.

2006/Q2 © 2005 SAP AG. All rights reserved. 63

Unit 2: Pricing Configuration SCM620

64 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Exercise 9: Comprehensive PricingExercise

Exercise ObjectivesAfter completing this exercise, you will be able to:� Build and link all the pricing elements into a working pricing model

Business ExampleAfter you have explored each of the elements of the pricing condition technique,you will use these elements to create a working pricing model that includes a newfreight condition type.

Task:Your project team has been asked to create and test a complete pricing strategy forthe company. You need to create all the necessary pricing elements and ensurethat they function properly together. You need to complete this exercise beforetrying the exercises in later units.

1. Quick review of terms: Describe and give an example of the followingterms in your own words without using any of the written definitions. If youare working with a partner, explain these terms to them.

Condition table:

Access sequence:

Condition type:

Pricing procedure:

Condition records:

2. The design phase: You will be building a pricing strategy from the bottomup. Your management has asked you to implement a new freight charge,which will only be applicable to particular customers.

3. Condition table: Create and save a new condition table named 7##. Thistable can be created with reference to the condition table created earlier bythe instructor and should include the fields, sales organization, incoterms,and destination country. Include your group number in the name of thenew condition table.

4. Generate the table. If you see a warning stating that a table with the samefields already exists, click the Enter button to proceed. Use package Z001when prompted and save the table.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 65

Unit 2: Pricing Configuration SCM620

5. Access sequence: Create and save a new access sequence, ZA##, whichincludes your new condition table 7##.

Caution: When creating the access sequence, go to the Fields levelto generate it correctly. If you do not perform this step, the systemissues an error message, 301 fields missing for access sequence,during the pricing analysis.

6. Condition type: Create and save a new condition type, ZF##, by copyingcondition type KF00. Enter a description, which includes your groupnumber. Change the access sequence to ZA##.

7. Pricing procedure: Create and save a new pricing procedure called Z##PRCby copying the existing pricing procedure RVAA01.

8. Add your new condition type ZF## to your new pricing procedure Z##PRCby replacing the KF00 condition type with ZF##. Save the pricing procedure.

9. Creating a new customer pricing procedure key for your group: Fromthe table below, find your customer pricing procedure key and create an entryfor it in the Customer pricing procedure configuration table:

Group number CuPP value (customer pricingprocedure)

01 A02 B03 C04 D05 E06 F07 G08 H09 I10 J11 K12 L13 M14 N15 O16 P

Continued on next page

66 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

17 Q18 R19 S20 T

10. Pricing procedure determination: Modify the pricing proceduredetermination in Customizing to select your new pricing procedureautomatically. A new entry must be made for your sales area, the documentpricing procedure key A, and the customer pricing procedure key of yourgroup that you created earlier (see table above).

11. Changing your customer to use the new pricing procedure: For customerT-L67A##, change the customer pricing procedure key to the key that youcreated for your group earlier.

12. Condition records: Create and save a freight condition record using yourZF## condition type for sales organization 1000, incoterms EXW, anddestination country DE. The rate should be EUR 10 per KG.

13. Testing: From the customer purchase order shown below, create a standardorder:

TELEFAX

Customer: T-L67A##

PO number: ##-3-3

Requested delivery date: In one week

Material Quantity

T-AT1## 10

If the item condition screen does not show condition type ZF## with theproper values, analyze the problem using the Analysis button.

2006/Q2 © 2005 SAP AG. All rights reserved. 67

Unit 2: Pricing Configuration SCM620

Solution 9: Comprehensive PricingExerciseTask:Your project team has been asked to create and test a complete pricing strategy forthe company. You need to create all the necessary pricing elements and ensurethat they function properly together. You need to complete this exercise beforetrying the exercises in later units.

1. Quick review of terms: Describe and give an example of the followingterms in your own words without using any of the written definitions. If youare working with a partner, explain these terms to them.

Condition table:

Access sequence:

Condition type:

Pricing procedure:

Condition records:

a) Condition table: The definition of the key of the condition record.

Access sequence: A search strategy to locate the proper conditionrecord.

Condition types: A calculation or formula to calculate a componentof pricing.

Pricing procedure: A sequential list of condition types and subtotals.

Condition records: The data used by condition types to calculatepricing.

2. The design phase: You will be building a pricing strategy from the bottomup. Your management has asked you to implement a new freight charge,which will only be applicable to particular customers.

a)

Continued on next page

68 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

3. Condition table: Create and save a new condition table named 7##. Thistable can be created with reference to the condition table created earlier bythe instructor and should include the fields, sales organization, incoterms,and destination country. Include your group number in the name of thenew condition table.

a) To create condition table 7##,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define Condition Tables.

Choose Create condition tables.

Enter 7## in the Table field and the condition table number created bythe instructor in the Copy from condition field.

Select Validity period.

Choose Propose/Maintain text and enter a description including yourgroup number in the appropriate field.

Ensure that the Sales organization, Incoterms, and Destination countryfields are selected.

4. Generate the table. If you see a warning stating that a table with the samefields already exists, click the Enter button to proceed. Use package Z001when prompted and save the table.

a) Click the Generate button.

5. Access sequence: Create and save a new access sequence, ZA##, whichincludes your new condition table 7##.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 69

Unit 2: Pricing Configuration SCM620

Caution: When creating the access sequence, go to the Fields levelto generate it correctly. If you do not perform this step, the systemissues an error message, 301 fields missing for access sequence,during the pricing analysis.

a) To create the access sequence, ZA##,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define Access Sequences.

Choose Maintain Access Sequences.

Click the New Entries button.

Enter access sequence ZA## and a name for the access sequence. PressEnter.

Select your access sequence and choose the Accesses node in theoverview tree.

Click the New Entries button.

Enter access number 10 and table 7##. Press Enter.

Select your access and choose the Fields node in the overview tree.

Hint: If you see a warning stating that no field assignment hasbeen made, click the Enter button to proceed.

Save your entries.

6. Condition type: Create and save a new condition type, ZF##, by copyingcondition type KF00. Enter a description, which includes your groupnumber. Change the access sequence to ZA##.

a) To create the condition type, ZF##,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define Condition Types.

Choose Maintain Condition Types.

Select condition type KF00 and click the Copy as button.

On the next screen, change the condition type to ZF##, description toGroup ## Freight, and the access sequence to ZA##.

Click the Enter button to copy the new condition type.

Save the new condition type.

Continued on next page

70 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

7. Pricing procedure: Create and save a new pricing procedure called Z##PRCby copying the existing pricing procedure RVAA01.

a) To create the pricing procedure, Z##PRC,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define And AssignPricing Procedures.

Choose Maintain pricing procedures.

Select pricing procedure RVAA01 and click the Copy As button.

On the next screen, change the procedure to Z##PRC and thedescription to Group ## Procedure.

Click the Enter button.

On the next screen , click the copy all button.

8. Add your new condition type ZF## to your new pricing procedure Z##PRCby replacing the KF00 condition type with ZF##. Save the pricing procedure.

a) To insert the condition type ZF## in the pricing procedure Z##PRC,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define And AssignPricing Procedures.

Choose Maintain pricing procedures.

Select the pricing procedure Z##PRC and choose the Control datanode in the overview tree.

Place the pointer on line KF00 and overwrite KF00 with ZF##.

Save your pricing procedure.

9. Creating a new customer pricing procedure key for your group: Fromthe table below, find your customer pricing procedure key and create an entryfor it in the Customer pricing procedure configuration table:

Group number CuPP value (customer pricingprocedure)

01 A02 B03 C04 D05 E06 F

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 71

Unit 2: Pricing Configuration SCM620

07 G08 H09 I10 J11 K12 L13 M14 N15 O16 P17 Q18 R19 S20 T

a) To create customer pricing procedure keys,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define And AssignPricing Procedures.

Choose Define customer pricing procedures.

Click the New Entries button.

On the next screen, enter your customer pricing procedure key and adescription, GROUP ## CUPP.

Save your entries.

Continued on next page

72 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

10. Pricing procedure determination: Modify the pricing proceduredetermination in Customizing to select your new pricing procedureautomatically. A new entry must be made for your sales area, the documentpricing procedure key A, and the customer pricing procedure key of yourgroup that you created earlier (see table above).

a) To determine the pricing procedure,

select SAP Reference IMG→ Sales and Distribution→ BasicFunctions→ Pricing→ Pricing Control→ Define And AssignPricing Procedures.

Choose Define Pricing Procedure Determination.

Click the New Entries button.

On the next screen, enter the appropriate values and Z##PRC in thePricing procedure field. Enter PR00 in the Condition type field.

Save your entries.

11. Changing your customer to use the new pricing procedure: For customerT-L67A##, change the customer pricing procedure key to the key that youcreated for your group earlier.

a) To change the customer to use the new pricing procedure, select

Logistics→ Sales and Distribution→ Master Data→ BusinessPartner→ Customer→ Change→ Sales and Distribution.

Enter the customer number and the sales area.

Click the Continue button.

Choose Sales Area Data.

Change the Customer pricing procedure field to the value you createdearlier.

12. Condition records: Create and save a freight condition record using yourZF## condition type for sales organization 1000, incoterms EXW, anddestination country DE. The rate should be EUR 10 per KG.

a) To create condition records, select

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Select Using Condition Type→ Create.

Choose condition type ZF##.

Enter the appropriate values and save the condition record.

13. Testing: From the customer purchase order shown below, create a standardorder:

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 73

Unit 2: Pricing Configuration SCM620

TELEFAX

Customer: T-L67A##

PO number: ##-3-3

Requested delivery date: In one week

Material Quantity

T-AT1## 10

If the item condition screen does not show condition type ZF## with theproper values, analyze the problem using the Analysis button.

a) If the item condition screen does not show condition type ZF## withthe proper values, analyze the problem using the Analysis button.

74 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Customizing Pricing Components

Lesson Summary

You should now be able to:� Implement customizing settings for pricing

2006/Q2 © 2005 SAP AG. All rights reserved. 75

Unit Summary SCM620

Unit SummaryYou should now be able to:� Change and add to different pricing elements� Explain pricing configuration� Implement customizing settings for pricing

76 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. A contains the keys that are used to createdependent condition records.Fill in the blanks to complete the sentence.

2. An access sequence consists of only one condition table.Determine whether this statement is true or false.□ True□ False

3. Requirement and provide a method tomodify the standard pricing logic to meet unique user requirements.Fill in the blanks to complete the sentence.

4. New fields may be added to the pricing field catalog.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2005 SAP AG. All rights reserved. 77

Test Your Knowledge SCM620

Answers

1. A condition table contains the keys that are used to create dependentcondition records.

Answer: condition table

2. An access sequence consists of only one condition table.

Answer: False

An access sequence consists of one or more condition tables.

3. Requirement routines and formulas provide a method to modify the standardpricing logic to meet unique user requirements.

Answer: routines, formulas

4. New fields may be added to the pricing field catalog.

Answer: True

New fields may be added to the pricing field catalog. This allows you to usethe new field to define condition tables.

78 © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 3Working with Condition Records

Unit OverviewThis unit explains how to work with condition records. It provides an overview ofpricing reports and describes how to create, change, and copy condition records. Italso describes how to create net price lists and how to use the release procedurefor condition records.

Unit ObjectivesAfter completing this unit, you will be able to:

� Maintain conditions using pricing reports� Create, change, and copy condition records� Create net price lists� Use a condition index to find condition records� Use the release procedure for condition records

Unit ContentsLesson: Pricing Reports and Maintenance ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Exercise 10: Maintaining Conditions Using Pricing Reports... . . . . . . . . 91Exercise 11: Creating Condition Records with Reference ... . . . . . . . . . . 97Exercise 12: Mass Change for Conditions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Exercise 13: Copying Condition Records .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Exercise 14: Pricing Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

2006/Q2 © 2005 SAP AG. All rights reserved. 79

Unit 3: Working with Condition Records SCM620

Lesson: Pricing Reports and Maintenance

Lesson OverviewThis lesson provides an overview of pricing reports. It describes how to maintainconditions using pricing reports and how to create, change, and copy conditionrecords. It also describes how to create net price lists and how to use the releaseprocedure for condition records.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Maintain conditions using pricing reports� Create, change, and copy condition records� Create net price lists� Use a condition index to find condition records� Use the release procedure for condition records

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements. In addition to all other master data, the condition records of thedepartments must also be maintained. These tasks include changing prices,copying condition records, and creating pricing reports and net price lists.

80 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Pricing Reports

Figure 29: Pricing Reports � Customer-Specific Prices

To provide an overview of existing condition records, you can generate a list ofconditions for analysis. You might ask the following questions:

� What customer-specific price agreements are made within a certain period?� What Incoterm condition records are stored in the system?� What price lists are created with scale prices?

The layout of the lists and the condition records reported is set in Customizing.

2006/Q2 © 2005 SAP AG. All rights reserved. 81

Unit 3: Working with Condition Records SCM620

Figure 30: Pricing Reports � Tables

When creating a new program for pricing reports, you first decide the views inwhich you want to analyze the condition records. To do this, you need to selectspecific fields from the existing condition tables.

Depending on which fields are selected, the system generates a list of tables,which contain at least one of the selected fields. From this list of tables, you canselect specific tables that will appear in the report.

The list layout is specified by positioning and sorting the fields, which appear inthe selected tables in one of the three report sections:

� Page header � A page break occurs when a value changes.� Group header � A new line heading is generated for each table analyzed.� Items � Detailed record information is provided.

82 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Maintaining Condition Records

Figure 31: Maintaining Conditions Using Pricing Reports (1)

Condition maintenance has two maintenance interfaces.

The newer interface allows mass maintenance of conditions based oncharacteristics (e.g. for the customers).

This means that condition records can now be maintained across all conditiontypes and condition tables. You will, for example, be able to display and maintainthe material prices and the discounts and surcharges for a customer in one step.

You can also call up the classis maintenance transaction for conditions by choosingSelect using condition type. This means that only condition records of the typechosen can be maintained through this interface.

2006/Q2 © 2005 SAP AG. All rights reserved. 83

Unit 3: Working with Condition Records SCM620

Figure 32: Maintaining Conditions Using Pricing Reports (2)

The newer condition maintenance function can be configured using area menus.

The standard area menu for condition maintenance is COND_AV.

A user-specific area menu can be assigned by selecting Environment →Assignment Area Menu.

These user-specific area menus can be created using transaction SE43, forexample, by copying the user menu, COND_AV, and changing it to meet specificrequirements.

84 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Figure 33: Creating Condition Records with Reference

New condition records can be created with reference to existing condition records.

During the process, changes can be made to the rate, validity period, and additionalsales data in the newly created records.

This function provides an efficient method to update condition recordssimultaneously.

Figure 34: Change Condition Records

Individual condition records can be maintained manually.

The price change function allows you to maintain multiple condition recordssimultaneously.

Use the change documents to review and monitor changes made to the conditionrecords.

2006/Q2 © 2005 SAP AG. All rights reserved. 85

Unit 3: Working with Condition Records SCM620

Figure 35: Copying Condition Records

Multiple condition records can be created by copying an existing condition record.

When copying a condition record, you may select from a range of copying rules.If, for example, you are copying a customer-specific price condition record, thestandard system provides the following options:

� Create the target conditions over a specified range of customer numbers.� Create the target conditions over a specified range of material numbers.

Copying rules are maintained in Customizing and you may create your owncopying rules.

Long Texts in Condition Records

� Can be maintained for condition records� Can be maintained for agreements

� Promotion� Sales deal� Rebate agreements

You can maintain long texts in the condition records for pricing and agreements,such as rebates, sales deals, and promotions.

These provide information about:

� Creating condition records� Approvals� Invalidity

86 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

If required, long texts in the rebate agreement can be copied to the documents. Forexample, long text can be copied to the credit memo request for rebate paymentsand then to the rebate credit memo.

However, text control customizing offers no possibility to copy the long textsfrom condition records to the documents.

Text is not copied when you create condition records with reference.

Net Price List

Figure 36: Net Price List

The net price list provides an option to create price information for a customer ona selected quantity of materials.

The net prices are determined by simulating a billing document.

The list is displayed using the ABAP list viewer. For that reason it is easy for youto create customer-specific display variants. All the fields in the VBRP tableare available for this purpose.

2006/Q2 © 2005 SAP AG. All rights reserved. 87

Unit 3: Working with Condition Records SCM620

Condition Indices

Figure 37: Condition Indices

You can create and use condition indices to search for condition records that werecreated for a variety of condition types and condition tables.

For example, you can view all the condition records that apply to a particularcustomer or product.

The activation function displays a list of all the available condition indices andindicates which indices are active. The system can use a condition index onlywhen it is activated.

Before you can use the indices that are delivered in the standard version, you mustfirst activate the indices in Customizing for sales.

If you create your own indices, the system automatically activates each new indexwhen you generate it. In addition, you must specify an update requirement foreach condition index.

You can configure for each condition type whether or not the system updatesthe condition indices when you post the condition records for the correspondingcondition type.

88 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Release Procedure

Figure 38: Release Procedure for Conditions

You can allow a release procedure to be used when a condition table is createdby selecting the With release status checkbox. This adds the following fieldsto the condition table automatically:

� KFRST: Release status as last key field� KBSTAT: Processing status as a field of the variable data part (non-key field)

The release status is predefined. At present the following status are defined:

� Released� Blocked� Released for price simulation (net price list)� Released for planning and price simulation (planning in CO-PA)

The release status is set indirectly by defining a processing status in Customizingfor pricing and assigning a release status to the processing status.

Business Transaction Event00503303 Maintain Conditions: Transfers areavailable to define individual processing logic for the processing status.

2006/Q2 © 2005 SAP AG. All rights reserved. 89

Unit 3: Working with Condition Records SCM620

Calculation Type

Figure 39: Changeable Calculation Types

The calculation type for a condition type is defined in Customizing. Thiscalculation type determines how prices or discounts and surcharges are calculatedfor a condition.

When creating new condition records, you can select a calculation type that differsfrom the one set in Customizing.

90 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Exercise 10: Maintaining Conditions UsingPricing Reports

Exercise ObjectivesAfter completing this exercise, you will be able to:� Adjust the condition maintenance to suit individual user needs via pricing

reports with configurable area menus

Business ExampleTo simplify the condition maintenance for certain groups of customers, providecolleagues involved with an area menu, which allows them to maintain allconditions for the selected customers at once �at the touch of a button�.

Task:The default area menu for condition maintenance via pricing reports is area menuCOND_AV. You will add your own nodes to the overview tree at the user levelin this area menu.

1. Determine first which pricing report is assigned to the Conditions→ Bycustomer node in the COND_AV area menu.

Hint: You can maintain area menus by choosing:

Tools→ ABAP Workbench→ Development→ Other Tools→Area Menus.

2. Create a variant called �Customer ##� for the report found and enter thefollowing selection data in its selection screen:

Sales organization 1000DistrChannel 10Customer number T-L67A## and T-L67B##

Hint: You can create variants in Reporting.

(System→ Services→ Reporting)

3. Create your own area menu called ZZCOND_## with the descriptionCustomer group ##.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 91

Unit 3: Working with Condition Records SCM620

Insert a My customers node to which you will assign the variants created inactivity 1-1-2 for the pricing report in activity 1-1-1.

Save your area menu as a local object.

4. Assign the area menu ZZCOND_## that you just created to your userSCM620-##.

Hint: You can assign the area menu by maintaining the conditionsand by choosing

Environment→ Assignment Area Menu.

Note: A newly assigned area menu only takes effect when youreturn to the SAP Easy Access overview tree and call up conditionmaintenance again.

5. The standard area menu for maintaining conditions is no longer displayed.To make this and your own area menu available, you must also assign areamenu COND_AV to your user, SCM620-##.

Hint: If you are assigning several area menus, you can use theNumber field to control the display order.

92 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Solution 10: Maintaining Conditions UsingPricing ReportsTask:The default area menu for condition maintenance via pricing reports is area menuCOND_AV. You will add your own nodes to the overview tree at the user levelin this area menu.

1. Determine first which pricing report is assigned to the Conditions→ Bycustomer node in the COND_AV area menu.

Hint: You can maintain area menus by choosing:

Tools→ ABAP Workbench→ Development→ Other Tools→Area Menus.

a) Assigned pricing report: /1SDBF12L/RV14AK28

Tools→ ABAP Workbench→ Development→ Other Tools→ AreaMenus.

Enter COND_AV in the Area menu field.

Click the Display Area Menu button.

Select the node Conditions→ By Customer.

Choose Execute Transaction (F8).

Choose System→ Status.

You will find the name of the pricing report in the field Report.

2. Create a variant called �Customer ##� for the report found and enter thefollowing selection data in its selection screen:

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 93

Unit 3: Working with Condition Records SCM620

Sales organization 1000DistrChannel 10Customer number T-L67A## and T-L67B##

Hint: You can create variants in Reporting.

(System→ Services→ Reporting)

a) Creating variants:

System→ Services→ Reporting.

Enter in the Program field: /1SDBF12L/RV14AK28

Choose Goto→ Variants.

Enter in the Variants field: Customer ##.

Choose Create.

Enter the selection data and save the variant.

3. Create your own area menu called ZZCOND_## with the descriptionCustomer group ##.

Insert a My customers node to which you will assign the variants created inactivity 1-1-2 for the pricing report in activity 1-1-1.

Save your area menu as a local object.

a) Creating area menus:

Tools→ ABAP Workbench→ Development→ Other Tools→ AreaMenus.

Enter in the Area menu field: ZZCOND_##.

Choose Create.

Enter the description: Customer Group ##.

Select the Customer Group ## node.

Choose:

Edit→ Insert menu Entry→ Insert as Subnode.

Choose Add report.

Enter in the Report field: /1SDBF12L/RV14AK28.

Choose in the Variant field: Customer ##.

Save your entry as a local object.

Continued on next page

94 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

4. Assign the area menu ZZCOND_## that you just created to your userSCM620-##.

Hint: You can assign the area menu by maintaining the conditionsand by choosing

Environment→ Assignment Area Menu.

Note: A newly assigned area menu only takes effect when youreturn to the SAP Easy Access overview tree and call up conditionmaintenance again.

a) Assigning area menus:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Change.

Choose: Environment→ Assign Area Menu.

Click the New Entries button

Enter your area menu: ZZCOND_##

Save your entry.

5. The standard area menu for maintaining conditions is no longer displayed.To make this and your own area menu available, you must also assign areamenu COND_AV to your user, SCM620-##.

Hint: If you are assigning several area menus, you can use theNumber field to control the display order.

a) Assigning additional standard area menus:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Change.

Choose: Environment→ Assign Area Menu.

Click the New Entries button.

Enter: COND_AV

Save your entry.

2006/Q2 © 2005 SAP AG. All rights reserved. 95

Unit 3: Working with Condition Records SCM620

96 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Exercise 11: Creating Condition Recordswith Reference

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create condition records for new validity periods on the basis of existing

condition records

Business ExampleIn many cases, entire groups of prices expire after a certain time, with the resultthat new records must be created to replace them. You will learn how to create newcondition records with validity dates in the future that can be used automatically atthe start of the validity period.

Task:In preparation for a new pricing strategy, which will take effect next year, you willcreate a new pricing condition from existing records.

1. Create a new pricing condition with reference to the material price conditionrecords for material T-AT2## and material T-AT3##. Change the validityperiod for the new records to be for 1 year, beginning January of next year.

2006/Q2 © 2005 SAP AG. All rights reserved. 97

Unit 3: Working with Condition Records SCM620

Solution 11: Creating Condition Recordswith ReferenceTask:In preparation for a new pricing strategy, which will take effect next year, you willcreate a new pricing condition from existing records.

1. Create a new pricing condition with reference to the material price conditionrecords for material T-AT2## and material T-AT3##. Change the validityperiod for the new records to be for 1 year, beginning January of next year.

a) Creating condition records with reference:

Logistics→ Sales and Distribution→Master Data→ Conditions→Create with Template→ Prices→ Material Price.

Enter the appropriate values for the reference conditions by choosingthe Multiple selection button.

Click the Copy button at the bottom of the pop up screen and thenclick Execute.

Select the condition records.

Choose Change validity.

Change the validity period to start next January for a duration of 1 year.

Choose Copy date.

Save the new condition records.

98 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Exercise 12: Mass Change for Conditions

Exercise ObjectivesAfter completing this exercise, you will be able to:� Change multiple condition records simultaneously

Business ExampleChanging several condition rates simultaneously is a practical and efficient way tomanage condition records. You will be testing this function while implementingpricing.

Task:Using the price change function, you can implement a price increase for the newcondition records created earlier.

1. Select the condition records created earlier and increase the price by 5%.Save the changed records.

2. Display the corresponding changed documents.

2006/Q2 © 2005 SAP AG. All rights reserved. 99

Unit 3: Working with Condition Records SCM620

Solution 12: Mass Change for ConditionsTask:Using the price change function, you can implement a price increase for the newcondition records created earlier.

1. Select the condition records created earlier and increase the price by 5%.Save the changed records.

a) To increase the price by 5%, select

Logistics→ Sales and Distribution→Master Data→ Conditions→Change→ Prices→ Material Price.

Enter the appropriate values to select material 2 and material 3.

Ensure that the date in the Valid on field falls within the validity periodduring which you want to execute the price increase.

Choose Execute.

Select the condition records.

Choose Change amount.

Enter 5 in the Percentage field and choose Copy.

Return to the previous screen and save the changed records.

2. Display the corresponding changed documents.

a) To display the changed documents, select

Logistics→ Sales and Distribution→Master Data→ Conditions→Change→ Prices→ Material Price.

Enter the appropriate values to select material 2 and material 3.

Choose Execute.

Select the displayed records and select.

Environment→ Changes→ Per Condition Record.

The display shows the author of the condition record and the date ofcreation. You can use the OldVal and NewVal columns to see the beforeand after values.

100 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Exercise 13: Copying Condition Records

Exercise ObjectivesAfter completing this exercise, you will be able to:� Practice copying one condition record to another with different key values

Business ExampleOccasionally, you may need to create several new condition records using onerecord as the source. This saves time and helps eliminate mistakes.

Task:You will now copy one of your condition records using two different strategies.

1. Copy the customer-specific pricing condition for customer T-L67A## andmaterial T-AT1## to a new record for customer T-L67B## and materialT-AT1##. Save the condition record.

2006/Q2 © 2005 SAP AG. All rights reserved. 101

Unit 3: Working with Condition Records SCM620

Solution 13: Copying Condition RecordsTask:You will now copy one of your condition records using two different strategies.

1. Copy the customer-specific pricing condition for customer T-L67A## andmaterial T-AT1## to a new record for customer T-L67B## and materialT-AT1##. Save the condition record.

a) To copy the condition records, select

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Change→ Prices→ Individual Prices.

Enter the appropriate data to select the key combination of CustomerT-L67A## and Material T-AT1##. Choose Execute.

Select the condition line and choose Select Rule.

Select rule 1 and choose Continue.

Enter customer T-L67B## as the target customer on the next screen.

Remove flag Display listat the bottom of the selection screen.

Choose Execute.

Save the condition records.

102 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Exercise 14: Pricing Reports

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use pricing reports to produce a list of specific condition records

Business ExampleBeing able to manage the large number of condition records, as business typicallyrequires, needs easy-to-use reporting tools. The pricing reports provided in SAPR/3 cover most reporting requirements. Additionally, more tailored reports areeasily developed.

Task:You will use a standard pricing report to gain experience with this reportingfunction. Additionally, you may create your own pricing report tailored to yourspecific requirements.

1. Using the pricing report function, create a list of all currently validcustomer-specific prices for customer T-L67A## (use list report 16).

2. Create your own pricing report, entitled �Group ## Pricing Report�. Thefollowing table contains the short name of your list report:

Group number List report01 C102 C203 C304 C405 C506 C607 C708 C809 C910 C011 D112 D213 D3

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 103

Unit 3: Working with Condition Records SCM620

14 D415 D516 D617 D718 D819 D920 D0

Your report should list condition records, which contain the fields Customer,Material or Sales Organization. Select at least tables 304, 305, and 007to appear on your report. Position the fields and select formatting optionsas desired.

3. Run your report for customer T-L67A##.

104 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Solution 14: Pricing ReportsTask:You will use a standard pricing report to gain experience with this reportingfunction. Additionally, you may create your own pricing report tailored to yourspecific requirements.

1. Using the pricing report function, create a list of all currently validcustomer-specific prices for customer T-L67A## (use list report 16).

a) Executing pricing reports:

Logistics→ Sales and Distribution→Master Data→ Conditions→List→ Pricing Report.

Enter 16 in the Pricing Report field and choose Execute.

Specify your customer. Leave all other fields blank.

Choose Execute.

2. Create your own pricing report, entitled �Group ## Pricing Report�. Thefollowing table contains the short name of your list report:

Group number List report01 C102 C203 C304 C405 C506 C607 C708 C809 C910 C011 D112 D213 D314 D415 D516 D6

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 105

Unit 3: Working with Condition Records SCM620

17 D718 D819 D920 D0

Your report should list condition records, which contain the fields Customer,Material or Sales Organization. Select at least tables 304, 305, and 007to appear on your report. Position the fields and select formatting optionsas desired.

a) Creating your own pricing report:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→Maintain Pricing Report→ Create Pricing Report.

Enter the short description and the title of your pricing report andchoose Enter.

Select the fields Customer number, Material number, and Salesorganization.

Choose tables that contain at least one selected field.

Select tables 304, 305, and 007 from the list (ensure that the list is notsorted according to table numbers!).

Choose Continue to list structure.

Use the Position column to place each field in the Page header, Groupheader or Item level of the report. Use the Sort field to sequence eachgroup of fields as desired. Use the Text field to choose if the descriptionof the item should be shown in addition to the key.

From the Default values for the selection screen, choose the additionaloptions that you want to include.

When finished, save your report definition.

The name generated for the pricing report is /1SDBF12L/RV14AKxx.

3. Run your report for customer T-L67A##.

a) Executing pricing reports:

Logistics→ Sales and Distribution→Master Data→ Conditions→List→ Pricing Report.

Enter your short description in the table in the Pricing Report fieldand choose Execute.

Specify customer T-L67A##. Leave all other fields blank.

Choose Execute.

106 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Reports and Maintenance

Lesson Summary

You should now be able to:� Maintain conditions using pricing reports� Create, change, and copy condition records� Create net price lists� Use a condition index to find condition records� Use the release procedure for condition records

2006/Q2 © 2005 SAP AG. All rights reserved. 107

Unit Summary SCM620

Unit SummaryYou should now be able to:� Maintain conditions using pricing reports� Create, change, and copy condition records� Create net price lists� Use a condition index to find condition records� Use the release procedure for condition records

108 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. The release status is set indirectly by defining a release procedure inCustomizing for pricing and assigning a release status to it.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2005 SAP AG. All rights reserved. 109

Test Your Knowledge SCM620

Answers

1. The release status is set indirectly by defining a release procedure inCustomizing for pricing and assigning a release status to it.

Answer: False

The release status is set indirectly by defining a processing status inCustomizing for pricing and assigning a release status to it.

110 © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 4Special Functions

Unit OverviewThis unit provides an overview of special functions. It describes the use of groupconditions and condition supplements. It explains how to compare condition typesand how to use condition update. In addition, it explains hierarchy accesses andthe techniques of data determination in access.

Unit ObjectivesAfter completing this unit, you will be able to:

� Use group conditions to carry out pricing for several items in an order� Compare condition types with several methods and outcomes� Set conditions for a maximum value, quantity, or number of orders� Describe how and when to use condition supplements� Optimize pricing for hierarchical data constellations using hierarchy accesses� Explain the techniques of data determination in access using the price book

as an example

Unit ContentsLesson: Special Pricing Functions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Exercise 15: Creative Use of Condition Type Attributes .. . . . . . . . . . . . .119Exercise 16: Exclusion Groups .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125Exercise 17: Updating Conditions � Tracking Cumulative Values .. .129

Lesson: Hierarchy Pricing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Lesson: Data Determination in Access .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

2006/Q2 © 2005 SAP AG. All rights reserved. 111

Unit 4: Special Functions SCM620

Lesson: Special Pricing Functions

Lesson OverviewThis lesson describes how to use group conditions to carry out pricing for severalitems in an order. It also explains how to compare condition types and how touse condition update. In addition, it explains how and when to use conditionsupplements.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Use group conditions to carry out pricing for several items in an order� Compare condition types with several methods and outcomes� Set conditions for a maximum value, quantity, or number of orders� Describe how and when to use condition supplements

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements.

In addition to the basic pricing elements, you need to use special functions thatallow dependencies between condition types or groups of condition types to bemapped and cumulative values in selected condition records to be updated.

112 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Group Conditions

Figure 40: Group Conditions

In Customizing, you can set a condition type to be a group condition. Thecondition base value, such as weight, is then calculated as the sum of the individualitems within a group.

Figure 41: Group Conditions with Varying Keys

For group conditions with varying keys, item quantities are accumulated forscale point determination purposes but the rate for each item is calculated fromits individual condition record.

Control data: Entry for condition type

2006/Q2 © 2005 SAP AG. All rights reserved. 113

Unit 4: Special Functions SCM620

Group condition: X

Unit of measure for accumulation, e.g. pieces

GrpCond.routine: 1, 2, or 3 (see explanation below)

� 1. Complete document:

Formula �1� adds up the quantities / values of all of the line items in thesales document that have the same condition type as the group conditioncurrently being processed.

� 2. Across all condition types:

Formula �2� adds up the quantities / values of all of the line items in the salesdocument independent of which condition types have been applied.

� 3. Material pricing group:

Formula �3� adds up the quantities / values of all of the line items in the salesdocument that have the same material pricing group (field KONDM) asthe current sales document line item.

Excluding Conditions

Figure 42: Excluding Conditions

Conditions can be linked to requirements in the pricing procedure.

A requirement can evaluate the condition exclusion indicator and ignore thecondition if the indicator is set.

114 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

The condition exclusion indicator can be set in either the condition type or thecondition record.

You may create your own exclusion indicators and test for the existence of theindicator in the requirement routines.

Comparing Condition Types

Figure 43: Determining the Best Price Using Condition Exclusion

Condition types to be compared are first placed in an exclusion group.

During pricing, the conditions, which result in the best price (lowest charge orhighest discount) are selected from this group. All other conditions are deactivated.

2006/Q2 © 2005 SAP AG. All rights reserved. 115

Unit 4: Special Functions SCM620

There are several comparison methods which may be used:

� A: All conditions found within the first exclusion group are compared and thecondition with the best price is chosen. All other conditions are deactivated.

� B: All condition records found for one condition are compared. The bestprice is chosen. All other conditions are deactivated. This method can beused with condition type PR00.

� C: The total of condition records found in the first exclusion group iscompared to the total of condition records found in the second exclusiongroup. The group that calculates the best price is chosen. The conditionsof the other groups are deactivated.

� D: If a condition record is determined for the condition types of the firstexclusion group, all the condition records for the second exclusion groupare deactivated.

� E: Similar to method B, except that the worst (highest charge or lowestdiscount) price is chosen.

� F: Similar to method C, except that the group with the worst overall price ischosen. The conditions of the other group are deactivated.

Condition Update

Figure 44: Updating Conditions � Tracking Cumulative Values

Values can be accumulated in condition records and tested against limits. In thisway, you can set a maximum condition value, condition base value, or number oforders for a condition.

The cumulative values in the condition record can be displayed.

116 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Condition Supplements

Figure 45: Condition Supplements

Condition supplements do not have their own access sequence. They are foundtogether with the underlying condition record.

2006/Q2 © 2005 SAP AG. All rights reserved. 117

Unit 4: Special Functions SCM620

118 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Exercise 15: Creative Use of ConditionType Attributes

Exercise ObjectivesAfter completing this exercise, you will be able to:� Solve pricing problems by combining various condition type attributes

Business ExampleCertain pricing requirements can be met by combining a few standardconfiguration settings. You will be presented with a new pricing scenario for yourcompany. You need to analyze and solve the problems in this pricing scenario.

Task:Your company has signed an agreement with a new carrier, Walldorf Parcel. Theywill be your carrier of choice for all orders weighing 30 kg or less. All ordersexceeding 30 kg will continue to have freight calculated using the ZF## conditiontype. The proper determination of the freight should happen automatically.

This requires changes in the pricing model you constructed in the previousexercises.

1. Configure a new condition type ZW## to calculate the freight for WalldorfParcel. You can use ZA## as the access sequence for this condition type. Inaddition you need to add together the gross weight of all the order items andhandle the following scale in the condition type:

from 0 kg 8 EUR0,5 kg 10 EUR1 kg 12 EUR2 kg 14 EUR5 kg 16 EUR10 kg 20 EUR20 kg 30 EUR

up to a maximum weight of 30 kg.

2. Add the new condition type to your pricing procedure Z##PRC immediatelybefore condition type ZF## (freight).

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 119

Unit 4: Special Functions SCM620

3. Create a condition record for the ZW## condition type for your salesorganization, incoterms EXW, and destination country DE. Use the scalevalues shown before. Save the condition record.

4. To test the new condition, enter an order from the customer purchase ordershown below. Check the header and item pricing to ensure that ZW## iscalculated properly. At this point, you should see both the conditions ZW##and ZF## in the order. Save the order.

Hint: Note that at present � depending on your procedures � thetest can still be correct if both condition types ZW## and ZF##are effective

TELEFAX

Customer: T-L67A##

PO number: ##-5-1

Requested delivery date: In one week

Material Quantity

T-AT1## 2

T-AT3## 1

120 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Solution 15: Creative Use of ConditionType AttributesTask:Your company has signed an agreement with a new carrier, Walldorf Parcel. Theywill be your carrier of choice for all orders weighing 30 kg or less. All ordersexceeding 30 kg will continue to have freight calculated using the ZF## conditiontype. The proper determination of the freight should happen automatically.

This requires changes in the pricing model you constructed in the previousexercises.

1. Configure a new condition type ZW## to calculate the freight for WalldorfParcel. You can use ZA## as the access sequence for this condition type. Inaddition you need to add together the gross weight of all the order items andhandle the following scale in the condition type:

from 0 kg 8 EUR0,5 kg 10 EUR1 kg 12 EUR2 kg 14 EUR5 kg 16 EUR10 kg 20 EUR20 kg 30 EUR

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 121

Unit 4: Special Functions SCM620

up to a maximum weight of 30 kg.

a) Condition type ZW##:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Pricing Control→ Define Condition Types.

Choose Maintain Condition Types.

Select condition type KF00 and click the Copy As button.

On the next screen, change the condition type to ZW##, and thedescription to Group ## Parcel, Ensure that the access sequence of thecondition type is ZA##.

Click the Enter button to copy the new condition type.

In order to use the values in the scale properly, the Calculation typemust be set to B, Fixed amount.

Because you will be adding the gross weight of all items, the conditiontype must be set as a group condition with the Scale base type D,Gross weight.

To test for the maximum weight of 30 kg, the condition record musthave a final line in the scale section of:

From 30,001 kg 0 EUR.

To allow this type of scale which is first ascending, and thendescending, leave the Check value field in the ZW## condition type toblank (scale rates are not checked).

Save the new condition type.

2. Add the new condition type to your pricing procedure Z##PRC immediatelybefore condition type ZF## (freight).

a) In your pricing procedure Z##PRC, click the New Entries button toinsert a new line. Choose Step and Counter values, which will placethe new line immediately before condition type ZF##. Enter the samevalues for the requirements and other fields that you find for conditiontype ZF##.

Continued on next page

122 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

3. Create a condition record for the ZW## condition type for your salesorganization, incoterms EXW, and destination country DE. Use the scalevalues shown before. Save the condition record.

a) To create condition records, select:

Logistics→ Sales and Distribution→ Master Data→ Conditions→ Select Using Condition Type→ Create..

Choose condition type ZW##.

Enter the appropriate values and save the condition record.

4. To test the new condition, enter an order from the customer purchase ordershown below. Check the header and item pricing to ensure that ZW## iscalculated properly. At this point, you should see both the conditions ZW##and ZF## in the order. Save the order.

Hint: Note that at present � depending on your procedures � thetest can still be correct if both condition types ZW## and ZF##are effective

TELEFAX

Customer: T-L67A##

PO number: ##-5-1

Requested delivery date: In one week

Material Quantity

T-AT1## 2

T-AT3## 1

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 123

Unit 4: Special Functions SCM620

124 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Exercise 16: Exclusion Groups

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use condition exclusion for groups of conditions

Business ExampleExclusion groups allow you to compare the results of pricing calculations andtake appropriate pricing actions. You will test the use of exclusion groups for thenew freight pricing strategy.

Task:Only one of the two possible freight conditions should be used on an order. Oneway to accomplish this is to use exclusion groups.

1. In the IMG, create and save two new exclusion groups, Z1## and Z2##.

2. Assign condition type ZW## to exclusion group Z1##. Assign conditiontype ZF## to exclusion group Z2##.

3. Assign these exclusion groups to your pricing procedure Z##PRC. Use acomparison type that will deactivate group Z2## if the condition type ingroup Z1## is found.

4. Test your new freight pricing strategy by creating an order from the customerpurchase order shown below. Vary the quantities to test both the ZW## andthe ZF## conditions.

TELEFAX

Customer: T-L67A##

PO number: ##-5-2

Requested delivery date: In one week

Material Quantity

T-AT1## 2

T-AT3## 1

Hint: You can simplify testing by checking whether or not thecondition screen of the header data is functioning properly.

5. Instead of exclusion groups, what alternative methods could have been usedin this condition to accomplish the same purpose?

2006/Q2 © 2005 SAP AG. All rights reserved. 125

Unit 4: Special Functions SCM620

Solution 16: Exclusion GroupsTask:Only one of the two possible freight conditions should be used on an order. Oneway to accomplish this is to use exclusion groups.

1. In the IMG, create and save two new exclusion groups, Z1## and Z2##.

a) To create exclusion groups, select:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Condition Exclusion→ Condition Exclusion For GroupsOf Conditions.

Choose Define Condition Exclusion Groups.

Click New Entries to add exclusion groups, Z1## and Z2##.

Save your entries.

2. Assign condition type ZW## to exclusion group Z1##. Assign conditiontype ZF## to exclusion group Z2##.

a) To assign condition types to the exclusion groups, select:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Condition Exclusion→ Condition Exclusion For GroupsOf Conditions.

Choose Assign condition types to the exclusion groups.

Click New Entries to add assignments of condition type ZW## toexclusion group Z1## and condition type ZF## to exclusion groupZ2##.

Save your entries.

Continued on next page

126 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

3. Assign these exclusion groups to your pricing procedure Z##PRC. Use acomparison type that will deactivate group Z2## if the condition type ingroup Z1## is found.

a) To assign exclusion groups to the pricing procedure, select:

SAP Reference IMG→ Sales and Distribution→ Basic Functions→Pricing→ Condition Exclusion→ Condition Exclusion For GroupsOf Conditions.

Choose Maintain condition exclusion for pricing procedures.

Select your pricing procedure Z##PRC and double-click the Exclusionnode in the overview tree.

Click New Entries to add the necessary entries. Use a sequence numberof 10, a condition exclusion procedure of D, an exclusion group 1 valueof Z1##, and an exclusion group 2 value of Z2##.

Save your entries.

4. Test your new freight pricing strategy by creating an order from the customerpurchase order shown below. Vary the quantities to test both the ZW## andthe ZF## conditions.

TELEFAX

Customer: T-L67A##

PO number: ##-5-2

Requested delivery date: In one week

Material Quantity

T-AT1## 2

T-AT3## 1

Hint: You can simplify testing by checking whether or not thecondition screen of the header data is functioning properly.

a) Test result:

If the weight of all the items is 30 kg or less, ZW## should be an activecondition. When the combined weight of both the items exceeds 30 kg,ZF## should be an active freight condition.

For the test to function correctly, condition type ZF## must also bemarked as a group condition.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 127

Unit 4: Special Functions SCM620

5. Instead of exclusion groups, what alternative methods could have been usedin this condition to accomplish the same purpose?

a) Alternative procedures:

The condition record for ZF## could use a scale that starts at 30,001 kg.

Similarly, a new exclusion indicator could possibly be created andused on the ZW## and ZF## conditions. A new pricing procedurerequirement would have to be created to check for the existence of thisnew exclusion indicator.

128 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Exercise 17: Updating Conditions �Tracking Cumulative Values

Exercise ObjectivesAfter completing this exercise, you will be able to:� Verify that cumulative conditions handle special pricing situations correctly

Business ExampleSome of your pricing conditions are only good for the first order, or for a specifiedquantity of material. Using the condition update function for cumulative conditionrecords, you will test this function.

Task:Marketing has implemented a new customer/material discount, which is onlygood for the first order.

1.

Hint: Make sure that the instructor has activated the conditionupdate function for condition type K005 before you begin theexercise.

Create a K005 customer/material discount record for customerT-L67B## and material T-AT2## and a rate of EUR 100 whenbuying from your sales organization and distribution channel. Usethe defaults for the validity period.

2. Change the K005 discount record so that it will only be valid for the nextorder. Save the changes.

3. From the customer purchase orders shown below, create two standard salesorders. Do not create the second order with reference to the first. Enter eachorder separately. Save each order.

TELEFAX

Customer: T-L67B##

PO number: ##-5-3a

Requested delivery date: In one week

Material Quantity

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 129

Unit 4: Special Functions SCM620

T-AT2## 10

Hint: When creating the following order, do not Create withreference to the first order because it will "inherit" the conditions.

TELEFAX

Customer: T-L67B##

PO number: ##-5-3b

Requested delivery date: In one week

Material Quantity

T-AT2## 10

4. Is the customer discount K005 used on the second order?

5. In the IMG, what setting is required in the condition type to enable thesystem to retain accumulated amounts? Use condition type K005 todetermine your answer.

6. Change your condition record for condition type K005 so that it is onlyactive for the first 15 pieces of material 2.

7. From the customer purchase order shown below, create a standard sales order.

TELEFAX

Customer: T-L67B##

PO number: #-5-3-7

Requested delivery date: In one week

Material Quantity

T-AT2## 15

8. Examine the item pricing and determine how many of the pieces receivedthe K005 discount. Why?

130 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Solution 17: Updating Conditions �Tracking Cumulative ValuesTask:Marketing has implemented a new customer/material discount, which is onlygood for the first order.

1.

Hint: Make sure that the instructor has activated the conditionupdate function for condition type K005 before you begin theexercise.

Create a K005 customer/material discount record for customerT-L67B## and material T-AT2## and a rate of EUR 100 whenbuying from your sales organization and distribution channel. Usethe defaults for the validity period.

a) Creating a condition record:

Logistics→ Sales and Distribution→Master Data→ Conditions→Create→ Discounts/Surcharges→ By Customer/Material.

Choose condition type K005.

Enter the appropriate values and save the condition record.

2. Change the K005 discount record so that it will only be valid for the nextorder. Save the changes.

a) Changing a condition record:

Logistics→ Sales and Distribution→Master Data→ Conditions→Change→ Discounts/Surcharges→ By Customer/Material.

Choose Execute.

Enter the value 1 in the Number of orders field.

Save the condition record.

3. From the customer purchase orders shown below, create two standard salesorders. Do not create the second order with reference to the first. Enter eachorder separately. Save each order.

TELEFAX

Customer: T-L67B##

PO number: ##-5-3a

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 131

Unit 4: Special Functions SCM620

Requested delivery date: In one week

Material Quantity

T-AT2## 10

Hint: When creating the following order, do not Create withreference to the first order because it will "inherit" the conditions.

TELEFAX

Customer: T-L67B##

PO number: ##-5-3b

Requested delivery date: In one week

Material Quantity

T-AT2## 10

a)

4. Is the customer discount K005 used on the second order?

a) The second order does not include the K005 discount since it wasvalid for only one order.

5. In the IMG, what setting is required in the condition type to enable thesystem to retain accumulated amounts? Use condition type K005 todetermine your answer.

a) The Condition update indicator must be set.

6. Change your condition record for condition type K005 so that it is onlyactive for the first 15 pieces of material 2.

a) Changing a condition record:

Logistics→ Sales and Distribution→Master Data→ Conditions→Change→ Discounts/Surcharges→ By Customer/Material.

Choose Execute.

Enter the value 15 in the MaxCondBaseVal. field and leave the Numberof orders field blank.

Save the condition record.

7. From the customer purchase order shown below, create a standard sales order.

TELEFAX

Customer: T-L67B##

PO number: #-5-3-7Continued on next page

132 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Pricing Functions

Requested delivery date: In one week

Material Quantity

T-AT2## 15

a)

8. Examine the item pricing and determine how many of the pieces receivedthe K005 discount. Why?

a) Only a quantity of 5 received the K005 discount because the conditionrecord already had a cumulative value of 10 pieces from the first orderin exercise 1-3-3.

2006/Q2 © 2005 SAP AG. All rights reserved. 133

Unit 4: Special Functions SCM620

Lesson Summary

You should now be able to:� Use group conditions to carry out pricing for several items in an order� Compare condition types with several methods and outcomes� Set conditions for a maximum value, quantity, or number of orders� Describe how and when to use condition supplements

134 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Hierarchy Pricing

Lesson: Hierarchy Pricing

Lesson OverviewThis lesson provides an overview of hierarchy accesses. It explains how tooptimize pricing for hierarchical data constellations.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Optimize pricing for hierarchical data constellations using hierarchy accesses

Business ExampleYour company produces consumer goods. The project team that implements theSAP system must meet the company�s pricing requirements. As a member of theproject team, you have been given the task of examining the pricing configurationoptions to provide solutions for your company�s pricing requirements. In additionto the basic pricing elements, you need to use special functions that allowdependencies between condition types or groups of condition types to be mappedand cumulative values in selected condition records to be updated. These functionsallow you to expand the pool of solution options in the pricing configuration.

Hierarchy Pricing

Figure 46: Hierarchy Accesses (1)

Hierarchy accesses optimize pricing for hierarchy data structures, such as theproduct hierarchy.

2006/Q2 © 2005 SAP AG. All rights reserved. 135

Unit 4: Special Functions SCM620

Figure 47: Hierarchy Accesses (2)

To define the condition table key for hierarchies such as this, you need to includepartial quantities for a predefined quantity of characteristics.

Without hierarchy accesses, you need to create a condition table for eachcombination and assign all the accesses to these tables in an access sequence.

This requires a lot of maintenance and reduces system performance. The sequenceof the accesses is also fixed.

This is disadvantageous for hierarchy data such as product or customer hierarchies.

Figure 48: Hierarchy Accesses (3)

The functions in hierarchy accesses enable you to solve problems using one accessto a condition table.

When you create the access sequence to use this condition table , you need todefine at the field level whether or not each field is a fixed component of the keyor whether or not the field is optional.

136 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Hierarchy Pricing

Priorities are in the next step assigned to the optional fields.

During pricing, the system sorts the records found with this single accessaccording to priority and uses the record with the highest priority.

Hierarchy accesses also provide clear and easy master data maintenance becausethe different condition records for a condition type can be created together in thequick entry screen for maintaining conditions.

2006/Q2 © 2005 SAP AG. All rights reserved. 137

Unit 4: Special Functions SCM620

Lesson Summary

You should now be able to:� Optimize pricing for hierarchical data constellations using hierarchy accesses

138 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Data Determination in Access

Lesson: Data Determination in Access

Lesson OverviewThis lesson explains the techniques of data determination in access.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the techniques of data determination in access using the price bookas an example

Business ExampleYour company produces consumer goods. The project team that implements theSAP system must meet the company�s pricing requirements. As a member of theproject team, you have been given the task of examining the pricing configurationoptions to provide solutions for your company�s pricing requirements. Inaddition to the basic pricing elements, you need to use special functions thatallow dependencies between condition types or groups of condition types to bemapped and cumulative values in selected condition records to be updated. Thesespecial functions allow you to expand the pool of solution options in the pricingconfiguration.

Data Determination in Access

Figure 49: Data Determination in Access

2006/Q2 © 2005 SAP AG. All rights reserved. 139

Unit 4: Special Functions SCM620

The two steps used to determine and use the data in Access differ in the waythey collect data, which means that a distinction must be made between threedata determination procedures, such as:

� Data determination using the communication structure KOMPAZD� Data determination using routines (condition 202, base value calculation

formula 202)� Data determination for sales deals (condition class H)

Figure 50: Data Determination in Access � Price Book

The term price book refers to a price determination strategy.

Pricing procedure RVAA02 was delivered in the SAP standard system as anexample of this.

� The aim here is to set certain prices for a group of customers.� Special agreements are also to be set for these prices, depending on the

material.

140 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Data Determination in Access

This can be achieved using a two-step data determination process, as shown:

� Step 1: A sales deal number (condition type PBU) is determined, dependingon the customer group.

� Step 2: Using the material group as a basis, special agreements aredetermined, which take:

Pricing date

Scale quantity

Item price list

into account (condition type PBUD).

� The special agreements that are determined are used in the condition type,PBBS. As a result, the base prices are read.

� On the basis of these prices, the gross price is calculated in the conditiontype, PBUP, using the percentage value from condition type, PBUD.

2006/Q2 © 2005 SAP AG. All rights reserved. 141

Unit 4: Special Functions SCM620

Lesson Summary

You should now be able to:� Explain the techniques of data determination in access using the price book

as an example

142 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Unit Summary

Unit SummaryYou should now be able to:� Use group conditions to carry out pricing for several items in an order� Compare condition types with several methods and outcomes� Set conditions for a maximum value, quantity, or number of orders� Describe how and when to use condition supplements� Optimize pricing for hierarchical data constellations using hierarchy accesses� Explain the techniques of data determination in access using the price book

as an example

2006/Q2 © 2005 SAP AG. All rights reserved. 143

Unit Summary SCM620

144 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. For group conditions with varying keys, item quantities are accumulated forscale point determination purposes but the rate for each item is taken from itsindividual condition type.Determine whether this statement is true or false.□ True□ False

2. When values are accumulated in condition records, you can set a minimumcondition value.Determine whether this statement is true or false.□ True□ False

3. Multiple conditions cannot be grouped together in a condition supplementprocedure.Determine whether this statement is true or false.□ True□ False

4. What are the several comparison methods that can be used for conditiontypes?

5. Without hierarchy accesses, you need to create a condition table foreach combination and assign all the accesses to these tables in an

.Fill in the blanks to complete the sentence.

6. Why do hierarchy accesses provide clear and easy master data maintenance?

2006/Q2 © 2005 SAP AG. All rights reserved. 145

Test Your Knowledge SCM620

7. The term price book refers to astrategy.Fill in the blanks to complete the sentence.

146 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Answers

1. For group conditions with varying keys, item quantities are accumulated forscale point determination purposes but the rate for each item is taken from itsindividual condition type.

Answer: False

For group conditions with varying keys, item quantities are accumulated forscale point determination purposes but the rate for each item is taken from itsindividual condition record.

2. When values are accumulated in condition records, you can set a minimumcondition value.

Answer: False

When values are accumulated in condition records, you can set a maximumcondition value, condition base value, or number of orders for a condition.

3. Multiple conditions cannot be grouped together in a condition supplementprocedure.

Answer: False

Several conditions can be grouped together in a condition supplementprocedure.

2006/Q2 © 2005 SAP AG. All rights reserved. 147

Test Your Knowledge SCM620

4. What are the several comparison methods that can be used for conditiontypes?

Answer: The several comparison methods that can be used for conditiontypes are:

� A: All conditions found within the first exclusion group are comparedand the condition with the best price is chosen. All other conditionsare deactivated.

� B: All condition records found for one condition are compared. Thebest price is chosen. All others are deactivated. This method can beused with condition type PR00, for example.

� C: The total of condition records found in the first exclusion groupis compared to the total of condition records found in the secondexclusion group. The group resulting in the best price is chosen. Theconditions of the other group are deactivated.

� D: If a condition record is determined for the condition types of the firstexclusion group, all condition records for the second exclusion groupare deactivated.

� E: As for method B, except the worst (highest charge or lowestdiscount) price is chosen.

� F: As for method C, except the group with the worst overall price ischosen. The conditions of the other group are deactivated.

5. Without hierarchy accesses, you need to create a condition table for eachcombination and assign all the accesses to these tables in an access sequence.

Answer: access sequence

6. Why do hierarchy accesses provide clear and easy master data maintenance?

Answer: Hierarchy accesses provide clear and easy master data maintenancebecause the various condition records for a condition type are created in thequick entry screen for maintaining conditions.

7. The term price book refers to a price determination strategy.

Answer: price determination

148 © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 5Condition Types

Unit OverviewThis unit explains special condition types. In addition, it describes some statisticalcondition types.

Unit ObjectivesAfter completing this unit, you will be able to:

� Create order values and net prices manually� Set a minimum price for a material or a minimum value for an order� Set interval scales for conditions� Use customer hierarchies for price agreements� Describe the effect of condition formulae� Round final amounts� Determine costs and cash discount amounts statistically in pricing� Describe how expected customer prices transferred using EDI are used

Unit ContentsLesson: Special Condition Types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Exercise 18: Selected Condition Type Configuration ... . . . . . . . . . . . . . . .161Lesson: Statistical Condition Types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

2006/Q2 © 2005 SAP AG. All rights reserved. 149

Unit 5: Condition Types SCM620

Lesson: Special Condition Types

Lesson OverviewThis lesson describes some standard condition types and explains how to usethe various special condition types, such as manual order value and customerhierarchy discount.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Create order values and net prices manually� Set a minimum price for a material or a minimum value for an order� Set interval scales for conditions� Use customer hierarchies for price agreements� Describe the effect of condition formulae� Round final amounts

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements. The SAP system comes with a lot of condition types that can beused immediately. You need to observe the configuration of these individualcondition types, so that you can profit from the experience when designing yourown condition types.

150 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Manual Pricing

Figure 51: Manual Order Value HM00

The header condition type HM00 allows you to enter the order value manually.The new order value is then distributed proportional between the items, taking intoaccount the previous net item value. Taxes are determined again for each item.

Figure 52: Net Price PN00

The PN00 condition in the standard system allows you to specify the net price foran item manually. The original conditions are deactivated.

2006/Q2 © 2005 SAP AG. All rights reserved. 151

Unit 5: Condition Types SCM620

Minimum Price Value

Figure 53: Minimum Order Values AMIW and AMIZ

You may create a minimum value for each order using condition type AMIW. Ifthe value in the order header is less than this minimum order value during pricing,the system uses the minimum as the net order value automatically. The minimumorder value is a statistical condition.

Condition type AMIW is a group condition and is divided among the differentitems according to value.

Calculation formula 13 is assigned to condition type AMIZ in the pricingprocedure. This formula calculates the minimum value surcharge by subtractingthe net item value from the minimum order value, AMIW.

152 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Figure 54: Minimum Price PMIN

You can create a minimum price for a material using condition type PMIN. If theminimum price is not met during pricing, the system determines the differenceusing condition type PMIN.

Scale Pricing

Figure 55: Interval Price PR02

You can maintain condition records with interval scales if the condition type isset to scale type D in Customizing. Interval scales cannot be used for groupconditions.

2006/Q2 © 2005 SAP AG. All rights reserved. 153

Unit 5: Condition Types SCM620

Customer Hierarchy Pricing

Figure 56: Customer Hierarchy

Customer hierarchies are available in Sales Order Management so that you cancreate flexible hierarchies to reflect the structure of customer organizations. Forexample, if your customer base includes multi-level buying groups, cooperatives,or chains of retail outlets, you can create hierarchies to reflect the structure ofthese groups. Use customer hierarchies during sales order processing and billingto determine pricing and running statistics.

A customer hierarchy consists of nodes.

To create a customer hierarchy:

1. Create master records for each node.2. Assign the nodes to each other.3. Assign the customer master records to the relevant nodes.

Customer hierarchies are valid for a certain period of time. Hierarchy nodes mayalso be moved. If a node is moved, the system automatically reassigns all relatednodes and customer master records.

154 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Figure 57: Hierarchy Path

With customer hierarchies, you can assign price or rebate agreements to a higherlevel node. The agreements are then valid for customers at all subordinate levelsof this node. You can create pricing condition records for each node indicatedas relevant for pricing. If one or more nodes in the hierarchy path of a salesorder contain pricing information, the system takes these nodes into accountautomatically during pricing according to the underlying access sequence.

The customer hierarchy above represents the multi-level buying group Miller. Theheadquarters, Miller Head office, is the highest node defined in the hierarchy. Thesouthern, northern, central, and north-eastern regional offices are also defined asnodes. A price agreement is reached with the Miller buying group for a particularproduct line. You offer a discount valid for all regions and offices in the buyinggroup. In addition, you grant a promotional discount for the northern zone. Youcreate the appropriate condition records for the Miller head office and northernnodes. An order for customer 2742 is received and granted the cross-regionaldiscount. When you receive orders from customers, 2743 and 2744, the systemuses the pricing data stored for Miller North and grants the exclusive promotionaldiscount.

2006/Q2 © 2005 SAP AG. All rights reserved. 155

Unit 5: Condition Types SCM620

Figure 58: Hierarchy Discount HI01

Customer 2743 belongs to the Miller northern office. As a result, a discount of8% has been assigned.

In the standard system, the access sequence is set in Customizing so that thediscount is initiated at the lowest hierarchy level.

Discounts and Surcharges

Figure 59: Pallet Discount KP00

156 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

The pallet discount grants the customer a discount for whole units of measureonly, such as a complete pallet. This is controlled by basic formula 22 in thepricing procedure, which only takes the number of complete pallets into account.

Figure 60: Incomplete Pallet Surcharge KP01

In this case, the customer pays a surcharge for an incomplete pallet. This iscontrolled in basic formula 24 in the pricing procedure, which tests the quantityfor a fractional portion.

Figure 61: Mixed Pallet Discount KP02

The mixed pallet discount accumulates the quantities of the individual items andcalculates the discount for complete pallets only. This is controlled by conditiontype KP02 (group condition = X, unit of measure = PAL) and the correspondingcondition record.

2006/Q2 © 2005 SAP AG. All rights reserved. 157

Unit 5: Condition Types SCM620

Figure 62: Surcharge for Incomplete Mixed Pallets KP03

The mixed pallet surcharge accumulates the quantities of the individual itemsand calculates the surcharge on any fractional portion of the total quantity. Thisis controlled by condition type KP03 (group condition = X, unit of measure =PAL and scale formula 23), which calculates the fractional proportion of the totalquantity.

Rounding Diff

Figure 63: Rounding DIFF

158 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

You can maintain a rounding unit in Table T001R (SAP NetWeaver→ GeneralSettings→ Currencies→ Define rounding rules for currencies) for each companycode and currency. If the final amount in the order header differs from therounding unit, the system rounds the amount up or down as specified.

Condition DIFF determines the difference amount. Condition type DIFF is agroup condition and is distributed among the different items according to value.

2006/Q2 © 2005 SAP AG. All rights reserved. 159

Unit 5: Condition Types SCM620

160 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Exercise 18: Selected Condition TypeConfiguration

Exercise ObjectivesAfter completing this exercise, you will be able to:� Test several calculations which can be accomplished using the special

condition types� Examine what Customizing settings enable the actions of each special

condition type

Business ExampleSAP ERP provides special condition types which enable a wide range ofcalculation variations. You will analyze the special needs of your business todetermine whether or not any of these condition types will be useful.

Task 1:You will test the ability of order entry personnel to specify the total net value forthe order and view the effect that has on the order items.

1. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-1Requested delivery date: In one week

Material QuantityT-AT1## 1T-AT2## 1

2. You have come to an agreement with the customer that the total net value forthis order will be EUR 400. Using a header condition, enter this data into theorder using condition type HM00.

3. Activate the header pricing changes.

4. Review condition type HM00 for each item. What has been done with theheader amount for HM00?

5. Save the order and record the document number.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 161

Unit 5: Condition Types SCM620

Task 2:Your company also requires that the person entering the order be able to overridethe net price of any line item. You will test this function of the system.

1. In an exceptional case, you agree with your customer on a one time net priceof EUR 200 per piece of material T-AT1##. From the customer purchaseorder shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-2Requested delivery date: In one week

Material QuantityT-AT1## 10

2. Manually enter the item net price of EUR 200 with condition type PN00.

3. What happens during pricing?

4. Save the order and record the document number.

Task 3:For certain materials, there is a price floor which is set regardless of the discountsapplicable. You will create this condition type for one of your materials and thentest the condition type with an order.

1. You require that material T-AT1## not be sold for less than a net price ofEUR 300 for the next three months. With this information, create and save aminimum price condition record for this material with condition type PMIN.

2. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-3Requested delivery date: In one week

Material QuantityT-AT1## 10

Continued on next page

162 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

3. What happens during pricing for the item?

4. Save the order and record the document number.

5. Delete the PMIN condition record you created.

Task 4:You will explore the behavior of interval scales by creating a special pricecondition record and then test its use in an order.

1. Create and save a PR02 price condition record with an interval scale forcustomer T-L67A## and material T-AT2##.

Use the default validity period.

Use the following scale values for the condition record:

to 10 pieces 300 EUR20 pieces 290 EUR999999 pieces 280 EUR

2. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-4Requested delivery date: In one week

Material QuantityT-AT2## 25

3. What gross price and value is determined in automatic pricing?

4. Save the order and record the document number.

5. What settings are necessary to use interval scales for the condition type inCustomizing? Check these settings for condition type PR02.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 163

Unit 5: Condition Types SCM620

Task 5:Being able to negotiate pricing at various levels in the organization of your largercustomers is important to your company. You will test customer hierarchy pricingby assigning one of your customers to an existing hierarchy, creating the necessarycondition record and viewing the effect on pricing for customer orders.

1. Assign your customer T-L67A## to the TOPCO Buying Group customerhierarchy under the Western Europe division, node 6222.

2. An agreement is reached with TOPCO�s European region for a blanketdiscount on material T-AT2##. Create an HI02 Hierarchy/Material discountcondition record for customer hierarchy node 6220 and material T-AT2##with a rate of EUR 50.

3. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-5Requested delivery date: In one week

Material QuantityT-AT2## 1

4. Examine the item pricing to determine whether or not the HI02 discountwas taken into account.

5. Save the order and record the document number.

164 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Solution 18: Selected Condition TypeConfigurationTask 1:You will test the ability of order entry personnel to specify the total net value forthe order and view the effect that has on the order items.

1. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-1Requested delivery date: In one week

Material QuantityT-AT1## 1T-AT2## 1

a)

2. You have come to an agreement with the customer that the total net value forthis order will be EUR 400. Using a header condition, enter this data into theorder using condition type HM00.

a) To enter data into the order, click the Display document header detailsbutton at the top right portion of the screen.

Select the Conditions tab.

Click the Insert line button.

Enter the condition type and rate.

3. Activate the header pricing changes.

a) Activate HM00 by choosing Activate: new document pricing. Originalprices become inactive and condition HM00 becomes active.

4. Review condition type HM00 for each item. What has been done with theheader amount for HM00?

a) The total net order value is divided among the items according to theirproportional value.

5. Save the order and record the document number.

a)Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 165

Unit 5: Condition Types SCM620

Task 2:Your company also requires that the person entering the order be able to overridethe net price of any line item. You will test this function of the system.

1. In an exceptional case, you agree with your customer on a one time net priceof EUR 200 per piece of material T-AT1##. From the customer purchaseorder shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-2Requested delivery date: In one week

Material QuantityT-AT1## 10

a)

2. Manually enter the item net price of EUR 200 with condition type PN00.

a)

3. What happens during pricing?

a) All the original conditions on the condition screen up to order PN00become inactive. You can identify this change either by the colors ofthe display or in the detail screen for each condition (Inactive field = Y).

4. Save the order and record the document number.

a)

Task 3:For certain materials, there is a price floor which is set regardless of the discountsapplicable. You will create this condition type for one of your materials and thentest the condition type with an order.

1. You require that material T-AT1## not be sold for less than a net price ofEUR 300 for the next three months. With this information, create and save aminimum price condition record for this material with condition type PMIN.

a) To Create a minimum price condition record:

Select Logistics→ Sales and Distribution→ Master Data→Conditions→ Select Using Condition Type→ Create.

Choose condition type PMIN

Continued on next page

166 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

2. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-3Requested delivery date: In one week

Material QuantityT-AT1## 10

a)

3. What happens during pricing for the item?

a) If the item net value determined is less than the minimum price, thesystem calculates the condition value of minimum price PMIN as thedifference between the minimum price and the gross amount aftersubtracting any discount amount. The net value per piece of the itemwill then correspond to the minimum price per piece.

4. Save the order and record the document number.

a)

5. Delete the PMIN condition record you created.

a) To Delete a condition record:

Select Logistics→ Sales and Distribution→ Master Data→Conditions→ Select Using Condition Type→ Change.

Enter condition type PMIN and choose Enter.

Enter the appropriate values for your condition record and chooseExecute.

Select the condition record.

Choose Delete line.

Task 4:You will explore the behavior of interval scales by creating a special pricecondition record and then test its use in an order.

1. Create and save a PR02 price condition record with an interval scale forcustomer T-L67A## and material T-AT2##.

Use the default validity period.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 167

Unit 5: Condition Types SCM620

Use the following scale values for the condition record:

to 10 pieces 300 EUR20 pieces 290 EUR999999 pieces 280 EUR

a) To Create prices with an interval scale:

Select Logistics→ Sales and Distribution→ Master Data→Conditions→ Select Using Condition Type→ Create.

Choose condition type PR02.

To enter the scale values, select the condition line and choose Scales.

2. From the customer purchase order shown below, create a standard sales order.

TELEFAXCustomer: T-L67A##PO number: ##-6-4Requested delivery date: In one week

Material QuantityT-AT2## 25

a)

3. What gross price and value is determined in automatic pricing?

a) Gross: EUR 292 per piece = EUR 7300

4. Save the order and record the document number.

a)

5. What settings are necessary to use interval scales for the condition type inCustomizing? Check these settings for condition type PR02.

a) Scale type D (graduated-to interval scale) must be used.

Continued on next page

168 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Task 5:Being able to negotiate pricing at various levels in the organization of your largercustomers is important to your company. You will test customer hierarchy pricingby assigning one of your customers to an existing hierarchy, creating the necessarycondition record and viewing the effect on pricing for customer orders.

1. Assign your customer T-L67A## to the TOPCO Buying Group customerhierarchy under the Western Europe division, node 6222.

a) Logistics→ Sales and Distribution→ Master Data→ BusinessPartner→ Customer Hierarchy→Edit.

Enter: Customer hierarchy type A.

and: Customer 6200

Choose Execute.

Select Expand all.

Select the hierarchy node 6222 TOPCO Western Europe.

Choose Create assignment.

Enter the data given below.

"Customer" field group Input dataCustomer T-L67A##Sales organization 1000DistrChannel 10Divis. 00

Choose Transfer. Customer T-L67A## is now assigned to TOPCO�s"Western Europe" division.

Save the assignment.

2. An agreement is reached with TOPCO�s European region for a blanketdiscount on material T-AT2##. Create an HI02 Hierarchy/Material discountcondition record for customer hierarchy node 6220 and material T-AT2##with a rate of EUR 50.

a)

3. From the customer purchase order shown below, create a standard sales order.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 169

Unit 5: Condition Types SCM620

TELEFAXCustomer: T-L67A##PO number: ##-6-5Requested delivery date: In one week

Material QuantityT-AT2## 1

a)

4. Examine the item pricing to determine whether or not the HI02 discountwas taken into account.

a) The HI02 hierarchy/material discount created for node 6220 is used bycustomer T-L67A## who is assigned to a lower node in that hierarchy.

5. Save the order and record the document number.

a)

170 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Special Condition Types

Lesson Summary

You should now be able to:� Create order values and net prices manually� Set a minimum price for a material or a minimum value for an order� Set interval scales for conditions� Use customer hierarchies for price agreements� Describe the effect of condition formulae� Round final amounts

2006/Q2 © 2005 SAP AG. All rights reserved. 171

Unit 5: Condition Types SCM620

Lesson: Statistical Condition Types

Lesson OverviewThis lesson describes how to determine costs and cash discount amountsstatistically in pricing. It also explains how expected prices transferred via EDIare used.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Determine costs and cash discount amounts statistically in pricing� Describe how expected customer prices transferred using EDI are used

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements.

When processing a pricing procedure, it is often necessary to determine valuesand make these values in the procedure available for various purposes. However,these values must not change the net value of the item. This can be achieved bymarking a condition type as statistical. For example the cost from the materialmaster and the maximum cash discount amount are determined as statisticalconditions in the sales document.

172 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Statistical Condition Types

Statistical Condition Types

Figure 64: Cost VPRS

In the standard version, condition type VPRS is used to retrieve the standard costof the material. The pricing procedure uses this condition type as a statistical value.

Using condition category G, VPRS accesses the valuation segment of the materialmaster locating either the standard cost or the moving average cost, as specifiedin the material master.

Condition category S always accesses the standard cost, whereas conditioncategory T always accesses the moving average cost.

The profit margin is calculated using formula 11 in the pricing procedure. Thisformula subtracts the cost from the net value.

2006/Q2 © 2005 SAP AG. All rights reserved. 173

Unit 5: Condition Types SCM620

Figure 65: Cash Discount SKTO

In the standard system, condition type SKTO is used to retrieve the cash discountrate. The pricing procedure uses this condition type as a statistical value.

Table T052 is accessed using condition category E and an amount is calculatedfrom the first percentage rate of the item payment terms.

Figure 66: Customer Expected Prices � EDI1 and EDI2

You can either enter the customer expected price manually in the order or retrievethe price from the incoming IDoc in an EDI environment.

174 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Statistical Condition Types

You can use condition type EDI1 to compare the net price for each item. You canuse condition type EDI2 to compare the overall item value, which is obtained bymultiplying the net price and the quantity.

Calculation formula 9 is assigned to condition type EDI1 in the pricing procedure.This formula tests for a maximum deviation of 0.05 currency units.

Calculation formula 8 is assigned to condition type EDI2 in the pricing procedure.This formula tests for a maximum deviation of 1.0 currency units.

If the customer expected price differs from the automatically determined price orvalue by more than the maximum difference allowed, the system considers thisorder as incomplete when the order is saved.

You can process lists of orders having differences in prices, allowing the system touse or correct the price it determined.

2006/Q2 © 2005 SAP AG. All rights reserved. 175

Unit 5: Condition Types SCM620

Lesson Summary

You should now be able to:� Determine costs and cash discount amounts statistically in pricing� Describe how expected customer prices transferred using EDI are used

176 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Unit Summary

Unit SummaryYou should now be able to:� Create order values and net prices manually� Set a minimum price for a material or a minimum value for an order� Set interval scales for conditions� Use customer hierarchies for price agreements� Describe the effect of condition formulae� Round final amounts� Determine costs and cash discount amounts statistically in pricing� Describe how expected customer prices transferred using EDI are used

2006/Q2 © 2005 SAP AG. All rights reserved. 177

Unit Summary SCM620

178 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. Which of the following is a group condition and is divided among thedifferent items according to value?Choose the correct answer(s).□ A PN00□ B AMIW□ C PMIN□ D AMIZ

2. You can maintain condition records with if thecondition type is set to scale type D in Customizing.Fill in the blanks to complete the sentence.

3. With , you can assign price orrebate agreements to a higher level node.Fill in the blanks to complete the sentence.

4. What is the function of mixed pallet discount KP02 condition type?

5. If the final amount in the order differs from the rounding unit, the systemrounds the amount up or down as specified.Determine whether this statement is true or false.□ True□ False

6. What is the use of condition category G?

2006/Q2 © 2005 SAP AG. All rights reserved. 179

Test Your Knowledge SCM620

7. Describe the use of calculation formulae 8 and 9.

180 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Answers

1. Which of the following is a group condition and is divided among thedifferent items according to value?

Answer: B

Condition type AMIW is a group condition that is divided among thedifferent items according to value.

2. You can maintain condition records with interval scales if the condition typeis set to scale type D in Customizing.

Answer: interval scales

3. With customer hierarchies, you can assign price or rebate agreements toa higher level node.

Answer: customer hierarchies

4. What is the function of mixed pallet discount KP02 condition type?

Answer: The mixed pallet discount accumulates the quantities of theindividual items and then calculates the discount for complete pallets only.This is controlled by condition type KP02 and the corresponding conditionrecord.

5. If the final amount in the order differs from the rounding unit, the systemrounds the amount up or down as specified.

Answer: True

If the final amount in the order header differs from the rounding unit, thesystem rounds the amount up or down as specified.

6. What is the use of condition category G?

Answer: Using condition category G, VPRS accesses the valuation segmentof the material master locating either the standard cost or the moving averagecost, as specified in the material master.

2006/Q2 © 2005 SAP AG. All rights reserved. 181

Test Your Knowledge SCM620

7. Describe the use of calculation formulae 8 and 9.

Answer: Calculation formula 9 is assigned to condition type EDI1 in thepricing procedure. This formula tests for a maximum deviation of 0.05currency units.Calculation formula 8 is assigned to condition type EDI2 in the pricingprocedure. This formula tests for a maximum deviation of 1.0 currency units.

182 © 2005 SAP AG. All rights reserved. 2006/Q2

Unit 6Taxes, Pricing Agreements, and

Rebates

Unit OverviewThis unit explains how tax is calculated in SD. It also explains how sales dealsand promotions are managed using agreements. In addition, it describes how toprocess rebates, create rebate agreements, and settle rebates.

Unit ObjectivesAfter completing this unit, you will be able to:

� Describe the criteria taken into account to determine taxes� Describe how taxes are determined for each order item� Use agreements to implement and evaluate marketing projects� Describe the entire rebate processing procedure� Create rebate agreements� Perform rebate settlements� Control rebate processing in Customizing

Unit ContentsLesson: Taxes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Lesson: Pricing Agreements .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Exercise 19: Promotions and Sales Deals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Lesson: Rebates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Exercise 20: Creating Rebate Agreements ... . . . . . . . . . . . . . . . . . . . . . . . . . .211Exercise 21: Processing Rebate Agreements ... . . . . . . . . . . . . . . . . . . . . . . .215Exercise 22: Settling Rebates .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

2006/Q2 © 2005 SAP AG. All rights reserved. 183

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Lesson: Taxes

Lesson OverviewThis lesson describes the criteria to be considered to determine taxes. It discussesthe factors affecting tax determination. In addition, it describes how taxes aredetermined for each order item.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the criteria taken into account to determine taxes� Describe how taxes are determined for each order item

Business ExampleYour company produces consumer goods. The project team that implements theSAP system must meet the company�s pricing requirements. As a member of theproject team, you have been given the task of examining the pricing configurationoptions to provide solutions for your company�s pricing requirements.

Ttaxes should be determined automatically within pricing in your company. Validtax categories and tax determination rules must be defined for every countrywhere you do business.

Criteria to Determine Tax

Figure 67: Criteria to Determine Tax

184 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Taxes

You can assign a rule, blank, A, B, at the sales organization level to determinethe sales tax identification number in the order and billing document (the taxclassification determination is linked to this).

For the status BLANK, the standard priority rules are as follows:

� 1. If PY has a sales tax ID and a different SP:

� The tax number and tax classification are taken from PY (SH is thennot relevant). The tax number is determined according to the taxdestination country.

� 2. If rule 1 does not apply:

� If SH has a sales tax ID or SP has no sales tax ID, the tax number andtax classification are taken from SH.

� 3. If rule 2 does not apply:

� The tax number and tax classification are transferred from the sold-toparty.

With status A, the tax number and tax classification are transferred from thesold-to party. The tax number is transferred according to the tax destinationcountry.

With status �B�, data is transferred from the payer in the same way as in rule A.

Figure 68: Tax Classification

2006/Q2 © 2005 SAP AG. All rights reserved. 185

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

The system determines a tax rate in the order/billing document on the basis ofthree criteria:

� Business transaction-domestic or export/import� Tax liability of the ship-to party� Tax liability of the material

Determining Taxes

Figure 69: Pricing Procedures for Tax

Taxes may be calculated in Sales and Distribution using the normal conditiontechniques.

The condition type for tax is entered into the pricing procedure.

The access sequence is used to find the appropriate condition record for thecurrent situation.

186 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Taxes

Figure 70: Tax Interfaces (Example � United States)

You need to decide when taxes are to be calculated. The tax procedure is assignedin the defaults for Financial Accounting according to country. For the UnitedStates, you have the following options:

� TAXUS (taxes are calculated in Sales and Distribution)� TAXUSJ (taxes are calculated in the central tax procedure using the tax

jurisdiction value stored in the master data for the ship-to party)� TAXUSX (taxes are calculated through an RFC and a central tax procedure)

For jurisdictional and third-party tax calculations, after the procedure has beendetermined, the corresponding pricing procedure in SD uses the appropriatecondition types. For example, if the tax procedure assigned to the country isTAXUSJ, the pricing procedure RVAJUS uses the condition types, UTXJ, JR1,JR2, JR3, and JR4. If the central tax procedure is TAXUSX, the pricing procedureRVAXUS uses the condition types, UTXJ, XR1, XR2, XR3, XR4, XR5, and XR6.

The condition type UTXJ initiates the tax calculation. JR1-4 and XR1-6 arecondition types that receive the jurisdictional breakdown of the TAX amountsreturned from the central tax procedure.

2006/Q2 © 2005 SAP AG. All rights reserved. 187

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Lesson Summary

You should now be able to:� Describe the criteria taken into account to determine taxes� Describe how taxes are determined for each order item

188 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Agreements

Lesson: Pricing Agreements

Lesson OverviewThis lesson describes how to use agreements to analyze marketing projects. It alsoexplains how to use various agreement types, such as promotions and sales deals.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Use agreements to implement and evaluate marketing projects

Business ExampleYour company produces consumer goods. The project team that implements theSAP system must meet the company�s pricing requirements. As a member of theproject team, you have been given the task of examining the pricing configurationoptions to provide solutions for your company�s pricing requirements.

Marketing programs are used in your company, for example, special conditionsare set for particular periods for individual products or product groups. To analyzethese special conditions later, the system provides various agreement types, suchas promotions and sales deals, within which these condition records can be created.

Promotion and Sales Deal

Figure 71: Validity Period

2006/Q2 © 2005 SAP AG. All rights reserved. 189

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

You can define a promotion or general marketing plan for a product line for acertain period of time. You can then link this promotion with specific sales deals,which are then linked to special condition records used for promotional pricingor discounts.

Figure 72: Sales Deal: Example

This example depicts a summer sales promotion, which contains several salesdeals for various product lines. Condition records for discounts are linked tothe corresponding sales deals.

Figure 73: Sales Deals and Promotions in the Billing Document

190 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Agreements

The sales deal number and promotion number fields are displayed in the detailscreen of the billing item. The Sales Information System can be used to captureand report the statistics for the sales deals and promotions with a user-definedinformation structure.

Figure 74: Release Status for Sales Deals

The release status of a sales deal controls where you can find the condition recordsfor a sales agreement. If, for example, the activity has status B, the activity recordsare included in pricing simulation (net price list) but are not used in the currentdocuments. If the activity has status C, the condition records are also consideredwhile planning in the CO-PA module.

2006/Q2 © 2005 SAP AG. All rights reserved. 191

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

192 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Agreements

Exercise 19: Promotions and Sales Deals

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create promotions and sales deals� Link condition records to agreements� Display agreement information in the billing document

Business ExampleYour sales department needs to report the pricing information. As a result, yourimplementation team needs to check the promotion and sales deal agreementfunction to see if it meets the requirement.

Task 1:You have been asked to test the capability of promotions and sales deals to ensurethat the necessary information flows from the order to the invoice for reportingpurposes.

1. Create and save a promotion using your group number in the description.Enter a description, which includes your group number.

2. Create a sales deal with reference to your promotion. Any sales ordersplaced by your customer using this sales deal will be offered special paymentterms of 20 days 2%, 30 days net.

3. Your sales deal is specific to certain customers. Customer T-L67B## willreceive an additional 5% discount for the entire sales deal. Create and save aK007 condition record for your sales deal.

Task 2:For reporting purposes, management needs to link customer invoices to aparticular promotion/sales deal combination. You need to test the ability of thesystem to meet this requirement.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67B##PO number: ##-9-2Requested delivery date: In one week

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 193

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Material QuantityT-AT3## 10

2. View the pricing for the item. Was the sales deal discount used on the order?

3. Save the order and record the document number.

4. Create a delivery for the order, pick the required quantity, and then postgoods issue. Use shipping point 1200 and a selection date of 10 daysfrom today. Choose warehouse number 012 for the transfer order. Notethe document number.

5. Create an invoice for the delivery.

6. View the item details in the invoice and locate the promotion number andsales deal number.

7. Save the invoice and record the document number.

194 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Agreements

Solution 19: Promotions and Sales DealsTask 1:You have been asked to test the capability of promotions and sales deals to ensurethat the necessary information flows from the order to the invoice for reportingpurposes.

1. Create and save a promotion using your group number in the description.Enter a description, which includes your group number.

a) To create a promotion, select:

Logistics→ Sales and Distribution→ Master Data→ Agreements→ Promotion→ Create.

Choose promotion type 0030.

2. Create a sales deal with reference to your promotion. Any sales ordersplaced by your customer using this sales deal will be offered special paymentterms of 20 days 2%, 30 days net.

a) To create a sales deal, select:

Logistics→ Sales and Distribution→ Master Data→ Agreements→ Sales deal→ Create.

Choose sales deal type 0020.

Choose Reference promotion.

Enter your promotion number and choose Copy.

Enter a description and payment terms (ZB03).

Save the sales deal and record the agreement number.

3. Your sales deal is specific to certain customers. Customer T-L67B## willreceive an additional 5% discount for the entire sales deal. Create and save aK007 condition record for your sales deal.

a) To creating a condition record for sales deal, select:

Logistics→ Sales and Distribution→ Master Data→ Agreements→ Sales deal→ Change.

Enter your sales deal number and choose Enter.

Choose Conditions.

Select K007 Customer discount and click the Choose button.

Enter the appropriate values and save the condition record.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 195

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Task 2:For reporting purposes, management needs to link customer invoices to aparticular promotion/sales deal combination. You need to test the ability of thesystem to meet this requirement.

1. From the customer purchase order shown below, create a standard sales order:

TELEFAXCustomer: T-L67B##PO number: ##-9-2Requested delivery date: In one week

Material QuantityT-AT3## 10

a)

2. View the pricing for the item. Was the sales deal discount used on the order?

a) Pricing automatically calculates a customer discount (K007) of 5%from the sales deal.

3. Save the order and record the document number.

a)

4. Create a delivery for the order, pick the required quantity, and then postgoods issue. Use shipping point 1200 and a selection date of 10 daysfrom today. Choose warehouse number 012 for the transfer order. Notethe document number.

a) To creating an outbound delivery order, use a transfer order to pick therequired quantity, and then to post goods issue, select:

Logistics→ Sales and Distribution→ Shipping and Transportation→ Outbound Delivery→ Create→ Single Document→ WithReference to Sales Order.

To pick the required quantity directly from within the deliverydocument, select:

Subsequent functions→ Create transfer order.

Enter the warehouse number 012.

In the Picking quantity field, choose function 2 (copy the pickingquantity to the delivery and post goods issue).

Save the transfer order.Continued on next page

196 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Pricing Agreements

5. Create an invoice for the delivery.

a) To create a billing document, select:

Logistics→ Sales and Distribution→ Billing→ Billing document→ Create.

Enter your delivery document number and click the Execute button.

6. View the item details in the invoice and locate the promotion number andsales deal number.

a) The promotion and sales deal numbers are displayed.

7. Save the invoice and record the document number.

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 197

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Lesson Summary

You should now be able to:� Use agreements to implement and evaluate marketing projects

198 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Lesson: Rebates

Lesson OverviewThis lesson describes the rebate processing procedure. It explains how to createrebate agreements and perform rebate settlements.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Describe the entire rebate processing procedure� Create rebate agreements� Perform rebate settlements� Control rebate processing in Customizing

Business ExampleYour company manufactures consumer goods. The project team that implementsthe SAP system must meet the company�s pricing requirements. As amember of the project team, you have been given the task of examining thepricing configuration options to provide solutions for your company�s pricingrequirements.

A rebate is a discount, which is granted subsequently to a rebate recipient on thebasis of a defined sales volume within a certain period. Rebate agreements arecreated to determine the values required for a rebate settlement within the validityperiod of the rebate agreement.

2006/Q2 © 2005 SAP AG. All rights reserved. 199

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Creating Rebate Agreements

Figure 75: Rebate Agreement Types

You may define rebates at as many levels as you require, similar to any otherpricing condition.

The standard system provides the following rebate agreement types:

� Material rebate� Customer rebate� Customer hierarchy rebate� Material group rebate� Independent of sales volume

Figure 76: Creating Rebate Agreements (1)

The rebate agreement is created with a specific rebate agreement type. Thefeatures of each rebate agreement type are set in Customizing.

200 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Figure 77: Creating Rebate Agreements (2)

Condition records are linked to the rebate agreement specifying the rebate rateand the accrual rate.

With the rebate agreement, you can specify:

� The condition types used with this rebate agreement type� A validity period proposal

Processing Rebates

Figure 78: Processing Rebates

2006/Q2 © 2005 SAP AG. All rights reserved. 201

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Rebates are different from other discounts in that they are based on the salesvolume generated by the customer within a specified period and are paidretrospectively. The rebate details are defined in a rebate agreement.

A settlement run creates the required credit memo request automatically. Whenthe rebate-relevant billing documents are processed, accruals can be determinedand posted automatically. You can use the rebate credit memo to reverse theseaccruals, if required.

Figure 79: Prerequisites for Rebate Processing

To function properly, rebate processing must be activated for:

� The sales organization� The payer master� The billing document type

To improve performance, you should deactivate rebate processing if it is notnecessary.

Figure 80: Rebate Processing (1)

Rebate processing begins by creating a rebate-relevant billing document.

202 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Figure 81: Rebate Processing (2)

The valid rebates are determined by the pricing procedure using the rebate basissubtotal.

Figure 82: Rebate Processing (3)

Each rebate condition type has an assigned access sequence.

2006/Q2 © 2005 SAP AG. All rights reserved. 203

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Figure 83: Rebate Processing (4)

The system uses the access sequence to search for the valid rebate conditionrecords. If valid condition records are found, the accrual rate is read.

Requirement 24 in the pricing procedure enforces that the rebate conditions areused only in billing documents.

Requirement 25 in the pricing procedure enforces that the rebate conditions areused only in rebate-relevant billing documents.

Figure 84: Rebate Processing (5)

The rebate accrual amount is calculated using the rebate basis.

204 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Figure 85: Rebate Processing (6)

The system posts an accrual to financial accounting when the rebate-relevantbilling document is released to accounting.

At the same time, the system updates the rebate basis and the accrual amount onthe rebate agreement sales volume screen.

Settling Rebates

Figure 86: Creating Rebate Settlements (1)

2006/Q2 © 2005 SAP AG. All rights reserved. 205

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

The system uses the accumulated amounts in the rebate agreement to create arebate settlement. Status A refers to an open rebate agreement.

Figure 87: Creating Rebate Settlements (2)

The system generates a rebate credit memo request for the rebate payment amountspecified.

Figure 88: Creating Rebate Settlements (3)

206 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

You can display the sales volume and drill-down in the rebate agreement.

You can perform a final settlement for the rebate agreement in the following ways:

� Manually� Automatically� In the background (batch programs: RV15C001 and RV15C002)

Accruals are reversed as soon as the rebate agreement is settled by credit memo.

Figure 89: Partial Rebate Settlement

Partial rebate settlements can be limited for each rebate agreement type, as follows:

� Up to the accumulated accrual amount� Up to the calculated payment amount for the current date� Unlimited

Accruals are cancelled automatically when a credit memo is created, provided thatthe rebate agreement type is set accordingly in Customizing.

2006/Q2 © 2005 SAP AG. All rights reserved. 207

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Figure 90: Settlement Material (1)

You may have a rebate that does not refer to a particular material but rather to agroup of materials or to a customer. In this case, you must refer to a settlementmaterial to provide information at the material level.

Maintain the rebate material in the material master in the Sales and Accountingviews.

Figure 91: Settlement Material (2)

When creating a credit memo, the settlement material is the source for importantmaterial master data, for example, account determination.

208 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Retroactive Rebate Agreements

Figure 92: Retroactive Rebate Agreements (1)

Retroactive rebate agreements allow you to take into account billing documentscreated before the rebate agreement is created.

Figure 93: Retroactive Rebate Agreements (2)

The rebate basis for the billing documents created previously is accumulatedand recorded in the rebate agreement.

The accrual amount is not automatically updated for billing documents createdpreviously. This amount can be entered manually or can be corrected by usingreport RV15B002.

2006/Q2 © 2005 SAP AG. All rights reserved. 209

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Figure 94: Retroactive Rebate Agreements (3)

Rebate-relevant billing documents created after the rebate agreement is createdupdate both the rebate basis and accrual fields automatically.

210 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Exercise 20: Creating Rebate Agreements

Exercise ObjectivesAfter completing this exercise, you will be able to:� Create rebate agreements and rebate condition records

Business ExampleRebates are offered to customers to promote sales and build customer loyalty. Youmust explore the rebate function to ensure that it meets your needs.

Task 1:To use the rebate function of the system, certain parameters must be set in thesystem. You need to ensure that these parameters are set properly in the system.

1. Check whether or not rebate processing is active for customer T-L67B##,billing type F2, and your sales organization. Make them active, if necessary.

Task 2:After the rebate processing is active, you will create rebate agreements and rebatecondition records for one of your customers to reward him or her for buying aparticular material.

1. Create a material rebate agreement for customer T-L67B##.

2. Enter the rebate conditions on your rebate agreement. You will be offeringcustomer T-L67B## a rebate on material T-AT3## purchased using thefollowing scale:

from 1 piece 20 EUR20 pieces 30 EUR

Use EUR 20 as the accrual rate.

3. Save the rebate agreement and record the document number.

2006/Q2 © 2005 SAP AG. All rights reserved. 211

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Solution 20: Creating Rebate AgreementsTask 1:To use the rebate function of the system, certain parameters must be set in thesystem. You need to ensure that these parameters are set properly in the system.

1. Check whether or not rebate processing is active for customer T-L67B##,billing type F2, and your sales organization. Make them active, if necessary.

a) Select the Rebates field on the Billing document tab.

Select Logistics→ Sales and Distribution→ Business Partner→Customer→ Display→ Sales and Distribution.

Enter the customer number and the sales area.

Click the Continue button.

Choose Sales Area Data.

To check the billing type in Customizing, select

SAP Reference IMG→ Sales and Distribution→ Billing→ RebateProcessing→ Activate Rebate Processing→ Select billing documentsfor rebate processing.

The Relevant for rebate field should be marked for document type F2.

To check the sales organization in Customizing, select

SAP Reference IMG→ Sales and Distribution→ Billing→ RebateProcessing → Activate Rebate Processing → Activate rebateprocessing for sales organizations.

The Rebate proc.active field should be marked for sales organization1000.

Task 2:After the rebate processing is active, you will create rebate agreements and rebatecondition records for one of your customers to reward him or her for buying aparticular material.

1. Create a material rebate agreement for customer T-L67B##.

a) To create a material rebate agreement, select:

Logistics→ Sales and Distribution→ Rebate Arrangements→Rebate Arrangement→ Create.

Choose agreement type 0002, material rebate.

Enter the appropriate values.

Continued on next page

212 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

2. Enter the rebate conditions on your rebate agreement. You will be offeringcustomer T-L67B## a rebate on material T-AT3## purchased using thefollowing scale:

from 1 piece 20 EUR20 pieces 30 EUR

Use EUR 20 as the accrual rate.

a) Enter rebate conditions

Choose Conditions.

Enter the values specified.

Select the condition line and choose Scales.

Enter the scale values.

3. Save the rebate agreement and record the document number.

a)

2006/Q2 © 2005 SAP AG. All rights reserved. 213

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

214 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Exercise 21: Processing RebateAgreements

Exercise ObjectivesAfter completing this exercise, you will be able to:� Test the calculation and updating of rebate accruals

Business ExampleFor rebates to function properly, the billing values must be accumulated accuratelyin the rebate agreement. You will test the updating of these accrual amounts.

Task:You will test your rebate agreement functionality by creating orders for theapplicable material, shipping, and then billing the orders.

1. Create two separate orders from the customer purchase orders shown below.

TELEFAXCustomer: T-L67B##PO number: ##-10-3aRequested delivery date: In one week

Material QuantityT-AT3## 3

TELEFAXCustomer: T-L67B##PO number: ##-10-3bRequested delivery date: In one week

Material QuantityT-AT3## 3

2. Save both orders and record the document numbers.

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 215

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

3. Create separate outbound deliveries for the orders. Use shipping point 1200and a selection date of 10 days from today. Pick the required quantities forthe two deliveries and then post a goods issue. Record all document numbers.

4. Create and save a billing document separately for each outbound delivery.Record all document numbers.

5. Display the rebate agreement. View the payment data screen and record theaccruals, rebate payments and maximum payable amount.

Hint: If you get the message: �The sales volume for agreementxy is not current�

Choose Logistics→ Sales and Distribution→ Billing→ Rebates→ Update Billing Documents in order to execute report SDBONT06for your payer T-L67B##.

6. When were the accruals and business volume updated in the rebateagreement?

216 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Solution 21: Processing RebateAgreementsTask:You will test your rebate agreement functionality by creating orders for theapplicable material, shipping, and then billing the orders.

1. Create two separate orders from the customer purchase orders shown below.

TELEFAXCustomer: T-L67B##PO number: ##-10-3aRequested delivery date: In one week

Material QuantityT-AT3## 3

TELEFAXCustomer: T-L67B##PO number: ##-10-3bRequested delivery date: In one week

Material QuantityT-AT3## 3

a)

2. Save both orders and record the document numbers.

a)

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 217

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

3. Create separate outbound deliveries for the orders. Use shipping point 1200and a selection date of 10 days from today. Pick the required quantities forthe two deliveries and then post a goods issue. Record all document numbers.

a) Creating an outbound delivery, a transfer order to do the picking, andthen posting goods issue.

Logistics→ Sales and Distribution→ Shipping and Transportation→ Outbound Delivery→ Create→ Single Document→ WithReference to Sales Order.

To pick the required quantity from directly within the delivery, choose:

Subsequent Functions→ Create Transfer Order.

Enter the warehouse number 012.

In the Picking quantity field, choose function 2 (copy the pickingquantity to the delivery and post goods issue).

Save the transfer order.

4. Create and save a billing document separately for each outbound delivery.Record all document numbers.

a) Creating a billing document:

Logistics→ Sales and Distribution→ Billing→ Billing Document→ Create.

Enter your delivery document number and click the Execute button.

Save the billing document and record the number. (The accountingdocument is automatically created at the same time).

Repeat this process for the second delivery document.

Continued on next page

218 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

5. Display the rebate agreement. View the payment data screen and record theaccruals, rebate payments and maximum payable amount.

Hint: If you get the message: �The sales volume for agreementxy is not current�

Choose Logistics→ Sales and Distribution→ Billing→ Rebates→ Update Billing Documents in order to execute report SDBONT06for your payer T-L67B##.

a) Accruals: 120 EUR

Rebate payments: 0 EUR

Max. payable amount: 120 EUR

Logistics→ Sales and Distribution→ Master Data→ RebateArrangements→Rebate Arrangement→ Display.

Enter the agreement number and choose Enter.

Choose Conditions.

Select the condition line.

Choose Payment data.

6. When were the accruals and business volume updated in the rebateagreement?

a) The accruals and business volume are updated when the accountingdocument for billing is created.

2006/Q2 © 2005 SAP AG. All rights reserved. 219

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

220 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Exercise 22: Settling Rebates

Exercise ObjectivesAfter completing this exercise, you will be able to:� Test the calculation of rebate amounts and the settlement of the rebate

agreement

Business ExampleTypically, after rebates have been accrued in the rebate agreement, payment canbe made to the rebate recipient according to a payment schedule. You need totest this function.

Task:You will test the settlement function of rebates by settling your rebate agreementwith a partial payment credit memo. You will also view various screens in therebate agreement to ensure that the settlement transaction has been recordedproperly.

1. Carry out a manual partial settlement for the rebate agreement. Create acredit memo request for EUR 80. You must first change the status of therebate agreement to B (released for payment).

2. Save the document. The credit memo request document is generatedautomatically.

3. Find and record the number of the credit memo request created from theagreement.

4. Release the billing block on the credit memo request and save your changes.

5. Create and save the credit memo from the credit memo request.

6. Release the credit memo to accounting.

7. What happened to the accrual amount in the rebate agreement?

8. Call the 1) Business volume, 2) Rebate documents and 3) Rebate paymentdrill-down screens and review the information.

2006/Q2 © 2005 SAP AG. All rights reserved. 221

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

Solution 22: Settling RebatesTask:You will test the settlement function of rebates by settling your rebate agreementwith a partial payment credit memo. You will also view various screens in therebate agreement to ensure that the settlement transaction has been recordedproperly.

1. Carry out a manual partial settlement for the rebate agreement. Create acredit memo request for EUR 80. You must first change the status of therebate agreement to B (released for payment).

a) To execute manual partial settlements, select:

Logistics→ Sales and Distribution→ Master Data→ RebateArrangements→ Rebate Arrangement→ Change.

Enter the agreement number and press Enter.

Change the Agreement status field to B.

Choose Create manual accrual or press Shift+F12.

Enter the amount to be paid.

Save the rebate agreement.

2. Save the document. The credit memo request document is generatedautomatically.

a)

3. Find and record the number of the credit memo request created from theagreement.

a) To view settlement documents, select:

Logistics→ Sales and Distribution→ Master Data→ RebateArrangements→ Rebate Arrangement→ Display.

Enter the agreement number and press Enter.

Select Rebate payments→ Rebate documents.

Select Partial settlement.

Click Choose.

View the credit memo request number.

Continued on next page

222 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

4. Release the billing block on the credit memo request and save your changes.

a) To remove the billing block, select:

Logistics→ Sales and Distribution→ Sales→ Order→ Change.

Enter the credit memo request number and press Enter.

Select the Item overview tab.

Release the billing block by selecting the blank line from the entriesand save the document.

5. Create and save the credit memo from the credit memo request.

a) To create a rebate credit memo, select:

Logistics→ Sales and Distribution→ Billing→ Billing Document→ Create.

Enter the credit memo request number and choose Execute.

Save the credit memo document.

6. Release the credit memo to accounting.

a) To release the credit memo to accounting, select:

Logistics→ Sales and Distribution→ Billing→ Billing Document→ Change.

Enter the billing document number and choose Release To Accounting.

7. What happened to the accrual amount in the rebate agreement?

a) The accruals are canceled when the rebate agreement is settled in acredit memo.

Select Logistics→ Sales and Distribution→Master Data→ RebateArrangements→ Rebate Arrangement→ Display.

Enter the agreement number and pressEnter.

Choose Conditions.

Select the condition line.

Choose Payment data.

Accruals: 120 EURAccruals reversed: 80 EURRebate payments: 80 EURMax. payable amount: 40 EUR

Continued on next page

2006/Q2 © 2005 SAP AG. All rights reserved. 223

Unit 6: Taxes, Pricing Agreements, and Rebates SCM620

8. Call the 1) Business volume, 2) Rebate documents and 3) Rebate paymentdrill-down screens and review the information.

a) To check the data:

1. Select Rebate payments→ Sales volume.2. Select Rebate payments→ Rebate documents.3. Select Rebate payments→ Drill-down.

224 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Lesson: Rebates

Lesson Summary

You should now be able to:� Describe the entire rebate processing procedure� Create rebate agreements� Perform rebate settlements� Control rebate processing in Customizing

2006/Q2 © 2005 SAP AG. All rights reserved. 225

Unit Summary SCM620

Unit SummaryYou should now be able to:� Describe the criteria taken into account to determine taxes� Describe how taxes are determined for each order item� Use agreements to implement and evaluate marketing projects� Describe the entire rebate processing procedure� Create rebate agreements� Perform rebate settlements� Control rebate processing in Customizing

226 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

Test Your Knowledge

1. Discuss the factors that play a role in determining tax rates.

2. The tax procedure is assigned in the defaults for Financial Accountingaccording to country.Determine whether this statement is true or false.□ True□ False

3. The release status of a sales deal controls where you can find the conditionrecords for a sales agreement.Determine whether this statement is true or false.□ True□ False

4. What are the prerequisites for rebate processing?

5. refers to an open rebate agreement.Fill in the blanks to complete the sentence.

6. Accruals are reversed automatically when a credit memo is created if therebate agreement type is set accordingly in Customizing.Determine whether this statement is true or false.□ True□ False

2006/Q2 © 2005 SAP AG. All rights reserved. 227

Test Your Knowledge SCM620

Answers

1. Discuss the factors that play a role in determining tax rates.

Answer: The following factors play a role in determining tax rates:

� Business transaction � domestic or export/import� Tax liability of the ship-to party� Tax liability of the material

2. The tax procedure is assigned in the defaults for Financial Accountingaccording to country.

Answer: True

The tax procedure is assigned in the defaults for Financial Accountingaccording to country. For example, for the United States, the options areTAXUS and TAXUSJ.

3. The release status of a sales deal controls where you can find the conditionrecords for a sales agreement.

Answer: True

The release status of a sales deal controls where you can find the conditionrecords for a sales agreement. For example, if the sales deal has status B,the condition records are included in pricing simulation but are not used inthe current documents.

4. What are the prerequisites for rebate processing?

Answer: To function properly, rebate processing must be activated for:·

� The sales organization� The payer master� The billing document typeTo enhance the performance, you should deactivate rebate processing if itis not necessary.

5. Status A refers to an open rebate agreement.

Answer: Status A

228 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Test Your Knowledge

6. Accruals are reversed automatically when a credit memo is created if therebate agreement type is set accordingly in Customizing.

Answer: True

Accruals are reversed automatically when a credit memo is created if therebate agreement type is set accordingly in Customizing.

2006/Q2 © 2005 SAP AG. All rights reserved. 229

Course Summary SCM620

Course SummaryYou should now be able to:

� Describe the elements of the pricing condition technique and the relationshipsbetween them

� Convert your pricing requirements to the necessary pricing strategy� Make the necessary Customizing settings to implement your pricing strategy

230 © 2005 SAP AG. All rights reserved. 2006/Q2

Appendix 1Appendix

Figure 95: Appendix

Figure 96: Table Structure: Conditions in Pricing

2006/Q2 © 2005 SAP AG. All rights reserved. 231

Appendix 1: Appendix SCM620

The tables above contain the following information:

� Annn: Condition table� KONH: Condition header� KONA: Agreement (only with rebate)� KONP: Condition item� KONM: Quantity scale� KONW: Value scale� Note:

KONM and KONW are never available at the same time.

Figure 97: Table Structure: Sales Document

VBUK: SD document: Header status and management data

VBAK: Sales document: Header data

VBKD: Sales document: Business data

VBUP: SD document: Item status

VBAP: Sales document: Item data

VBEP: Sales document: Schedule line data

VBPA: Sales document Partners

SADR: Address

VBFA: SD document flow

KONV: Conditions

232 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Appendix 1: Appendix

NAST: Output

STXH: Texts: Header

STXL: Texts: Lines

VBUV: Incompletion log

Figure 98: Table Structure: Billing Document

VBUK: Header status and management data

VBRK: Billing document: Header data

VBRP: Billing document: Item data

VBPA: SD document: Partners

SADR: Address

VBFA: SD document flow

KONV: Conditions

NAST: Output

STXH: Texts: Header

STXL: Texts: Lines

2006/Q2 © 2005 SAP AG. All rights reserved. 233

Appendix 1: Appendix SCM620

Figure 99: Master Data in IDES for SCM620 Pricing

Figure 100: Optional Troubleshooting Exercise

Exercise 23: Pricing Troubleshooting

Exercise Duration: 30 minutes

Exercise Objectives

After completing this exercise, you will be able to:

� Analyze and correct problems in Customizing for pricing

Business Example

Occasionally, problems with pricing configuration may arise. You will practiceusing the analysis tools available in SAP system to detect and solve a varietyof problems.

Task

234 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Appendix 1: Appendix

As a member of the project team, you have been asked by your project manager totroubleshoot some problems in Customizing for pricing, which have only recentlyappeared when a standard order was created. You have been given a set of datato use for testing and some requirements that must be taken into account forsolving the problems.

1. Test by creating a standard order from the customer purchase order shownbelow.

TELEFAX

Customer: T-L67A##

PO number: ##-11

Requested delivery date: In one week

Material Quantity

T-AT3## 100

The test will be successful if the following requirements are met:

The order must use the proper pricing procedure, Z##PRC.

The price of the material must be determined by a PR00 condition recordwith a valid rate.

The ZF## discount must appear on the line item with a valid rate.

Repeat the first step until the requirements in the second step are met. Donot rely on the New pricing button to see the effect of changes you make inthe pricing configuration tables. Instead, begin from the Sales menu andre-enter the order each time.

This is the only way to ensure that all your improvements are taken intoaccount.

Solution 23: Pricing Troubleshooting

Task

As a member of the project team, you have been asked by your project manager totroubleshoot some problems in Customizing for pricing, which have only recentlyappeared when a standard order was created. You have been given a set of datato use for testing and some requirements that must be taken into account forsolving the problems.

1. Test by creating a standard order from the customer purchase order shownbelow.

TELEFAX

Customer: T-L67A##

PO number: ##-11

2006/Q2 © 2005 SAP AG. All rights reserved. 235

Appendix 1: Appendix SCM620

Requested delivery date: In one week

Material Quantity

T-AT3## 100

The test will be successful if the following requirements are met:

The order must use the proper pricing procedure, Z##PRC.

The price of the material must be determined by a PR00 condition recordwith a valid rate.

The ZF## discount must appear on the line item with a valid rate.

Repeat the first step until the requirements in the second step are met. Donot rely on the New pricing button to see the effect of changes you make inthe pricing configuration tables. Instead, begin from the Sales menu andre-enter the order each time.

This is the only way to ensure that all your improvements are taken intoaccount.

a)

Caution: Only look at the solutions after you have tried toresolve the problems using the tools available to you.

Your instructor has made changes to your group�s pricing configurationtables, which result in a variety of symptoms. Now, you have a list ofall the symptoms you may observe and their causes.

Symptom: Pricing procedure Z##PRC is not used to price the order.

Cause: In the pricing procedure determination table, the procedureselected when using order type OR, sales area 1000 10 00, andcustomer T-L67A## has been changed to RVAA01. The correct valueis pricing procedure Z##PRC.

Symptom: PR00 condition record does not appear on the itemcondition screen.

Cause: In pricing procedure Z##PRC, on the PR00 line, therequirement has been changed from 2 to 11. Since the line item doesnot meet requirement 11, the condition is ignored. The correct value forthe requirement field is 2.

Symptom: Condition ZF## appears on the order, but without a rate.The pricing condition analysis lists a message for ZF## of �Conditionhas been found (without condition record)�.

Cause: In condition type ZF##, the Access sequence field is blank. Thecorrect value for the Access sequence field is ZA##.

236 © 2005 SAP AG. All rights reserved. 2006/Q2

SCM620 Appendix 1: Appendix

Symptom: When the correct value (ZA##) is entered into the Accesssequence field of condition type ZF##, the system responds with amessage: �E: An access sequence has not been assigned for the headercondition.�

Cause: Condition type ZF## is marked as a header condition. This isan error. It should be marked as an item condition.

Symptom: On the pricing detail screen for the item, both PR00 andZF## are displayed with rates, but the PR00 rate is not being used asthe price. Instead, the ZF## rate is being used.

Cause: Condition type ZF## has a value of B (Prices) in theCondition class field. This causes it to be used as a price, overridingthe PR00 record since ZF## occurs at a later step in the pricingprocedure. The correct value for the Condition class field should beA (discounts/surcharges).

Recommended Follow-up Activities

� Go through the exercises using IDES data or your own data� Read on-line documentation� Read IMG documentation� Read release notes

2006/Q2 © 2005 SAP AG. All rights reserved. 237

Appendix 1: Appendix SCM620

238 © 2005 SAP AG. All rights reserved. 2006/Q2

Appendix 2Exercise Data

Data used in the Exercises

Data for each group has been created in the system for the exercises.

Where you see Substitute## Your group number (01,02, ...,19, 20)

Type of Data Data in Training SystemSales organization 1000DistrChannel 10Divis. 00Plant 1200Shipping point 1200Warehouse number 012Customer 1 T-L67A##Customer 2 T-L67B##Material 1 T-AT1##Material 2 T-AT2##Material 3 T-AT3##

2006/Q2 © 2005 SAP AG. All rights reserved. 239

Appendix 2: Exercise Data SCM620

240 © 2005 SAP AG. All rights reserved. 2006/Q2

IndexAAccess sequence, 20, 49�50,55

CCalculation formula, 152, 175Calculation type, 90Condition, 114, 151Condition category, 173Condition indices, 88Condition maintenance, 5,83�84

Condition records, 2�3, 49,85�86, 116

Condition supplements, 117Condition table, 20, 48, 55Condition type, 4, 51, 55, 152,175

Condition types, 115Customer hierarchy, 154�155DData determination, 140�141DIFF, 159Document header, 24GGroup condition, 113HHierarchy accesses, 135�136Hierarchy nodes, 154IInterval scales, 153MMinimum price, 153Minimum value, 152NNet price, 151

Net price list, 87New pricing, 26OOrder value, 151PPallet discount, 157Partial rebate settlements, 207Price book, 140Pricing agreement, 3Pricing procedure, 19, 52, 55,173�174

Pricing reports, 81�82Pricing type, 25Procedure determination, 53,55

Promotion, 190�191RRebate agreement, 200�201Rebate agreement types, 200Rebate processing, 202Rebate settlement, 206Rebates, 202Release procedure, 89Retroactive rebateagreements, 209

Rule, 185SSales deal, 191Settlement run, 202TTax rate, 186Taxes, 186�187

2006/Q2 © 2005 SAP AG. All rights reserved. 241

Index SCM620

242 © 2005 SAP AG. All rights reserved. 2006/Q2

FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.

2006/Q2 © 2005 SAP AG. All rights reserved. 243