sapnote_0000062536(1)

28.07.2012 of 36

SAP Note 62536 - Info: Conditions in Profitability Analysis

Note Language: English Version: 18 Validity: Valid Since 21.03.2002

Summary

Symptom

In Profitability Analysis (CO-PA) you can calculate imputed values usingthe condition tool.

This note is intended to give you an idea of how to use this tool. Firstthe used technical terms and the interaction of the individual componentsof the condition tool are described. Then an example is used to illustratehow the condition tool lets you meet your business requirements inProfitability Analysis.

The note applies to all users (end users, consultants, and so on) who wantto familiarize themselves with the conditions technique in ProfitabilityAnalysis and who would like to obtain information in addition to that inthe online documentation.

This note does not claim to be complete. A complete explanation couldhardly be achieved by just one note due to the great flexibility of thecondition tool. However, this note aims at explaining in detail thosefunctions of the condition tool that are most frequently required inProfitability Analysis.

The note applies to all releases where it describes the conceptualprocedure for working with the condition tool. The actual examples refer tothe Customizing functions available in Release 3.0. Consequently,deviations from Releases 2.1 and 2.2 may exist in certain instances.

Other terms

Valuation, conditions, actual data, planning, costing sheet, accesssequence, condition table, SD/CO-PA interface, condition note

KE4U, KE44, KE47, KE45, KE48, KE4A, KE46, ZKPRS, MBEW-ZKPRS

Reason and Prerequisites

Valuation with conditions

Solution

Introduction: Valuation in Profitability Analysis

Valuation is used for finding and calculating fictitious values inProfitability Analysis. It can be used for updating both actual and plandata.

The following methods of valuation are available:

28.07.2012 of 36


o Valuation using conditions and costing sheets

Using the condition technique, you can attribute values needed forfor analysis purposes in Profitability Analysis, even if thesevalues are not known at the time of the actual posting. Forexample, you can determine sales commissions, discounts, orshipping costs not yet known at the time of billing, and use thisinformation to analyze your sales transaction.For information on using SD costing sheets in CO-PA planning, seeto section 6.7.

o Valuation using product costing

Valuation using product costing lets you find the cost of goodsmanufactured for the product sold when you post a sales transactionto Profitability Analysis. For example, you can find the variableand fixed cost components for the product sold and compare these tothe revenues and sales deductions copied from the billing documentfor the sales transaction.

o Valuation using customer-defined valuation routines

Customer-defined valuation routines let you calculate imputedvalues that cannot be determined using the two preceding methods.You can program your own valuation logic.You can find more detailed information on this topic where youdefine your CO-PA valuation strategy (transaction KE4U, screen"Valuation Strategy: Details") in the F1 help for the "Exit no."field. See also the documentation on SAP enhancement COPA0002. InRelease 3.0, you can access this documentation in transaction CMOD.

A so-called "valuation strategy" determines how valuation is carried outin Profitability Analysis. It determines which methods are used to fill theindividual value fields, and in which order these methods are to beapplied.

For example, a typical valuation strategy might have the followingstructure:

Valuation strategy | x--------Product cost estimate | x--------Costing sheet (conditions) | x--------User exit

With this valuation strategy, the system first reads a product costestimate for the product or material type specified in the document beingvaluated. Then it uses a costing sheet to calculate additional values.Finally, it reads the customer-defined valuation routines.

28.07.2012 of 36


This note deals primarily with valuation using costing sheets. Thefollowing chapters describe this approach in detail.

1. Terminology of the condition technique

Before you use the condition tool, it is important to understand sometechnical terms used in Customizing for Profitability Analysis. Thischapter is intended to explain these terms. First the terms are explainedfrom a more technical standpoint. Then their controlling significance isillustrated using concrete examples (see section 4).

1.1 Costing sheets

A costing sheet determines which conditions are used to calculate imputedcosts, in what order these conditions are used, and what dependencyrelationships exist between the individual conditions. For example, you cansay that sales commission should be calculated on the basis of the salesrevenues.In sum, the tasks of the costing sheet are to:

o specify the basis for calculating additional values

o define subtotals

o define any dependency relationships between conditions (by groupingcondition types) and determining the order in which they arecalculated in the costing sheet

1.2 Condition types, conditions and condition records

The condition type defines the characteristics of a condition. For example,the condition type distinguishes different surcharges or reductions (i.e.percentage surcharges vs. quantity-dependent surcharges) or defines fixedprices (i.e. standard prices). In addition, conditions can be used todefine the basis for calculating other conditions in the costing sheet.

Generally speaking, a condition type represents a number of conditions thatapply when you calculate a value. For example, a surcharge might depend onvariable values such as the current value of the CO-PA characteristics"Customer" and "Product" or the value in the value field "Sales volume".Information on the surcharge calculated on the basis of these variablevalues is be stored by the system in the form of so-called "conditionrecords".

The definition of a condition type consists of the following:

o condition category

o calculation type

o condition class

28.07.2012 of 36


o scale basis

Furthermore, special control flags can be set for each condition type tocontrol whether or not certain parameters can be changed (i.e. during acondition analysis) or whether the condition master record can be modified.Further details on these terms are provided in the following sections.

By assigning an "access sequence" to a condition type, you determine whichcondition tables the system has to read to find valid condition records forthe valuation. Condition records are stored in different condition tables,which are defined with different combinations of characteristics. Thus byassigning an access sequence to the condition type, you determine whichcharacteristic or characteristics the condition records (percentages orfixed amounts) for this condition type for this condition type aredependent on. Note that it is not mandatory to assign an access sequence toall condition types (see section 1.3).

The next section explains the aforementioned fields found in the definitionof a condition type.

1.2.1 Condition category:-------------------------The condition category classifies conditions according topredefined categories, such as "Base amount" or "Price".

The following condition categories can be used in ProfitabilityAnalysis:

E Cash discount G Cost of a product K Base amount S Standard cost T Moving average cost " " Blank for conditions which belong to none of thesecategories. This includes surcharges and deductions to be calculatedin the costing sheet.

1.2.2 Calculation type:-----------------------The calculation type determines how the system is to calculateprices or surcharges/discounts for a condition. For example, thesystem can calculate a discount depending on a quantity or on avalue scale.

The following calculation types can be used in ProfitabilityAnalysis:

A Percentage B Fixed amount C Quantity-dependent D Gross-weight-dependent E Net-weight-dependent F Volume-dependent

28.07.2012 of 36


1.2.3 Condition class:----------------------A condition class comprises several condition types.

The following condition classes can be used in ProfitabilityAnalysis:

A Discount or surcharge B Price

1.2.4 Scale basis:------------------The scale basis defines how the system is to interpret the scale ofa condition. The scale may be a quantity scale or a value scale.

The following scale bases can be used in Profitability Analysis:

B Value scale C Quantity scale D Gross weight scale E Net weight scale F Volume scale

