LO521 Pricing in Purchasing 46C

LO521 Pricing in Purchasing LO521

Release 46C 12.12.2002

LO521 Pricing in Purchasing ................................................................................................................................. 0-1

Copyright ........................................................................................................................................................... 0-2 Materials Management................................................................................................................................... 0-3 Course Prerequisites....................................................................................................................................... 0-4 Target Group.................................................................................................................................................. 0-5

Course Overview................................................................................................................................................ 1-1 Course Goals .................................................................................................................................................. 1-2 Course Objectives .......................................................................................................................................... 1-3 Course Content............................................................................................................................................... 1-4 Course Overview Diagram............................................................................................................................. 1-5 Main Business Scenario ................................................................................................................................. 1-6

Elements of the Condition Technique ................................................................................................................ 2-1 Elements of the Condition Technique: Objectives......................................................................................... 2-2 Elements of the Condition Technique: Scenario ............................................................................................ 2-3 Elements of the Condition Technique: Overview .......................................................................................... 2-4 Conditions ...................................................................................................................................................... 2-5 Time-Dependent Conditions .......................................................................................................................... 2-6 Condition Types............................................................................................................................................. 2-7 Condition Records and Condition Tables ...................................................................................................... 2-8 Access Sequence ............................................................................................................................................ 2-9 Calculation Schema...................................................................................................................................... 2-10 Sequence of Conditions................................................................................................................................ 2-11 Elements of the Condition Technique: Summary ........................................................................................ 2-12 Exercise Data Sheet ..................................................................................................................................... 2-13 Elements of the Condition Technique Exercises.......................................................................................... 2-14 Elements of the Condition Technique Solutions .......................................................................................... 2-20

Price Determination ........................................................................................................................................... 3-1 Price Determination: Unit Objectives ............................................................................................................ 3-2 Price Determination: Business Scenario ........................................................................................................ 3-3 Price Determination: Overview Diagram....................................................................................................... 3-4 Price Determination Process: Overview ........................................................................................................ 3-5 Schema Determination ................................................................................................................................... 3-6 Calculation Schema for Condition Type PB00 .............................................................................................. 3-7 Access Sequence for Gross Price ................................................................................................................... 3-8 Conditions For Several Purchasing Organizations......................................................................................... 3-9 Validity Periods and Pricing Date................................................................................................................ 3-10 Scales ........................................................................................................................................................... 3-11 Info Record and Order Price History ........................................................................................................... 3-12 Conditions Adopted from Last Purchase Order ........................................................................................... 3-13 Condition Types PB00 and PBXX............................................................................................................... 3-14 Price Determination: Unit Summary............................................................................................................ 3-15 Price Determination Exercises ..................................................................................................................... 3-16 Price Determination Solutions ..................................................................................................................... 3-22

Header and Group Conditions............................................................................................................................ 4-1 Header and Group Condition: Unit Objectives .............................................................................................. 4-2 Header and Group Conditions: Business Scenario......................................................................................... 4-3 Header and Group Conditions: Overview Diagram ....................................................................................... 4-4 Header, Group, and Item Conditions ............................................................................................................. 4-5 Header Conditions.......................................................................................................................................... 4-6

Group Conditions and Scales ......................................................................................................................... 4-7 Group Conditions and Print Indicator ............................................................................................................ 4-8 Condition Group ............................................................................................................................................ 4-9 Header and Group Conditions: Unit Summary ............................................................................................ 4-10 Header and Group Conditions Exercises...................................................................................................... 4-11 Header and Group Conditions Solutions...................................................................................................... 4-16

Maintaining Conditions...................................................................................................................................... 5-1 Maintaining Conditions: Unit Objectives....................................................................................................... 5-2 Maintaining Conditions: Business Scenario................................................................................................... 5-3 Maintaining Conditions: Overview Diagram................................................................................................. 5-4 Maintaining Time-Dependent Conditions 1................................................................................................... 5-5 Maintaining Time-Dependent Conditions 2................................................................................................... 5-6 Validity Periods.............................................................................................................................................. 5-7 Collective Changes ........................................................................................................................................ 5-8 Changing Conditions using a Condition Index .............................................................................................. 5-9 Automatic Adjustment - Changes to Conditions.......................................................................................... 5-10 Change Documentation................................................................................................................................ 5-11 Change Options Within Document .............................................................................................................. 5-12 Data Protection Through User Authorizations ............................................................................................. 5-13 Maintaining Conditions: Unit Summary ...................................................................................................... 5-14 Maintaining Conditions Exercises ............................................................................................................... 5-15 Maintaining Conditions Solutions................................................................................................................ 5-18

Special Condition Types and Special Functions ................................................................................................ 6-1 Unit Objectives .............................................................................................................................................. 6-2 Unit Business Scenario .................................................................................................................................. 6-3 Overview Diagram......................................................................................................................................... 6-4 Delivery Costs................................................................................................................................................ 6-6 Pallet Discount/Incomplete Pallet Surcharge ................................................................................................. 6-7 Weight- and Volume-Dependent Conditions ................................................................................................. 6-8 Condition Exclusion Procedure...................................................................................................................... 6-9 Unit Summary.............................................................................................................................................. 6-10

Special Condition Types and Special Functions Exercises....................................................................................................................................... 6-11

Special Condition Types and Special Functions Solutions .......................................................................... 6-18 Subsequent (End-of-Period Rebate) Settlement................................................................................................. 7-1

Subsequent Settlement: Unit Objectives ........................................................................................................ 7-2 Subsequent Settlement: Business Scenario .................................................................................................... 7-3 Subsequent Settlement: Overview Diagram................................................................................................... 7-4 End-of-Period Rebates: Overview ................................................................................................................. 7-5 Prerequisites ................................................................................................................................................... 7-6 Conditions in Rebate Arrangements .............................................................................................................. 7-7 Cumulative Updating of Business Volumes .................................................................................................. 7-8 Comparison/Agreement of Business Volumes............................................................................................... 7-9 Settlement .................................................................................................................................................... 7-10 Extension of Rebate Arrangements.............................................................................................................. 7-11 Retrospective Compilation of Statistics ....................................................................................................... 7-12 Subsequent Settlement: Unit Summary........................................................................................................ 7-13

Subsequent (End-of-Period Rebate) Settlement Exercises....................................................................................................................................... 7-14

Subsequent (End-of-Period Rebate) Settlement Solutions ....................................................................................................................................... 7-17

Customizing ....................................................................................................................................................... 8-1 Customizing: Unit Objectives ........................................................................................................................ 8-2 Customizing: Business Scenario .................................................................................................................... 8-3 Customizing: Overview Diagram................................................................................................................... 8-4 Overview........................................................................................................................................................ 8-5 Customizing: Calculation Schema ................................................................................................................. 8-6 Customizing: Condition Type ........................................................................................................................ 8-7 Customizing: Access Sequences .................................................................................................................... 8-8 Customizing: Condition Tables...................................................................................................................... 8-9 Routines: Formulas and Requirements ........................................................................................................ 8-10 Adjusting the System ................................................................................................................................... 8-11 Customizing: Unit Summary........................................................................................................................ 8-12 Customizing Exercises ................................................................................................................................. 8-13 Customizing Solutions ................................................................................................................................. 8-17

Conclusion ......................................................................................................................................................... 9-1 Course Objectives .......................................................................................................................................... 9-2 Recommended Follow-up Courses ................................................................................................................ 9-3 Recommended Follow-up Activities.............................................................................................................. 9-4

Appendix.......................................................................................................................................................... 10-1 Frequently-used Menu Paths........................................................................................................................ 10-2

� SAP AG 1999

LO521 Pricing in Purchasing

� SAP AG

��R/3 System ��Release 4.6C ��August 2000 ��Material number 5004 0956

� SAP AG 2001

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

All rights reserved.

Copyright

Trademarks: ��Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors. ��Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered

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. ��HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide

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, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,

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

� SAP AG 1999

Materials Management

Processes inProcurement

LO020 5 days

Inventory ManagementLO510 3 days

Invoice Verification3 daysLO515

Consumption-BasedPlanning and Forecasting

LO525 2 days

Procurement of External Services

LO540 2 days

Foreign TradeLO640 3 days

QM in ProcurementLO715 2 days KANBAN

LO235 2 days

Batch ManagementLO955 3 days

Pricing in Purchasing2 days LO521

Cross-FunctionalCustomizing in MM

5 days LO550

Purchasing Details andOptimization

LO520 3 days

Cross Application Business Processes in SD and MM

LO925 2 days

Level 2 Level 3

� SAP AG 1999

Course Prerequisites

� Essential:

� LO020�Processes in Procurement

� Recommended:

� LO520�Purchasing Details and Optimization

� LO550�Cross-Functional Customizing in Materials Management

� Participants should be thoroughly familiar with the Purchasing area. Ideally, they should also have some knowledge of the Customizing functionality for this area.

� SAP AG 1999

Target Group

� Audience:

� Project team members responsible for pricing and purchasing.

� Duration: 2 days

Notes to the user ��The training materials are not teach-yourself programs. They complement the course

instructor's explanations. On the sheets, there is space for you to write down additional information.

(C) SAP AG LO521 1-1

� SAP AG 1999

� Course Goals

� Course Objectives

� Course Content

� Course Overview Diagram

� Main Business Scenario

Contents:

Course Overview


� SAP AG 1999

� Carry out price determination functions in purchasing

� Configure the IMG settings for price determination

Course Goals

This course will prepare you to:


� SAP AG 1999

� Outline the various elements of the condition technique and define how they interact

� Maintain conditions at different levels

� Describe how the process of price determination works in the system

� Recognize the special condition types that can be used in price determination

� Define the subsequent settlement process

� Create condition types and calculation schemas, and customize the price determination process

Course Objectives

At the conclusion of this course, you will be able to:


� SAP AG 1999

Unit 6 Special Condition Types and Special Functions *

Unit 7 Subsequent (End-of-Period Rebate) Settlement

Unit 8 Customizing

Unit 9 Conclusion

Unit 1 Course Overview

Unit 2 Elements of the Condition Technique

Unit 3 Price Determination

Unit 4 Header and GroupConditions

Unit 5 Maintaining Conditions

Preface

Appendices

Course Content

* If time is short, some of the topics covered in this unit may be omitted. Information on the topics in this unit is available in the text and in the documentation.


� SAP AG 1999

Course Overview Diagram

Course Overview

Elements of theCondition Technique

Price Determination

Header and GroupConditions

Maintaining Conditions

Special Condition Types and Special Functions *

Customizing

Subsequent (End-of-Period Rebate) Settlement

Conclusion


� SAP AG 1999

� A vendor’s price for a material is often made up of different components. Your vendor may offer to sell you a material at a certain price, but additional factors may affect what you pay. Prices, discounts and surcharges, freight costs, and the like are represented in the system as pricing conditions. The conditions are applied in order to arrive at the net and effective purchase prices in purchase orders. Settings made in Customizing define the details of the conditions and price determination process.

Main Business Scenario


� SAP AG 1999

� Condition Types

� Condition Records and Tables

� Access Sequences

� Calculation Schemas

Elements of the Condition Technique

Contents:


� SAP AG 1999

� Describe the elements of the condition technique and their interaction

� Examine differences between and maintenance of time-dependent and time-independent conditions

� Define important control parameters for condition types and calculation schemas

At the conclusion of this unit, you will be able to:

Elements of the Condition Technique: Objectives


� SAP AG 1999

� Your purchasing department needs a method for storing and determining the purchase prices for materials.

Elements of the Condition Technique: Scenario

��In the R/3 System, the condition technique is used to determine purchase and valuation prices. This technique is based on conditions that are described by condition types, stored in condition records and tables, found by means of access sequences and arranged in calculation schemas.


� SAP AG 1999

Elements of the Condition Technique: Overview

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Conditions

Discounts and surchargesPrices

Contract

Info record

Scheduling agreement

Quotation

Percentage, quantity-dependent,or absolute discounts/surcharges

Freight charges

Cash discounts

End-of-period rebates

Conditions

��Conditions are stipulations agreed with vendors regarding prices, discounts and surcharges and suchlike. The system determines the effective net purchase price in POs on the basis of these pricing elements.

��Conditions can be maintained when you enter or create quotations, info records, outline purchase agreements, and purchase orders.

��MM Purchasing differentiates between the following prices: - Gross price: Price excluding any possible discounts or surcharges - Net price: Price taking discounts, surcharges, and possibly taxes into account - Effective price: Net price less or plus delivery (incidental procurement) costs, cash discount,

and miscellaneous provisions for accrued costs or rebates. ��Discounts or surcharges may be percentage-based, quantity-dependent, or absolute in nature. ��You can also enter conditions that do not take effect immediately, at the time of individual

transactions, but subsequently thereto, and which require settlement at the end of a predefined period.

��In MM Purchasing, a distinction is made between conditions that are valid for a certain period (time-dependent conditions) and conditions for which no special validity period can be defined (time-independent conditions).

��Prior to Release 4.0A, the term Master conditions was used in place of the term "time-dependent conditions", and the term Document conditions was used for "time-independent conditions".


� SAP AG 1999

Surcharge 5%

From 100 pc 3%

Time-Dependent Conditions

Outl. purchase agreement

General conditionsVendorCondition groupMaterial typeIncotermsInvoicing partyOther

DMDMFFFF$$

Upper limit 5%

Lower limit 1%

pc%

Conditions

$Info record

Price 1 Price 2

01.01. 12.31.07.01.

Purch. organizationPlant Ref. purch. organization

��Conditions in info records and contracts are always time-dependent. You can specify in Customizing (via the document type) whether time-dependent or time-independent conditions can be maintained in quotations and scheduling agreements. As of Release 4.0A, the standard settings are time-dependent conditions for both scheduling agreements and quotations.

��Conditions in purchase orders are always time-independent conditions. ��Time-dependent conditions can be stored on either a plant-specific or a cross-plant basis (in the latter

case, for all plants belonging to a purchasing organization). You can also use conditions negotiated by another purchasing organization (reference purchasing organization).

��In addition to time-dependent conditions that apply to individual info records, or quotation or outline agreement items, you can also define time-dependent conditions reflecting more general pricing arrangements (general conditions).

��Time-dependent conditions can be limited to a certain validity period. ��If a vendor's pricing varies according to the quantity purchased, you can enter it in the form of a

price/quantity scale. ��You can specify upper and lower limits for time-dependent conditions in order to prevent agreed

maximum or minimum figures from being exceeded in the event that condition values are changed manually in the purchase order.

��Valid time-dependent conditions from info records or outline purchase agreements are adopted as default values in purchase orders.


� SAP AG 1999

Condition Types

Key Description Control

PB00

FRB1

SKTO

Gross price

Freight, absolute

Cash discount

Condition class: PricesCalculation type: Quantity-dependentCondition cat.: Base priceAccess sequence: Gross price

Condition class: Discount/surchargeCalculation type: Fixed amountCondition cat.: Delivery costs

Condition class: Discount/surchargeCalculation type: PercentageCondition cat.: Cash discount

��The individual conditions are described by means of condition types. There are condition types for the gross price, various discounts and surcharges, freight charges, fixed costs and so on.

��Condition types are defined together with their control parameters in Customizing. ��Condition types are differentiated broadly using the condition class and more finely using the

condition category. ��The calculation type (or rule) stipulates how the R/3 System calculates the condition value. For

example, a discount or surcharge can be a percentage of the gross price, a fixed amount or a quantity-dependent amount.

��The plus/minus sign determines whether a condition is treated as a negative or positive amount. Negative amounts are discounts (deductions), positive amounts are surcharges (additions).

��The scale basis (or reference magnitude) for scales also depends on the condition type. A scale can be based on quantity or dollar value, for example.

��An access sequence may be assigned to a condition type. The access sequence is a search strategy that enables you to specify the order in which condition tables are to be searched for relevant entries for a condition type. In the standard R/3 System, no access sequences are assigned to the condition types for discounts and surcharges (RA00, RA01 and so on.) because they do not have separate validity periods. They are always maintained at the same time as the gross price (PB00) and their validity period is always the same as the validity period of the gross price.

��You can define your own condition types.


� SAP AG 1999

4321

Condition Records and Condition Tables

Condition table A017 (info record with plant)

Cond. ty. Vendor Material Pur. org. Plant . . . Cond. rec. no.

PB00 A 1 1000 1000 1234

Condition table A018 (info record without plant)

Cond. ty. Vendor Material Pur. org. . . .

PB00 A 1 1000

Cond. rec. no.

4321. . .

Table KONP (item conditions)

Cond. rec. no.

1234

PB00 . . .

Cond. ty. . . .

PB00 . . .

11.00

Cond. amount

10.00

. . .

. . .

. . .

. . .

��Conditions are stored in the system as condition records. ��Condition tables reference condition records. Condition tables enable you to vary the key structure of

condition records. ��There are condition tables with the following key fields

��Vendor, material, purchasing organization, info record category ��Vendor, material, purchasing organization, plant, info record category ��Vendor, material, purchasing organization, info record category, order unit ��Purchasing document, item, plant

��Entries in condition tables consist of a key part and a data part. The data part contains the number of a condition record.

��Condition records are stored in the following transparent tables ��KONP (time-dependent conditions) ��KONH (header conditions) ��KONM (quantity scales) ��KONW (value scales)


� SAP AG 1999

Access Sequence

Cond. ty.

PB00

Control

Access sequence 0002

Access sequence

0002

No.

10

20

Condition table

. . .

A017 (Info record w. plant)

A018 (Info rec. w/o plant)

30

Exclusive

��An access sequence can be assigned to a condition type. ��An access sequence is a search strategy that enables you to specify the order in which condition

tables are to be searched for relevant entries for a condition type. In the case of a price, for example, you can specify that the R/3 System is first to search for a plant-specific price – it is to search for a general, cross-plant price only if it cannot find a plant-specific one.

��The order of the accesses is determined by the order of the condition tables in the access sequence. ��The Exclusive indicator determines that the search for further valid entries in (other) condition tables

is interrupted if an access was successful and a relevant entry was found. ��You define the prerequisites according to which the R/3 System searches certain condition tables for

relevant entries using requirement routines. Certain condition tables are accessed only if the document item satisfies certain criteria.

��A condition type must have an access sequence assigned to it if you want to maintain conditions with their own validity periods (for example, condition type PB00).

��In the standard R/3 System, no access sequence is assigned to the condition types for discounts and surcharges (RA00, RA01and so on) because they do not have a separate validity period. They are always maintained at the same time as the gross price (PB00) and have the same validity period as the latter.

��You cannot assign an access sequence to a header condition.

(C) SAP AG LO521 2-10

� SAP AG 1999

