SCM521 Pricing in Purchasing

Full text

(1)SCM521 Pricing in Purchasing. Only Partner. Pricing in Purchasing. THE BEST-RUN BUSINESSES RUN SAP. Use. SAP AG 2002  SAP AG©2003  SAP AG. !. 2003/Q2. !. Materialnummer: 50061152. Only. Internal. Use. SAP R/3 Enterprise. Partner. !. SAP. SAP. Internal. SCM521. © SAP AG. SCM521. 0-1.

(2) Copyright. Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved.. SAP. Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.. !. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.. !. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.. !. ORACLE® is a registered trademark of ORACLE Corporation.. !. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.. !. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.. !. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.. !. JAVA® is a registered trademark of Sun Microsystems, Inc.. !. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.. !. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.. !. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.. © SAP AG. SCM521. Only. !. Partner. Use. SAP. Internal. Use. Partner. Only. Internal.  SAP AG 2003. 0-2.

(3) Course Prerequisites. # Essential: # SCM020Processes in Procurement # Recommended: # SCM520Purchasing Details and Optimization # SCM550Cross-Functional Customizing in Materials Management. Use. Only.  SAP AG 2002. SAP. SAP. Partner. Internal. # Participants should be thoroughly familiar with the Purchasing area. Ideally, they should also have some knowledge of the Customizing functionality for this area.. Only. Internal. Use. Partner. © SAP AG. SCM521. 0-3.

(4) Target Group. # Audience: !. Project team members responsible for pricing in purchasing.. # Duration: 2 days. SAP. SAP. Notes to the user The training materials are not teach–yourself programs. They complement the course instructor's explanations. On the sheets, there is space for you to write down additional information.. Only. Internal. !. Partner. Use. Use. Partner. Only. Internal.  SAP AG 2002. © SAP AG. SCM521. 0-4.

(5) Course Overview. Contents: ! Course Goals ! Course Objectives ! Course Content ! Main Business Scenario. Use.  SAP AG 1999. SAP. SAP. Partner. Internal. Only. ! Course Overview Diagram. Only. Internal. Use. Partner. © SAP AG. SCM521. 1-1.

(6) Course Goals. This course will prepare you to: ! Carry out price determination functions in. purchasing ! Configure the IMG settings for price determination. Use. Partner. Only. Internal. SAP. SAP.  SAP AG 1999. Only. Internal. Use. Partner. © SAP AG. SCM521. 1-2.

(7) Course Objectives. At the conclusion of this course, you will be able to: ! Outline the various elements of the condition. technique and define how they interact ! Maintain conditions at different levels. Only. Internal. ! Describe how the process of price determination. works in the system ! Recognize the special condition types that can be. used in price determination. Partner. ! Define the subsequent settlement process ! Create condition types and calculation schemas,. Use. and customize the price determination process. SAP. SAP.  SAP AG 1999. Only. Internal. Use. Partner. © SAP AG. SCM521. 1-3.

(8) Course Content. Course Overview. Unit 2. Elements of the Condition Technique. Unit 3. Price Determination. Unit 4 Unit 5. Unit 6. Special Condition Types and Special Functions *. Unit 7. Header and Group Conditions. Subsequent (End-ofPeriod Rebate) Settlement. Unit 8. Customizing. Maintaining Conditions. Unit 9. Conclusion. Appendices. Use. Partner. Unit 1. Internal. Only. Preface. Only. Internal. * If time is short, some of the topics covered in this unit may be omitted. Information on the topics in this unit is available in the text and in the documentation.. Partner. Use. SAP. SAP.  SAP AG 1999. © SAP AG. SCM521. 1-4.

(9) Partner. Course Overview. Special Condition Types and Special Functions. Elements of the Condition Technique. Subsequent (Endof-Period Rebate) Settlement. Price Determination. Customizing. Header and Group Conditions. Conclusion. Internal. Only. Course Overview Diagram. Use. Maintaining Conditions. SAP. SAP.  SAP AG 2001. Only. Internal. Use. Partner. © SAP AG. SCM521. 1-5.

(10) Main Business Scenario. ! A vendor’s price for a material is often made up of. Only. Use. Partner. Internal. different components. Your vendor may offer to sell you a material at a certain price, but additional factors may affect what you pay. Prices, discounts and surcharges, freight costs, and the like are represented in the system as pricing conditions. The system applies these conditions to arrive at the net and effective purchase prices in purchase orders. Settings made in Customizing define the details of the conditions and price determination process.. SAP. SAP.  SAP AG 2001. Only. Internal. Use. Partner. © SAP AG. SCM521. 1-6.

(11) Elements of the Condition Technique. Contents: ! Condition Types ! Condition Records and Tables ! Access Sequences ! Calculation Schemas. Use SAP. SAP. Partner. Only. Internal.  SAP AG 1999. Only. Internal. Use. Partner. © SAP AG. SCM521. 2-1.

(12) Elements of the Condition Technique: Objectives. At the conclusion of this unit, you will be able to: ! Describe the elements of the condition technique and their interaction ! Identify and properly apply time-dependent and time- independent conditions. Only. Use.  SAP AG 2003. SAP. SAP. Partner. Internal. ! Define important control parameters for condition types and calculation schemas. Only. Internal. Use. Partner. © SAP AG. SCM521. 2-2.

(13) Elements of the Condition Technique: Scenario. ! Your purchasing department needs a method for storing and determining the purchase prices for materials.. The condition technique refers to the method by which the system determines prices from information stored in condition records. In Purchasing, the various elements used in the condition technique are set up and controlled in Customizing. During purchase order processing, the system uses the condition technique to determine a variety of important pricing information. For example, the system automatically determines which gross price should apply and which discounts and surcharges are relevant given the conditions that apply.. Internal. Use. ". © SAP AG. SCM521. Only. The term pricing is used broadly to describe the calculation of prices (for external use by vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, we order a certain quantity of a particular product on a certain day from a certain vendor. The variable factors here - the vendor, the product, the order quantity, and the date - determine the final price we pay. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.. Partner. ". SAP. SAP. Use. Partner. Only. Internal.  SAP AG 2002. 2-3.

(14) Elements of the Condition Technique. Subsequent (Endof-Period Rebate) Settlement. Price Determination. Customizing. Header and Group Conditions. Conclusion. Maintaining Conditions. Use.  SAP AG 1999. SAP. SAP. Partner. Course Overview. Special Condition Types and Special Functions *. Internal. Only. Elements of the Condition Technique: Overview. Only. Internal. Use. Partner. © SAP AG. SCM521. 2-4.

(15) Conditions. Conditions Prices. Discounts and surcharges. Contract. Percentage, quantity-dependent, or absolute discounts/surcharges. Scheduling agreement Quotation. SAP. Partner. End-of-period rebates.  SAP AG 2002. SAP. Conditions are stipulations agreed with vendors regarding prices, discounts and surcharges. The system determines the price in purchasing on the basis of these pricing elements.. ". Conditions are stored in the system as condition records. Condition records allow you to store and retrieve pricing data in the system. You create condition records for all the pricing elements - the prices, discounts, and surcharges - that the system takes into account during automatic pricing. You can define as many condition records as you want for the different pricing elements.. ". During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the purchasing document.. ". A distinction is made between conditions that are valid for a certain period (time-dependent conditions) and conditions for which no validity period can be specified (time-independent conditions). In the latter case, the validity period corresponds to that of the purchasing document. Whether time-dependent or time-independent conditions are created is determined via the document type.. ". You can also store conditions that do not take effect immediately, but only at the end of a certain period. Settlement with regard to such conditions takes place subsequent to the settlement of vendor invoices relating to individual purchase orders.. © SAP AG. SCM521. 2-5. Only. ". Partner. Use. Cash discounts. Use. Internal. Freight charges. Internal. Only. Info record.