1.2.5 Change options:---------------------The change options allow you to determine which parameters of acondition type the user can change during condition analysis.You can allow or forbid changes to the amount or percentage, thevalue, the calculation type, or the quantity conversion of acondition type. In addition, you can make it possible or impossibleto delete a condition type from the document.

1.2.6 Condition master record maintenance:------------------------------------------You can define whether scales are to be checked or not when youmaintain condition master records. For example, you could specifythat scale rates must always be maintained in ascending order.You could also fix the +/- sign of the condition type.

1.2.7 Access sequences and condition tables:--------------------------------------------An access sequence must be assigned to any condition type that isnot of the condition category K, G, S, T or E. This means that youmust assign an access sequence to condition types for calculatedvalues as well as fixed amounts of the category " ". The accesssequence allows you to maintain condition records for the conditiontype.

In the access sequence, you determine:

28.07.2012 of 36


- which condition tables the system reads to access conditionrecords

- the order in which these condition tables are read

- the field contents with which they are read

Thus the access sequence is a kind of search strategy, whichinforms the system which condition tables to search in for validdata for a given condition.The structure of a condition table defines a kind of key for thecondition records. This key contains the characteristic values thatexactly identify the individual condition record. The conditionrecord contains the values that are to be applied to a documentwhen the characteristic values in the given document match those inthe key for that condition record. A condition record can contain,for example, a fixed price for a certain product or a percentage tobe added or deducted for a certain customer. The order of thecondition tables in the access sequence determines which individualcondition record or records should be applied in which order.

o Example:

You want to define a percentage surcharge that depends on thecharacteristic "Product group". At the same time, you also want todefine a special percentage surcharge for certain individualproducts. If no surcharge is defined for a specific product, thesystem should apply the surcharge for the appropriate productgroup. In other words, the surcharge for individual products shouldhave a higher priority than the surcharge for product groups.To achieve this, you first need to create two condition tables: onefor the characteristic "Product group" and another for thecharacteristic "Product". Then you create access sequence 'ZZ01',which accesses the these condition tables: first the table"Product" (since you want this table to take priority) and then thetable "Product group". Once you have assigned this access sequenceto a condition type, you can then maintain the correspondingcondition records.

Overview: Access sequence Condition table -------------------------------------- 'ZZ01' Product Product group

1.3 Defining condition types in Profitability Analysis

The settings described in the previous section make it possible for you todefine a number of different kinds of condition types. This section isintended to give you an overview of all the possible combinations ofsettings for condition types in Profitability Analysis and to illustratehow these are used with brief examples.The examples here are only intended to show you the various possibilitiesfor defining condition types and demonstrate how these possibilities affect

28.07.2012 of 36


the maintenance of condition records. One example illustrates, forinstance, how to define a percentage discount.

Open questions such as "How do I calculate a discount on the basis ofrevenue?" and similar questions will be answered in section 4.

Abbreviations used: Ctype : condtion type Calcr.: calculation rule C.cl.: condition class Ref.: reference base AccS.: access sequence

Condition type Ctype Calcr. C.cl. Ref. AccS. ------------------------------a) Define tracing factor K B B - -

b) Define prices from material masterba) internal price acc. to price control G C B - -bb) standard price S C B - -BC) moving average price T C B - -

c) Define cash disc. from cust. master E A A - -

d) Define surcharge/discount in percentda) not scaled - A A - yesdb) with value scale - A A B yesdc) with quantity scale - A A C yes

e) Define quantity-dep. surcharge/discountea) not scaled - C A yeseb) with value scale - C A B yesec) with quantity scale - C A C yes

f) Define fixed amountfa) not scaled - B B yesfb) with value scale - B B B yesfc) with quantity scale - B B C yes

The change options and the settings for condition master maintenance can bedefined in any way for any of these combinations.

The following contains examples for the condition types listed above. Wherean access sequence is allowed, assume that it accesses a condition tablethat uses the characteristic "Material group".

o Example for (a) :A base condition for revenues transferred from Sales andDistribution (SD). This condition type can then be used in acosting sheet to calculate surcharges or deductions depending onthe revenue.

o Example for (b) :The appropriate price is read from the material master. Forexample, suppose that the standard price for material "M099312" is100.00 USD apiece. If you have sold 5 units of this material, the

28.07.2012 of 36


condition takes on the value 500.00 USD.If in the material master you have defined a 'future price'(accounting view, field MBEW-ZKPRS), this future price is alwaystaken into account for the CO-PA valuation if you call thevaluation with a price date that is after the valid-from date(field MBEW-ZKDAT) belonging to the 'future price'.

o Example for (c) :The percentage for the cash discount is read from the terms ofpayment in the customer master. If the payment terms provide for acash discount of 3% for a payment within 14 days, the percentage isdetermined as 3%.

o Example for (da) :For material groups '312', '313' and '314', you can maintain thefollowing condition records:

Material group Amount Unit of measure 312 1 % (percentage sign is inserted 313 2 % automatically by thesystem!) 314 1.5 % ....

These condition records can be used, for example, to calculate theexpected outgoing freight.

o Example for (db) :For material group '312', you can define the following value scale:

From value Scale currency Amount Unit of measure 10,000 USD 3 % 50,000 USD 3.5 %

This lets you define the expected sales commission depending on therevenue generated.

o Example for (dc) :For material group '312', you can define the following quantityscale:

From quantity Unit of measure Amount Unit 1000 PI 1 % 5000 PI 2 %

Thus you can calculate the expected discount depending on thequantity sold.

o Example for (ea) :For material group '312', you can define the following conditionrecord:

Material group Amount Unit per Unit of measure

28.07.2012 of 36


312 1 USD 1 IT

Thus you can assess 1 USD per item for packaging material.

o Example for (eb) :For material group '312', you can define the following value scale:

From value Currency Amount Unit per Unit of measure 100 USD 0.10 USD 1 IT 500 USD 0.20 USD 1 IT

o Example for (ec) :For material group '312', you can define the following quantityscale:

From quantity Unit of meas. Amount Unit per Unit ofmeasure 1,000 PI 0.01 USD 1 IT 10,000 PI 0.03 USD 1 IT

o Example for (fa) :For material group '312', you can define the following conditionrecord:

Material group Amount Unit 312 100 USD

o Example for (fb) :For material group '312', you can define the following value scale:

From value Scale currency Amount Unit 1000 USD 20 USD 5000 USD 30 USD

o Example for (fc) :For material group '312', you can define the following quantityscale:

From quantity Unit of measure Amount Unit 1,000 IT 50 USD 10,000 IT 70 USD

2. Relationship between the individual components of the conditiontoolThe relationship between these components can be shown in a simplifiedmanner as follows:

28.07.2012 of 36


Costing sheet | x----> condition type (N) | x----> access sequence (0 or 1) | x----> condition table (N) | x----> condition record (N)