Calculation Schema

Step

1

Counter

1

Cond. ty.

PB00

10 1 RB00

. . . . . . . . .

10 9 ZA01

. . . . . . . . .

20 0

. . . . . . . . .

31 1

. . . . . . . . .

FRA1

35 1

40 0

SKTO

Fr. . . .

1

20

20

Description

Gross price

Absolute discount

Freight %

Cash discount

Effective price

% Surcharge on gross X

StatManu.

X

X

Net value incl. discount

X

X

��In MM, the framework for determining the purchase or valuation price is “price calculation schema”, which groups together all the condition types that are relevant to this process. (Note that in the SD area such calculation schemas may be referred to as “pricing procedures”.)

��Among other things, the calculation schema defines the: ��Permissible condition types ��Condition types for which conditions are adopted automatically (Manu. indicator) ��Condition types for which the net price calculation is applied (Stat. indicator) ��Order in which the condition types are taken into account in the calculation of the net or effective

price ��Condition types for which subtotals are calculated ��Requirements that must be satisfied before a certain condition type is taken into account

��In addition, the From reference step for percentage conditions is defined in the calculation schema. The From reference step can be combined with a To reference step.

(C) SAP AG LO521 2-11

� SAP AG 1999

Sequence of Conditions

Calculation schemaStep10101010...

Cnt.1234

C.ty.RB00RC00RA00RA01

DescriptionAbs. discountDiscount/qty.% disc. on net% disc. /gross

Conditions for item 10C.ty.PB00RA00RB00

DescriptionGross price% disc. on netAbs. discountNet value

Amount100.00

2%10.0088.00

Pur. order


Cnt.0000

C.ty.RB00RC00RA00RA01

DescriptionAbs. discountDiscount/qty.% disc. on net% disc./gross.

Conditions for item 10C.ty.PB00RB00RA00

DescriptionGross priceAbs. discount% disc. on net Net value

Amount100.0010.00

2%88.20

Pur. order

��The step numbers of the condition types in the calculation schema determine the sequence (order) in which the condition types are taken into account in the calculation of the net or effective price. This sequence cannot be changed in the document even if the condition types are entered manually.

��Condition types assigned to the same step in the calculation schema are sorted by means of a counter. With these condition types, the order of manual entry decides the point at which the condition type is taken into account in the calculation of the net or effective price.

(C) SAP AG LO521 2-12

� SAP AG 1999

� Describe the elements of the condition technique and their interaction

� Examine differences between and maintenance of time-dependent and time-independent conditions

� Define important control parameters for condition types and calculation schemas

You are now able to:

Elements of the Condition Technique: Summary

(C) SAP AG LO521 2-13

Exercise Data Sheet Key to Icons in Exercises and Solutions

Exercises

Solutions

Objectives

Business Scenario

Hints and Tips

Warning or Caution

Data Used in Exercises Type of Data Data in Training System Company code 1000 (IDES AG 1000) Purchasing organization 1000 (IDES Deutschland) Plants 1000 (Hamburg),

1100 (Berlin), 1200 (Dresden)

Storage location 0001 (Materiallager) Purchasing group Z21 (LO521 Buyer) Materials T-REK## T-REL##

T-REM## T-REN## Material group ZT21 (LO521 Material Group)

Vendors T-L21A## T-L21B## T-L21C## T-L21D## T-L21E##

G/L account 400000 Cost center T-L20

(C) SAP AG LO521 2-14

Elements of the Condition Technique Exercises

Unit: Elements of the Condition Technique

At the conclusion of this exercise, you will be able to:

�� Describe the elements of the condition technique and their interaction

�� Examine differences between, and maintenance of, time-dependent and time-independent conditions

�� Define important control parameters for condition types and calculation schemas

Your purchasing department needs a method for storing and determining purchase prices for materials. In the R/3 System, the condition technique is used to determine purchase and valuation prices. This technique is based on conditions that are described by condition types, stored in condition records and condition tables, found by means of access sequences, and arranged in calculation schemas.

1-1 Create an info record with the following data: Vendor: T-L21A## Material: T-REK## Purchasing organization: IDES Deutschland (1000) Planned delivery time: 10 days Purchasing group: Z21 (LO521 Buyer) Standard quantity: 100 Gross price: 9.90 UNI (from 1 pc)

9.50 UNI (from 100 pc) 9.00 UNI (from 500 pc)

Discount % on net: 1% (from 1 pc) 2% (from 500 pc) Freight (value): 50.00 UNI

The conditions are valid until the end of next year.

(C) SAP AG LO521 2-15

1-1-1 What condition types do you use?

Condition Condition type

Gross price

Discount % on net

Freight (value)

1-1-2 Add the task from the above exercise to your Favorites.

1-2 Vendor T-L21A## also grants a scaled discount on all materials for a limited period of time:

�� 3% from a value of 1000 UNI upwards

�� 4% from a value of 5000 UNI upwards

�� 5% from a value of 9000 UNI upwards The discount is valid for a period of four weeks, starting today.

Maintain the vendor discount for purchasing organization 1000.

If a discount or surcharge is to apply only from a certain value upwards, you should insert a zero line in the scale, for example: From 0.00 UNI: 0% From 1000.00 UNI: 3%

1-2-1 Add this task to your Favorites.

1-3 Now create a purchase order:

Vendor: T-L21A##

Purchasing organization: IDES Deutschland (1000)

Purchasing group: LO521 Buyer (Z21)

Delivery date: In 2 weeks (applies to both items)

Item 1: Order 120 pc of material T-REK## for plant 1000.

Item 2: Order 560 pc of material T-REK## for plant 1100. 1-3-1 Must you enter an order price?

______________________________________________________

1-3-2 Check the conditions for both items and determine the amounts/percentages for each:

(C) SAP AG LO521 2-16

Item 10 Item 20

Gross price (per 1 pc)

Discount % on net

Vendor discount

Net price (per 1 pc)

Freight surcharge

Cash discount

Actual price (per 1 pc)

1-3-3 Trace the origin of the condition values by displaying the master data for the condition records:

Item 10 Item 20

Gross price

Discount % on net

Vendor discount

Freight surcharge

Cash discount

Save your purchase order.

Purchase order number: ___________________


(C) SAP AG LO521 2-17

1-4 Display the Customizing settings and determine the specified control parameters for the following condition types:

Condition type

Access sequence

Condition class

Calculation type

Condition category

Plus/ minus

PB00

RA00

RB00

RC00

RL01

FRB1

SKTO

1-5 Create an additional info record:

Vendor: T-L21A##

Material: T-REL##


Planned delivery time: 10 days


Standard quantity: 100

For this material, you have negotiated the following conditions with your vendor, which are valid indefinitely:

Gross price: 120.00 UNI

Discount % on gross: 1%

Discount/quantity: 2.00 UNI (from 1 carton) 5.00 UNI (from 10 cartons) 10.00 UNI (from 50 cartons)

Be sure to scale the discount/quantity by carton, not pc.

Discount (value): 20.00 UNI (from 1 pc)

120.00 UNI (from 500 pc)

Discount % on net: 1.5%

1-5-1 What condition types did you use for the above conditions?

�� Gross price _________________________________

(C) SAP AG LO521 2-18

�� Discount % on gross _________________________________

�� Discount/quantity _________________________________

�� Discount (value) _________________________________

�� Discount % on net _________________________________

Save your info record.

*1-6 Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types:

Condition type Step Counter

RB00

RC00

RA00

RA01

HB01

RL01

RGR0

*1-7 Create a purchase order.

Vendor: T-L21A##



Delivery date: In 8 weeks

Order 500 pc of material T-REL## for plant 1000.

Check the conditions of your purchase order item and compare the sequence of the discount conditions with the sequence in your info record and in the calculation schema.

1-7-1 In which sequence are the discount conditions adopted in the purchase order?

______________________________________________________

Purchase order number: ______________________________________________________

(C) SAP AG LO521 2-19

(C) SAP AG LO521 2-20

Elements of the Condition Technique Solutions

Unit: Elements of the Condition Technique

1-1 SAP menu ��Logistics ��Materials Management ��Purchasing ��Master Data � Info Record � Create. Enter the vendor, material and purchasing organization on the initial screen. Be sure to leave the plant field blank.

From the Purch. Org data 1 screen, choose Conditions and enter the pricing conditions. Choose Scales on the Conditions screen to enter the scales.

1-1-1

Condition Condition type

Gross price PB00

Discount % on net RA00

Freight (value) FRB1 or 2

1-1-2 Select Favorites � Add.

1-2 SAP menu ��Logistics ��Materials Management ��Purchasing ��Master Data Conditions � Discounts/Surcharges � By Vendor.

Enter the vendor and purchasing organization, then choose Execute.

On the next screen, select the purchasing organization and choose Create.

Select the vendor line item and choose Scales and enter the scale.

1-2-1 Choose Favorites � Add.

1-3 SAP menu ��Logistics ��Materials Management ��Purchasing ��Purchase Order � Create � Vendor/Supplying Plant Known.. 1-3-1 No, the order price is adopted from your cross-plant info record.

(C) SAP AG LO521 2-21

1-3-2 Select the appropriate line item in the Item overview screen area and then select the Conditions tab in the Item details screen area.

Item 10 Item 20

Gross price (per 1 pc) 9.50 UNI 9.00 UNI

Discount % on net 1% 2%

Vendor discount 3% 4%

Net price (per 1 pc) 9.12 UNI 8.46 UNI

Freight surcharge 50.00 UNI 50.00 UNI

Cash discount 3% 3%

Actual price (per 1 pc) 9.26 UNI 8.30 UNI

1-3-3 Select the line item for each of the condition types and choose Master data condition record

Item 10 Item 20

Gross price Information record Information record

Discount % on net Information record Information record

Vendor discount Purchase org. / Vendor conditions

Purchase org. / Vendor conditions

Freight surcharge Information record Information record

Cash discount Information record Information record

1-3-4 Favorites � Add

(C) SAP AG LO521 2-22

1-4 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG � Materials Management � Purchasing � Conditions � Define Price Determination Process � Define Condition Types � Define Condition Types. Choose Define Condition Type.

Look at the detail screen for each of the condition types.

Condition type

Access sequence

Condition class

Calculation type

Condition category

Plus/ sign

PB00 0002 B C H (blank)

RA00 (blank) A A (blank) X

RB00 (blank) A B (blank) X

RC00 (blank) A C (blank) X

RL01 0006 A A (blank) X

FRB1 (blank) A B B (blank)

SKTO (blank) A A E (blank)

Condition class: A = Discount or surcharge B = Prices Calculation type: A = Percentage B = Fixed amount C = Quantity-dependent Condition category: B = Delivery costs E = Cash discount H = Base price Plus/Minus: X = Negative, A = Positive, Blank(_) = positive and negative

1-5 Favorites � Purchasing � Master data � Info Record � Create.

1-5-1

�� Gross price PB00

�� Discount % on gross RA01

�� Discount/quantity RC00

�� Discount (value) RB00

�� Discount % on net RA00

*1-6 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG. IMG�� Materials management � Purchasing � Conditions � Define Price Determination Process � Define Calculation Schema.

(C) SAP AG LO521 2-23

Select RM0000, then choose Control data.

Condition type Step Counter

RB00 10 1

RC00 10 2

RA00 10 3

RA01 10 4

HB01 10 10

RL01 10 11

RGR0 10 13

*1-7 Favorites � Purchasing � Purchase Order � Create � Vendor/Supplying Pplant Known. 1-7-1 Since all discount condition types in the calculation schema are assigned to

the same step, their sequence in the purchase order is determined by the manual entry in the info record.


� SAP AG 1999

� Price Determination

� Schema Determination and Schema Groups

� Access Sequences for Gross Price

� Validity Periods for Pricing

� Conditions Adopted from Last Purchase Order

� Scales

� Condition type PB00 versus PBXX

Price Determination

Contents:


� SAP AG 1999

� Examine how the R/3 System finds the appropriate calculation schema

� Analyze the price determination process, taking into account different condition tables, validity periods and scales

� Create condition types and calculation schemas by copying existing data


Price Determination: Unit Objectives


� SAP AG 1999

� Your purchasing policy dictates that prices should automatically default into purchase orders whenever possible. Since you negotiate with vendors and agree on prices ahead of time, you often create info records to facilitate this process.

Price Determination: Business Scenario

��When a purchase order is created, the R/3 System finds the appropriate calculation schema and carries out the price determination process on the basis of the condition types contained therein. In doing so, it also takes into consideration scaled conditions and differing validity periods.


� SAP AG 1999

Price Determination: Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Price Determination Process: Overview


. . .Cond. type ...PB00

Condition type: PB00Access sequence: 0002

Access sequence: 0002Condition tables:1. Contract item (excl.)2. Plant info record (excl.)3. Info record (excl.)...

Purch. order

Pur. org. 1000Vendor A

For plant 1000Material 1

10 pc

Condition tableContract itemNo record exists

Condition tablePlant info recordMaterial 1 50.00From 500 pc 48.00

50.00

��When you create a purchase order, a contract release order, or a delivery schedule (under a scheduling agreement), the R/3 System searches existing info records and documents for valid conditions and adopts any it finds as default values in the new document.

��The price determination process is carried out in a number of steps: ��First, the relevant calculation schema is determined. ��The R/3 System then searches for condition records for all condition types listed in the calculation

schema that have an access sequence assigned to them. ��The search for condition records is carried out in the order specified in the access sequence. ��The search is concluded when a valid condition record is found.

��Material-specific discounts and surcharges are supplementary conditions linked to the gross price (condition type PB00). No access sequence is assigned to a supplementary condition in Customizing for the condition type. No separate price determination is carried out for supplementary conditions. They are found using the condition record for the gross price.


� SAP AG 1999

Customizing

Schema Determination

Schema gr.purch. org.

0001

0001

Schema gr.vendor

01

02

Calculation schema

RM0000

YM0000

ZM0000

XM0000

Purch. org.

2000

3000

Schema gr.

0001

0001

Purch. order

Pur. org. 1000

Vendor A

Vendor ASchema group 02

��You can predefine how the calculation schema is determined for standard POs and stock transport orders, the calculation of the market price in vendor evaluation and for external services management (as of Release 4.0A).

��You have the following options with regard to schema assignment for standard POs: ��You can assign a generally valid calculation schema (in the standard R/3 System, RM0000) ��You can make the assignment of a calculation schema dependent on a schema group for one or

more purchasing organizations and/or a schema group for one or more vendors. ��The schema group comprises those purchasing organizations or vendors to which the same

calculation schema is to be assigned. Schema groups are defined in Customizing. The assignment of purchasing organizations to schema groups is also made in Customizing, whereas the assignment of a vendor to a schema group must be made in the relevant vendor master record.

��Schema assignment for stock transport orders depends on the schema group of the purchasing organization, the document type and/or the supplying plant. Schema assignment for the calculation of the market price in vendor evaluation depends on the purchasing organization. The calculation schema for external services management depends on the document type. In this case, you should note that a uniform calculation schema per document type must be chosen for the documents RFQ/quotation (AN), purchase requisition (NB), and purchase order (NB).


� SAP AG 1999

Calculation Schema for Condition Type PB00

Calculation schema RM0000Step1...

Count.1

Cond. typePB00

Condition type PB00Condition classCalculation typeCalculation schema: RM0002...

Info record

Valid

Cond. typePB00GAU1RB00

Cond. value...

Propose condition supplements

Calculation schema RM0002Step1510...

Count.111

Cond. typePB00GAU1RB00

fromto

01.01. 12.31.

Pc.%

Conditions

$

Pc.%

Conditions

$

��A calculation schema for supplementary conditions must be assigned to condition type PB00 (or your own, comparable condition type for the gross price). In the standard R/3 System, schema RM0002 is used for this purpose.

��Condition types of this calculation schema are discounts and surcharges (RA00, RA01 and so on), and freight conditions (FRA1, FRB1 and so on), which can be valid for specific materials.

��The list of condition types suggested to you if you choose the Propose condition supplements function when maintaining info record conditions or conditions for quotation or outline agreement items is based on the calculation schema for supplementary conditions.

��The assignment facilitates the entry of discounts, surcharges and so on based on the info record or quotation or outline agreement item.

��Supplementary conditions have the same validity period as the main condition. ��In the standard R/3 System, no access sequence is usually assigned to the condition types of the

supplementary calculation schema because they do not have their own validity periods and are always maintained in conjunction with the gross price.

��The structure of the calculation schema assigned to the standard purchase order should correspond to that of the calculation schema for supplementary conditions.


� SAP AG 1999

Calculation schemaStep1

Condition typePB00

Purch. order

Pur. org.Vendor

For plantMaterial

Access Sequence for Gross Price

1000A

10001

Condition type PB00Access sequence: 0002

Access sequence 0002No.101520

253545...

Tab.681667

171828

Contract item, plant-dependentContract itemPlant info record per order unit

Material info record, plant-specificMaterial info recordInfo record for non-stock material

Requirement

Plant info record exists,variable order unit activePlant info record exists

Item without material

Condition tableNo. of condition record

��The access sequence is a search strategy defining the order in which condition tables are searched for relevant entries for a condition type. The order of accesses is determined by the order of the condition tables in the access sequence.

��A vendor’s gross price for a material can depend on a variety of factors. There are different condition tables with different combinations of key fields for the various price-influencing factors, for example: ��Table A068 – for gross prices in plant-specific outline agreement items ��Table A016 – for gross prices in the items of centrally agreed contracts ��Table A067 – for order-unit-dependent gross prices in plant-specific material info records ��Table A017 – for gross prices in plant-specific material info records ��Table A018 – for gross prices in material info records ��Table A025 – for gross prices in plant-specific non-stock-material info records (info records

without a material number). ��You can differentiate between gross prices, discounts and surcharges for different variants of a

configurable material. ��Requirement routines are used to determine the prerequisites by which the system searches certain

condition tables for relevant entries. Some condition tables are accessed only if the document item fulfills certain criteria.


� SAP AG 2001

Customizing enterprise structurePurch. Org. D Purch. org. EUR

- Contracts- Conditions

Purch. Org.EUR

Purch. Org. D

Release orderPurch. org. DMat. 1for plant

10,00 1000

Central contractPurch. org. EURMat. 1 10,00


10,00 2000


10,00 1000

Plant contractPurch. org. EURMat. 2for plant

10,00 1000

Conditions For Several Purchasing Organizations

Plant 1000:

Purch. Org.D

Plant 2000:

��Typically, each individual purchasing organization negotiates and maintains its own conditions. However, if your R/3 System has been set up appropriately, your purchasing organization can make use of the conditions negotiated by another (the reference purchasing organization) or make the conditions it has negotiated available to others. This is useful, for example, in the case of centrally agreed (national or corporate) contracts with vendors.

