Quickstart REA Pricing - Archive

SAP AG Quickstart

June 2008 1

Quickstart REA PricingCalculation

Version 2.0

SAP AG Quickstart

June 2008 2

1 Contents1 Contents .............................................................................................................................. 2

2 Preliminary Remark ............................................................................................................. 3

3 Changes .............................................................................................................................. 3

3.1 Changes in version 2.0 ................................................................................................. 3

4 Introduction to the REA master data model .......................................................................... 4

5 Pricing calculation in general ............................................................................................... 7

6 Packaging price calculation.................................................................................................. 8

6.1 Item dependent fee ....................................................................................................... 8

6.2 Weight dependent fee ................................................................................................. 11

6.3 Petty rules, fraction formulas, fee formulas .................................................................. 15

6.3.1 Petty rules ........................................................................................................... 15

6.3.2 Fraction formulas ................................................................................................. 16

6.3.3 Fee formula ......................................................................................................... 17

6.3.4 Remnants ............................................................................................................ 18

7 Article price calculation ...................................................................................................... 19

7.1 Base Quantity ............................................................................................................. 19

7.2 Item dependent fee ..................................................................................................... 19

7.2.1 Deriving a dimensionless unit from a non dimensionless unit ............................... 22

7.3 Weight dependent fee ................................................................................................. 23

7.3.1 Derivation of Sales units ...................................................................................... 25

7.3.2 Remnants ............................................................................................................ 26

7.3.3 Fee Formula and fraction formula ........................................................................ 26

8 Price Formula .................................................................................................................... 27

9 Reference .......................................................................................................................... 28

10 Conventions ................................................................................................................... 29

10.1 Typographic Conventions ........................................................................................ 29

10.2 Icons ....................................................................................................................... 30

11 Copyright ....................................................................................................................... 31

SAP AG Quickstart

June 2008 3

2 Preliminary RemarkThe following document is a quick start to the REA pricing calculation. It begins with a short intro-duction to the REA master data model in section 4. With the start of section 6 it is explained howthe price in REA is calculated bottom up from the REA packaging to the REA Article (section 7).The document neither explains any customizing activities that influence the transactional behavior,nor does it discuss the recycling partner/price list set up. In addition to the master data REA usesterms like recycling partner, price list, license fee or splitting that are all part of a contract betweenthe REA user and a compliance scheme. Those contract management tasks are not explained inthis document.

After reading this document you should be able to understand the REA pricing calculation and toverify the calculation of license fees for all recycling partners in REA.

3 Changes

3.1 Changes in version 2.0 Formal revision due to transfer to SAP AG

Elaboration of the special condition use during price list access

SAP AG Quickstart

June 2008 4

4 Introduction to the REA master data modelThe REA master data consists of two main objects: REA Article and REA Packaging.

REA packaging is based on REA internal fractions. Figure 1 depicts the master data modelschematically. The colors in Figure 1 will be used consistently through out this document.

Fraction

Packaging

ArticleArticle

Figure 1: REA Master data scheme

REA article and REA packaging refer to the material number in the ERP Material master (MARA-MATNR). Hence neither REA articles nor REA packaging can exists without a corresponding MMentry. However it is possible that a REA article and a REA packaging refer to the identical MM entry(Figure 2).

Figure 2: Relationship to ERP Material master

REA internal fractions are maintained in the REA Customizing an assigned to one are many recy-cling partner fractions (Figure 3). It also possible to assign an internal fraction to a recycling partnerfraction without specifying a partner fraction. In this case there is no settlement with this particular

Material masterimR/3

ArtikelArticle

Packaging

Access isRead- only

SAP AG Quickstart

June 2008 5

recycling partner for that internal fraction. This mechanism is called cancellation of partner frac-tion requirement. This fraction assignment is out of scope of this document.

InternalInternal fractionfractionSyntheticSynthetic fibrefibre

RecyclingRecycling partnerpartner BBFractionFraction:: PlasticsmallPlasticsmall

RecyclingRecycling partnerpartner CCFractionFraction:: PlasticPlastic partsparts

RecyclingRecycling partnerpartner AAFractionFraction:: PlasticPlastic

Figure 3: Assignment internal fraction to recycling partner fraction by Customizing

An internal fraction in REA is a packaging material that can be assigned 1 to n times to a REApackaging with a defined weight / weight unit.