The costing sheet represents the framework for valuation using conditions.It determines the order in which the conditions are processed. You canassign one access sequence to a condition type. The access sequence in turncan access one or more condition tables, while a condition table can beused by one or more access sequences. Finally, you can define any number ofcondition records for each condition table.

3. Conditions in the data flow of Profitability Analysis

As stated earlier, a valuation strategy controls how valuation isperformed, and thus also controls valuation using conditions.Now the question remains: at what point in time is this valuation strategy-- and thus the costing sheet(s) that it contains -- processed when data isupdated in Profitability Analysis?

3.1 Actual postings

When actual postings are transferred to CO-PA, the system always firstcopies the data from the sender document (sales order or billing document).For example, characteristics such as the sales organization or the productare copied from the sender document to the CO-PA line item, and quantitiesand values are entered into the quantity and value fields of the CO-PA lineitem according to how you defined the corresponding interface (SDinterface) in Customizing for Profitability Analysis.Next, the system performs derivation to add further characteristics thatare only relevant in Profitability Analysis. Then the appropriate valuationstrategy is read and the valuation methods specified there (valuation usingproduct costing, costing sheets and/or user exits) are processed in theorder specified. Finally, the new line item is posted.

The following is a schematic diagram of how actual data is posted:

28.07.2012 of 36


Document from sender application | Characteristics copied | Amounts/values copied | Derivation | Valuation | Posting | Line item in Profitability Analysis

3.2 Planning

The procedure in planning differs only sligthly from the one for actualpostings. First, data entered in the planning layout during a planningsession is copied to the plan line items. Derivation is also performedautomatically for the characteristics specified, and the quantities andvalues are updated. However, unlike with actual data, valuation in planningis not performed automatically. You need to execute it explicitly. If youdo so, the system reads the corresponding valuation strategy and processesthe valuation steps defined there.

The data flow in planning can be represented as follows:

Data from planning session | Characteristics copied | Amounts/values copied | Derivation | Valuation (if explicitly performed) | Posting | Plan line item in Profitability Analysis

3.3 Data for valuation using conditions

As you can see from this description, all the characteristics and all knownquantities and values are available in the line item for use in valuation.Valuation lets you then add further values to this line item. To find outwhich characteristics and values are available for reference duringvaluation -- this can be all the characteristics of an operating concern --for actual postings, you have to analyze the field assignments made inCustomizing for the corresponding interface. In planning, you need toanalyze the fields of the planning layout.

28.07.2012 of 36


4. How to use the "condition" technique to meet your management requirements: Example

While the preceding sections primarily explained the technical aspects ofthe "condition" technique, this section will attempt to illustrate how youcan use conditions to help meet your business and management requirementsin Profitability Analysis.

4.1 Global settings of the operating concern

4.1.1 Fields of the operating concern

In this example, we will be working in an operating concern that containsthe following fields:

Field Description -------------------------- * Quantity fields VVIQT Invoiced quantity in sales units VVSQT Invoiced quantity in stockkeeping units .... * Value fields VV010 Revenue VV020 Quantity discount VV030 Customer discount VV040 Material discount VV050 Price reduction VV060 Other discounts VV070 Cash discount VV110 Imputed outgoing freight VV120 Packaging VV130 Sales commission VV140 Transfer price .... * Characteristics VKORG Sales organization ARTNR Material number WERKS Plant ....

4.1.2 Maintaining the SD interface

The following fields are copied from the billing document:

* SD quantity fields --> CO-PA quantity fields (transaction KE4M) ............................................................... FKIMG Invoiced quantity --> VVIQT Inv. quantity in VME FKLMG Invoice quan. LME --> VVSQT Inv. quantity in LME

28.07.2012 of 36


* SD conditions --> CO-PA value fields (transaction KE4I) ........................................................... PR00 Price VV010 Revenue PI00 Price intercom. bill. VV010 Revenue KP00 Pallet discount VV020 Quantity discount KP02 Mixed pallet disc. VV020 Quantity discount BO03 Customer rebate VV030 Customer discount K029 Material group VV040 Material discount K004 Material VV040 Material discount K030 Customer/mat.group VV050 Price reduction K020 Price group VV060 Other discounts SKTO Cash discount VV070 Cash discount KF00 Freight VV110 Imputed outg.freight VPRS Cost VV140 Transfer price ....

4.1.3 Valuation strategy

We will use valuation strategy '001', which so far only calls for valuationusing product costing (transaction KE4U):

Sequence Appl. Cost.sheet Name Prod.cost Quantity field Exitno.

---------------------------------------------------------------------- 10 X VVIQT</>

The valuation strategy is assigned to record type "F" for actual billingdocuments (transaction KE44) :

Pt.of val. Rec. type Plan vers. Val.strat. Name

---------------------------------------------------------------- 01 F 001 Actualvaluation</>

4.2 What should valuation using conditions do?

The transfer price is to be subtracted from the net revenue, which isrevenue minus the customer discount and price reduction. The amount thusdetermined represents the basis for calculating the sales commission.Commission should be a percentage rate that can differ for the differentsales organizations. Furthermore, you also need to determine the commissionseparately for certain materials within individual sales organizations.It should be possible to calculate outgoing freight separately for eachplant as a percentage of the transfer price.Based on the quantity sold, you also want to calculate imputed costs fordispatch packaging separately for each plant. In certain cases the dispatchpackaging should also depend on the material sold.

4.3 Concept for valuation with conditions that meets the above

28.07.2012 of 36


requirements

4.3.1 Analysis of the requirements

First of all, the requirements listed in section 4.2 mean that you need todetermine three conditions:

* commission * outgoing freight * dispatch packaging

The commission should be based on the difference between the net revenueand the transfer price. The net revenue results from the gross revenueminus the customer discount and price reduction. The outgoing freight andthe dispatch packaging are to be based on the transfer price and the salesvolume, respectively.

The formula that needs to be defined using conditions therefore looks likethis:

Line Element ----------------------------------------------------------------- 10 Revenue 20 % Customer discount 30 % Price reduction ------------------------------------------ 40 Net revenue ------------------------------------------ 50 % Transfer price ------------------------------------------ 60 Basis for commission ------------------------------------------ 100 Commission = percentage/100 * line 60

300 Dispatch packaging = amount * quantity sold 310 Outgoing freight = percentage/100 * line 50

When you create a billing document, the revenue, customer discount, pricereduction and transfer price are transferred from Sales and Distribution(SD) to Profitability Analysis. In Profitability Analysis, lines 40, 60,100, 300 and 310 above need to be calculated, and the results of lines 100,300 and 310 must be copied to the corresponding value fields.

4.3.2 Concept for valuation using conditions

To be able to define the above calculation using conditions, you need todefine a condition type for each line except the totals lines 40 and 60,which can be calculated without condition types.As stated earlier, the costing sheet represents the framework for workingwith conditions. It determines how individual conditions are calculated andhow they relate to one another.