(16) Time-Dependent Conditions. General conditions Vendor FF FF DM DM Condition group $$ Material type Incoterms Invoicing party Other. pc. Outl. purchase agreement. % Conditions. $. Price 1 01.01.. SAP. From 100 pc 3%. Purch. organization. 5%. Lower limit 1%. Ref. purch. organization.  SAP AG 2002. Conditions in info records and contracts are always time-dependent. You can specify in Customizing (via the document type) whether time-dependent or time-independent conditions can be maintained in quotations and scheduling agreements. As of Release 4.0A, the standard settings are timedependent conditions for both scheduling agreements and quotations.. ". In addition to time-dependent conditions that apply to individual info records, or quotation or outline agreement items, you can also define time-dependent conditions reflecting more general pricing arrangements (general conditions).. ". Time-dependent conditions are always limited to a certain period of validity, which is defined by a start date and an end date. If you do not enter a validity period, the R/3 System suggests a period. The default validity period is controlled using Customizing.. ". If a vendor's pricing varies according to the quantity purchased, you can enter it in the form of a price/quantity scale.. ". You can specify upper and lower limits for time-dependent conditions in order to prevent agreed maximum or minimum figures from being exceeded in the event that condition values are changed manually in the purchase order.. ". Time-dependent conditions can be stored on either a plant-specific or a cross-plant basis (in the latter case, for all plants belonging to a purchasing organization). You can also use conditions negotiated by another purchasing organization (reference purchasing organization).. ". Valid time-dependent conditions from info records or outline purchase agreements are adopted as default values in purchase orders.. ". Conditions in purchase orders are always time-independent. No validity periods and scales can be defined for these conditions.. © SAP AG. SCM521. Only. ". Partner. Use. 12.31.. Upper limit. SAP. Internal. 07.01.. 5%. Use. Partner. Plant. Surcharge. Price 2. Internal. Only. Info record. 2-6.

(17) Condition Types. Control. Freight, absolute. Condition class: Discount/surcharge Calculation type: Fixed amount Condition cat.: Delivery costs. SKTO. Cash discount. Condition class: Discount/surcharge Calculation type: Percentage Condition cat.: Cash discount. Use. A condition type is a representation in the system of some aspect of your daily pricing activities. You can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions. There are condition types for the gross price, various discounts and surcharges, freight charges, or fixed costs in the standard version of the SAP R/3 System.. ". You can change and maintain condition types provided in the standard version of the SAP R/3 System or you can create new condition types to suit the needs of your own organization. You create and maintain condition types in Customizing.. ". Condition types are differentiated broadly using the condition class and more finely using the condition category. The condition category also has various control functions. For example, condition category U (for precious metal discounts and surcharges) causes a new price determination process to be carried out at the time of goods receipt, and condition category E (for cash discount) causes the discount to be derived from the terms of payment.. ". The calculation type (or rule) determines how the system calculates prices, discounts, or surcharges for a condition. For example: $ the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight. $ a discount or surcharge can be a percentage of the gross price, a fixed amount or a quantitydependent amount.. ". The plus/minus sign determines whether a condition is treated as a negative or positive amount. Negative amounts are discounts (deductions), positive amounts are surcharges (additions).. ". The scale basis (or reference magnitude) for scales also depends on the condition type. A scale can be based on quantity or dollar value, for example.. © SAP AG. SCM521. 2-7. Only. ". Partner. Internal.  SAP AG 2003. SAP. SAP. FRB1. Use. Gross price. Internal. PB00. Condition class: Prices Calculation type: Quantity-dependent Condition cat.: Base price Access sequence: Gross price. Only. Description. Partner. Key.

(18) Condition Records and Condition Tables. Condition table A017 (info record with plant) Cond. ty.. Vendor. Material. Pur. org.. Plant. .... Cond. rec. no.. PB00. A. 1. 1000. 1000. .... 1234. Pur. org.. .... Cond. rec. no.. PB00. A. 1. 1000. .... 4321. Table KONP (item conditions). Partner SAP. Material. Cond. rec. no. Cond. ty.. .... Cond. amount. .... 1234. PB00. .... 10.00. .... 4321. PB00. .... 11.00. ....  SAP AG 2003. ". A condition table consists of one or more condition keys and a data part. The data part contains a number that references the record in another table.. ". The standard SAP R/3 System includes predefined condition tables. You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.. ". Examples of condition tables with the following key fields in the Standard SAP R/3 System.. Only. A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a material or a special discount for a vendor, you create an individual condition record.. $ Table A018 - Vendor, material, purchasing organization, info record category $ Table A017 - Vendor, material, purchasing organization, plant, info record category $ Table A066 - Vendor, material, purchasing organization, info record category, order unit $ Table A068 - Purchasing document, item, plant (for outline agreements) ". Condition records are stored in the following transparent tables $ KONP (time-dependent conditions) $ KONH (header conditions) $ KONM (quantity scales) $ KONW (value scales). © SAP AG. SCM521. Partner. ". SAP. Use. Vendor. Use. Internal. Cond. ty.. Internal. Only. Condition table A018 (info record without plant). 2-8.

(19) Access Sequence. Cond. ty.. Control. PB00. Access sequence 0002. Condition table. 0002. 10. A017 (Info record w. plant). 20. A018 (Info rec. w/o plant). 30. .... ". A condition type must have an access sequence assigned to it if you want to maintain conditions with their own validity periods (for example, condition type PB00). In the case of a gross price, you can specify that the R/3 System is first to search for a plant-specific price – it is to search for a general, cross-plant price only if it cannot find a plant-specific one.. ". In the standard R/3 System, no access sequences are assigned to the condition types for discounts and surcharges (RA00, RA01 and so on.) because they do not have separate validity periods. They are always maintained at the same time as the gross price (PB00) and their validity period is always the same as the validity period of the gross price.. ". The order of the accesses is determined by the order of the condition tables in the access sequence.. ". The Exclusive indicator controls whether the system stops searching for a record after the first successful access for a condition type within an access sequence. In other words, the search for further valid entries in (other) condition tables is interrupted if an access was successful and a relevant entry was found.. ". You define the prerequisites (or requirement) according to which the R/3 System searches certain condition tables for relevant entries using requirement routines. Certain condition tables are accessed only if the document item satisfies certain criteria.. ". You cannot assign an access sequence to a header condition.. © SAP AG. SCM521. 2-9. Only. An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record.. Partner. ". Use. SAP.  SAP AG 2002. SAP. Internal. Exclusive. Use. Partner. Only. No.. Internal. Access sequence.

(20) Partner. Counter Cond. ty.. Description. 1. 1. PB00. Gross price. 10. 1. RB00. Absolute discount. .... .... .... 10. 9. ZA01. .... .... .... 20. 0. .... .... .... 31. 1. FRA1. .... .... .... 35. 1. SKTO. 40. 0. Fr.. Manu.. .... X. 1. X. Freight %. 20. X. Cash discount. 20. % Surcharge on gross. Stat. Net value incl. discount. X. X. Use. Effective price.  SAP AG 2002. A calculation schema (or pricing procedure) groups together all of the condition types that play a part in calculating the price. It sets out the order in which the condition types are taken into account in the calculation. In addition, the calculation schema specifies the following: $ Which subtotals are arrived at $ To what extent the price determination process can be carried out manually $ The basis upon which the system calculates percentage discounts and surcharges $ Order in which the condition types are taken into account in the calculation of the net or effective price $ Which requirements must be satisfied in order for a certain condition type to be taken into account. ". In addition, the Fro(m) reference step for percentage conditions is defined in the calculation schema. The Fro(m) reference step can be combined with a To reference step.. ". You can define a variety of calculation schemas (for individual purchasing organizations and/or vendors, for example). In the standard system, calculation schema RM0000 is defined for determining the purchase price in purchasing documents.. ". There are three kinds of price in Purchasing: $ Gross price: Price without taking any possible discounts and surcharges into account. $ Net price: Gross Price taking any applicable discounts and surcharges into account. ". Effective price: Net price after deduction of cash discount, with allowance for any miscellaneous provisions, delivery costs, and non-deductible taxes.. © SAP AG. SCM521. 2-10. Only. Internal. $ Condition types for which subtotals are calculated. Partner. Use. ". SAP. SAP. Step. Internal. Only. Calculation Schema.