��In Customizing, a link must be set up between the relevant purchasing organizations. Furthermore, you must stipulate whether: ��It is permissible to issue release orders against contracts of the reference purchasing organization ��Conditions are to be adopted from info records of the reference purchasing organization, ��Conditions from info records of the reference purchasing organization are to take priority over

conditions from info records of your own purchasing organization. ��If the conditions are to be adopted from info records of the reference purchasing organization, you

must change the access sequences of the price determination process in such a way that accessing of the condition tables is carried out using the key of the reference purchasing organization.

(C) SAP AG LO521 3-10

� SAP AG 1999

Validity Periods and Pricing Date

Gross price01.01. - 03.31. 10.00

04.01. - 06.30. 10.20

07.01. - 09.30. 10.50

10.01. - 12.31. 10.80

Pricing date category

Pricing date =Current date

Pricing date = PO date

Pricing date =Delivery date

Purchase order 2Current date:PO date:Delivery date:

Price:

04.01.03.26.07.15.

10.00


Price:

04.0103.26.07.15.

10.50


Price:

04.01.03.26.07.15.

10.20

��Time-dependent conditions are always limited to a certain period of validity, which is defined by a start date and an end date. If you do not enter a validity period, the R/3 System suggests a period. The default validity period is controlled using Customizing.

��The price of the current validity period is always displayed in info records, outline purchase agreements and quotation.

��When a purchase order is created, the pricing date determines the validity period that is accessed. In the standard situation, the pricing date is the same as the document date of the PO. However, instead of the document date you can choose the current date, the delivery date, the GR date or a date entered manually in the PO.

��You can enter the pricing date category in the vendor master record or the purchasing info record as a default value, or enter an individual pricing date on the initial screen for the purchase order.

��The suggested pricing date category or pricing date can be changed in the PO item. However, price determination using a changed pricing date is not carried out automatically – it must be initiated manually on the condition screen.

��If you have chosen the delivery date as the pricing date, the delivery date of the first schedule line is taken in the case of items with several delivery dates (delivery schedule).

(C) SAP AG LO521 3-11

� SAP AG 1999

Scales

Price Surcharge

From 1 pc500 pc

1000 pc

100.00 UNI 99.00 UNI 96.00 UNI

To 500.00 UNI1000.00 UNI

50.00 UNI 30.00 UNI

Scale typeScale basis

(= From scale)(= Qty. scale)

Customizing condition type

Condition record (KONP)

Scale lines (KONM/KONW)

AC

Scale typeScale basis

BB

(= To scale)(= Value scale)

��A vendor’s gross price for a material (or a discount or surcharge) can vary – for example, according to the quantity ordered. In this case, you must enter the conditions in the form of a scale. Scaled conditions consist of one or more scale levels. Each scale level consists of a scale value and a scale amount depending on the latter. For example: ��Above 1000pc 96.00 UNI | Scale value | Scale basis | Scale amount |

��The first scale level should always start with 1 or 0, for example.: ��Gross price from 1 pc upwards 100.00 UNI; from 100 pc 99 UNI, ��Discount from 0 pc upwards 0 %; from 500 pc 2.5 %.

��The scale type and the scale basis for a scale are defined for the condition type in Customizing. Using the scale type, you specify whether the scale values of the condition represent the upper or lower limits for the price, discount or surcharge. There are ”From” scales (scale type A) and ”To” scales (scale type B). If no scale type has been assigned to a condition type in Customizing, you can specify whether the scale is to be maintained as a From or To scale before entering the lines of the scale. You specify how the R/3 System is to interpret the price scale for a condition by means of the scale basis. For example, the scale can relate to a money value (scale basis B), a quantity, (scale basis C) or a weight (scale basis D or E).

��Scaled conditions are stored in the tables KONM and KONW.

(C) SAP AG LO521 3-12

� SAP AG 1999

Info Record and Order Price History

Info record

Condition:

Valid:

10.00

01.01. - 06.30. Purch. order 123

Item Mat. Price10.50

Purchase order

Pricing date: 07.01.


Purchase order

Pricing date: 06.01.


Quotation inresponse to RFQ


Order price historyPO no. 123: 10.50

Order price historyPO no. 123: 10.50

��An info record can be created either manually or automatically (using the info update indicator). If an info record is created manually, the gross price and supplementary conditions can be maintained for a certain validity period. You can enter scales and upper and lower limits.

��If an info record is generated from a contract, the gross price and all supplementary conditions are adopted in the info record.

��If an info record is created from a PO or scheduling agreement, the conditions are adopted in the order price history not in the info record.

��If info record conditions exist and are valid, they are suggested (that is, they appear as default values) when a new PO is created. The conditions from the order price history (that is, the price and conditions of the last PO) are used as default values only if the R/3 System was unable to find any valid info record conditions.

��In info record list displays, a distinction is made between info record conditions (headword “condition”) and the conditions of the last PO (headword “purchase order”).

(C) SAP AG LO521 3-13

� SAP AG 1999

Conditions Adopted from Last Purchase Order

Last Purchase order 123

Item Mat. Price10 1 10.00

User Parameter EVO

New Purchase order

Item Mat. Price10 1 ?

��As of Release 4.5A, you can specify in the default values for buyers (user parameter EVO) how the R/3 System treats the conditions from the last purchase order.

��Using user parameter EVO, you can make the following settings: ��If the price determination process is unable to arrive at a valid price, the conditions are copied

from the last purchase order (as was the case prior to Release 4.5A). ��If you enter a price in the current purchase order manually, the conditions are not copied from the

last purchase order. ��The conditions are never copied from the last purchase order.

��In addition, you can specify whether or not the R/3 System is to apply a manually entered gross price during the price determination process. That is, if a price is entered manually and the R/3 System determines a different price after going through the price determination process, the R/3 System will not change the manually entered price.

(C) SAP AG LO521 3-14

� SAP AG 1999

Condition Types PB00 and PBXX

Purchase orderMat.1

PriceItem10

Conditions for item 10PB00RA01

100.005%

95.00

Info rec. conditionsPB00RA01

100.005%

Purchase orderMat.2

PriceItem10 ?

Conditions for item 20PB00PBXX 50.00

Please enter net price


Cnt.12

C. typePB00PBXX

Reqt.

Requirement 6Condition exclusion <> ‘X‘CHECK KOMP-KZNEP NE ‘X‘.

Condition type PB00...Exclusion = X...

6

��If you create an info record manually or automatically, the gross price entered or adopted is assigned to condition type PB00. When a PO is created without reference to a contract or quotation, a vendor’s gross price for a material is adopted from the info record conditions (or, where appropriate, from the order price history) as the default value for condition type PB00.

��If no valid info record conditions exist and no order price history can be found, the R/3 System is not able to suggest a price and requires the manual entry of a net price. The manually entered price is assigned to condition type PBXX.

��Two condition types for the gross price must be available in the calculation schema assigned to the standard purchase order. In the standard R/3 System, these are the condition types PB00 and PBXX. An access sequence is assigned to PB00, so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX. PB00 must be come before PBXX in the calculation schema. You can also use your own, comparable condition types in place of PB00 and PBXX.

��At the time a purchase order is created, if the R/3 System finds a condition record belonging to PB00 with valid conditions, PBXX is irrelevant. This is determined by the calculation schema. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).

(C) SAP AG LO521 3-15

� SAP AG 1999

� Examine how the R/3 System finds the appropriate calculation schema

� Analyze the price determination process, taking into account different condition tables, validity periods and scales

� Create condition types and calculation schemas by copying existing data


Price Determination: Unit Summary

(C) SAP AG LO521 3-16

Price Determination Exercises

Unit: Price Determination Topic: Customizing Settings


�� Examine how the R/3 System finds the appropriate calculation schema

�� Create condition types and calculation schemas by copying existing data

Your purchasing policy dictates that prices should automatically default into purchase orders whenever possible. Since you negotiate with vendors and agree on prices ahead of time, you often create info records to facilitate this process. When a purchase order is created, the R/3 System finds the appropriate calculation schema and carries out the price determination process.

1-1 Create a new condition type Z##A by copying the standard condition type PB00. Name your condition type LO521 Gross price ##.

Save your ondition type.

1-2 Read the IMG documentation for the node Define Calculation Schema.

1-3 Create a new calculation schema ZM00## with the title Document Schema LO521-##, by copying the standard calculation schema RM0000 with all dependent entries.

During the copying process, the R/3 System will repeatedly issue the warning message You should use the counter only for manual item conditions. Acknowledge this and any other warnings by choosing Enter each time.

1-4 Create a second new calculation schema YM00## with the title Supplementary Conditions LO521-## by copying the standard calculation schema RM0000 with all dependent entries. Acknowledge the repeated warnings by choosing Enter each time.

1-4-1 In both new calculation schemas YM00## and ZM00##, replace the standard condition type PB00 with your condition type Z##A.

Save your calculation schemas.

(C) SAP AG LO521 3-17

1-5 Now change your condition type Z##A by assigning your new calculation schema YM00## to it as the supplementary schema instead of the standard calculation schema.

Save your change.

1-6 Create a new vendor schema group ## with the title Schema group LO521-##.

For course participants belonging to group 01:

Schema group 01 already exists in the standard system and need not be created. Simply change the title.

Save your schema group.

1-7 Now define the schema determination process by assigning your calculation schema ZM00## to your vendor schema group ##. The assignment should be independent of the purchasing organization.

Save your assignment.

1-8 Assign your schema group ## to vendor T-L21B## on the Purchasing data screen of the vendor master record for purchasing organization 1000.

Save your assignment.


(C) SAP AG LO521 3-18

Exercises

Unit: Price Determination Topic: Analyzing Price Determination


�� Analyze the price determination process, taking into account different condition tables, validity periods and scales

When a buyer creates a purchase order, you’d like the R/3 System to determine the correct price from a condition record. You want to make sure that scaled conditions and differing validity periods are also taken in account.

2-1 Create a purchase order with the following data:

Vendor: T-L21B##


Purchasing group: Z21 (LO521 Buyer)


Order 100 pc of material T-REL## for plant Hamburg (1000) at a price of 100 UNI.

2-1-1 Why must you enter the price manually?

______________________________________________________

2-1-2 Go to the condition tab for purchase order item.

Which condition type has been assigned to your manually entered price? ________________________________________________

2-1-3 What calculation schema has been determined for your purchase order? ________________________________________________


Purchase order number: ___________________

2-2 Change the info record for vendor T-L21B##, material T-REL##, purchasing organization IDES Deutschland (1000), which was generated automatically from your purchase order data.

2-2-1 Go to the condition screen.

Which condition type is suggested to you? ___________________

(C) SAP AG LO521 3-19

2-2-2 You and your vendor have agreed to the following conditions:

Gross price: 100 UNI

Discount (value): 10 UNI from 1 pc 50 UNI from 200 pc

Enter the conditions.

If you have used the Propose Condition Supplements function, do not forget to use the Restore (Re-create) Condition Supplements function before saving to ensure that all conditions with a value of 0 are deleted from the list. Otherwise, problems are liable to occur in subsequent exercises due to a discrepancy between the condition type in the info record and the condition types in the soon-to-be-changed calculation schema.

Save the changed info record.


2-3 You have also negotiated the following general discount with vendor T-L21B##, which applies to all materials and is valid for four weeks, starting today.

�� 1% up to a condition value of 1000 UNI



Before entering the discount scale, you must change the scale type on the condition detail screen.

(C) SAP AG LO521 3-20

*2-4 Create a purchase order with the following data:

Vendor: T-L21B##




Order 100 pc of material T-REL## for plant Hamburg (1000).

2-4-1 Is an order price suggested to you? If so, what is it?

______________________________________________________

2-4-2 Go to the Conditions tab for your purchase order item.

How is the default order price calculated? ______________________________________________________

2-4-3 Use the Analysis function to see the details of the price determination process.

Purchase order number: ______________________________

*2-5 You have agreed with vendor T-L21B## that the conditions valid on the delivery date for material T-REL## are to be applied for price determination purposes. Record this in the R/3 System by changing the info record for purchasing organization IDES Deutschland (1000) and entering a suitable pricing date category.

2-5-1 Which pricing date category do you use?

______________________________________________________

*2-6 Create a purchase order with the following data:

Vendor: T-L21B##




Order 200 pc of material T-REL## for plant Hamburg (1000).

2-6-1 Is an order price suggested to you? _________________________

2-6-2 Go to the Condition tab for your purchase order item.

How is the order price calculated?

______________________________________________________

2-6-3 Why wasn’t the vendor discount from above taken into account?

______________________________________________________

(C) SAP AG LO521 3-21

2-6-4 Select Details for condition type Z##A.

Which date was taken as the basis for price determination?

______________________________________________________

2-6-5 Select the Condition control tab to see the pricing date category.

(C) SAP AG LO521 3-22

Price Determination Solutions

Unit: Price Determination Topic: Customizing Settings

1-1 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose� SAP Reference IMG. IMG � Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types. Choose Define Condition Type.

1-2 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose � SAP Reference IMG. IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process. Select IMG activity documentation on the left-hand side of the Define Calculation Schema node.

1-3 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG. IMG � Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Calculation Schema.

Choose Copy all when asked.

1-4 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG. IMG� Materials Management � Purchasing � Conditions ��Define Price Dtermination Process � Define Calculation Schema.


1-4-1 Select the calculation schema, then choose Control data.

1-5 SAP menu � Tools � AcceleratedSAP � Customizing � Edit project. Choose SAP Reference IMG. IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types. Choose Define Condition Type.

Go into the detail screen and change the entry in the PricingProc field.

(C) SAP AG LO521 3-23

1-6 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG. IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Schema Group. Choose� Schema Groups: Vendor.

1-7 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project. Choose � SAP Reference IMG. IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Schema Determination. Choose� Determine Calculation Schema for Standard Purchase Orders.

Leave Schema gp. POrg blank. Enter only your vendor schema group and your calculation schema.

1-8 SAP menu � Logistics � Materials Management � Purchasing � Master data � Vendor � Purchasing � Change (Current).

Select Purchasing data.

1-8-1 Favorites � Add.

(C) SAP AG LO521 3-24

Solutions

Unit: Price Determination Topic: Analyzing Price Determination

2-1 Favorites � Purchasing � Purchase order � Create � Vendor/Supplying Plant Known. 2-1-1 You must enter the order price manually because no info record yet exists

and the R/3 System could not determine a valid price.

2-1-2 Condition type PBXX.

2-1-3 From Conditions, choose Analysis.

ZM00##. Due to the assignment of your vendor T-L21B## to schema group ##, the R/3 System determined that calculation schema ZM00## is to be used in your purchase order.

2-2 Logistics � Materials Management � Purchasing � Master data � Info record � Change. 2-2-1 Condition type Z##A.


2-3 Favorites � Master Data � Conditions � Discounts/Surcharges � By Vendor.

Enter the vendor and purchasing organization, then choose Execute.

On the next screen, choose purchasing organization and select Create.

To change the scale type, select the condition type RL01 and choose Detail. Change the scale type to B (To-scale).

*2-4 Favorites �Purchasing � Purchase order � Create � Vendor/Supplying Plant Known.

2-4-1 An order price of 96.90 is suggested.

2-4-2 The suggested order price is calculated as follows: 100.00 UNI gross price less 0.10 UNI discount (10.00 UNI discount (value) is divided by the order quantity of 100 pc = 0.10), less 3.00 UNI vendor discount (3% vendor discount x 10000 = 300 UNI; 300.00 UNI vendor discount is divided by the order quantity of 100 pc = 3.00 UNI).

2-4-3 Select Analysis while in the Condition tab.

*2-5 Favorites � Purchasing � Master data � Info record � Change.

(C) SAP AG LO521 3-25

Go to the Purch. org. data 1 screen.

2-5-1 The pricing date category of 2 (Delivery date) is used.

*2-6 Favorites � Purchasing � Purchase order � Create � Vendor/Supplying Plant Known.

2-6-1 An order price of 99.75 is suggested.

2-6-2 The suggested order price is calculated as follows:

100.00 UNI gross price, less 0.25 UNI discount (50.00 UNI discount (value) is divided by the order quantity of 200 pc).

2-6-3 The vendor discount is not taken into account because it is not valid on the delivery date (it was only valid for four weeks).

2-6-4 The delivery date was taken as the basis for price determination.


� SAP AG 1999

� Header Conditions

� Group Conditions

� Item Conditions

� Condition Groups

Header and Group Conditions

Contents:


� SAP AG 1999

� Describe the differences between and the creation of header, group and item conditions

� Define condition types as group conditions

� Identify and use important control parameters for condition types and calculation schemas


Header and Group Condition: Unit Objectives


� SAP AG 1999

� When creating a purchase order with multiple items, you often have conditions that apply to all the items. On the other hand, certain conditions may be item specific. In the R/3 system, conditions can relate to individual items of a purchasing document, to several items (group conditions), or to all items of the document (header conditions). Header and group conditions can apportioned among the items on the basis of value.

Header and Group Conditions: Business Scenario


� SAP AG 1999

Header and Group Conditions: Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Header, Group, and Item Conditions

Purchase orderMat.145

Item102040

Mat. gr.001009009

Qty.11

10

Price81.0072.0063.00

Per purchase order: 20.00freight surcharge

Mat. group discount:5% from 100.00

Special discount for material 51% from 10 pc upwards

��Item conditions are conditions relating to a single item of a document. ��Header conditions are entered in the header of a document and relate to all the items of that

document. ��Some standard condition types can be used only as item conditions, some only as header conditions

and others as both header and item conditions. Usage options are determined by the Header condition/Item condition switch in Customizing for the condition type.

��No automatic price determination process is carried out for header conditions. For this reason, you cannot assign an access sequence to a header condition (except if it is also defined as an item condition) or create condition records for such a condition.

��A condition type can be defined as a group condition in Customizing. A group condition is a condition relating to several items of a document. In the case of a group condition, the condition values (price, order quantities, weight or volume) of the relevant items are added and the total used as the condition basis. This allows more favorable values to be taken as a basis for the scale computation than would be the case if individual items were considered. The grouping of items is carried out using the key of the condition record for the group condition or by means of a group condition routine assigned to the condition type in Customizing.


� SAP AG 1999

Header Conditions

Purchase orderMat.1+ surcharge2+ surcharge3+ surcharge

Pos.10

20

30

Qty.1

1

1

Price300.00

10.00100.00

10.0050.0010.00

Header conditionZB00 Abs. surcharge 10.00

ZB00 Group condition =ZB00 Abs. surcharge 10.00

Purchase orderMat.1+ surcharge2+ surcharge3+ surcharge