It is therefore necessary to define a costing sheet in which the individualcalculation lines are represented by condition types.

The layout for a costing sheet 'ACT001' which defines the above calculationwould be as follows:

28.07.2012 of 36


Step Counter Cond.type Description From To ----------------------------------------------------------------- 10 0 REVN revenues 0 0 20 0 DISC customer discount 0 0 30 0 DISP price reduction 0 0 40 0 net revenue 10 30 50 0 COGS transfer price 0 0 60 0 basis for commission 40 50 110 0 PROV commission 60 0 300 0 OUPA dispatch packaging 0 0 310 0 OUTF outgoing freight 50 0

According to the requirements, the commission is to be determined based onthe characteristics "Sales organization" and "Material". To be able tomaintain condition records for condition PROV depending on the mentionedcharacteristics, you need to define an access sequence Z100. Since thecondition records must be determined depending on two different possiblecombinations - sales organization only and sales organization/material -you must define two condition tables: A502 (with the characteristics 'salesorganization' and 'material') and A503 (with the characteristic 'salesorganization').

Overview: Condition type Access sequence Condition table ----------------------------------------------------- PROV Z100 A502 A503

The outgoing packaging is to be determined depending on either the plant orthe combination of plant and material, and should be dependent on thequantity of the good sold. Again, you need two condition tables here: A505(with the characteristics 'plant/material') and A506 (with thecharacteristic 'plant'). These tables are accessed by access sequence Z200.

Overview: Condition type Access sequence Condition table ----------------------------------------------------- OUPA Z200 A505 A506

The outgoing freight must be determined for each plant. Thus, you needaccess sequence Z300 which accesses a condition table with characteristic'plant'. Since a condition table may be used for various access sequences,you can use table A506, which you already defined in the previous step.

Overview: Condition type Access sequence Condition table ----------------------------------------------------- OUTF Z300 A506

Conditions REVN, DISC, DISP and COGS are so-called base conditions, whichprovide the basis for calculating the other conditions. They do not requirean access sequence. The condition values transferred from the SD billingdocument are the source for these conditions.

Consequently, these conditions have to point to the corresponding valuefields in the CO-PA line item. Your conditions should therefore be assignedas follows:

28.07.2012 of 36


Condition (CO-PA) -------> Value field ------------------------------------------------------------------- COGS Transfer price VV140 Transfer price DISC Customer discounts VV030 Customer discount DISP Price reduction VV050 Price reduction OUPA Dispatch packaging VV120 Dispatch packaging OUTF Outgoing freight VV110 Imputed out.freight PROV Commission VV130 Sales commission REVN Revenue VV010 Revenue

Conditions COGS, DISC, DISP and REVN are assigned to the same value fieldsas the SD conditions for revenue, customer discount, price reduction andtransfer price (see section 4.1.2). When you post a billing document, theSD condition values are copied to these CO-PA value fields. And since theCO-PA conditions refer to the same value fields, the SD condition valuesare then available for use in the CO-PA costing sheet. Thus, there is adirect link between the SD conditions from the billing document and theconditions defined in CO-PA.

---------------------------------------------------- Data flow: SD condition ---> Value field ---> CO-PA condition ---------------------------------------------------- Example: PR00 ---> VV010 ---> REVN ----------------------------------------------------

The condition 'OUPA' (dispatch packaging) is to be dependent on thequantity, defined as the invoiced quantity in sales units. In our example,this is the quantity field 'VVIQT' (see section 4.1.2).

4.3.3 Realization of the concept using the condition tool

In Customizing for Profitability Analysis, special functions are providedfor maintaining the individual elements of the condition tool. Looking atthe relationships illustrated in section 2 between costing sheets,condition types, access sequences and condition tables, it is recommendedthat you proceed "top-down" when realizing your requirements. This meansthat you first have to create the condition tables, since these are aprecondition for defining access sequences. After definitng the accesssequences, you can define the condition types and then finally group themtogether in a costing sheet.

4.3.3.1 Defining the condition tables-------------------------------------

Use the IMG activity "Maintain condition tables" to create the followingtables:

Table 502 Condition table 'sales organization/material'

Selected fields Field catalog ------------------------------------------------------- Long key word Long key word Sales organization ABC indicator ---> Material ABC classification Order reason Volume rebate group ....

28.07.2012 of 36


Table 503 Condition table 'sales organization'

Specific fields Field catalog ------------------------------------------------------- Long key word Long key word ---> Sales organization ABC indicator ABC classification Order reason Volume rebate group ....

Table 505 Condition table 'plant/material'

Specific fields Field catalog ------------------------------------------------------- Long key word Long key word<Z1> ---> Plant</> ABC indicator<Z1> ---> Material</> ABC classification Order reason Volume rebate group ....

Table 506 Condition table 'plant'

Specific fields Field catalog ------------------------------------------------------- Long key word Long key word<Z1> ---> Plant</> ABC indicator ABC classification Order reason Volume rebate group ....

4.3.3.2 Defining the access sequences-------------------------------------

You can then create the required access sequences using IMG function"Define access sequences":

Access sequence Z100 Internal sales commissions

No. Tab Name Condition Exclusive ------------------------------------------------------------ 1 502 sales organization/material X 2 503 sales organization

As a rule, the access criteria should become more general from top tobottom. In other words, tables which specify more characteristics shouldhave a smaller number than the tables which specify fewer characteristics.It is not necessary to define a condition for the access here (see section6).

The "Exclusive" indicator has to be set in order to ensure that no furtherrecord is selected after the system has found a suitable condition recordfor a condition type within an access sequence.Thus, if a condition record is found for the given combination of sales

28.07.2012 of 36


organization and material, this record is used, and the system does notsearch for a suitable condition record in the "sales organization"condition table. If you do not set the "Exclusive" indicator, the systemwill search for condition records in both condition tables and possibly addtogether the records found, which of course is not desired in this case.

After entering a name for the access sequence and selecting the conditiontable(s), save the access sequence.

The fields for the access you just defined look like this:

Access Z100 1 Internal sales commissions Table 502

Condition Doc.str. Doc.field Key word long Spec.val. Init. -------------------------------------------------------------------- VKORG KOMK VKORG sales organization MATNR KOMP MATNR material

Access Z100 2 internal sales commissions Tabelle 503

Condition Doc.str. Doc.field Key word long Spec.val. Init. -------------------------------------------------------------------- VKORG KOMK VKORG sales organization

The fields for the access are automatically assigned by the system. Youtherefore do not need to maintain these. Observe that the thecharacteristics "Sales organization" and "Material" selected in conditiontable 502 are used as key fields for the condition records there.

You can make entries in the fields "Specific value" and "Initial value" ifa field should always be filled with a predefined value during the access,or if a condition should also be accessed if the field is empty. Usually,you can leave these fields empty.

