SCM521 Pricing in Purchasing
April 14, 2017 | Author: fnovoac5046 | Category: N/A
Short Description
Download SCM521 Pricing in Purchasing...
Description
SCM521 Pricing in Purchasing
Only Partner
Pricing in Purchasing
THE BEST-RUN BUSINESSES RUN SAP
Use
SAP AG 2002 SAP AG©2003 SAP AG
!
2003/Q2
!
Materialnummer: 50061152
Only
Internal
Use
SAP R/3 Enterprise
Partner
!
SAP
SAP
Internal
SCM521
© SAP AG
SCM521
0-1
Copyright
Copyright 2003 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.
SAP
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®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
!
ORACLE® is a registered trademark of ORACLE Corporation.
!
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
!
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
!
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.
!
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
!
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
© SAP AG
SCM521
Only
!
Partner
Use
SAP
Internal
Use
Partner
Only
Internal
SAP AG 2003
0-2
Course Prerequisites
# Essential: # SCM020Processes in Procurement # Recommended: # SCM520Purchasing Details and Optimization # SCM550Cross-Functional Customizing in Materials Management
Use
Only
SAP AG 2002
SAP
SAP
Partner
Internal
# Participants should be thoroughly familiar with the Purchasing area. Ideally, they should also have some knowledge of the Customizing functionality for this area.
Only
Internal
Use
Partner
© SAP AG
SCM521
0-3
Target Group
# Audience: !
Project team members responsible for pricing in purchasing.
# Duration: 2 days
SAP
SAP
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.
Only
Internal
!
Partner
Use
Use
Partner
Only
Internal
SAP AG 2002
© SAP AG
SCM521
0-4
Course Overview
Contents: ! Course Goals ! Course Objectives ! Course Content ! Main Business Scenario
Use
SAP AG 1999
SAP
SAP
Partner
Internal
Only
! Course Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
1-1
Course Goals
This course will prepare you to: ! Carry out price determination functions in
purchasing ! Configure the IMG settings for price determination
Use
Partner
Only
Internal
SAP
SAP
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
1-2
Course Objectives
At the conclusion of this course, you will be able to: ! Outline the various elements of the condition
technique and define how they interact ! Maintain conditions at different levels
Only
Internal
! Describe how the process of price determination
works in the system ! Recognize the special condition types that can be
used in price determination
Partner
! Define the subsequent settlement process ! Create condition types and calculation schemas,
Use
and customize the price determination process
SAP
SAP
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
1-3
Course Content
Course Overview
Unit 2
Elements of the Condition Technique
Unit 3
Price Determination
Unit 4 Unit 5
Unit 6
Special Condition Types and Special Functions *
Unit 7
Header and Group Conditions
Subsequent (End-ofPeriod Rebate) Settlement
Unit 8
Customizing
Maintaining Conditions
Unit 9
Conclusion
Appendices
Use
Partner
Unit 1
Internal
Only
Preface
Only
Internal
* 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.
Partner
Use
SAP
SAP
SAP AG 1999
© SAP AG
SCM521
1-4
Partner
Course Overview
Special Condition Types and Special Functions
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Internal
Only
Course Overview Diagram
Use
Maintaining Conditions
SAP
SAP
SAP AG 2001
Only
Internal
Use
Partner
© SAP AG
SCM521
1-5
Main Business Scenario
! A vendor’s price for a material is often made up of
Only
Use
Partner
Internal
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 system applies these conditions 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.
SAP
SAP
SAP AG 2001
Only
Internal
Use
Partner
© SAP AG
SCM521
1-6
Elements of the Condition Technique
Contents: ! Condition Types ! Condition Records and Tables ! Access Sequences ! Calculation Schemas
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
2-1
Elements of the Condition Technique: Objectives
At the conclusion of this unit, you will be able to: ! Describe the elements of the condition technique and their interaction ! Identify and properly apply time-dependent and time- independent conditions
Only
Use
SAP AG 2003
SAP
SAP
Partner
Internal
! Define important control parameters for condition types and calculation schemas
Only
Internal
Use
Partner
© SAP AG
SCM521
2-2
Elements of the Condition Technique: Scenario
! Your purchasing department needs a method for storing and determining the purchase prices for materials.
The condition technique refers to the method by which the system determines prices from information stored in condition records. In Purchasing, the various elements used in the condition technique are set up and controlled in Customizing. During purchase order processing, the system uses the condition technique to determine a variety of important pricing information. For example, the system automatically determines which gross price should apply and which discounts and surcharges are relevant given the conditions that apply.
Internal
Use
"
© SAP AG
SCM521
Only
The term pricing is used broadly to describe the calculation of prices (for external use by vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, we order a certain quantity of a particular product on a certain day from a certain vendor. The variable factors here - the vendor, the product, the order quantity, and the date - determine the final price we pay. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.
Partner
"
SAP
SAP
Use
Partner
Only
Internal
SAP AG 2002
2-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Elements of the Condition Technique: Overview
Only
Internal
Use
Partner
© SAP AG
SCM521
2-4
Conditions
Conditions Prices
Discounts and surcharges
Contract
Percentage, quantity-dependent, or absolute discounts/surcharges
Scheduling agreement Quotation
SAP
Partner
End-of-period rebates
SAP AG 2002
SAP
Conditions are stipulations agreed with vendors regarding prices, discounts and surcharges. The system determines the price in purchasing on the basis of these pricing elements.
"
Conditions are stored in the system as condition records. Condition records allow you to store and retrieve pricing data in the system. You create condition records for all the pricing elements - the prices, discounts, and surcharges - that the system takes into account during automatic pricing. You can define as many condition records as you want for the different pricing elements.
"
During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the purchasing document.
"
A distinction is made between conditions that are valid for a certain period (time-dependent conditions) and conditions for which no validity period can be specified (time-independent conditions). In the latter case, the validity period corresponds to that of the purchasing document. Whether time-dependent or time-independent conditions are created is determined via the document type.
"
You can also store conditions that do not take effect immediately, but only at the end of a certain period. Settlement with regard to such conditions takes place subsequent to the settlement of vendor invoices relating to individual purchase orders.
© SAP AG
SCM521
2-5
Only
"
Partner
Use
Cash discounts
Use
Internal
Freight charges
Internal
Only
Info record
Time-Dependent Conditions
General conditions Vendor FF FF DM DM Condition group $$ Material type Incoterms Invoicing party Other
pc
Outl. purchase agreement
% Conditions
$
Price 1 01.01.
SAP
From 100 pc 3%
Purch. organization
5%
Lower limit 1%
Ref. purch. organization
SAP AG 2002
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 timedependent conditions for both scheduling agreements and quotations.
"
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 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.
"
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.
"
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).
"
Valid time-dependent conditions from info records or outline purchase agreements are adopted as default values in purchase orders.
"
Conditions in purchase orders are always time-independent. No validity periods and scales can be defined for these conditions.
© SAP AG
SCM521
Only
"
Partner
Use
12.31.
Upper limit
SAP
Internal
07.01.
5%
Use
Partner
Plant
Surcharge
Price 2
Internal
Only
Info record
2-6
Condition Types
Control
Freight, absolute
Condition class: Discount/surcharge Calculation type: Fixed amount Condition cat.: Delivery costs
SKTO
Cash discount
Condition class: Discount/surcharge Calculation type: Percentage Condition cat.: Cash discount
Use
A condition type is a representation in the system of some aspect of your daily pricing activities. You can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions. There are condition types for the gross price, various discounts and surcharges, freight charges, or fixed costs in the standard version of the SAP R/3 System.
"
You can change and maintain condition types provided in the standard version of the SAP R/3 System or you can create new condition types to suit the needs of your own organization. You create and maintain condition types in Customizing.
"
Condition types are differentiated broadly using the condition class and more finely using the condition category. The condition category also has various control functions. For example, condition category U (for precious metal discounts and surcharges) causes a new price determination process to be carried out at the time of goods receipt, and condition category E (for cash discount) causes the discount to be derived from the terms of payment.
"
The calculation type (or rule) determines how the system calculates prices, discounts, or surcharges for a condition. For example: $ the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight. $ a discount or surcharge can be a percentage of the gross price, a fixed amount or a quantitydependent 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.
© SAP AG
SCM521
2-7
Only
"
Partner
Internal
SAP AG 2003
SAP
SAP
FRB1
Use
Gross price
Internal
PB00
Condition class: Prices Calculation type: Quantity-dependent Condition cat.: Base price Access sequence: Gross price
Only
Description
Partner
Key
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
Pur. org.
...
Cond. rec. no.
PB00
A
1
1000
...
4321
Table KONP (item conditions)
Partner SAP
Material
Cond. rec. no. Cond. ty.
...
Cond. amount
...
1234
PB00
...
10.00
...
4321
PB00
...
11.00
...
SAP AG 2003
"
A condition table consists of one or more condition keys and a data part. The data part contains a number that references the record in another table.
"
The standard SAP R/3 System includes predefined condition tables. You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.
"
Examples of condition tables with the following key fields in the Standard SAP R/3 System.
Only
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a material or a special discount for a vendor, you create an individual condition record.
$ Table A018 - Vendor, material, purchasing organization, info record category $ Table A017 - Vendor, material, purchasing organization, plant, info record category $ Table A066 - Vendor, material, purchasing organization, info record category, order unit $ Table A068 - Purchasing document, item, plant (for outline agreements) "
Condition records are stored in the following transparent tables $ KONP (time-dependent conditions) $ KONH (header conditions) $ KONM (quantity scales) $ KONW (value scales)
© SAP AG
SCM521
Partner
"
SAP
Use
Vendor
Use
Internal
Cond. ty.
Internal
Only
Condition table A018 (info record without plant)
2-8
Access Sequence
Cond. ty.
Control
PB00
Access sequence 0002
Condition table
0002
10
A017 (Info record w. plant)
20
A018 (Info rec. w/o plant)
30
...
"
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 case of a gross price, 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.
"
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.
"
The order of the accesses is determined by the order of the condition tables in the access sequence.
"
The Exclusive indicator controls whether the system stops searching for a record after the first successful access for a condition type within an access sequence. In other words, 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 (or requirement) 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.
"
You cannot assign an access sequence to a header condition.
© SAP AG
SCM521
2-9
Only
An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record.
Partner
"
Use
SAP
SAP AG 2002
SAP
Internal
Exclusive
Use
Partner
Only
No.
Internal
Access sequence
Partner
Counter Cond. ty.
Description
1
1
PB00
Gross price
10
1
RB00
Absolute discount
...
...
...
10
9
ZA01
...
...
...
20
0
...
...
...
31
1
FRA1
...
...
...
35
1
SKTO
40
0
Fr.
Manu.
...
X
1
X
Freight %
20
X
Cash discount
20
% Surcharge on gross
Stat
Net value incl. discount
X
X
Use
Effective price
SAP AG 2002
A calculation schema (or pricing procedure) groups together all of the condition types that play a part in calculating the price. It sets out the order in which the condition types are taken into account in the calculation. In addition, the calculation schema specifies the following: $ Which subtotals are arrived at $ To what extent the price determination process can be carried out manually $ The basis upon which the system calculates percentage discounts and surcharges $ Order in which the condition types are taken into account in the calculation of the net or effective price $ Which requirements must be satisfied in order for a certain condition type to be taken into account
"
In addition, the Fro(m) reference step for percentage conditions is defined in the calculation schema. The Fro(m) reference step can be combined with a To reference step.
"
You can define a variety of calculation schemas (for individual purchasing organizations and/or vendors, for example). In the standard system, calculation schema RM0000 is defined for determining the purchase price in purchasing documents.
"
There are three kinds of price in Purchasing: $ Gross price: Price without taking any possible discounts and surcharges into account. $ Net price: Gross Price taking any applicable discounts and surcharges into account
"
Effective price: Net price after deduction of cash discount, with allowance for any miscellaneous provisions, delivery costs, and non-deductible taxes.
© SAP AG
SCM521
2-10
Only
Internal
$ Condition types for which subtotals are calculated
Partner
Use
"
SAP
SAP
Step
Internal
Only
Calculation Schema
Cnt. C.ty.
Description
C.ty.
1 2 3 4
Abs. discount Discount/qty. % disc. on net % disc. /gross
PB00 Gross price 100.00 RA00 % disc. on net 2% RB00 Abs. discount 10.00 Net value 88.00
RB00 RC00 RA00 RA01
Calculation schema Step 10 11 12 13 . . .
Partner SAP
Step 10 10 10 10 . . .
Cnt. C.ty. 0 0 0 0
RB00 RC00 RA00 RA01
Description
Amount
Conditions for item 10
Description
C.ty.
Abs. discount Discount/qty. % disc. on net % disc./gross .
100.00 PB00 Gross price RB00 Abs. discount 10.00 2% RA00 % disc. on net 88.20 Net value
Description
Pur. order
Pur. order
Amount
SAP AG 1999
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.
Partner
"
SAP
Use
Conditions for item 10
Use Only
Internal
Calculation schema
Internal
Only
Sequence of Conditions
© SAP AG
SCM521
2-11
Elements of the Condition Technique: Summary
You are now able to: ! Describe the elements of the condition technique and their interaction ! Identify and properly apply time-dependent and time-independent conditions
Only
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! Define important control parameters for condition types and calculation schemas
Only
Internal
Use
Partner
© SAP AG
SCM521
2-12
Exercise Data Sheet Key to Icons in Exercises and Solutions Exercises Solutions Objectives Business Scenario
Partner SAP
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),
SAP
1200 (Dresden) Storage location
0001 (Materiallager)
Purchasing group
Z21 (SCM521 Buyer)
Materials
T-REK## T-REM##
Material group
ZT21 (SCM521 Material Group)
Vendors
T-K521A## T-K521C## T-K521E##
G/L account
400000
Cost center
T-L20
SCM521
T-REL## T-REN##
T-K521B## T-K521D##
Only
© SAP AG
Partner
Use
Warning or Caution
Use
Internal
Internal
Only
Hints and Tips
2-13
Exercises Unit: Elements of the Condition Technique
At the conclusion of this exercise, you will be able to:
Only
• Define important control parameters for condition types and calculation schemas
Use
Create a standard information record using the following data: Vendor:
T-K521A##
Material:
T-REK##
Purchasing organization:
IDES Deutschland (1000)
Planned delivery time:
10 days
Purchasing group:
Z21 (SCM521)
Standard quantity:
100
Gross price (PB00):
9.90 EUR (from 1 pc)
Partner Only
Internal
SAP
1-1
Use
SAP
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.
Internal
• Examine differences between, and maintenance of, timedependent and time-independent conditions
Partner
• Describe the elements of the condition technique and their interaction
9.50 EUR (from 100 pc) 9.00 EUR (from 500 pc) Discount % on net (RA00): 1% (from 1 pc) 2% (from 500 pc) Freight (value FRB1):
50.00 EUR
The conditions are valid until the end of next year. Information Record Number: ___________________
© SAP AG
SCM521
2-14
1-2
Vendor T-K521A## also grants Purchase organization 1000 a scaled discount on all materials for a limited period of time: • 3% from a value of 1000 EUR upwards • 4% from a value of 5000 EUR upwards • 5% from a value of 9000 EUR upwards The discount is valid for a period of four weeks, starting today.
From 0.00 EUR: 0% From 1000.00 EUR: 3% 1-3
Internal
Create a purchase order using the following data: T-K521A##
Purchasing group:
Z21
Company code:
1000
Material:
T-REK## /qty 120 pc/ plant 1000.
Material:
T-REK##/qty 560 pc/plant 1100.
Delivery date:
In 2 weeks (applies to both items)
SAP
Purchasing organization: 1000
Use
Partner
Vendor:
SAP
Only
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:
Use Internal
1-3-1 Must you enter an order price? Yes or No 1-3-2 Check the conditions for both items and determine the amounts/percentages for each. Record the findings below:
Only
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)
© SAP AG
SCM521
Partner
Do not save the purchase order until you have answered steps 1-3-1 to 1-3-3
2-15
1-3-3 Trace the origin of the condition value for each item by displaying the master data for the condition records. Record the findings below: Item 10
Item 20
Gross price Discount % on net Vendor discount Freight surcharge Purchase order number: ___________________ 1-4
Partner
Condition type
Access Condition sequence class
Calculation Condition type category
Plus/ minus
PB00
Use
RA00 RB00
SAP
RC00
SAP
RL01 FRB1 SKTO Create an additional information record using the following data: Vendor:
T-K521A##
Material:
T-REL##
Purchasing organization:
IDES Deutschland (1000)
Planned delivery time:
10 days
Purchasing group:
Z21 (SCM521)
Standard quantity:
100
Only
Internal
1-5
Partner
Use
Display the Customizing settings and determine the specified control parameters for the following condition types. Record the findings below:
For this material, you have negotiated the following conditions with your vendor, which are valid indefinitely: Gross price:
120.00 EUR
Discount % on gross:
1%
Discount/quantity:
2.00 EUR (from 1 carton) 5.00 EUR (from 10 cartons) 10.00 EUR (from 50 cartons)
© SAP AG
Internal
Only
Cash discount
SCM521
2-16
Be sure to scale the discount/quantity by carton, not pc. Discount (value):
20.00 EUR (from 1 pc) 120.00 EUR (from 500 pc)
Discount % on net:
1.5%
1-5-1 What condition types did you use for the above conditions? • Gross price
_________________________________
• Discount % on gross _________________________________
Only
• Discount % on net _________________________________ • Information Record number: ___________________ *1-6
Condition type
Step
Counter
RB00
SAP
RC00
SAP
RA00 RA01
Use
HB01
Partner
RL01 RGR0 *1-7
Create a purchase order using the following data: Vendor:
T-K521A##
Purchasing organization:
IDES Deutschland (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
In 8 weeks
Only
Internal
Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types. Record the findings below:
Use
Partner
• Discount (value) _________________________________
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: ______________________________________________________ © SAP AG
Internal
• Discount/quantity _________________________________
SCM521
2-17
Solutions Unit: Elements of the Condition Technique
1-1
Create a standard information record. Logistics → Materials Management → Purchasing → Master Data → Info Record → Create.
Only Partner
Vendor:
T-K521A##
Material:
T-REK##
Purchase Organization:
1000
Plant:
Leave blank
Internal
Enter the following data:
Use
Choose: Info category Standard Enter 1-1-1 Select the Purch. Org data 1 radio button.
SAP Use
10
Purchase group:
Z21
Standard qty:
100
Net price:
9.90 EUR
Partner
Plnd dely time:
SAP
Enter the following data:
1-1-2 Select the Conditions radio button. Condition
Condition type
Amount
Gross price
PB00
9.90 EUR note: this will have defaulted from the purchase org screen.
Discount % on net
RA00
1%
Freight (value)
FRB1
50.00 EUR
Only
Internal
Enter the following data:
Change the Valid on date to: The current date (note: this will have defaulted today’s date) Change the Valid to date to: One year from today’s date 1-1-3 Select the Gross price line (PB00) line with the mouse by clicking once the gray box to the left of PB00.
© SAP AG
SCM521
2-18
1-1-4 Select the Scales icon Enter the following data: Scale quantity:
Amount:
Blank
9.90 EUR (note this will have defaulted)
100
9.50 EUR
500
9.00 EUR
Green arrow back to the main Conditions screen 1-1-5 Select the Discount% on net (RA00) line with the mouse by clicking once the gray box to the left of RA00.
Only
Amount:
Blank
1 % (note this will have defaulted)
500
2%
SAVE 1-2
Vendor T-K521A## also grants Purchase organization 1000 a scaled discount on all materials for a limited period of time:
SAP
SAP
Logistics → Materials Management → Purchasing → Master Data Conditions → Discounts/Surcharges → By Vendor
1000
Vendor:
T-K521A##
Scope of list:
0001 (note this will default)
Partner
Use
Enter the following data: Purchasing organization:
Execute
1-2-2 Select the vendor line item with the mouse by clicking once the gray box to the left and choose Scales icon. Enter the following data:
© SAP AG
Amount:
Blank
Blank
1000
3%
5000
4%
9000
5%
SCM521
2-19
Only
Internal
1-2-1 Select the Purchasing organization by clicking once on the line and choosing the Create icon.
Scale quantity:
Use
Partner
Scale quantity:
Internal
Enter the following data:
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 EUR: 0% From 1000.00 EUR: 3% Change the Valid on date to: The current date (note: this will have defaulted today’s date) Change the Valid to date to: Four weeks from today’s date. SAVE 1-3
Create a purchase order using the following data:
Vendor:
T-K521A##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Use
Only Partner
Enter the following date in the Header area of the purchase order:
SAP Use
PO quantity
Deliv. Date
Plant
T-REK##
120
2 weeks from today
1000
T-REK##
560
2 weeks from today
1100
Partner
Material
SAP
Enter the following data in the Item overview area of the purchase order:
1-3-1 No, the order price is adopted from the cross-plant info record. 1-3-2 Check the conditions for both items and determine the amounts/percentages for each. Verify the findings below: 1-3-2-1
Select the appropriate line item by using the mouse and clicking once in the gray box to the left of the line.
1-3-2-2
Open the Item overview screen area, if not already open, by selecting the Item overview icon within the purchase order.
SCM521
2-20
Only
Internal
Do not save the purchase order until you have answered steps 1-3-1 to 1-3-3
© SAP AG
Internal
Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known
1-3-2-3
Select the Conditions tab in the Item details screen area. Item 10
Item 20
Gross price (per 1 pc)
9.50 EUR
9.00 EUR
Discount % on net
1%
2%
Vendor discount
3%
4%
Net price (per 1 pc)
9.12 EUR
8.46 EUR
Freight surcharge
50.00 EUR
50.00 EUR
Cash discount
3%
3% 8.30 EUR
Internal
Only
Actual price (per 1 pc) 9.26 EUR
Select the appropriate line item by using the mouse and clicking once in the gray box to the left of the line.
SAP
1-3-3-2
Open the Item overview screen area, if not already open, by selecting the Item overview icon within the purchase order.
1-3-3-3
Select the Conditions tab in the Item details screen area.
1-3-3-4
Select the Conditions rec. radio button Gross price
Information record Information record
Discount % on net
Information record Information record
Vendor discount
Purchase org. / Purchase org. / Vendor conditions Vendor conditions
Freight surcharge
Information record Information record
Cash discount
Information record Information record
SAVE Purchase order number: ___________________ 1-4
Display the Customizing settings and determine the specified control parameters for the following condition types. Verify the findings below: 1-4-1 Tools → Customizing → IMG → Edit Project 1-4-2 Choose: SAP Reference IMG radio button 1-4-3 Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types 1-4-4 Choose: Define Condition Type. Enter
© SAP AG
SCM521
2-21
Only
Internal
Item 20
Partner
Item 10
SAP
1-3-3-1
Use
Step 1-3-3 can be done using the same steps as 1-3-2. Skip to step 1-3-3-4 if still in the Conditions tab.
Use
Partner
1-3-3 Trace the origin of the condition value for each item by displaying the master data for the condition records. Verify the findings below:
Condition type
Access Condition sequence class
Calculation Condition type 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)
SAP
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
Create an additional information record using the following data:
Partner
Logistics → Materials Management → Purchasing → Master Data → Info Record → Create
Internal
Use
Condition class:
SAP
1-5
Verify what each control data 1 code means by using the F4 matchcodes:
Use
Partner
1-4-5-1
Enter the following data: T-K521A##
Material:
T-REL##
Purchase Organization:
1000
Plant:
Leave blank
Only
Vendor:
Choose: Info category Standard Enter
© SAP AG
SCM521
Internal
Only
1-4-5 Verify the details of each of the condition types by selecting the condition. Select the Details icon.
2-22
1-5-1 Select the Purch. Org data 1 radio button. Enter the following data: Plnd dely time:
10
Purchase group:
Z21
Standard qty:
100
Net price:
120.00 EUR
1-5-2 Select the Conditions radio button. Amount
Only
Gross price
PB00
120.00 EUR note: this will have defaulted from the purchase org screen.
Discount % on Gross
RA01
1%
Discount/quantity
RC00
2.00 EUR per Carton
Discount (value)
RB00
20.00 EUR per Carton
Discount % on net
RA00
1.5%
Use
Condition type
SAP
SAP
Be sure to scale the discount/quantity by carton, not pc. Change the Valid on date to: The current date (note: this will have defaulted today’s date)
Use
1-5-3 Select the Discount/quantity (RC00) line with the mouse by clicking once the gray box to the left of RC00.
Internal
1-5-4 Select the Scales icon Enter the following data: Blank
2.00 EUR (note this will have defaulted)
10 Cartons
5.00 EUR
50 Cartons
10.00 EUR
Only
Amount:
Green arrow back to the main Conditions screen
© SAP AG
SCM521
Partner
Change the Valid to date to: Indefinitely
Scale quantity:
Internal
Condition
Partner
Enter the following data:
2-23
1-5-5 Select the Discount Value (RB00) line with the mouse by clicking once the gray box to the left of RB00. Enter the following data: Scale quantity:
Amount:
Blank
20.00 EUR (note this will have defaulted)
500 pieces
120.00 EUR
1-5-6 What condition types did you use for the above conditions? • Gross price
_________________________________
Only
• Discount (value) _________________________________ • Discount % on net _________________________________ • Information Record number: ___________________ *1-6
Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types. Verify the findings below: 1-6-1 Tools → Customizing → IMG → Edit Project
SAP
SAP
1-6-2 Choose: SAP Reference IMG radio button 1-6-3 Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema
Use
Partner
1-6-4 Verify the details of RM0000 by selecting the schema.
© SAP AG
Counter
RB00
10
1
RC00
10
2
RA00
10
3
RA01
10
4
HB01
10
10
RL01
10
11
RGR0
10
13
SCM521
Only
Internal
1-6-5 Choose the Control data folder by double clicking. Condition type Step
Use
SAVE
Internal
• Discount/quantity _________________________________
Partner
• Discount % on gross _________________________________
2-24
*1-7
Create a purchase order using the following data: Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known Enter the following date in the Header area of the purchase order: Vendor:
T-K521A##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Only
Material
PO quantity
Deliv. Date
Plant
T-REL##
500 pc
8 weeks from today
1000
Partner
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.
Use
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.
Internal
Enter the following data in the Item overview area of the purchase order:
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
2-25
Price Determination
Contents: ! Price Determination ! Schema Determination and Schema Groups ! Access Sequences for Gross Price
Internal
Only
! Validity Periods for Pricing ! Conditions Adopted from Last Purchase Order ! Scales
Use
SAP AG 1999
SAP
SAP
Partner
! Condition type PB00 versus PBXX
Only
Internal
Use
Partner
© SAP AG
SCM521
3-1
Price Determination: Unit Objectives
At the conclusion of this unit, you will be able to: ! Describe how the R/3 System finds the appropriate calculation schema
Only
! Create condition types and calculation schemas by copying existing data
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! Explain the price determination process, taking into account different condition tables, validity periods and scales
Only
Internal
Use
Partner
© SAP AG
SCM521
3-2
Price Determination: Business Scenario
! Your purchasing policy dictates that prices should automatically default on 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.
$ In the case of purchase orders, the system searches for conditions in info records and contracts (for contract release orders), and for general conditions. $ In the case of scheduling agreements with time-independent conditions, the system searches for conditions in info records and for general conditions. "
If no conditions are found, but the last PO is noted in the info record, the system can adopt the conditions from this PO. You can specify how the system treats the conditions from the last PO in Customizing for Purchasing (default values for buyers).
© SAP AG
SCM521
Only
Internal
When you create a purchase order or scheduling agreement with time-independent conditions, the system searches for valid conditions and inserts these conditions into the new document (this is the process of price determination).
Partner
Use
"
SAP
SAP
Use
Partner
Only
Internal
SAP AG 2002
3-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Price Determination: Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
3-4
Price Determination Process: Overview
Calculation schema
Purch. order
Step Cond. type . . . ...
Pur. org. Vendor
1000 A
For plant Material
1000 1
1 . . .
PB00
Condition type: PB00
10 pc
Access sequence: 0002
Partner SAP
SAP AG 2002
"
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 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
SCM521
3-5
Only
$ The search for condition records is carried out in the order specified in the access sequence.
Partner
Use
Condition table Plant info record Material 1 50.00 From 500 pc 48.00
SAP
Internal
Condition table Contract item No record exists
Use
Condition tables: 1. Contract item (excl.) 2. Plant info record (excl.) 3. Info record (excl.) . . .
50.00
Internal
Only
Access sequence: 0002
Schema Determination Customizing Schema gr. purch. org.
Schema gr. vendor
0001
Partner SAP
Vendor
A
XM0000 01
YM0000
02
ZM0000
Purch. org.
Schema gr.
2000
0001
3000
0001
Vendor A Schema group 02 SAP AG 2002
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.
"
You have the following options with regard to schema assignment for standard POs:
Partner
"
SAP
Use
RM0000
Pur. org. 1000
Use
$ You can assign a generally valid calculation schema (in the standard R/3 System, RM0000) $ You can define the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations. $ You can define the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations and 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
SCM521
3-6
Only
Internal
Purch. order
Internal
Only
0001
Calculation schema
Calculation Schema for Condition Type PB00
Calculation schema RM0000 Step Count. Cond. type
Condition class Calculation type Calculation schema: RM0002 . . . Calculation schema RM0002
Pc. Pc.
Info record Valid
Partner SAP
Condition type PB00
from 01.01. to 12.31.
Cond. type PB00 GAU1 RB00
Cond. value . . .
% % Conditions Conditions
$$
Step 1 5 10 . . .
Count. 1 1 1
Cond. type PB00 GAU1 RB00
Propose condition supplements
SAP AG 2002
SAP
"
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 conditions because no separate condition record has to be found for them. 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.
SCM521
Only
© SAP AG
Partner
Use
PB00
Use
Internal
1
Internal
Only
1 . . .
3-7
Access Sequence for Gross Price
Calculation schema Step
Condition type
1
PB00
Purch. order Pur. org. 1000 Vendor A
Condition type PB00
For plant 1000 Material 1
Access sequence: 0002
Access sequence 0002
Only
68 16 67
Contract item, plant-dependent Contract item Plant info record per order unit
Partner
25 35 45 ...
17 18 28
Material info record, plant-specific Material info record Info record for non-stock material
Item without material
Condition table No. of condition record
SAP AG 2002
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:
Internal
"
$ Table A068 – for gross prices in plant-specific outline agreement items
Partner
Use
Plant info record exists, variable order unit active Plant info record exists
SAP
SAP
10 15 20
Use
Tab.
Internal
Requirement
No.
$ Table A016 – for gross prices in the items of centrally agreed contracts
Only
$ 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
SCM521
3-8
Conditions For Several Purchasing Organizations Customizing enterprise structure Purch. Org. D
Only
Release order Purch. org. D Mat. 2 10,00 for plant 1000
SAP AG 2002
"
In Customizing, a link must be set up between the relevant purchasing organizations. Furthermore, you must stipulate whether:
Use
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.
$ It is permissible to issue release orders against contracts of the reference purchasing organization
Only
$ 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.
© SAP AG
SCM521
Partner
"
SAP
SAP
Plant contract Purch. org. EUR Mat. 2 10,00 for plant 1000
Release order Purch. org. D Mat. 1 10,00 for plant 2000
Use
Release order Purch. org. D Mat. 1 10,00 for plant 1000
Plant 2000:
Internal
Central contract Purch. org. EUR 10,00 Mat. 1
Internal
Purch. Org. D
Plant 1000:
Partner
Purch. org. EUR - Contracts Purch. Org. D - Conditions
Purch. Org. EUR
3-9
Validity Periods and Pricing Date
04.01. - 06.30.
10.20
07.01. - 09.30.
10.50
10.01. - 12.31.
10.80
Partner
Pricing date category Purchase order 1
Purchase order 2
Purchase order 3
Current date: 04.01. PO date: 03.26. Delivery date: 07.15.
Current date: 04.01. PO date: 03.26. Delivery date: 07.15.
Current date: 04.01 PO date: 03.26. Delivery date: 07.15.
Price:
Price:
Price:
Pricing date = Current date
10.20
10.00
Pricing date = PO date
10.50
Pricing date = Delivery date
SAP AG 2002
In the automatic price determination process, the price can be calculated as at the document date of the PO, or as at another date (such as the current day’s date, the delivery date, or the goods receipt date). You can specify the date to which the price that is determined relates at the following points: $ In the vendor master record, in the Pricing date control field, if you wish to use the same price determination date for all a vendor’s materials. $ In the purchasing info record, in the Pricing date category field, if you wish to use a different pricing date for a certain material supplied by a particular vendor. The value in the purchasing info record takes precedence over the value in the vendor master record.
"
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.
"
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).
© SAP AG
SCM521
3-10
Only
$ In the purchase order, in the Pricing date category field.
Partner
Use
"
SAP
SAP
10.00
Use
Internal
01.01. - 03.31.
Internal
Only
Gross price
Scales
Price From
Surcharge 1 pc 500 pc 1000 pc
100.00 EUR 99.00 EUR 96.00 EUR
To
500.00 EUR 1000.00 EUR
50.00 EUR 30.00 EUR
Customizing condition type
Only Partner SAP
Scale type Scale basis
B B
(= To scale) (= Value scale)
Condition record (KONP) Scale lines (KONM/KONW) SAP AG 2002
SAP
When you create a condition record for condition, you can define a pricing scale. For example, a scale based on quantity can determine that the more we purchase from a vendor of a particular material, the lower the price. You can also create condition records with graduated scales.
"
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.
"
The scale type and the scale basis for a scale are defined in customizing for the condition type. 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).
"
You can also maintain condition records with graduated scales. Using a graduated scale allows you to price an item for each level of a pricing scale. By comparison, when you use normal scales, the system determines one price depending, for example, on the item quantity; the same price then applies to each unit of the item. With graduated scales, the result is that multiples prices can appear in the pricing screen for an individual item.
"
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.
"
Scaled conditions are stored in the tables KONM and KONW.
© SAP AG
SCM521
3-11
Only
"
Partner
Use
(= From scale) (= Qty. scale)
Use
Internal
A C
Internal
Scale type Scale basis
Info Record and Order Price History
Quotation in response to RFQ Info record
10.00
Condition:
Partner SAP
Purch. order 123
Order Orderprice pricehistory history PO no. 123: PO no. 123:10.50 10.50
Item Mat. Price 10.50
Purchase order
Purchase order
Pricing date: 06.01.
Pricing date: 07.01.
Item Mat. Price
Item Mat. Price
10.00
10.50
SAP AG 2002
SAP
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 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 can be 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”).
© SAP AG
SCM521
3-12
Only
"
Partner
Use
Valid: 01.01. - 06.30.
Use
Internal
10.00
Internal
Only
Item Mat. Price
Conditions Adopted from Last Purchase Order
Last Purchase order 123 Item Mat. Price 10
1
New Purchase order
10.00
Item Mat. Price
SAP
Partner
User Parameter EVO
SAP AG 2003
Until Release 4.5A, during the creation of a purchase order, the system copied the conditions from the last purchase order if the price determination process failed to establish a valid price. The system did not take the manually entered gross price into account in price determination.
"
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: $ 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).
- 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.
© SAP AG
SCM521
3-13
Only
$ If you enter a price in the current purchase order manually, the conditions are not copied from the last purchase order.
Partner
"
SAP
Use
?
Use
Internal
1
Internal
Only
10
Condition Types PB00 and PBXX
Purchase order Item Mat. Price 10
1
95.00
Info rec. conditions PB00
100.00
RA01
5%
5% Requirement 6
Purchase order Item Mat. Price
Partner SAP
RA01
6
20
2
?
Condition exclusion ‘X‘ Conditions for item 20 PB00 PBXX
50.00
Please enter net price
CHECK KOMP-KZNEP NE ‘X‘.
Condition type PB00 ... Exclusion =X ...
SAP AG 2002
"
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.
"
These 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. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).
© SAP AG
SCM521
3-14
Only
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.
Partner
"
SAP
Use
100.00
Reqt.
Use
Internal
PB00
Step Cnt. C. type 1 1 PB00 1 2 PBXX . . .
Internal
Only
Conditions for item 10
Calculation schema
Price Determination: Unit Summary
You are now able to: ! Describe how the R/3 System finds the appropriate calculation schema
! Create condition types and calculation schemas by copying existing data
Use
SAP AG 2001
SAP
SAP
Partner
Internal
Only
! Explain the price determination process, taking into account different condition tables, validity periods and scales
Only
Internal
Use
Partner
© SAP AG
SCM521
3-15
Exercises Unit: Price Determination Topic: Customizing Settings At the conclusion of this exercise, you will be able to: •
1-1
Create a new condition type Z##A by copying the standard condition type PB00. Name your condition type ZP521 Gross price ##. Save your condition type.
1-2
Read the IMG documentation for the node Define Calculation Schema.
Use
If the IMG help is not loaded on the server access help.sap.com though the internet for document assistance. 1-3
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. Save your calculation schema 1-4
Create a second new calculation schema YM00## with the title Supplementary Conditions ZP521-## by copying the standard calculation schema RM0002 with all dependent entries. Replace the standard condition type PB00 with your condition type Z##A Acknowledge the repeated warnings by choosing Enter each time. Save your calculation schema
© SAP AG
SCM521
3-16
Only
Create a new calculation schema ZM00## with the title Document Schema ZP521-##, by copying the standard calculation schema RM0000 with all dependent entries. Replace the standard condition type PB00 with your condition type Z##A.
Partner
The IMG help files must be loaded in the server in order to complete step 1-2.
SAP
SAP
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.
Use
Partner
Only
• Create condition types and calculation schemas by copying existing data
Internal
Internal
Examine how the R/3 System finds the appropriate calculation schema
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 ZP521-## 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. 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.
Partner
1-8
Assign your schema group ## to vendor T-K521B## on the Purchasing data screen of the vendor master record for purchasing organization 1000. Save your assignment.
Internal
Only
1-7
Use
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
3-17
Exercises Unit: Price Determination Topic: Analyzing Price Determination At the conclusion of this exercise, you will be able to:
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. Create a purchase order using with the following data: Vendor:
T-K521B##
Purchasing organization:
IDES Deutschland (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
In 4 weeks
SAP
SAP
2-1
Use
Partner
Internal
Only
• Analyze the price determination process, taking into account different condition tables, validity periods and scales
Order 100 pc of material T-REL## for plant Hamburg (1000) at a price of 100 EUR.
Use
______________________________________________________ 2-1-2 Which condition type has been assigned to the manually entered price? ________________________________________________ 2-1-3 What calculation schema has been determined for the purchase order? ________________________________________________ Save your purchase order. Purchase order number: ___________________ 2-2
Change the info record for vendor T-K521B##, material T-REL##, purchasing organization IDES Deutschland (1000), which was generated automatically from the purchase order created in step 2-1. 2-2-1 Which condition type did the system suggest? ___________________ 2-2-2 You and your vendor have agreed to the following conditions: Gross price:
100 EUR
Discount (value): 10 EUR from 1 pc 50 EUR from 200 pc Enter the conditions.
© SAP AG
SCM521
3-18
Only
Internal
Partner
2-1-1 Why must the price be entered manually?
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-bechanged calculation schema. Save the changed information record.
•
1% up to a condition value of 1000 EUR
•
2% up to a condition value of 5000 EUR
•
3% up to a condition value of 999999 EUR Before entering the discount scale, you must change the scale type on the condition detail screen.
Create a purchase order with the following data: Vendor:
T-K521B##
Purchasing organization:
IDES Deutschland (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
In 2 weeks
SAP
SAP
*2-4
Use
Partner
You have also negotiated the following general discount with vendor T-K521B##, which applies to all materials and is valid for four weeks, starting today.
Internal
Only
2-3
Use
Partner
Order 100 pc of material T-REL## for plant Hamburg (1000). 2-4-1 Is an order price suggested? If so, what is it? ______________________________________________________
Internal
2-4-2 How is the default order price calculated? ______________________________________________________
Only
2-4-3 Determination the details of the price process. ______________________________________________________ Save the purchase order number Purchase order number: ______________________________ *2-5
You have agreed with vendor T-K521B## 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 determining if the system selected a suitable pricing date category. 2-5-1 Which pricing date category did the system use? ______________________________________________________
© SAP AG
SCM521
3-19
*2-6
Create a purchase order with the following data: Vendor:
T-K521B##
Purchasing organization:
IDES Deutschland (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
In 6 weeks
Order 200 pc of material T-REL## for plant Hamburg (1000). 2-6-1 Did the system propose an order price? _________________________ 2-6-2 How was the order price calculated? ______________________________________________________
Only
Internal
2-6-3 Why wasn’t the vendor discount taken into account?
Use
Partner
______________________________________________________
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
3-20
Solutions Unit: Price Determination Topic: Customizing Settings 1-1
Create a new condition type Z##A by copying the standard condition type PB00. Tools → Customizing → IMG → Edit Project
Choose: Define Condition Type SAVE your condition type 1-2
Read the IMG documentation for the node Define Calculation Schema. Tools → Customizing → IMG→ Edit Project Choose: SAP Reference IMG
Select IMG activity documentation on the left-hand side of the Define Calculation Schema node
Use
If the IMG help is not loaded on the server access help.sap.com though the internet for document assistance. 1-3
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. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Choose: Copy all. Replace the standard condition type PB00 with your condition type Z##A SAVE your calculation schema © SAP AG
SCM521
3-21
Only
Create a new calculation schema ZM00## with the title Document Schema ZP521-##, by copying the standard calculation schema RM0000 with all dependent entries.
Partner
The IMG help files must be loaded in the server in order to complete step 1-2.
SAP
Materials Management → Purchasing → Conditions → Define Price Determination Process
SAP
Partner
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types
Use
Internal
Internal
Only
Choose: SAP Reference IMG radio button
1-4
Create a second new calculation schema YM00## with the title Supplementary Conditions ZP521-## by copying the standard calculation schema RM0002 with all dependent entries Tools → Customizing → IMG → Edit Project Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Choose: Copy all Replace the standard condition type PB00 with your condition type Z##A
Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button 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. 1-6
Create a new vendor schema group ## with the title Schema group ZP521-##.
SAP
SAP
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.
Partner
Use
Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Group Choose→ Schema Groups: Vendor 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. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button 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. SAVE your assignment
© SAP AG
SCM521
3-22
Only
Internal
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.
Use
Partner
1-5
Internal
Only
SAVE your calculation schema
1-8
Assign your schema group ## to vendor T-K521B## on the Purchasing data screen of the vendor master record for purchasing organization 1000. Logistics → Materials Management → Purchasing → Master data → Vendor → Purchasing → Change (Current) Enter the following data: Vendor:
T-K521B##
Purch organization:
1000
Select: Purchasing data. Select: Enter Schema group, vendor
Internal
Only
Enter the following data: ##
Use
Partner
SAVE
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
3-23
Solutions Unit: Price Determination Topic: Analyzing Price Determination 2-1
Create a purchase order using the following data: Logistics-> Materials Management-> Purchasing → Purchase order → Create → Vendor/Supplying Plant Known
Partner
Vendor:
T-K521B##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Internal
Only
Enter the following date in the Header area of the purchase order:
Deliv. Date
Plant
Price
T-REL##
100
4 weeks from today
1000
100 EUR
SAP
PO quantity
SAP
Material
Use
Enter the following data in the Item overview area of the purchase order:
Use
Partner
Do not save the purchase order until you have answered steps 2-1-1 to 2-1-3
2-1-1 Why must the price be entered manually?
Internal
The price must be manually entered because the system is unable to determine a valid price.
Only
2-1-2 Which condition type has been assigned to the manually entered price? Select the Conditions tab in the Item details area of the purchase order. Condition type: PBXX 2-1-3 What calculation schema has been determined for the purchase order? Select the Conditions tab, and then choose the Analysis radio button. Calculation schema: ZM00## The R/3 System determined that calculation schema ZM00## was to be used based on the schema group ## assigned in vendor T-K521B##. SAVE Purchase order: ________________________
© SAP AG
SCM521
3-24
2-2
Change the info record for vendor T-K521B##, material T-REL##, purchasing organization IDES Deutschland (1000), which was generated automatically from the purchase order created in step 2-1. Logistics → Materials Management → Purchasing → Master data → Info record → Change Enter the following data: Vendor
T-K521B##
Material
T-REL##
Purchasing org.
1000
Only
Internal
Select: Enter 2-2-1 Which condition type did the system suggest? Select the Conditions radio button
Partner
Using the mouse double click in the dates within the validity period. Condition type: Z##A.
Use
Stay in the conditions area of the information record to complete step 2-2-2
SAP Use Internal
Enter the following data: Rate
PB00 (note this will have defaulted)
100
Only
CnTy
Enter condition RB00 and the rate of 10 EUR Select the RB00 line Select the Scales icon Enter the following data: Scale quantity
Rate
blank
10 EUR (this will have defaulted)
200
50 EUR
SAVE the changed information record.
© SAP AG
SCM521
Partner
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-bechanged calculation schema.
SAP
2-2-2 You and your vendor have agreed to the following conditions:
3-25
2-3
You have also negotiated the following general discount with vendor T-K521B##, which applies to all materials and is valid for four weeks, starting today. Logistics->Materials Management->Purchasing→ Master Data → Conditions → Discounts/Surcharges → By Vendor Enter the following data: Purchasing Organization
1000
Vendor
T-K521B##
Scope of list
0001 (this will default)
Only
Select the Change icon. Select the Details icon. SAVE *2-4
Create a purchase order with the following data: Logistics-> Materials Management-> Purchasing → Purchase order → Create → Vendor/Supplying Plant Known
SAP Use
T-K521B##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Partner
Vendor:
SAP
Enter the following date in the Header area of the purchase order:
PO quantity
Deliv. Date
Plant
T-REL##
200
6 weeks from today
1000
Only
Internal
Enter the following data in the Item overview area of the purchase order: Material
Do not save the purchase order until you have answered steps 2-4-1 to 2-4-3
2-4-1 Is an order price suggested? If so, what is it? An order price of 96.90 EUR was suggested.
© SAP AG
SCM521
Use
Change the scale type to B (To-scale).
Internal
Choose the date line by using the mouse and clicking once on the line
Partner
Choose the Execute icon.
3-26
2-4-2 How is the default order price calculated? Select the Conditions tab from within the item details area of the purchase order The suggested order price was calculated as follows: 100.00 EUR gross price less 0.10 EUR discount (10.00 EUR discount (value) is divided by the order quantity of 100 pc = 0.10), less 3.00 EUR vendor discount (3% vendor discount x 10000 = 300 EUR; 300.00 EUR vendor discount is divided by the order quantity of 100 pc = 3.00 EUR). 2-4-3 Determination the details of the price process
Only
Purchase order number ______________________________ *2-5
SAP
Logistics → Materials Management → Purchasing → Master data → Info record → Change
Vendor
T-K521B##
Material
T-REL##
Purchasing org.
1000
Partner
Use
Enter the following data:
Select: Enter Select the Purch. org. data 1 radio button.
Only
2-5-1 Which pricing date category did the system use? The pricing date category of 2 (Delivery date) was used. *2-6
Create a purchase order with the following data: Logistics-> Materials Management-> Purchasing → Purchase order → Create → Vendor/Supplying Plant Known Enter the following date in the Header area of the purchase order:
© SAP AG
Vendor:
T-K521B##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
SCM521
SAP
Internal
You have agreed with vendor T-K521B## 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 determining if the system selected a suitable pricing date category.
Use
Partner
SAVE
Internal
Select the Condition tab from within the Item details area of the purchase order the select the Analysis icon.
3-27
Enter the following data in the Item overview area of the purchase order: Material
PO quantity
Deliv. Date
Plant
T-REL##
200
6 weeks from today
1000
Do not save the purchase order until you have answered steps 2-6-1 to 2-6-4
An order price of 99.75 EUR was suggested. 2-6-2 How was the order price calculated?
The suggested order price was calculated as follows: 100.00 EUR gross price, less 0.25 EUR discount (50.00 EUR discount (value) is divided by the order quantity of 200 pc). 2-6-3 Why wasn’t the vendor discount taken into account?
SAP
SAVE
Use
Only
Internal
Partner
Purchase Order number ________________________
SAP
The vendor discount is not taken into account because it is not valid on the delivery date (it was only valid for four weeks).
Use
Partner
Select the Conditions tab from within the item details area of the purchase order
Internal
Only
2-6-1 Did the system propose an order price?
© SAP AG
SCM521
3-28
Header and Group Conditions
Contents: ! Header Conditions ! Group Conditions ! Item Conditions ! Condition Groups
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
4-1
Header and Group Condition: Unit Objectives
At the conclusion of this unit, you will be able to: ! Describe the differences among the header, group and item conditions and explain how each is created ! Define condition types as group conditions
Only
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! Identify and use important control parameters for condition types and calculation schemas
Only
Internal
Use
Partner
© SAP AG
SCM521
4-2
Header and Group Conditions: Business Scenario
Only
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! 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.
Only
Internal
Use
Partner
© SAP AG
SCM521
4-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Header and Group Conditions: Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
4-4
Header, Group, and Item Conditions
Purchase order Item Mat. Mat. gr. Qty.
Only
1
001
1
81.00
4
009
1
72.00
Mat. group discount:
5
009
10
63.00
5% from 100.00
Internal
10 Per purchase 20 order: 20.00 freight surcharge 40
Price
Special discount for material 5
SAP
The standard system includes condition types that you can only apply at the header level, the header conditions. Header conditions are entered in the header of a document and relate to all the items of that document.
"
Condition types that you can only use for items are called item conditions. Item conditions are conditions relating to a single item of a document.
"
The standard system also includes some condition types that can be used both at header and item level: Percent from gross (RA01) Absolute discount (RB00) Vendor discount (RL01). The Header condition/Item condition switch in Customizing for the condition type determines usage options.
"
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
SCM521
4-5
Only
"
Partner
Use
SAP AG 2002
SAP
Internal
Use
Partner
1% from 10 pc upwards
Header Conditions
Header condition
Header condition
ZB00 Abs. surcharge 10.00
HB00 Header surch. 180.00
ZB00 Group condition =
HB00 group condition =
ZB00 Abs. surcharge 10.00
180.00 Total
Purchase order
Only Partner SAP
Price
10
300.00 1 1 + surcharge 10.00
10
1 1 300.00 + surcharge 120.00
20
100.00 2 1 + surcharge 10.00
20
2 1 100.00 + surcharge 40.00
30
50.00 3 1 + surcharge 10.00
30
3 1 50.00 + surcharge 20.00
SAP AG 2002
SAP
Header conditions apply to all the items of a document and are distributed 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
SCM521
4-6
Only
"
Partner
Use
Item Mat. Qty.
Use
Internal
Price
Internal
Pos. Mat. Qty.
Purchase order
Partner
Material 1
Item Mat. Qty.
PB00
Gross price
10
1
80
100.00 A1
From
1 pc 100.00
20
1
40
100.00 A2
From
100 pc 99.00
From
900 pc 90.00
Price Cost center
Customizing
Purchase order
Condition type PB00
Item Mat. Qty.
Group cond. =
10
1
80
99.00 A1
20
1
40
99.00 A2
Price Cost center
SAP AG 2002
As long 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.
Use
"
© SAP AG
SCM521
4-7
Only
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.
Partner
"
SAP
SAP
Purchase order
Use
Internal
Info record conditions
Internal
Only
Group Conditions and Scales
Group Conditions and Print Indicator
Purchase order Material 1 1 pc @ 100.00
Surcharge: 50.00
Partner
Surcharge: Print = X
Surcharge: Print = S
Material 1 1 pc Surcharge Net value
100.00 45.00 145.00
Material 2 1 pc Surcharge Net value
10.00 5.00 15.00
Material 1 1 pc Material 2 1 pc
100.00
Surcharge Total value
50.00 160.00
10.00
SAP AG 2002
SAP
SAP
Calculation schema
Use
"
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 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
SCM521
4-8
Only
Internal
$ A condition line is not to be printed (print indicator _),
Partner
Use
Calculation schema
Internal
Only
Material 2 1 pc @ 10.00
Condition Group
Info record
Purchase order
Info record
Conditions RGR0
Vendor A Material 2 Cond. group XY
Vendor A Cond. group XY 2% discount
Partner
3
20.00
Vendor A Material 3
SAP AG 2002
SAP
SAP
20 2 150.00 - 2% Discount
Use
The use of condition groups allows you to regulate the price determination process on a variable basis. For example, you can assign info records showing the same price changes to a certain condition group by giving them the same alphanumeric character string.
"
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.
© SAP AG
SCM521
4-9
Only
"
Partner
Use
10 1 100.00 - 2% Discount
30
Info record
Internal
Item. Mat. Price
Internal
Only
Vendor A Material 1 Cond. group XY
Header and Group Conditions: Unit Summary
You are now able to: ! Describe the differences among the header, group and item conditions and explain how each is created ! Define condition types as group conditions
Only
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! Identify and use important control parameters for condition types and calculation schemas
Only
Internal
Use
Partner
© SAP AG
SCM521
4-10
Exercises Unit: Header and Group Conditions
Partner
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.
Use
1-2
You procure various office supplies from vendor T-K521C##. You have negotiated particularly favorable conditions for these supplies but you do not wish to create material master records.
Use
Calculation schema ZM00## is also to be valid for your vendor T-K521C##. Assign your vendor schema group ## to this vendor on the purchasing data screen of the vendor master record for purchasing organization 1000.
Create an information record for these supplies without material master records using the following data:
Internal
T-K521C## IDES Deutschland (1000) Hamburg (1000) Office supplies SCM521 Material group (ZT521) PC SCM521-## 4 days Z21 (SCM521) 100 pc 3.00 EUR from 1 pc 2.50 EUR from 500 pc
Only
Vendor: Purchasing organization: Plant: Short text: Material group: Order unit: Sort string: Planned delivery time: Purchasing group: Standard quantity: Price:
Save Information record ____________________________________. © SAP AG
SCM521
Partner
1-1
SAP
SAP
•
Internal
Only
At the conclusion of this exercise, you will be able to:
4-11
1-3
To ensure the lower price of 2.50 EUR is applied where appropriate on purchase orders for vendor T-K521C## using the material group ZT521 verify, condition type Z##A has a valid designated grouping condition indicator. If necessary set the group condition indicator for Z##A Save your change.
1-4
Based on the following data determine if a new condition type is required? In some instances, vendor T-K521C## imposes a general surcharge that varies according to the total order of each purchase order: • 30 EUR up to a total order value of 500 EUR • 20 EUR up to a total order value of 800 EUR
Only
Internal
• 10 EUR up to a total order value of 2000 EUR No surcharge is payable if the total order value exceeds 2000 EUR.
1-4-1 Upon which factors is a condition depend? ______________________________________________________ ______________________________________________________ 1-4-2 If you determine a new condition is required which condition class should you assign?
SAP
______________________________________________________
Use
______________________________________________________ ______________________________________________________
Internal
1-4-4 How can you make sure that your condition type is interpreted as a surcharge?
Partner
1-4-3 If you determine a new condition is required which calculation type should you assign?
SAP
______________________________________________________
Use
Partner
The surcharge applies to all materials supplied by the vendor and is to be apportioned among the individual purchase order items by value share.
______________________________________________________
Only
______________________________________________________ 1-4-5 How do you make sure that the amount of the surcharge is apportioned among the items? ______________________________________________________ ______________________________________________________ 1-4-6 Which scale basis and which scale type are appropriate? ______________________________________________________ ______________________________________________________ 1-4-7 Based on the data you have determined a new condition type is required. Which condition should you copy your new condition from? _____________________________________________________ © SAP AG
SCM521
4-12
1-4-8 Define the new condition type. Use the key Z##B and the description Surcharge SCM521-##. Save the new condition 1-5
Assign your new condition type Z##B to your calculation schema ZM00##. 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 is to be printed out at the item level. Which print indicator must you set to achieve printing at an item level? ? Set the printing indicator. ___________________________________________
1-6
Create a condition record for vendor T-K521C## for your new condition type Z##B using the following data: • 30 EUR up to a total order value of 500 EUR
Partner
• 20 EUR up to a total order value of 800 EUR • 10 EUR up to a total order value of 2000 EUR No surcharge is payable if the total order value exceeds 2000 EUR.
Use
The surcharge is valid until the end of next year. Save the new condition record. 1-7
Create a purchase order using the following data: Vendor:
SAP
T-K521C##
Purchasing organization: IDES Deutschland (1000)
Internal
Purchasing group
Z21 (SCM521)
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:
SCM521 (applies to both items)
Partner
Use
SAP
Internal
Only
Save your change.
Only
Order the following two items, which have no material master records, for cost center T-L20 Notepads, 400 pc Ring binders, 100 pc 1-7-1 Select 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 ________________
© SAP AG
SCM521
4-13
1-7-2 What is the net price for each item? ______________________________________________________ 1-7-3 What is the amount of the surcharge for each item? ______________________________________________________ Purchase order number: _________________________________
Use
Partner
Only
Internal
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
4-14
Solutions Unit: Header and Group Conditions
1-1
Only
Logistics → Materials Management → Purchasing → Master Data → Vendor → Purchasing → Change (Current) Enter the following data: Vendor
T-K521C##
Purchasing Organization
1000
Select Purchasing data SAVE You procure various office supplies from vendor T-K521C##. You have negotiated particularly favorable conditions for these supplies but you do not wish to create material master records. Create an information record for these supplies without material master records using the following data:
Vendor
T-K521C##
Material
Leave Blank
Purchasing Org
1000
Plant
1000
Only
Use Internal
Enter the following data on the initial screen:
Select the Enter icon Enter the following data on the General Data screen: Material group
ZT21
Description
SCM521-##
Order unit
PC
Sort String
SCM521-##
Select the Purch. Organization Data 1 radio button Enter the following data on the Purch. Organization Data 1 screen: © SAP AG
SCM521
Partner
Logistics → Materials Management → Purchasing → Master data → Info record → Create
SAP
SAP
1-2
Use
Enter Calculation schema ZM00##
Internal
Partner
Calculation schema ZM00## is also to be valid for your vendor T-K521C##. Assign your vendor schema group ## to this vendor on the purchasing data screen of the vendor master record for purchasing organization 1000.
4-15
Standard qty
100
Purch. Group
Z21
Plnd dely time
4
Net price
3.00 EUR
Select the Conditions radio button Select the Scales icon
Leave blank
3.00 EUR (this will default)
500
2.50 EUR
SAVE Information record ____________________________________. 1-3
To ensure the lower price of 2.50 EUR is applied where appropriate on purchase orders for vendor T-K521C## using the material group ZT521verify condition type Z##A has a valid designated grouping condition indicator. If necessary set the group condition indicator for Z##A Tools → Customizing→IMG → Edit Project Choose SAP Reference IMG radio button
SAP
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types
SAP
Partner
Amount
Use
Choose Define Condition Type.
Use
Select condition type Z##A
Partner
Select the Details icon and verify that Group condition is selected SAVE 1-4
Based on the following data determine if a new condition type is required? 1-4-1 Upon which factors is a condition depend? 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 If you determine a new condition is required which condition class should you assign? Condition class A (discounts and surcharges). 1-4-3 If you determine a new condition is required which calculation type should you assign? Calculation type B (fixed amount). 1-4-4 How can you make sure that your condition type is interpreted as a surcharge? Specify the condition type is interpreted as a surcharge via the Plus/minus sign: A (positive sign).
© SAP AG
SCM521
4-16
Only
Internal
Scale quantity
Internal
Only
Enter the following data on the Scales screen:
1-4-5 How do you make sure that the amount of the surcharge is apportioned among the items? 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 Which scale basis and which scale type are appropriate? Scale basis should be B (value scale) and scale type should B (To-scale). 1-4-7 Based on the data you have determined a new condition type is required. Which condition should you copy your new condition from? Copy condition type RL01
Tools → Customizing→IMG → Edit Project Choose SAP Reference IMG radio button
Partner
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Choose Define Condition Type. Select condition type RL01
Use
Select the Copy icon and make the following settings: Calculation type = B
SAP
Plus/Minus = A
SAP
Select the Group condition indicator Scale type and scale basis = B Be sure value is not checked.
Partner
SAVE 1-5
Assign your new condition type Z##B to you calculation schema ZM00##. Tools → Customizing→IMG → Edit Project
Internal
Use
Internal
Only
1-4-8 Define the new condition type. Use the key Z##B and the description Surcharge SCM521-##.
Choose SAP Reference IMG radio button
Only
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema. Select ZM00## and choose Control. Select step 10 RL01 Select the Copy icon Change the Ctyp to Z##B. 1-5-1 In which step have the discounts and surcharges been inserted into the calculation schema? Step 10 has the discounts and surcharges inserted into the calculation schema.
© SAP AG
SCM521
4-17
1-5-2 The condition values for your condition type Z##B is to be printed out at the item level. Which print indicator must you set to achieve printing at an item level? Set the printing indicator. Specify the condition values to be printed out at the item level by setting the print indicator of X. SAVE 1-6
Create a condition record for vendor T-K521C## for your new condition type Z##B using the following data: Logistics → Materials → Management → Purchasing → Master Data → Conditions → Other → Create Select the Key combination radio button and choose the Vendor as the Key combination Enter the vendor T-K521C##
Partner
Select the Scales icon Scale value
Amount
30 EUR
500 EUR
20 EUR
800 EUR
10 EUR
2000 EUR
SAP
SAP
Enter the following data:
Use
A surcharge is not payable if the total order value exceeds 2000 EUR. Change the validity period to be valid for a year. Save the new condition record 1-7
Create a purchase order using the following data:
Internal
Logistics-> Materials Management → Purchasing → Purchase order → Create → Vendor/Supplying Plant Known Enter the following date in the Header area of the purchase order: T-K521C##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
SCM521
Only
© SAP AG
Vendor:
Partner
Use
Internal
Only
Enter condition type Z##B
4-18
Enter the following data in the Item overview area of the purchase order: A
Short Text
PO quantity
OUn
Deliv. Date
Material group
Plant
Info rec.
K
Notepads
400
pc
4 weeks from today
ZT21
1000
Created in Step 1-2
K
Ring Binders
100
pc
4 weeks from today
ZT21
1100
Created in Step 1-2
Only Partner
Line item
Cost Center
10
T-L20
20
T-L20
Use
Do not save the purchase order until you have answered steps 1-7-1 to 1-7-3
SAP
1260 EUR
The gross price per 1 pc
2.50 EUR
SAP
1-7-1 Select the header Condition tab and check The total net value of the purchase order
Use
Partner
The surcharge for the entire purchase order 10 EUR 1-7-2 What is the net price for each item? Select the item details Conditions tab
Internal
The net price 2.52 EUR was calculated for the two items. 1-7-3 What is the amount of the surcharge for each item? 8 EUR
The surcharge amount for item 20 is
2 EUR
Only
The surcharge amount for item 10 is SAVE
Purchase Order number: ________________________________
© SAP AG
SCM521
Internal
Enter the following data in the Item details/Account assignment tab of the purchase order:
4-19
Maintaining Conditions
Contents: ! Maintaining Time-Dependent Conditions ! Validity Periods in Info Records ! Change Documentation and Change Options ! List of Conditions
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
5-1
Maintaining Conditions: Unit Objectives
At the conclusion of this unit, you will be able to: ! Execute the functions for the maintenance and display of conditions ! Change condition values and validity periods using collective functions
Only
Use
SAP AG 2003
SAP
SAP
Partner
Internal
! Define change options for condition types
Only
Internal
Use
Partner
© SAP AG
SCM521
5-2
Maintaining Conditions: Business Scenario
! Over time, your vendors’ prices and conditions may change. Individual and collective functions are available for maintaining and displaying conditions.
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
5-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Maintaining Conditions: Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
5-4
Maintaining Time-Dependent Conditions 1
Validity from 01.01. to 12.31. Cond. ty. Amount PB00 10.00 GAU1 Restore RB00 ZB00 5% RA00 ...
Validity from 01.01. to 12.31. Cond. ty. Amount PB00 10.00 RA00 5%
Scale PB00
Info record conditions
Details (RA00)
Validity from 01.01. to 12.31. Qty. Amount From 1 pc 10.00 From 500 pc 9.50
Validity from 01.01. to 12.31. Qty. Amount PB00 10.00 RA00 5%
Validity from 01.01. to 12.31. Amount: 10.00 per: 1 pc Scale type: A Deletion ind.:
Partner
Only
Propose cond. supplements
Scale
Details
SAP AG 2002
"
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
SCM521
5-5
Only
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 by the condition type.
Partner
"
Use
SAP
Validity from 01.01. to 12.31. Cond. ty. Amount PB00 10.00
SAP
Internal
Info record conditions
Use
Info record conditions
Internal
Info record conditions
Maintaining Time-Dependent Conditions 2
Master data ... Conditions ...
Prices ...
... Per contract Per info record ...
... Per vendor Per condition group Per material type Per invoicing party ...
Condition type RL01 Vendor discount RGR0 Group discount MAR1 Misc. provision REST Account discount
Master data
Partner SAP
Discounts/surch. ...
...
...
Conditions ...
Other ...
Create Create by referencing Change Display
1) Condition types GAU2, NAVS 2) Own condition types
SAP AG 2002
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
SCM521
5-6
Only
"
Partner
"
SAP
Use
...
Conditions ...
Use
Internal
...
Internal
Only
Master data
Validity Periods
Info record Vendor Material Price Valid from to
Only
11.00 Price Valid from 07.01.01 to 12.31.01
Conditions whose validity periods are completely covered by those of new conditions are deleted when the latter are saved.
Confirm
Partner
Existing validity periods 01.01.01
06.30.01
12.31.01
New validity period 01.01.01 04.01.01
12.31.01
06.30.99
SAP AG 2002
"
You can change both the conditions of an existing validity period and the start/end dates of the validity period.
"
Condition validity periods are not permitted to overlap. 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.
"
When accessing time dependant conditions within a single function call, you can only access one validity period.
© SAP AG
SCM521
5-7
Only
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.
Partner
"
SAP
SAP
Overlapping validity periods
Use
Use
New price 10.50 Valid from 04.01.01 to 06.30.99
Internal
Internal
A 1 10.00 01.01.01 06.30.01
Collective Changes
Vendor A Material 1
Gross price Discount
(PB00) (RA00)
10.00 2%
Valid from 01.01. - 12.31.
10.20 2%
Valid from 01.01. - 12.31.
Change in gross price: + 2% valid as of 07.01.
Condition type change: 5% discount from 06.01. - 07.31.
SAP
Partner
Vendor A Material 1
Gross price
(PB00)
10.20
Valid from 01.01. - 12.31.
Discount
(RA00)
2%
Valid from 01.01. - 05.31.
Discount
(RA00)
5%
Valid from 06.01. - 07.31.
Discount
(RA00)
2%
Valid from 08.01. - 12.31.
SAP AG 2002
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
SCM521
5-8
Only
"
Partner
"
SAP
Use
(PB00) (RA00)
Use
Internal
Gross price Discount
Internal
Only
Vendor A Material 1
Changing Conditions using a Condition Index
Information record Vendor A Material group 005
Information record
Only
Define Permitted Fields
;
Edit Condition Index Tables
;
Activate Cond Index Tables
; ; ;
Rebuild Cond Index Tables
New price for all info records for material group 005 regardless of vendor, for example
Define Overviews Assign Overviews
Vendor C Material group 005
SAP AG 2002
"
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.
SCM521
5-9
Only
© SAP AG
Partner
Use
;
SAP
Internal
Change Cond Types
Use
SAP
Partner
Information record
;
Internal
Vendor B Material group 005
Customizing
Automatic Adjustment: Changes to Conditions
Vendor Pur. data. pur. group Doc. index active
Customizing Document update C. ty. Origin Cond. tab. PB00 2 017 PB00 2 018
Only Partner
01.01.
Automatic document adjustment
Info record change 01.01. - 12.31. Price 11.00
04.01.
07.01.
12.31.
Price 11.00 Adjustment of worklist
Compilation of worklist
Use
SAP AG 2002
SAP
SAP
"
If you intend to use the Automatic document adjustment function to retroactively modify vendor documents in response to future changes you must set the Document index active indicator in the vendor’s master record. 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.
Use
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.
© SAP AG
SCM521
5-10
Only
"
Partner
Internal
Internal
Purchase order Price 10.00 (info record)
Customizing Document update Log. message cat. active CONDBI
Change Documentation
Date + 01.10. + 15.12.
Only
Description 1 "Valid to" date 2 Condition amount/percentage 3 Suppl. condition (RA00): scale changed Suppl. condition (RA00): scale changed Condition amount/percentage
Old value New value 31.12.97 31.12.98 10,00 11,00 1000 4% 5000 5% 3% 4% -
Partner
1 Change in validity period 2 Change in gross price 3 Change in a discount scale
SAP AG 2003
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
"
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.
© SAP AG
SCM521
5-11
Only
$ 2. Description of change made; old value (before change) and new value (after change); name of changed field
Partner
"
SAP
SAP
Cond. Vend. Mat. Purch. org. validity PB00 A 1 1000 01.01.97 - 12.31.97 PB00 A 1 1000 01.01.97 - 12.31.98
Use
Use
User Myers Myers
Internal
Internal
Time 14:25 10:14
Change Options Within Document
A Vendor Purch. org. 1000 10 pc material 1
Only
C. ty. Amount PB00 10.00 RA00 1% FRA1 5%
Conditions PB00 RA00 FRA1
10.00 1% 5%
Partner
Changeable? Customizing condition types: Change options Manual entry Delete
Amount/percent
Calculation type
Value
Quantity conversion
SAP AG 2002
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 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.
© SAP AG
SCM521
5-12
Only
$ The manual condition takes priority (indicator C). In the case of manual entry, no check is made to see if a condition record exists.
Partner
"
SAP
SAP
Vendor A Material 1 Purch. org. 1000
Use
Use
Purchase order
Internal
Internal
Info record conditions
Data Protection Through User Authorizations
Outl. agreement
Partner
User authorizations
User parameter EFB
Authorization object V_KONH_VKS Activity: 01. 02. 03 Condition type: PB00
Display condition Enter condition Without material Field selection
SAP AG 2002
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, access sequences and so on. In addition, authorizations for the authorization object V_KONG_VWE (generation of conditions: authorization for usage/application) belonging to the class Conditions is necessary.
© SAP AG
SCM521
5-13
Only
"
Partner
Use
"
SAP
SAP
Price 1.00
Use
Internal
Info record
Internal
Only
Price 1.00
Pur. order
Maintaining Conditions: Unit Summary
You are now able to: ! Execute functions for the maintenance and display of conditions ! Change condition values and/or validity periods using collective functions
Only
Use
SAP AG 1999
SAP
SAP
Partner
Internal
! Define change options for condition types
Only
Internal
Use
Partner
© SAP AG
SCM521
5-14
Exercises Unit: Maintaining Conditions
At the conclusion of this exercise, you will be able to: • Execute functions for the maintenance and display of conditions
Only Partner
• Define change options for condition types
Create a new condition type Z##C with the description SCM521 Freight ## by copying the standard condition type FRB1.
SAP
SAP
Use
Over time, your vendors’ prices and conditions may change. Individual and collective functions are available for maintaining and displaying conditions.
1-1
Specify the following for your new condition type: • Condition amounts cannot be changed in the document
Partner
Use
• The condition type may not be deleted in the document 1-1-1 Can you make these settings changes? Which control parameters for condition types would be used to make the setting changes? ______________________________________________________ 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. Save your changes.
© SAP AG
SCM521
5-15
Only
Internal
Internal
• Change condition values or validity periods (or both) using collective functions
1-3
You procure material T-REM## from vendor T-K521B##. Use your new condition type Z##C and create a cross-plant information record for purchasing organization 1000 using the following data:
1-4
Partner
Using your new condition type Z##C create two plant-specific information records for purchasing organization 1000 using the following data: Plant Berlin (1100): Gross price: 17.80 EUR Freight surcharge: 40.00 EUR
•
Plant Dresden (1200): Gross price: 18.20 EUR Freight surcharge: 35.00 EUR
SAP
1-5
•
Use
Create a purchase order using the following data:
Internal
Partner
Vendor: T-K521B## Purchasing organization: IDES Deutschland (1000) Purchasing group: Z21 (SCM521) Delivery date: In four weeks Order 100 pc of material T-REM## for plant Hamburg (1000)
Use
SAP
Vendor T-K521B## grants special conditions for material T-REM## but only for plants Berlin (1100) and Dresden (1200).
Internal
Only
Planned delivery time: 7 days Purchasing group: Z21 (SCM521) Standard quantity: 100 pc You have agreed to the following conditions with the vendor: Gross price: 18 EUR Freight surcharge: 50 EUR The conditions are valid from January 1 of the current year until December 31 of next year.
1-5-1 Can you change the freight surcharge taken from the info record? ______________________________________________________
Only
1-5-2 Can you delete the freight surcharge taken from the info record? ______________________________________________________ Purchase order number: ___________________________________ 1-6
Vendor T-K521B## advises he will reduce all gross prices for his materials by 5%. The new prices are for all Plants. The reduced prices are valid for a threemonth period. The reductions start on the first of next month. Collectively change all info records for vendor T-K521B##. Save the price change.
1-7
© SAP AG
Display a general overview of all the prices of vendor T-K521B## for material TREM##.
SCM521
5-16
Solutions Unit: Maintaining Conditions
1-1
Create a new condition type Z##C with the description SCM521 Freight ## by copying the standard condition type FRB1. Tools → Customizing → IMG → Edit Project
Only
Internal
Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types
Partner
Choose Define Condition Type. Select FRB1 then choose Copy. Create a new conditions type Z##C specify the following:
Use
• Condition amounts cannot be changed in the document • The condition type may not be deleted in the document
SAP
SAP
Deselect the indicators for the Amount/Percent and Delete fields 1-1-1 Can you make these settings changes? Which control parameters for condition types would be used to make the setting changes?
Use
1-2
Change your calculation schemas YM00## and ZM00## by replacing the standard condition type FRB1 with your new condition type Z##C. Tools → Customizing → IMG→Edit Project
Only
Internal
SAVE your condition type.
Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select the schema Z##C Choose the Control icon and replace FRB1 with Z##C. Save
© SAP AG
SCM521
Partner
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 one to specify whether a condition type can be deleted in a document.
5-17
1-3
You procure material T-REM## from vendor T-K521B##. Use your new condition type Z##C and create a cross-plant information record for purchasing organization 1000 using the following data: Logistics → Materials Management → Purchasing → Master data → Info record → Create Enter the following data on the Initial screen: Vendor
T-K521B##
Material
T-REM##
Purchasing org.
1000
Select the Purch. Org data 1 radio button.
Only Partner
7
Purchase group:
Z21
Standard qty:
100
Net price:
18.00 EUR
Select the Conditions radio button.
Use
Condition
Condition type
Amount
Gross price
PB00
18.00 EUR note: this will have defaulted from the purchase org screen.
Freight surcharge
Z##C
50.00 EUR
Partner
Use
SAP
Enter the following data on the Conditions screen:
SAP
Change the Valid on date to: January 1st of the current year Change the Valid to date to: December 31st of the following year SAVE 1-4
Vendor T-K521B## grants special conditions for material T-REM## but only for plants Berlin (1100) and Dresden (1200). Using your new condition type Z##C create two plant-specific information records for purchasing organization 1000 using the following data: Logistics → Materials Management → Purchasing → Master data → Info record → Create Enter the following data on the Initial screen: Vendor
T-K521B##
Material
T-REM##
Purchasing org.
1000
Plant
1000
Select the Purch. Org data 1 radio button. © SAP AG
SCM521
5-18
Only
Internal
Plnd dely time:
Internal
Enter the following data on the Purch. Org data 1 screen:
Enter the following data on the Purch. Org data 1 screen: Plnd dely time:
7
Purchase group:
Z21
Standard qty:
100
Net price:
17.80 EUR
Select the Conditions radio button.
Condition type
Amount
Gross price
PB00
17.80 EUR note: this will have defaulted from the purchase org screen.
Freight surcharge
Z##C
40.00 EUR
Use
Partner
Condition
Internal
Only
Enter the following data on the Conditions screen:
Change the Valid on date to: January 1st of the current year Change the Valid to date to: December 31st of the following year
SAP
SAP
SAVE Using the vendor’s pricing data repeat the process steps for plant 1100 SAVE
Use
Create a purchase order using the following data: Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known Vendor:
T-K521B##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Only
Internal
Enter the following date in the Header area of the purchase order:
Enter the following data in the Item overview area of the purchase order: Material
PO quantity
Deliv. Date
Plant
T-REM##
100
4 weeks from today
1000
Select the Conditions tab within the Item details area of the purchase order. 1-5-1 Can you change the freight surcharge taken from the info record? The freight surcharge taken from the info record cannot be changed. © SAP AG
SCM521
Partner
1-5
5-19
1-5-2 Can you delete the freight surcharge taken from the info record? The freight surcharge taken from the info record cannot be deleted SAVE Purchase order number_____________________________________ 1-6
Vendor T-K521B## advises he will reduce all gross prices for his materials by 5%. The new prices are for all Plants. The reduced prices are valid for a threemonth period. The reductions start on the first of next month. Collectively change all info records for vendor T-K521B##. Logistics → Materials Management → Purchasing → Master Data → Conditions → Vendor Price Changes → Involving Info Records
Only
Internal
Enter vendor T-K521B## 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. Choose Execute. SAVE the price change 1-7
Display a general overview of all the prices of vendor T-K521B## for material TREM##.
SAP
Choose a scope-of-list parameter that enables you to list both cross-plant and plantspecific prices in a general overview.
Use Internal
Vendor
T-K521B##
Material
T-REM##
Scope of list
0003
Partner
Enter the following data:
SAP
Logistics → Materials Management → Purchasing → Master Data → Conditions → Prices → General Overview
Use
Partner
Deselect the indicator for Test run.
Choose the Execute icon
Only
© SAP AG
SCM521
5-20
Special Condition Types and Special Functions
Contents: ! Precious Metal Conditions ! Delivery Costs ! Pallet Discount/Surcharge
Partner
! Condition Exclusion Procedure
Use
SAP AG 1999
Only
Internal
Partner
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.
Use
"
SAP
SAP
Internal
Only
! Weight and Volume Dependent Conditions
© SAP AG
SCM521
6-1
Unit Objectives
At the conclusion of this unit, you will be able to: ! Create condition types for precious metal conditions by copying existing ones ! Explain the price determination process using precious metal conditions
Only
! Explain the function of the pallet discount/surcharge condition types ! Describe how to maintain weight and volume dependent conditions
Use
! Create a condition exclusion SAP AG 2001
SAP
SAP
Partner
Internal
! Describe the control parameters for condition types for delivery costs
Only
Internal
Use
Partner
© SAP AG
SCM521
6-2
Unit Business Scenario
! 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.
Only
! Your vendor imposes a surcharge based on the weight of the material provided. ! In some instances, several conditions are valid for the same item. You want to define which condition should take priority.
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! There are certain materials you purchase that are delivered on pallets, and the vendor offers you a discount if you purchase a complete pallet.
Only
Internal
Use
Partner
© SAP AG
SCM521
6-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
6-4
Precious Metal Conditions (GAU1/GAU2)
Material master rec.
Info rec. conditions
Conditions GAU2
Base unit: Altern. unit: 2 GAU
C. ty. Amt. per unit PB00 100.00 GAU1 - 10.00 1 GAU
01.01. - 01.07.:10.20/1 GAU 01.08. - 01.14.: 9.80/1 GAU 01.15. - 01.21.: 9.95/1 GAU
Only
Ruling PM price on 01.16.: 9.95
SAP AG 2002
"
You specify the precious metal portion in the material master record or the info record using a special non-dimensional unit of measure (for example, GAU = (G) gram of (AU) 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 be entered in the document schema in the above sequence. Different but directly consecutive steps must be assigned for both. The Statistical indicator may not be set for either.
"
The two condition types must satisfy special requirements:
Use
There is a special condition category ”U” for pricing components that vary according to daily fluctuations in ruling rates, 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.
$ Both condition types have condition class A, condition category U, and calculation rule C (quantity-dependent), and the same unit of measurement (e.g. GAU) must be assigned to each. $ The first condition type must be flagged as "manual" and have the calculation formula "31". Only this first condition type may be entered in the supplementary condition schema. $ The second condition type may not be flagged as "manual". It must have the calculation formula "32" and the requirement "31". "
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”
© SAP AG
SCM521
6-5
Only
"
Partner
Internal
SAP
SAP
Ruling PM price on 01.04.: 10.20
Time
Use
Goods receipt GR date: 01.16. Valuation price: 99.90
Internal
Purch. order PO date: 01.04. Order price: 100.40
Partner
pc GAU 1 pc
Delivery Costs
Calculation schema C. ty. Stat AKey
Accr.
FRA1
FRE
FR1
FRE
FR2
Cond. type FRA2
Only
1 Entry possible if no vendor maintained
Planned delivery costs are delivery costs (incidental procurement costs) agreed with or stipulated by the vendor, a forwarder or carrier, or a customs office before the purchase order is placed, which are entered in the PO when the latter is created.
"
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 determination.
© SAP AG
SCM521
6-6
Only
"
Partner
Use
SAP AG 2002
SAP
SAP
Partner
2 Entry always possible
Use
Internal
Transaction/event key for freight purchase account
Internal
Condition class: A Calculation type:A Condition cat. B X Accrual: Vendor GR: _ No entry possible
Transaction/event key for account determination
Pallet Discount/Incomplete Pallet Surcharge
Pallet discount 5.00 /1 pallet
100.00
1 pallet = 10 boxes
Incomplete pallet surcharge 20.00 /1 pallet
Calculation schema ...
Reqt.
CalcForm BasForm
20
0
Net val. incl. discount
0
LP00
Pallet discount
22
26 ...
0
LP01
Incompl. pallet surch.
24
*Qty. in whole numbers
*Qty. = 1 if incomplete pallet
FORM FRM_KOND_BASIS_022. ... ENDFORM.
FORM FRM_KOND_BASIS_024. ... ENDFORM.
Use
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 formula determines 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 formula 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 accumulation 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
SCM521
6-7
Only
"
Partner
Internal
SAP AG 2002
SAP
SAP
24
Use
Only
Description
Partner
Count. C. type
Internal
Step
Weight- and Volume-Dependent Conditions
Vendor A
Purchase order
Weight-dep. surcharge
Material 1 10 pc @ 0.2 kg
Up to 10 kg 2.00 per kg Up to 30 kg 2.20 per kg Up to 50 kg 2.50 per kg
Only
=> 26.40 Surcharge
Material 2 Net weight : 1.0 kg
Partner SAP
= 12 kg
Material 1 Net weight : 0.2 kg
Material 3 Net weight : 0.5 kg SAP AG 2002
"
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
"
You can maintain the Gross weight and Volume fields in the additional data for the item. Both fields relate to an order unit. This means that if you order 100 pcs. of material A, for example, and one piece weighs 10 kg, the Weight field contains the figure 10 kg (not 1000 kg).
"
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
SCM521
6-8
Only
You have the option of maintaining weight- or volume-dependent conditions. The condition types for weights and volumes are then taken into account during the purchase price determination process.
Partner
"
SAP
Use
6 kg
Use
Internal
Material 3 12 pc @ 0.5 kg
4 kg +
Internal
Material master record Basic data
Material 2 4 pc @ 1.0 kg
2 kg +
Condition Exclusion Procedure
Condition exclusion procedure A Vendor A: vendor discount
?
Most favorable condition value
Vendor A: discount for material 1
?
Condition exclusion procedure C
Only
?
SAP
Partner
Condition exclusion procedure D Vendor A: vendor discount
?
Either/or
?
Vendor A: discount for material 1
SAP AG 2002
"
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).
© SAP AG
SCM521
6-9
Only
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.
Partner
"
SAP
Use
Vendor A: discount for material 1 + discount for material 2
Use
Internal
?
Most favorable sum of condition values
Internal
Vendor A: vendor discount
Unit Summary
You are now able to: ! Create condition types for precious metal conditions by copying existing ones ! Explain the price determination process using precious metal conditions
Only
! Explain the function of the pallet discount/surcharge condition types ! Describe how to maintain weight and volume dependent conditions ! Create a condition exclusion
Use
SAP AG 2001
SAP
SAP
Partner
Internal
! Describe the control parameters for condition types for delivery costs
Only
Internal
Use
Partner
© SAP AG
SCM521
6-10
Exercises Unit: Special Condition Types and Special Functions Topic: Precious Metal Conditions
•
Maintain precious metal conditions
•
Examine the price determination process using precious metal conditions
Partner
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 Mat. price ## by copying the standard condition type GAU1. Assign the unit of measure: GAU (gram of gold) to your new condition type.
Internal
1-2
Create a second new condition type Z##2 with the description Curr. mat. price ## by copying the standard condition type GAU2. Check whether the unit of measure GAU has also been assigned. 1-2-1 The current date for condition type Z##2 should be define to automatically suggest the validity start and end dates.
Only
Which control parameters would need to be defined? _____________________________________________________ Save the new condition type. 1-3
Change the calculation schemas ZM00## and YM00## by replacing the standard condition types GAU1 and GAU2 with the new condition types Z##1 and Z##2. Save the changes.
1-4
Change the material master record for material T-REN## by assigning an alternative unit of measure of 5 GAU (gram of gold) equals one piece. 1-4-1 What is the conversion formula for the units of measure? ______________________________________________________ Save the change.
© SAP AG
SCM521
Partner
Save the new condition type.
SAP
SAP
Create condition types for precious metal conditions by copying existing ones
Use
Use
•
Internal
Only
At the conclusion of this exercise, you will be able to:
6-11
1-5
Using condition type Z##1 create an information record using the following data: Vendor:
T-K521C##
Material:
T-REN##
Purchasing organization:
IDES Deutschland (1000)
Plant:
Hamburg (1000)
Planned delivery time:
10
Purchasing group:
Z21 (SCM521)
Standard quantity:
100
Save the information record. 1-6
Maintain the current prices for precious metals by creating condition records for the condition type Z##2. Yesterday’s price was:
10.60 EUR per 1 GAU.
Today’s price is:
10.20 EUR per 1 GAU.
Use
Partner
The conditions are valid from the first day of the current month until December 31st of next year.
Save the precious metal conditions.
SAP
Vendor:
T-K521C##
Document date:
Yesterday
Purchasing organization:
IDES (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
Today
Internal
Order 1 pc of material T-REN## for plant Hamburg (1000), storage location 0001. 1-7-1 Check the results of the price determination process: _________________________________
Metal price portion:
_________________________________
Current metal price:
_________________________________
Only
Gross price:
Condition base value for Z##2 _________________________________
© SAP AG
Condition value for Z##2
_________________________________
Additional surcharges:
_________________________________
Discounts:
_________________________________
Net price:
_________________________________
Actual price:
_________________________________
SCM521
Partner
Use
Create a purchase order using the following data:
SAP
1-7
Internal
Only
The gross price for the material is 120 EUR. This price includes 10 EUR per 1 gram of gold.
6-12
1-7-2 Display an analysis of the pricing log to determine the condition pricing date for Z##2: ______________________________ Save your purchase order. 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? _________________________________________________________
Only
Use
Partner
_________________________________________________________
Internal
1-9-2 How do you explain the difference between the goods receipt value and the purchase order price?
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
6-13
Exercises Unit: Special Condition Types and Special Functions Topic: Condition Exclusion Procedure At the conclusion of this exercise, you will be able to: • Compare the different condition exclusion procedures
2-2
Vendor T-K521D## supplies you with the materials T-REK##, T-REL##, and TREM##. Create an information record for all three materials with the following conditions: •
The planned delivery time 7 days
•
purchasing group Z21 (SCM521)
•
The standard order quantity 100 pc
•
Validity period indefinitely
Partner
Use
SAP
The calculation schema ZM00## is also to be valid for vendor T-K521D## purchasing organization (1000). Assign your vendor schema group ## to vendor TK521D##.
10 EUR
Discount % on gross:
2.5%
Only
Internal
Material T-REK## Gross price: Material T-REL## Gross price:
100 EUR
Discount (value):
2 EUR from 1 pc 5 EUR from 100 pc
Material T-REM## Gross price: 2-3
20 EUR
Your vendor T-K521D## advises you that he is granting you a general discount of 5%, valid indefinitely. Create the vendor discount for condition type RL01.
© SAP AG
SCM521
SAP
2-1
Use
Partner
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.
Internal
Only
• Create a condition exclusion
6-14
2-4
Vendor T-K521D## discounts only apply 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 the condition exclusion group A##. Assign the condition type RL01 to the condition exclusion group B##. Save your assignments.
2-6-1 Which condition exclusions procedure did you choose? ___________________________________________________ 2-6-2 In which order must the condition exclusion groups be specified? ______________________________________________________ T-K521D##
Purchasing organization:
IDES Deutschland (1000)
Purchasing group:
Z21 (SCM521)
Delivery date:
In four weeks (applies to all items)
Plant:
1000 (applies to all items)
Go to each purchase order item and check the price determination process.
SAP
Vendor:
SAP
Create a purchase order using the following data:
Use
2-7
Use
Partner
Assign the condition exclusion groups A## and B## and a suitable condition exclusion procedure to the calculation schema ZM00##.
Internal
Only
2-6
Order 10 pc of each of materials T-REK##, T-REL##, and T-REM##.
Partner
How are the net prices for the following materials determined?
Internal
2-7-1 Material T-REK## _________________________________________________________
Only
2-7-2 Material T-REL## _________________________________________________________ 2-7-3 Material T-REM## _________________________________________________________ Purchase order number: _____________________________________
© SAP AG
SCM521
6-15
Solutions Unit: Special Condition Types and Special Functions Topic: Precious Metal Conditions 1-1
Create a new condition type Z##1 with the description Mat. price ## by copying the standard condition type GAU1. Assign the unit of measure: GAU (gram of gold) to your new condition type.
Only
Internal
Tools -> Customizing -> IMG -> Edit Project Choose: SAP Reference IMG radio button
Partner
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Choose Define Condition Type
Use
Select GAU1 then choose Copy Change the unit of measure to GAU. SAVE
SAP
Create a second new condition type Z##2 with the description Curr. mat. price ## by copying the standard condition type GAU2. Check whether the unit of measure GAU has also been assigned. Tools -> Customizing -> IMG -> Edit Project
Use
Partner
Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Select GAU2 then choose Copy Verify the unit of measure is GAU. 1-2-1 The current date for condition type Z##2 should be define to automatically suggest the validity start and end dates. Which control parameters would need to be defined? 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. SAVE
SCM521
6-16
Only
Internal
Choose Define Condition Type
© SAP AG
SAP
1-2
1-3
Change the calculation schemas ZM00## and YM00## by replacing the standard condition types GAU1 and GAU2 with the new condition types Z##1 and Z##2. Tools -> Customizing -> IMG -> Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process→ Define Calculation Schema. Select schema ZM00## then choose Control. Replace GAU1 and GAU2 with Z##1 and Z##2 Select schema YM00## then choose Control. Replace GAU1 and GAU2 with Z##1 and Z##2 SAVE
1-4
Partner
Logistics → Materials Management → Material Master → Material → Change → Immediately. Select the Basic Data 1 view.
Use
Select Additional data, and then choose Units of measure tab SAVE 1-4-1 What is the conversion formula for the units of measure? The conversion formula for the units of measure is 5 GAU = 1 pc 1-5
Using condition type Z##1 create an information record using the following data:
Use
Partner
Logistics → Materials Management → Purchasing → Master data → Info Record → Create T-K521C##
Material
T-REN##
Purchasing org.
1000
Plant
1000
Only
Internal
Enter the following data on the Initial screen: Vendor
Select the Purch. Org data 1 radio button. Enter the following data on the Purch. Org data 1 screen: Plnd dely time:
10
Purchase group:
Z21
Standard qty:
100
Net price:
120.00 EUR
Select the Conditions radio button.
© SAP AG
SCM521
SAP
SAP
Change the material master record for material T-REN## by assigning an alternative unit of measure of 5 GAU (gram of gold) equals one piece
Internal
Only
SAVE
6-17
Enter the following data on the Conditions screen: Condition
Condition type
Amount
Gross price
Z##A
120.00 EUR note: this will have defaulted from the purchase org screen.
Mat price port ##
Z##1
10 EUR
Change the Valid to date to: December 31st of the following year SAVE 1-6
Create a purchase order using the following data:
Partner SAP Internal
Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor /Supplying Plant Known
Vendor:
T-K521C##
Document date
Yesterday’s date
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Only
Enter the following date in the Header area of the purchase order:
Enter the following data in the Item overview area of the purchase order:
© SAP AG
Material
PO quantity
Deliv. Date
Plant
T-REN##
1
Today
1000
SCM521
Partner
1-7
SAP
Logistics-> Materials Management-> Purchasing → Conditions → Other → Create. Enter condition type Z##2. On the following screen, enter company code 1000 Change Valid on and Valid to yesterday’s date and Enter the price of 10.60 EUR per 1 GAU SAVE Repeat the steps to enter the new price for Today’s price. Change Valid on and Valid to today’s date and Enter the price of 10.20 EUR per 1 GAU SAVE
Use
Use
Maintain the current prices for precious metals by creating condition records for the condition type Z##2.
Internal
Only
Change the Valid on date to: The first day of the current month of the current year
6-18
1-7-1 Check the results of the price determination process:
Partner
120.00 EUR
Metal price portion:
10.00 EUR per 1 GAU = 50.00 EUR per 1 pc
Current metal price:
10.60 EUR per 1 GAU = 53.00 EUR per 1 pc
Condition base value for Z##2:
5 GAU
Condition value for Z##2:
53.00 EUR (10.60 x 5 GAU)
Additional surcharges;
30.00 EUR
Discounts:
None
Net price:
153.00 EUR
Actual price:
153.00 EUR (This surcharge may appear due to a surcharge condition type created in a prior unit.)
1-7-2 Display an analysis of the pricing log to determine the condition pricing date for Z##2 Condition pricing date
Use
Yesterday’s date
SAVE Purchase order number: _______________________________________ 1-8
SAP
Post a goods receipt against your purchase order Logistics → Materials Management → Inventory Management → Goods Movement → Goods Receipt → For Purchase Order → PO Number Known. Select Item OK SAVE
Only
Internal
Material document number: __________________________________________
Partner
Enter your purchase order number and choose the Execute icon
Use
SAP
Gross price:
Internal
Only
Go to the Conditions tab in the item details screen area of your purchase order
© SAP AG
SCM521
6-19
1-9
Display the accounting document for your goods receipt posting. 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 At which price was the material valuated at the time of goods receipt? The material was valuated at 151.00 EUR. 1-9-2 How do you explain the difference between the goods receipt value and the purchase order price?
Only
To be specific, the goods receipt valuation price of 151.00 EUR is 2.00 EUR less than the 153.00 EUR order value on the purchase order. yesterday’s price of 10.60 EUR and today’s price of 10.20 EUR. This is a decrease of 0.40 EUR. Therefore, 0.40 UNI x 5 GAU = 2.00 EUR decrease.
Use
Partner
In the previous exercise you entered
Internal
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.
SAP
SAP Only
Internal
Use
Partner
© SAP AG
SCM521
6-20
Solutions Unit: Special Condition Types and Special Functions Topic: Condition Exclusion Procedure 2-1
The calculation schema ZM00## is also to be valid for vendor T-K521D## purchasing organization (1000). Assign your vendor schema group ## to vendor TK521D##.
Enter the following data: Vendor
T-K521D##
Purchasing org
1000
Select the purchase date Maintain the vendor schema group ## SAVE Vendor T-K521D## supplies you with the materials T-REK##, T-REL##, and TREM##. Create an information record for all three materials with the following conditions: Gross price:
10 EUR
Discount % on gross:
2.5%
Partner
Use
Material T-REK##
Internal
Material T-REL## Gross price:
100 EUR
Discount (value):
2 EUR from 1 pc 5 EUR from 100 pc
SAP
SAP
2-2
Use
Partner
Internal
Only
Logistics → Materials Management → Purchasing → Vendor → Purchasing → Change (Current).
Material T-REM##
Only
Gross price:
20 EUR
Logistics → Materials Management → Purchasing → Master data → Info Record → Create Enter the following data on the Initial screen: Vendor
T-K521D##
Material
T-REK##
Purchasing org.
1000
Plant
1000
Select the Purch. Org data 1 radio button.
© SAP AG
SCM521
6-21
Enter the following data on the Purch. Org data 1 screen: Plnd dely time:
7
Purchase group:
Z21
Standard qty:
100
Net price:
10.00 EUR
Select the Conditions radio button.
Partner
Condition type
Amount
Gross price
PB00
10.00 EUR note: this will have defaulted from the purchase org screen.
Discount % on Gross
RA01
2.5 %
Change the Valid on date to: Today
Use
Change the Valid to date to: indefinitely SAVE Repeat the steps for material T-REL## and T-REM##. Hint: make the requested changes to the conditions for each material.
SAP
Save each information record 2-3
Your vendor T-K521D## advises you that he is granting you a general discount of 5%, valid indefinitely. Create the vendor discount for condition type RL01.
Internal
Logistics → Materials Management → Purchasing → Master Data → Conditions → Discounts/Surcharges → by Vendor Enter the following data: 1000
Vendor
T-K521D##
Scope of list
0001
Only
Purchasing Organization
Choose the Execute icon Select the purchasing organization line by using the mouse and clicking on the line once. Choose the Create icon Enter the discount of 5% SAVE
© SAP AG
SCM521
Partner
Use
SAP
Condition
Internal
Only
Enter the following data on the Conditions screen:
6-22
2-4
Vendor T-K521D## discounts only apply 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 ##. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Exclusion Choose Condition Exclusion Groups Select the New entries radio button
Only
Internal
Enter the new exclusion groups A## with the description Material discounts ## and B## with the description Vendor discounts ## SAVE
Partner
2-5
Assign the discount condition types RA00, RA01, RB00, and RC00 to the condition exclusion group A##. Assign the condition type RL01 to the condition exclusion group B##.
Use
Tools → Customizing → IMG →> Edit Project Choose: SAP Reference IMG radio button
SAP
SAP
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Exclusion Choose Assignment of Condition Exclusion Groups - Condition Types Select the New entries radio button
Use Internal
CTyp
A##
RA00
A##
RA01
A##
RB00
A##
RC00
B##
RL01
SCM521
Only
© SAP AG
ExGr
Partner
Enter the following data:
6-23
2-6
Assign the condition exclusion groups A## and B## and a suitable condition exclusion procedure to the calculation schema ZM00##. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Exclusion Choose Assignment of Condition Exclusion Groups - Condition Schema Select the schema ZM00## Choose the Exclusion folder
Internal
Only
Select the New entries radio button
Sno
1
Cpr
D
ExGr1
A##
ExGr2
B##
2-6-1 Which condition exclusion procedures did you choose?
SAP Use
Only
Internal
Partner
2-6-2 In which order must the condition exclusion groups be specified? 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 materialspecific 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.
SAP
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.
Use
Partner
Enter the following data:
© SAP AG
SCM521
6-24
2-7
Create a purchase order using the following data: Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor /Supplying Plant Known.
Vendor:
T-K521B##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Internal
Only
Enter the following date in the Header area of the purchase order:
Material
PO quantity
Deliv. Date
Plant
T-REK##
10
4 weeks from today
1000
T-REL##
10
4 weeks from today
1000
T-REM##
10
4 weeks from today
1000
Use
Partner
Enter the following data in the Item overview area of the purchase order:
Select the Conditions tab within the Item details area of the purchase order to answer steps 2-7-1 to 2-7-3. 2-7-1 Material T-REK##:
SAP Use
99.80 EUR (100.00 EUR gross price less 2 EUR RB00 discount). The vendor discount RL01 appears but is inactive and is not included in the calculation since there was a material-specific discount. 19.00 EUR (20.00 EUR gross price less 5% vendor discount RL01). There was no material-specific discount for this item, so the vendor discount applied. SAVE Purchase Order number _________________________________
© SAP AG
SCM521
6-25
Only
Internal
2-7-3 Material T-REM##:
Partner
2-7-2 Material T-REL##:
SAP
9.75 EUR (10.00 EUR 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.
Subsequent (End-of-Period Rebate) Settlement
Contents: ! Prerequisites for Rebate Arrangements ! Conditions in Rebate Arrangements ! Updating of Business Volumes ! Settlement and Extension of Rebates
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
7-1
Subsequent Settlement: Unit Objectives
At the conclusion of this unit, you will be able to: ! Define the process of subsequent settlement with regard to end-of-period rebates granted by vendors
Only
! Describe the process of cumulative business volume updating
Use
SAP AG 1999
SAP
SAP
Partner
Internal
! Create a rebate arrangement and carry out the related settlement
Only
Internal
Use
Partner
© SAP AG
SCM521
7-2
Subsequent Settlement: Business Scenario
! 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.
Partner
SAP
A volume-based incentive rebate is a partial refund of the total amount spent by one business partner on goods or services supplied by the other over a period. The party granting the rebate is termed the "condition granter" and the actual amount due may vary according to the volume of business done (value of spend) over the period. The basis for a volume rebate can be defined in a variety of ways (for example, vendor or vendor/vendor sub-range).
Only
Internal
"
SAP
Use
Use
Partner
Only
Internal
SAP AG 2002
© SAP AG
SCM521
7-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Subsequent Settlement: Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
7-4
End-of-Period Rebates: Overview Negotiations with vendor
From 01.01.
Create/maintain rebate arrangement From business volume of 20,000 upwards: 1 % volume rebate
Pur. order
Only
?
Partner
Cumulative busn. volume updates over period
12.31.
Busn. vol. comp.
Settlement acctg.
to 12.31
Credit memo
Use
SAP AG 2002
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.
Use
"
© SAP AG
SCM521
7-5
Only
A rebate arrangement, governing the payment of end-of-period rebates (or retrospective discounts), is an understanding with the "condition granter" (vendor, or entity granting the rebate) to which condition records are assigned. This ensures that stipulations involving conditions requiring end-ofperiod settlement can be made dependent on a variety of different criteria (e.g. vendor, article, settlement group) and handled on a variable basis. Different calculation rules and reference magnitudes can be used.
Partner
"
SAP
SAP
Invoice
Internal
Internal
Invoice
Prerequisites
Vendor Subseq. sett. BV comp. Reb. arrangement Arrang. type
Only Partner
Condition tables Condition types
SAP AG 2002
SAP
SAP
Settlement type Settlement calendar Arrangement calendar Condition type group
Settlement statement
Use
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 parameters, 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: As of SAP R/3 Enterprise Core 4.70 You cannot use settlement with a credit memo as a settlement document. Use vendor billing documents (debit-side settlement) instead. For more information, see the release notes - Converting Subsequent Settlement to Vendor Billing Documents. “Debit-side settlement” means that Purchasing issues one or more billing documents to the vendor (settlement documents are billing documents in Sales and Distribution).
© SAP AG
SCM521
7-6
Only
Internal
"
Partner
Use
Customizing: arrangement type
Internal
Cond. granter Currency Validity Busn. vol. comp. Conditions
Rebate arrangement
Purchase order Vendor A 10 pc mat. 1 Sett. acctg.
Purchase order Vendor A 10 pc mat. 1 @ 10.00
Goods receipt 10 pc mat. 1
Invoice Vendor A 10 pc mat. 1 @ 10.00
Accounting document GR/IR 100.00 Stock account 100.00
Partner
Conditions PB00 100.00 A001 0%
100.00
Accrual
Business volume update Period
Rebate arr.
Vendor
Pur. org.
...
99
A
1000
Prov. value
Busn. vol.
...
100.00
...
SAP AG 2002
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.
Only
"
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.
Use
"
Partner
SAP
SAP
Info record Vendor A Material 1 No s. acctg.
Use
Internal
Rebate arr. no. 99 Vendor A 01.01. - 12.31. Cond. type A001
Internal
Only
Cumulative Updating of Business Volumes
© SAP AG
SCM521
7-7
Comparison/Agreement of Business Volumes
Rebate arrangement Cond. granter BV comp.
BV comparison
Final settlement
Partner SAP
Mat. 1: 2450.00 Mat. 5: 3800.00 Mat. 8: 1620.00
Mat. 1: 2450.00 Mat. 5: 3800.00 Mat. 8: 1610.00
Agreed value 1615.00
Settlement basis SAP AG 2002
"
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.
© SAP AG
SCM521
7-8
Only
The business volume figures arrived at by the two parties for a rebate arrangement may differ, due to the vendor and customer assigning items to different accounting periods for example. The business volume comparison serves as the basis for the reconciliation of your and your business partner’s figures, the aim being to avoid having to make subsequent adjustments.
Partner
"
SAP
Use
Vendor‘s statistics
Use
Internal
Own business volume statistics
Internal
Only
Comparison of business volumes
Settlement
Validity period of rebate arrangement
One-time settlement
01.01.
12.31.
Partial settlement
Final settlement
Settlement document Scales taken into account
Blocking of affected condition records
Settlement list
Status of rebate arrangement: Settlement effected
Partner SAP
Settlement document Settlement list
Statistical apportionment of rebate income at plant level
Blocking of condition records Deactivation of business vol. updating Status of rebate arrangement: Final settlement effected for rebate arr. Statistical apportionment of rebate income at plant level
SAP AG 2002
"
"
"
"
© SAP AG
SCM521
7-9
Only
"
Partner
"
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.
SAP
Use
Final settlement
Use
Internal
Partial settlement
Internal
Only
Interim settlement
Extension of Rebate Arrangements
Arrangement calendar
Rebate arr. no. 10 Arrang. type: 1000 Arr. calendar: AJ Validity: 01.01.- 12.31.2000
01.01.01
12.31.01
01.01.01
Only
Business volume updates
!
Activation of busn. volume updating
Rebate arr. no. 34 01.01.02 SAP AG 2002
Business volume updates
12.31.02
"
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.
© SAP AG
SCM521
7-10
Only
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.
Partner
"
SAP
SAP
Partner
Extension of rebate arr.
Use
Use
Deactivation of busn. volume updating
Final settlement
Internal
Internal
12.31.2000
Retrospective Compilation of Statistics
Rebate arrangement 01.01. - 12.31.
01.01.
Purchase order GR, IR
Purchase order GR, IR
Purchase order GR, IR
Retrosp. compilation of statistics
Autom. updating of busn. vols.
Internal
Only
12.31
Retrospective compilation of statistics Vendor master rec.: subsequent settlement subseq. settlement index Report RMCENEUA/RMEBEIN3: Comp. of index structure S111 Report RWMBON08 (update run, version 000): comp. of info structures S015, S074 SAP AG 2002
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.
Use
"
© SAP AG
SCM521
7-11
Only
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.
Partner
"
SAP
Internal
Use
SAP
Partner
Purch. order item: settlement accounting
Subsequent Settlement: Unit Summary
You are now able to: ! Define the process of subsequent settlement with regard to end-of-period rebates granted by vendors
! Describe the process of cumulative business volume updating
Use
SAP AG 1999
SAP
SAP
Partner
Internal
Only
! Create a rebate arrangement and carry out the related settlement
Only
Internal
Use
Partner
© SAP AG
SCM521
7-12
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
Only
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-K521E## for purchasing organization IDES Deutschland (1000) and want to record this arrangement in the R/3 System. If necessary make the required setting changes Save the change Vendor T-K521E##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 EUR upwards. ______________________________________________________ 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 Can you maintain material T-REK## as the settlement material? Arrangement number: ____________________________________
© SAP AG
SCM521
7-13
Only
Internal
1-2-1 Which agreement type did you choose?
Partner
1-2
SAP
SAP
Partner
• Describe the process of cumulative business volume updating
Use
Use
Internal
• Create a rebate arrangement and carry out the related settlement
1-3
Create a purchase order using the following data: Vendor: Purchasing organization: Purchasing group: Delivery date: Plant: Storage location:
T-K521E## IDES Deutschland (1000) Z21 (SCM521) Today Hamburg (1000) Materiallager (0001)
Tax code:
0I
Order 60 pc of material T-REL## at a price of 100 EUR. 1-3-1 Was condition type A001 used to determine a rebate for this purchase order?
Partner
Post a goods receipt for the purchase order created in Step 1-3. Material document number: ________________________________________
1-5
You receive an invoice from vendor T-K521E## for the purchase order document created in step 1-3 for 6000 EUR at a tax code of 0I specifying today’s date as the document date and period baseline date. Enter the vendor’s invoice on the system. Invoice document number: ________________________________________
1-6
Was the invoice blocked for payment? If needed release the invoice.
1-7
Display the cumulative business volume update figures for your rebate arrangement.
Use
1-7-1 What is the figure for the scale basis? ________________________________________________________ Simulate the settlement accounting for your rebate arrangement for the end of the current year, using the report function. 1-8-1 What is the simulated value of the rebate for the subsequent settlement?
Only
Internal
________________________________________________________
Partner
Use
1-8
SAP
SAP
1-4
Internal
Only
Purchase order number: _________________________________________
© SAP AG
SCM521
7-14
Solutions Unit: Subsequent (End-of-Period Rebate) Settlement
1-1
Only
Logistics → Material Management → Purchasing → Master Data →Vendor → Purchasing → Change (Current) Enter the following data: Vendor
T-K521E##
Purchasing Organization
1000
Select Purchasing data
Internal
Check the Subsequent settlement indicator SAVE Vendor T-K521E##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 EUR upwards.
Use
Enter the agreement type 1000 Choose Enter
Internal
Enter the purchasing group Z21.
Only
Do not save until you have answered steps 1-2-1 to 1-2-4
1-2-1 Which agreement type did you choose? 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.
© SAP AG
SCM521
Partner
Logistics → Materials Management → Purchasing → Master Data → Subsequent Settlement → Vendor Rebate Arrangements → Rebate Arrangement → Create.
SAP
SAP
1-2
Use
Partner
You have entered into a volume-based, period-end incentive rebate arrangement with vendor T-K521E##and want to record this arrangement in the R/3 System.
7-15
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. Choose the Conditions radio button Choose the Vendor line by double clicking on the vendor line with the mouse. Vendor
Rebate
T-K521E##
.5%
Internal
Only
Enter the following data:
Select the Vendor line by choosing the box to the left of the line Select the Scales icon Scale Value
Rate
Blank
.5% (this will default)
5000
2.5%
SAP
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? Select the Vendor line by choosing the box to the left of the line
Internal
Choose the Period-spec. condit icon
Only
Yes, a condition been created for each month within the overall validity period of the rebate arrangement? Stay in the Create Rebate: Rebate (A001) Periodspecific conditions screen to process step 1-2-4
1-2-4 Can you maintain material T-REK## as the settlement material? Select from the menu toolbar Go to → Matl for settlement Enter material T-REK## in the Matl f. settl. field Yes, you maintain material T-REK## as the settlement material SAVE Arrangement number: ____________________________________
© SAP AG
SCM521
Partner
Use
Stay in the Create Rebate: Overview Rebate (A001) screen to process step 1-2-3
SAP
Select the Green arrow icon and go back to the Create Rebates: Overview Rebates (A001) screen
Use
Partner
Enter the following data:
7-16
1-3
Create a purchase order using the following data: Vendor: Purchasing organization: Purchasing group: Delivery date: Plant: Storage location:
T-K521E## IDES Deutschland (1000) Z21 (SCM521) Today Hamburg (1000) Materiallager (0001)
Tax code:
0I
Order 60 pc of material T-REL## at a price of 100 EUR.
Internal
Only
Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known
Vendor:
T-K521E##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
Use
Partner
Enter the following date in the Header area of the purchase order:
PO quantity
Net price
Delivery date
Plant
T-REL##
60 pc
100 EUR
Today’s date
1000
Enter the following date on the Invoice tab within the Item details area of the purchase order:
Internal
Tax code
0I
1-3-1 Was condition type A001 used to determine a rebate for this purchase order?
Only
Select the Condition tab from within the item details area of the purchase order Yes, condition type A001 (volume-based incentive rebate) was used. SAVE Purchase order number: __________________________________________
© SAP AG
SCM521
Partner
Use
Material
SAP
SAP
Enter the following data in the Item overview area of the purchase order:
7-17
1-4
Post a goods receipt for the purchase order created in Step 1-3. Logistics → Materials Management → Inventory Management → Goods Movement → Goods Receipt → For Purchase Order → PO Number Known. Enter the purchase order number Choose the Execute icon. Select item OK Select the Save icon Material document number: ________________________________________ You receive an invoice from vendor T-K521E## for the purchase order document created in step 1-3 for 6000 EUR at a tax code of 0I specifying today’s date as the document date and period baseline date. Enter the vendor’s invoice on the system. Logistics → Materials Management → Logistics Invoice Verification → Document Entry → Enter Invoice.
SAP
Today’s date
Posting date
Today’s date (this will default)
Amount
6000
Tax amount
Leave blank and change the default tax to 0I
SAP
Invoice date
Use
Partner
Enter the following date in the Basic date tab of the invoice:
Enter the following date in the Payment tab of the invoice: BaselineDt
Use
The purchase order number created in step 1-3 Enter to verify the data Select the Post icon Invoice document number: ________________________________________ 1-6
Was the invoice blocked for payment? If needed release the invoice. Logistics → Materials Management → Logistics Invoice Verification → Further Processing → Release Blocked Invoices Enter the following data: Company code
1000
Vendor
T-K521E##
Choose the Execute icon If your invoice is listed, select the blocking reason for your invoice and choose Cancel blocking reason. SAVE © SAP AG
SCM521
7-18
Only
If you get a warning message about exceptions, choose Enter to accept it.
Partner
Internal
Today’s date
Enter the following date in the PO reference tab of the invoice:
Internal
Only
1-5
1-7
Display the cumulative business volume update figures for your rebate arrangement. Logistics → Materials Management → Purchasing Master Data → Subsequent Settlement → Vendor Rebate Arrangements→ List Displays → Business Volume Data. Enter the arrangement number from step 1-2-4 Choose the Execute icon 1-7-1 What is the figure for the scale basis? 6000 EUR Simulate the settlement accounting for your rebate arrangement for the end of the current year, using the report function.
Partner
Logistics → Materials Management → Purchasing Master Data → Subsequent Settlement → Vendor Rebate Arrangements → Rebate Arrangement → Create Settlement Document → Via Report
Use
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.
SAP
Enter your rebate arrangement number and the settlement and billing (posting) dates.
SAP
Internal
Only
1-8
Under Control data: settlement run, select Simulate. Choose Execute.
Partner
Use
Choose Yes at the Confirmation prompt. 1-8-1 What is the simulated value of the rebate for the subsequent settlement?
Only
Internal
A rebate value of 30 EUR.
© SAP AG
SCM521
7-19
Customizing
Contents: ! Calculation Schemas ! Condition Types ! Access Sequences ! Routines and Adjusting the System
Use
SAP AG 1999
SAP
SAP
Partner
Internal
Only
! Condition Tables
Only
Internal
Use
Partner
© SAP AG
SCM521
8-1
Customizing: Unit Objectives
At the conclusion of this unit, you will be able to: ! Outline the ways in which the price determination process can be influenced through Customizing
Only
! Review the most important control parameters for calculation schemas, condition types and access sequences
Use
SAP AG 1999
SAP
SAP
Partner
Internal
! Explain when you have to work with formulas and requirements of your own or carry out system modifications
Only
Internal
Use
Partner
© SAP AG
SCM521
8-2
Customizing: Business Scenario
! 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.
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
8-3
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Customizing: Overview Diagram
Only
Internal
Use
Partner
© SAP AG
SCM521
8-4
Overview Customizing MM ❍ ❍ ❍ ❍
Maintain condition table(s) Maintain access sequence(s) Maintain condition type(s) Maintain calculation schemas
Customizing SD
Only
System adjustment
Partner
❍ ❍ ❍ ❍
Extend condition structures by adding new fields Supply new fields from documents Activate user exits Extend catalog of allowed fields
Use
SAP AG 2002
"
SAP
The Customizing functionality for Purchasing enables you to:
Partner
$ Create, change, and display access sequences
Use
SAP
Define requirements Define formulas
Internal
❍ ❍
$ Create, change, and display condition types $ Set upper and lower limits for the conditions belonging to a condition type
Internal
$ Define exclusion indicators for condition exclusion $ Create, change, and display calculation schemas
Only
$ Create schema groups for purchasing organizations or vendors, and assign them to purchasing organizations $ Define the process of determining the calculation schema $ Define transaction/event keys $ Define condition exclusion groups and condition exclusion procedures $ Create, change, and display condition tables $ Extend the field catalog for condition tables $ Define Copy Control for Conditions "
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
SCM521
8-5
Customizing: Calculation Schema
Step
Count. C.ty.
1
10
From
To
Man.
Mand. Stat.
PB00
Print
Subtot.
X
1
...
Accr.
Basis for percentage discounts/surcharges
Mandatory Statistical Print indicator
Transaction/event key for account determination SAP AG 2002
"
SAP
SAP
Partner
Subtotaling of condition values
Use
The calculation schema (pricing procedure) includes the following information: $ Step: sequence of conditions within the calculation schema $ Cntr: sequence of conditions within a Step (counter) $ CTyp: which condition types are to be taken into account (Condition Type) $ To: percentage discounts or surcharges are calculated based on preceding steps up to this step (To Reference Step), can be used with the from step $ Man: whether conditions of a certain type are determined automatically or have to be entered manually
Only
Internal
$ Fro: percentage discounts or surcharges are calculated based on this step (From reference Step)
$ Mdt: whether the condition type is mandatory $ Stat: whether a condition is taken into account in the net price calculation (Statistical indicator) $ Print: whether and how condition lines are to be printed on documents $ Subto: whether and in which fields condition values or subtotals are to be stored for further processing (Subtotal). $ Reqt: controls whether a prerequisite must be fulfilled in order for a condition type to be included/excluded from the price determination process (Requirement) $ AltCTy: Alternative formula to the formula in the standard system that determines a condition. (Alternative calculation type) $ AltCBV: Formula for determining the condition basis as an alternative to the standard. $ ActKy: The transaction/event key to which the G/L account postings will be made $ Accr: Key which identifies various types of G/L Accounts for accruals or provisions © SAP AG
SCM521
Partner
Use
Internal
Only
Autom. determination/ manual maintenance
8-6
Customizing: Condition Type
Condition type ZXYZ Control data 1
Access Sequence
Cond. class Calculation type: Condition cat.:
+/- sign
Group Conditions Group Conditions
Only
Item condition
Partner
Master data Pricing procedure
... ...
Scale type
Control data 2 Accrual
... ...
SAP AG 2002
"
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
SCM521
8-7
Only
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.
Partner
"
SAP
SAP
Header condition
Manual entry
Use
Use
Internal
Internal
...
Change options
Scales Scale basis
...
Customizing: Access Sequences
Access sequence 0002 Gross price
Accesses Requirement
SNo. Tab. Description
Only
Fields
Partner SAP
36 35
Condition
Doc. structure
Doc. field
LIFNR MATNR EKORG WERKS ESOKZ
KOMK KOMP KOMK KOMP KOMP
LIFNR MATNR EKORG WERKS ESOKZ
Direct value source
SAP AG 2002
SAP
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
SCM521
8-8
Only
"
Partner
Use
Agreement item, plant-dependent Contract item Plant info record per order unit Material info rec., plant-dependent
Use
Internal
68 16 67 17
Internal
10 15 20 25 ...
Excl.
Customizing: Condition Tables
With validity period
Table 999
Technical view
Only
Purchasing doc. Choose
Purchasing doc. ...
Activate
Partner SAP
Order unit Company code Purch. organization
Table A999 activated Reports and screen flagged for generation SAP AG 2002
"
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.
© SAP AG
SCM521
Only
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.
Partner
"
SAP
Use
Purch. organization
Use
Internal
Field catalog
Internal
Line Text Field name EVRTN ...
Selected fields
8-9
Routines: Formulas and Requirements
Step
Count. C.ty.
1
2
PBXX
...
Reqt.
Calc. for.
Bas. for.
...
6
35
17
Source text
ABAP 14: Editor Program LV61A035 FORM KOBED_035. SY-SUBRC = 4. CHECK KOMP-NO017 EQ SPACE. SY-SUBRC = 0. ENDFORM.
Partner SAP
25
FORM KOBEV _035. SY-SUBRC = 0. ENDFORM.
SAP AG 2002
SAP
"
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 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.
© SAP AG
SCM521
8-10
Only
$ Condition basis – You can assign a formula for calculating the condition basis in the Base formula field in Customizing for the calculation schema.
Partner
Use
Reqt.
Use
Internal
S .no. Tab
Internal
Only
Access sequence
Adjusting the System
1 Extend condition structure
Communication structure KOMG .. . KOMPAZ INCLUDE ... KOMKAZ INCLUDE
Partner SAP
***
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 ...
INCLUDE ZXM06U14.
MOVE I_KOMK TO E_KOMK. MOVE I_EKKO-EKGRP TO E_KOMK_ZZEKGRP.
SAP AG 2002
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:
Partner
"
SAP
Use
2 Supply new field from document
Use
$ 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.
© SAP AG
SCM521
8-11
Only
Internal
Data element EKGRP
Internal
Only
Field name ZZEKGRP
Customizing: Unit Summary
You are now able to: ! Outline the ways in which the price determination process can be influenced through Customizing
Only
! Review the most important control parameters for calculation schemas, condition types and access sequences
Use
SAP AG 1999
SAP
SAP
Partner
Internal
! Explain when you have to work with formulas and requirements of your own or carry out system modifications
Only
Internal
Use
Partner
© SAP AG
SCM521
8-12
Exercises Unit: Customizing
At the conclusion of this exercise, you will be able to:
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.
SAP
SAP
1-1-1 Condition Table: _________________________________________________________ _________________________________________________________
Use
Partner
1-1-2 Access Sequence: _________________________________________________________ _________________________________________________________
Internal
1-1-3 Condition Type: _________________________________________________________
Only
_________________________________________________________ 1-1-4 Calculation Schema: _________________________________________________________ _________________________________________________________ 1-1-5 Condition Records: _________________________________________________________ _________________________________________________________ 1-1-6 Condition Group: _________________________________________________________ _________________________________________________________
© SAP AG
SCM521
Use
Partner
Internal
Only
• Create a working price determination process by building and linking all the components for conditions and prices
8-13
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. ____________________________________________________________ ____________________________________________________________
Partner
1-4
Access Sequence: Create and save a new access sequence ZS## description Access sequence ## include your new condition table 7##.
1-5
Condition type: Using condition type RGR0 as a reference, create and save a new condition type ZG## description Condition type ##. Link condition type ZG## to your new 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-6
Calculation schema: Using the existing calculation schema RM0000, create and save a new calculation schema called Z##CGR description Calculation schema ##. 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. Replace condition type RGR0 in your new calculation schema Z##CGR with your new condition type ZG##. .
Only
Internal
1-7
Partner
Use
SAP
SAP
Condition Table: Using condition table 45 as the reference, create and save a new condition table named 7## description Vendor Condition Group ##. The new condition table 7## should include the vendor, purchasing organization, and condition group fields.
Use
1-3
Internal
Only
____________________________________________________________
© SAP AG
SCM521
8-14
1-8
Vender Schema group: Create a new vendor schema group. On the table below, find your group number; using the schema group code create a new vendor schema group:
C
04
D
05
E
Only
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-9
Determination of Calculation Schema: Link your new vendor schema group created in step 1-8 to your calculation schema Z##CGR.
1-10
Changing your master data: 1-10-1 Vendor T-K521D##in purchasing organization 1000 will be using the new vendor schema group created in step 1-8. Make the required changes to the vendor master record. 1-10-2 Change the existing information record for material T-REM##, vendor TK521D##, purchasing organization 1000, and plant 1000 to reflect the new group conditions. 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 EUR.
© SAP AG
SCM521
8-15
Only
Internal
Use
03
Partner
B
SAP
02
Use
A
Internal
01
Partner
Schema group
SAP
Group number
1-11
Condition records: Create and save a condition record for your new condition type ZG##. Use the following data: Purchasing Organization
1000
Vendor
T-K521D##
Rate Discount
10% per piece, starting with 1000 pieces, the 12%
1-11-1 What validity period defaults? Why? _________________________________________________________ _________________________________________________________ Purchase Group
Z21
Purchasing Org:
1000
Vendor:
T-K521D##
Delivery Date:
In one week
Ship to:
Plant 1000
Material:
T-REM##
Qty:
1000 pc
Use
Partner
Test: Create a purchase order using the following data:
Internal
Only
1-12
SAP
SAP
Verify your new condition type ZG## was used.
Partner
Use
If the item Condition tab does not show condition type ZG## with the proper values, choose Analysis to analyze the problem.
Only
Internal
Purchase order number: _____________________________
© SAP AG
SCM521
8-16
Solutions Unit: Customizing
1-1
SCM521
8-17
Only Partner SAP Use Internal
Only
© SAP AG
Partner
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).
SAP
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.
Use
1-2
Internal
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-3
Condition Table: Using condition table 45 as the reference, create and save a new condition table named 7## description Vendor Condition Group ##. The new condition table 7## should include the vendor, purchasing organization, and condition group fields. Tools → Customizing → IMG → Edit Project Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Maintain Condition Table Choose Create Condition Table Table
7##
Table
45
Internal
Only
Enter the following data:
Enter
Partner
Choose from the menu toolbar Edit → Propose text Change the table description to Vendor Condition Group ##. Choose the Generate icon to generate the new table.
Use
Choose Local object. Enter Access Sequence: Create and save a new access sequence ZS## description Access sequence ## include your new condition table 7##. Tools → Customizing→IMG → Edit Project
Partner
Use
SAP
1-4
SAP
The table will be generated
Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Access Sequences
Internal
Choose New Entries. Enter ZS## and a description Access sequence ##. Select your access sequence ZS## and choose Accesses.
Only
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. Select the Save icon
© SAP AG
SCM521
8-18
1-5
Condition type: Using condition type RGR0 as a reference, create and save a new condition type ZG## description Condition type ##. Link condition type ZG## to your new 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. Tools → Customizing→IMG → Edit Project Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Choose Define Condition Type Select condition type RGR0
Only
Internal
Choose the copy icon Change the condit.type to ZG## and the description to Condition type ## Enter the Valid to: 2 (end of current year) Enter Save
SAP
Calculation schema: Using the existing calculation schema RM0000, create and save a new calculation schema called Z##CGR description Calculation schema ##. Tools → Customizing→IMG → Edit Project
SAP
1-6
Use
Partner
Change the Scale basis to: C (Quantity scale)
Choose SAP Reference IMG radio button
Use
Partner
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select RM0000 Choose the copy icon
Internal
Change the Procedure name to Z##CGR and the description to Calculation schema ##. Enter and Choose Copy all
Only
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. SAVE
© SAP AG
SCM521
8-19
1-7
Replace condition type RGR0 in your new calculation schema Z##CGR with your new condition type ZG##. . Tools → Customizing→IMG → Edit Project Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select schema Z##GCR and choose the Control data folder. Find RGR0 in the list and overtype condition type RGR0 with condition type ZG## SAVE Vender Schema group: Create a new vendor schema group. On the table below, find your group number; using the schema group code create a new vendor schema group:
SAP Use
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
Only
A
Partner
01
SAP
Internal
Schema group
Use
Partner
Group number
Tools → Customizing→IMG → Edit Project Choose SAP Reference IMG radio button
© SAP AG
SCM521
Internal
Only
1-8
8-20
Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Group Choose Schema Groups: Vendor Select the New Entries radio button Enter the schema group from the list above for you group number and a description Group ## SAVE 1-9
Determination of Calculation Schema: Link your new vendor schema group created in step 1-8 to your calculation schema Z##CGR. Tools → Customizing→IMG → Edit Project
Only
Internal
Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Determination Leave Schema gp. POrg blank. Enter only your vendor schema group and your calculation schema Z##GCR. SAVE 1-10
Changing your master data:
SAP
Logistics-> Materials Management-> Purchasing → Vendor → Purchasing → Change (Current)
Partner
Select Purchasing data.
Use
SAP
1-10-1 Vendor T-K521D##in purchasing organization 1000 will be using the new vendor schema group created in step 1-8. Make the required changes to the vendor master record.
Use
Partner
Choose Determine Calculation Schema for Standard Purchase Orders
Enter the Schema group, vendor
Only
Internal
SAVE
© SAP AG
SCM521
8-21
1-10-2 Change the existing information record for material T-REM##, vendor TK521D##, purchasing organization 1000, and plant 1000 to reflect the new group conditions. 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 EUR. Logistics → Materials Management → Purchasing → Master Data → Info Record → Change
Partner
Vendor
T-K521D##
Material
T-REM##
Purchasing Org
1000
Plant
1000
Internal
Only
Enter the following data:
Enter Select the Purch. Organization Data 1 radio button
Use
Condition group
00##
Standard qty
1000
SAP
SAP
Enter the following date:
Select the Conditions radio button Double click in the validity dates
Use
1-11
21 EUR
Condition records: Create and save a condition record for your new condition type ZG##. Use the following data: Purchasing Organization
1000
Vendor
T-K521D##
Rate
10% per piece, starting with 1000 pieces, the Discount 12%
Only
Internal
Gross price
Logistics-> Materials Management → Purchasing → Master Data → Conditions → Other → Create Enter Condition type
ZG##
Enter the vendor
T-K521D##
Enter purchasing org
1000
Enter the rate
10% per piece, starting with 1000 pieces
Enter the discount of
12%
SAVE © SAP AG
SCM521
Partner
Enter the following data:
8-22
1-11-1 What validity period defaults? Why? The validity period starts today through to the last day of the current year. You specified this when you created condition type ZG##. Test: Create a purchase order using the following data: Purchase Group
Z21
Purchasing Org:
1000
Vendor:
T-K521D##
Delivery Date:
In one week
Ship to:
Plant 1000
Material:
T-REM##
Qty:
1000 pc
Verify your new condition type ZG## was used.
Partner
Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Know
SAP
T-K521D##
Purchase org:
1000
Purch. Group
Z21
Company Code:
1000
SAP
Vendor:
Use
Enter the following date in the Header area of the purchase order:
Use
PO quantity
Deliv. Date
Plant
T-REM##
1000
1 week from today 1000
Choose the Conditions tab within the Item details area of the purchase order and verify condition type ZG## was used. If the item Condition tab does not show condition type ZG## with the proper values, choose Analysis to analyze the problem.
SAVE Purchase order number: _____________________________
SCM521
8-23
Only
Internal
Material
Partner
Enter the following data in the Item overview area of the purchase order:
© SAP AG
Internal
Only
1-12
Elements of the Condition Technique
Subsequent (Endof-Period Rebate) Settlement
Price Determination
Customizing
Header and Group Conditions
Conclusion
Maintaining Conditions
Use
SAP AG 1999
SAP
SAP
Partner
Course Overview
Special Condition Types and Special Functions *
Internal
Only
Conclusion
Only
Internal
Use
Partner
© SAP AG
SCM521
9-1
Course Objectives
You are now able to: ! Outline the various elements of the condition
technique and define how they interact ! Maintain conditions at different levels
Only
Internal
! Describe how the process of price determination
works in the system ! Recognize the special condition types that you
Partner
can use in price determination ! Define the subsequent settlement process
Use
! Create condition types and calculation schemas,
and customize the price determination process
SAP
SAP
SAP AG 2001
Only
Internal
Use
Partner
© SAP AG
SCM521
9-2
Recommended Follow-up Courses
! SCM550 Cross-Functional Customizing in MM
Use
Partner
Only
Internal
SAP
SAP
SAP AG 2002
Only
Internal
Use
Partner
© SAP AG
SCM521
9-3
Recommended Follow-up Activities
! Perform the exercises using IDES data or your own data ! Read IMG documentation
Internal
! Read release notes
Use
Partner
Only
! Read on-line documentation
SAP
SAP
SAP AG 2001
Only
Internal
Use
Partner
© SAP AG
SCM521
9-4
Appendix
Contents: ! Menu Paths
Use SAP
SAP
Partner
Only
Internal
SAP AG 1999
Only
Internal
Use
Partner
© SAP AG
SCM521
10-1
Frequently-used Menu Paths Activity
Menu Path
Partner SAP Use
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 or Involving Contracts
Partner
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 or Create Worklist
© SAP AG
SCM521
Only
Internal
Contract
SAP
SAP menu→ Logistics→ Materials Management → Purchasing→ Master Data→ Info Record→ Create
Use
Info Record
Internal
Only
Maintenance of Time-dependent Conditions:
10-2
Partner SAP
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 or Via Report
Basic Materials Management Functions: SAP menu→ Logistics→ Materials Management→ Material Master→ Material→ Create(General)→ Immediately
Vendor Master Record
SAP menu→ Logistics→ Materials Management→ Purchasing→ Master Data→ Vendor→ Purchasing or Central→ Create or Change or 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 Blocked Invoices
© SAP AG
SCM521
10-3
Only
Material Master Record
Partner
Use
Business Volume
SAP
Internal
SAP menu→ Logistics→ Materials Management→ Purchasing→ Master Data→ Subsequent Settlement → Vendor Rebate Arrangements → Rebate Arrangement→ Create
Use
Rebate Arrangement
Internal
Only
Subsequent (End-of Period Rebate) Settlement:
Customizing: All menu paths begin with: SAP menu→ Tools→ Customizing→ IMG→ Edit Project Choose SAP Reference IMG
Partner SAP Use Internal
Calculation Schemas
Conditions→ Define Price Determination Process→ Define Calculation Schema
Schema Groups
Conditions→ Define Price Determination Process→ Define Schema Group 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 Choose Condition Exclusion Groups
Condition Tables
Conditions→ Define Price Determination Process→ Maintain Condition Table Choose Create or Change or 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 Scopeof-List Parameters
Condition Index
Conditions → Configure Condition Index…
© SAP AG
SCM521
Only
Conditions→ Define Price Determination Process→ Define Condition Types Choose Define Condition Type
Partner
Condition Types
SAP
Conditions→ Define Price Determination Process→ Define Access Sequences
Use
Access Sequences
Internal
Only
Materials Management→Purchasing
10-4
View more...
Comments