Item10

20

30

Qty.1

1

1

Price300.00120.00100.0040.0050.0020.00

Header conditionHB00 Header surch. 180.00

HB00 group condition =180.00 Total

��Header conditions apply to all the items of a document and are apportioned among the items automatically.

��A header condition may involve a percentage or a fixed amount. If you have specified a header condition in the form of a percentage discount or surcharge, this percentage applies to all the items of the document automatically. If the header condition involves a fixed amount, the value of the condition can be assigned to each item or spread proportionately among the items.

��The condition value is spread proportionately among the document items if the condition type has been defined as a group condition in Customizing. If the condition type has not been defined as a group condition, the value of the header condition is assigned to each item, in which case the header condition constitutes an entry aid.

��In the standard R/3 System, the apportionment of an absolute header condition is carried out on a value basis. However, you can specify in Customizing that apportionment is to be according to the weight or volume of the individual items. The basis for apportionment is specified in the Base formula field of the calculation schema.


� SAP AG 1999

Material 1PB00 Gross price

Group Conditions and Scales

Info record conditions

FromFromFrom

1 pc100 pc900 pc

100.0099.0090.00

Purchase orderMat.11

Item1020

Qty.8040

Cost centerA1A2

Condition type PB00Group cond. =

Customizing Purchase orderMat.11

Item1020

Qty.8040

Price99.0099.00

Cost centerA1A2

Price100.00100.00

��A condition type can be defined as a group condition in Customizing. A group condition is a condition that relates to several items of a document. In the case of a group condition, the values (price, order quantities, weight or volume) of the relevant items are added and the total used as the condition basis. This allows more favorable values to be taken as the basis for the scale computation than would be the case if individual items were considered. The grouping of items is carried out using the key of the condition record for the group condition or using a group condition routine assigned to the condition type in Customizing.

��Solong as the document has not yet been saved, a price determination process is carried out for each document item in isolation, and the condition basis determined. Only after the document is saved are the item values cumulated. Then, the scale amount is determined on the basis of the cumulated item values.

��You can explicitly initiate the determination of the scale amount on the basis of the cumulated item values on the header condition screen by activating the conditions. Both the activation of the conditions and saving the document constitute opportunities to verify the determination of the lower scale amount.


� SAP AG 1999

Group Conditions and Print Indicator

Material 11 pcSurchargeNet value

Purchase order

Material 11 pc @ 100.00Material 21 pc @ 10.00

Surcharge:50.00

100.0045.00

145.00Material 2

1 pcSurchargeNet value

10.005.00

15.00

Calculation schemaSurcharge: Print = X

Material 11 pc

Material 21 pc

100.00

10.00

SurchargeTotal value

50.00160.00

Calculation schemaSurcharge: Print = S

��The print indicator in the calculation schema controls the output of the condition line when the document is printed (for example, in purchase order print-outs).

��As of Release 4.0A, for more detailed specifications, the print indicators A, B, C, and D are available for the output of condition lines in the totals block, and the indicators a, b, c, and d for the output of condition lines at item level: ��A condition line is not to be printed (print indicator _), ��A condition line is to be printed (print indicator A or a), ��A condition line is to be printed if the condition value is not 0 (print indicator B or b), ��a condition line is to be printed if the condition value differs from the condition value of the

preceding condition line (print indicator C or c), ��a condition line is to be printed if the condition value is not 0 and differs from the condition value

of the preceding condition line (print indicator D or d). ��The meaning of the print indicator is explained in the field documentation. ��The old print indicators (_, X, S) can still be used, but must not be mixed with the new indicators in

the calculation schema. The new print indicators are taken into account only if a print indicator X or S is not assigned to any condition type in the calculation schema.


� SAP AG 1999

Condition Group

Info record

Vendor AMaterial 1Cond. group XY

Info record

Vendor AMaterial 2Cond. group XY

Info record

Vendor AMaterial 3

Conditions RGR0

Vendor ACond. group XY2% discount

Item.10- 2% Discount

20- 2% Discount

30

Purchase orderMat.1

2

3

Price100.00

150.00

20.00

��The condition group embraces a number of different materials supplied by a vendor to which a uniform discount or surcharge applies.

��The condition group is a freely definable, four-character, alphanumeric string that is assigned in the info record.

��You can create time-dependent conditions with validity periods and scales for a condition group defined for a vendor. For this purpose, the condition type RGR0 is provided as a percentage condition group discount in the standard R/3 System.

��Condition type RGR0 is not defined as a group condition. ��A discount or surcharge belonging to a vendor condition group is a general condition. ��When purchase orders are created, a discount or surcharge belonging to a condition group is taken

into account only in respect of those materials that have been assigned to the condition group by their info records.

(C) SAP AG LO521 4-10

� SAP AG 1999

� Describe the differences between and the creation of header, group and item conditions

� Define condition types as group conditions

� Identify and use important control parameters for condition types and calculation schemas


Header and Group Conditions: Unit Summary

(C) SAP AG LO521 4-11

Header and Group Conditions Exercises

Unit: Header and Group Conditions


�� Describe the differences between, and the creation of, header, group, and item conditions

�� Define condition types as group conditions

�� Identify and use important control parameters for condition types and calculation schemas

When creating purchase orders with multiple items, you often have conditions that apply to all the items. However, certain conditions may be item specific. In the R/3 System, conditions can relate to individual items of a purchasing document, to several items, or to all items of the document.

1-1 Calculation schema ZM00## is also to be valid for your vendor T-L21C##. Therefore, assign your vendor schema group ## to this vendor on the purchasing data screen of the vendor master record for purchasing organization 1000.

1-2 You procure various office supplies, for which you have not created any material master records, from vendor T-L21C##. For these materials, you have negotiated particularly favorable conditions, which are to be entered in an info record without a material master record.

Create the info record with the following data: Vendor: T-L21C## Purchasing organization: IDES Deutschland (1000) Plant: Hamburg (1000) Short text: Office supplies Material group: LO521 Material group (ZT21) Order unit: PC Sort string: LO521-## Planned delivery time: 4 days Purchasing group: LO521 Buyer (Z21) Standard quantity: 100 pc Price: 3.00 UNI from 1 pc

2.50 UNI from 500 pc

1-3 To ensure that the order quantities are totaled in purchase orders in which different office supplies are listed as items, and the lower price of 2.50 UNI is applied where appropriate, your condition type Z##A must be designated as a group condition.

(C) SAP AG LO521 4-12

Check whether your condition type Z##A is designated as a group condition. If necessary, set the group condition indicator and save your change.

1-4 In some instances, vendor T-L21C## imposes a general surcharge that varies according to the total order of each purchase order:

�� 30 UNI up to a total order value of 500 UNI �� 20 UNI up to a total order value of 800 UNI �� 10 UNI up to a total order value of 2000 UNI

No surcharge is payable if the total order value exceeds 2000 UNI.

The surcharge applies to all materials supplied by the vendor and is to be apportioned among the individual purchase order items by value share.

There is no suitable condition type for this condition.

Before defining a new condition type, please consider the following questions.

1-4-1 Upon which factors does the condition depend – for example, vendor, material? ______________________________________________________

______________________________________________________

1-4-2 Which condition class should you assign to the new condition type? ______________________________________________________

______________________________________________________

1-4-3 Which calculation type should you use for the new condition type? ______________________________________________________

______________________________________________________

1-4-4 How can you make sure that your condition type is interpreted as a surcharge? ______________________________________________________

______________________________________________________

1-4-5 How do you make sure that the amount of the surcharge is apportioned among the items?

______________________________________________________

(C) SAP AG LO521 4-13

______________________________________________________

1-4-6 Which scale basis and which scale type are appropriate?

______________________________________________________

______________________________________________________

1-4-7 Define the new condition type. Use the key Z##B and the description LO521 Surcharge ##.

Copy condition type RL01 and make the appropriate changes

1-5 Change your calculation schema ZM00## by inserting your new condition type Z##B as an additional surcharge. Your condition type is to be assigned to the same step as all other discounts and surcharges and is to be added as the last condition type in this step.

Acknowledge the familiar warning message: You should use the counter only for manual item conditions by selecting Enter.

1-5-1 In which step have the discounts and surcharges been inserted into the calculation schema?___________________________________

1-5-2 The condition values for your condition type Z##B are to be printed out at the item level. Which print indicator must you set to achieve this?___________________________________________

Save your change.

1-6 Now create the condition record for vendor T-L21C## for your new condition type Z##B:

30 UNI up to a total order value of 500 UNI



No surcharge is payable if the total order value exceeds 2000.

The surcharge is valid until the end of next year.

1-6-1 What menu path do you use?

______________________________________________________

______________________________________________________

(C) SAP AG LO521 4-14


1-7 Create a purchase order with the following data: Vendor: T-L21C## Purchasing organization: IDES Deutschland (1000) Purchasing group: LO521 Buyer (Z21) Acct. assgt. category: K (applies to both items) Delivery date: In 4 weeks (applies to both items) Plant: Hamburg (1000) (applies to both items) Material group: LO521 Material group ZT21 (applies to both tems)

Order the following two items, which have no material master records, for cost center T-L20 Notepads, 400 pc Ring binders, 100 pc

For both items, reference your info record without a material master. You do this by entering the info record number in the Info rec. field at the line item level.

You can use the search help procedure for Info Record per Material Group to find your info record number. Use material group ZT21 and your vendor T-L21C## as selection criteria.

1-7-1 Go to the header Condition tab and check:

�� The total net value of the purchase order __________________

�� The gross price per 1 pc _______________________________

�� The surcharge for the entire purchase order ________________

1-7-2 Look at the Conditions tab in the item details screen area. What net price has been calculated for the two items?

______________________________________________________

1-7-3 Check the apportionment of the surcharge among the two items by looking at the item Condition tabs. What is the amount of the surcharge for item 10?

______________________________________________________

What is the amount of the surcharge for item 20?

______________________________________________________

(C) SAP AG LO521 4-15

Purchase order number: _________________________________

(C) SAP AG LO521 4-16

Header and Group Conditions Solutions

Unit: Header and Group Conditions

1-1 Favorites � Purchasing � Vendor � Purchasing � Change (Current).


1-2 Favorites � Purchasing � Master data � Info record � Create. On the initial screen, leave Material blank.

1-3 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

Check the detail screen for your condition type and verify that Group condition is selected.

1-4

1-4-1 Since the surcharge is to apply to all materials supplied by the vendor, it depends solely on the purchasing organization and the vendor.

1-4-2 You should assign Condition class A (discounts and surcharges).

1-4-3 Use Calculation type B (fixed amount).

1-4-4 You specify that the condition type is interpreted as a surcharge via the Plus/minus sign: A (positive sign).

1-4-5 If you set the Group condition indicator, the amount of the surcharge is apportioned among all purchase order items on the basis of value share.

1-4-6 The scale basis should be B (value scale) and the scale type should also be B (To-scale).

1-4-7 SAP menu �Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

Copy condition type RL01 and make the following settings, based on the answers above:

Calculation type = B

(C) SAP AG LO521 4-17

Plus/Minus = A

Select the Group condition indicator

Scale type and scale basis = B

Be sure Check value is blank.

1-5 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Calculation Schema.

Select ZM00## and choose Control. Add your condition type to step 10 by copying RL01 and changing the counter.

1-5-1 Step 10 has the discounts and surcharges inserted into the calculation schema.

1-5-2 You specify the condition values to be printed out at the item level by setting the print indicator X.

1-6

1-6-1 Logistics � Materials � Management � Purchasing � Master Data � Conditions � Other � Create.

Select Vendor as the Key combination.


1-7 Favorites � Purchasing � Purchase order � Create � Vendor/Supplying Plant Known.

The Info rec. field is several fields to the right of Plant in the standard system. To search for your info record number, select the field and Possible entries. Use search help N and enter material group ZT21 and your vendor T-L21C##.

1-7-1 The total net value of the purchase order 1260 UNI The gross price per 1 pc 2.50 UNI The surcharge for the entire purchase order 10 UNI

1-7-2 The net price 2.52 UNI was calculated for the two items.

1-7-3 The surcharge amount for item 10 is 8 UNI

The surcharge amount for item 20 is 2 UNI


� SAP AG 1999

� Maintaining Time-Dependent Conditions

� Validity Periods in Info Records

� Change Documentation and Change Options

� List of Conditions


Contents:


� SAP AG 1999

� Execute functions for the maintenance and display of conditions

� Change condition values and/or validity periods using collective functions

� Define change options for condition types


Maintaining Conditions: Unit Objectives


� SAP AG 1999

� Over time, your vendors’ prices and conditions may change. Individual and collective functions are available for maintaining and displaying conditions.

Maintaining Conditions: Business Scenario


� SAP AG 1999

Maintaining Conditions: Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Maintaining Time-Dependent Conditions 1


Cond. ty.PB00

Amount10.00

Validityfrom 01.01. to 12.31.


Cond. ty. PB00GAU1RB00ZB00RA00...

Amount 10.00



Cond. ty. PB00RA00

Amount 10.00

5%


Scale PB00

Qty.From 1 pcFrom 500 pc

Amount10.00

9.50


Info record conditionsValidityfrom 01.01. to 12.31.

Details (RA00)

Amount:per:Scale type:Deletion ind.:

10.001 pcA


Qty. PB00 RA00

Amount10.00

5 %

Propose cond.supplements

Restore

ScaleDetails

5 %

��Time-dependent conditions for outline agreement items, quotations or info records are maintained directly in the relevant documents or in the info record. In the case of time-dependent conditions, specification of a validity period is mandatory. If you fail to enter a validity period, the R/3 System will assign a predefined maximum validity period to your conditions (standard setting: current date until 12.31.9999). You can specify the default start and end dates in Customizing using the condition type.

��You can maintain scaled values for time-dependent conditions. A detail screen is available for each condition type enabling you to maintain the scale values and scale amounts. If necessary, the scale type (From or To scale) can be changed prior to entry of the scale lines on the detail screen for the condition type.

��To simplify maintenance of discounts and surcharges, delivery costs, and so on that have the same validity period as the gross price, you can use the Propose condition supplements function. If you use this function, you obtain a list of the condition types that have been assigned in Customizing to condition type PB00 (or a comparable condition type of your own). You then simply enter the condition amounts or percentages for the relevant condition types. After this, you choose the Restore function, so that all the lines with a condition amount = 0 or with no specified amount are deleted.

��You can also delete conditions whose amount differs from 0 by selecting the condition line and setting a deletion indicator. You can cancel the latter indicator, if necessary.


� SAP AG 1999

Maintaining Time-Dependent Conditions 2

. . .

. . .Per contractPer info record. . .

. . .

. . .Per vendorPer condition groupPer material typePer invoicing party. . .

. . .Condition typeRL01RGR0MAR1REST

Vendor discountGroup discountMisc. provisionAccount discount

Other. . .

CreateCreate by referencingChangeDisplay

. . .1) Condition types

GAU2, NAVS

2) Own condition types

Prices

Discounts/surch.

Master data. . .

. . .Conditions

Master data. . .Conditions. . .

Master data. . .

. . .Conditions

��Time-dependent conditions can be maintained using the Master data menu in Purchasing (Master data � Conditions � Prices or Discounts/surcharges). SAP recommends that you do not maintain info record, outline agreement and quotation conditions using the Master data menu but maintain them in the relevant documents or in the info record.

��You can maintain general conditions using the Master data menu that apply, for example: ��To all the materials supplied by a vendor (vendor discount, condition type RL01) ��To all the materials belonging to a vendor condition group (condition group discount, condition

type RGR0) ��There are special condition maintenance functions for the general standard condition types supplied

by SAP (for example, RL01 and RGR0) (Master data � Conditions � Discounts/surcharges � By vendor/By condition group).

��For your own condition types, which cannot be maintained using the info record or outline agreement, you must use the general condition maintenance function (Master data � Conditions � Other � Create/Change).

��You must also use the general condition maintenance function for the standard condition types GAU2 and NAVS. You should only use the general maintenance function for other standard condition types if expressly advised to do so by SAP.


� SAP AG 1999

Validity Periods

Info recordVendorMaterialPriceValid from

toPriceValid from

to

A110.0001.01.9806.30.98 11.0007.01.9812.31.98

New priceValid from

to

10.5004.01.9806.30.99

Overlapping validity periodsConditions whose validity periods are completely covered by those of new conditions are deleted when the latter are saved.Confirm

01.01.98 06.30.98 12.31.98

01.01.98 04.01.98 12.31.98

Existing validity periods

New validity period

06.30.99

��If you access info record, outline agreement or quotation conditions in order to make changes, a dialog box appears containing a list of existing validity periods. You can choose an existing validity period or create a new one.

��You can change both the conditions of an existing validity period and the start/end dates of the validity period.