The rest of the access sequences required in the example look like this:

Access sequence Z200 Dispatch packaging --------------------------------------------------------------- No. Tab Name Condition Exklusive 1 505 Plant/Material X 2 506 Plant

Access sequence Z300 Outgoing freight --------------------------------------------------------------- No. Tab Name Condition Exklusive 1 506 Plant

4.3.3.3 Defining the condition types--------------------------------------

28.07.2012 of 36


The condition types 'REVN', 'DISC' and 'DISP' are copied from the billingdocument and form the basis for calculating the net revenue. Thus it is notnecessary to maintain condition records for these conditions. Instead, youneed to define them as base condition types as described in section 1.3.The condition types should look like this:

o Condition type REVN RevenueAccess sequence

Control data:Condition category K Base amount excl. taxCalculation type B Fixed amountCond.class B PricesScale basis

Change options/condition master record maintenance: (not required)

o Condition type DISC Customer discountAccess sequence


Change options: (not required)

Condition master record maintenance:+/- signs X (+/- sign is negative)

The discount (DISC) is to be subtracted from the revenue (REVN) andtherefore must be negative.

o Condition type DISP Price reductionAccess sequence




The price reduction (DISP) is to be subtracted from the revenue(REVN) and therefore must be negative.

Condition type 'COGS' (Transfer price) is the basis for determining

28.07.2012 of 36


the base used for commission. The transfer price is copiedautomatically from the billing document. You therefore do not haveto maintain condition records. Instead, define this condition typeas a base condition type as well.

o Condition type COGS Transfer priceAccess sequence




The transfer price (COGS) is to be subtracted from the net revenueand a therefore must be negative.

Condition types 'PROV', 'OUPA' and 'OUTF' should be used to calculatesurcharges/discounts based on either the above conditions or totals (netrevenue or the base for commission). You therefore need to define these assurcharge/discount conditions and enter an access sequence to be able tocreate the corresponding condition records.

o Condition type PROV CommissionAccess sequence Z100 Internal sales commission

Control data:Condition categoryCalculation type A In percentCond.class A Surcharge/discountScale basis


o Condition type OUPA Dispatch packagingAccess sequence Z200 Dispatch packaging

Control data:Condition categoryCalculation type C Quantity-dependentCond.class A Surcharge/discountScale basis


28.07.2012 of 36


o Condition type OUTF Outgoing freightAccess sequence Z300 Outgoing freight

Control data:Condition categoryCalculation type A In percentcond.class A Surcharge/discountScale basis


4.3.3.4 Maintaining the condition records-----------------------------------------

You can maintain condition records directly when you maintain the conditiontypes. The condition records you maintain are those for the conditiontables entered in the appropriate access sequence:

o Condition type 'PROV'

Condition records for the characteristics combination 'salesorganization/material' (condition table A502)

Validity period 12/09/1996

SalesOrg. Material Amount0001 CK-700 chocolate 10.000 %0001 CK-710 vanilla waffles 12.000 %....

Condition records for the 'sales organization' characteristic(condition table A503)


SalesOrg. Amount0001 Salesorgan. DE 2.000 %0002 Salesorgan. USA 4.000 %....

o Condition type 'OUPA'

Condition records for characteristics combination 'plant/material'(condition table A505)


Plant Material Amount Unit per UoM1000 CK-700 chocolate 4.00 USD 1 PAC1000 CK-701 chocolate beans 3,90 USD 1 PAC ....

Condition records for characteristic 'plant' (condition table A506)

28.07.2012 of 36



Plant. Amount Unit per UoM1000 Hamburg 1,50 USD 1 PAC....

o Condition type 'OUTF'

Condition records for characteristic 'plant' (condition table A506)


Plant Amount1000 Hamburg 2.000 %1100 Berlin 4.000 %1200 Dresden 8.000 %1300 Karlsruhe 5.000 %....

4.3.3.5 Defining the costing sheet----------------------------------

Once you have maintained the condition types and the correspondingcondition records, you can create the costing sheet using the IMG function"Maintain costing sheets". Here, you can copy the costing sheet shown insection 4.3.2.

Costing sheet 'ACT001'

Step Counter Cond, type Description From To ---------------------------------------------------------------- 10 0 REVN revenue 0 0 20 0 DISC customer discount 0 0 30 0 DISP price reduction 0 0 40 0 net revenue 10 30 50 0 COGS transfer price 0 0 60 0 basis for commission 40 50 110 0 PROV commission 60 0 300 0 OUPA dispatch packaging 0 0 310 0 OUTF outgoing freight 50 0

The step number determines the order in which the system reads andprocesses the conditions. The "Counter" column is only required if you wantto use several conditions in one step. With the "From" and "To" fields youdetermine which steps are used as the basis for calculating the value ofthe given step. If you enter a "From" value as well as a "To" value, thesystem adds the condition values of the two specified steps and thecondition values of all the steps in between. In this case, the resultingtotal is the basis for calculating the value of the step.

Since the conditions 'REVN', 'DISC' and 'DISP' are base conditions whichare supplied from the SD billing document (see also section 4.3.3.6), youdo not have to refer to another step in the costing sheet. The same appliesto the condition 'COGS'.In step 40, the net revenue is calculated as the sum of steps 10 to 30.

28.07.2012 of 36


Since condition types 'DISC' and 'DISP' are defined with a - sign, the netrevenue is calculated as follows:

REVN - DISC - DISP = net revenue

Step 50 contains the transfer price ('COGS') with a - sign. The line "Basisfor commission" is the total of steps 40 and 50:

Net revenue - COGS = basis for commission

The commission ('PROV') is now calculated based on step 60. If, forexample, a percentage of 10 % is found for sales organization '0001' andmaterial 'CK-700' (see section 4.3.3.4), the following value is calculatedin step 110:

PROV = basis for commission * 10/100

The dispatch packaging ('OUPA') is determined depending on the quantity.Since the basis for calculating the condition value is a quantity field andnot a condition, you do not need to refer to another step. You specifywhich quantity field should be used as the basis for calculatingquantity-dependent condition values when you assign the costing sheet tothe valuation strategy (see section 4.3.3.7).If we assume that only 2 PAC (packages) of material 'CK-700' are sold fromplant '1000', the condition record amounting to 4 USD/PAC is used. Thus thefollowing value is calculated:

OUPA = 2 PAC * 4 USD/PAC = 8 USD

The outgoing freight ('OUTF') is calculated based on the transfer price,which is negative (step 50). In plant '1000', for example, this would bethe value:

OUTF = ( - transfer price ) * 2/100

4.3.3.6 Assigning the conditions to value fields------------------------------------------------