(21) Cnt. C.ty.. Description. C.ty.. 1 2 3 4. Abs. discount Discount/qty. % disc. on net % disc. /gross. PB00 Gross price 100.00 RA00 % disc. on net 2% RB00 Abs. discount 10.00 Net value 88.00. RB00 RC00 RA00 RA01. Calculation schema Step 10 11 12 13 . . .. Partner SAP. Step 10 10 10 10 . . .. Cnt. C.ty. 0 0 0 0. RB00 RC00 RA00 RA01. Description. Amount. Conditions for item 10. Description. C.ty.. Abs. discount Discount/qty. % disc. on net % disc./gross .. 100.00 PB00 Gross price RB00 Abs. discount 10.00 2% RA00 % disc. on net 88.20 Net value. Description. Pur. order. Pur. order. Amount.  SAP AG 1999. The step numbers of the condition types in the calculation schema determine the sequence (order) in which the condition types are taken into account in the calculation of the net or effective price. This sequence cannot be changed in the document even if the condition types are entered manually.. ". Condition types assigned to the same step in the calculation schema are sorted by means of a counter. With these condition types, the order of manual entry decides the point at which the condition type is taken into account in the calculation of the net or effective price.. Partner. ". SAP. Use. Conditions for item 10. Use Only. Internal. Calculation schema. Internal. Only. Sequence of Conditions. © SAP AG. SCM521. 2-11.

(22) Elements of the Condition Technique: Summary. You are now able to: ! Describe the elements of the condition technique and their interaction ! Identify and properly apply time-dependent and time-independent conditions. Only. Use.  SAP AG 2001. SAP. SAP. Partner. Internal. ! Define important control parameters for condition types and calculation schemas. Only. Internal. Use. Partner. © SAP AG. SCM521. 2-12.

(23) Exercise Data Sheet Key to Icons in Exercises and Solutions Exercises Solutions Objectives Business Scenario. Partner SAP. Data Used in Exercises Type of Data. Data in Training System. Company code. 1000 (IDES AG 1000). Purchasing organization. 1000 (IDES Deutschland). Plants. 1000 (Hamburg), 1100 (Berlin),. SAP. 1200 (Dresden) Storage location. 0001 (Materiallager). Purchasing group. Z21 (SCM521 Buyer). Materials. T-REK## T-REM##. Material group. ZT21 (SCM521 Material Group). Vendors. T-K521A## T-K521C## T-K521E##. G/L account. 400000. Cost center. T-L20. SCM521. T-REL## T-REN##. T-K521B## T-K521D##. Only. © SAP AG. Partner. Use. Warning or Caution. Use. Internal. Internal. Only. Hints and Tips. 2-13.

(24) Exercises Unit: Elements of the Condition Technique. At the conclusion of this exercise, you will be able to:. Only. • Define important control parameters for condition types and calculation schemas. Use. Create a standard information record using the following data: Vendor:. T-K521A##. Material:. T-REK##. Purchasing organization:. IDES Deutschland (1000). Planned delivery time:. 10 days. Purchasing group:. Z21 (SCM521). Standard quantity:. 100. Gross price (PB00):. 9.90 EUR (from 1 pc). Partner Only. Internal. SAP. 1-1. Use. SAP. Your purchasing department needs a method for storing and determining purchase prices for materials. In the R/3 System, the condition technique is used to determine purchase and valuation prices. This technique is based on conditions that are described by condition types, stored in condition records and condition tables, found by means of access sequences, and arranged in calculation schemas.. Internal. • Examine differences between, and maintenance of, timedependent and time-independent conditions. Partner. • Describe the elements of the condition technique and their interaction. 9.50 EUR (from 100 pc) 9.00 EUR (from 500 pc) Discount % on net (RA00): 1% (from 1 pc) 2% (from 500 pc) Freight (value FRB1):. 50.00 EUR. The conditions are valid until the end of next year. Information Record Number: ___________________. © SAP AG. SCM521. 2-14.

(25) 1-2. Vendor T-K521A## also grants Purchase organization 1000 a scaled discount on all materials for a limited period of time: • 3% from a value of 1000 EUR upwards • 4% from a value of 5000 EUR upwards • 5% from a value of 9000 EUR upwards The discount is valid for a period of four weeks, starting today.. From 0.00 EUR: 0% From 1000.00 EUR: 3% 1-3. Internal. Create a purchase order using the following data: T-K521A##. Purchasing group:. Z21. Company code:. 1000. Material:. T-REK## /qty 120 pc/ plant 1000.. Material:. T-REK##/qty 560 pc/plant 1100.. Delivery date:. In 2 weeks (applies to both items). SAP. Purchasing organization: 1000. Use. Partner. Vendor:. SAP. Only. If a discount or surcharge is to apply only from a certain value upwards, you should insert a zero line in the scale, for example:. Use Internal. 1-3-1 Must you enter an order price? Yes or No 1-3-2 Check the conditions for both items and determine the amounts/percentages for each. Record the findings below:. Only. Item 10. Item 20. Gross price (per 1 pc) Discount % on net Vendor discount Net price (per 1 pc) Freight surcharge Cash discount Actual price (per 1 pc). © SAP AG. SCM521. Partner. Do not save the purchase order until you have answered steps 1-3-1 to 1-3-3. 2-15.

(26) 1-3-3 Trace the origin of the condition value for each item by displaying the master data for the condition records. Record the findings below: Item 10. Item 20. Gross price Discount % on net Vendor discount Freight surcharge Purchase order number: ___________________ 1-4. Partner. Condition type. Access Condition sequence class. Calculation Condition type category. Plus/ minus. PB00. Use. RA00 RB00. SAP. RC00. SAP. RL01 FRB1 SKTO Create an additional information record using the following data: Vendor:. T-K521A##. Material:. T-REL##. Purchasing organization:. IDES Deutschland (1000). Planned delivery time:. 10 days. Purchasing group:. Z21 (SCM521). Standard quantity:. 100. Only. Internal. 1-5. Partner. Use. Display the Customizing settings and determine the specified control parameters for the following condition types. Record the findings below:. For this material, you have negotiated the following conditions with your vendor, which are valid indefinitely: Gross price:. 120.00 EUR. Discount % on gross:. 1%. Discount/quantity:. 2.00 EUR (from 1 carton) 5.00 EUR (from 10 cartons) 10.00 EUR (from 50 cartons). © SAP AG. Internal. Only. Cash discount. SCM521. 2-16.

(27) Be sure to scale the discount/quantity by carton, not pc. Discount (value):. 20.00 EUR (from 1 pc) 120.00 EUR (from 500 pc). Discount % on net:. 1.5%. 1-5-1 What condition types did you use for the above conditions? • Gross price. _________________________________. • Discount % on gross _________________________________. Only. • Discount % on net _________________________________ • Information Record number: ___________________ *1-6. Condition type. Step. Counter. RB00. SAP. RC00. SAP. RA00 RA01. Use. HB01. Partner. RL01 RGR0 *1-7. Create a purchase order using the following data: Vendor:. T-K521A##. Purchasing organization:. IDES Deutschland (1000). Purchasing group:. Z21 (SCM521). Delivery date:. In 8 weeks. Only. Internal. Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types. Record the findings below:. Use. Partner. • Discount (value) _________________________________. Order 500 pc of material T-REL## for plant 1000. Check the conditions of your purchase order item and compare the sequence of the discount conditions with the sequence in your info record and in the calculation schema. 1-7-1 In which sequence are the discount conditions adopted in the purchase order? ______________________________________________________ Purchase order number: ______________________________________________________ © SAP AG. Internal. • Discount/quantity _________________________________. SCM521. 2-17.