��Condition validity period overlaps are not allowed. When you create a new validity period or change the start or end date of an existing one, it can happen that the new or changed period completely overlaps another existing period. In this case, a dialog box appears in which the critical validity periods are displayed. You can either: ��Delete the overlapped validity period with its conditions (Choose Confirm) ��Decide not to create the new validity period or change the date of the existing period (Choose

Delete or Cancel. ��You can obtain an overview of existing validity periods and the gross prices for each such period. ��Within a single function call, you can only access one validity period.


� SAP AG 1999

Collective Changes

Vendor AMaterial 1

Gross priceDiscount

(PB00)(RA00)

Vendor AMaterial 1

Gross priceDiscount

(PB00)(RA00)

10.002%

Valid from 01.01. - 12.31.

10.202%

Valid from 01.01. - 12.31.

Change in gross price: + 2% valid as of 07.01.

Vendor AMaterial 1

Gross price (PB00) 10.20 Valid from 01.01. - 12.31.

Condition type change: 5% discount from 06.01. - 07.31.

Discount (RA00) 2% Valid from 01.01. - 05.31.



��You can make collective changes to a vendor’s conditions in info records, contracts or scheduling agreements.

��Such collective changes can affect: ��The gross price ��A certain condition type that is to be entered

��The change to the conditions can be percentage or absolute in nature, and can be positive or negative. ��Both percentage and absolute condition changes are also taken into account automatically in the case

of scaled conditions. If you do not want this to happen, you must deselect the Scale lines indicator on the initial screen of the function.

��You can change the condition amounts or percentages of existing validity periods by entering a key date in the Change to conditions valid on field. In this case, all condition records that are valid on the key date you specified are selected and changed. The validity period of the condition records remains unchanged.

��If your condition change is to apply for a certain validity period or from a certain time, you must enter the start and end dates of the period in the Change valid only from/to fields. In this case, the collective change function results in the creation of a new period and the end date of the existing period is altered.

��Changes to conditions are simulated initially. To actually implement the changes, you must deselect the Test run field and then save the changes that are displayed.


� SAP AG 2001

Changing Conditions using a Condition Index

Information record

Vendor AMaterial group 005

Information record

Vendor BMaterial group 005

Information record

Vendor CMaterial group 005

Customizing

� Change Cond Types

� Define Permitted Fields

� Edit Condition Index Tables

� Activate Cond Index Tables

��Rebuild Cond Index Tables

� Define Overviews

� Assign Overviews

New price for all info records for material group 005 regardless of vendor, for example

��As of Release 4.6C, you can collectively change the time-dependent conditions using a condition index.

��You can collectively change time-dependent conditions and their validity periods, administrative data, and so on, in info records, contracts, or scheduling agreements.

��If you use condition indices, you can define your own criteria (for example, vendor or purchasing organization), which are used to select the conditions to be changed.

��The conditions to be edited are selected using condition tables that are created in Customizing. ��You must create a conditions index in Customizing for Purchasing at Conditions -> Configure

Condition Index. ��In the example above, there was a need to change all info records for material group 005, regardless

of vendor. The SAP R/3 system was configured with a condition index that contained material group.

(C) SAP AG LO521 5-10

� SAP AG 1999

Automatic Adjustment - Changes to Conditions

VendorPur. data. pur. groupDoc. index active

CustomizingDocument updateLog. message cat. active CONDBI

CustomizingDocument updateC. ty. PB00PB00

Origin 22

Cond. tab. 017018

01.01. 04.01. 07.01. 12.31.

Automaticdocumentadjustment

Adjustment of worklist Compilation of worklist

Info record change01.01. - 12.31.Price

Purchase orderPrice(info record) 11.00

10.00

Price 11.00

��If time-dependent conditions change after a PO has been created, and these new conditions are to apply to this and other created but still open POs, you can use the Automatic document adjustment function to ensure that the relevant amended conditions are adopted in all affected documents. A prerequisite for automatic document adjustment in the case of changes involving conditions is that no follow-on documents exist in the R/3 System.

��The Document index active indicator must be set in the master record of the vendor for whose retrospective changes to conditions the Automatic document adjustment function is to be used. The document index determines the purchasing documents that are affected by vendor-initiated changes to conditions. It is compiled when a vendor’s time-dependent conditions (from which the document index indicator has been set) are changed. You should set this indicator only if you want to use the automatic document adjustment function for the vendor in question, otherwise the volume of data is inflated unnecessarily.

��You can specify in Customizing, which condition types and condition tables are updated in the case of automatic document adjustment. Automatic document adjustment is carried out in the following steps: ��With the Create worklist function, all indexed condition changes are read and compared with the

Customizing settings and your selection criteria (change period). The relevant worklist of condition changes is stored and serves as the basis for further processing.

(C) SAP AG LO521 5-11

� SAP AG 2001

Change Documentation

1 Change in validity period2 Change in gross price3 Change in a discount scale

++

Date Time User Cond. Vend. Mat. Purch. org. validity01.10. 14:25 Myers PB00 A 1 1000 01.01.97 - 12.31.9715.12. 10:14 Myers PB00 A 1 1000 01.01.97 - 12.31.98

Description1 „Valid to“ date2 Condition amount/percentage3 Suppl. condition (RA00): scale changed

Suppl. condition (RA00): scale changedCondition amount/percentage

Old value31.12.9710,00

3% -

New value31.12.9811,001000 4% -5000 5% -4% -

��Changes to condition records are documented in change documents. A report function is available for the display of change documents, enabling you to trace all changes made to condition records.

��The selection of the change documents can relate to one condition record or encompass several condition records using a report.

��Changes are displayed at the following levels: ��1. Change date, time; user who made changes and transaction code with which the changes were

made; condition type, condition table, and key combination of changed condition record; validity period of condition record at time of change

��2. Description of change made; old value (before change) and new value (after change); name of changed field

��In the case of changes to scales, all condition scale entries (not just the changed ones) are written as change documents.

��All changes involving the supplementary conditions are documented and displayed with the changes made to the condition record.

��As of Release 4.6C, you can display change documents relating to price changes if you change the vendor's prices in info records, contracts, or scheduling agreements using Master data -> Conditions -> Vendor price change. Until now, you could not display these change documents using the Environment function in the info record. Sie erreichen die Änderungsbelege aus dem entsprechenden Beleg heraus über: Zusätze -> Konditionen -> Umfeld -> Änderungen -> Je Konditionssatz

(C) SAP AG LO521 5-12

� SAP AG 1999

Change Options Within Document


VendorMaterialPurch. org.

A11000

Purchase order

VendorPurch. org.

10 pc material 1

A1000

Conditions

PB00RA00FRA1

10.001%5%

Customizing condition types: Change options

Amount/percent

Value

Manual entry

Delete

Calculation type

Quantity conversion

Changeable?

C. ty. PB00RA00FRA1

Amount 10.00

1%5%

��In Customizing for the condition type, you can specify whether conditions stemming from info records or outline agreement items that are suggested in POs can be changed and which changes are permitted.

��You specify the relative priorities of automatically determined and manually entered conditions using the Manual entry indicator. For example, you can specify that: ��The automatically determined condition takes priority (indicator B). If a condition record exists for

the condition type, the condition cannot be entered manually. ��The manual condition takes priority (indicator C). In the case of manual entry, no check is made to

see if a condition record exists. ��The condition in a document cannot be processed (indicator D).

��If a condition type can be changed manually, you can specify whether: ��The default condition amount or percentage, the condition value, the calculation type the condition

type or the conversion factors for the units of measure can be changed. ��The default condition can be deleted.

(C) SAP AG LO521 5-13

� SAP AG 1999

Data Protection Through User Authorizations

Pur. order

User parameter EFB

Display conditionEnter conditionWithout materialField selection

Price 1.00

User authorizations

Authorization objectV_KONH_VKSActivity: 01. 02. 03Condition type: PB00

Outl. agreement

Info recordPrice 1.00

��The authorization object V_KONH_VKS (condition: authorization for condition types) is assigned to the class Sales and Distribution and enables you to restrict user access to certain condition types and comprises the following authorization fields: ��The authorization field Activity enables you to restrict user access to a certain activity (Create =

activity 01, Change = activity 02, Display = activity 03) ��The authorization field Condition type enables you to restrict user access to certain condition

types. ��Authorization for authorization object V_KONH_EKO (purchasing organization in the master

condition) is assigned to the class Materials Management – Purchasing and is necessary for the maintenance of other conditions if the purchasing organization is part of the key of the condition record..

��The user parameter EFB enables you to specify the authorizations for certain functions used when processing requisitions and purchase orders per user or user group (including authorization to display or maintain conditions). You define the authorizations in Customizing and assign them to a user by entering the authorization key in the user master record under the parameter ID EFB.

��Authorization for authorization object S_TABU_DIS (table maintenance) and/or S_TABU_CLI (maintenance of client-independent tables) belonging to the class Basis – Administration is necessary in Customizing for the maintenance of condition types, calculation schemas, acess sequences and so on. In addition, authorizations for the authorization objects V_KONG_VWE (generation of conditions: authorization for usage/application) belonging to the class Conditions.

(C) SAP AG LO521 5-14

� SAP AG 1999

� Execute functions for the maintenance and display of conditions

� Change condition values and/or validity periods using collective functions

� Define change options for condition types


Maintaining Conditions: Unit Summary

(C) SAP AG LO521 5-15

Maintaining Conditions Exercises

Unit: Maintaining Conditions

At the conclusion of this exercise, you will be able to: �� Execute functions for the maintenance and display of

conditions �� Change condition values or validity periods (or both) using

collective functions

�� Define change options for condition types

Over time, your vendors’ prices and conditions may change. Individual and collective functions are available for maintaining and displaying conditions.

1-1 Create a new condition type Z##C with the description LO521 Freight ## by copying the standard condition type FRB1.

Specify the following for your new condition type:

�� Condition amounts cannot be changed in the document �� The condition type may not be deleted in the document

1-1-1 Through which control parameters for condition types can you make these settings?

______________________________________________________

Save your condition type.

1-2 Change your calculation schemas YM00## and ZM00## by replacing the standard condition type FRB1 with your new condition type Z##C in each case.

Save your changes.

1-3 You procure material T-REM## from vendor T-L21B##. Create a cross-plant info record for purchasing organization 1000 with the following data: Planned delivery time: 7 days Purchasing group: LO521 Buyer (Z21) Standard quantity: 100 pc

You have agreed to the following conditions with the vendor:

Gross price: 18 UNI

Freight surcharge: 50 UNI

Use your new condition type Z##C for the freight surcharge.

(C) SAP AG LO521 5-16

The conditions are valid from January 1 of the current year until December 31 of next year.

1-4 Vendor T-L21B## grants special conditions if you order material T-REM## for plant Berlin (1100) or for plant Dresden (1200).

Create two plant-specific info records for purchasing organization IDES Deutschland (1000), plant Berlin (1100) and plant Dresden (1200)with the conditions below. The conditions are valid from January 1 of the current year until December 31 of next year.

Use your new condition type Z##C for these two info records, too.

�� Plant Berlin (1100): Gross price: 17.80 UNI Freight surcharge: 40.00 UNI

�� Plant Dresden (1200): Gross price: 18.20 UNI Freight surcharge: 35.00 UNI

1-5 Create a purchase order with the following data.

Vendor: T-L21B##



Delivery date: In four weeks

Order 100 pc of material T-REM## for plant Hamburg (1000).

Go to the Condition tab for your purchase order item.

1-5-1 Can you change the freight surcharge taken from the info record?

______________________________________________________

1-5-2 Can you delete it?

______________________________________________________

Purchase order number: ___________________________________

1-6 Vendor T-L21B## advises you that he will reduce all gross prices for his materials by 5%. These reduced prices are valid for a three-month period only, starting on the first of next month. The change applies to all plants.

Collectively change all info records for vendor T-L21B##.

(C) SAP AG LO521 5-17

Save the price change.

1-7 Display a general overview of all the prices of vendor T-L21B## for material T-REM##.

Choose a scope-of-list parameter that enables you to list both cross-plant and plant-specific prices in a general overview.


(C) SAP AG LO521 5-18

Maintaining Conditions Solutions

Unit: Maintaining Conditions

1-1 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project �Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

Select FRB1, then choose Copy. For your new condition type Z##C, deselect the indicators for the Amount/Percent and Delete fields.

1-1-1 You can use the Amount/Percent control parameter to specify whether the amount or percentage of a condition can be changed in a document. The Delete parameter allows you to specify whether a condition type can be deleted in a document.

1-2 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Calculation Schema.

Select your schema, then choose Control. Replace FRB1.

1-3 Favorites � Purchasing � Master data � Info record � Create.

1-4 Favorites � Purchasing � Master data � Info record � Create.

1-5 Favorites � Purchasing � Purchase Order � Create � Vendor/Supplying Plant Known. 1-5-1 You cannot change the freight surcharge taken from the info record.

1-5-2 You cannot delete it.

1-6 SAP menu � Logistics � Materials Management � Purchasing � Master Data ��Conditions � Vendor Price Changes � Involving Info Records.

Enter your vendor, and check that the Gross Price field is selected.

Enter a 5 for Percentage and a – for the Sign.

Enter the three-month period in the Conditions valid from…to fields.

(C) SAP AG LO521 5-19

Deselect the indicator for Test run. Choose Execute.

1-7 SAP menu � Logistics � Materials Management � Purchasing � Master Data ��Conditions � Prices � General Overview.

Enter your vendor, material and Scope of list 0003. Choose Execute.



� SAP AG 1999

� Precious Metal Conditions

� Delivery Costs

� Pallet Discount/Surcharge

� Weight and Volume Dependent Conditions

� Condition Exclusion Procedure

Special Condition Types and Special Functions

Contents:

��If time is short, some of the topics covered in this unit may be omitted. Information on the topics in this unit is available in the text and in the documentation.


� SAP AG 1999

� Create condition types for precious metal conditions by copying existing ones

� Examine the price determination process using precious metal conditions

� Describe the control parameters for condition types for delivery costs

� Explain the function of the pallet discount/surcharge condition types

� Describe how to maintain weight and volume dependent conditions

� Create a condition exclusion


Unit Objectives


� SAP AG 1999

� You purchase certain materials that contain a precious metal. Since the market price of the metal fluctuates, this influences the purchase price.

� Your vendor charges delivery costs for which you need a condition type.

� There are certain materials you purchase that are delivered on pallets, and the vendor offers you a discount if you purchase a complete pallet.

� Your vendor imposes a surcharge based on the weight of the material he provides.

� In some instances, several conditions are valid for the same item. You want to define which condition should take priority.

Unit Business Scenario


� SAP AG 1999

Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Info rec. conditionsC. ty.PB00GAU1

Amt.100.00- 10.00

per unit

1 GAU

Conditions GAU201.01. - 01.07.:01.08. - 01.14.:01.15. - 01.21.:

10.20/1 GAU9.80/1 GAU9.95/1 GAU

Material master rec.Base unit:Altern. unit:2 GAU

pcGAU1 pc

Time

Purch. orderPO date:01.04.Order price:100.40

Goods receiptGR date:01.16.Valuation price:99.90

Ruling PM priceon 01.04.: 10.20

Ruling PM priceon 01.16.: 9.95

“Precious Metal” Conditions (GAU1/GAU2)

��There is a special condition category ”U” for pricing components that vary from day to day, such as discounts and surcharges for precious metals. This condition category causes the purchase/valuation price for the material to be newly determined at the time of ordering and at the time of goods receipt on the basis of the ruling market price for the relevant precious metal on those dates.

��You specify the precious metal portion in the material master record or the info record using a special nondimensional unit of measure (for example, GAU = gram of gold).

��You enter the precious metal price portion included in the material price in the info record under the condition type GAU1 (or a comparable condition type of your own). You maintain the daily ruling price for precious metals as a condition of type GAU2 (or a comparable condition type of your own).

��The two condition types must satisfy special requirements: ��Condition class A, condition category U, calculation type C and identical units of measure (for

example, GAU) must be assigned to both condition types. This first condition type must be marked as ”manual” and have the calculation formula 31 assigned to it. Only this first condition type may be entered in the supplementary condition schema. The Statistical indicator must be set for this condition type.

��An access sequence must be assigned to the condition type for the daily ruling price (GAU2). This second condition type must not be marked as ”manual”. The calculation formula 32 and the requirement 31 must be assigned to it.


� SAP AG 1999

Calculation schemaC. ty.FRA1

Stat

Delivery Costs

Cond. type FRA2Condition class:Calculation type:Condition cat.Accrual:Vendor GR:

AABX_ No entry possible1 Entry possible if no vendor maintained2 Entry always possible

Transaction/event key for account determination

Transaction/event key for freight purchase account

AKeyFREFRE

Accr.FR1FR2

��Delivery costs (incidental procurement costs) are costs for which you make provision at the time a purchase order is created. They can cover amounts payable to, or charges made by, the vendor, a forwarder or carrier, or the customs authorities, for example.

��Planned freight or duty costs are entered in connection with a certain vendor. If they are not to be invoiced by the vendor (supplier) to which the purchase order is issued, you must enter a ”different vendor” when you make provision for delivery costs in the PO (in this case, the ”vendor” is a forwarder or carrier, referred to as a ”freight vendor”, or a customs office). The ”freight vendor” can be changed at the time of goods receipt. A ”different freight vendor" is entered on the condition detail screen. Whether a ”different freight vendor” can be specified depends on the condition type (Vendor GR indicator).

��Condition types for delivery costs must satisfy certain requirements: ��The condition category must be B (= delivery costs). ��The Accrual indicator must be set. (This indicator causes the condition to be posted as a provision

for accrued costs in Financial Accounting.) ��The Statistical indicator must be set in the calculation schema.

(This indicator ensures that the condition is not taken into account in the calculation of the net price.)

��A transaction/event key must be assigned to a provision-relevant condition type in the calculation schema (Accrual field) to enable the G/L account that is to be posted to be found.


� SAP AG 1999

Pallet Discount/Incomplete Pallet Surcharge

Calculation schemaStep

20

24

26...

Count.

0

0

0

C. type

LP00

LP01

. . . Reqt.Description

Net val. incl. discount

Pallet discount

Incompl. pallet surch.

CalcForm

2224

BasForm

*Qty. in whole numbersFORM FRM_KOND_BASIS_022....ENDFORM.

*Qty. = 1 if incomplete palletFORM FRM_KOND_BASIS_024....ENDFORM.

Pallet discount5.00 /1 pallet

1 pallet = 10 boxes

Incomplete pallet surcharge20.00 /1 pallet

100.00

��Condition type LP00 allows you to define discount conditions that are taken into account only in the case of a whole unit of measure (for example, pallet, box). The unit of measure is assigned to the condition type. The condition type must be inserted at a suitable point in the calculation schema, with assignment of the base formula 22. The latter checks whether the order quantity is a whole number. The condition type is taken into account only in the case of whole numbers.

��Condition type LP01 allows you to specify surcharges that are taken into account only in the case of less-than-whole units of measure. The unit of measure (for example, pallet) is assigned to the condition type. The condition type must be inserted in the calculation schema at a suitable point with assignment of the base formula 24. The latter checks the order quantity and rounds up to a unit of the unit of measure that is assigned to the condition type.

��For mixed pallets, you can use the condition types LP02 (mixed pallet discount) and LP03 (incomplete mixed pallet surcharge). Both are designated as group conditions and permit cumulation of the quantities of the individual items. The scale formula 23 is assigned to condition type LP03. This eliminates the digits in front of the decimal point and checks for places after the decimal point.

��Condition types LP00, LP01, LP02 and LP03 are not included in the standard MM calculation schema RM0000.

��In all cases, the unit of measure that is assigned to the condition type must be maintained in the master records of the materials that are to be ordered.


� SAP AG 1999

Weight- and Volume-Dependent Conditions

Vendor AWeight-dep. surchargeUp toUp toUp to

2.00 per kg2.20 per kg2.50 per kg

10 kg30 kg50 kg

Material master recordBasic data

Material 1Net weight : 0.2 kg



Purchase order

Material 110 pc @ 0.2 kg



2 kg+

4 kg+

6 kg

= 12 kg

=> 26.40Surcharge

��You can maintain weight- or volume-dependent conditions if you have created condition types with the calculation types D, E or F and scale basis D, E or F. D = gross weight E = net weight F = volume

��The gross or net weight or the volume per order unit must be specified in the material master record or purchasing document item.

��Weight- or volume-dependent conditions can also be used as group conditions.


� SAP AG 1999

Condition Exclusion Procedure

Condition exclusion procedure AVendor A:vendor discount

Vendor A:discount for material 1

?Most favorable

condition value ?

Condition exclusion procedure CVendor A:vendor discount

Vendor A:?Most favorable sum of

condition values?

Condition exclusion procedure DVendor A:vendor discount

Vendor A:discount for material 1

?Either/or

?

discount for material 1+ discount for material 2

��If several condition records are valid for price determination purposes, you can define rules specifying which condition records are chosen and which are not taken into account. To do so, you use the condition exclusion procedure.

��The exclusion of condition records is controlled using exclusion groups. An exclusion group is a list of condition types that are compared with each other during the price determination process and lead to the exclusion of an entire group of condition types or individual condition types within a group.

��The result of the price determination process can be influenced according to a desired criterion (for example, the most favorable price) through the exclusion of certain condition types, while others are taken into account in this process.

��An exclusion group and an exclusion procedure are assigned to a calculation schema. ��The exclusion procedure specifies whether:

��The most or least favorable condition type within an exclusion group is chosen. ��The most or least favorable exclusion group is chosen. ��The existence of conditions of one condition type precludes the consideration of conditions of

other types (exclusive procedure).

(C) SAP AG LO521 6-10

� SAP AG 1999

� Create condition types for precious metal conditions by copying existing ones

� Examine the price determination process using precious metal conditions

� Describe the control parameters for condition types for delivery costs

� Explain the function of the pallet discount/surcharge condition types

� Describe how to maintain weight and volume dependent conditions

� Create a condition exclusion


Unit Summary

(C) SAP AG LO521 6-11

Special Condition Types and Special Functions Exercises

Unit: Special Condition Types and Special Functions Topic: Precious Metal Conditions


�� Create condition types for precious metal conditions by copying existing ones

�� Maintain precious metal conditions

�� Examine the price determination process using precious metal conditions

You purchase certain materials that contain a precious metal. Since the market price of the precious metal fluctuates, this influences the purchase price. There is a special condition category (“U”) for pricing components that vary from day to day. This condition category causes the price for the material to be newly determined at the time a purchase order is created and at the time a goods receipt is posted. This is based on the ruling market price for the precious metal on those dates.

1-1 Create a new condition type Z##1 with the description Met. price port. ## by copying the standard condition type GAU1.

Check the assignment of the unit of measure: the unit GAU (gram of gold) should be assigned to your new condition type.

Save your new condition type.

1-2 Create a second new condition type Z##2 with the description Curr. met. price ## by copying the standard condition type GAU2.

Check whether the unit of measure GAU has also been assigned to this condition type through the copying process.

1-2-1 Specify that for this condition type the current date is to be suggested as the validity start and end dates automatically.

Which control parameters in the condition type do you use to specify this? _____________________________________________________

Save your new condition type.

1-3 Change your calculation schema ZM00## by replacing the standard condition types GAU1 and GAU2 with your new condition types Z##1 and Z##2, respectively.

Also change your calculation schema YM00## by replacing the standard condition type GAU1and GAU2 with your new condition types Z##1 and Z##2, respectively.

(C) SAP AG LO521 6-12

Save your changes.

1-4 Change the material master record for material T-REN##. Assign the alternative unit of measure GAU (gram of gold) to the material.

One piece of material T-REN## has a precious metal content of 5 GAU.

1-4-1 What is the conversion formula for the units of measure?

______________________________________________________

______________________________________________________

Save your change.

1-5 Create an info record with the following data:

Vendor: T-L21C##

Material: T-REN##


Plant: Hamburg (1000)

Planned delivery time: 10


Standard quantity: 100

The gross price for the material is 120 UNI. This price includes 10 UNI per 1 gram of gold.

The conditions are valid from the first day of the current month until December 31 of next year.

When maintaining the conditions, use your condition type Z##1 for the metal price portion.

Save the info record.

1-6 Maintain the current prices for precious metals by creating condition records for your condition type Z##2.

Yesterday’s price was: 10.60 UNI per 1 GAU.

Today’s price is: 10.20 UNI per 1 GAU.

Save your precious metal conditions.


Vendor: T-L21C##

(C) SAP AG LO521 6-13

Document date: Yesterday!!!

Purchasing organization: IDES (1000)


Delivery date: Today

Order 1 pc of material T-REN## for plant Hamburg (1000), storage location 0001.

1-7-1 Go to the Conditions tab in the item details screen area of your purchase order and check the results of the price determination process:

Gross price: ______________________________________________

Metal price portion: ________________________________________

Current metal price: ________________________________________

Condition base value for Z##2 ________________________________

Condition value for Z##2 ____________________________________

Additional surcharges: ______________________________________

Discounts: _______________________________________________

Net price: ________________________________________________

Actual price: ______________________________________________

1-7-2 Display an analysis of the pricing log to determine the:

condition pricing date for Z##2: ______________________________


Purchase order number: _____________________________________

1-8 Post a goods receipt against your purchase order.

Material document number: ________________________________________

1-9 Display the accounting document for your goods receipt posting.

1-9-1 At which price was the material valuated at the time of goods receipt?

_________________________________________________________

_________________________________________________________

1-9-2 How do you explain the difference between the goods receipt value and the purchase order price?

(C) SAP AG LO521 6-14

_________________________________________________________

_________________________________________________________

(C) SAP AG LO521 6-15

Exercises

Unit: Special Condition Types and Special Functions Topic: Condition Exclusion Procedure


�� Compare the different condition exclusion procedures

�� Create a condition exclusion

In some instances, there are several conditions that are valid for the same item. In such cases, you can define which conditions are to be selected by using the condition exclusion procedure.

2-1 The calculation schema ZM00## is also to be valid for vendor T-L21D##. Therefore, assign your vendor schema group ## to this vendor by changing the purchasing data for purchasing organization IDES (1000) in the vendor master record.

2-2 Vendor T-L21D## supplies you with the materials T-REK##, T-REL##, and T-REM## with the following conditions, which are valid indefinitely:

For all three materials:

�� The planned delivery time is 7 days

�� The responsible purchasing group is LO521 Buyer (Z21)

�� The standard order quantity is 100 pc Create the info records for vendor T-L21D##, purchasing organization IDES

(1000), plant 1000, for all three materials.

2-2-1 Material T-REK##

Gross price: 10 UNI

Discount % on gross: 2.5%

2-2-2 Material T-REL##

Gross price: 100 UNI

Discount (value): 2 UNI from 1 pc 5 UNI from 100 pc

2-2-3 Material T-REM##

Gross price: 20 UNI

(C) SAP AG LO521 6-16

2-3 Your vendor T-L21D## advises you that he is granting you a general discount of 5%, valid indefinitely.

Create the vendor discount for condition type RL01.

2-4 This vendor discount applies only to those materials for which there is no material-specific discount.

Define two condition exclusion groups: A## with the description Material discounts ## and B## with the description Vendor discounts ##.

Save these condition exclusion groups.

2-5 Assign the discount condition types RA00, RA01, RB00 and RC00 to your condition exclusion group A##.

Assign the condition type RL01 to your condition exclusion group B##.

Save your assignments.

2-6 Assign the condition exclusion groups A## and B## and a suitable condition exclusion procedure to your calculation schema ZM00##.

2-6-1 Which condition exclusion procedure do you choose?

___________________________________________________

2-6-2 Pay attention to the order of the condition exclusion groups. In which order must you specify them? ______________________________________________________

(C) SAP AG LO521 6-17

2-7 Create a purchase order with the following data: Vendor: T-L21D## Purchasing organization: IDES Deutschland (1000) Purchasing group: LO521 Buyer (Z21) Delivery date: In four weeks (applies to all items) Plant: 1000 (applies to all items)

Order 10 pc of each of materials T-REK##, T-REL##, and T-REM##.

Go to each purchase order item and check the price determination process. How are the net prices for the following materials determined?

2-7-1 Material T-REK## _________________________________________________________ _________________________________________________________ _________________________________________________________

2-7-2 Material T-REL## _________________________________________________________ _________________________________________________________ _________________________________________________________

2-7-3 Material T-REM## _________________________________________________________ _________________________________________________________ _________________________________________________________

Purchase order number: _____________________________________

(C) SAP AG LO521 6-18

Special Condition Types and Special Functions Solutions

Unit: Special Condition Types and Special Functions Topic: Precious Metal Conditions

1-1 SAP menu �Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

1-2 SAP menu �Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

1-2-1 The Valid-from (= blank) and Valid to (= 0) default control parameters allow you to specify that the current date is suggested as the validity start and end dates when condition records are being created.

1-3 SAP menu �Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process� Define Calculation Schema.

Select your schema, then choose Control. Overtype GAU1 and GAU2.

1-4 SAP menu ��Logistics � Materials Management � Material Master � Material � Change � Immediately.

Select the Basic Data 1 view. Select Additional data, then choose Units of measure.

1-4-1 The conversion formula for the units of measure is 5 GAU = 1 pc

(C) SAP AG LO521 6-19


The value for your condition type for Gross Price (Z##A) will be 120, while your condition type Z##1 will be 10.

1-6 Favorites � Purchasing � Conditions � Other � Create.

Enter condition type Z##2. On the following screen, enter company code 1000. Change Valid on and select Enter. Valid to to yesterday’s date and enter the price. Save your work.

Do the same for today’s price.

1-7 Favorites � Purchasing � Purchase Order � Create � Vendor /Supplying Plant Known.

After entering the item, choose Purchase Order � Check.

1-7-1 Gross price: 120.00 UNI

Metal price portion: 10.00 UNI per 1 GAU = 50.00 UNI per 1 pc

Current metal price: 10.60 UNI per 1 GAU = 53.00 UNI per 1 pc

Condition base value for Z##2 5 GAU

Condition value for Z##2 53.00 UNI (10.60 x 5 GAU)

Additional surcharges: 30.00 UNI

Discounts: None

Net price: 153.00 UNI

Actual price: 153.00 UNI (This surcharge may appear due to a surcharge condition type created in a prior unit.)

1-7-2

Condition pricing date Yesterday’s date

Purchase order number: _______________________________________

1-8 SAP menu ��Logistics � Materials Management � Inventory Management ��Goods Movement � Goods Receipt � For Purchase Order � PO Number Known.

Enter your purchase order number and choose Enter.

When your line item appears, select OK, then save.

Material document number: __________________________________________

(C) SAP AG LO521 6-20

1-9 SAP menu ��Logistics � Materials Management � Inventory Management ��Material Document � Display.

On the overview screen for the material document, choose Environment � Accounting docs, and then the document category Accounting document.

1-9-1 The material was valuated at 151.00 UNI.

1-9-2 The valuation price at the time of goods receipt differs from the order price due to the different market price for precious metals that applies on the goods receipt date.

To be specific, the goods receipt valuation price of 151.00 UNI is 2.00 UNI less than the 153.00 UNI order value on the purchase order.

In the previous exercise you entered

yesterday’s price of 10.60 UNI

and today’s price of 10.20 UNI.

This is a decrease of 0.40 UNI. Therefore, 0.40 UNI x 5 GAU = 2.00 UNI decrease.

(C) SAP AG LO521 6-21

Solutions

Unit: Special Condition Types and Special Functions Topic: Condition Exclusion Procedure



2-3 Favorites � Purchasing � Conditions � Discounts/Surcharges � By Vendor.

Enter your vendor, purchasing organization 1000, then choose Execute.

Select the purchasing organization under RL01, then choose Create.

2-4 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Exclusion Choose Condition Exclusion Groups.

2-5 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Exclusion Choose Condition Exclusion Groups - Condition Types.

2-6 SAP menu � Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Exclusion � Condition Exclusion Procedure Assignment.Select your schema ZM00##, then choose Exclusion.

Sno = 1

Cpr = D (exclusive)

ExGr1 = A##

ExGr2 = B##

(C) SAP AG LO521 6-22

2-6-1 You choose the exclusive procedure. This procedure states that the condition types of the second condition exclusion group are not taken into account if conditions types of the first condition exclusion group are found.

2-6-2 Condition exclusion group A## must be specified as ExGr1 and condition exclusion group B## as ExGr2. They must be specified in this order, since the general vendor discount is applied only if there is no relevant material-specific discount, That is, if the R/3 System finds an applicable condition from the A## group, that excludes the transaction from proposing conditions that belong to the B## group.

2-7 Favorites � Purchasing � Purchase Order � Create � Vendor /Supplying Plant Known. 2-7-1 Material T-REK##: 9.75 (10.00 gross price less 2.5% RA01 discount).

The vendor discount RL01 appears but is inactive and is not included in the calculation since there was a material-specific discount.

2-7-2 Material T-REL##: 99.80 (100.00 gross price less 2 UNI RB00 discount). The vendor discount RL01 appears but is inactive and is not included in the calculation since there was a material-specific discount.

2-7-3 Material T-REM##: 19.00 (20.00 gross price less 5% vendor discount RL01). There was no material-specific discount for this item, so the vendor discount applied.


� SAP AG 1999

� Prerequisites for Rebate Arrangements

� Conditions in Rebate Arrangements

� Updating of Business Volumes

� Settlement and Extension of Rebates


Contents:


� SAP AG 1999

� Define the process of subsequent settlement with regard to end-of-period rebates granted by vendors

� Create a rebate arrangement and carry out the related settlement

� Describe the process of cumulative business volume updating


Subsequent Settlement: Unit Objectives


� SAP AG 1999

� Your vendor may offer you a rebate at the end of the year if you do a certain amount of business with him. The subsequent settlement process allows you to create a rebate arrangement to record this agreement.

Subsequent Settlement: Business Scenario


� SAP AG 1999

Subsequent Settlement: Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Negotiations with vendor

Pur. order

Create/maintainrebate arrangement

Invoice Invoice

Cumulative busn. volume updates over period

From01.01.

to12.31

12.31. Busn. vol. comp. Settlement acctg. Credit memo

?

From business volume of 20,000 upwards:

1 % volume rebate

End-of-Period Rebates: Overview

��A rebate arrangement (sometimes referred to simply as an ”arrangement”) consists of a number of agreed conditions requiring ”subsequent settlement” that are valid during a certain period (for example, a fiscal year) and for which settlement accounting is to take place at the same point in time. Settlement accounting with the vendor regarding conditions requiring subsequent settlement (as opposed to conditions that come into effect immediately and relate to individual business transactions) has to be carried out retrospectively, at the end of a certain period.

��Within the overall validity period of a rebate arrangement, the cumulative figures on the volume of business done with the vendor (purchases made) are updated continually for each condition on the basis of the verified vendor invoices. This updated data then serves as the basis for automatic settlement.

��At the end of the overall validity period of an arrangement or at the time of interim or partial settlement, the rebate income in respect of the conditions for which settlement is due is calculated and the data posted in Financial Accounting. The outstanding cumulative business volumes qualifying for end-of-period rebates (that is, the portion of the total for which no rebate has yet been paid) are taken as the basis for this process.

��If your enterprise has arranged with the vendor to carry out a business volume comparison and agreement process prior to settlement, the business volume figures recorded by each party over the period are compared with each other and reconciled before final settlement accounting takes place.


� SAP AG 1999

Prerequisites

VendorSubseq. sett.BV comp.

Rebate arrangement

Reb. arrangementArrang. typeCond. granterCurrencyValidityBusn. vol. comp.Conditions

Condition tablesCondition types

Customizing: arrangement typeSettlement typeSettlement calendarArrangement calendarCondition type group

Settlementstatement

��To enable rebate arrangements entered into with a vendor to be created in the R/3 System and for settlement accounting to take place with respect to such arrangements, the Subsequent settlement indicator must be set in the vendor master record.

��A rebate arrangement must be assigned to an arrangement type. The latter specifies whether the arrangement relates to a vendor in general or to specific materials. Arrangement types are defined in Customizing and contain default values and control parameter,s such as the following: ��Arrangement and settlement calendars

The arrangement calendar specifies the end of the validity periods of rebate arrangements and controls the extension of the latter. The settlement calendar specifies the points in time at which partial settlements are to be effected.

��Condition type group The condition type group indicates which condition types and condition tables can be used for an arrangement type.

��Settlement type The settlement type determines whether debit-side or credit-side settlement is to be effected with respect to a rebate arrangement in Purchasing and whether settlement accounting is to be carried out at plant or purchasing organization level. “Debit-side settlement” means that Purchasing issues one or more billing documents to the vendor (settlement documents are billing documents in Sales and Distribution). “Credit-side settlement” means that the vendor issues one or more credit notes to Purchasing (settlement documents are credit notes).


� SAP AG 1999

Conditions in Rebate Arrangements

Rebate arrangementArrangement type:Condition granter:Currency:Validity:Settlement:

Material rebateVendor AUNI01.01. - 12.31.Quarterly

Main conditions

1) Material 1 1 %ScaleFrom 10,000 UNI 1%From 20,000 UNI 2%From 30,000 UNI 3%

Period condition01.01. - 03.31. 1%04.01. - 06.30. 1%. . .

Period condition04.01. - 06.30. 5%07.01. - 09.30. 5%

2) Material 2 5 %Validity 04.01. - 09.30.