In order for the system to be able to copy the values from the billingdocument to the base conditions and to copy the calculated conditions tothe value fields of the CO-PA line item, you need to assign your CO-PAcondition types to the corresponding CO-PA value fields. This assignmentmust be done in a way that the CO-PA conditions are assigned to the samevalue fields as the corresponding SD conditions (in the SD interface).In the IMG step "Assign value fields", you tell the system which valuefields of the operating concern are source fields for base conditions andwhich are target fields for the values calculated in the costing sheet.

The assignments necessary for our example are shown in section 4.3.2 andcan be copied from there without any changes.

28.07.2012 of 36


Condition (CO-PA) <--------> Value field ------------------------------------------------------------------ COGS Transfer price VV140 Transfer price DISC Customer discounts VV030 Customer discount DISP Price reduction VV050 Price reduction OUPA Dispatch packaging VV120 Dispatch packaging OUTF Outgoing freight VV110 Imputed out.freight PROV Commissions VV130 Sales commission REVN Revenue VV010 RevenueSection 4.4 shows the data flow for a concrete an example.

4.3.3.7 Entering the costing sheet in the valuation strategy------------------------------------------------------------

The entire valuation is controlled by a valuation strategy. Valuation usingconditions is not active until you enter the costing sheet in a valuationstrategy.

In this example, you have to add an entry for costing sheet ACT001 invaluation strategy 001. Assign the field VVIQT (invoiced quantity in salesunit) as the quantity field. This makes it possible to use the invoicedquantity as the basis for calculating the condition type 'OUPA' (Dispatchpackaging).

Sequence Appl. Cost.sheet Name Prod.cost Quantity field Exitno.

---------------------------------------------------------------------- 10 X VVIQT 20 ACT001 VVIQT

According to this valuation strategy, the system processes costing sheetACT001 after reading the product cost estimate.You must always assign a quantity field to a costing sheet if aquantity-dependent condition type is used in that sheet.

4.4 Data flow and valuation in the example

This section provides a concrete example of how the data from the SDbilling document is updated and valuated in Profitability Analysis.

The billing document reads as follows:

-----------------------------------------------------------------------Sales organization: 0001Distribution channel: 01Division 05-----------------------------------------------------------------------

Item 10 contains 1 PAC (= 10 IT) of material 'CK-701' with the followingcondition values:

-----------------------------------------------------------------------

28.07.2012 of 36


Ctyp Name Amount Curr. per UoM ConValPR00 Price 10.00 USD 1 IT 100.00 USD Gross 10.00 USD 1 ITK030 Cust./material group 5.000- % 5.00- USDBO03 Customer rebate 6.000- % 6.00- USD....VPRS Cost 4.00 USD 1 IT 40.00 USD-----------------------------------------------------------------------

In addition to the characteristics listed here, the following values aretransferred to the Profitability Analysis line item according to valuefield assignment in the SD interface:

The CO-PA line item before valuation:-------------------------------------

Characteristic Name Value -------------------------------------------------- VRGAR Record type F VKORG Sales organization 0001 VTWEG Distribution channel 01 SPART Division 05 ARTNR Product CK-701 KNDNR Customer 900687 WERKS Plant 1000 ....

Field Name Value Unit --------------------------------------------------------- VVIQT Inv. quant. in VME 1 PAC VVSQT Inv. quant. in LME 10 IT

VV010 Revenue 100.00 USD VV030 Customer discount 6.00 USD VV050 Price reduction 5.00 USD .... VV110 Cos.-bas. outg.freight 0.00 USD VV120 Dispatch packaging 0.00 USD VV130 Salesperson commission 0.00 USD VV140 Transfer price 40.00 USD

In line with the assignment of CO-PA value fields to CO-PA condition types,the individual conditions are supplied with the following values beforevaluation takes place:

Condition type Name Value field Value ------------------------------------------------------------------ REVN Revenue <--- VV010 100.00 DISC Customer discount <--- VV030 6.00 DISP Price reduction <--- VV050 5.00 COGS Transfer price <--- VV140 40.00 PROV Commission <--- VV130 0.00 OUPA Dispatch packaging <--- VV120 0.00 OUTF Outgoing freight <--- VV110 0.00

Quantity field VVIQT, which contains the value 1 PAC, is assigned tocosting sheet ACT001.

28.07.2012 of 36


The following calculations are then performed on the individual steps incosting sheet ACT001:

Step Counter Cond. type Name from Step to Step

--------------------------------------------------------------

10 0 REVN revenues 0 0

1. Condition type 'REVN' is a base condition. No condition records areread and no calculations are performed. 'REVN' contains the valueobtained from 'VV010', which amounts to 100.00 USD.

20 0 DISC customer discount 0 0

2. Condition type 'DISC' is a base condition. No condition records areread and no calculations are performed. 'DISC' contains the valueobtained from 'VV030', which is -6.00 USD. The value is negative,since the condition type was defined as negative (see section4.3.3.3).

30 0 DISP price reduction 0 0

3. Condition type 'DISP' is a base condition. No condition records areread and no calculations are performed. 'DISP' contains the valueobtained from 'VV050', which is -5.00 USD. The value is negative,since the condition type was defined as negative (see section4.3.3.3).

40 0 net revenue 10 30

4. The net revenue is the total of steps 10 to 30. Thus, the system addsthe values in steps 10 to 30:

+-----------------------------------+ Step Value 10 100.00 USD 20 6.00- USD 30 5.00- USD

Total 40 Net revenue 89.00 USD

+-----------------------------------+

50 0 COGS Transfer price 0 0

5. Condition type 'COGS' is a base condition. No condition records are

28.07.2012 of 36


read and no calculations are performed. 'COGS' contains the valueobtained from 'VV140', which is -40.00 USD. The value is negative,since the condition type was defined as negative (see section4.3.3.3).

60 0 basis for commis. 40 50

6. The basis for commissions is the total of steps 40 and 50. Thus, thesystem adds the values of steps 40 to 50:

+-----------------------------------+ Step Value 40 89.00 USD 50 40.00- USD

Totas 60 Basis comm. 49.00 USD

+-----------------------------------+

110 0 PROV commission 60 0

7. Condition type 'PROV' is a surcharge. The system reads the accesssequence Z100 to find condition records. The line item contains thevalue 0001 for characteristic 'Sales organization' and the valueCK-701 the material.According to access sequence Z100, the system first should search forcondition records in condition table A502. However, no entry for thecombination of sales organization 0001 and material CK-701 exists.Therefore the system searches for a valid condition record in thesecond condition table (A503) of the access sequence. There it finds apercentage of 2.000% for the sales organization 0001 and takes thisvalue (see section 4.3.3.4).Condition type 'PROV' refers to step 60, the line "Basis forcommission". Thus the system applies the value found in the conditionrecord to the basis for commission, yielding the following:

+----------------------------------------------------+ Basis for commission * Percentage = PROV 49.00 USD * 2/100 = 0.98 USD +----------------------------------------------------+

300 0 OUPA Dispatch packag. 0 0