(28) Solutions Unit: Elements of the Condition Technique. 1-1. Create a standard information record. Logistics → Materials Management → Purchasing → Master Data → Info Record → Create.. Only Partner. Vendor:. T-K521A##. Material:. T-REK##. Purchase Organization:. 1000. Plant:. Leave blank. Internal. Enter the following data:. Use. Choose: Info category Standard Enter 1-1-1 Select the Purch. Org data 1 radio button.. SAP Use. 10. Purchase group:. Z21. Standard qty:. 100. Net price:. 9.90 EUR. Partner. Plnd dely time:. SAP. Enter the following data:. 1-1-2 Select the Conditions radio button. Condition. Condition type. Amount. Gross price. PB00. 9.90 EUR note: this will have defaulted from the purchase org screen.. Discount % on net. RA00. 1%. Freight (value). FRB1. 50.00 EUR. Only. Internal. Enter the following data:. Change the Valid on date to: The current date (note: this will have defaulted today’s date) Change the Valid to date to: One year from today’s date 1-1-3 Select the Gross price line (PB00) line with the mouse by clicking once the gray box to the left of PB00.. © SAP AG. SCM521. 2-18.

(29) 1-1-4 Select the Scales icon Enter the following data: Scale quantity:. Amount:. Blank. 9.90 EUR (note this will have defaulted). 100. 9.50 EUR. 500. 9.00 EUR. Green arrow back to the main Conditions screen 1-1-5 Select the Discount% on net (RA00) line with the mouse by clicking once the gray box to the left of RA00.. Only. Amount:. Blank. 1 % (note this will have defaulted). 500. 2%. SAVE 1-2. Vendor T-K521A## also grants Purchase organization 1000 a scaled discount on all materials for a limited period of time:. SAP. SAP. Logistics → Materials Management → Purchasing → Master Data Conditions → Discounts/Surcharges → By Vendor. 1000. Vendor:. T-K521A##. Scope of list:. 0001 (note this will default). Partner. Use. Enter the following data: Purchasing organization:. Execute. 1-2-2 Select the vendor line item with the mouse by clicking once the gray box to the left and choose Scales icon. Enter the following data:. © SAP AG. Amount:. Blank. Blank. 1000. 3%. 5000. 4%. 9000. 5%. SCM521. 2-19. Only. Internal. 1-2-1 Select the Purchasing organization by clicking once on the line and choosing the Create icon.. Scale quantity:. Use. Partner. Scale quantity:. Internal. Enter the following data:.

(30) If a discount or surcharge is to apply only from a certain value upwards, you should insert a zero line in the scale, for example: From 0.00 EUR: 0% From 1000.00 EUR: 3% Change the Valid on date to: The current date (note: this will have defaulted today’s date) Change the Valid to date to: Four weeks from today’s date. SAVE 1-3. Create a purchase order using the following data:. Vendor:. T-K521A##. Purchase org:. 1000. Purch. Group. Z21. Company Code:. 1000. Use. Only Partner. Enter the following date in the Header area of the purchase order:. SAP Use. PO quantity. Deliv. Date. Plant. T-REK##. 120. 2 weeks from today. 1000. T-REK##. 560. 2 weeks from today. 1100. Partner. Material. SAP. Enter the following data in the Item overview area of the purchase order:. 1-3-1 No, the order price is adopted from the cross-plant info record. 1-3-2 Check the conditions for both items and determine the amounts/percentages for each. Verify the findings below: 1-3-2-1. Select the appropriate line item by using the mouse and clicking once in the gray box to the left of the line.. 1-3-2-2. Open the Item overview screen area, if not already open, by selecting the Item overview icon within the purchase order.. SCM521. 2-20. Only. Internal. Do not save the purchase order until you have answered steps 1-3-1 to 1-3-3. © SAP AG. Internal. Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known.

(31) 1-3-2-3. Select the Conditions tab in the Item details screen area. Item 10. Item 20. Gross price (per 1 pc). 9.50 EUR. 9.00 EUR. Discount % on net. 1%. 2%. Vendor discount. 3%. 4%. Net price (per 1 pc). 9.12 EUR. 8.46 EUR. Freight surcharge. 50.00 EUR. 50.00 EUR. Cash discount. 3%. 3% 8.30 EUR. Internal. Only. Actual price (per 1 pc) 9.26 EUR. Select the appropriate line item by using the mouse and clicking once in the gray box to the left of the line.. SAP. 1-3-3-2. Open the Item overview screen area, if not already open, by selecting the Item overview icon within the purchase order.. 1-3-3-3. Select the Conditions tab in the Item details screen area.. 1-3-3-4. Select the Conditions rec. radio button Gross price. Information record Information record. Discount % on net. Information record Information record. Vendor discount. Purchase org. / Purchase org. / Vendor conditions Vendor conditions. Freight surcharge. Information record Information record. Cash discount. Information record Information record. SAVE Purchase order number: ___________________ 1-4. Display the Customizing settings and determine the specified control parameters for the following condition types. Verify the findings below: 1-4-1 Tools → Customizing → IMG → Edit Project 1-4-2 Choose: SAP Reference IMG radio button 1-4-3 Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types 1-4-4 Choose: Define Condition Type. Enter. © SAP AG. SCM521. 2-21. Only. Internal. Item 20. Partner. Item 10. SAP. 1-3-3-1. Use. Step 1-3-3 can be done using the same steps as 1-3-2. Skip to step 1-3-3-4 if still in the Conditions tab.. Use. Partner. 1-3-3 Trace the origin of the condition value for each item by displaying the master data for the condition records. Verify the findings below:.

(32) Condition type. Access Condition sequence class. Calculation Condition type category. Plus/ sign. PB00. 0002. B. C. H. (blank). RA00. (blank). A. A. (blank). X. RB00. (blank). A. B. (blank). X. RC00. (blank). A. C. (blank). X. RL01. 0006. A. A. (blank). X. FRB1. (blank). A. B. B. (blank). SKTO. (blank). A. A. E. (blank). SAP. A = Discount or surcharge B = Prices. Calculation type:. A = Percentage B = Fixed amount C = Quantity-dependent. Condition category:. B = Delivery costs E = Cash discount H = Base price. Plus/Minus:. X = Negative, A = Positive, Blank(_) = positive and negative. Create an additional information record using the following data:. Partner. Logistics → Materials Management → Purchasing → Master Data → Info Record → Create. Internal. Use. Condition class:. SAP. 1-5. Verify what each control data 1 code means by using the F4 matchcodes:. Use. Partner. 1-4-5-1. Enter the following data: T-K521A##. Material:. T-REL##. Purchase Organization:. 1000. Plant:. Leave blank. Only. Vendor:. Choose: Info category Standard Enter. © SAP AG. SCM521. Internal. Only. 1-4-5 Verify the details of each of the condition types by selecting the condition. Select the Details icon.. 2-22.

(33) 1-5-1 Select the Purch. Org data 1 radio button. Enter the following data: Plnd dely time:. 10. Purchase group:. Z21. Standard qty:. 100. Net price:. 120.00 EUR. 1-5-2 Select the Conditions radio button. Amount. Only. Gross price. PB00. 120.00 EUR note: this will have defaulted from the purchase org screen.. Discount % on Gross. RA01. 1%. Discount/quantity. RC00. 2.00 EUR per Carton. Discount (value). RB00. 20.00 EUR per Carton. Discount % on net. RA00. 1.5%. Use. Condition type. SAP. SAP. Be sure to scale the discount/quantity by carton, not pc. Change the Valid on date to: The current date (note: this will have defaulted today’s date). Use. 1-5-3 Select the Discount/quantity (RC00) line with the mouse by clicking once the gray box to the left of RC00.. Internal. 1-5-4 Select the Scales icon Enter the following data: Blank. 2.00 EUR (note this will have defaulted). 10 Cartons. 5.00 EUR. 50 Cartons. 10.00 EUR. Only. Amount:. Green arrow back to the main Conditions screen. © SAP AG. SCM521. Partner. Change the Valid to date to: Indefinitely. Scale quantity:. Internal. Condition. Partner. Enter the following data:. 2-23.

