Download IRT320 - Pricing and Promotions...
IRT 320Inkasso/Exkasso Preise und Aktionen FS310
IRT 320
Pricing and Promotions
THE BEST-RUN BUSINESSES RUN SAP
SAP AG©2003 SAP AG 2003
System R/3 2003/Q3 50063445
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
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 AG 2003
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.
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Prerequisites
Required: IRT100 Recommended: IRT310
Participants should have a good understanding of the areas of purchasing and/or sales, and ideally also of customizing.
SAP AG 1999
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Target Group
Participants Project team members Administration/IT employees Consultants
Duration: 3 Days
SAP AG 1999
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview
Contents: z Course Goals z Course Objectives z Course Content z Course Overview Diagram z Main Business Scenario
SAP AG 2003
© SAP AG
IRT320
1-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Goals
This course will prepare you to: z Understand the special features of the condition
technique in SAP Retail z Create a promotion with follow-on activities
SAP AG 2003
© SAP AG
IRT320
1-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Objectives
At the conclusion of this course, you will be able to: z Implement the various elements of the condition
technique z Use the special features of conditions for sales
and purchase prices z Understand price determination in the system z Plan, create, and perform a promotion, including
all associated follow-on activities
SAP AG 2003
© SAP AG
IRT320
1-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Content
Preface Unit 1
Course Overview
Unit 4
Pricing
Unit 2
Elements of the Condition Technique
Unit 5
Promotion
Unit 6
Inventory Management and Valuation
Unit 3
Conditions in Purchasing
SAP AG 2003
© SAP AG
IRT320
1-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Diagram
1 2 3
Course Overview
Elements of the Condition Technique Conditions in Purchasing
4 5 6
Pricing
Promotion
Inventory Management and Valuation
SAP AG 2003
© SAP AG
IRT320
1-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Main Business Scenario
z Your company has decided to implement SAP
Retail, and you are responsible for maintaining purchase price conditions, calculating sales prices, and planning promotions.
SAP AG 2003
© SAP AG
IRT320
1-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Elements of the Condition Technique
SAP AG 2003
© SAP AG
IRT320
2-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit Objectives
At the conclusion of this unit, you will be able to: Maintain condition records Use the functions of the calculation schema Explain the central role of the condition types and their control fields Describe access sequences and their data retention levels
SAP AG 2003
© SAP AG
IRT320
2-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Business Scenario
The condition technique is used to determine prices in SAP Retail. It is based on conditions, which are described by condition types. Information is stored in condition records and conditions. Access sequences and calculation schemas are also a key part of this functionality.
SAP AG 2003
© SAP AG
IRT320
2-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Diagram
1 2 3
Course Overview Elements of the Condition Technique Conditions in Purchasing
4 5 6
Pricing
Promotion
Inventory Management and Valuation
SAP AG 2003
© SAP AG
IRT320
2-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Conditions
Purchase order
Vendor Vendor
Article Vendor Price Quantity
R100000 R3000 USD 1.00 1000 pc
Head Head office office
Final price USD 1,000
SAP AG 2003
© SAP AG
IRT320
2-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Conditions 12
Purchase order
Vendor Vendor
Article R100000 Vendor R3000 Price USD 1.00 Quantity 1000 pc Discount 2%
Head Head office office
Final price USD 980
Condition type RA01 = % discount on gross price SAP AG 2003
© SAP AG
IRT320
2-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Type Customizing settings
Condition Type
Possible settings Condition class
• Prices
• Control data 1 • Group condition
• Markups/downs
• Change options .
• Freight
• Scales • ...
• ...
• ...
Condition category Group condition Group condition routine Header condition Amount/percentage
• Master data
• Cash discount
Calculation type
Delete Valid from Valid to Scale basis Scale type Scale formula
• ...
... ... SAP AG 2003
Condition types are defined generally using the condition class, and in detail using the condition category. The calculation type defines how the system calculates the condition value. A markup or markdown could be a percentage of the gross price, a fixed amount, or a quantity-dependent amount, for example. The plus/minus sign indicates whether the condition is treated as a positive or negative amount. Negative amounts are markdowns, positive amounts are markups. Scale bases for scales are also dependent on the condition type. Scales can relate to a quantity or a value, for example. An access sequence can be assigned to a condition type. The access sequence is a search strategy that defines the sequence in which the system searches through condition tables looking for relevant entries for a condition type. In the standard sequence, an access sequence is not assigned to the condition types for surcharges and discounts (RA00, RA01 and so on), because they are maintained as supplementary conditions for the gross price (PB00). You can define your own condition types.
© SAP AG
IRT320
2-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Time-Dependent Conditions General conditions Vendor Condition group Article type Incoterms Invoicing party Other
Piece % Conditions
USD Purch. data in the article Price 1 Jan. 1
£ $
€
Price 2 July 1
Dec. 31
Purchasing organization
Maintenance option
Site
SAP AG 2003
Conditions in purchasing info records are always time-dependent. Conditions in purchase orders are not always time-dependent. Time-dependent conditions can apply to specific sites, or to all sites in a purchasing organization. In addition to time-dependent prices that are valid for specific purchasing data for the article (purchasing view in article maintenance), time-dependent conditions relating to more general price agreements can be defined (general conditions). Time-dependent conditions are limited to a particular validity period. No subtotals (net price, effective price) are formed for time-dependent conditions. Valid time-dependent conditions from purchasing info records are used as default values in purchase orders.
© SAP AG
IRT320
2-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Header Conditions, Group Conditions, Item Conditions Purch. order
Per PO: 20.00 freight surcharge Item Article no. Merch. categ.
Special discount for art. R100004 1% for purchase of 10 pieces or more
Qty
Price
10
R100000
R1111
100
81.00
20
R100003
R1112
50
72.00
40
R100004
R1113
100
63.00
Vendor subrange: 5% on a total of 500.00
SAP AG 2003
Item conditions are conditions that relate to individual articles. Some standard condition types can only be used as item conditions, others can only be used as header conditions, and some can be used as both header and item conditions. How a condition type can be used is controlled using the Header condition and Item condition indicators in Customizing for the condition type. Automatic price determination is carried out for header conditions. As a result, you cannot assign an access sequence to a header condition (unless it is also defined as an item condition), and cannot create condition records for it. A condition type can be defined as a group condition in Customizing. A group condition relates to several items of a document.
© SAP AG
IRT320
2-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Header Conditions
Header condition
Header condition
ZB00 Abs. markup 10.00
HB00 Header markup 180.00
ZB00 Group condition =
HB00 Group condition =
ZB00 abs. markup 10.00
180.00 in total1
Purchase order Item Article
Purchase order Qty
Price
Item Article
Qty
Price
10
1 + markup
1
300.00 10.00
10
1 + markup
1
300.00 120.00
20
2 + markup
1
100.00 10.00
20
2 + markup
1
100.00 40.00
30
3 + markup
1
50.00 10.00
30
3 + markup
1
50.00 20.00
SAP AG 2003
Header conditions apply for all items in a document and are automatically applied to all document items. A header condition can be a percentage or a fixed amount. If you define a header condition as a percentage markup or markdown, the defined percentage applies automatically for all document items. If you define a header condition as a fixed amount, the condition value of the header condition can be assigned for each article, or split up over all items. The condition value is split up proportionally over the document items if the condition type is defined as a group condition in Customizing. If the condition type is not defined as a group condition, the condition value of the header condition is assigned to each item. In this case, the header condition is used to make data intput easier. In the standard system, an absolute header condition is appied to the individual items on a value basis. However, in Customizing you can define that the value is applied on the basis of the weight or volume of the individual items. The basis for used to apply conditions to items is defined in the Basic formula field in the calculation schema.
© SAP AG
IRT320
2-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Group Conditions and Scales Customizing
Collective PO Store
Item
Article
Qty
Price
10
1
80
100.00
1
20
1
40
100.00
2
Qty
Condition type PB00 Group cond. =
120 Info record conditions Article 1
Collective PO Item
Article
Qty
Price
Store
10
1
80
99.00
1
20
1
40
99.00
2
Qty
PB00
Gross price
as of
1 pc 100.00
as of 100 pc
99.00
as of 900 pc
90.00
120
SAP AG 2003
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 item values (price, order quantities, weights or volume) of the items in question are added together, and the result is used as the condition basis. As a result, when calculating scales, more advantageous values can be obtained than would be the case if items were considered individually. The items are grouped together using the key of the condition record for the group condition, or a group condition routine assigned to the condition type in Customizing. As long as the document has not already been saved or checked, price determination is carried out for each document item and the condition basis determined. The item values are not cumulated until the document is saved or checked. The scale amount is then determined on the basis of the cumulated item values. On the header condition screen, you can explicitly trigger the determination of the scale amount based on the cumulated item values by activating the conditions. You can therefore determine the lowest scale value before saving the document by either activating the condition or checking the document.
© SAP AG
IRT320
2-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Technical Information
The header information of the document is stored in internal structure KOMK. MANDT
KNUMV
IDES
1234
VKORG R300
VTWEG R1
... ...
KOMK
The item information of the document is stored in internal structure KOMP. KPOSN
MATNR
WERKS
WKREG
...
20
1
2
SO
...
KOMP
SAP AG 2003
During internal processing, the header information is stored in the fields of structure KOMK. The fields in KOMK are called "header fields". The information in KOMK is valid for the whole document. During purchase order processing, the item information is stored in the fields of structure KOMP. These fields are called "item fields". The information in structure KOMP is only valid for a single line. The pricing components or condition types are either entered manually or calculated using site-specific formulae. These formulae take account of customers, manufacturing costs, quantity-based discounts, and so on. This information is stored in the structures KOMK and KOMP.
© SAP AG
IRT320
2-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Records
Level at which the condition is defined
Condition Condition type type
::
RA01 RA01 Vendor Vendor discount discount % %
Purch. Purch. organization organization
::
R300 R300
Vendor Vendor
::
R3000 R3000
Article Article
::
R100000 R100000
Period Period 11 March March 11 -- March March 30 30 $$ 1000 1000 $$ 2000 2000 $$ 3000 3000
1.0 1.0 -- % % 2.0 2.0 -- % % 3.2 3.2 -- % %
Lower Lower limit: limit: 5.0 5.0 -- % % Upper limit: 0.0 Upper limit: 0.0 -- % %
Period Period 22 May May 11 -- May May 31 31 $$ 1000 1000 $$ 2000 2000 $$ 3000 3000
1.5 1.5 -- % % 2.5 2.5 -- % % 4.0 4.0 -- % %
Lower Lower limit: limit: 5.0 5.0 -- % % Upper limit: 0.0 Upper limit: 0.0 -- % %
SAP AG 2003
© SAP AG
IRT320
2-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Records and Condition Tables
Condition table A017 (info record with site) Cond. type RA01
Vendor
Article
POrg
Site
...
Cond. rec. no.
A
1
R300
R300
...
1234
Condition table A018 (info record without site) Cond. type RA01
Vendor
Article
POrg
...
Cond. rec. no.
A
1
R300
...
4321
Table KONP (item conditions) Cond. rec. no. 1234
Cond. type
...
Cond. amount
...
RA01
...
2,00
...
4321
RA01
...
4,00
...
SAP AG 2003
Conditions are stored in the system as condition records. Condition tables refer to condition records. Condition tables enable you to vary the key of condition records. Condition tables with the following keys exist, for example Vendor, article, purchasing organization, info record category Vendor, article, purchasing organization, site, info record category Vendor, article, purchasing organization, info record category, order unit Purchasing document, item, site Entries in condition tables consist of the key and the data. The data contains the number of the condition record. Condition records are stored in the following tables, for example: KONP (time-dependent item conditions) KONH (header conditions) KONM (quantity scales) KONW (value scales).
© SAP AG
IRT320
2-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Table Customizing
With validity
Table 999
Technical view Line Text Field name EVRTN ...
Selected fields
Field catalog
Purch. organization
Order unit Company code Purch. organization
Purch. document Select
Purch. document ...
Activate
Table A999 was activated Reports and screen flagged for generation SAP AG 2003
You can create your own condition tables. The name of the table must be a number between 501 and 999. If you do not enter a name, the system automatically assigns a sequential number. Before you create your own condition tables, you should determine the extent to which you can use the standard condition tables. If you want to create a new condition table, you must first check whether the fields in the field catalog meet your requirements. You may have to add fields to the field catalog. You can include any of the fields of communication structures KOMK, KOMP and KOMG in the field catalog. If you want to maintain time-dependent conditions, you must define your new condition table as a condition table with a validity period. You select the key fields you want to include in your condition table from the list of permitted fields (fields in the field catalog). On the Technical view screen, you can modify the layout of the condition maintenance screen using the fields Line and Text. Finally, you generate your condition table. When you generate the condition table, it is activated, and the reports and screens for condition maintenance are flagged for generation. You should not change the standard condition tables.
© SAP AG
IRT320
2-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Calculation Schema
Step
Counter Cond.type
Description
From to
Man.
Stat
...
Gross price
...
Gross value
...
1
1
3
0
10
1
RA01
% discount on gross price
3
10
9
ZA01
% markup on gross price
3
20
0
...
...
...
31
1
FRA1
Freight %
20
X
...
35
1
SKTO
Cash discount
20
X
...
40
0
PB00
... ...
X
...
Net value incl. discount ...
Effective price
...
...
...
...
SAP AG 2003
The calculation schema is used in price determination. It groups together all condition types that are involved in price determination. The calculation schema defines: which condition types are allowed for which condition types conditions can be automatically adopted ('Man.' indicator) which condition types are used to calculate net prices ('Stat' indicator) the sequence in which the condition types are used when calculating net and effective prices the condition types for which subtotals are calculated what requirements must be met to ensure a certain condition type is considered In addition, the reference level 'From' for percentage conditions is defined in the calculation schema. The reference level 'From' can be combined with a reference level 'To'.
© SAP AG
IRT320
2-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Calculation Schema Customizing
Step
Cntr
1
10
CTyp From
To
Man.
Mdt
PB00
Stat
P
SubTo
X
1
Reqt ..
Accrls
Basis for percentage markup/markdown Automat. determin./ manual maintenance Obligatory Statististical Print indicator Interim storage of cond. values Requirement Transaction key for account determination SAP AG 2003
The calculation schema defines: which condition types are to be taken into consideration and in which sequence (Step and Cntr) the basis on which percentage markups and markdowns are to be made (From and (optional) To) whether conditions for a condition type are to be determined automatically or must be entered manually (Man.) whether a condition type is mandatory (Mdt) whether the condition is to be taken into consideration when net prices are calculated (Stat) whether condition lines are to be printed, and if so, how (P) whether, and in what form, condition values or subtotals are to be stored for further processing (SubTo) in what circumstances access to a particular condition type is excluded (Reqm) which alternative formulae are to be used to calculate the condition value (AltCty) which alternative formulae are to be used to calculate the condition basis (AltCBV) which transaction key is used to find the G/L account for a condition type that is relevant for accruals (Accrls or AcctKey), when purchase accounts handling is active
© SAP AG
IRT320
2-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Calculation Schema: Schema Determination
Purch.order POrg Vendor
R300 R3000
Vendor Vendor R3000 R3000
Schema Schema gr. gr. Pur. Pur. Org Org Pur. Pur. Org Org R300 R300
R001 R001
Schema Schema gr. gr. Schemagr Vendor Vendor Vendor R1 VendR1
Cakulation Cakulation schema schema RMISR0 RMISR0
SAP AG 2003
You can define the determination of calculation schemas for standard purchase orders, stock transport orders, market price determination in vendor evaluations, and service processing. You have the following options when assigning schemas for standard purchase orders: You can assign a calculation schema that is generally valid (such as RMISR0) You can make the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations and/or a schema group for one or more vendors. The schema group enables you to group together purchasing organizations or vendors that you want to assign the same calculation schema to. Schema groups are defined in Customizing. Purchasing organizations are also assigned to schema groups in Customizing, while vendors are assigned to a schema in the vendor master. For stock transport orders, the schema assignment is dependent on the purchasing organization, the document type, and/or the supplying plant. For market price determination in the vendor evaluation, schema determination is dependent on the purchasing organization. For service processing, the calculation schema is dependent on the document type. Here, for each document type, the same calculation schema must be used for the documents RFQ/quotation (AN), purchase requisition (NB), and purchase order (NB).
© SAP AG
IRT320
2-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Group Conditions and Print Indicators Purch.order Art. 1 1 pc 90 USD
Surcharge
Art. 2 1 pc 10 USD
50 USD
Schema RMISR0
Print indicator =
X
Article 1 1 pc Surcharge Net value
90.00 45.00 135.00
Article 2 1 pc Surcharge Net value
10.00 5.00 15.00
CTyp .... PB00 ... ZB00 ....
Printing X ?
Print indicator =
Article 1 1 pc Article 2 1 pc Surcharge Total value
S
90.00 10.00 50.00 150.00
SAP AG 2003
The print indicator in the calculation schema controls the output of the condition line in document output, for example, when printing the purchase order. From Release 4.0A, for more specific definition, print indicators A, B, C, and D are available for printing condition lines as totals, and a, b, c, and d for printing condition lines at item level. A condition line is not printed (print indicator _) A condition line is printed (print indicator A or a) A condition line is printed if the condition value is not equal to zero (print indicator B or b) A condition line is printed if the condition value is not the same as the condition value of the previous line (print indicator C or c) A condition line is printed if the condition value is not equal to zero and not the same as the condition value of the previous line (print indicator C or c) The print indicators are explained in the field documentation.
© SAP AG
IRT320
2-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Calculation Schema for Condition Type PB00
Calculation schema RMISR0 Step CounterC.Typ 1 1 PB00 . . .
Condition type PB00 Condition class Calculation type Calculation schema: RM0002 . . . Calculation schema: RM0002
PC PC
Article Article
Purchasing view Valid
from 01.01. to 31.12.
C.Typ PB00 RB00 RA01
Cond. value . . .
% %
Conditions Conditions
$$
Step 1 10 10 . . .
CounterCondition Type 1 PB00 1 RB00 3 RA01
Suggest additional conditions
SAP AG 2003
A calculation schema for supplementary conditions must be assigned to condition type PB00 (or another, comparable condition type for the gross price). Usually, schema RM0002 is used. Condition types for this 'supplementary calculation schema' are surcharges and discounts (RA00, RA01 and so on) and freight conditions (FRA1, FRB1 and so on), which can be valid for specific articles. The calculation schema for supplementary conditions defines the list of condition types that the system proposes when you choose the Suggest supplementary conditions function when maintaining conditions in the Purchasing view of the article or quotation/outline agreement items. This assignment simplifies the entry of surcharges and discounts and so on based on the article or quotation/outline agreement item. Supplementary conditions have the same validity period as the main condition. An access sequence is not usually assigned to the condition types of the additional condition schema, because they are always maintained in connection with the gross price. The calculation schema assigned to the standard purchase order and the calculation schema for supplementary conditions should be structured in the same way.
© SAP AG
IRT320
2-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Access Sequences
PB00 PB00
Price Price
RA01 RA01
Discount Discount % %
RA04 RA04
Discount/weight Discount/weight
specific
Access sequences sequences Access
Calculation schema schema Calculation
Condition type
Access sequence
Search condition record for vendor Allfresh and article Banana
Condition Condition record record for for tab. tab. 001 001
1 RA01
2
general
Apples Peaches Oranges Cherries
2% 1% 3% 2%
Condition Condition record record for for tab. tab. 002 002
1. Vendor/article 2. 2.Vendor/ Vendor/ merch. merch. category category
Allfresh Roberts Rudez Smith
John Roberts Allfresh Miller
Bath Fashion Fruit Fashion
4% 2% 3% 5%
SAP AG 2003
© SAP AG
IRT320
2-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Access Sequence Customizing
Access sequence 0006 Vendor discount
Accesses No.
Tab. Description
Requirement excl.
10 20 30
45 69 44
0 0 0
Condition group of the vendor Vendor subrange Vendor
...
Fields Condition
Doc. structure
Doc.field
EKORG LIFNR
KOMK KOMK
EKORG LIFNR
Direct value source
SAP AG 2003
An access sequence can be assigned to a condition type. The access sequence is a search strategy that defines the sequence in which the system searches through condition tables looking for relevant entries for a condition type. The sequence in which data is accessed is defined by the sequence of condition tables in the access sequence. The 'Exclusive' indicator is used to define that the serch for further valid entries in (other) condition tables is terminated if the access was successful and a relevant entry was found. The requirement routines control the circumstances in which the system searches through certain condition tables for relevant entries. Some condition tables are only accessed if the document item meets certain criteria. If you want to maintain a condition type with a validity period (for example condition type PB00), an access sequence must be assigned to it. An access sequence cannot be assigned to a header condition. If you create a new access sequence or change an existing one, you must generate the new access so that the new or changed access sequence is available in the productive system.
© SAP AG
IRT320
2-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Data Retention Levels of Conditions
Site
Article
Scope of table
Data maintenance
Performance
SAP AG 2003
It is usual to retain data for conditions at site/article level. As most retailers have a large number of articles in their assortments, and also have many sites, condition tables become increasingly large. As the table sizes increase, the performance of the system can decrease as the tables are accessed. This can lead to performance problems in the whole productive system (invoicing, POS outbound and so on). Even though retention of data at site/article level is favored by many, it is not absolutely essential. As a result, where possible, data should be retained at a higher level.
© SAP AG
IRT320
2-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Alternative Data Retention Levels
Purch. organization /
Sales organization /
article
article Reference purch. organization / article
Customer price list / article
Site price list / article
SAP AG 2003
In Customizing, you can assign a reference purchasing organization to a purchasing organization. As a result, a purchasing organization can access the conditions and contracts of this reference purchasing organization.
© SAP AG
IRT320
2-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
Conditions are agreements relating to prices, surcharges, discounts and so on. Conditions are defined by condition types and are stored in the system as condition records. The access sequence is a search strategy that defines the sequence in which the system searches for condition records for a condition type. A calculation schema groups together all condition types that are involved in price determination.
SAP AG 2003
© SAP AG
IRT320
2-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Elements of the Condition Technique Exercises Unit: Elements of the Condition Technique
At the conclusion of this exercise, you will be able to: • Differentiate between and create header, group, and item conditions • Define condition types as group conditions • Understand and use the main control parameters for condition types and calculation schemas • Understand calculation schema determination • Create condition types and calculation schemas • Analyze and understand price determination, taking account of several condition tables, validity periods, and scales Conditions can relate to a single item in a purchasing document, several items (group condition), or all items (header conditions). Header and group conditions can be divided among the individual items proportionally. When you create a purchase order in Purchasing, the system determines the calculation schema and carries out price determination for the condition types contained in the calculation schema. This process takes account of scaled conditions and different periods of validity.
© SAP AG
IRT320
2-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
1
Display various condition types in Customizing and create your own calculation schemas. 1-1
Display the Customizing settings for the following condition types and find the control parameters specified:
Condition Type
Condition Class
Calculation Rule
Condition Category
+/.
PB00 RA00 RB00 RC00 RL01 FRB1 SKTO
1-2
Display the control parameters for calculation schema RMISR0 and determine the sequence of discount condition types:
Condition Type
Step
Counter
RB00 RC00 RA00 RA01 HB01 RL01 RGR0 1-3
© SAP AG
Create a new calculation schema ZISR## with the description “Purchasing document IRT320-##” by copying standard calculation schema RMISR0, including all dependent entries. (Note: During copying, the system displays the message “You should use the counter only for manual item conditions” a number of times. Confirm this warning each time by pressing Enter.) IRT320
2-27
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2
Assign your calculation schema ZISR## to your organizational levels as appropriate. 2-1
Create a new vendor schema group 20+## (for example, 23 for group 03) with the description “Schema group IRT320-##” by copying the standard schema group. Save your schema group.
2-2
Now define schema determination by assigning your calculation schema ZISR## to POrg schema group R001 and your vendor schema group 20+##. Save this assignment.
2-3
Assign your schema group 20+## to vendor TS3## by changing the purchasing data of the vendor master record for company code R300 and purchasing organization R300. Save this assignment.
2-4
© SAP AG
You also want calculation schema ZISR## to be valid for vendors TS1## and TS2##. Therefore, assign your vendor schema group 20+## (from exercise 2-1) to these vendors as well by changing the purchasing data of the vendor master record for purchasing organization R300.
IRT320
2-28
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
3
Look at the settings for the access sequence that is assigned to condition type RL01. 3-1
How many accesses does the access sequence contain? ................................................................................................................
3-2
Which tables are searched for valid condition records? ................................................................................................................
3-3
Which fields in the document structure and table determine the search for a valid condition record in access 30? 1.............................................................................................................. 2...............................................................................................................
3-4
How would you go about creating a new access sequence? 1.............................................................................................................. 2............................................................................................................... 3............................................................................................................... 4................................................................................................................
3-5
Do all condition types refer to an access sequence? Give reasons for your answer: .................................................................................................................. ................................................................................................................... ...................................................................................................................
4
Create a condition type that fulfills the following prerequisites: 4-1
A general surcharge is due for all purchase orders for vendor TS3##. This surcharge is scaled according to the total value of the purchase order. The surcharge applies for all articles supplied by the vendor, and is to be divided among the individual order items proportionally. A suitable condition type does not exist for this condition. Before you define a new condition type, consider: On which factors does the condition (e.g. vendor, article) ________________________________________________________ Which condition class should be assigned to the new condition type? ________________________________________________________
© SAP AG
IRT320
2-29
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Which calculation type should you use for the new condition type? ________________________________________________________ How can you make sure that your condition type is interpreted as a surcharge? ________________________________________________________ How do you ensure that the surcharge amount is split among the items? ________________________________________________________ What scale basis should you choose? ________________________________________________________ Choose scale type B. 4-2
Define the new condition type; Use the key ZS## and the description “Surcharge IRT320-##”. Use the standard condition type RL01 as a reference.
4-3
Change your calculation schema ZISR## by adding your new condition type ZS## as a further surcharge. You should assign your condition type to the same step as all other surcharges and discounts, and have it as the last condition type at this level. Use standard condition type RL01 as a reference. (Note: Confirm the message “You should use the counter only for manual item conditions” by pressing Enter.)
4-4
At what level/counter are the surcharges/discounts included in the calculation schema? ___________________________________________________________ The condition values for your condition type ZS## should be printed item-by-item (procedure up to now). What print indicator do you have to set to achieve this? ___________________________________________________________ Save your changes.
© SAP AG
IRT320
2-30
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Introductory sheet for the solutions The Solutions are based on the following assumptions:
© SAP AG
•
You are on the SAP Retail initial screen (transaction W10T). You should enter this transaction as the start menu in your user parameters.: System → User profile → Own data, on the 'Defaults' view, enter ‘W10T’ as the StartMenu.
•
If the term Retailing is written before a path, you are in the SAP Retailing menu, the SAP Retail application menu (transaction W10M). You get here from SAP Easy Access SAP Retail by choosing Logistics → Retailing
•
If the term IMG is written before a path, you are in the Implementation Guide of the R/3 System, where you can make Customizing settings. You get here from SAP Easy Access SAP Retail by choosing Tools → AcceleratedSAP → Customizing → Edit project → Display SAP Reference IMG (F5) or the transaction NSPRO → F5
IRT320
2-31
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Elements of the Condition Technique Solutions Unit: Elements of the Condition Technique
1-1
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types → Define Condition Type Button: Choose
Condition Type
Condition Class
Calculation Type
Condition Category
+/.
PB00
B
C
H
positive
RA00
A
A
--
negative
RB00
A
B
--
negative
RC00
A
C
--
negative
RL01
A
A
--
negative
FRB1
A
B
B
positive
SKTO
A
A
E
positive
1-2
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select calculation schema; Double click on Control data
© SAP AG
IRT320
2-32
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Type
Step
Counter
RB00
110
1
RC00
110
2
RA00
110
3
RA01
110
4
HB01
110
10
RL01
110
11
RGR0
110
13
RGR0
110
13
1-3
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select calculation schema; Edit → Copy As… Enter name and description of the new calculation schema
© SAP AG
IRT320
2-33
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-1
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Group → Schema Groups: Vendor Button: Choose Select Standard procedure vendor Edit → Copy As… Enter vendor schema group and description
2-2
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process→ Define Schema Determination → Determine Calculation Schema for Standard Purchase Orders Button: Choose Button: New Entries
2-3
Schema gr. POrg
Schema gr. Vnd
Schema
Description
R001
20+##
ZISR##
Purch. doc. group 20+##
Menu path: Retailing → Master data → Vendor data → Edit Vendors → Vendor → Change → Purchasing (Immed.) Vendor TS3## Purch. organization R300 Select Purchasing data Subscreen Conditions Field Schema group, vendor: 20+##
2-4
See 2-3
3 Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Condition type: RL01 Vendor Discount % Access sequence: 0006 Vendor Discount 3-1
© SAP AG
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Access Sequences Confirm message Select access sequence 0006, double-click on Accesses 3 accesses IRT320
2-34
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
3-2 AcN o.
Tab.
Description
Requirem nt
Exclusiv e
10
45
Condition group of the vendor
x
20
69
Vendor subrange
x
30
44
Vendor
x
3-3
Table 44: EKORG and LIFNR Document structure KOMK: EKORG and LIFNR
3-4
1. Check whether a suitable access sequence already exists, which can be enhanced or changed → Copy this access sequence 2. Insert a new access or delete accesses that are not required and assign to the relevant database table. 3. Assign the fields of the communication structure to the fields in the table 4. Assign the new access sequence to the relevant condition type.
3-5
No, not all condition types refer to an access sequence. The deciding factor is whether conditions with their own validity period can be created for the condition type. Exceptions are, for example, article-specific discounts and surcharges. The validity of these always depends on the validity of the gross price of the article.
4-1
As the surcharge is to apply to all articles from the vendor, it only depends on the purchasing organization and vendor. Condition class A (surcharges and discounts) and calculation type B (= fixed amount) should be assigned to the new condition type. You use sign A (= “positive”) to define that the condition type is interpreted as a surcharge. If you select the group condition indicator, the surcharge amount is split proportionally among the document items. The scale basis should be B (= value scale), the check value = A and the scale type B or blank.
4-2
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types → Define Condition Type Button: Choose
© SAP AG
IRT320
2-35
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
4-3
Menu path: IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Select calculation schema; Double click on Control data
4-4
Surcharges and discounts are sorted at level 110 in the calculation schema. Insert your new condition type ZS## at level 110 with the counter 18. By selecting print indicator X, you define that the condition values are printed itemby-item (procedure up to now).
© SAP AG
IRT320
2-36
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conditions in Purchasing
SAP AG 2003
© SAP AG
IRT320
3-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conditions in Purchasing
At the conclusion of this unit, you will be able to: Explain price determination for a purchase order Apply pallet discounts and free-goods discounts
SAP AG 2003
© SAP AG
IRT320
3-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Business Scenario
You agree on a new type of condition and its settlement, with your vendor. Once you have entered your conditions for the vendor, you want to use the new purchase price.
SAP AG 2003
© SAP AG
IRT320
3-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Diagram
1 2 3
Course Overview
Elements of the Condition Technique Conditions in Purchasing
4 5 6
Pricing
Promotion
Inventory Management and Valuation
SAP AG 2003
© SAP AG
IRT320
3-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Maintenance
Conditions Site Site
Vendor Vendor
Condition maintenance in the purchasing view of article maintenance
SAP AG 2003
© SAP AG
IRT320
3-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Maintenance
Purchase order Site Site
Vendor Vendor
Purchase order POrg Vendor Article Order quantity Price/pc
R300 R3000 R100000 1000 pc 10
SAP AG 2003
© SAP AG
IRT320
3-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Price Determination Overview Calculation Schema RMISR0 Step 1 . . .
C.Typ PB00
Purch.order
...
POrg R300 Vendor: A For site R301 Article 1
Condition type: PB00
5 pieces 50,00
Access sequence: 0002 . . .
Access sequence: 0002 Condition tables: 1. Site info record (excl.) 2. Article info record (excl.) . . . . SAP AG 2003
Condition table Site info record no record available Condition table Article info record Article 1 10.00 as of 500 pc 9.50
When you create a purchase order, the system searches through purchasing info records, purchasing documents, and general conditions for valid conditions and adopts these as default values in the new document. Prices are determined in several steps: First, the schema assignment is used to determine the relevant calculation schema The system searches for condition records for all the condition types listed in the calculation schema, providing an access sequence is assigned to the condition type The system searches for condition records in the order defined in the access sequence The search is complete when the system has found a valid condition record Article-specific surcharges and discounts are usually defined as supplementary conditions for the gross price (PB00). An access sequence is not assigned to additional conditions in Customizing for the condition type. Separate price determination is not carried out for additional conditions - they are determined using the condition record for the gross price.
© SAP AG
IRT320
3-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Validity Periods and Pricing Date Gross price PB00 1.01. - 31.03. 9.50 1.04. - 30.06. 9.80
Purchasing Purchasing view view
1.07. - 30.09. 9.00 1.11. - 31.12.10.00 Price control 1 = Order date
2 = Delivery date
3 = Current date
Purch. order 1
Purch. order 2
Purch. order 3
Current date: 1.07. Order date: 30.06. Delivery date: 3.10.
Current date: 1.07. Order date: 30.06. Delivery date: 3.10.
Current date: 1.07. Order date: 30.06. Delivery date: 3.10.
Price:
Price:
Price:
9.80
10.00
9.00
SAP AG 2003
Time-dependent conditions are always restricted to a validity period defined by a start date and end date. If you do not enter a validity period, the system proposed a period. In Customizing, you can control the period proposed by the system. When you create a purchase order, the pricing date determines which validity period the system uses. In the standard system, the pricing date is the same as the document date of the purchase order. However, you can select the delivery date, goods receipt, or a manually entered date instead of the document date. You can define a default value for the pricing date category in the vendor master or the purchasing view of the article or enter a specific pricing date on the purchase order initial screen. The proposed pricing date category or the pricing date can be changed at PO item level. However, if you change the date, price determination is not carried out automatically. It must be triggered manually on the conditions screen. If you select the delivery date for price determination, the delivery date of the first schedule line is used for items with several delivery dates (schedule lines).
© SAP AG
IRT320
3-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Retail-Specific Conditions
Pallet discounts Pallet discount Surcharge for incomplete pallet
Free goods Inclusive bonus quantity Exclusive bonus quantity
SAP AG 2003
© SAP AG
IRT320
3-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pallet-Specific Conditions
Pallet discount Discount for each full pallet
Pallet Surcharge Surcharge for incomplete pallet
Article 1
Article 1
Article 1
Article 1
Article 1
Article 1
Article 1 Article 1 Article 1
Article 1
$5 $5 discount discount for for each each full full pallet pallet
$20 $20 surcharge surcharge for for each each incomplete incomplete pallet pallet
SAP AG 2003
A pallet discount is granted even if the pallet contains several different articles. These articles must always have the same base unit of measure and alternative unit of measure. The pallet discount can then be split over the individual articles. The same applies for a surcharge for an incomplete pallet.
© SAP AG
IRT320
3-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pallet Discount/Surcharge for Incomplete Pallet (LP00/LP01)
Pallet discount 5.00 /1 pallet
100,00
1 pallet = 10 cartons
Calculation schema Step
Cntr
CTyp
20
0
24
0
LP00
26 ...
0
LP01
Surcharge for incomplete pallet 20.00 /1 pallet
...
Description
Reqt
AltCty
AltCBV
Net value incl. discount
22
Pallet discount
24
Surcharge for incomplete pallet
*Quantity (whole number) FORM FRM_KOND_BASIS_022. ... ENDFORM.
*Quantity = 1 if incomplete pallet FORM FRM_KOND_BASIS_024. ... ENDFORM.
SAP AG 2003
Condition type LP00 allows you to define discount conditions that are only taken into consideration if the unit of measure is a whole number (pallet or carton, for example). The unit of measure is assigned to the condition type. This condition type must be included in the calculation schema and assigned to basis formula 22. Basis formula 22 checks whether the purchase order quantity is a whole number, and the condition type is only taken into consideration if it is a whole number. Condition type LP01 enables you to define surcharges that are only taken into consideration if the pallet is incomplete. The unit of measure (pallet, for example) is assigned to the condition type. This condition type must be included in the calculation schema and assigned to basis formula 24. Basis formula 24 checks the purchase order quantity and rounds it to value of a unit of measure that is assigned to the condition type. In the case of mixed pallets, you can use condition types LP02 (mixed pallet discount) and LP03 (surcharge for incomplete mixed pallet). Both are defined as group conditions and therefore allow you to cumulate the quantities of the individual items. Scale formula 23 is assigned to condition type LP03. This formula eliminates the numbers in front of the decimal point and checks the decimal places.
© SAP AG
IRT320
3-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Free-Goods Discount: Inclusive Bonus Quantity
Purchase order
Delivery
Invoice
Company Company Company
Company Company Company
M Invoice Purchase order Invoice
10 10 pieces pieces
Invoice Invoice Invoice
10 10 pieces pieces
xyz
88 pieces pieces
SAP AG 2003
Free-goods discount are discounts in kind given on merchandise and are part of the price agreements made for an article. With inclusive bonus quantities, the ordering party only pays for a part of the quantity of goods ordered. The remaining quantity is free. Inclusive bonuses are also referred to as inclusive discounts in kind, meaning that a part of the quantity ordered is given as a free-goods discount (at no charge). As an example: If you order 10 bottles, the vendor gives you 1 bottle free. 10 are delivered, and you are only billed for 9. In this case, you take the free-goods discount into account when you order this article from this vendor. For the free-goods discount to be taken into consideration in the purchase order, you must define that the free goods are allowed for the vendor and the article in question.
© SAP AG
IRT320
3-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Free-Goods Discount: Exclusive Quantity
Purchase order Company Company Company
Invoice Purchase Invoice
Delivery
Invoice Company Company Company
M order
Invoice Invoice Invoice
44 packets packets ++ 11 coffee coffee machine machine
44 packets packets
xyz
44 packets packets
Coff ee
Coff ee
Coff ee
Coff ee
Coff ee
Coff ee
+
SAP AG 2003
With exclusive bonus quantities, the ordering party is charged for the merchandise ordered but receives additional goods free of charge. Exclusive bonus quantities are often referred to as exclusive discounts in kind, meaning that a certain quantity is granted as a discount in kind over and above the quantity ordered in the purchase order. You receive more than you ordered, with no charge being made for the extra quantity. As an example: If you order 10 bottles, the vendor gives you 1 bottle free. 10 are ordered, but 11 are delivered. You are only invoiced for 10. With exclusive bonus quantities, the article you receive free can be the same as the article ordered, or a different article.
© SAP AG
IRT320
3-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Free Goods: Control Schema NR0001 10 1 .
Vendor Vendor
NR00 Free goods
Qual.f. disc.in kind X
Qual.f. disc.in kind X
Condition type NR00 Access seq.
Article Article
Valid from Valid to
Purchase order Access seq. NR00 Access:10 05 Vend./Article/POrg/Site Access:20 10 Vend./Article/POrg Condition records Table 05 Table 10
1Doc.
type : Purch. org. : Purch.group :
2Vendor
no record available access successful
NB R300 R30
: R3002
Main item R100014
R3002 R100014 R300 ... ... ... ...
Sub-item U
SAP AG 2003
Prerequisites for determining free-goods discounts in Purchasing: Article and vendor must be flagged as qualifying for free-goods discounts. The free-goods discount schema of the business transaction is determined from the purchasing organization schema group and vendor schema group. The condition types of the free-goods discount are listed in the condition types.
© SAP AG
IRT320
3-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conditions in Purchasing: Unit Summary
You are now able to: Explain price determination for a purchase order Apply pallet discounts and free-goods discounts
SAP AG 2003
© SAP AG
IRT320
3-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conditions in Purchasing Exercises Unit: Conditions in Purchasing
At the conclusion of this exercise, you will be able to: 1. Understand price determination for a purchase order 2. Create pallet discounts and free-goods discounts 3. You agree on a new type of condition and its settlement with your vendor. Once you have entered your new conditions, you want to calculate a new purchase price.
1
In article maintenance, you want to maintain new conditions. 1-1
Maintain the Purchasing view for your new article TA13##: Purchasing organization: Vendor:
R300 TS3##
Planned delivery time: Purchasing group: Minimum order quantity:
10 days R 30 10 pieces
Gross price:
285.00 USD as of 1 piece 275.00 USD as of 50 pieces 250.00 USD as of 250 pieces 1% for purchase of 1 piece or more 2.5% for purchase of 50 pieces or more 50.00 USD
Discount on net price: Freight surcharge:
The conditions are to be valid until the end of the following year. Save your entries. 1-2
What condition types do you use? Condition
Condition Type
Gross price % discount on net price Absolute freight surcharge © SAP AG
IRT320
3-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
1-3
Vendor TS3## also grants a scaled discount on all articles for a limited period (vendor rebate): -3% for a condition value over 10,000.00 USD -4% for a condition value over 50,000.00 USD -5% for a condition value over 100,000.00 USD This discount is limited for a period of four weeks, starting from today. Maintain the vendor discount for purchasing organization R300. Save your entries.
2
Check the conditions in a purchase order 2-1
Create a purchase order: Vendor: Purchasing organization: Purchasing group: Delivery date:
TS3## R300 R30 in 2 weeks (applies to both items)
Item 1: Order 50 pieces of article TA13## for site T1## . Item 2: Order 450 pieces of article TA13## for site T1## . Do you have to enter a net price? _________________________ 2-2
Check the conditions for both items and determine the amounts/percentages for both items: Item 10
Item 20
Gross price (per piece) % discount on net price Vendor discount Net price (per piece) Freight surcharge Cash discount Effective price (per piece) Save your purchase order. 2-3
Why are different prices and different vendor rebates determined? _________________________________________________
© SAP AG
IRT320
3-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-4
What setting do you have to make in Customizing to ensure that the individual items are cumulated, meaning that other prices and discounts can be obtained? _________________________________________________
2-5
In addition, your vendor TS3# grants you a pallet discount of 20.00 USD for each complete pallet. If the pallet quantity is incomplete, a surcharge of 10.00 USD is due. Maintain conditions for this.
2-6
Now create a new purchase order: Vendor:
TS3##
Purchasing organization:
R300
Purchasing group:
R30
Delivery date:
in 2 weeks (applies to both items)
Item 1: Order 100 pieces of article TA13## for site T1## . Item 2: Order 720 pieces of article TA13## for site T1## . Which pallet conditions does the system use? _________________________________________________ Save your purchase order. 3
You have negotiated a new agreement with vendor TS1##. 3-1
Now maintain the Purchasing view of article TA13## for vendor TS1## . Vendor: Article: Purchasing organization:
TS1## TA13## R300
Planned delivery time: Purchasing group: Purchase price:
10 days R30 290.00 USD
Save your entries.
© SAP AG
IRT320
3-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
3-2
You negotiated the following surcharge with your vendor. Maintain the conditions of vendor TS1## for your new condition type ZS## (see exercises for unit Element of the Condition Technique 4-2). -30.00 USD up to a total purchase order value of 5,000.00 USD -20.00 USD up to a total purchase order value of 8,000.00 USD -10.00 USD up to a total purchase order value of 20,000.00 USD If the total purchase order value is greater than 20,000.00 USD, the surcharge does not apply. The surcharge applies until the end of the following year. What menu option do you use? ___________________________________________________________ Save your entries.
3-3
Create a purchase order with the following data: Vendor: Purchasing organization: Purchasing group: Delivery date: Site:
TS1## R300 R30 in 4 weeks (applies to both items) T1## (applies to both items)
Article 1
TA13## 10 piece
Article 2
TA05## 38 pieces
Go to the header conditions screen and check: The total net value of the purchase order The gross price per piece
______________________ ______________________
The surcharge for the whole purchase order
______________________
Go back to the item overview screen. What net price was calculated for both articles? ___________ Use the condition details screens for both items to check the proportional distribution of the surcharge. What is the surcharge for item 10 ? _________________ What is the surcharge for item 20 ? _________________ Save your purchase order.
© SAP AG
IRT320
3-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
4 You want to maintain a free-goods discount for your article in the form of an exclusive bonus quantity. 4-1
In the Purchasing view of vendor TS3##, check if the indicator that controls whether the vendor can grant free goods is selected.
4-2
In the Basic Data view of article TA13## maintain the indicator that controls whether the article is eligible for discount in kind for Purchasing and Sales.
4-3
Assign the free-goods calculation schema NR0001 to your vendor schema group ##.
4-4
Create an exclusive bonus quantity for your article. Article:
TA13##
Vendor:
TS3##
Purchasing organization:
R300
Key combination:
Info record per order unit
Info record category:
0
Order unit:
Piece
Maintain your free goods discount NR00 as exclusive bonus quantity so that, with an order quantity of 1000 pieces or more, one piece of article TA20## is delivered for each 100 pieces of article TA13##. Set the calculation to “Unit reference”. Save the free-goods discount. 4-5
Create a new purchase order for 999 pieces of article TA13##: Vendor:
TS3##
Purchasing group:
R30
Delivery date:
in 2 weeks
Site:
T1##
What happens? ___________________________________________________________ ___________________________________________________________ Change the order quantity to 1,000 pieces. What happens? ______________________________________________________________________ ________________________________________________ What is the price of exclusive bonus article TA20## ? ____________________ © SAP AG
IRT320
3-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Save your purchase order.
4-6
This setting is needed for the next unit: Maintain a purchase price of 0.80 USD for Article TA14## and Vendor TS1##.
5 In some cases, several conditions apply for the same item. In these cases, you can use the condition exclusion procedure to define which condition should be selected. 5-1
Vendor TS1## delivers articles TA01##, TA03## and TA04## at the following conditions, valid for an unlimited period: For all three articles, create conditions for vendor TS1## and purchasing organization R300. 5-1-1 Article
TA01##
Gross price:
1.0 USD
Discount RA01
3%
5-1-2 Article
TA03##
Gross price:
60 USD
Discount RB00:
2 USD as of 2 car 5 USD as of 100 car
5-1-3 Article TA04## Gross price:
5-2
31 USD
Vendor TS1## informs you that you will be granted a general discount of 5% for an unlimited period. Create the vendor discount for condition type RL01.
5-3
This vendor discount only applies to articles that do not have an article-specific discount. Define two condition exclusion groups: AG## with the description Article group ## and LG## with the description Vendor group ##. Save these condition exclusion groups.
© SAP AG
IRT320
3-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-4
Assign discount condition types RA01 and RB00 to condition exclusion group AG##. Assign condition type RL01 to condition type group LG##. Save these assignments.
5-5
Assign condition exclusion groups AG## and LG## and a suitable condition exclusion procedure to calculation schema ZISR##. 5-5-1 Which condition exclusion procedure do you choose? ___________________________________________________ 5-5-2 Pay attention to the condition exclusion group sequence. In what order must you enter the condition exclusion groups? ___________________________________________________
5-6
Create a purchase order with the following data: Vendor: Purchasing organization: Delivery date: Site
TS1## R300 In four weeks (for all items) T1## (for all items)
Order 100 car each of articles TA01##, TA03## and TA04##. Go to the individual PO items and look at price determination. How are the net prices determined for the following articles? 5-6-1 Article TA01## ________________________________________________________________ ________________________________________________________________ __________________________________ 5-6-2 Article TA03## ________________________________________________________________ ________________________________________________________________ __________________________________ 5-6-3 Article TA04## ________________________________________________________________ ________________________________________________________________ __________________________________
© SAP AG
IRT320
3-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conditions in Purchasing Solutions Unit: Conditions in Purchasing
.
The solutions are based on the following assumptions: •
You are on the SAP Retail initial screen (transaction W10T). You should enter this transaction as the start menu in your user parameters.: System → User profile → Own data, on the 'Defaults' view, enter ‘W10T’ as the StartMenu.
•
If the term Retailing is written before a path, you are in the SAP Retailing menu, the SAP Retail application menu (transaction W10M). You get here from SAP Easy Access SAP Retail by choosing Logistics → Retailing
•
If the term IMG is written before a path, you are in the Implementation Guide of the R/3 System, where you can make Customizing settings. You get here from SAP Easy Access SAP Retail by choosing Tools → AcceleratedSAP → IMG → Edit project → Goto → SAP Reference IMG (F5) or the transaction /NSPRO → F5
1-1
Retailing: Master data → Article data → Article → Change
1-2
Gross price
1-3
2-1
PB00 % discount on net price
RA00
Absolute freight surcharge
FRB1 or FRB2
Retailing: Master Data → Conditions/Arrangements → Condition: Purchasing → Discounts/Surcharges → By Vendor Cursor in row
POrg/Vendor
Button:
[Create]
Retailing: Purchasing → Purchase order → Purchase order → Create → Vendor known You do not have to enter a gross price.
© SAP AG
IRT320
3-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-2 Item 10
Item 20
Gross price for 1 piece
275.00 USD
250.00 USD
% discount on net price
2,5%
2,5%
Vendor discount
3%
5%
Net price for 1 piece
259.88 USD
231.25 USD
Freight surcharge
50.00 USD
50.00 USD
Cash discount
--
--
Effective price for 1 piece
260.88 USD
231.36 USD
2-3
Because of the scales, several prices and discounts are used for each PO item.
2-4
The conditions must be flagged as a group condition.
2-5
Retailing: Master Data → Conditions/Arrangements → Conditions: Purchasing → Discounts/Surcharges → By Vendor→ Create Choose Edit → Scope → All possibilities to display all possible conditions.
2-6
Retailing: Purchasing → Purchase order → Purchase order → Create → Vendor known Item 10: LP01; surcharge 10.00 USD Item 20: LP00; discount 20.00 USD per pallet
3-1
Retailing: Master data → Article data → Article → Change
3-2
Retailing: Master Data → Conditions/Arrangements → Purchasing Conditions → Discounts/Surcharges → For Vendor→ Create-{}-
© SAP AG
IRT320
3-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
3-3
Retailing: Purchasing → Purchase order → Purchase order → Create → Vendor known Total value of the purchase order:
8,876.00 USD
Gross price per piece:
290.00 USD / 157.00 USD
Surcharge for whole purchase order:
10.00 USD
Net price per article:
290.33 USD / 157.18 USD
Surcharge for item 10:
3.27 USD
Surcharge for item 20:
6.73 USD
4-1
Retailing: Master data → Vendor data → Edit vendors → Vendor → Change → Central
4-2
Retailing: Master data → Article data → Article → Change
4-3
IMG: Materials Management → Purchasing → Free Goods → Define and Assign Free Goods Schema → Determine Free Goods Schema
4-4
Retailing: Master data → Conditions/arrangements → Conditions: Purchasing → Free goods → Create Free goods discount type NR00 Button: [Key Combination info record per order unit] Button: [Execute] Button: [Exclusive bonus quantity]
4-5
Retailing: Purchasing → Purchase order → Purchase order → Create → Vendor known Message: Minimum quantity for free goods not reached. The free goods discount is taken into consideration, the free goods article is displayed in the item overview. The exclusive bonus article is free of charge.
4-6
Retailing: Master data → Article data → Article → Change Purchasing view
5-1
Retailing: Master data → Article data → Article → Change
5-2
Retailing: Master Data → Conditions/Arrangements → Purchasing Conditions → Discounts/Surcharges → For Vendor→ Create
© SAP AG
IRT320
3-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-3
IMG: Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Exclusion → Condition Exclusion Groups
5-4
→ Assignment of Condition Exclusion Condition Types
5-5
→ Assignment of Condition Exclusion Calculation Schema Calculation schema ZISR## 5-5-1 SNo. = 1 Condition exclusion procedure D (exclusive) Sequence AG##, LG##
5-6
Retailing: Purchasing → Purchase order → Purchase order → Create → Vendor known
→ Item Conditions In the first two items, RL01 is determined but not used, in the third item RL01 is used, as there is no article-specific discount.
© SAP AG
IRT320
3-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Contents: Sales price calculations Price points Additionals Price lists Price determination sequences Functions for maintaining competitor prices Market-basket price calculations Pricing documents Pricing worklist function
SAP AG 2003
© SAP AG
IRT320
4-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Unit Objectives (1) At the conclusion of this unit, you will be able to: Calculate sales prices, taking into account various retail and cost conditions Explain the differences between one-step and twostep calculations Use price points Include material and handling costs for additionals in price calculations Explain how the pricing table is structured and define list variants
SAP AG 2003
© SAP AG
IRT320
4-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Unit Objectives (2)
At the conclusion of this unit, you will be able to: Explain the functions for price lists, pricing documents and the pricing worklist Name the price determination types and sequences in both Purchasing and Sales Enter competitor prices, define pricing strategies and perform sales price calculations based on these Explain the market-basket pricing functionality Sell seasonal goods at reduced prices in line with a predefined plan in markdown planning
SAP AG 2003
© SAP AG
IRT320
4-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Diagram
1 2 3
Course Overview Elements of the Condition Technique Conditions in Purchasing
4 5 6
Pricing
Promotion
Inventory Management and Valuation
SAP AG 2003
© SAP AG
IRT320
4-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Business Scenario
You have maintained prices and conditions for a new vendor, and you now want to calculate sales prices based on these prices and conditions. Additionally, you want to enter competitor pricing information, and perform a market-basket analysis.
SAP AG 2003
© SAP AG
IRT320
4-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Objectives
At the conclusion of this topic, you will be able to: Calculate sales prices for different articles and organizational levels in a single procedure Use two-step price calculations Describe the procedure and control parameters for calculating sales prices
SAP AG 2003
© SAP AG
IRT320
4-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Basic Functions in Sales Price Calculations
1
22 Sales price
Purchase price
3 Planned or actual markup SAP AG 2003
© SAP AG
IRT320
4-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Planned Markups
Planned Planned markup markup
valid from - to
valid from - to
per per distribution distribution chain chain
per per price price list list per merchandise category
SAP AG 2003
Markup calculations are one way of determining a suggested value for the sales price. Planned markups can be stored in the system for markup calculations. Planned markups are added to the (net/net) purchase price. They reflect both the profit that a company aims to make by selling certain articles and general cost components. Usually, you would define a planned percentage markup for a combination of sales organization, distribution channel and merchandise category. In wholesale, planned markups can also be defined for different price lists. As planned markups are condition types, you can also define them for other organizational levels, such as for individual articles.
© SAP AG
IRT320
4-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Selection
Selecting articles
Selecting organizational levels
Article
Distribution chain
Merchandise category Vendor
any combination
Site Price list
Vendor sub-range
Site group
Season
Sales price calculation
SAP AG 2003
Sales price maintenance allows you to maintain the final sales prices for an article in a store or a particular group of stores, or to maintain transfer prices in a warehouse or distribution center. Purchase prices and predefined markups form the basis for calculating these sales prices. You can maintain sales prices for an individual article or for a group of articles (mass maintenance). The prices are always stored at article and site/distribution chain or price list level. The selection options for articles are: Article number (variant) from/to Merchandise category Vendor or vendor sub-range Season The following organizational levels can be selected: Distribution chain Site group Site Price list
© SAP AG
IRT320
4-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Display Header
List group
Site or Article
Article or Site
Vendor
PP
Planned markup Actual markup Gross SP
Margin
Fixed part
Pricing table
List fields
List variants SAP AG 2003
In the initial screen for sales price calculations, you can select how they should be displayed. This display is determined by list group and list variant. The list group controls which data is displayed in the header and which in the fixed part of the pricing table. List variants are used for individually designing the list screen in which the calculation is performed (pricing table). You can use list variants to define which list fields should appear in the pricing table. The list variant determines which table columns appear in the list screen and in what order they are displayed. The column number defines the sequence of the columns in the table. You can also add your own texts to the predefined list fields in the pricing table for sales price calculations. These texts are used as titles for the columns in the table.
© SAP AG
IRT320
4-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Control Parameters
Calculation Schema Document creation
Pricing type
Pricing currency
...
Organizational level
SAP AG 2003
The pricing type controls (among other things) which sales price calculation schema is to be used for the different distribution chains. The pricing type also controls: whether pricing documents are to be created, whether, if the purchase price of an article changes, the sales price or the markup remain the same, which currency is to be used for the conversion, and which conversion rate is to be used to convert foreign currencies.
© SAP AG
IRT320
4-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Procedure Sales price calculation schema WWS001 Article 4711 Quantity: 100 PC C.Type
Description Amount Currency
EKNN
Cost price (net/net) Markup
AUFS
9.00
USD
10
Unit of measure PC
Condition value 900
%
Currency USD
90
USD
Net value
990
USD
Gross value
990
USD
Retroactive adjustment
... MWST
1
2
3 4
Control parameters Org. Level List field Value
...
Pur. price Sls price (net/net) (net)
Sls price Pricing Final price Sales (gross) currency currency
EKPNN
VKPNE
VKPBR
9.00
9.90
9.90
KWAER USD
ENDPR
VWAER
9.99
USD
SAP AG 2003
The starting point is the (net/net) purchase price that is determined during purchase price determination and transported to the schema via condition type EKNN (see red arrow 1 in slide diagram). In Customizing for Pricing (Control Data for Pricing Table and Data Backup), you define how the list fields of the pricing table are filled using pricing data from the sales price calculation schema. The data transport can take place either via a subtotal or via a condition type from the schema. The actual markup in the pricing table is linked to the condition types AUFS and AUFX via a subtotal (compare supplied sample calculation schema WWS001). These refer to the purchase price displayed above them in the pricing table. The (net) sales price and the (gross) sales price are also connected via subtotals from the schema. The main difference between the gross and net sales prices is the inclusion of taxes in the gross sales price. The prices are transported to the list fields as shown by arrows 2 and 3 (see slide diagram). If rounding to price points has been defined, the sales price determined using the schema is rounded (arrow 4 in slide diagram) and the calculation is adjusted to reflect the rounded final price.
© SAP AG
IRT320
4-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Saving Calculations
Org. level List field Value
Pur.Price Sls Price (net/net) (net) EKPNN
VKPNE
9.00
9.99
Sls Price (gross)
Pricing Final price currency
VKPBR
KWAER
9.99
USD
Sales currency
ENDPR
VWAER
9.99
USD
Database Cond. type VKP0
Value Currency 9.99
USD
Price unit 1
Unit of meas. pc
SAP AG 2003
When the calculation is saved, the value of the ENDPR list field is written to the database as a condition record. You should make all the settings for saving the data under Control Data for the Pricing Table and Data Backup in Customizing for Pricing. You define the condition type to which the data is to be saved in the ENDPR list field in the Control Data for Sales Price Calculation Schema and List Field view. In the Assignment of Pricing Tables view, you can define which condition tables are to be used for storing the condition records for the various pricing levels (distribution chain, site, price list).
© SAP AG
IRT320
4-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
One-Step Calculations
Vendor Vendor Purchase price USD 1.00
Purchase price determination - usually performed using a purchase price calculation schema such as RMISR0
Store Store Sales price determination using a sales price calculation schema such as WWS001
Sales prices USD 1.19
Consumer Consumer SAP AG 2003
If sites are to be supplied directly by vendors, a sales price calculation method known as "one-step calculation" is used. It is also possible to perform the sales price calculation based on the desired sales price. In this case, the system automatically calculates various factors, such as the margin. The actual margin determined can also be overwritten.
© SAP AG
IRT320
4-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Two-Step Price Calculations (1) With temporary storage in the database
Purchase price USD 1.00 Vendor Vendor
Store Store
Distribution Distribution center center
Transfer price USD 1.00 Saved to database
Purchase price determination using calculation schema (such as VKP002) for sales price determination Consumer Consumer
SAP AG 2003
The RMISR0 calculation schema is supplied. The various factors that influence sales are calculated using the calculation schema. For example: if the price is calculated using a planned markup, the sales price is determined on the basis of the purchase price and the planned markup. The subtotal "S" is assigned to the effective value in purchase price calculation schema RMISR0 that is determined automatically in the condition type EKNN. The condition type EKNN is used as a receipt condition in sales price calculation schema WWS001.
© SAP AG
IRT320
4-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Two-Step Price Calculations (2) Simultaneous calculation for DC and store
Purchase price USD 1.00 Vendor Vendor
Store Store
Distribution Distribution center center Internal comparison Transfer price USD 1.00
Consumer Consumer SAP AG 2003
© SAP AG
IRT320
4-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Two-Step Price Calculations (3) Generates calculation in background
Calculation just for store supplied Purchase price USD 1.00
Vendor Vendor
Distribution Distribution center center
Transfer
Transfer price USD 1.00 Transfer price is determined in background
Consumer Consumer
SAP AG 2003
When you are calculating prices for a store that is supplied internally, but not for the distribution center (or the distribution center, distribution chain or the relevant price list), and there is no sales price in the system for the distribution center, a calculation for the distribution center is generated in the background. The issue price that is determined in this way is used for the calculation for the store.
© SAP AG
IRT320
4-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Price Points: Topic Objectives
At the conclusion of this topic, you will be able to: Make and use the settings required for rounding to price points - that is, for rounding to "psychological" prices
SAP AG 2003
© SAP AG
IRT320
4-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Rounding to Price Points
Article -> Merch. cat. Sales organization Distribution channel Site group Site Price list
Define Price Point Groups
13.99
rounding up 13.69
Rounding rule
30 %
Price point ranges first price 0.29 10.99 109.99
12.99
last price 9.99 99.99 999.99
price difference 0.10 1.00 10.00
SAP AG 2003
A price point interval is defined using two adjacent price points. The value of the rounding rule is a percentage that defines which part of an interval is to be rounded up. This part starts at a lower level and ends at the upper interval limit of the price point interval. Rounding = 0% means that the whole interval is rounded down, Rounding = 100% means that it is always rounded up.
© SAP AG
IRT320
4-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Additionals: Objectives
At the conclusion of this topic, you will be able to: Take account of material and handling costs for additionals when determining sales prices
SAP AG 2003
© SAP AG
IRT320
4-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Additionals
An additional is an article with its own master record and is assigned to an article for sale for presentation and sales purposes.
The trademark of Marks & Spencer
C&A Regular Ticket
Composition of goods and care instructions
C&A Reduction Ticket
SAP AG 2003
Because the number of additionals assigned to an article can differ, it is hard to take account of additionals when calculating prices. Material and handling costs for the various additionals of an article are mapped using the usual condition types. The condition types for material and handling costs are used only once in a purchase price calculation schema.
© SAP AG
IRT320
4-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Additionals in Purchase Price Determination
Additional data Article Article
....
Unit of measure
....
Additionals
....
Procedure
....
PC
....
Price ticket
....
Attached in store
....
Usage indicator for promotions
....
Invoice recipient
....
Price calculation control
....
always use
....
Retailer
....
Material and handling costs
SAP AG 2003
© SAP AG
IRT320
4-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Additionals in Purchase Price Determination
Material costs
Handling costs
Condition type KAD0
Condition type KAD1
Requirement 64
Requirement 63 Purchase price calculation schema
SAP AG 2003
Special requirements are used to define that an article can have several additionals. These requirements analyze the article master data and determine whether additionals are taken into account during price determination, and if so, how (requirement 63 and 64).
© SAP AG
IRT320
4-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Calculations: Data Retention
Organizational levels
Data retention levels
Vendor / Purchasing organization
Vendor
Vendor / purchasing organization /site Distribution chain Site Price list
Sales price calculation
Purch. price
Distribution chain Site Price list
Site price list
Site price list
Site groups
Site
Sales price
SAP AG 2003
Sales prices can be calculated individually for various sites and distribution chains, based on the organizational structure of the company. Note: If the sales price calculation is performed for the "site group" organizational level, the data is stored at the "site" level, which in turn affects performance.
© SAP AG
IRT320
4-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Price Lists: Topic Objectives
At the conclusion of this topic, you will be able to: Explain the possibilities for and advantages of using price lists to calculate sales prices
SAP AG 2003
© SAP AG
IRT320
4-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Site Price Lists
Article Article 11 1.99 1.99 USD USD
Distribution chain self service warehouses
Article Article 11 1.69 1.69 USD USD
Store 1
Store 2
Store 3
Store 4
Store 5
Store 6
Store 7
Store 8
Store 9
Store 10
Store 11
Store 12
Store 13
Store 14
Store 15
Price list 1
Price list 2
SAP AG 2003
Sales prices can be calculated individually for various sites and distribution chains, based on the organizational structure of the company. Example for the motivation for using site price lists: If only two prices are to be used for the stores of a distribution chain, you can maintain a sales price at distribution chain level for the larger group, however you then still need to create the same site-specific sales price for the stores in the second group. Among other things, this had a negative effect on system performance. Sales prices at price list level are used in the wholesale business. These price lists are assigned to customers in their sales area data and allow customers to be grouped according to sales price. Because of this setup, the sales prices at price list level have higher priority than sales prices at distribution chain level. These wholesale price lists are similar to the site price lists used to group the sites of a distribution chain for pricing purposes. The sales prices at site price list level are therefore ranked between sales prices at distribution chain and site level in terms of priority.
© SAP AG
IRT320
4-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Site Price Lists: Example
Butter: 1.99 Perfume 79.90 M Lemonade: 0.99 Dist. Chain R300/R1 M
M
Cosmetics
Price list type: "Luxury"
Price list type: "Economy"
Beverages
Perfume 89.90
Site Site
Butter: 1.99 Perfume 89.90 Lemonade: 0.89
Lemonade: 0.89
SAP AG 2003
Site price lists are assigned (optionally) to sites in the merchandise category data of the site master. This means that the sites are grouped according to merchandise category. This means that a site may be in different (sales price) groups for different merchandise categories.
© SAP AG
IRT320
4-27
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Site Price Lists: Calculation
Beverages
Sales prices in the site price lists
Article 1
Sales price calculation
1.99
B1 : Luxury
1.95
B2 : Expensive
1.69
B9
: Economy
SAP AG 2003
© SAP AG
IRT320
4-28
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Site Price Lists: Price Changes
Beverages Change to calculation
1
B1
Price assignment
Article 1: 1.99 2.09 B1
Site
Article 1: 1.69 B9
Site Change in assignment
2
Beverages B2
B9
Article 1: 1.99 B2
SAP AG 2003
© SAP AG
IRT320
4-29
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Site Price Lists: Control
Controlling the dist. dist. chain Article Sales organization Distribution channel Price list
Condition type VKP0
Dist. chain pricing level
Permitted pricing level: - price lists only 1 Sites only 2 Price lists and sites
Price list types • Keys • Description
Pricing for article/site
Price list type
A071: Site level A006: Site price list level A073: Distribution chain level SAP AG 2003
Site price lists are maintained in the same way as price lists for customers in Customizing for Sales and Distribution. Sales price lists are calculated in the same way as price lists for customers (in conjunction with a distribution chain) in the sales price calculation function. Note: Sales prices may also change due to changes to the site price list in the site master data.
© SAP AG
IRT320
4-30
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Price Determination Sequences: Topic Objectives
At the conclusion of this topic, you will be able to: Use different determination sequences to create flexible purchase and sales price determination functions
SAP AG 2003
© SAP AG
IRT320
4-31
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Determination Types
F Price determination using standard schema determination
A
Vendor mixed price
E Determination using the components of a sales set
B
Purchase price determination types
Price determination using a special schema
D Interactive entry
Price determination using a customerdefined function module
C
SAP AG 2003
In the sales price calculation function, the sales price for an article is calculated based on a purchase price that represents the average procurement costs of an article for the relevant organizational level. This price is known as the net/net purchase price (EKNN), or simply as the purchase price. There are several different procedures available for determining the purchase price, which use certain article characteristics, particular features of procurement and the structure of the sales price calculation process. The basic elements of the purchase price determination function are the purchase price determination types defined by SAP. In the purchase price determination sequence that must be entered in the initial screen of the sales price calculation function, you define the purchase price determination types that are to be used in determining the purchase price, together with the associated parameter values and the sequence in which the purchase price determination types are to be used.
© SAP AG
IRT320
4-32
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Determination
Basis
Purchase price determination type Combination
Customizing
Purchase price determination sequence Entry in selection screen
Sales price calculation
SAP AG 2003
The purchase price determination sequences form the second element in the flexible structure of the purchase price determination function. They are defined in Customizing for Pricing. You enter steps to define a sequence in which the purchase price determination types are to be used to determine the purchase price, in the same way that you define access sequences for conditions.
© SAP AG
IRT320
4-33
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Determination - Sales Set
Set 1
Purchase price
Comp 1: 1 PC
Comp1: Costs
5.00 USD
Comp 2: 2 PC
Comp2: Costs
10.00 USD
Purchasing view - Set 1 Article master record Vendor: --Purchase price: 25.00 USD Purchase price determination sequence 02 Purchase price determination type E
Requirement 1: "Sales sets only"
SAP AG 2003
Purchase price determination type E is used for calculating prices for structured articles, such as sales sets, which are made up of several components. In such cases, the purchase price for each of the components is determined, and the purchase price for the structure article is calculated by adding the prices for the correct quantities of these components together.
© SAP AG
IRT320
4-34
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Determination for Sales Sets
PP = 5.00 USD
Vend.1
Shampoo
Sls set
Vend. 2
Conditioner
Shampoo Conditioner
Problem: no purchase price for the set
PP = 4.00 USD
Solution: First step: purchase price calculation at component level Second step: purchase price of the sales set = purchase price of the components
SAP AG 2003
© SAP AG
IRT320
4-35
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Purchase Price Determination - Mixed Price
Purchase price Vendor 1: 1.00 USD Vendor 2: 2.00 USD Purchasing view - bananas article master record Vendor: --Purchase price: 1.50 USD Purchase price determination sequence 03
Purchase price determination type F
Requirement 2: "Perishables in DC only"
SAP AG 2003
If an article is procured from several vendors at different purchase prices for a certain period of time, you can use purchase price determination type F to calculate the average purchase price for the article. Here, you can enter weighting factors for vendors according to the planned procurement quantities, for example.
© SAP AG
IRT320
4-36
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Vendor Mixed Price (Perishables)
Vendor A
1.20 USD per piece
Vendor B
1.25 USD per piece
Vendor C
1.45 USD for 2 pieces
Purch. Purch. price determination
Purchase price = 0.98 USD per piece SAP AG 2003
© SAP AG
IRT320
4-37
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Determination Types
A
E
Calculate sales price using planned markup
Absolute price change for list field
B
Sales Price Determination Types
D
Adopt current sales price, adjust margin
Percentage price change for list field
C Adopt sales price from list field
SAP AG 2003
As well as defining the sales prices themselves, determining the margin (gross/net) or the actual markup from the sales and purchase prices are key steps in the sales price calculation process. Depending on whether the margin or the sales price is to be supplied, and how they are to be determined, you can use different procedures to perform the calculation. For this reason, a flexible structure for determining the sales price and margin (similar to that used in Purchasing) has been implemented.
© SAP AG
IRT320
4-38
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Determination Sequences
Basis Sales price determination type Combination
Customizing
Sales price determination sequence
Entry in selection screen
Sales price calculation
SAP AG 2003
© SAP AG
IRT320
4-39
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Price Determination
Sales price calculation Predefined by SAP
Sales price determination types
Sales price determination sequence 01 SP from planned markup 02 adopt current sales price
Step 1 Step 1
A: from planned markup B: current sales price
E: absolute price change
Round to price points?
SAP AG 2003
Customizing: User-defined sales price determination sequences Combination of sales price determination types Determining the sequences in steps Specifying additional parameters for each individual step (list field, flag for rounding to price points) Sales price calculations: Entering the sales price determination sequence in the selection screen
© SAP AG
IRT320
4-40
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Competitor Prices: Topic Objectives
At the conclusion of this topic, you will be able to: Use the competitor prices stored in the system to define sales prices
SAP AG 2003
© SAP AG
IRT320
4-41
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Competitor Prices: Introduction
Cost-oriented calculation
Competitor-oriented calculation
Define planned markups for each merchandise category
Enter competitor prices in SAP Retail
Create/change price calculation
Create/change price calculation
Calculate sales price based on planned markup
Calculate sales price based on competitor prices
Change sales price if necessary
Evaluate margin
Save individual price calculation
Change individual sales price Save price calculation
SAP AG 2003
© SAP AG
IRT320
4-42
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Competitors Competitor 1
n:m
Competitor 2 Competitor 3
Competitor group 1 Competitor group 2
Site Site Merch. cat.: Food
Competitor Competitor group 1 group 1
Site Site Merch. cat.: Food
Merch. cat.: Food
Merch. cat.: Food
Competitor
Competitor
Competitor
group 2
group 1
group 3
SAP AG 2003
Every competitor must have a customer master. Each one of the competitor's stores that does its own pricing should have its own customer master record. If a competitor operates with the same prices in the whole of Germany, only one customer master record is required for the enterprise. The competitor is modeled as a customer, with an account number that is flagged as a "competitor account group". The classification system can be used to group competitors in competitor groups. You can then enter these competitor groups in the merchandise category data for the store.
© SAP AG
IRT320
4-43
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Competitor Prices
Condition type VKPM Requirement "85" Taken into account in sales price calculation schema Controlling the sales price calculation Pricing table list field
Determine different competitors
Pricing strategy (site/merchandise category)
Sales price determination type C with special list field
Determine the suggested price
Use the suggested price as the sales price
SAP AG 2003
Condition type VKPM is supplied for using competitor prices in the sales price calculation function. This condition type allows as many competitor prices as desired to be determined for an article using the sales price calculation schema. In order to do this, requirement 85 must be assigned to the condition type for the competitor prices in the sales price calculation schema. Sales price calculation schema WWS003 is supplied as an example of this. The pricing strategies are used to determine the suggested price in the sales price calculation function.
© SAP AG
IRT320
4-44
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Competitor Price Shopping
Using requirements to exclude articles (for example, just for articles that have the "- = no competition" indicator as their competitor characterization)
Sales View Article Article
Competitor characterization -: no competition C: strong competition SAP AG 2003
The "competitor characterization" field in the sales view of the article master is used to define how much pressure an article is under from competitors. When calculating sales prices, you can use this field to control how the suggested price is to be adopted as the final price.
© SAP AG
IRT320
4-45
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Price Calculations: Topic Objectives
At the conclusion of this topic, you will be able to: Calculate sales prices for a group of articles and sites, taking into account the total profitability of these articles in the sites entered.
SAP AG 2003
© SAP AG
IRT320
4-46
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Price Calculations Sales price calculation • Competitor prices Article Article
important factors • Absolute margin • Markup per article
Market-basket price calculation Aggregation of articles/sites for New characteristics:
• Analysis • Simulation • Calculation
Article Article
• Price activation
SAP AG 2003
The market-basket price calculation function is an enhancement to the sales price calculation function, which allows you to determine sales quantity figures to be used in calculating sales and gross margin figures. You can perform these calculations for a group of articles - known as a 'market-basket' - and a group of sites. The sales and gross margin key figures determined on this level are cumulated for each article and for the whole market basket. As this function is integrated with the sales price calculation function, you can calculate sales prices as usual and use the market-basket price calculation function as an additional planning and analysis tool.
© SAP AG
IRT320
4-47
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Price Calculations
Market-basket analysis Effect of suggested price changes on margins Display of sales key figures (such as average weekly sales quantity) Determination of special key figures (sales, gross margin, changes in sales, changes in the gross margin)
SAP AG 2003
© SAP AG
IRT320
4-48
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Analysis
Key figures Sales key figures (such as average weekly sales figures) Purchase price (calculated price, moving average price) Total value based on purchase prices Current sales price Gross margin New sales price Total value of the market-basket Effect (on margins, sales, profit) Competitor information Sales prices SAP AG 2003
© SAP AG
IRT320
4-49
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Price Calculations - Basic List
Article (article description, merchandise category, and so on), sales unit Purchase price (calculated price or moving average price) Average sales quantity (sales key figures) Total value based on purchase prices Calculated sales price (calculation using planned markup, competitor) Sales price based on cost-oriented price calculation Final price (in manual price changes) Margin Total sales and gross margin Current sales price + total sales/gross margin Changes to total sales/gross margin SAP AG 2003
© SAP AG
IRT320
4-50
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market-Basket Price Calculations - Scenario
Step 1
Step 2
Create market-basket price calculation
Enter competitor prices
Competitor prices
Calculate prices
Step 3
Determine sales key figures
Step 4
Processing
Information structure
New sales price
SAP AG 2003
The sales quantities can be determined individually from the data in the Retail Information System, for example, by entering a customer-specific function module. SAP supplies a number of function modules (such as function module WV_EXAMPLE_MBC_01) as examples for creating customer-specific function modules.
© SAP AG
IRT320
4-51
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Topic Objectives
At the conclusion of this topic, you will be able to: Explain the basic markdown planning terms used in SAP Retail Explain the basic functionalities and goals of markdown planning Create a markdown plan
SAP AG 2003
© SAP AG
IRT320
4-52
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Definition
Definition of planned price reductions (or increases) for articles on sale within a specified period. The markdown plan can also contain the planned sales quantities and values. A sales price calculation can be carried out to create valid conditions from the planned prices.
SAP AG 2003
© SAP AG
IRT320
4-53
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Steps in the Process Planning markdowns
Price activation Rel. price
100% •
80%
•
50%
•
Sale of articles
30%
•
Markdown rule
Time
Analysis of sales
Adjustment of markdown planning if required SAP AG 2003
Pricing strategies are used to control the sale of seasonal goods. The purpose of markdowns is usually to increase the sales of an article. The aim of markdown planning is to finish the season with as little stock as possible while minimizing losses by reducing prices (or in some cases, increasing prices). You can use a markdown plan to plan and make price changes for certain goods. Once you have defined your markdown strategy, you can compare the actual results with the planned results at regular intervals to monitor the efficiency of your strategy. When you monitor your markdown plan, you can make changes at any time to react to an unexpected increase or drop in sales.
© SAP AG
IRT320
4-54
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Overview
Markdown Markdown rule rule
Markdown plan Header
Site Site
Markdown Markdown type type Selection Selection options options
Distribution Distribution chain chain
Items
Article Article detailed detailed data data Price phases
SAP AG 2003
You must first choose a markdown type for the markdown plan. The markdown type is used to determine the markdown rule, which contains details of the individual price phases. In the markdown plan, each article is displayed in a separate line. For each article, you enter the planned sales quantity and the initial sales price. The price phases for the individual articles contain additional information such as the planned sales quantity, the sales price per price phase, the planned sales values, and the margins.
© SAP AG
IRT320
4-55
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Markdown Type
Markdown plan Key
Control data
Markdown type
Reference for sales price determination Number range
SAP AG 2003
When you create a markdown plan, you need to enter a markdown type. From the markdown type, the system proposes certain settings, which reduces the amount of data you have to enter. If a reference distribution distribution chain or reference site is not preset, the system does not propose any sales prices.
© SAP AG
IRT320
4-56
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Markdown Planning: Price History
Markdown Markdown rule rule Days SPChng 0 90 120
Sls%
100 75 50
50 30 15
Markdown Markdown plan plan Markdown plan: 0815 Summer season 2001 Valid from: 01. March 2001 Article
Current dist. chain SOrg R300 Retail USA DChnl R1 SB Store
Valid from Planned sales qty SPC Markd%
ActiveMargin
4711 4711 4711 4711
Men's suit, black Men's suit, black Men's suit, black Men's suit, black
01.03.01 01.03.01 30.05.01 29.06.01
1000 500 300 150
496,496,372,248,-
0 25 50
X
4712 4712 4712 4712
Ladies' blouse, size 38 Ladies' blouse, size 38 Ladies' blouse, size 38 Ladies' blouse, size 38
01.03.01 01.03.01 30.06.01 29.07.01
200 75 75 20
150,150,135,75,-
0 10 50
X X
44,4 50,3 33,7 0,5 37,4 44,0 25,4 -12,0
SAP AG 2003
The markdown rules define: - The period between the markdowns - The percentage of the orignal price at which the goods are to be sold in the various price phases - The total sales in percent that you expect per price phase For the men's suit in the above example, the markdown rule means: . - The item is offered for sale for the first time on March 1, 2001. - Within the first 90 days, you expect to sell 50% of your stock at the full price. - You then reduce the price of the item to 75% of its original price, and expect to sell 30% of your stock in this period. - One month later, you reduce the price further by 25%, to half the item's original price, and plan 15% of sales in this period.
© SAP AG
IRT320
4-57
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Documents: Topic Objectives
At the conclusion of this topic, you will be able to: Save information on sales price calculations in a pricing document
SAP AG 2003
© SAP AG
IRT320
4-58
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Documents
Contain all the information about a saved sales price calculation Validity period Creation date Change date User (created by, changed by) Automatic or manual generation
SAP AG 2003
© SAP AG
IRT320
4-59
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Documents
Advantages Documentation of sales price calculations Control of pricing documents (price dumping) Creating and saving sales price calculations / release strategy Prerequisite for Pricing worklist Canceling sales prices Euro conversion
SAP AG 2003
© SAP AG
IRT320
4-60
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Worklist: Topic Objectives
At the conclusion of this topic, you will be able to: Generate a pricing worklist that allows you to flag sales price condition records for processing later
SAP AG 2003
© SAP AG
IRT320
4-61
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Worklist: Process Article/vendor
Article/vendor
Site
200
200
Purchase price/conditions 140
- Regular vendor - Source of supply
120 100 80
Time
Pricing worklist
Sales price
?
SAP AG 2003
The sales prices calculated in retail pricing are usually based on the purchase price. The purchase price is determined using the purchase price calculation schema from the condition types that affect calculation, for example, the basic purchase price and vendor discounts. Other parameters that affect price calculation include the indicators Regular vendor and Source of supply in the article master. These are evaluated when the source of supply is being established. If the purchase price changes or if the parameters for supply source determination are modified, it is necessary to check the calculated sales prices with regard to the new margin. The pricing worklist function determines all the price calculations affected by pricing-relevant parameter changes.
© SAP AG
IRT320
4-62
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Worklist: Technical Information
Document indexes BAdI
Save SP calc.
S111
Pricing documents
T6I1
Filter
Comparison
Pricing worklist
T6I1 BAdI
Change to conditions
WIND
Modified conditions
T6I2A
Worklist of modified conditions SAP AG 2003
The entries in tables S111 and WIND are controlled using filters. These filters are maintained in Customizing. T6I2A determines the scope of changes for direct entry into the worklist. T6I1 contains the conditions that are to be checked for changes. You can also insert additional BAdIs, which limit the selection further by, for example, excluding certain article types. The pricing worklist function creates a list of the new price calculations in the form of pricing documents (pricing worklist). All calculations affected by the changes and the validity periods of modified calculations are taken into account. The entries in S111 are compared with those in WIND using the field 'VARKEY'.
© SAP AG
IRT320
4-63
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Worklist: Prerequisites Create pricing documents with document index Activate direct entry for creating the worklist Control automatic document adjustment for external procurement for internal procurement Define scope of change (check default values) Define filter values for changes to conditions using BAdI WIND_UPDATE Define filter values for document index creation using BAdI SPC_DOCINDEX_CONTROL (when saving pricing documents)
SAP AG 2003
© SAP AG
IRT320
4-64
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Unit Summary (1)
You are now able to: Calculate sales prices, taking into account various retail and cost conditions Explain the differences between one-step and two-step calculations Use price points Take account of material and handling costs for additionals when determining sales prices Explain how the pricing table is structured and define list variants
SAP AG 2003
© SAP AG
IRT320
4-65
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Unit Summary (2)
You are now able to: Explain the functions of price lists, pricing documents and the pricing worklist Name the price determination types and sequences in both Purchasing and Sales Enter competitor prices, define pricing strategies and perform sales price calculations based on these Explain what the market-basket pricing function does Use markdown planning to sell seasonal goods at reduced prices in line with a predefined plan
SAP AG 2003
© SAP AG
IRT320
4-66
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing Exercises Unit: Pricing
At the conclusion of this exercise, you will be able to: • Calculate sales prices, taking into account various purchasing and sales conditions, as well as understand the different purchasing and sales price determination sequences. • Perform one-step and two-step calculations • Define price points, list fields and list variants • Enter competitor prices, define pricing strategies and perform sales price calculations based on these • Perform a market-basket price calculation • Create a markdown plan • Explain the functions of price lists, pricing documents and the pricing worklist 1. 1
Assign planned markups to your distribution chains. 1-1
The following planned markups are maintained for the distribution chain for the distribution center R300/R5 and store distribution chain R300/R1: Distribution chain of distribution center: 10% Store distribution chain:
30%
Display the planned markups in the system and search for the corresponding entries for merchandise category TMC2## of your article TA14##. 2
Definition and assignment of a price point group. 2-1
Define a price point group EPGR## and give it the description “Price point group ##”. The currency is USD; the rounding rule is to be 50%. Save your entries.
© SAP AG
IRT320
4-67
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-2
Assign the following price point areas to your price point group EPGR##: First price
Last price
Increment
0,09
9,99
0,10
10,99
99,99
1,00
109,99
999,99
10,00
Save your entries. 2-3
Now assign your price point group to the merchandise category of your article TA14## and to your store distribution chain R300/R1. Sales organization:
R300
Distribution channel:
R1
Merchandise category:
TMC2##
Price point currency:
USD
Price point type:
01 (final price)
Price point group:
EPGR##
Save your entries. 3
One-step calculation 3-1
Create a price calculation for article TA14##. Article:
TA14##
Sales organization:
R300
Distribution channel:
R1 and R5
Which vendors are found for distribution chains R300/R1 and R5? ___________________________________________________________ Why were these vendors determined? ___________________________________________________________ Does the final price for the stores differ from that for the distribution centers and if so, how? ___________________________________________________________ Save your calculation.
© SAP AG
IRT320
4-68
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
4
Calculate your article prices taking account of additionals 4-1
You want to take into account the costs of additionals for your article TA05## when determining the purchase price. To do this, you assign additionals TA40## and TA41## to article TA05## in the first step. Set the control indicator for the calculation to make sure that the material and handling costs are taken into account in the calculation. Use the additionals procedure 0004 and sales unit PC. Save your entries.
4-2
In the next step, you create condition records (condition type KAD0 and KAD1) for the additionals. Additionals:
TA40##
Material costs:
0.07 USD
Handling costs:
0.10 USD
Additionals
TA41##
Material costs:
0.05 USD
Handling costs:
0.10 USD
4-3
Before you create a calculation for your article TA05##, check whether condition types KAD0 and KAD1 exist in your calculation schema ZISR##.
4-4
Create a calculation: Article:
TA05##
Sales organization:
R300
Distribution channel:
R1 and R5
Use the analysis to check which conditions are used. DO NOT save your calculation
5
Two-step price calculation 5-1
Change the article master for your article TA05## to enable you to perform a two-step calculation for the same distribution chains. Which changes to the article master are required? ___________________________________________________________
© SAP AG
IRT320
4-69
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-2
Create a calculation for your distribution center. Article:
R300
Distribution channel:
R5
Which price has been calculated? _____________________________________________________ Do not save your calculation. 5-3
Create a calculation for your store. Article:
TA05##
Sales organization:
300
Distribution channel:
R1
Which price has been used as the purchase price? _____________________________________________________ Why was this price determined? _____________________________________________________ Save your calculation. 5-4
Calculate the price for your distribution center and your store. Article:
TA05##
Sales organization:
300
Distribution channel:
R1 and R5
Change the distribution center purchase price to 300.00 USD. What happens when you change the purchase price manually? _____________________________________________________ Which sales price was found for the distribution center? _____________________________________________________ Save your calculation. 5-5
Now calculate the sales price for your store only. Article:
TA05##
Sales organization:
300
Distribution channel:
R1
Which price has been used as the purchase price? _____________________________________________________ Do not save your calculation.
© SAP AG
IRT320
4-70
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-6
Finally, create a calculation for your distribution center and your store. Article:
TA05##
Sales organization:
300
Distribution channel:
R1 and R5
Which price has been used as the purchase price for the store? _____________________________________________________ Save your calculation. 6
Price calculation for a sales set 6-1
Now, you want to determine the price of a sales set based on the purchase price of the components. Which purchase price determination sequence supports this calculation? ___________________________________________________________
6-2
Check this purchase price determination sequence in Customizing. What does this purchase price determination sequence imply? ___________________________________________________________
6-3
Now calculate the price for your set using the two-step method. Article (Set):
TA18##
Sales organization:
300
Distribution channel:
R1 and R5
Which vendor was found? ___________________________________________________________ Which purchase price was determined? ___________________________________________________________ Why could no vendor or purchase price be determined? ___________________________________________________________
© SAP AG
IRT320
4-71
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
7
Price calculation for perishables 7-1
Perform a calculation for your perishable article TA19##. Note that this perishable article is supplied by several vendors at different prices. Article (perishables)
TA19##
Sales organization:
300
Distribution channel (DC):
R5
Which purchase price determination sequence do you use? ___________________________________________________________ 7-2
Check this purchase price determination sequence in Customizing. What does this purchase price determination sequence imply? ___________________________________________________________ Why could no vendor or purchase price be found? ___________________________________________________________ Change the proportions for various vendors. How does this change affect the purchase price? ___________________________________________________________
8 You make Customizing settings so that you can calculate sales prices on the basis of competitor prices. 8-1
Define price entry type PA## with the description “Price entry type IRT320-##” by copying price entry type 0001. Save your entries.
8-2
Next, enter a new pricing strategy ##+40 (group number + 40) by copying existing pricing strategy 01 and call it “IRT320-##; 10% above the cheapest”. Change the pricing strategy to ensure that the suggested price is 10% above the cheapest price. Ensure that the sales prices are rounded to price points.
8-3
Copy the list variant R1 to create a new list variant ##+20 (group number + 20) and call it “List variant IRT 320-##”.
8-4
Copy the pricing procedure WWS004 to create a new pricing procedure ZMBW## with the description “Competitor IRT 320-##”. Check whether condition type VKPM exists in the pricing schema, and if so, whether requirement 85 is assigned to it.
© SAP AG
IRT320
4-72
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
8-5
Create a new pricing type MB## as a copy of the pricing type US04 and give it the description “Competitor 320-##”. Change the control data for the pricing procedure in accordance with 8-4.
8-6
Now assign your new pricing type MB## to your distribution chain (store) R300/##+70 (group number + 70).
8-7
Make the settings for each pricing table list field and your pricing procedure ZMBW##. To do this, copy all the entries from the pricing procedure WWS004. Make sure that transfer type A is set for the VORPR list field.
8-8
9
Assign the relevant condition tables to the different pricing levels for the appropriate condition types of your pricing procedure ZMBW##. To do this, copy all the entries from the pricing procedure WWS004.
Calculate your prices on the basis of competitor prices. 9-1
Create a competitor class MBWK## with the description “Competitor class IRT320##.” Class:
MBWK##
Class type:
011
Save your entries. 9-2
Assign your competitors TC70##, TC71##, and TC72## to your new competitor class MBWK##. Save your entries.
9-3
9-4
Now maintain your competitor pricing data at store/merchandise category level. Store:
1##
Merchandise category:
TMC1##
Pricing strategy:
##+40
Class type:
11
Competitor group:
WK##
Create the following price entry list. Price entry type:
##
Competitor group:
WK##
Sales organization:
300
Distribution channel (store): #+70 Store: © SAP AG
1## IRT320
4-73
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
TA15## TA16## TA17##
TC70## 185,33 325,66 379,15
TC71## 195,25 315,50 364,35
TC72## 179,21 329,33 359,75
Activate the prices and save your entries. 9-5
Create a calculation, taking into account the competitor prices you have entered. Sales organization:
300
Distribution channel (store):
##+70
Store:
1##
Article:
A15##, TA16##, TA17##
Purchase price determination sequence:
1
Sales price determination sequence:
1
List variant:
##+20
Save your calculation. 10 You want to perform a market-basket price calculation. 10-1
To do this, you need to define a market-basket pricing type ZK## by copying marketbasket pricing type WKUS. Name your market-basket pricing type Market-basket IRT 320-## and use your own list variant.
10-2
Create the market-basket price calculation:
© SAP AG
Description:
Market-basket price calc. IRT320-##
Market-basket pricing type:
ZK##
Article:
TA15##, TA16##, TA17##
Sales organization:
R300
Distribution channel:
## +70
Site:
T1##
IRT320
4-74
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
11 You want to create a markdown plan 11-1
Markdown type
MDT
Sales organization
R300
Distribution channel
R1
Site
T1##
Article
R100033
Valid from
1. of next month
11-2
Give the plan the number AP## and the description “T-shirt markdown group##”.
11-3
Enter the following planned sales quantities:
11-4
Variant
Planned sales qty
red, small
750
red, medium
900
blue, small
1500
white, small
1800
Go to detailed planning. What are the final prices together with their validity periods and the planned sales quantity for the blue t-shirt, size small? Final price in USD
Planned sales qty
Valid from
11-5
Why can you not change the sales prices of the individual variants here? _________________________________________________ _________________________________________________ Save the markdown plan. Go to change mode for the markdown plan.
11-6
© SAP AG
Go to detailed planing and select the first and second price phases for generic article R100033. IRT320
4-75
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
11-7
Activate these two price phases.
11-8
Go back and save the sales prices you created.
11-9
Open a second session and display the prices you just generated in the price overview in Pricing. Make the following selection: Article Sales organization Distribution channel Site Validity List group
R100033 R300 R1 T1## From today to the end of the current year B
11-10 Which prices are displayed and why? _________________________________________________ _________________________________________________ 11-11 Go back to change mode for your markdown plan and activate the third price phase. Now select the same data and go to the price overview.
© SAP AG
IRT320
4-76
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Pricing: Solutions Unit: Pricing
Introduction to solutions
The solutions are based on the following assumptions: •
You are on the SAP Retail initial screen (transaction W10T). You should enter this transaction as the start menu in your user parameters.: System → User profile → Own data, on the 'Defaults' view, enter ‘W10T’ as the StartMenu.
•
If the term Retailing is written before a path, you are in the SAP Retailing menu, the SAP Retail application menu (transaction W10M). You get here from SAP Easy Access SAP Retail by choosing Logistics → Retailing
•
If the term IMG is written before a path, you are in the Implementation Guide of the R/3 System, where you can make Customizing settings. You get here from SAP Easy Access SAP Retail by choosing Tools → AcceleratedSAP → IMG → Edit project → Goto → SAP Reference IMG (F5) or the transaction /NSPRO → F5
1-1
Retailing: Master data → Pricing → Conditions → Planned markup → Distribution chain → Display
2-1
IMG: Logistics - General → Retail Pricing → Sales Price Calculation → Price Point Group → Define Price Point Group and Assign Price Point Ranges
2-2
Button: [New Entries] Select price point group; double-click on “Assign Price Point Ranges”
2-3
© SAP AG
IMG: Logistics - General → Retail Pricing → Sales Price Calculation → Price Point Group → Assign Price Point Group to Organizational Level/Merchandise Group
IRT320
4-77
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
3-1
Retailing: Master data → Pricing → Price calculation → Create The same vendor was found for both distribution chains. The settings for supply source determination mean that both the distribution centers and the stores are supplied directly from the external vendor. The prices differ due to the different planned markups and to price point rounding at store level.
4-1
Retailing: Master data → Article data → Article → Change From the basic data view for the article, branch to the additional data and to the additionals tabstrip for assigning the additionals to the article.
4-2
Retailing: Master data → Conditions/arrangements → Conditions: Purchasing → Other → Create
4-3
IMG: Materials Management → Purchasing → Conditions → Define Price Determination → Define Calculation Schema
4-4
Retailing: Master data → Pricing → Price calculation → Create
5-1
Retailing: Master data → Article data → Article → Change Set source of supply in the Logistics Store View to value 2 or 4 (procurement via DC)
5-2
Retailing: Master data → Pricing → Price calculation → Create Different prices depending on the vendor: 149.47 USD, 159.32 USD
5-3
See above. Price: 149.47 USD, 159.32 USD The issue price for the distribution center is calculated in the background.
5-4
The basic purchase price in the store changes in the same way. 285.32 USD, 300.32 USD, see above
5-5
285.32 USD, 300.32 USD, see above
5-6
149.47 USD, 159.32 USD, see above
6-1
Purchase price determination sequence 02
© SAP AG
IRT320
4-78
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
6-2
IMG: Logistics - General→ Retail Pricing → Sales Price Calculation → Maintain Purchase Price Determination Sequence Purchase price determination sequence 02 means that SP determination is performed first using the schema in accordance with standard schema determination, and then, when no purchase price is found, purchase price determination is performed using the components of the set.
6-3
Retailing: Master data → Pricing → Price calculation → Create Neither vendor nor purchase price is displayed. No purchase price exists for the set article, the price is determined by adding together the prices of the components, which can even be procured from different vendors.
7-1
Retailing: Master data → Pricing → Price calculation → Create Purchase price determination sequence 03
7-2
IMG: Logistics - General→ Retail Pricing → Sales Price Calculation → Maintain Purchase Price Determination Sequence Purchase price determination sequence 03 means that, first, a vendor mixed price is determined, providing that the article concerned is a perishable article in a distribution center. If no price is found here, the purchase price is determined according to the standard. The price is determined based on the purchase price for the different vendors. The net/net purchase price changes according to the proportions involved.
8-1
IMG: Logistics - General→ Retail Pricing → Competitor Prices → Maintain Price Entry Types
8-2
IMG: Logistics - General→ Retail Pricing → Competitor Prices → Maintain Pricing Strategies End rule B, Percentage Rate 10%
8-3
© SAP AG
IMG: Logistics - General→ Retail Pricing → Sales Price Calculation → Define List Variant and Assign Items
IRT320
4-79
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
8-4
IMG: Sales & Distribution → Basic Functions → Pricing → Pricing Control → Define and Assign Pricing Procedures Cursor on “Maintain pricing procedures” Button: [Choose]
8-5
IMG: Logistics - General→ Retail Pricing → Sales Price Calculation → Maintain Pricing Type
8-6
IMG: Logistics - General → Retail Pricing → Sales Price Calculation → Assign Pricing Type /Reference Site to Organizational Level
8-7
IMG: Logistics - General → Retail Pricing → Sales Price Calculation → Control Data for Pricing Table and Data Backup Place cursor on “Control per Sales Price Calculation Schema and List Field” Button: [Choose]
8-8
IMG: Logistics - General → Retail Pricing → Sales Price Calculation → Control Data for Pricing Table and Data Backup Cursor on “Assignment of Condition Tables” Button: [Choose]
9-1
Retailing: Master data → Classification system, Retail → Class → Create
9-2
Retailing: Master data → Edit customers → Grouping → Classification → Classification → Assign Objects/Classes to Class Button:
[Only New Assignments]
Radio button: Customer Button: 9-3
[Enter]
Retailing: Master data → Site data → Site → Change Button: [Merchandise categories]
9-4
Retailing: Master data → Pricing → Conditions → Price entry → Create
9-5
Retailing: Master data → Pricing → Price calculation → Create
10-1
IMG: Logistics - General→ Retail Pricing → Market-Basket Pricing → Maintain Market-Basket Pricing Type
10-2
Retailing: Master data → Pricing → Market-basket price calculation → Create
© SAP AG
IRT320
4-80
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
11-1
Retailing: Master data → Season → Markdown Plan → Create
11-2
Maintain the planned quantities for the relevant variant.
11-3
[Detailed Planning] tab Final price in USD
Planned sales qty
Valid from
without PPA
1. of next month
14.99
14.99
975
90 days later
11.24
10.99
375
7.50
7.49
150
Another 30 days later
with PPA
11-4
This depends on the pricing profile maintained in the basic data for the article. There are three options: - Price of variants always the same as price of header article – System proposes price of header article as price of variants – Variants calculated differently without header article price being proposed
11-5
In the relevant line, set the flag in the first column
11-6
[Activ. sales prices] button
11-7
Confirm the dialog box, if one appears
11-8
Retailing: Master data → Pricing → Conditions → Price overview
11-9
All the prices that are valid in the selected period are displayed.
11-10 See above
© SAP AG
IRT320
4-81
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management and Valuation
Contents: Types of inventory management Valuation procedures Sales price valuation Revaluation Split valuation
SAP AG 2003
© SAP AG
IRT320
6-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management and Valuation: Objectives
At the conclusion of this unit, you will be able to: Explain the difference between the various kinds of inventory management Explain the controls for value-based inventory management and revaluation
SAP AG 2003
© SAP AG
IRT320
6-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management and Valuation: Business Scenario
Your company has decided to carry out inventory management at value-only level for certain merchandise categories. However, in some cases you want to allow exceptions to this rule. As your company is running more and more promotions, you want to split your stock up into standard stock and promotional stock and valuate it accordingly.
SAP AG 2003
© SAP AG
IRT320
6-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Diagram
1 2 3
Course Overview Elements of the Condition Technique Conditions in Purchasing
4 5 6
Pricing
Promotion Inventory Management and Valuation
SAP AG 2003
© SAP AG
IRT320
6-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management: Types of Inventory Management
Inventory Management Article Article type type
Updating
Quantity Quantity and and value value basis basis
Stock Stock quantity quantity Stock Stock value value G/L G/L accounts accounts Financial Financial and and Cost Cost Accounting Accounting
Quantity Quantity basis basis
Stock Stock quantity quantity Goods movement
Value Value basis basis
Stock Stock value value (Stock (Stock quantity) quantity)
None None of of the the above above
No No updating updating
SAP AG 2003
If inventory management for an article is carried out on a quantity and value basis, the stock quantity, stock value, and G/L accounts in Finanical Accounting and Cost Accounting are usually updated. If inventory management is on a quantity basis only, no accounting data can be maintained in the article master record. When a goods movement is posted, only the stock quantities are updated. The stock value, article, and G/L accounts in Financial Accounting and Cost Accounting are not updated. If inventory management is on a value basis only, quantity information may be available. The sales value must be managed for these articles. A valuation at purchase price and sales price is carried out for each goods movement. As a result, stores can avoid inventory management on an article basis, for example.
© SAP AG
IRT320
6-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management: Special Article Categories
Structured articles
Generic articles
Variant Unit of measure
Inventory Management
Component Component
Generic article
Empties
Logistics variants Variant 001
Variant 002
SAP AG 2003
A generic article has a number of variants with different colors or sizes for example. It is possible to process these variants directly in goods movements. The use of logistics variants enables you to manage the stock of an article in a distribution center with different logistics units of measure. The various units of measure for an article are created as logistics variants of a generic article. Structured articles consist of a header article and a bill of materials containing the components. Sets, prepacks, and displays are examples of structured articles. In Inventory Management, it is possible to split the header article into its components or to form a header article from its components. Empties components can be assigned to a full product in a bill of material (BOM). In certain processes, the system automatically includes the empties components for the full product.
© SAP AG
IRT320
6-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management: On a Value Basis Site Site Hierarchy article: Perishables
Merchandise category: Fruit - SP valuation active - Value-only article created and assigned - Profile for inventory management on val.basis - Sales price conditions
SAP AG 2003
Store004
Merchandise category article: Fruit
Group article: Tropical fruits
Group article: Nuts
Store 003
Store 003
Store 002 Store 003
Qty & value basis: Apples, pears
Qty & value basis: Coconuts
Store 001
Store 002
When inventory management is carried out on a purely value basis, goods movements are not posted on a quantity and value basis. Values, and not quantities, are updated for a value-only article. The system determines the value-only article for which the data is posted using value-only article determination. The value-only article can be automatically created for each merchandise category. To obtain a greater level of detail within a merchandise category for value-based inventory management, several group articles can be created for the merchandise category. It is also possible to post individual articles on a quantity and value basis in one of these merchandise categories, for example if the article is expensive. A hierarchy article can be created for a node of the merchandise category hierarchy. This then includes all merchandise categories below this level in the hierarchy. If a store decides to carry out merchandise-category-independent inventory management, it must decide the level in the hierarchy at which this is to take place. If this is not done, nonsensical sales figures will result, particularly in statistics used to compare stores.
© SAP AG
IRT320
6-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Value-Based Inventory Management: Profiles
R1100 Groceries Site Site
R1120 Perishables
Profile f. valuevalue-based IM: 0001 on article basis
R1121 Fruit
Apples
Pears
Hazelnuts
Walnuts
Coconuts
R1122 Vegetables
Kiwis
Bananas
SAP AG 2003
Prerequisites for inventory management on a value basis: - Sales price valuation is activated for the site in question. - The value-only articles have been created. - The profiles have been created and assigned to the sites. - Exceptions are defined in site maintenance, if required. The eight profiles in the standard system cannot be changed. Each of these profiles can be copied (if you do this, use a customer name space). The value-only article flag can be selected or deselected in the copy. As a result, each value-only article can be used at any level of the hierarchy.
© SAP AG
IRT320
6-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Value-Based Inventory Management: Profiles
R1100 Groceries Site Site
R1120 Perishables
Profile f. valuevalue-based IM: 0003 merch. merch. cat. article
R1121 Fruit
Merch. Merch. cat. article: Fruit
Apple
Pears
Hazelnuts
Walnuts
Coconuts
R1122 Vegetables
Kiwis
Bananas
SAP AG 2003
© SAP AG
IRT320
6-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Value-Based Inventory Management: Profiles
R1100 Groceries Site Site
R1120 Perishables Perishables hierarchy article
Profile f. valuevalue-based IM: 0005 Hierarchy article level
R1121 Fruit
Apples
Pears
Hazelnuts
Walnuts
Coconuts
R1122 Vegetables
Kiwis
Bananas
SAP AG 2003
© SAP AG
IRT320
6-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Value-Based Inventory Management: Profiles
R1100 Groceries Site Site
R1120 Perishables
Profile f. valuevalue-based IM: 0004 Merch. Merch. cat. article with exceptions
R1121 Fruit
Merch. Merch. cat. article: Fruit Group article Tropical fruits
Apples
Pears
Hazelnuts
Walnuts
Coconuts
Kiwis
Bananas
SAP AG 2003
© SAP AG
IRT320
6-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activities Relevant for Valuation
Company Company Company
Invoice Purch.order Invoice
Company Company Company
M
Invoice Invoice Invoice
xyz
Invoice verification
Goods movement
Valuation Physical inventory XXL
M
Yellow
M
X
20,B-lueXL2
0
39,90 3 ,9,9 0
49 21 4921 1172 11
Price change
72
SAP AG 2003
Article valuation is not a separate area as most of the functions are carried out automatically. Depending on the organization, the activities that are performed manually are part of the areas of inventory management, invoice verification, or accounting. Valuation creates a link between Logistics and FI by accessing and updating G/L accounts. The value of the article stock is calculated using the simple formula: Stock value = Stock quantity * Article price. Therefore, the stock value changes if the stock quantity or the article price changes. The calculation can be based on the purchase price and the sales price (in pricing and valuation, the sales price is sometimes referred to as the ‘retail price’. Both the determination of the lowest value and the LIFO valuation support SAP Retail Valuation for balance sheets.
© SAP AG
IRT320
6-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Valuation Procedures
Moving average price price
1 Initial situation
2
Goods receipt Quantity 100 Value 150.00
Standard price
Article Site Price control
4711 0001 V
Article Site Price control
4712 0001 S
Total stock Total value MA price
100 100.00 1
Total stock Total value Standard price
100 100.00 1
Total stock Total value MA price
200 250.00 1.25
Total stock Total value Standard price
200 200.00 1
Price difference 50.00
SAP AG 2003
The type of price control used for an article is defined in the Accounting view when the master record is created. In the case of the moving average price, all receipts are posted with the receipt value. As a result, the price in the article master record is always adjusted in line with the cost price. The price displayed in the article master is rounded up/down. The exact price (stock value / stock quantity) is always used for the valuation of goods movements. Price differences only occur in exceptional cases. In the procedure using the standard price, all goods movements are valuated using the standard price. If deviations occur, they are posted to the price difference account.
© SAP AG
IRT320
6-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Sales Value
Purchase price
Sales price calculation
Text Gross PPrice Discount -5%
1.00 0.95
Text Net PP 0.95 Markup +18% AST +15%
1.12 1.29
Conditions
Article Article
Goods receipt
Text Article Quantity
4711 100
Article master 4711 Total qty Total value Total sales price val. val.
100 95.00 129.00
SAP AG 2003
In the article master, the sales value can be based on the current stock quantity, if you make the appropriate setting for the valuation area. The system automatically updates the sales value when goods movements occur. At goods receipt, the sales value is taken from the purchase order, determined by the system, or entered manually. The system can determine the sales value if sales price conditions are maintained for the article. You can create or update these conditions using the sales price calculation. You can use the information system to analyze the information relating to the sales values for stocks and goods movements. The following indicators must be maintained accordingly in the site master data: - Sales price valuation - Revaluation profile - Profile for inventory management on a value basis
© SAP AG
IRT320
6-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Sales Price Change
Site Site 0001 0001 Article Article 4711 4711 Qty Moving ave. price Cost value Sales price Sales value Affecting margins
Moving ave. price Cost value Sales price Sales value
5.00 500.00 8.00 800.00
100 5.00 500.00 10.00 1000.00
new new price 8.00
Not affecting margins
Moving ave. price Cost value Sales price Sales value
4.00 400.00 8.00 800.00
Stock 100.00 FI
SAP AG 2003
A sales price change that affects margins has no effect in FI as the valuation price of the article remains unchanged. Alternatively, you can make a sales price change that does not affect margins. Here, the valuation price of the article is changed in such a way that the margin remains constant. In doing this, you create an accounting document and post data to the relevant stock account. It is also possible to change the valuation price only. This is usually done at the end of the year when balance sheets are created. In Customizing, you can define reasons for revaluation.
© SAP AG
IRT320
6-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Revaluation Profiles
Stock counting
X
•Count affected articles before revaluation?
Site Site Revaluation profile
Promotion valuation
X
•Valuate total stock during promotion period with promotion sales price? Local markdowns
X
•Carry out (automatic) revaluation after local markdown? Not affecting margins
X
•Value should not affect margins? SAP AG 2003
Valuation profiles result from a combination of the four flags shown in the slide. All 16 profiles are supplied. Stock counting If you select this indicator, the articles affected must be counted before revaluation if inventory management is carried out on a quantity and value article basis. If inventory management uses a valueonly article, quantity counting is mandatory, which is why this indicator only relates to inventory management on a quantity and value basis. Promotion valuation This indicator only applies if you do not use split valuation in promotions. If you select this indicator, the total stock of the articles involved in the promotion are valuated at the promotion sales price during the period of the promotion. This means that a revaluation takes place at the start of the promotion so that a promotion price is used, and a revaluation back to the standard sales price takes place at the end of the promotion period. Local markdowns are price changes in individual sites that are not entered in the sales price conditions of the central SAP System. If you select this indicator, you can then carry out a revaluation following a local markdown. Revaluation can take place online or automatically in POS inbound processing.
© SAP AG
IRT320
6-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Split Valuation
Valuation Valuation area area
Valuation Valuation category category
Valuation Valuation type type
Global
Local
Switzerland 0001
Origin Italy Own
0002
Source External RNormal
R300
Site Site
Retail Standard Standard Retail Retail valuation valuation category category
RAktion
SAP AG 2003
If split valuation is active, stocks of an article can be valuated separately. If you want to carry out split valuation for an article, you enter a valuation category in the accounting data of the article. This defines which valuation types can be specified. A valuation type characterizes one of the possible types of stock for a certain valuation category. Default valuation types can be defined for a valuation category. This affects the valuation type that is to be entered in a purchase order. When setting up valuation categories and valuation types, you first define them as global, that is to say, independent of a valuation area. You then assign the valuation categories to valuation areas. As a result, category-specific data (in particular the valuation types assigned to the category) are valid locally. Local valuation categories and types can be changed. When you assign a valuation category to an organizational unit, all valuation types that are globally active for the valuation category are automatically assigned to this organizational unit.
© SAP AG
IRT320
6-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Valuation: Split Valuation in Retail
Valuation area 0001 Article 4711 Valuation category R Quantity 1000 Moving ave. price 5.40
Site 0001 Article 4711 Quantity 1000
Site Site
Stor. loc. 0001 Article 4711 Quantity 1000
Storage Storage location location Stock for valuation type
RAKTION Quantity 300
Valuation type RNORMAL
Valuation type RAKTION
Quantity 700 MvgAve. price 6.00
Quantity 300 MvgAve. price 4
RNORMAL Quantity 700
SAP AG 2003
Split valuation enables you to manage different parts of the stock of an article at different prices. In SAP Retail this is used to differentiate between promotion stock and standard stock. This function can be used for both distribution centers and stores. Each valuation type has its own valuation record, which contains the valuation price and other control information. In addition, for each storage location, different parts of stock are managed using the relevant valuation type. If split valuation is active, it is necessary to state which part of stock is affected by the relevant transaction for each goods movement.
© SAP AG
IRT320
6-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
You can valuate your stock using the purchase price and sales price. You can use valuation profiles for each site to define the level at which you want to manage inventory. Above article level, you can only manage stock on a value basis. Stocks valuated at sales prices can be revaluated in part or full. This is controlled by revaluation profiles, which you must assign to your sites. You can use split valuation in SAP Retail to differentiate between standard stock and promotion stock. SAP AG 2003
© SAP AG
IRT320
6-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management and Valuation: Exercises Unit: Inventory Management and Valuation Topic: Stock Revaluation At the conclusion of this exercise, you will be able to: • Explain the effects of a change to the retail price on the stock managed on value-only articles. Your store manages stock for the perishables merchandise category on a value-only basis at merchandise category article level.
1-1
Before carrying out the revaluation, check the relevant settings for the store. 1-1-1 Which profile for value-only inventory management is assigned to store T2##? _________________________________________________ 1-1-2 Which valuation profile is entered, and what effect does this profile have if the sales price is changed? _________________________________________________ _________________________________________________ _________________________________________________ 1-1-3 How is inventory management carried out in merchandise category R1121 Perishables? _________________________________________________
© SAP AG
IRT320
6-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
1-2
What is the procedure for articles for which stock is managed on a quantity and value basis? _______________________________________________________ _______________________________________________________ _______________________________________________________
1-3
For store T2##, find out the value of the stock managed on a value-only basis for merchandise category R1121. Stock:_________________________________________________
1-4
Change the value of the stock by increasing the retail price. 1-4-1 In the price calculation, increase the retail prices (= current price) for articles TA22## and TA09## by 0.50 USD. Article Sales organization Distribution channel List group
TA22##, TA09## R300 R1 B
1-4-2 Have the sales price change affect stock. Count quantity
TA22##
100 pc
Count quantity
TA09##
100 lb
1-4-3 How has the stock value changed? New stock:____________________________________________
© SAP AG
IRT320
6-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inventory Management and Valuation: Solutions Unit: Inventory Management and Valuation Topic: Stock Revaluation The solutions are based on the following assumptions:
1-1
•
You are on the SAP Retail initial screen (transaction W10T). You should enter this transaction as the start menu in your user parameters.: System → User profile → Own data, on the 'Defaults' view, enter ‘W10T’ as the StartMenu.
•
If the term Retailing is written before a path, you are in the SAP Retailing menu, the SAP Retail application menu (transaction W10M). You get here from SAP Easy Access SAP Retail by choosing Logistics → Retailing
•
If the term IMG is written before a path, you are in the Implementation Guide of the R/3 System, where you can make Customizing settings. You get here from SAP Easy Access SAP Retail by choosing Tools → AcceleratedSAP → IMG → Edit project → Goto → SAP Reference IMG (F5) or the transaction /NSPRO → F5
Prerequisites 1-1-1 Value-Based Inventory Management Retailing: Master data → Site data → Site → Change Site
T2##
IM Profile
0002
1-1-2 Revaluation profile tabstrip Revalua. profile
Valuation/Inv. Mgmnt 5
When you change sales prices, you must count the stock before carrying out the revaluation. A sales price revaluation is carried out for local markdowns. The changes should affect the margins. 1-1-3 Merchandise category R1121 Button Column M
© SAP AG
Merchandise categories Indicator: selected (merchandise category-based)
IRT320
6-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
1-2
Article-based inventory management In article-based inventory management, the quantity is recorded and updated in the system, so a stock count is not required before the stock revaluation.
1-3
Stock of merchandise category R1121 in T2## Retailing: Merchandise logistics → Inventory management → Environment → Stock → Value-only article
Field name or data type
Values
Merchandise category
R1121
Site
T2##
The current value should be $596. 1-4
Stock change 1-4-1 New sales prices Retailing: Master data → Pricing → Price calculation → Create Field name or data type
Values
Article
TA22##, TA09##
Purchasing organization
R300
Distribution channel
R1
List group
B
Save the changes. 1-4-2 To affect stock Retailing: Master data → Pricing → Environment→ Value assignment → Valuation at retail → List display of retail price changes Retailing: Master data → Pricing → Environment→ Value assignment → Valuation at retail → Partial revaluation at retail
© SAP AG
IRT320
6-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Field name or data type
Values
Site
T2##
Reasn
R001
Field name or data type
Values
Quantity in entry TA22##
100 pc
Quantity in entry TA09##
100 lb
1-4-3 New stock value Retail: Merchandise logistics → Inventory management → Environment → Stock → Value-only article
Field name or data type
Values
Merchandise category
R1121
Site
T2##
New value: $696.
© SAP AG
IRT320
6-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Example Scenarios Store plan
Inventory Planning
Business plan
Integration in business processes
Merchandise and store plan
MAP
SAP BW Enterprise
Store
Merchandise category
Article
SAP AG 2001
In this training course, different example scenarios will be developed and presented. These scenarios are used to represent the different functions and configuration option which exist in SAP Retail's Merchandise and Assortment Planning (MAP) tool. All the examples converted in this training course can be used as templates with which participants can later develop their very own planning scenarios.
© SAP AG
IRT350
8-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
MAP Functions I Clear user guide
Advanced processes
Document management system
Authorizations Different planning currencies Different planning key figures
USD
398 157
005
DM
EUR
SAP AG 2003
The Merchandise and Assortment Planning (MAP) component in SAP Retail offers the following functions of a flexible planning system: A graphical network plan provides a clear user guide. You can use MAP to create planning data and map entire planning processes to your system. MAP is linked to SAP's Document Management System allowing you to store Office documents and graphics for reference purposes. Authorization objects ensure that only certain associates have access to the planning system. Planning data can be created in different planning currencies. SAP provides a large number of predefined planning key figures that you can use in MAP.
© SAP AG
IRT350
8-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
MAP Functions II Plan versions B
Advanced hierarchies A
Value - quantity conversion
Flexible entry screens UM WE (U M -W E ) / U M
Time-based granularity
1 000 800 0 ,2
UMS
90
WE 1000 2000 3000
80 70 60
40 30 20 10 0
50 40 Jan
F e b r.
M ä rz
A p ril
SAP AG 2003
Plan
500 1400 2000
UMS-WE 500 600 1000
Actual
The Merchandise and Assortment Planning (MAP) component in SAP Retail offers the following functions of a flexible planning system: Using plan versions enables you to manage different data records for different planning types of planning in the system. Planning can be done at different levels (planning characteristics) in complex planning hierarchies. Data is stored at the lowest possible planning level so that data consistency is guaranteed when data is aggregated or disaggregated between different planning levels. MAP allows you to create planning data on a value-basis or quantity-basis or convert values to quantity. The total planning you create in your system can be adjusted on a time-basis and allocated to different time periods. You can configure your entry screens so that they match your requirements. You can, alternatively, integrate Microsoft Excel in your SAP application.
© SAP AG
IRT350
8-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
MAP Functions III Business Information Warehouse
Interfaces
Workflow
Alloc. table/ Promotion Store Store A A
Store Store B B
Listing
Assortments Assortments
Special Special buy buy -20 -20 % %
SAP AG 2003
The Merchandise and Assortment Planning (MAP) component in mySAP Retail supports the following functions: You can create promotions and allocation tables in MAP. You can use the SAP Business Information Warehouse (SAP BW) as your actual data source for planning. SAP BW Release 2.0B contains suitable content (for example, predefined Queries) for Best Practice Scenario 1_SAP. To coordinate the sequence of the individual planning activities, thereby ensuring the authorized associate runs the planning activity at the correct time and the next associate continues the planning, MAP supports the SAP Business Workflow. You can use your planning data to create article master data (as well as generic articles and their variants). You can use the listing interface to list articles in assortments.
© SAP AG
IRT350
8-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Objectives
You are now able to: Configure the correct Customizing settings for Merchandise and Assortment Planning (MAP) Recognize the links and relations between the individual MAP components Use MAP in business processes Create your own planning scenarios using MAP and run the resulting planning processes
SAP AG 2003
© SAP AG
IRT350
8-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Performance Map SAP Service Marketplace under SAPNet alias performancemap Released for for customers and partners (free of charge) Central point of access for performance-related topics Divided up in line with the mySAP.com components (contains core and industry-specific areas, plus cross-component and technical blocks) Gives recommendations and suggestions, detailed information, documents and links, and a direct link to relevant notes and collective notes in OSS Continually updated and enhanced (history) Available in English (some notes and detailed documentation are also translated into other languages).
SAP AG 2003
You can find the SAP Service Marketplace under the alias performancemap by entering the following address: http://service.sap.com/performancemap
© SAP AG
IRT350
8-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Best Practices for mySAP Retail ...
... Offer you "Best Practice" configuration of mySAP Retail in a number of versions for the following sectors: • • • •
Fashion (including apparel, textiles, footwear) * Food (discounters, supermarkets, hypermarkets, convenience stores) * Wholesale (technical wholesale, mail order, Internet) ** Hardlines (specialists in building materials, electrical items, toys, and so on) **
... Are an implementation tool combining AcceleratedSAP (ASAP) and Preconfigured Systems (PCS), are free of charge and can be installed in a day.
* already available
** planned
SAP AG 2003
For more information on SAP Best Practices for mySAP Retail, see service.sap.com –> Industry Solutions -> Retail on the SAP Service Marketplace.
© SAP AG
IRT350
8-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Best Practices for mySAP Retail ...
... Provide help in every mySAP Retail implementation ... The preconfigured development client reduces the project runtime. ... Allow early prototyping in the implementation, which reduces problems later thanks to a system-based discussion in the Blueprint Workshops. ... Contain detailed documentation of the preconfigured processes including full integration with AcceleratedSAP. Enable you to set up a pared-down, functioning system in a short period of time and test live operations.
SAP AG 2003
© SAP AG
IRT350
8-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
