62536 - Info Conditions in Profitability Analysis

8/11/2019 62536 - Info Conditions in Profitability Analysis

http://slidepdf.com/reader/full/62536-info-conditions-in-profitability-analysis 1/19

SAP Note

Header Data

Symptom

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

This note is intended to give you an idea of how to use this tool. First the used technical termsand the interaction of the individual components of the condition tool are described. Then anexample is used to illustrate how the condition tool lets you meet your business requirements inProfitability Analysis.

The note applies to all users (end users, consultants, and so on) who want to familiarize themselves

with the conditions technique in Profitability Analysis and who would like to obtain information inaddition to that in the online documentation.

This note does not claim to be complete. A complete explanation could hardly be achieved by just onenote due to the great flexibility of the condition tool. However, this note aims at explaining indetail those functions of the condition tool that are most frequently required in ProfitabilityAnalysis.

The note applies to all releases where it describes the conceptual procedure for working with thecondition tool. The actual examples refer to the 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, access sequence, 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 in Profitability Analysis. It can beused for updating both actual and plan data.

The following methods of valuation are available:

l Valuation using conditions and costing sheets

Using the condition technique, you can attribute values needed for for analysis purposes inProfitability Analysis, even if these values are not known at the time of the actual posting.For example, you can determine sales commissions, discounts, or shipping costs not yet known atthe time of billing, and use this information to analyze your sales transaction.For information on using SD costing sheets in CO-PA planning, see to section 6.7.

l Valuation using product costing

Valuation using product costing lets you find the cost of goods manufactured for the productsold when you post a sales transaction to Profitability Analysis. For example, you can find thevariable and fixed cost components for the product sold and compare these to the revenues andsales deductions copied from the billing document for the sales transaction.

l Valuation using customer-defined valuation routines

Customer-defined valuation routines let you calculate imputed values that cannot be determinedusing the two preceding methods. You can program your own valuation logic.You can find more detailed information on this topic where you define your CO-PA valuationstrategy (transaction KE4U, screen "Valuation Strategy: Details") in the F1 help for the "Exit

62536 - Info: Conditions in Profitability Analysis

Version 18 Validity: 21.03.2002 - active Language English

Released On 21.03.2002 13:37:03

Release Status Released for Customer

Component CO-PA Profitability Analysis

Priority Recommendations / Additional InfoCategory Consulting



no." field. See also the documentation on SAP enhancement COPA0002. In Release 3.0, you canaccess 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 the individual value fields,and in which order these methods are to be applied.

For example, a typical valuation strategy might have the following structure:

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

With this valuation strategy, the system first reads a product cost estimate for the product or

material type specified in the document being valuated. Then it uses a costing sheet to calculateadditional values. Finally, it reads the customer-defined valuation routines.

This note deals primarily with valuation using costing sheets. The following chapters describe thisapproach in detail.

1. Terminology of the condition technique

Before you use the condition tool, it is important to understand some technical terms used inCustomizing for Profitability Analysis. This chapter is intended to explain these terms. First theterms are explained from 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 imputed costs, in what order theseconditions are used, and what dependency relationships exist between the individual conditions. Forexample, you can say that sales commission should be calculated on the basis of the sales revenues.In sum, the tasks of the costing sheet are to:

l specify the basis for calculating additional values

l define subtotals