8. Condition type 'OUPA' is a quantity-dependent surcharge. The systemuses access sequence Z200 to search for condition records. The lineitem contains plant 1000 and product CK-701.According to access sequence Z200, the system first searches forcondition records in condition table A505. There it finds 3.90 USD/PACfor plant 1000 and product CK-701 (see section 4.3.3.4). Although acondition record also exists for plant 1000 in the second condition

28.07.2012 of 36


table (A506) of the access sequence, the system does not search thattable, since the "Exclusive" indicator is activated in the accesssequence (see section 4.3.3.2).Condition type 'OUPA' has no reference step. Since the condition typewas defined depending on the quantity, the quantity field VVIQT ' isused as the basis:

+--------------------------------------------------------+ Inv. quant. in VME * Amount = OUPA 1 PAC * 3.90 USD/PAC 3.90 USD +--------------------------------------------------------+

310 0 OUTF Dispatch freight 50 0

9. Condition type 'OUTF' is a discount. The system searches for conditionrecords using access sequence Z300. The line item contains plant 1000.According to access sequence Z300, the system first searches forcondition records in condition table A506. There it finds a value of2% for plant 1000 (see section 4.3.3.4).Condition type 'OUTF' uses step 50 -- COGS, the transfer price -- asreference step. This means that the percentage found is applied to thecondition type COGS. This yields the following calculation:

+-----------------------------------------------------+ Transfer price * Percentage = OUTF 40.00- USD * 2/100 = 0.80- USD +-----------------------------------------------------+

Note that the system automatically uses the value '0' if no conditionrecord is found by the access sequence. You do not receive an errormessage. Consequently, in the example the transfer price would bemultiplied with 0%, which would yield a value of 0.00 USD for 'OUTF'.

Once all calculations have been carried out, the costing sheet contains thefollowing values:

Step Counter Condition type Name Value

----------------------------------------------------------------

10 0 REVN revenues 100.00 USD

20 0 DISC customer discount 6.00- USD

30 0 DISP price reduction 5.00- USD

40 0 net revenue 89.00 USD

50 0 COGS transfer price 40.00- USD

60 0 basis for commission 49.00 USD

110 0 PROV commissions 0.98 USD

28.07.2012 of 36


300 0 OUPA dispatch packaging 3.90 USD

310 0 OUTF outgoing freight 0.80- USD

Now the condition values calculated are written to the line item accordingto how the conditions are assigned to value fields (see section 4.3.3.6).Note that base conditions (in this example, these are condition types'REVN', 'DISC', 'DISP' and 'COGS') are not written to the line item. Forthese condition types, the value field assignment merely defines whatfields their values come from.

The CO-PA line item after valuation:------------------------------------

Characteristic Name Value -------------------------------------------------- VRGAR Record type F VKORG Sales organization 0001 VTWEG Distribution channel 01 SPART Division 05 ARTNR Product CK-701 KNDNR Customer 900687 WERKS Plant 1000 ....

Field Name Value Unit --------------------------------------------------------- VVIQT Inv. quant. in VME 1 PAC VVSQT inv. quant. in LME 10 PI

VV010 Revenue 100.00 USD VV030 Customer rebate 6.00 USD VV050 Price reduction 5.00 USD .... VV110 Imputed outg. freight 0.80- USD VV120 Dispatch packaging 3.90 USD VV130 Sales commission 0.98 USD VV140 Transfer price 40.00 USD

Finally, the line item is posted in Profitability Analysis.

5. How to work with the condition tool: a recommendation

The example described in section 4 yields the following recommendation forhow to go about carrying out the Customizing activities required to set upvaluation using conditions in Profitability Analysis.

28.07.2012 of 36


+------------------------------------------------------------------+

I. Define condition tables

II. Define access sequences III. Define condition types

IV. Maintain condition records

V. Define costing sheet by entering the necessary condition types in the desired order

VI. Assign the conditions to value fields

VII. Enter the costing sheet into the valuation strategy

+------------------------------------------------------------------+

This order is only a recommendation, which should provide orientation forless experienced users. Since IMG activities are not strictly hierarchical,it is ultimately up to the user to develop his or her own method forworking with the condition tool.

6. Further functions and special features

This section explains some functions and special features that areavailable in Customizing but were not required in the example.

6.1 Deleting condition records

Condition records that are no longer valid can be deleted. After itsdeletion, the condition record becomes inactive and in no longer valuated.However, the condition record remains in the system until the nextreorganization is carried out.

o How to delete a condition record:

To delete a condition record, use the IMG function "Createcondition types" to access the condition type detail screen. Fromthere, choose "Condition records". The system displays all thecondition records for the condition type. Use the function "Edit ->Delete" to delete the individual records. An "L" appears on thescreen to indicate that the condition records are now inactive andwill no longer be used. If you have inadvertently deleted acondition record, choose "Edit -> Undo delete" to reactivate itagain. Of course, reactivation is only possible until the nextreorganization is carried out in your system.

o How to reorganize condition records:

Once you have deactivated condition records, you can remove themfrom the system by carrying out a reorganization. This is doneusing the archive object "SD_COND", which is provided in archive

28.07.2012 of 36


administration (transaction 'SARA'). To reorganize the conditionrecords for Profitability Analysis, you only have to select thecondition records with usage "A" and application "KE" when youcreate the archive file. For more detailed information onarchiving, see the online documentation for transaction 'SARA'.

6.2 Conditions for access sequences

A "condition" here determines under what conditions the system will NOTaccess a certain condition type.

You define these conditions with transaction VOFM under "Conditions ->Pricing". Enter application "KE" for Profitability Analysis. Then you canmaintain the source code.

Example:Routine 602, which specifies that the system should not access acondition table for sales organization 1000 only, could look likethis:

form kobev_602. sy-subrc = 4. check komk-vkorg ne '1000'. sy-subrc = 0.endform.

Thus, if the field VKORG has the value "1000", the Sy-Subrc is notequal to zero, and the condition is therefore not accessed. For allother values, Sy-Subrc is zero and the access is carried out.

6.3 Records for access

The "Records for access" function is available on the detail screen forcondition types. It lists all condition records for an access sequence.

Example:The "records for access" are listed for the condition type 'PROV'of the example in chapter 4:

Table 502 ------------------------ SaOrg Material Valid from Valid to ---------------------------------------------- 0001 CK-700 01/01/1996 12/31/9999 0001 CK-710 01/01/1996 12/31/9999 ....

28.07.2012 of 36


Table 503 ------------------------ SaOrg Valid from Valid to ---------------------------- 0001 01/01/1996 12/31/9999 0002 01/01/1996 12/31/9999 1000 08/01/1996 12/31/9999 ....

If you look at the details for the record with 'VkOrg = 0001' fromcondition table '503', you obtain additional information:

Sal.org. Name 0001 Sales org. DE ------------------------------- Validity period 01/01/1996 to 12/31/9999 -------------------------------------------------- Condition type Amount UoM L PROV Commissions 2.000 %