A REA packaging represents a component that consists of one or many internal fractions and thatcan be settled with one or many recycling partners. Both assignments are time dependent, so thatseveral packaging versions with a certain timeframe can be created. REA packaging can be of typeconsumed packaging, which can be directly identified in material movements by the declarationsystem, or of type sales packaging, which can be assigned to one are many REA articles as acomponent.

A REA Article represents finished product that must be reported to a recycling partner due to thelegal obligations of the REA user. In addition to the material number a REA article is identified bythe key values company code, country and sales unit. REA packaging and recycling partners areassigned to REA articles in a time dependent manner. REA Articles are directly identified in billingdocuments and/or material movements by the declaration system.

Figure 4 depicts the REA master data structuring. The REA Article and the REA Packaging are thetwo main components that form the REA master data. In addition to the keys and relationships ex-plained so far, REA articles and REA packaging can hold various attribute values that are generallydependent on the assigned recycling partner.

SAP AG Quickstart

June 2008 6

REAREA ArticleArticle

REAREA PackagingPackaging

REAREA FractionFraction

(n:m)

(1-n)

Cap

Aluminium Plastic Label

Bottle

Glass Label

Bottle

Figure 4: REA Master data

REA packagings are maintained by the transactions J7L5/J7L6/J7L7. The tab fraction is used tomaintain the internal fraction assignment. The tab partner is used to maintain the recycling partnerassignment. A REA packaging can only be settled with partners that are assigned to the packagingin a particular timeframe.

REA articles are maintained by transaction J7L1/J7L2/J7L3. The tab packaging is used to maintainthe REA packaging assignment. The tab partner is used to maintain the recycling partner assign-ment. A REA article can only be settled with partners that are assigned to the article in a particulartimeframe In case there are multiple recycling partners assigned in the identical timeframe licensefee splitting rules enable the user to split the license fee of the packaging between the assignedrecycling partners dependent on the business process.

REA articles can alternatively be maintained as reference article by transaction J7L0. Referencearticles are settled exactly as their referenced article. Reference articles are not discussed in thisdocument in detail.

Figure 5 summarizes the REA master data maintenance process.

SAP AG Quickstart

June 2008 7

Packaging Article Reference Article

Fractionassignment

Recycling partnerassignment

Packagingassignment

Recycling partnerassignment

Splitting definition

Referencing typedefinition

Article assignment

Fraction

Packaging

ArticleArticle

Fraction

Packaging

ArticleArticle

Fraction

Packaging

ArticleArticle

Figure 5: Process view

5 Pricing calculation in generalPricing calculation is carried out in REA by three possible mechanisms:

1. Weight dependent fee

2. Item dependent fee

3. Price formula

The weight dependent fee is calculated based on the amount of the weight of the recycling partnerfraction assigned to the REA packaging. The weight is multiplied with the price of the correspondingprice list item. Petty rules, fraction formulas and fee formulas may influence the weight dependentfee.

The item dependent fee is calculated based on the volume area class of the REA packaging. Thevolume area class’s price is taken from the corresponding price list item. Fee formulas may influ-ence the item dependent fee.

Weight/item dependent fee per packaging are then multiplied with the component quantity of thepackaging assigned to the article. The sum of all packaging’ weight and item dependent fees equalthe article’s license fee.

Alternative the article license fee may be calculated by a fee formula, which is an individually codedalgorithm that may be based on article or recycling partner fields and on business processes.

SAP AG Quickstart

June 2008 8

6 Packaging price calculationNavigation in the packaging maintenance is explained in [2].The price calculation of a packagingalways refers to the base unit of measure displayed in screen group [] Material Master Record ontab dimension (Figure 6).

Figure 6: Base unit of measure

Versioning of fraction assignment, recycling partner assignment and price lists are considered dur-ing price calculation.

6.1 Item dependent feeItem dependent fee is calculated per packaging for all recycling partners, which have the item de-pendent fee indicator set. Prerequisite is an assigned volume area class as shown in Figure 7. Inaddition a special condition type may also be used in conjunction with the volume area class.

Figure 7: Volume area class (VAC) 001 as key to item dependent fee (red rectangle)

SAP AG Quickstart

June 2008 9

The volume area class (and the special condition type) is used to access the price list items of thecorresponding price list version of the recycling partner. If no special condition is explicitly used, the“normal condition” 0 is used to access the price list items (Figure 8). If the special condition is notdefined as price list item, the “normal condition” 0 is used to access the price list in a second step.

Figure 8: Price list items (red rectangle is price list item of VAC 001 in Figure 7)