l define any dependency relationships between conditions (by grouping condition types) anddetermining the order in which they are calculated 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-dependentsurcharges) or defines fixed prices (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 that apply when you calculatea value. For example, a surcharge might depend on variable values such as the current value of theCO-PA characteristics "Customer" and "Product" or the value in the value field "Sales volume".Information on the surcharge calculated on the basis of these variable values is be stored by thesystem in the form of so-called "condition records".

The definition of a condition type consists of the following:o condition category o calculation type o condition class o scale basis

Furthermore, special control flags can be set for each condition type to control whether or not

certain parameters can be changed (i.e. during a condition analysis) or whether the condition masterrecord 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 which condition tables thesystem has to read to find valid condition records for the valuation. Condition records are storedin different condition tables, which are defined with different combinations of characteristics.Thus by assigning an access sequence to the condition type, you determine which characteristic orcharacteristics the condition records (percentages or fixed amounts) for this condition type forthis condition type are dependent 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 definition of a condition type.

1.2.1 Condition category: -------------------------The condition category classifies conditions according to predefined categories, such as "Baseamount" or "Price".

The following condition categories can be used in Profitability Analysis:

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 these categories. This includes surcharges and deductions to be calculated in the costing sheet.



1.2.2 Calculation type:

-----------------------The calculation type determines how the system is to calculate prices or surcharges/discounts for acondition. For example, the system can calculate a discount depending on a quantity or on a valuescale.

The following calculation types can be used in Profitability Analysis:

A Percentage B Fixed amount C Quantity-dependentD Gross-weight-dependentE Net-weight-dependentF Volume-dependent

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

The following condition classes can be used in Profitability Analysis:

A Discount or surcharge B Price

1.2.4 Scale basis: ------------------The scale basis defines how the system is to interpret the scale of a condition. The scale may be aquantity 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 a condition type the user can changeduring condition analysis.You can allow or forbid changes to the amount or percentage, the value, the calculation type, or thequantity conversion of a condition type. In addition, you can make it possible or impossible todelete 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 you maintain condition master records.For example, you could specify that 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 is not of the condition category K,G, S, T or E. This means that you must assign an access sequence to condition types for calculatedvalues as well as fixed amounts of the category " ". The access sequence allows you to maintaincondition records for the condition type.

In the access sequence, you determine:

¡ which condition tables the system reads to access condition records

¡ 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, which informs the system whichcondition tables to search in for valid data for a given condition.The structure of a condition table defines a kind of key for the condition records. This keycontains the characteristic values that exactly identify the individual condition record. Thecondition record contains the values that are to be applied to a document when the characteristicvalues in the given document match those in the key for that condition record. A condition recordcan contain, for example, a fixed price for a certain product or a percentage to be added ordeducted for a certain customer. The order of the condition tables in the access sequence determineswhich individual condition record or records should be applied in which order.

l Example:

You want to define a percentage surcharge that depends on the characteristic "Product group". Atthe same time, you also want to define a special percentage surcharge for certain individualproducts. If no surcharge is defined for a specific product, the system should apply thesurcharge for the appropriate product group. In other words, the surcharge for individualproducts should have a higher priority than the surcharge for product groups.To achieve this, you first need to create two condition tables: one for the characteristic"Product group" and another for the characteristic "Product". Then you create access sequence'ZZ01', which accesses the these condition tables: first the table "Product" (since you wantthis table to take priority) and then the table "Product group". Once you have assigned thisaccess sequence to a condition type, you can then maintain the corresponding condition 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 to define a number ofdifferent kinds of condition types. This section is intended to give you an overview of all thepossible combinations of settings 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 possibilities for defining conditiontypes and demonstrate how these possibilities affect the maintenance of condition records. Oneexample illustrates, for instance, how to define a percentage discount.

Open questions such as "How do I calculate a discount on the basis of revenue?" 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 - yes db) with value scale - A A B yes dc) with quantity scale - A A C yes

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

f) Define fixed amountfa) not scaled - B B yes fb) with value scale - B B B yes fc) with quantity scale - B B C yes

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

The following contains examples for the condition types listed above. Where an access sequence isallowed, assume that it accesses a condition table that uses the characteristic "Material group".

l Example for (a) :A base condition for revenues transferred from Sales and Distribution (SD). This condition typecan then be used in a costing sheet to calculate surcharges or deductions depending on therevenue.

l Example for (b) :The appropriate price is read from the material master. For example, suppose that the standardprice for material "M099312" is 100.00 USD apiece. If you have sold 5 units of this material,the 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 always taken 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'.

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