(34) 1-5-5 Select the Discount Value (RB00) line with the mouse by clicking once the gray box to the left of RB00. Enter the following data: Scale quantity:. Amount:. Blank. 20.00 EUR (note this will have defaulted). 500 pieces. 120.00 EUR. 1-5-6 What condition types did you use for the above conditions? • Gross price. _________________________________. Only. • Discount (value) _________________________________ • Discount % on net _________________________________ • Information Record number: ___________________ *1-6. Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types. Verify the findings below: 1-6-1 Tools → Customizing → IMG → Edit Project. SAP. SAP. 1-6-2 Choose: SAP Reference IMG radio button 1-6-3 Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema. Use. Partner. 1-6-4 Verify the details of RM0000 by selecting the schema.. © SAP AG. Counter. RB00. 10. 1. RC00. 10. 2. RA00. 10. 3. RA01. 10. 4. HB01. 10. 10. RL01. 10. 11. RGR0. 10. 13. SCM521. Only. Internal. 1-6-5 Choose the Control data folder by double clicking. Condition type Step. Use. SAVE. Internal. • Discount/quantity _________________________________. Partner. • Discount % on gross _________________________________. 2-24.

(35) *1-7. Create a purchase order using the following data: Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known Enter the following date in the Header area of the purchase order: Vendor:. T-K521A##. Purchase org:. 1000. Purch. Group. Z21. Company Code:. 1000. Only. Material. PO quantity. Deliv. Date. Plant. T-REL##. 500 pc. 8 weeks from today. 1000. Partner. 1-7-1 Since all discount condition types in the calculation schema are assigned to the same step, their sequence in the purchase order is determined by the manual entry in the info record.. Use. Check the conditions of your purchase order item and compare the sequence of the discount conditions with the sequence in your info record and in the calculation schema.. Internal. Enter the following data in the Item overview area of the purchase order:. SAP. SAP Only. Internal. Use. Partner. © SAP AG. SCM521. 2-25.

(36) Price Determination. Contents: ! Price Determination ! Schema Determination and Schema Groups ! Access Sequences for Gross Price. Internal. Only. ! Validity Periods for Pricing ! Conditions Adopted from Last Purchase Order ! Scales. Use.  SAP AG 1999. SAP. SAP. Partner. ! Condition type PB00 versus PBXX. Only. Internal. Use. Partner. © SAP AG. SCM521. 3-1.

(37) Price Determination: Unit Objectives. At the conclusion of this unit, you will be able to: ! Describe how the R/3 System finds the appropriate calculation schema. Only. ! Create condition types and calculation schemas by copying existing data. Use.  SAP AG 2001. SAP. SAP. Partner. Internal. ! Explain the price determination process, taking into account different condition tables, validity periods and scales. Only. Internal. Use. Partner. © SAP AG. SCM521. 3-2.

(38) Price Determination: Business Scenario. ! Your purchasing policy dictates that prices should automatically default on purchase orders whenever possible. Since you negotiate with vendors and agree on prices ahead of time, you often create info records to facilitate this process.. $ In the case of purchase orders, the system searches for conditions in info records and contracts (for contract release orders), and for general conditions. $ In the case of scheduling agreements with time-independent conditions, the system searches for conditions in info records and for general conditions. ". If no conditions are found, but the last PO is noted in the info record, the system can adopt the conditions from this PO. You can specify how the system treats the conditions from the last PO in Customizing for Purchasing (default values for buyers).. © SAP AG. SCM521. Only. Internal. When you create a purchase order or scheduling agreement with time-independent conditions, the system searches for valid conditions and inserts these conditions into the new document (this is the process of price determination).. Partner. Use. ". SAP. SAP. Use. Partner. Only. Internal.  SAP AG 2002. 3-3.

(39) Elements of the Condition Technique. Subsequent (Endof-Period Rebate) Settlement. Price Determination. Customizing. Header and Group Conditions. Conclusion. Maintaining Conditions. Use.  SAP AG 1999. SAP. SAP. Partner. Course Overview. Special Condition Types and Special Functions *. Internal. Only. Price Determination: Overview Diagram. Only. Internal. Use. Partner. © SAP AG. SCM521. 3-4.

(40) Price Determination Process: Overview. Calculation schema. Purch. order. Step Cond. type . . . .... Pur. org. Vendor. 1000 A. For plant Material. 1000 1. 1 . . .. PB00. Condition type: PB00. 10 pc. Access sequence: 0002. Partner SAP.  SAP AG 2002. ". When you create a purchase order, a contract release order, or a delivery schedule (under a scheduling agreement), the R/3 System searches existing info records and documents for valid conditions and adopts any it finds as default values in the new document.. ". The price determination process is carried out in a number of steps: $ First, the relevant calculation schema is determined. $ The R/3 System then searches for condition records for all condition types listed in the calculation schema that have an access sequence assigned to them. $ The search is concluded when a valid condition record is found.. ". Material-specific discounts and surcharges are supplementary conditions linked to the gross price (condition type PB00). No access sequence is assigned to a supplementary condition in Customizing for the condition type. No separate price determination is carried out for supplementary conditions. They are found using the condition record for the gross price.. © SAP AG. SCM521. 3-5. Only. $ The search for condition records is carried out in the order specified in the access sequence.. Partner. Use. Condition table Plant info record Material 1 50.00 From 500 pc 48.00. SAP. Internal. Condition table Contract item No record exists. Use. Condition tables: 1. Contract item (excl.) 2. Plant info record (excl.) 3. Info record (excl.) . . .. 50.00. Internal. Only. Access sequence: 0002.

(41) Schema Determination Customizing Schema gr. purch. org.. Schema gr. vendor. 0001. Partner SAP. Vendor. A. XM0000 01. YM0000. 02. ZM0000. Purch. org.. Schema gr.. 2000. 0001. 3000. 0001. Vendor A Schema group 02  SAP AG 2002. You can predefine how the calculation schema is determined for standard POs and stock transport orders, the calculation of the market price in vendor evaluation and for external services management.. ". You have the following options with regard to schema assignment for standard POs:. Partner. ". SAP. Use. RM0000. Pur. org. 1000. Use. $ You can assign a generally valid calculation schema (in the standard R/3 System, RM0000) $ You can define the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations. $ You can define the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations and for one or more vendors. ". The schema group comprises those purchasing organizations or vendors to which the same calculation schema is to be assigned. Schema groups are defined in Customizing. The assignment of purchasing organizations to schema groups is also made in Customizing, whereas the assignment of a vendor to a schema group must be made in the relevant vendor master record.. ". Schema assignment for stock transport orders depends on the schema group of the purchasing organization, the document type and/or the supplying plant. Schema assignment for the calculation of the market price in vendor evaluation depends on the purchasing organization. The calculation schema for external services management depends on the document type. In this case, you should note that a uniform calculation schema per document type must be chosen for the documents RFQ/quotation (AN), purchase requisition (NB), and purchase order (NB).. © SAP AG. SCM521. 3-6. Only. Internal. Purch. order. Internal. Only. 0001. Calculation schema.