All price list items of item dependent fee have an item category V, A or L (Figure 8). The price isalways defined for a condition price unit (Per) and condition unit (Unit). If necessary an item dis-count can be applied (Dis%).

On tab pricing you can select the recycling partner entry (sorted after price list versions). With priceanalysis you reach Figure 9. The field base quantity price contains the quantity for which the priceis calculated and refers to the base unit of measure in Figure 6.

Figure 9: Base quantity

By selecting a row (representing version of the packaging within the price list version) you can na-vigate to the detailed display by pushbutton item-dep.Fee. (Figure 10).

SAP AG Quickstart

June 2008 10

Figure 10: item dependent fee details

Table 1 explains most important fields in Figure 10.

Column name Field value origin Description

Pricing Condition type Assigned to special conditiontype in REA customizing if pric-ing conditions are used

Holds discount of special con-dition in time dependent man-ner

Special condition type Assigned to r-partner in Figure7

Key to price list item

Volume Area Class Assigned to r-partner in Figure7


Sales Quantity (Price quantity) Determined at packaging inFigure 9.

Quantity base of price calcula-tion referring to base unit ofmeasure in Figure 6

Price Fee Price in partner currency ofprice list item in Figure 8 withdiscount (Price Fee W/O D *discount / 100)

Price in partner currency

Price Fee W/O D Price in partner currency ofprice list item in Figure 8


Partner Currency Partner currency of price listitem in Figure 8

Partner currency

SAP AG Quickstart

June 2008 11

Per Condition price unit in Figure 8 Condition price unit

Unit Condition unit in Figure 8 Condition unit

Table 1: Fields in detail screen

The item dependent fee is calculated after the following formula:

Sales Quantity * Price Fee W/O D / Per * ([Base Unit of measure / Unit]1 )

6.2 Weight dependent feeWeight dependent fee is calculated per packaging for all recycling partners, which have the weightdependent fee indicator set. If a special condition is defined as in Figure 11, it is used for price listitem access. If not the “normal condition” 0 is used as default (or in a second step). In addition thepackaging type weight dependent fee (not shown in Figure 11) may have an effect on the price cal-culation as described in section 6.3.

Figure 11: R-partner assignment (special condition type 11 in red rectangle)

The assigned internal fractions on tab fractions can be expanded to display the partner fraction ofthe desired recycling partner (Figure 12). In case the partner fraction requirement is lifted, no part-ner fraction is displayed. The effect of the level or the categories is explained in section 6.3.

1 Refers to the proportion between unit (of price list item) and base unit of measure of packaging inFigure 6. Both units shall be compatible.

SAP AG Quickstart

June 2008 12

Figure 12: R-partner fractions (red rectangle is example of fraction 00 Glas)

The special condition type of Figure 11 and the recycling partner fractions of Figure 12 are used toaccess the price list items of the corresponding recycling partner’s price list version in Figure 13. Allweight dependent price list items have the item category M. The price is always defined for a condi-tion price unit (Per) and condition unit (Unit). If necessary an item discount can be applied (Dis%).Typically discounts are linked to the special condition type either directly or by a pricing condition inREA customizing.

Figure 13: Price list items (red rectangle is recycling partner fraction 00 from Figure 12 andspecial condition type 11 from Figure 11)

SAP AG Quickstart

June 2008 13

On tab pricing you can select the recycling partner entry (sorted after price list versions). With priceanalysis you reach Figure 14. The field base quantity price contains the quantity for which the priceis calculated and refers to the base unit of measure in Figure 6.

Figure 14: Base Quantity

By selecting a row (representing version of the packaging within the price list version) you can na-vigate to the detailed display by pushbutton Weight-dep.Fee. (Figure 15).

Figure 15: Weight dependent fee details

Table 2 explains most important fields in Figure 15.




SAP AG Quickstart

June 2008 14



Partner fraction Derived from the internal frac-tion in Figure 12

Key to price list item if no Frac-tion price is defined

Fraction Price Fraction used mapped to part-ner fraction at the recyclingpartner


Internal Fraction Assigned to packaging in Fig-ure 12

Internal fraction which is as-signed to packaging.

Weight Fraction weight sum Sum of fraction weight

Weight Unit Unit taken from Condition unitin Figure 13

Unit of weight for fraction

PriceFee Price per item with discount(fraction weight * Price PartnerCurrency / per) * discount / 100

License fee per fraction withdiscount

PriceFee w/o Discount Price per item with discount(fraction weight * Price PartnerCurrency / per)