l Example for (da) :For material groups '312', '313' and '314', you can maintain the following condition records:Material group Amount Unit of measure 312 1 % (percentage sign is inserted 313 2 % automatically by the system!) 314 1.5 % ....These condition records can be used, for example, to calculate the expected outgoing freight.

l 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 the revenue generated.

l Example for (dc) :For material group '312', you can define the following quantity scale:

From quantity Unit of measure Amount Unit 1000



PI 1 % 5000 PI 2 %

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

l Example for (ea) :For material group '312', you can define the following condition record:

Material group Amount Unit per Unit of measure 312 1USD 1 IT Thus you can assess 1 USD per item for packaging material.

l 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

l Example for (ec) :For material group '312', you can define the following quantity scale:

From quantity Unit of meas. Amount Unit per Unit of measure 1,000PI 0.01 USD 1 IT

10,000 PI 0.03 USD 1 IT

l Example for (fa) :For material group '312', you can define the following condition record:

Material group Amount Unit 312 100 USD

l Example for (fb) :

For material group '312', you can define the following value scale:From value Scale currency Amount Unit 1000 USD 20USD

5000 USD 30 USD

l Example for (fc) :For material group '312', you can define the following quantity scale:

From quantity Unit of measure Amount Unit 1,000 IT50 USD

10,000 IT 70 USD

2. Relationship between the individual components of the condition tool

The relationship between these components can be shown in a simplified manner as follows:

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 orderin which the conditions are processed. You can assign one access sequence to a condition type. Theaccess sequence in turn can access one or more condition tables, while a condition table can be usedby one or more access sequences. Finally, you can define any number of condition records for eachcondition table.

3. Conditions in the data flow of Profitability Analysis

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

3.1 Actual postings

When actual postings are transferred to CO-PA, the system always first copies the data from thesender document (sales order or billing document). For example, characteristics such as the salesorganization or the product are copied from the sender document to the CO-PA line item, andquantities and values are entered into the quantity and value fields of the CO-PA line itemaccording to how you defined the corresponding interface (SD interface) in Customizing forProfitability Analysis.Next, the system performs derivation to add further characteristics that are only relevant inProfitability Analysis. Then the appropriate valuation strategy is read and the valuation methodsspecified there (valuation using product costing, costing sheets and/or user exits) are processed inthe order specified. Finally, the new line item is posted.

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

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 actual postings. First, dataentered in the planning layout during a planning session is copied to the plan line items.Derivation is also performed automatically for the characteristics specified, and the quantities andvalues are updated. However, unlike with actual data, valuation in planning is not performed

automatically. You need to execute it explicitly. If you do so, the system reads the correspondingvaluation strategy and processes the 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 known quantities and valuesare available in the line item for use in valuation. Valuation lets you then add further values tothis line item. To find out which characteristics and values are available for reference duringvaluation -- this can be all the characteristics of an operating concern -- for actual postings, youhave to analyze the field assignments made in Customizing for the corresponding interface. Inplanning, you need to analyze the fields of the planning layout.

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

While the preceding sections primarily explained the technical aspects of the "condition" technique,this section will attempt to illustrate how you can use conditions to help meet your business andmanagement requirements in 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 contains the following fields:

Field Description -------------------------- * Quantity fieldsVVIQT 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 ....

* CharacteristicsVKORG 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

* 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 valuation using product costing(transaction KE4U):

Sequence Appl. Cost.sheet Name Prod.cost Quantity field Exit no. ----------------------------------------------------------------------

10 X VVIQT </>

The valuation strategy is assigned to record type "F" for actual billing documents (transactionKE44) :

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

01 F 001 Actual valuation</>

4.2 What should valuation using conditions do?