(42) Calculation Schema for Condition Type PB00. Calculation schema RM0000 Step Count. Cond. type. Condition class Calculation type Calculation schema: RM0002 . . . Calculation schema RM0002. Pc. Pc.. Info record Valid. Partner SAP. Condition type PB00. from 01.01. to 12.31.. Cond. type PB00 GAU1 RB00. Cond. value . . .. % % Conditions Conditions. $$. Step 1 5 10 . . .. Count. 1 1 1. Cond. type PB00 GAU1 RB00. Propose condition supplements.  SAP AG 2002. SAP. ". A calculation schema for supplementary conditions must be assigned to condition type PB00 (or your own, comparable condition type for the gross price). In the standard R/3 System, schema RM0002 is used for this purpose.. ". Condition types of this calculation schema are discounts and surcharges (RA00, RA01 and so on), and freight conditions (FRA1, FRB1 and so on), which can be valid for specific materials.. ". The list of condition types suggested to you if you choose the Propose condition supplements function when maintaining info record conditions or conditions for quotation or outline agreement items is based on the calculation schema for supplementary conditions.. ". The assignment facilitates the entry of discounts, surcharges and so on based on the info record or quotation or outline agreement item.. ". Supplementary conditions have the same validity period as the main condition.. ". In the standard R/3 System, no access sequence is usually assigned to the condition types of the supplementary conditions because no separate condition record has to be found for them. They do not have their own validity periods and are always maintained in conjunction with the gross price.. ". The structure of the calculation schema assigned to the standard purchase order should correspond to that of the calculation schema for supplementary conditions.. SCM521. Only. © SAP AG. Partner. Use. PB00. Use. Internal. 1. Internal. Only. 1 . . .. 3-7.

(43) Access Sequence for Gross Price. Calculation schema Step. Condition type. 1. PB00. Purch. order Pur. org. 1000 Vendor A. Condition type PB00. For plant 1000 Material 1. Access sequence: 0002. Access sequence 0002. Only. 68 16 67. Contract item, plant-dependent Contract item Plant info record per order unit. Partner. 25 35 45 .... 17 18 28. Material info record, plant-specific Material info record Info record for non-stock material. Item without material. Condition table No. of condition record.  SAP AG 2002. The access sequence is a search strategy defining the order in which condition tables are searched for relevant entries for a condition type. The order of accesses is determined by the order of the condition tables in the access sequence.. ". A vendor’s gross price for a material can depend on a variety of factors. There are different condition tables with different combinations of key fields for the various price-influencing factors, for example:. Internal. ". $ Table A068 – for gross prices in plant-specific outline agreement items. Partner. Use. Plant info record exists, variable order unit active Plant info record exists. SAP. SAP. 10 15 20. Use. Tab.. Internal. Requirement. No.. $ Table A016 – for gross prices in the items of centrally agreed contracts. Only. $ Table A067 – for order-unit-dependent gross prices in plant-specific material info records $ Table A017 – for gross prices in plant-specific material info records $ Table A018 – for gross prices in material info records $ Table A025 – for gross prices in plant-specific non-stock-material info records (info records without a material number). ". You can differentiate between gross prices, discounts and surcharges for different variants of a configurable material.. ". Requirement routines are used to determine the prerequisites by which the system searches certain condition tables for relevant entries. Some condition tables are accessed only if the document item fulfills certain criteria.. © SAP AG. SCM521. 3-8.

(44) Conditions For Several Purchasing Organizations Customizing enterprise structure Purch. Org. D. Only. Release order Purch. org. D Mat. 2 10,00 for plant 1000.  SAP AG 2002. ". In Customizing, a link must be set up between the relevant purchasing organizations. Furthermore, you must stipulate whether:. Use. Typically, each individual purchasing organization negotiates and maintains its own conditions. However, if your R/3 System has been set up appropriately, your purchasing organization can make use of the conditions negotiated by another (the reference purchasing organization) or make the conditions it has negotiated available to others. This is useful, for example, in the case of centrally agreed (national or corporate) contracts with vendors.. $ It is permissible to issue release orders against contracts of the reference purchasing organization. Only. $ Conditions are to be adopted from info records of the reference purchasing organization, $ Conditions from info records of the reference purchasing organization are to take priority over conditions from info records of your own purchasing organization. ". If the conditions are to be adopted from info records of the reference purchasing organization, you must change the access sequences of the price determination process in such a way that accessing of the condition tables is carried out using the key of the reference purchasing organization.. © SAP AG. SCM521. Partner. ". SAP. SAP. Plant contract Purch. org. EUR Mat. 2 10,00 for plant 1000. Release order Purch. org. D Mat. 1 10,00 for plant 2000. Use. Release order Purch. org. D Mat. 1 10,00 for plant 1000. Plant 2000:. Internal. Central contract Purch. org. EUR 10,00 Mat. 1. Internal. Purch. Org. D. Plant 1000:. Partner. Purch. org. EUR - Contracts Purch. Org. D - Conditions. Purch. Org. EUR. 3-9.

(45) Validity Periods and Pricing Date. 04.01. - 06.30.. 10.20. 07.01. - 09.30.. 10.50. 10.01. - 12.31.. 10.80. Partner. Pricing date category Purchase order 1. Purchase order 2. Purchase order 3. Current date: 04.01. PO date: 03.26. Delivery date: 07.15.. Current date: 04.01. PO date: 03.26. Delivery date: 07.15.. Current date: 04.01 PO date: 03.26. Delivery date: 07.15.. Price:. Price:. Price:. Pricing date = Current date. 10.20. 10.00. Pricing date = PO date. 10.50. Pricing date = Delivery date.  SAP AG 2002. In the automatic price determination process, the price can be calculated as at the document date of the PO, or as at another date (such as the current day’s date, the delivery date, or the goods receipt date). You can specify the date to which the price that is determined relates at the following points: $ In the vendor master record, in the Pricing date control field, if you wish to use the same price determination date for all a vendor’s materials. $ In the purchasing info record, in the Pricing date category field, if you wish to use a different pricing date for a certain material supplied by a particular vendor. The value in the purchasing info record takes precedence over the value in the vendor master record.. ". When a purchase order is created, the pricing date determines the validity period that is accessed. In the standard situation, the pricing date is the same as the document date of the PO. However, instead of the document date you can choose the current date, the delivery date, the GR date or a date entered manually in the PO.. ". The suggested pricing date category or pricing date can be changed in the PO item. However, price determination using a changed pricing date is not carried out automatically – it must be initiated manually on the condition screen.. ". If you have chosen the delivery date as the pricing date, the delivery date of the first schedule line is taken in the case of items with several delivery dates (delivery schedule).. © SAP AG. SCM521. 3-10. Only. $ In the purchase order, in the Pricing date category field.. Partner. Use. ". SAP. SAP. 10.00. Use. Internal. 01.01. - 03.31.. Internal. Only. Gross price.

(46) Scales. Price From. Surcharge 1 pc 500 pc 1000 pc. 100.00 EUR 99.00 EUR 96.00 EUR. To. 500.00 EUR 1000.00 EUR. 50.00 EUR 30.00 EUR. Customizing condition type. Only Partner SAP. Scale type Scale basis. B B. (= To scale) (= Value scale). Condition record (KONP) Scale lines (KONM/KONW)  SAP AG 2002. SAP. When you create a condition record for condition, you can define a pricing scale. For example, a scale based on quantity can determine that the more we purchase from a vendor of a particular material, the lower the price. You can also create condition records with graduated scales.. ". Scaled conditions consist of one or more scale levels. Each scale level consists of a scale value and a scale amount depending on the latter.. ". The scale type and the scale basis for a scale are defined in customizing for the condition type. There are ”From” scales (scale type A) and ”To” scales (scale type B). If no scale type has been assigned to a condition type in Customizing, you can specify whether the scale is to be maintained as a From or To scale before entering the lines of the scale. You specify how the R/3 System is to interpret the price scale for a condition by means of the scale basis. For example, the scale can relate to a money value (scale basis B), a quantity, (scale basis C) or a weight (scale basis D or E).. ". You can also maintain condition records with graduated scales. Using a graduated scale allows you to price an item for each level of a pricing scale. By comparison, when you use normal scales, the system determines one price depending, for example, on the item quantity; the same price then applies to each unit of the item. With graduated scales, the result is that multiples prices can appear in the pricing screen for an individual item.. ". Using the scale type, you specify whether the scale values of the condition represent the upper or lower limits for the price, discount or surcharge.. ". Scaled conditions are stored in the tables KONM and KONW.. © SAP AG. SCM521. 3-11. Only. ". Partner. Use. (= From scale) (= Qty. scale). Use. Internal. A C. Internal. Scale type Scale basis.