6.4 Condition analysis

When you enter data manually in Profitability Analysis -- in planning orfor actual postings -- you can use the "Condition analysis" function.There you receive a list of all the conditions valid in valuation as wellas a short overview of how the condition values are found.

In particular, you obtain information on

o whether a valid condition record was found

o whether an access was performed

o whether a condition record was ignored because a precondition wasnot met

Example:

In the following example, the same data is used as in section 4, but thecharacteristics and values from the billing document were entered manuallyin transaction KE21 (line item entry).If you call up the "Condition analysis" function from the "ValueFields"screen, you obtain the following:

Item 1 net value in USD Menge 1 PAC Material CK-701

28.07.2012 of 36


Ctype Name Amount Curr. per UoM Con.value (USD) ------------------------------------------------------------------- REVN Revenues 100.00 DISC Customer discounts 6.00- DISP Price reduction 5.00- Net revenue 89.00 USD 1 PAC 89.00 COGS Transfer price 40.00- Basis for commis. 49.00 USD 1 PAC 49.00 PROV Commissions 2.000 % 0.98 OUPA Outgoing packaging 3.90 USD 1 PAC 3.90 OUTF Outgoing freight 2.000 % 0.80-

The "Analysis" function gives you more detailed information:

Condition type Note -------------------------------------------------------------------- REVN Revenues 207 ) DISC Cust. discounts 207 Condition was found (w/o cond.record) DISP Price reduction 207 Condition was found (w/o cond.record) Net revenue 200 Subtotal COGS Transfer price 207 Condition was found (w/o cond.record) Basis for commissions 200 Subtotal PROV Commissions 208 Condition record was found OUPA Outgoing packaging 208 Condition record was found OUTF Outgoing freight 208 Condition record was found

Now you can call up details of an individual condition, say 'PROV':

No. Note ------------------------------------------------------------- 01 109 Condition record is missing 02 208 Condition record was found

On the left hand side, you see the access number. In our example, acondition record was found in the second condition table only. If you nowchoose the "Details" function for number 02, you obtain the characteristicsor fields that were used to search for condition records in the conditiontable:

Condition field Document field Value -------------------------------------------------------------- A503-VKORG KOMK-VKORG 0001 KOMK-PRSDT 12/10/1996

The complete key is usedThus, using the condition analysis, you can see in detail how the systemfound the condition records.

6.5 Condition lists

If you want to obtain an overview of the condition records available in thesystem, you can create condition lists.Condition lists list information from condition records according tovarious criteria.

For example, a condition list can help you answer the following questions:

28.07.2012 of 36


o Which condition records are available for certain customer groupsand product ranges in a certain country or geographical region?

o Which condition records for freights exist in the system?

6.6 Using valuation to supply value fields

6.6.1 More than one costing sheet

You can use more than one costing sheet in the same valuation strategy.When you transfer the condition values to value fields, note that severalcondition types can be added together in one value field if they are allassigned to the same value field. This is also true if the condition typescome from different costing sheets.

6.6.2 More than one valuation method

A valuation step fills a value field only if it that value field is empty.Consequently, values from the billing document cannot be overwritten usingvaluation. Likewise, values from product costing cannot be overwritten bycondition values from a costing sheet and vice versa.The general principle is that values from sender documents or manuallyentered values are not overwritten by valuation unless they contain thevalue "0". The exception to this is in planning, where the valuated valueshave always priority over those entered manually.Different valuation methods -- that is, product costing or conditions -- donot overwrite value fields that are already filled (value <> 0), nor dothey add values to value fields that are already filled. An addition ofvalues is only possible within two steps that use the same method -- suchas two costing sheets.

6.7 Plan valuation using pricing procedures from SD

In planning, you can also use pricing procedures from the Sales andDistribution (SD) application component in Profitability Analysis. Thesehave the same technical structure and work the same way as the costingsheets in Profitability Analysis. To use a pricing procedure, enterapplication class "V" in the valuation strategy. This makes it possible,for example, to use material prices (SD condition type 'PR00') to valuateyour plan data in CO-PA.This is not required for actual data, since there the condition values aredirectly copied from the billing document according to the value fieldassignment of the SD interface.

6.7.1 Which SD condition types can you use?

Not all SD condition types can be used, since the access sequences used inSD might use condition tables that contain access fields which are notcharacteristics in Profitability Analysis. You should therefore checkwhether the fields required by the condition types are also characteristicsin your operating concern before using an SD pricing procedure! If not, thesystem will not find the condition records, even if these are defined inSD.

6.7.2 Value field assignment

28.07.2012 of 36


SD conditions are transferred to CO-PA value fields according to the valuefield assignment for actual data for the SD interface.

6.8 Creating conditions with reference to other conditions

When you create a condition with reference to another condition, conditionrecords need not be maintained twice since the system then reads thecondition records of the referenced condition and returns the results. Thecondition and the reference need to have an identical definition. For theaccess to condition records to be successful for conditions with accesssequence, the following two cases have to be distinguished:

6.8.1 The referenced condition is a CO-PA condition

In this case, enter the access sequence of the referenced condition asaccess sequence for the new condition.

6.8.2 The referenced condition is an SD condition, for example

In this case, you cannot use the access sequence of the SD condition sincethis is not allowed by the customizing. The reason is that the accesssequence depends on the application. To allow this nevertheless, define anew CO-PA access sequence that has the same definition as the correspondingaccess sequence of the SD condition, and use this access sequence for thenew condition.

Header Data

Release Status: Released for CustomerReleased on: 21.03.2002 13:37:03Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: CO-PA Profitability Analysis

The Note is release-independent

Related Notes

28.07.2012 of 36


Number Short Text

420992 Information: Changing CO-PA conditions / deleting records

420227 Valuation: Condition type with field 'LAND1' not supplied

354842 CO-PA valuation:problem for valuation w/ quantity 0

354617 CO-PA valuation on basis of NTGEW, BRGEW, VOLUM

330791 Performance of valuation with conditions

323346 Valuation with conditions: Value not transferred

168631 CO-PA: No valuation with price list type

140056 No valuation with gross/net weight/volume II

137067 No valuation with gross/net weight/volume I

121675 CO-PA valuation: copying condition records

111232 INFO: Valuation for materials valuated separately

107284 Performance improvemnt measures in condition access

84154 SD/CO PA: cash discnt from cust.master

74486 INFO: Overview of consulting notes for CO-PA

73477 Planned valuat.: Pricing conditions are accumulated

70981 SD/CO-PA: Planned valuation with SD conditions

68251 Partner no field for condition table

62523 CO-PA: Planned valuation with product hierarchy

52849 INFO: Transfer of conditions with +/- signs

44766 Weight/volume-dependent condition records

43882 Condition values of a costing sheet are not added

sapnote_0000062536(1)

Documents