The transfer price is to be subtracted from the net revenue, which is revenue minus the customerdiscount and price reduction. The amount thus determined represents the basis for calculating thesales commission.Commission should be a percentage rate that can differ for the different sales organizations.Furthermore, you also need to determine the commission separately for certain materials withinindividual sales organizations.It should be possible to calculate outgoing freight separately for each plant as a percentage of thetransfer price.Based on the quantity sold, you also want to calculate imputed costs for dispatch packagingseparately for each plant. In certain cases the dispatch packaging should also depend on thematerial sold.

4.3 Concept for valuation with conditions that meets the aboverequirements

4.3.1 Analysis of the requirements

First of all, the requirements listed in section 4.2 mean that you need to determine threeconditions:

* commission * outgoing freight

* dispatch packaging The commission should be based on the difference between the net revenue and the transfer price. Thenet revenue results from the gross revenue minus the customer discount and price reduction. Theoutgoing freight and the 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 like this:

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, price reduction and transferprice are transferred from Sales and Distribution (SD) to Profitability Analysis. In ProfitabilityAnalysis, 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 to define 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 working with conditions. Itdetermines how individual conditions are calculated and how they relate to one another.

It is therefore necessary to define a costing sheet in which the individual calculation lines arerepresented by condition types.

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

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 on the characteristics"Sales organization" and "Material". To be able to maintain condition records for condition PROVdepending on the mentioned characteristics, you need to define an access sequence Z100. Since thecondition records must be determined depending on two different possible combinations - salesorganization only and sales organization/material - you must define two condition tables: A502 (withthe characteristics 'sales organization' 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 or the combination of plantand material, and should be dependent on the quantity of the good sold. Again, you need twocondition tables here: A505 (with the characteristics 'plant/material') and A506 (with thecharacteristic 'plant'). These tables are accessed by access sequence Z200.


OUPA Z200 A505 A506

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


OUTF Z300 A506

Conditions REVN, DISC, DISP and COGS are so-called base conditions, which provide the basis forcalculating the other conditions. They do not require an access sequence. The condition valuestransferred from the SD billing document are the source for these conditions.

Consequently, these conditions have to point to the corresponding value fields in the CO-PA lineitem. Your conditions should therefore be assigned as follows:

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 fields as the SD conditions forrevenue, customer discount, price reduction and transfer price (see section 4.1.2). When you post abilling document, the SD condition values are copied to these CO-PA value fields. And since the CO-PA conditions refer to the same value fields, the SD condition values are then available for use inthe CO-PA costing sheet. Thus, there is a direct link between the SD conditions from the billingdocument and the conditions 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 the quantity, defined as theinvoiced quantity in sales units. In our example, this is the quantity field 'VVIQT' (see section4.1.2).

4.3.3 Realization of the concept using the condition tool

In Customizing for Profitability Analysis, special functions are provided for maintaining theindividual elements of the condition tool. Looking at the relationships illustrated in section 2between costing sheets, condition types, access sequences and condition tables, it is recommendedthat you proceed "top-down" when realizing your requirements. This means that you first have tocreate the condition tables, since these are a precondition for defining access sequences. Afterdefinitng the access sequences, 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 following tables:

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....

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 Orderreason

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 to bottom. In other words, tableswhich specify more characteristics should have a smaller number than the tables which specify fewercharacteristics.It is not necessary to define a condition for the access here (see section 6).

The "Exclusive" indicator has to be set in order to ensure that no further record is selected afterthe system has found a suitable condition record for a condition type within an access sequence.Thus, if a condition record is found for the given combination of sales organization and material,this record is used, and the system does not search for a suitable condition record in the "salesorganization" condition table. If you do not set the "Exclusive" indicator, the system will searchfor condition records in both condition tables and possibly add together the records found, which ofcourse is not desired in this case.

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

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. You therefore do not need tomaintain these. Observe that the the characteristics "Sales organization" and "Material" selected incondition table 502 are used as key fields for the condition records there.

You can make entries in the fields "Specific value" and "Initial value" if a field should always befilled with a predefined value during the access, or if a condition should also be accessed if thefield 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



l Condition type OUPA Dispatch packaging Access sequence Z200 Dispatch packaging

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

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

l Condition type OUTF Outgoing freight Access sequence Z300 Outgoing freight

Control data:

Condition categoryCalculation type A In percent cond.class A Surcharge/discount Scale basis

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

4.3.3.4 Maintaining the condition records -----------------------------------------You can maintain condition records directly when you maintain the condition types. The conditionrecords you maintain are those for the condition tables entered in the appropriate access sequence:

l Condition type 'PROV'

Condition records for the characteristics combination 'sales organization/material' (conditiontable A502)Validity period 12/09/1996 SalesOrg. Material Amount 0001 CK-700 chocolate 10.000 % 0001 CK-710 vanilla waffles 12.000 % ....

Condition records for the 'sales organization' characteristic (condition table A503)Validity period 12/09/1996 SalesOrg. Amount 0001 Salesorgan. DE 2.000 % 0002 Salesorgan. USA 4.000 % ....

l Condition type 'OUPA'

Condition records for characteristics combination 'plant/material' (condition table A505)Validity period 12/09/1996 Plant Material Amount Unit per UoM 1000 CK-700 chocolate 4.00 USD 1 PAC 1000 CK-701 chocolate beans 3,90 USD 1 PAC

....

Condition records for characteristic 'plant' (condition table A506)Validity period 12/09/1996 Plant. Amount Unit per UoM 1000 Hamburg 1,50 USD 1 PAC ....

l Condition type 'OUTF'

Condition records for characteristic 'plant' (condition table A506)Validity period 12/09/1996 Plant Amount 1000 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 corresponding condition records, you can createthe costing sheet using the IMG function "Maintain costing sheets". Here, you can copy the costingsheet shown in section 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 and processes the conditions. The"Counter" column is only required if you want to use several conditions in one step. With the "From"and "To" fields you determine which steps are used as the basis for calculating the value of thegiven step. If you enter a "From" value as well as a "To" value, the system adds the conditionvalues of the two specified steps and the condition values of all the steps in between. In this



case, the resulting total is the basis for calculating the value of the step.

Since the conditions 'REVN', 'DISC' and 'DISP' are base conditions which are supplied from the SDbilling document (see also section 4.3.3.6), you do not have to refer to another step in the costingsheet. The same applies to the condition 'COGS'.In step 40, the net revenue is calculated as the sum of steps 10 to 30. Since condition types 'DISC'and 'DISP' are defined with a - sign, the net revenue is calculated as follows:

REVN - DISC - DISP = net revenue

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

Net revenue - COGS = basis for commission

The commission ('PROV') is now calculated based on step 60. If, for example, a percentage of 10 % isfound for sales organization '0001' and material 'CK-700' (see section 4.3.3.4), the following valueis calculated in step 110:

PROV = basis for commission * 10/100

The dispatch packaging ('OUPA') is determined depending on the quantity. Since the basis forcalculating the condition value is a quantity field and not a condition, you do not need to refer toanother step. You specify which quantity field should be used as the basis for calculating quantity-dependent condition values when you assign the costing sheet to the valuation strategy (see section4.3.3.7).If we assume that only 2 PAC (packages) of material 'CK-700' are sold from plant '1000', thecondition record amounting to 4 USD/PAC is used. Thus the following 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 (step50). In plant '1000', for example, this would be the 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 billing document to the baseconditions and to copy the calculated conditions to the value fields of the CO-PA line item, youneed to assign your CO-PA condition types to the corresponding CO-PA value fields. This assignmentmust be done in a way that the CO-PA conditions are assigned to the same value fields as thecorresponding SD conditions (in the SD interface).

In the IMG step "Assign value fields", you tell the system which value fields of the operatingconcern are source fields for base conditions and which are target fields for the values calculatedin the costing sheet.

The assignments necessary for our example are shown in section 4.3.2 and can be copied from therewithout any changes.

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 concretean example.

4.3.3.7 Entering the costing sheet in the valuation strategy ------------------------------------------------------------The entire valuation is controlled by a valuation strategy. Valuation using conditions is not activeuntil you enter the costing sheet in a valuation strategy.

In this example, you have to add an entry for costing sheet ACT001 in valuation strategy 001. Assignthe field VVIQT (invoiced quantity in sales unit) as the quantity field. This makes it possible touse the invoiced quantity as the basis for calculating the condition type 'OUPA' (Dispatchpackaging).

Sequence Appl. Cost.sheet Name Prod.cost Quantity field Exit no. ---------------------------------------------------------------------- 10 X VVIQT

20 ACT001 VVIQT

According to this valuation strategy, the system processes costing sheet ACT001 after reading theproduct cost estimate.You must always assign a quantity field to a costing sheet if a quantity-dependent condition type isused in that sheet.

4.4 Data flow and valuation in the example

This section provides a concrete example of how the data from the SD billing document is updated andvaluated in Profitability Analysis.

The billing document reads as follows:



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

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

-----------------------------------------------------------------------Ctyp Name Amount Curr. per UoM ConVal PR00 Price10.00 USD 1 IT 100.00 USD

Gross 10.00 USD 1 IT K030 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 are transferred to theProfitability Analysis line item according to value field 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-701KNDNR 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 individualconditions are supplied with the following values before valuation 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 to costing sheet ACT001.

The following calculations are then performed on the individual steps in costing 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 are read and no calculationsare performed. 'REVN' contains the value obtained from 'VV010', which amounts to 100.00 USD.

20 0 DISC customer discount 0 0

1. Condition type 'DISC' is a base condition. No condition records are read and no calculationsare performed. 'DISC' contains the value obtained from 'VV030', which is -6.00 USD. The value isnegative, since the condition type was defined as negative (see section 4.3.3.3).

30 0 DISP price reduction 0 0

1. Condition type 'DISP' is a base condition. No condition records are read and no calculationsare performed. 'DISP' contains the value obtained from 'VV050', which is -5.00 USD. The value isnegative, since the condition type was defined as negative (see section 4.3.3.3).

40 0 net revenue 10 30 1. The net revenue is the total of steps 10 to 30. Thus, the system adds the values in steps 10to 30:

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

Total 40 Net revenue 89.00 USD



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

50 0 COGS Transfer price 0 0

1. Condition type 'COGS' is a base condition. No condition records are read and no calculationsare performed. 'COGS' contains the value obtained from 'VV140', which is -40.00 USD. The valueis negative, since the condition type was defined as negative (see section 4.3.3.3).

60 0 basis for commis. 40 50

1. The basis for commissions is the total of steps 40 and 50. Thus, the system adds the valuesof 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

1. Condition type 'PROV' is a surcharge. The system reads the access sequence Z100 to findcondition records. The line item contains the value 0001 for characteristic 'Sales organization'and the value CK-701 the material.According to access sequence Z100, the system first should search for condition records incondition table A502. However, no entry for the combination of sales organization 0001 andmaterial CK-701 exists. Therefore the system searches for a valid condition record in the secondcondition table (A503) of the access sequence. There it finds a percentage of 2.000% for thesales organization 0001 and takes this value (see section 4.3.3.4).Condition type 'PROV' refers to step 60, the line "Basis for commission". Thus the systemapplies the value found in the condition record to the basis for commission, yielding thefollowing:

+----------------------------------------------------+ Basis for commission* Percentage = PROV

49.00 USD * 2/100 = 0.98 USD +----------------------------------------------------+

300 0 OUPA Dispatch packag. 0 0

1. Condition type 'OUPA' is a quantity-dependent surcharge. The system uses access sequence Z200to search for condition records. The line item contains plant 1000 and product CK-701.According to access sequence Z200, the system first searches for condition records in conditiontable A505. There it finds 3.90 USD/PAC for plant 1000 and product CK-701 (see section 4.3.3.4).Although a condition record also exists for plant 1000 in the second condition table (A506) of

the access sequence, the system does not search that table, since the "Exclusive" indicator isactivated in the access sequence (see section 4.3.3.2).Condition type 'OUPA' has no reference step. Since the condition type was defined depending onthe quantity, the quantity field VVIQT ' is used as the basis:

+--------------------------------------------------------+ Inv. quant. inVME * Amount = OUPA

1 PAC * 3.90 USD/PAC 3.90 USD +--------------------------------------------------------+

310 0 OUTF Dispatch freight 50 0

1. Condition type 'OUTF' is a discount. The system searches for condition records using accesssequence Z300. The line item contains plant 1000.According to access sequence Z300, the system first searches for condition records in conditiontable A506. There it finds a value of 2% for plant 1000 (see section 4.3.3.4).

Condition type 'OUTF' uses step 50 -- COGS, the transfer price -- as reference step. This meansthat the percentage found is applied to the condition type COGS. This yields the followingcalculation:

+-----------------------------------------------------+ Transferprice * Percentage = OUTF

40.00- USD * 2/100 = 0.80- USD+-----------------------------------------------------+

Note that the system automatically uses the value '0' if no condition record is found by the accesssequence. You do not receive an error message. Consequently, in the example the transfer price wouldbe multiplied with 0%, which would yield a value of 0.00 USD for 'OUTF'.

Once all calculations have been carried out, the costing sheet contains the following 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 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 according to how the conditions areassigned to value fields (see section 4.3.3.6). Note that base conditions (in this example, theseare condition types 'REVN', 'DISC', 'DISP' and 'COGS') are not written to the line item. For thesecondition types, the value field assignment merely defines what fields 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 for how to go about carryingout the Customizing activities required to set up valuation using conditions in ProfitabilityAnalysis.

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

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 for less experienced users.Since IMG activities are not strictly hierarchical, it is ultimately up to the user to develop hisor her own method for working with the condition tool.

6. Further functions and special features

This section explains some functions and special features that are available in Customizing but werenot required in the example.

6.1 Deleting condition records

Condition records that are no longer valid can be deleted. After its deletion, the condition recordbecomes inactive and in no longer valuated. However, the condition record remains in the systemuntil the next reorganization is carried out.

l How to delete a condition record:

To delete a condition record, use the IMG function "Create condition types" to access thecondition type detail screen. From there, choose "Condition records". The system displays allthe condition records for the condition type. Use the function "Edit -> Delete" to delete theindividual records. An "L" appears on the screen to indicate that the condition records are nowinactive and will no longer be used. If you have inadvertently deleted a condition record,

choose "Edit -> Undo delete" to reactivate it again. Of course, reactivation is only possibleuntil the next reorganization is carried out in your system.

l How to reorganize condition records:

Once you have deactivated condition records, you can remove them from the system by carrying outa reorganization. This is done using the archive object "SD_COND", which is provided in archiveadministration (transaction 'SARA'). To reorganize the condition records for ProfitabilityAnalysis, you only have to select the condition records with usage "A" and application "KE" whenyou create the archive file. For more detailed information on archiving, see the online



documentation for transaction 'SARA'.

6.2 Conditions for access sequences

A "condition" here determines under what conditions the system will NOT access a certain conditiontype.

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

Example: Routine 602, which specifies that the system should not access a condition table for salesorganization 1000 only, could look like this: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 not equal to zero, and the conditionis therefore not accessed. For all other 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 for condition types. It listsall 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 ....

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' from condition 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 or for actual postings -- youcan use the "Condition analysis" function.There you receive a list of all the conditions valid in valuation as well as a short overview of howthe condition values are found.

In particular, you obtain information on

l whether a valid condition record was found

l whether an access was performed

l whether a condition record was ignored because a precondition was not met

Example:

In the following example, the same data is used as in section 4, but the characteristics and valuesfrom the billing document were entered manually in transaction KE21 (line item entry).If you call up the "Condition analysis" function from the "Value Fields"screen, you obtain thefollowing:

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

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, a condition record was found inthe second condition table only. If you now choose the "Details" function for number 02, you obtainthe characteristics or fields that were used to search for condition records in the condition table:

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 system found the conditionrecords.

6.5 Condition lists

If you want to obtain an overview of the condition records available in the system, you can createcondition lists.Condition lists list information from condition records according to various criteria.

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

l Which condition records are available for certain customer groups and product ranges in acertain country or geographical region?

l 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 thecondition values to value fields, note that several condition types can be added together in one

value field if they are all assigned to the same value field. This is also true if the conditiontypes come 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 fromthe billing document cannot be overwritten using valuation. Likewise, values from product costingcannot be overwritten by condition values from a costing sheet and vice versa.The general principle is that values from sender documents or manually entered values are notoverwritten by valuation unless they contain the value "0". The exception to this is in planning,where the valuated values have always priority over those entered manually.Different valuation methods -- that is, product costing or conditions -- do not overwrite valuefields that are already filled (value <> 0), nor do they add values to value fields that are alreadyfilled. An addition of values is only possible within two steps that use the same method -- such astwo costing sheets.

6.7 Plan valuation using pricing procedures from SD

In planning, you can also use pricing procedures from the Sales and Distribution (SD) applicationcomponent in Profitability Analysis. These have the same technical structure and work the same wayas the costing sheets in Profitability Analysis. To use a pricing procedure, enter application class"V" in the valuation strategy. This makes it possible, for example, to use material prices (SDcondition type 'PR00') to valuate your plan data in CO-PA.This is not required for actual data, since there the condition values are directly copied from thebilling document according to the value field assignment 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 in SD might use conditiontables that contain access fields which are not characteristics in Profitability Analysis. Youshould therefore check whether the fields required by the condition types are also characteristicsin your operating concern before using an SD pricing procedure! If not, the system will not find thecondition records, even if these are defined in SD.

6.7.2 Value field assignment

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

6.8 Creating conditions with reference to other conditions

When you create a condition with reference to another condition, condition records need not bemaintained twice since the system then reads the condition records of the referenced condition andreturns the results. The condition and the reference need to have an identical definition. For the



access to condition records to be successful for conditions with access sequence, the following twocases 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 as access sequence for the newcondition.

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 since this is not allowed bythe customizing. The reason is that the access sequence depends on the application. To allow thisnevertheless, define a new CO-PA access sequence that has the same definition as the correspondingaccess sequence of the SD condition, and use this access sequence for the new condition.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (21)

420992 Information: Changing CO-PA conditions / deleting records 420227 Valuation: Condition type with field 'LAND1' not supplied

398084 INFO: CO-PA ( Merkmalsableitung und Bewertung )

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

323346 Valuation with conditions: Value not transferred

330791 Performance of valuation with conditions

52849 INFO: Transfer of conditions with +/- signs

62523 CO-PA: Planned valuation with product hierarchy

68251 Partner no field for condition table

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

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

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

73477 Planned valuat.: Pricing conditions are accumulated

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

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

420992 Information: Changing CO-PA conditions / deleting records

107284 Performance improvemnt measures in condition access 168631 CO-PA: No valuation with price list type

121675 CO-PA valuation: copying condition records

111232 INFO: Valuation for materials valuated separately

74486 INFO: Overview of consulting notes for CO-PA

137067 No valuation with gross/net weight/volume I

140056 No valuation with gross/net weight/volume II

43882 Condition values of a costing sheet are not added



44766 Weight/volume-dependent condition records

62536 - Info Conditions in Profitability Analysis

Documents

Transcript of 62536 - Info Conditions in Profitability Analysis