License fee per fraction without discount

Price Partner Currency Price in partner currency ofprice list item in Figure 13



Partner currency

Per Condition price unit in Figure13

Condition price unit


Percent Discount in Figure 13 Discount linked to the price listitem via special condition type

Table 2: Fields in detail screen

The internal fraction do no necessarily correspond one to one to partner fractions. The weight de-pendent fee is calculated for each partner fraction after the following formula:

Sales Quantity * Price Fee W/O D / Per * Weight ([fraction weight unit / Unit]2 ) * Per-cent/100

2 Refers to the proportion between unit (of price list item) and fraction weight unit in Figure 12.

SAP AG Quickstart

June 2008 15

6.3 Petty rules, fraction formulas, fee formulas

6.3.1 Petty rulesPetty rules are defined at the recycling partner based on contract information provided by the recy-cling partner ([1]). In general they are applied if different packaging material (fraction) are non-separatable components of packaging. Therefore a petty rule has an impact on the weight depen-dent fee in section 6.2. Petty rules are coded as function modules in REA and use several inputparameters. In REA petty rules are linked to the weight dependent fee packaging type in Figure 12.In addition the packaging must be defined as non-separable in Figure 16.

Figure 16: Material Properties in REA on tab dimensions

If the price of an article is calculated the packaging type of the assigned packagingoverrides the packaging type in Figure 11.

If the weight dependent fee packaging type is linked to a petty rule and the packaging is marked asnon-separable the petty rule is executed during weight dependent fee calculation. Figure 17 showsas example a fraction assignment to a packaging.

Figure 17: Fraction assignment

Figure 18 displays the corresponding weight dependent fee detail calculation as described in sec-tion 6.2. Figure 19 displays the same details after changing the separatability to non, so that a pettyrule is applied and the complete fraction weight is subtotaled with the majority fraction.

Figure 18: Weight dependent fee without petty rule

SAP AG Quickstart

June 2008 16

Figure 19: Weight dependent fee with petty rule

Petty rules may be applied to a single REA packaging only, or to several REA packaging assignedto one REA article grouped by the packaging level and/or he packaging type weight dependent fee.

6.3.2 Fraction formulasFraction formulas reflect recycling partner regulation that deviate from the default calculationscheme in REA ([1]). Fraction formulas can be used to (partially) exclude recycling partner fractionsfrom the weight and/or fee calculation based on attributes, such as packaging category, packaginglevel or packaging type. Fraction formulas are coded as function modules with various input para-meters. Hence the fraction formulas only influence the weight dependent fee. Figure 20 shows asexample the fraction assignment with the attributed recycling partner fractions. The fraction formulaevaluates those attributes according to the recycling partner’s settings and excludes in this case allrecycling partner fractions other than marked with level 1 and domestic from the weight dependentfee calculation in Figure 21.

Figure 20: Attributes of recycling partner fractions (Category, Packlevel)

SAP AG Quickstart

June 2008 17

Figure 21: weight dependent fee filtered by fraction formula

If a fraction formula is applied following columns hold data in addition to Table 2:


Fraction Weight with fractionformula

Fraction weight sum after for-mula execution ( FractionWeight * Condition Factor)

Sum of fraction weight

PriceFractionFormula Price per item with discount(fraction weight * Price PartnerCurrency / per) * discount / 100after fraction formula execution


PriceFractionFormula w/oDiscount

Price per item with discount(fraction weight * Price PartnerCurrency / per) after fractionformula execution


FractionFormula Name of the Function module Function module that codes theformula

Condition Factor Factor returned by the formula The factor is multiplied with thefraction weight

Table 3: Fields of fraction formula

6.3.3 Fee formulaFee formulas influence the calculation of weight and/or item dependent fee. After the default calcu-lation scheme described in section 6.1 and section 6.2 a formula is applied that may change thepreviously calculated price. Fee formulas are based on the recycling partner’s regulations and arecoded as function modules. Figure 22 shows the fee formula execution in the details of the weightdependent price calculation.

Figure 22: Fee formula execution

If a fee formula is applied following columns hold data in addition to Table 2:


PriceFeeFormula Price per item after fee formulaexecution

License fee per fraction

FeeFormula Name of the Function module Function module that codes the

SAP AG Quickstart

June 2008 18

formula

Condition Factor Factor returned by the formula The factor is multiplied with thefraction price

Table 4: Fields of fee formula