��When a rebate arrangement is created, the main conditions are defined at the highest level. A main condition relates to an individual stipulation within an arrangement. Each main condition contains a certain rebate (for example, fixed amount, percentage) and is assigned to a condition type.

��In Customizing, you can specify whether a provision for accrued rebate income is to be created in respect of a certain condition type.

��Settlement accounting with respect to a rebate arrangement is always carried out with the main condition.

��A main condition can be scaled and/or subject to periodic settlement. Periodic settlement is possible only if a settlement calendar has been assigned to the rebate arrangement. The settlement calendar specifies the points in time at which partial settlements are to be effected.

��Conditions requiring periodic settlement are supplementary conditions applicable in relation to a main condition within a certain period. The main condition lays down the overall timeframe: that is, the validity periods of period-specific conditions may not lie outside the validity period of the main condition. Period-specific conditions are created automatically if a rebate arrangement is based on a settlement calendar. The periods of the period-specific conditions correspond to the periods of the settlement calendar. The periods cannot be changed once a rebate arrangement has been created.

��For individual periods, you can specify conditions that vary from the main condition.


� SAP AG 1999

Purchase orderVendor A10 pc mat. 1Sett. acctg.

-

InvoiceVendor A10 pc mat. 1

@ 10.00

100.00

Rebate arr. no. 99Vendor A01.01. - 12.31.Cond. type A001

Info recordVendor AMaterial 1No s. acctg.

Purchase orderVendor A10 pc mat. 1

@ 10.00

Goods receipt10 pc mat. 1

Accounting documentGR/IRStock account

100.00100.00