(47) Info Record and Order Price History. Quotation in response to RFQ Info record. 10.00. Condition:. Partner SAP. Purch. order 123. Order Orderprice pricehistory history PO no. 123: PO no. 123:10.50 10.50. Item Mat. Price 10.50. Purchase order. Purchase order. Pricing date: 06.01.. Pricing date: 07.01.. Item Mat. Price. Item Mat. Price. 10.00. 10.50.  SAP AG 2002. SAP. An info record can be created either manually or automatically (using the info update indicator). If an info record is created manually, the gross price and supplementary conditions can be maintained for a validity period. You can enter scales and upper and lower limits.. ". If an info record is generated from a contract, the gross price and all supplementary conditions can be adopted in the info record.. ". If an info record is created from a PO or scheduling agreement, the conditions are adopted in the order price history not in the info record.. ". If info record conditions exist and are valid, they are suggested (that is, they appear as default values) when a new PO is created. The conditions from the order price history (that is, the price and conditions of the last PO) are used as default values only if the R/3 System was unable to find any valid info record conditions.. ". In info record list displays, a distinction is made between info record conditions (headword “condition”) and the conditions of the last PO (headword “purchase order”).. © SAP AG. SCM521. 3-12. Only. ". Partner. Use. Valid: 01.01. - 06.30.. Use. Internal. 10.00. Internal. Only. Item Mat. Price.

(48) Conditions Adopted from Last Purchase Order. Last Purchase order 123 Item Mat. Price 10. 1. New Purchase order. 10.00. Item Mat. Price. SAP. Partner. User Parameter EVO.  SAP AG 2003. Until Release 4.5A, during the creation of a purchase order, the system copied the conditions from the last purchase order if the price determination process failed to establish a valid price. The system did not take the manually entered gross price into account in price determination.. ". As of Release 4.5A, you can specify in the default values for buyers (user parameter EVO) how the R/3 System treats the conditions from the last purchase order: $ If the price determination process is unable to arrive at a valid price, the conditions are copied from the last purchase order (as was the case prior to Release 4.5A).. - The conditions are never copied from the last purchase order. ". In addition, you can specify whether or not the R/3 System is to apply a manually entered gross price during the price determination process. That is, if a price is entered manually and the R/3 System determines a different price after going through the price determination process, the R/3 System will not change the manually entered price.. © SAP AG. SCM521. 3-13. Only. $ If you enter a price in the current purchase order manually, the conditions are not copied from the last purchase order.. Partner. ". SAP. Use. ?. Use. Internal. 1. Internal. Only. 10.

(49) Condition Types PB00 and PBXX. Purchase order Item Mat. Price 10. 1. 95.00. Info rec. conditions PB00. 100.00. RA01. 5%. 5% Requirement 6. Purchase order Item Mat. Price. Partner SAP. RA01. 6. 20. 2. ?. Condition exclusion <> ‘X‘ Conditions for item 20 PB00 PBXX. 50.00. Please enter net price. CHECK KOMP-KZNEP NE ‘X‘.. Condition type PB00 ... Exclusion =X ....  SAP AG 2002. ". If no valid info record conditions exist and no order price history can be found, the R/3 System is not able to suggest a price and requires the manual entry of a net price. The manually entered price is assigned to condition type PBXX.. ". These two condition types for the gross price must be available in the calculation schema assigned to the standard purchase order. In the standard R/3 System, these are the condition types PB00 and PBXX. An access sequence is assigned to PB00, so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX. PB00 must be come before PBXX in the calculation schema. You can also use your own, comparable condition types in place of PB00 and PBXX.. ". At the time a purchase order is created, if the R/3 System finds a condition record belonging to PB00 with valid conditions, PBXX is irrelevant. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).. © SAP AG. SCM521. 3-14. Only. If you create an info record manually or automatically, the gross price entered or adopted is assigned to condition type PB00. When a PO is created without reference to a contract or quotation, a vendor’s gross price for a material is adopted from the info record conditions (or, where appropriate, from the order price history) as the default value for condition type PB00.. Partner. ". SAP. Use. 100.00. Reqt.. Use. Internal. PB00. Step Cnt. C. type 1 1 PB00 1 2 PBXX . . .. Internal. Only. Conditions for item 10. Calculation schema.

(50) Price Determination: Unit Summary. You are now able to: ! Describe how the R/3 System finds the appropriate calculation schema. ! Create condition types and calculation schemas by copying existing data. Use.  SAP AG 2001. SAP. SAP. Partner. Internal. Only. ! Explain the price determination process, taking into account different condition tables, validity periods and scales. Only. Internal. Use. Partner. © SAP AG. SCM521. 3-15.

(51) Exercises Unit: Price Determination Topic: Customizing Settings At the conclusion of this exercise, you will be able to: •. 1-1. Create a new condition type Z##A by copying the standard condition type PB00. Name your condition type ZP521 Gross price ##. Save your condition type.. 1-2. Read the IMG documentation for the node Define Calculation Schema.. Use. If the IMG help is not loaded on the server access help.sap.com though the internet for document assistance. 1-3. During the copying process, the R/3 System will repeatedly issue the warning message You should use the counter only for manual item conditions. Acknowledge this and any other warnings by choosing Enter each time. Save your calculation schema 1-4. Create a second new calculation schema YM00## with the title Supplementary Conditions ZP521-## by copying the standard calculation schema RM0002 with all dependent entries. Replace the standard condition type PB00 with your condition type Z##A Acknowledge the repeated warnings by choosing Enter each time. Save your calculation schema. © SAP AG. SCM521. 3-16. Only. Create a new calculation schema ZM00## with the title Document Schema ZP521-##, by copying the standard calculation schema RM0000 with all dependent entries. Replace the standard condition type PB00 with your condition type Z##A.. Partner. The IMG help files must be loaded in the server in order to complete step 1-2.. SAP. SAP. Your purchasing policy dictates that prices should automatically default into purchase orders whenever possible. Since you negotiate with vendors and agree on prices ahead of time, you often create info records to facilitate this process. When a purchase order is created, the R/3 System finds the appropriate calculation schema and carries out the price determination process.. Use. Partner. Only. • Create condition types and calculation schemas by copying existing data. Internal. Internal. Examine how the R/3 System finds the appropriate calculation schema.

(52) 1-5. Now change your condition type Z##A by assigning your new calculation schema YM00## to it as the supplementary schema instead of the standard calculation schema. Save your change.. 1-6. Create a new vendor schema group ## with the title Schema group ZP521-## For course participants belonging to group 01: Schema group 01 already exists in the standard system and need not be created. Simply change the title. Save your schema group. Now define the schema determination process by assigning your calculation schema ZM00## to your vendor schema group ##. The assignment should be independent of the purchasing organization. Save your assignment.. Partner. 1-8. Assign your schema group ## to vendor T-K521B## on the Purchasing data screen of the vendor master record for purchasing organization 1000. Save your assignment.. Internal. Only. 1-7. Use. SAP. SAP Only. Internal. Use. Partner. © SAP AG. SCM521. 3-17.