6.3.4 RemnantsIf a packaging with non dimensionless component units is used, it is possible to define a remnant inFigure 23. This remnant is applied to all fraction weight quantities of the packaging, before execut-ing the pricing calculation.

Figure 23: Remnants on tab dimension

SAP AG Quickstart

June 2008 19

7 Article price calculationPer default the price calculation of the article iterates on the price calculation of each assigned REApackaging and sums up the weight and item dependent fees of the particular packaging for the re-cycling partner of interest. The default process may be changed by petty rules that are configuredto act across several packaging (see section 6.3.1). The complete license fee is calculated by add-ing weight and item dependent fee. Versioning of price lists, recycling partner and packaging as-signment and of the assigned packaging is taken into account. Navigation in the article mainten-ance is explained in [2].

7.1 Base QuantityThe price calculation of the article is executed for a variable Base Quantity of a selected unit ofmeasurement (UoM) in Figure 24.

Figure 24: Base Quantity with UoM PC

7.2 Item dependent feeThe item dependent fee is calculated from all packaging that have an active item dependent feeindicator. The component quantity/unit is directly used in the calculation. The volume areaclass/special condition type is derived from the packaging assignment, too.

Figure 25: Packaging assignment (component quantity, item dependent fee indicator, Vo-lume Area Class in red rectangle)

On the pricing tab you navigate to the Price analysis in Figure 26 by selecting a price list version ofthe recycling partner.

SAP AG Quickstart

June 2008 20

Figure 26: Price analysis

By selecting a version you navigate to the details (Figure 27) by the pushbutton Item dependentFee.

Figure 27: Item dependent fee details

Table 5 explains the most important fields in Figure 27,






Packaging Packaging assigned in time-frame in Figure 25

Packaging the item is based on

Volume Area Class Assigned to packaging in Fig-ure 25


Sales Quantity Determined from componentquantity in Figure 25.

The component quantity andthe proportion of componentunit and base unit of the pack-aging (Figure 6) is taken intoaccount. During item depen-dent fee calculation the com-ponent quantity is convertedinto a dimensionless unit byvarious means (section 7.2.1).

Sales Unit Key to article in Figure 24 Sales unit of the article

Quantity Component quantity in Figure25

Component Unit Component unit in Figure 25



SAP AG Quickstart

June 2008 21

Price Fee W/O D Price in partner currency ofprice list item in Figure 8



Partner currency

Per Condition price unit in Figure 8 Condition price unit


Table 5: Fields on detail screen

For each item (packaging) the item dependent fee is calculated after the following formula:

Sales Quantity * Price Fee W/O D / Per * ([Base Unit of measure / Component Unit]3 )

3 Refers to the proportion between base unit of measure of the packaging in Figure 6 and compo-nent unit of measure of the assignment in Figure 25.

SAP AG Quickstart

June 2008 22

7.2.1 Deriving a dimensionless unit from a non dimensionless unitFigure 28 illustrates the detail screen of a packaging, which is assigned with a non dimensionlesscomponent unit and active item dependent fee indicator. The field help to convert the non dimen-sionless component quantity into a dimensionless by a simple rule of three:

Dimensionless component quantity = non dimensionless component quantity in Figure 25 / <com-ponent quantity> in Figure 28 * Quantity in Figure 28

The Input in Additional data must be compatible to the component unit in Figure 25.A component unit of mass requires a value and a unit in Net weight in Figure 28.

Figure 28: Additional data on the detail screen

SAP AG Quickstart

June 2008 23

7.3 Weight dependent feeThe weight dependent fee is calculated from all packaging that have an active weight dependentfee indicator. The component quantity/unit is directly used in the calculation. In addition the specialcondition type and the packaging type weight dependent fee are used, too.

Figure 29: Packaging assignment (component quantity, item dependent fee indicator, Spe-cial Condition Type, packaging type weight dependent fee red rectangle)

On the pricing tab you navigate to the Price analysis in Figure 30 by selecting a price list version ofthe recycling partner.

Figure 30: Price analysis

By selecting a version you navigate to the details (Figure 31) by the pushbutton Weight dependentFee.

Figure 31: Weight dependent fee details

Table 6 explains the most important fields in Figure 31:

SAP AG Quickstart

June 2008 24






Packaging Packaging assigned in time-frame in Figure 25

Packaging the item is based on

Partner Fraction Assigned to each packaging inFigure 12


Fraction Price Fraction used mapped to part-ner fraction at the recyclingpartner