Business volume updatePeriod Rebate arr. Vendor Pur. org. Prov. value

. . . 99 A 1000

Busn. vol.

100.00

. . .

. . .

ConditionsPB00 100.00A001 0 %

Accrual

Cumulative Updating of Business Volumes

��The basis for cumulative business volume updates is the purchase order. When a purchase order is created, a price determination process takes place. If, in the course of this process, a condition is found that involves the creation of a provision for accrued rebate income (Accrual indicator set for condition type), the value of this provision is shown in the purchase order. In the case of conditions that do not have this indicator, the value 0 is shown.

��The business volume update for subsequent rebate settlement takes place at the time of invoice receipt as per the date on the vendor’s invoice. The data from a successfully verified vendor invoice serves as the basis for settlement accounting.

��Cumulative updating takes place for each settlement period if settlement takes place monthly or more frequently. If settlement takes place less frequently than monthly, cumulative updating nevertheless takes place on a monthly basis. This is to ensure that monthly statistics can subsequently be created.

��The Statement function enables you to display a list of all statistical records created within the framework of the cumulative business volume update process with respect to a rebate arrangement. To see all the purchasing documents covered by a rebate arrangement in addition to the statistical data, you can use the Detailed statement function.


� SAP AG 1999

Comparison/Agreement of Business Volumes

BV comparisonRebatearrangementCond. granterBV comp.

Comparison of business volumesVendor‘s statistics

Mat. 1: 2450.00Mat. 5: 3800.00Mat. 8: 1610.00

Own business volume statistics

Mat. 1: 2450.00Mat. 5: 3800.00Mat. 8: 1620.00

Settlement basis

Agreed value1615.00

Final settlement

��Internally (that is, within your enterprise’s R/3 System), the cumulative figures for the volume of business done with the vendor (purchases made) are continually updated for the purposes of subsequent settlement. At the same time, the vendor is keeping its own figures for the volume of business done with your enterprise (sales made). These two sets of figures might differ. The purpose of the business volume comparison and agreement process is to permit reconciliation of any such differences prior to settlement, thus eliminating the need for any subsequent correction.

��In the case of discrepancies between the two sets of figures, an ”agreed value” can be entered. This latter value is then taken into account in the settlement accounting process that follows.

��If you have arranged to carry out the business volume comparison and agreement process with your vendor prior to settlement, the Business volume comparison indicator must be set in the rebate arrangement.

��If it has been stipulated that the business volume comparison and agreement process is to be carried out with the vendor prior to final settlement and the Business volume comparison indicator has been set in the rebate arrangement, the R/3 System will not allow final settlement accounting to be effected until this process has taken place.

��If your business volume statistics agree with the vendor’s figures, you should not save the business volume comparison but cancel (that is, deselect) the Business volume comparison indicator in the rebate arrangement.

(C) SAP AG LO521 7-10

� SAP AG 1999

Settlement

01.01. 12.31.

Validity period of rebate arrangement

Partial settlement

One-time settlement

Final settlementInterim settlement

Partial settlement

Settlement document(credit memo)

Settlement list

Blocking of affectedcondition records

Status of rebate arrangement:Settlement effected

Statistical apportionment ofrebate income at plant level

Final settlement

Settlement document (credit memo)Scales taken into account

Settlement list

Blocking of condition recordsDeactivation of business vol. updating

Status of rebate arrangement:Final settlement effected for rebate arr.

Statistical apportionment ofrebate income at plant level

��Settlement accounting can be effected with respect to a rebate arrangement if conditions are due for settlement and cumulative business volume data (update data) relating to these conditions exists.

��Rebate arrangements are subdivided into those requiring once-only settlement and those requiring periodic settlement. Settlement accounting with regard to rebate arrangements requiring once-only settlement is carried out as per the validity end date of the arrangement. With regard to rebate arrangements requiring periodic settlement, partial and final settlement is carried out in accordance with the periods specified in the settlement calendar.

��Partial settlement means settlement with regard to a “periodic” rebate arrangement, where the settlement date lies before the validity end date of the rebate arrangement. When partial settlement accounting has been carried out with regard to a rebate arrangement, the condition records are blocked and the rebate arrangement acquires the status Settlement effected.

��Final settlement means the concluding settlement with respect to a rebate arrangement upon expiration of the latter’s validity period, taking into account any already effected partial and interim settlements. In the case of periodic settlements, the last settlement to be effected within the validity period of a rebate arrangement is the final settlement. When final settlement accounting has been carried out with regard to a rebate arrangement, the condition records are blocked and the updating of the business volume statistics deactivated. In addition, the status of the rebate arrangement is set to Final settlement effected for rebate arrangement.

��Interim settlement can be carried out both for rebate arrangements requiring once-only settlement and for those requiring periodic settlement. In the case of an interim settlement, the end date of the current period must be specified as the settlement date and the Interim settlement indicator set for the settlement run. Interim settlement means settlement accounting in respect of vendor business volume carried out prior to expiration of the validity period, facilitating the generation of rebate income in advance of the due date.

��Following a successful settlement run the relevant data is posted in Financial Accounting automatically.

(C) SAP AG LO521 7-11

� SAP AG 1999

Extension of Rebate Arrangements

01.01.97 12.31.2000Arrangement calendar

01.01.97 12.31.97

Rebate arr. no. 10Arrang. type: 1000Arr. calendar: AJValidity: 01.01.- 12.31.97

Final settlement

Extension of rebate arr.

Rebate arr. no. 34

01.01.98 12.31.98

Deactivation of busn.volume updating

Activation of busn.volume updating

Businessvolumeupdates

Businessvolumeupdates

!!

��Rebate arrangements entered into with a vendor are often long-term arrangements lasting several years or even indefinitely. In the R/3 System, however, they are usually initially created for a shorter period, such as the current calendar year.

��Rebate arrangements can be extended if the arrangement conditions are to remain in effect for a new validity period.

��A prerequisite for the extension of a rebate arrangement is that an arrangement calendar has been assigned to the relevant arrangement type in Customizing. The arrangement calendar specifies the validity end date of a rebate arrangement. It also specifies the period by which an arrangement is to be extended.

��The Extend arrangement function allows you ”extend” an existing rebate arrangement by creating a new, follow-on arrangement with an adjusted validity period. The validity start date of the new arrangement is the day after the validity end date of the arrangement that is to be extended. The end date is determined from the arrangement calendar.

��A rebate arrangement must be extended in good time, before the creation of the first purchase order within the new arrangement validity period, so that the business volume data can be recorded correctly. You can display rebate arrangement extensions.

��If a rebate arrangement is not to be extended, you can delete the arrangement calendar from the last valid arrangement by choosing the Remove agreement calendar function from the Extras menu while in arrangement maintenance mode. If you later decide to extend the arrangement after all, you can reassign the arrangement calendar to the rebate arrangement in similar fashion.

(C) SAP AG LO521 7-12

� SAP AG 1999

Retrospective Compilation of Statistics

01.01. 12.31

Rebate arrangement01.01. - 12.31.

Purchase orderGR, IR



Retrosp. compilation of statistics Autom. updating of busn. vols.

Retrospective compilation of statistics

Vendor master rec.:

Purch. order item:

Report RMCENEUA/RMEBEIN3:

Comp. of index structure S111

Report RWMBON08 (update run, version 000):comp. of info structures S015, S074

subsequent settlementsubseq. settlement index

settlement accounting

��The cumulative vendor business volumes are continually updated in statistical records of the info structures S015 and S074 when invoices are entered relating to purchase orders whose price determination process takes into account conditions requiring ”subsequent settlement” (that is, which relate to end-of-period rebates). You can compile these statistics retrospectively. Such retrospective compilation of the statistics is necessary if the validity start date of a rebate arrangement lies before the date the arrangement is entered in the R/3 System. In this case, all purchase orders issued prior to this date of entry must be treated as though the arrangement conditions had already been valid on the PO date.

��If you know that you will have to compile the business volume statistics for a vendor retrospectively, you should set the Subsequent settlement index indicator in the master record of the vendor in question. This indicator causes relevant data to be logged in an index (info structure S111) when a purchase order is created. The indicator should be set only if it is clear that retrospective compilation of the statistics will be necessary for a vendor, otherwise the volume of data would be inflated unnecessarily.

��The retrospective compilation of business volume statistics is based on the index structure S111. It is carried out using report RWMBON08, which you can access from the Purchasing menu The report updates the vendor business volumes in the info structures S015 and S074. If you failed to set the Subsequent settlement index indicator in the vendor master record in good time, you can have the index structure S111 compiled retrospectively using report RMCENEUA or (as of 4.0A) RMEBEIN3.

(C) SAP AG LO521 7-13

� SAP AG 1999

� Define the process of subsequent settlement with regard to end-of-period rebates granted by vendors

� Create a rebate arrangement and carry out the related settlement

� Describe the process of cumulative business volume updating


Subsequent Settlement: Unit Summary

(C) SAP AG LO521 7-14

Subsequent (End-of-Period Rebate) Settlement Exercises

Unit: Subsequent (End-of-Period Rebate) Settlement

At the conclusion of this exercise, you will be able to: �� Define the process of subsequent settlement with regard to

end-of-period rebates granted by vendors �� Create a rebate arrangement and carry out the related

settlement

�� Describe the process of cumulative business volume updating

Your vendor may offer you a rebate at the end of the year if you do a certain amount of business with him. The subsequent settlement process allows you to create a rebate arrangement to record this agreement.

1-1 You have entered into a volume-based, period-end incentive rebate arrangement with vendor T-L21E## and want to record this arrangement in the R/3 System.

First check that the Subsequent settlement indicator has been set in the vendor master record for purchasing organization IDES Deutschland (1000).

If not, set it and save your change.

1-2 Vendor T-L21E## grants a general volume-based, period-end, incentive rebate of 0.5% on all materials, increasing to 2.5% on a business volume of 5000 UNI upwards.

1-2-1 Which agreement type do you choose? ______________________________________________________

1-2-2 The overall arrangement validity period is to start on today’s date and end on December 31 of the current year. Check the default validity period.

A business volume comparison and agreement process is optional, but not mandatory.

Maintain the arrangement conditions, including the necessary scale.

1-2-3 Check the period-specific conditions. Has a condition been created for each month within the overall validity period of the rebate arrangement?

______________________________________________________

1-2-4 Use your material T-REK## as the settlement material.

Save your rebate arrangement.

(C) SAP AG LO521 7-15

Acknowledge any warning messages that are displayed regarding currency conversions by choosing Enter.

Arrangement number: ____________________________________


Vendor: T-L21E## Purchasing organization: IDES Deutschland (1000) Purchasing group: LO521 (Z21) Delivery date: Today Plant: Hamburg (1000) Storage location: Materiallager (0001) Order 60 pc of material T-REL## at a price of 100 UNI. Tax code: 0I

1-3-1 Go to the Condition tab for your purchase order item and check whether a condition record for condition type A001 (volume-based incentive rebate) was found. Save your purchase order.

Purchase order number: __________________________________________

1-4 Post a goods receipt against your purchase order.

Material document number: ________________________________________

1-5 You receive the invoice from the vendor. Enter this invoice with reference to your purchase order. Specify today’s date as the document date and period baseline date. The invoice amount is 6000 UNI. Change the default tax code to 0I (Input tax Training 0%). Save your invoice.

Invoice document number: ________________________________________

1-6 If your invoice was blocked for payment, release it now.

1-7 Display the cumulative business volume update figures for your rebate arrangement.

1-7-1 What is the figure for the scale basis?

________________________________________________________

1-8 Simulate the settlement accounting for your rebate arrangement for the end of the current year, using the report function.

(C) SAP AG LO521 7-16

Enter the last day of the current year as Settlement date and the current date as the Posting date.

Be sure to choose Simulate on the initial screen.

1-8-1 What is the simulated value of the rebate for the subsequent settlement?

________________________________________________________

(C) SAP AG LO521 7-17

Subsequent (End-of-Period Rebate) Settlement Solutions

Unit: Subsequent (End-of-Period Rebate) Settlement



1-2 SAP menu ��Logistics � Materials Management � Purchasing � Master Data � Subsequent Settlement � Vendor Rebate Arrangements � Rebate Arrangement � Create.

Enter the agreement type and choose Enter. If prompted, use purchasing group Z21.

Enter the vendor as the Condition granter.

1-2-1 The agreement type is 1000. If a rebate arrangement applies to all the materials supplied by a vendor, the agreement type Vendor rebate (key 1000 in the standard system) should be chosen.

1-2-2 To maintain the conditions, choose Conditions, and then choose Vendor.

1-2-3 Yes. From the conditions screen, choose Go to � Period-spec. condit.

1-2-4 Go to � Matl for settlement.

1-3 Favorites � Purchasing � Purchase Order � Create � Vendor/Supplying Plant Known. Use tax code 0I if needed.

1-3-1 Choose Conditions in the item details screen area.

1-4 SAP menu �� Logistics � Materials Management � Inventory Management �� Goods Movement � Goods Receipt � For Purchase Order � PO Number Known.

Enter your purchase order number, then choose Enter.

When your line item appears, select OK. Save your work.

1-5 SAP menu ��Logistics � Materials Management � �Logistics Invoice Verification � Document Entry � Enter Invoice.

Invoice date: Today

(C) SAP AG LO521 7-18

Amount: 6000

Tax amount: 0I Input Tax (Training) 0%

Also enter your purchase order number.

Baseline date: Today

If you get a warning message about exceptions, choose Enter to accept it.

1-6 SAP menu ��Logistics � Materials Management ��Logistics Invoice Verification � Further Processing � Release Invoices Enter your vendor T-L21E##, then choose Execute.

If your invoice is listed, select the blocking reason for your invoice and choose Cancel blocking reason.

1-7 SAP menu ��Logistics � Materials Management � Purchasing Master Data � Subsequent Settlement � Vendor Rebate Arrangements� List Displays � Business Volume Data.

Enter your arrangement number, then choose Execute.

1-7-1 6000 UNI

1-8 SAP menu ��Logistics � Materials Management � Purchasing Master Data � Subsequent Settlement � Vendor Rebate Arrangements � Rebate Arrangement � Create Settlement Document � Via Report.

Enter your rebate arrangement number and the settlement and billing (posting) dates.

Under Control data: settlement run, select Simulate.

Choose Execute.

Choose Yes at the Confirmation prompt.

1-8-1 A rebate value of 30 UNI.


� SAP AG 1999

� Calculation Schemas

� Condition Types

� Access Sequences

� Condition Tables

� Routines and Adjusting the System

Customizing

Contents:


� SAP AG 1999

� Outline the ways in which the price determination process can be influenced through Customizing

� Explain when you have to work with formulas and requirements of your own or carry out system modifications

� Review the most important control parameters for calculation schemas, condition types and access sequences


Customizing: Unit Objectives


� SAP AG 1999

� You want to adapt the price determination process to suit the specific needs of your organization using Customizing. Additional adjustments can be made using your own program subroutines.

Customizing: Business Scenario


� SAP AG 1999

Customizing: Overview Diagram

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999

Customizing SD❍ Define requirements❍ Define formulas

Customizing MM❍ Maintain condition table(s)❍ Maintain access sequence(s)❍ Maintain condition type(s)❍ Maintain calculation schemas

System adjustment❍ Extend condition structures by adding new fields❍ Supply new fields from document❍ Activate user exits❍ Extend catalog of allowed fields

Overview

��The Customizing functionality for Purchasing enables you to: ��Create, change, and display access sequences ��Create, change, and display condition types ��Set upper and lower limits for the conditions belonging to a condition type ��Define exclusion indicators for condition exclusion ��Create, change, and display calculation schemas ��Create schema groups for purchasing organizations or vendors, and assign them to purchasing

organizations ��Define the process of determining the calculation schema ��Define condition exclusion groups and condition exclusion procedures ��Create, change, and display condition tables ��Extend the field catalog for condition tables

��In Customizing for Sales and Distribution, you can define the requirements for price determination and formulas for determining and calculating the scale basis, the condition basis, the condition value or the group key in the form of ABAP form routines.


� SAP AG 1999

Customizing: Calculation Schema

Step Count. C.ty. From To Mand.

1 10 PB00

Man. Stat. Print Subtot. Accr.

X 1

. . .

Basis for percentagediscounts/surcharges

Autom. determination/manual maintenance

Mandatory

Statistical

Print indicator

Subtotaling of condition values

Transaction/event key for account determination

��The calculation schema includes the following information: ��Which condition types are to be taken into account and in which order (Step and Count.) ��The basis for percentage discounts or surcharges (From and perhaps To) ��Whether conditions of a certain type are determined automatically or have to be entered manually

(Man.) ��Whether the condition type is mandatory (Mand.) ��Whether a condition is taken into account in the net price calculation (Stat.) ��Whether and how condition lines are to be printed (Print) ��Whether and in which fields condition values or subtotals are to be stored for further processing

(Subtot.). ��The prerequisites for precluding accesses of a certain condition type (Reqt.) ��Which non-standard formula is to be used for calculating the condition value (Calc.frm)Which

non-standard formula is to be used for calculating the condition basis (BasFrm) ��The transaction/event key through which the G/L account for a provision-relevant condition type is

found (Accr. or AccKy if purchase account processing is active).


� SAP AG 2001

Customizing: Condition Type

Cond. class

Calculation type:

Condition cat.:

Control data 1

Header condition

Group Conditions

Item condition

+/- sign

Access Sequence

Group Conditions

Manual entry

Condition type ZXYZ

Change options

Master dataPricing procedure

Scale basisScales

Scale type

AccrualControl data 2

...

...

...

...

...

...

��A condition type defines the properties and characteristics of a pricing element. Condition types are defined in Customizing. You should not change the standard condition types.

��If conditions with their own validity period are to be maintained for a certain condition type, this condition type must have an Access sequence assigned to it.

��A Condition class (e.g. A = discounts or surcharges) and a Calculation rule ("calculation type" field) must be assigned to a condition type. The calculation rule specifies whether the condition amount is defined as an absolute amount, an amount per unit of quantity, weight, or volume, or as a percentage. Furthermore, a Condition category may have to be assigned to the condition type.

��A condition type can be defined as a Header condition and/or an Item condition, as well as a Group condition.

��The Plus/minus sign determines whether the condition type is treated as a discount (deduction) or surcharge (addition).

��Whether condition amounts or values can be changed or deleted is determined by the change options, particularly by the Manual entry field.

��A Calculation schema (”pricing procedure”) for supplementary conditions must be assigned to the condition type for the gross price.

��The scale basis for a scale defines how the R/3 System interprets a condition price scale. For example, the scale can be based on a value, a quantity or a weight.