(53) Exercises Unit: Price Determination Topic: Analyzing Price Determination At the conclusion of this exercise, you will be able to:. When a buyer creates a purchase order, you’d like the R/3 System to determine the correct price from a condition record. You want to make sure that scaled conditions and differing validity periods are also taken in account. Create a purchase order using with the following data: Vendor:. T-K521B##. Purchasing organization:. IDES Deutschland (1000). Purchasing group:. Z21 (SCM521). Delivery date:. In 4 weeks. SAP. SAP. 2-1. Use. Partner. Internal. Only. • Analyze the price determination process, taking into account different condition tables, validity periods and scales. Order 100 pc of material T-REL## for plant Hamburg (1000) at a price of 100 EUR.. Use. ______________________________________________________ 2-1-2 Which condition type has been assigned to the manually entered price? ________________________________________________ 2-1-3 What calculation schema has been determined for the purchase order? ________________________________________________ Save your purchase order. Purchase order number: ___________________ 2-2. Change the info record for vendor T-K521B##, material T-REL##, purchasing organization IDES Deutschland (1000), which was generated automatically from the purchase order created in step 2-1. 2-2-1 Which condition type did the system suggest? ___________________ 2-2-2 You and your vendor have agreed to the following conditions: Gross price:. 100 EUR. Discount (value): 10 EUR from 1 pc 50 EUR from 200 pc Enter the conditions.. © SAP AG. SCM521. 3-18. Only. Internal. Partner. 2-1-1 Why must the price be entered manually?.

(54) If you have used the Propose Condition Supplements function, do not forget to use the Restore (Re-create) Condition Supplements function before saving to ensure that all conditions with a value of 0 are deleted from the list. Otherwise, problems are liable to occur in subsequent exercises due to a discrepancy between the condition type in the info record and the condition types in the soon-to-bechanged calculation schema. Save the changed information record.. •. 1% up to a condition value of 1000 EUR. •. 2% up to a condition value of 5000 EUR. •. 3% up to a condition value of 999999 EUR Before entering the discount scale, you must change the scale type on the condition detail screen.. Create a purchase order with the following data: Vendor:. T-K521B##. Purchasing organization:. IDES Deutschland (1000). Purchasing group:. Z21 (SCM521). Delivery date:. In 2 weeks. SAP. SAP. *2-4. Use. Partner. You have also negotiated the following general discount with vendor T-K521B##, which applies to all materials and is valid for four weeks, starting today.. Internal. Only. 2-3. Use. Partner. Order 100 pc of material T-REL## for plant Hamburg (1000). 2-4-1 Is an order price suggested? If so, what is it? ______________________________________________________. Internal. 2-4-2 How is the default order price calculated? ______________________________________________________. Only. 2-4-3 Determination the details of the price process. ______________________________________________________ Save the purchase order number Purchase order number: ______________________________ *2-5. You have agreed with vendor T-K521B## that the conditions valid on the delivery date for material T-REL## are to be applied for price determination purposes. Record this in the R/3 System by changing the info record for purchasing organization IDES Deutschland (1000) and determining if the system selected a suitable pricing date category. 2-5-1 Which pricing date category did the system use? ______________________________________________________. © SAP AG. SCM521. 3-19.

(55) *2-6. Create a purchase order with the following data: Vendor:. T-K521B##. Purchasing organization:. IDES Deutschland (1000). Purchasing group:. Z21 (SCM521). Delivery date:. In 6 weeks. Order 200 pc of material T-REL## for plant Hamburg (1000). 2-6-1 Did the system propose an order price? _________________________ 2-6-2 How was the order price calculated? ______________________________________________________. Only. Internal. 2-6-3 Why wasn’t the vendor discount taken into account?. Use. Partner. ______________________________________________________. SAP. SAP Only. Internal. Use. Partner. © SAP AG. SCM521. 3-20.

(56) Solutions Unit: Price Determination Topic: Customizing Settings 1-1. Create a new condition type Z##A by copying the standard condition type PB00. Tools → Customizing → IMG → Edit Project. Choose: Define Condition Type SAVE your condition type 1-2. Read the IMG documentation for the node Define Calculation Schema. Tools → Customizing → IMG→ Edit Project Choose: SAP Reference IMG. Select IMG activity documentation on the left-hand side of the Define Calculation Schema node. Use. If the IMG help is not loaded on the server access help.sap.com though the internet for document assistance. 1-3. During the copying process, the R/3 System will repeatedly issue the warning message You should use the counter only for manual item conditions. Acknowledge this and any other warnings by choosing Enter each time. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Choose: Copy all. Replace the standard condition type PB00 with your condition type Z##A SAVE your calculation schema © SAP AG. SCM521. 3-21. Only. Create a new calculation schema ZM00## with the title Document Schema ZP521-##, by copying the standard calculation schema RM0000 with all dependent entries.. Partner. The IMG help files must be loaded in the server in order to complete step 1-2.. SAP. Materials Management → Purchasing → Conditions → Define Price Determination Process. SAP. Partner. Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types. Use. Internal. Internal. Only. Choose: SAP Reference IMG radio button.

(57) 1-4. Create a second new calculation schema YM00## with the title Supplementary Conditions ZP521-## by copying the standard calculation schema RM0002 with all dependent entries Tools → Customizing → IMG → Edit Project Choose SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema Choose: Copy all Replace the standard condition type PB00 with your condition type Z##A. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Condition Types Choose: Define Condition Type. Go into the detail screen and change the entry in the PricingProc field. 1-6. Create a new vendor schema group ## with the title Schema group ZP521-##.. SAP. SAP. For course participants belonging to group 01: Schema group 01 already exists in the standard system and need not be created. Simply change the title.. Partner. Use. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Group Choose→ Schema Groups: Vendor SAVE your schema group. 1-7. Now define the schema determination process by assigning your calculation schema ZM00## to your vendor schema group ##. The assignment should be independent of the purchasing organization. Tools → Customizing → IMG → Edit Project Choose: SAP Reference IMG radio button Materials Management → Purchasing → Conditions → Define Price Determination Process → Define Schema Determination Choose→ Determine Calculation Schema for Standard Purchase Orders. Leave Schema gp. POrg blank. Enter only your vendor schema group and your calculation schema. SAVE your assignment. © SAP AG. SCM521. 3-22. Only. Internal. Now change your condition type Z##A by assigning your new calculation schema YM00## to it as the supplementary schema instead of the standard calculation schema.. Use. Partner. 1-5. Internal. Only. SAVE your calculation schema.

(58) 1-8. Assign your schema group ## to vendor T-K521B## on the Purchasing data screen of the vendor master record for purchasing organization 1000. Logistics → Materials Management → Purchasing → Master data → Vendor → Purchasing → Change (Current) Enter the following data: Vendor:. T-K521B##. Purch organization:. 1000. Select: Purchasing data. Select: Enter Schema group, vendor. Internal. Only. Enter the following data: ##. Use. Partner. SAVE. SAP. SAP Only. Internal. Use. Partner. © SAP AG. SCM521. 3-23.

(59) Solutions Unit: Price Determination Topic: Analyzing Price Determination 2-1. Create a purchase order using the following data: Logistics-> Materials Management-> Purchasing → Purchase order → Create → Vendor/Supplying Plant Known. Partner. Vendor:. T-K521B##. Purchase org:. 1000. Purch. Group. Z21. Company Code:. 1000. Internal. Only. Enter the following date in the Header area of the purchase order:. Deliv. Date. Plant. Price. T-REL##. 100. 4 weeks from today. 1000. 100 EUR. SAP. PO quantity. SAP. Material. Use. Enter the following data in the Item overview area of the purchase order:. Use. Partner. Do not save the purchase order until you have answered steps 2-1-1 to 2-1-3. 2-1-1 Why must the price be entered manually?. Internal. The price must be manually entered because the system is unable to determine a valid price.. Only. 2-1-2 Which condition type has been assigned to the manually entered price? Select the Conditions tab in the Item details area of the purchase order. Condition type: PBXX 2-1-3 What calculation schema has been determined for the purchase order? Select the Conditions tab, and then choose the Analysis radio button. Calculation schema: ZM00## The R/3 System determined that calculation schema ZM00## was to be used based on the schema group ## assigned in vendor T-K521B##. SAVE Purchase order: ________________________. © SAP AG. SCM521. 3-24.

No results found