Internal Fraction Assigned to packaging in Fig-ure 12

Internal fraction which is as-signed to packaging.

Quantity Component quantity calculatedfrom Figure 25

The component quantity is al-ways calculated according tothe packaging’ base unit ofmeasure

Component Unit Component unit in base unit ofmeasure of the packaging(Figure 6)

Weight Fraction weight sum Sum of fraction weight

Weight Unit Unit taken from Condition unitin Figure 13

Unit of weight for fraction

PriceFee Price per item with discount(fraction weight * Price PartnerCurrency / per) * discount / 100


PriceFee w/o Discount Price per item with discount(fraction weight * Price PartnerCurrency / per)





Partner currency

Per Condition price unit in Figure13

Condition price unit


Percent Discount in Figure 13 Discount linked to the price list

SAP AG Quickstart

June 2008 25

item via special condition type

Table 6: Fields on detail screen

For each item (packaging) the item dependent fee is calculated after the following formula:

Component Quantity * Price Fee W/O D / Per * ([Base Unit of measure / Component Unit]4) * Percent / 100

7.3.1 Derivation of Sales unitsIf a article is sold in a sales unit, in which he is not defined in REA, REA uses the reference salesunit to calculate the quantity flow (Figure 32).

Figure 32: Reference Sales unit

On tab sales units you get an overview on all sales units and the reference sales unit. In order tocalculate the price of a sales unit that is derived from the reference unit you have to multiply theprice of the reference unit with the proportion taken from the material master as listed in Figure 33.

Figure 33: Proportion of sales units

4 Refers to the proportion between base unit of measure of the packaging in Figure 6 and compo-nent unit of measure of the assignment in Figure 25.

SAP AG Quickstart

June 2008 26

7.3.2 RemnantsIf a component with non dimensionless component units are assigned, it is possible to define aremnant in Figure 34. This remnant is applied to all fraction weight quantities of the particular pack-aging, before executing the pricing calculation.

Figure 34: Remnants of packaging

7.3.3 Fee Formula and fraction formulaFee formulas are applied as described in section 6.3.3 to articles to. Based on the configuration thefee formula is applied separately for each assigned packaging or in one step on all assigned pack-aging.

The fraction formula is applied as described in section 6.3.2.Figure 35 illustrates a combination offee and fraction formula.

Figure 35: Fee and fraction formula

SAP AG Quickstart

June 2008 27

8 Price FormulaPrice formulas override the default fee calculation, with an individually coded algorithm. Their pres-ence is indicated as shown in Figure 36.

Figure 36: Price formula

SAP AG Quickstart

June 2008 28

Kind regardsYour REA teamFebruary 2008

9 Reference[1] QuickStart_REA_RPartner&PricelistDialog.doc

[2] QuickStart_REA_MasterDataDialogs.doc

[3] QuickStart_REA_Infosystems&Declarations.doc

SAP AG Quickstart

June 2008 29

10 Conventions

10.1 Typographic ConventionsType Style Use

Interface Text Words or characters that appear on the screen.This includes system messages, field names,screen titles, pushbuttons, menu names, and menuoptions.Cross-references to other documentation.

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

User entry Exact user entry. These are words and charactersthat you enter exactly as they appear in the docu-mentation.

Example text Screen output. This includes file and directorynames and their paths, messages, source code,names of variables and parameters, as well asnames of installation, upgrade and database tools.

<Variable User Entry> Variable user entry. Pointed brackets indicate thatyou replace these words and characters with ap-propriate entries.

NAME Names of elements in the SAP System. These in-clude report names, program names, transactioncodes, table names, and programming languageelements that are framed by body text, for exampleSELECT and INCLUDE.

KEY Keys on your keyboard. These include functionkeys (for example, F2 and the ENTER key).

SAP AG Quickstart

June 2008 30

10.2 IconsIcon Meaning

Caution

Example

Note

Recommendation

Syntax

SAP AG Quickstart

June 2008 31

11 Copyright© Copyright 2008 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 permis-sion of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other soft-ware vendors.

Microsoft, Windows, Outlook, and PowerPoint 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, and Informix are trademarks orregistered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Mas-sachusetts 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 imple-mented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP Recycling Administration is a registered trademark of SAP AG.

SAP AG Quickstart

June 2008 32

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respective compa-nies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated compa-nies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Groupshall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictableand severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be mod-ified or altered in any way.

Quickstart REA Pricing - Archive

Documents

Transcript of Quickstart REA Pricing - Archive