��Using the Scale type, you specify whether the scale values of the condition represent the upper or lower limit for the price, discount or surcharge.


� SAP AG 1999

Customizing: Access Sequences

Access sequence0002 Gross price

AccessesSNo.10152025. . .

Tab.68166717

DescriptionAgreement item, plant-dependentContract itemPlant info record per order unitMaterial info rec., plant-dependent

Requirement

3635

Excl.

FieldsConditionLIFNRMATNREKORGWERKSESOKZ

Doc. structureKOMKKOMPKOMKKOMPKOMP

Doc. fieldLIFNRMATNREKORGWERKSESOKZ

Direct value source

��The access sequence is a search strategy through which you specify the order in which condition tables are to be searched for relevant entries for a condition type.

��The order of access is determined by the order of the condition tables in the access sequence. ��Using requirement routines, you specify the prerequisites according to which the R/3 System

searches through certain condition tables for relevant entries. Requirement routines can be created in Customizing for Sales and Distribution as ABAP form routines.

��You use the Exclusive indicator to specify that the search for further valid conditions in (other) condition tables is stopped if an access was successful and a relevant entry found.

��The field contents with which a condition table is to be accessed are also defined in the access sequence, through the assignment of source fields from the document to the key fields of the condition table. Typically, accessing of the condition tables is carried out with the content of a field from the document header and/or the document item. However, you can specify a Direct value for the access. To define your own access sequences, the key should begin with the letter Z. When creating your own access sequences, pay special attention to the order of the fields. It is detrimental to system performance if a header field follows an item field in the field sequence.

��You should not change the standard access sequences.


� SAP AG 1999

Customizing: Condition Tables

Table 999

Technical view

Selected fieldsPurch. organizationPurchasing doc.

With validity period

ChooseLineTextField name EVRTN. . .

Activate

Table A999 activatedReports and screen flagged for generation

Field catalogOrder unitCompany codePurch. organizationPurchasing doc.. . .

��Condition tables refer to condition records. Condition tables enable you to vary the key structure of condition records. You should not change a standard condition table.

��You can create your own condition tables. The name of the table must be a number between 501 and 999. If you make no specification, the R/3 System assigns a sequential number.

��To create a new condition table, you must first check whether the existing fields in the field catalog are sufficient for your requirements. You may first have to extend the field catalog. You can include all the fields of the communication structures KOMK, KOMP and KOMG in the field catalog.

��To maintain time-dependent conditions, your new condition table must be defined as a condition table with a validity period.

��Choose the key fields for your condition table from among the allowed fields (fields in the field catalog).

��Finally, you must generate your condition table. Through the generation process, your new condition table is activated and the reports and screens for condition maintenance flagged for generation.

��You can maintain conditions for a new condition table only if the condition table is used in an access sequence.

(C) SAP AG LO521 8-10

� SAP AG 1999

Routines: Formulas and Requirements

Step Count. C.ty.

1 2 PBXX

Calc. for. Bas. for.. . . . . .Reqt.

6

S .no. Tab Reqt.

25 17 35

Access sequence

Source text

ABAP 14: Editor Program LV61A035FORM KOBED_035.SY-SUBRC = 4.CHECK KOMP-NO017 EQ SPACE. SY-SUBRC = 0.

ENDFORM.FORM KOBEV _035.SY-SUBRC = 0.

ENDFORM.

��Requirements and formulas for price determination are defined as ABAP form routines in Customizing for Sales and Distribution.

��A requirement sets out the prerequisites according to which a system access of a certain condition type or a certain access sequence takes place or is precluded.

��Formulas influence the calculation of prices according to predefined rules and are used at various points in the overall price determination process. There are the following groups of formulas: ��Scale basis: You can assign a formula for calculating the scale basis in the Scale formula field in

Customizing for the condition type. ��Condition basis – You can assign a formula for calculating the condition basis in the Base formula

field in Customizing for the calculation schema. ��Condition value – You can assign a formula for calculating the condition value in the Calculation

formula field in Customizing for the calculation schema. ��Group key – You can assign a formula for calculating the scale basis in the case of group

conditions in the Group condition routine field in Customizing for the condition type. ��Rounding rules – You can assign a formula for rounding purposes in the Rounding rule field in

Customizing for the condition type.

(C) SAP AG LO521 8-11

� SAP AG 1999

Adjusting the System

1 Extendconditionstructure

2 Supply newfield from document

Communication structure KOMG. . .INCLUDE. . .INCLUDE

KOMPAZKOMKAZField nameZZEKGRP

Data elementEKGRP

*** INCLUDE ZXM06U14.MOVE I_KOMK TO E_KOMK. MOVE I_EKKO-EKGRP TO E_KOMK_ZZEKGRP.

3 Activate user exit

Project management of SAP enhancements- Create project with enhancement LMEKO001

and/or LMEKO002- Activate project

4 Customizing Extend field catalog for condition tables. . .

��To use your own fields for the price determination process, you must extend the communication structure KOMK, KOMP or KOMG. The structure KOMG represents the sum of KOMK and KOMP and contains all the fields that can be used in price determination. New fields entered in KOMK or KOMP are adopted in the structure KOMG automatically.

��New fields for price determination must be inserted in the following INCLUDEs: ��Header data in the INCLUDE KOMKAZ (INCLUDE in KOMK/KOMG) ��Item data in the INCLUDE KOMPAZ (INCLUDE in KOMP/KOMG).

��You must ensure that the new field in the communication structure is filled with a value from the document. This is achieved by using appropriate MOVE or MOVE-CORRESPONDING instructions in the INCLUDE program ZXM06U14 or ZXM06U15, which you must either create or change.

��A MOVE instruction MOVE I_KOMK TO E_KOMK or MOVE I_KOMP TO E_KOMP is always necessary for technical reasons.

��The INCLUDE programs are invoked using the following function modules: ��INCLUDE ZXM06U14 via EXIT_SAPLMEKO_001 (enhancement KOMK) ��INCLUDE ZXM06U15 via EXIT_SAPLMEKO_002 (enhancement KOMP).

��The function modules are invoked using the following user exits (enhancements): ��Function module EXIT_SAPLMEKO_001 via the user exit LMEKO001, ��Function module EXIT_SAPLMEKO_002 via the user exit LMEKO002.

(C) SAP AG LO521 8-12

� SAP AG 1999

� Outline the ways in which the price determination process can be influenced through Customizing

� Explain when you have to work with formulas and requirements of your own or carry out system modifications

� Review the most important control parameters for calculation schemas, condition types and access sequences


Customizing: Unit Summary

(C) SAP AG LO521 8-13

Customizing Exercises

Unit: Customizing


�� Create a working price determination process by building and linking all the components for conditions and prices

Your project team has been asked to create and test a complete price determination strategy for the company. You will create all the necessary price determination components and ensure that they function properly together.

1-1 Quick Review of Terms: In your own words, describe and give an example of the following terms. If you are working with a partner, explain these terms to that person.

1-1-1 Condition Table: ______________________________________________________

______________________________________________________

1-1-2 Access Sequence: ______________________________________________________

______________________________________________________

1-1-3 Condition Type: ______________________________________________________

______________________________________________________

1-1-4 Calculation Schema: ______________________________________________________

______________________________________________________

1-1-5 Condition Records: ______________________________________________________

______________________________________________________

1-1-6 Condition Group: ______________________________________________________

(C) SAP AG LO521 8-14

______________________________________________________

1-2 The Design Phase: You will be building a price determination strategy from the bottom up. Your management has asked you to implement a new condition group discount that will be applicable only to certain vendor-material combinations, grouped together by condition groups. Before proceeding, make some brief notes on what has to be done in terms of configuration and master data, and in what sequence. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

1-3 Condition Table: Create and save a new condition table named 7##. This table should be created with reference to condition table 45 (Vendor/Purch.org./Cond.group) and should include the vendor, purchasing organization, and condition group fields. Include your group number in the description of the new condition table.

1-4 Generate the table.

If you are warned that a table with the same fields already exists, choose Enter to proceed.

Save the table as a local object.

1-5 Access Sequence: Create and save a new access sequence, ZS##, that includes your new condition table 7##.

1-6 Condition type: Create and save a new condition type ZG## by copying condition type RGR0. Enter a description that includes your group number. Link condition type ZG## to your access sequence ZS##. The valid-to date for condition records should default to the end of the current year. Scales will be on the basis of quantity.

1-7 Calculation schema: Create and save a new calculation schema called Z##CGR by copying the existing calculation schema RM0000.

During the copying process, the R/3 System will repeatedly issue the warning message You should use the counter only for manual item conditions. Acknowledge this warning by choosing Enter each time.

(C) SAP AG LO521 8-15

1-8 Add your new condition type ZG## to your new calculation schema Z##CGR in place of the RGR0 condition type by overtyping the RGR0 value with ZG##. Save the calculation schema.

1-9 Create a new vendor schema group: On the table below, find your group number. Then create the vendor schema group listed.

Group number Schema group

01 A 02 B 03 C 04 D 05 E 06 F 07 G 08 H 09 I 10 J 11 K 12 L 13 M 14 N 15 O 16 P 17 Q 18 R 19 S 20 T

1-10 Determination of Calculation Schema: You now need to link your new vendor schema group to your calculation schema Z##CGR.

1-11 Changing your master data:

1-11-1 Change the master record of vendor T-L21D## in purchasing organization 1000 by entering the vendor schema group you just created.

1-11-2 This new group condition applies when you purchase material T-REM## from vendor T-L21D## for purchasing organization 1000, plant 1000.

This material-vendor combination is going to use vendor condition group 00##.

The standard order quantity of 1000 pieces must be specified.

The gross price is 21 UNI.

(C) SAP AG LO521 8-16

Create the info record accordingly.

1-12 Condition records: Create and save a condition record for your new condition type ZG##, purchasing organization 1000, vendor T-L21D## The rate should be 10% per piece. Starting with 1000 pieces, the discount will be 12%.

1-12-1 What validity period defaults? Why?

_________________________________________________________ _________________________________________________________

1-13 Test: Test your work by creating a purchase order.

Purchase Order Vendor: T-L21D##

Delivery Date: In one week

Ship to: Plant 1000

Material Quantity

T-REM## 1000

If the item Condition tab does not show condition type ZG## with the proper values, choose Analysis to analyze the problem.

Purchase order number: _____________________________

(C) SAP AG LO521 8-17

Customizing Solutions

Unit: Customizing

1-1

1-1-1 Condition Table: Definition of a combination of fields (key) that identifies a condition record. For example, one field that must be in the condition table for a vendor discount is the vendor.

1-1-2 Access Sequence: A search strategy (comparable to a search engine) that is used to find valid data for a particular condition type. An access sequence consists of one or more accesses, and determines the sequence in which the system searches for data.

1-1-3 Condition Type: Representation of some aspect of your daily pricing activities – for example, a price, discount, surcharge or rebate.

1-1-4 Calculation Schema: Defines a group of condition types in a particular sequence. It is the framework for the price determination process.

1-1-5 Condition Records: The way the R/3 System stores the actual condition information. For example, by entering a price or a discount in the system, you create a condition record.

1-1-6 Condition Group: Alphanumeric key for conditions that refer to a certain vendor and material. The key is entered in the purchasing info record. It is valid for a number of different materials supplied by a vendor to which a uniform discount or surcharge applies.

1-2 Configuration: First, you define the criteria by which your condition records are to be created in the R/3 System by creating a condition table. You then create the search mechanism by which the condition records are to be found in the system. For this, you create an access sequence. Then you create the condition type, which controls the creation of condition records. The access sequence has to be linked to the condition type. Now you have to establish the rules for price determination. You do this by creating a calculation schema, which has to be linked to a schema group. Schema groups can be created for vendors and for purchasing organizations. Master data: After your price determination procedure is set up, you create condition records for the new condition type and link the relevant master data to the relevant configuration data (for example, if you have a vendor schema group, it has to be linked to your vendor master record).

(C) SAP AG LO521 8-18

1-3 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Maintain Condition Table Choose Create Condition Table.

Choose Edit � Propose text to change the table description.

1-4 From the Create Condition Table (Pricing Purchasing) screen, in the Overview field, choose Condition �� Generate.

Choose Enter to accept the warning message.

Choose Yes to Generate Conditions.

Choose Local object.

1-5 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Access Sequences.

Choose New Entries. Enter ZS## and a description.

Select your access sequence ZS## and choose Accesses.

Choose New Entries and enter access number 10, table 7##

Choose Enter to accept the warning message.

Select Exclusive.

Select access 10 and choose Fields.

Save your work.

1-6 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Condition Types Choose Define Condition Type.

Valid to: 2

Scale basis: C

1-7 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Calculation Schema.


(C) SAP AG LO521 8-19

1-8 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Calculation Schema. Select schema Z##GCR and choose Control data.

Overtype condition type RGR0 with condition type ZG##

1-9 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Schema Group Choose Schema Groups: Vendor.

1-10 SAP menu ��Tools � AcceleratedSAP � Customizing � Edit Project. Choose SAP Reference IMG IMG� Materials Management � Purchasing � Conditions ��Define Price Determination Process � Define Schema Determination Choose Determine Calculation Schema for Standard Purchase Orders.

Leave Schema gp. POrg blank. Enter only your vendor schema group and your calculation schema Z##GCR.

1-11

1-11-1 Favorites � Purchasing � Vendor � Purchasing � Change (Current).


1-11-2 Favorites� Purchasing � Master Data � Info Record � Change. On the Purch. Organization Data 1 screen, enter Condition group 00##

Choose Conditions and enter the gross price.

1-12 Favorites � Purchasing � Master Data � Conditions � Other � Create.

1-12-1 The validity period starts today through to the last day of the current year. You specified this when you created condition type ZG##.

1-13 Favorites � Purchasing �Purchase Order � Create � Vendor/Supplying Plant Known.


� SAP AG 1999

Conclusion

Course Overview


Price Determination




Customizing


Conclusion


� SAP AG 1999


� Outline the various elements of the condition technique and define how they interact

� Maintain conditions at different levels

� Describe how the process of price determination works in the system

� Recognize the special condition types that can be used in price determination

� Define the subsequent settlement process

� Create condition types and calculation schemas, and customize the price determination process

Course Objectives


� SAP AG 1999

Recommended Follow-up Courses

� LO550 Cross-Functional Customizing in MM


� SAP AG 1999

Recommended Follow-up Activities

� Go through the exercises using IDES dataor your own data

� Read on-line documentation

� Read IMG documentation

� Read release notes

(C) SAP AG LO521 10-1

� SAP AG 1999

� Menu Paths

Contents:

Appendix

(C) SAP AG LO521 10-2

Frequently-used Menu Paths

Activity Menu Path Maintenance of Time-dependent Conditions: Info Record SAP menu�Logistics�Materials

Management�Purchasing�Master Data�Info Record�Create

Contract

SAP menu�Logistics�Materials Management�Purchasing�Outline Agreement�Contract�Create

Scheduling Agreement SAP menu�Logistics�Materials Management�Purchasing�Outline Agreement�Scheduling Agreement�Create�Vendor Known

General Conditions SAP menu�Logistics�Materials Management�Purchasing�Master Data�Conditions�Discounts/Surcharges�By Vendor

Other Conditions SAP menu�Logistics�Materials Management�Purchasing�Master Data�Conditions�Other�Create

Display Price Overview SAP menu�Logistics�Materials Management�Purchasing�Master Data�Conditions�Prices�General Overview

Vendor Price change SAP menu�Logistics�Materials Management�Purchasing�Master Data�Conditions�Vendor price changes�Involving Info Recors/Involving Contracts

Maintenance of Time-independent Conditions: Purchase Order SAP menu�Logistics�Materials

Management�Purchasing�Purchase Order�Create�Vendor/Supplying Plant Known

Automatic Document Adjustment

SAP menu�Logistics�Materials Management�Purchasing�Purchase Order�Follow-On Functions�Automatic Document Adjustment�Individual Documents/Create Worklist

Subsequent (End-of Period Rebate) Settlement: Rebate Arrangement SAP menu�Logistics�Materials

Management�Purchasing�Master Data�Subsequent Settlement � Vendor Rebate Arrangements �Rebate Arrangement�Create

(C) SAP AG LO521 10-3

Business Volume SAP menu�Logistics�Materials Management�Purchasing�Master Data�Subsequent Settlement � Vendor Rebate Arrangements �List Displays�Business Volume Data

Settlement Document SAP menu�Logistics�Materials Management�Purchasing�Master Data�Subsequent Settlement � Vendor Rebate Arrangements �Rebate Arrangement�Create Settlement Document�Via Report

Extension of Rebate SAP menu�Logistics�Materials Management�Purchasing�Master Data�Subseq. Settlement � Vendor Rebate Arrangements �Rebate Arrangement�Extend�Manually/Via Report

Basic Materials Management Functions: Material Master Record SAP menu�Logistics�Materials Management�Material

Master�Material�Create(General)�Immediately

Vendor Master Record SAP menu�Logistics�Materials Management� Purchasing�Master Data�Vendor� Purchasing/Central�Create/Change/Display

Goods Receipt SAP menu�Logistics�Materials Management�Inventory Management�Goods Movement�Goods Receipt�For Purchase Order�PO Number Known

Enter Invoice SAP menu�Logistics�Materials Management� Logistics Invoice Verification �Document Entry�Enter Invoice

Release Invoice SAP menu�Logistics�Materials Management� Logistics Invoice Verification �Further Processing�Release Invoices

Customizing: All menu paths begin with: SAP menu�Tools�AcceleratedSAP�Customizing�Edit Project Choose SAP Reference IMG IMG�Materials Management�Purchasing

Access Sequences Conditions�Define Price Determination Process�Define Access Sequences

Condition Types Conditions�Define Price Determination Process�Define Condition Types Choose Define Condition Type

Calculation Schemas Conditions�Define Price Determination Process�Define Calculation Schema

Schema Groups Conditions�Define Price Determination Process�Define Schema Group

(C) SAP AG LO521 10-4

Choose Schema Groups: Vendor

Schema Determination Conditions�Define Price Determination Process�Define Schema Determination Choose Determine Calculation Schema for Standard Purchase Orders

Condition Exclusion Conditions�Define Price Determination Process�Define Condition Exclusion ChooseCondition Exclusion Groups

Condition Tables

Conditions�Define Price Determination Process�Maintain Condition Table ChooseCreate/Change/Display Condition Table

Automatic Document Adjustment Control

Conditions � Automatic Document Adjustment � Control Document Adjustment � Control Purchasing Document Adjustment

Scope-of-List Parameters for Lists of Conditions

Conditions � Scope of List for Conditions � Define Scope-of-List Parameters

Condition Index Conditions � Condition Index