CO Profitability Analysis
`
`The following Help Topics are available:
`
`See Also
`
`For Help on Help, Press F1
`
`Version
`
`SAP-00006065
`
`

`
`Version
`Prepared for R/3 Release 2.2.
`June 94
`
`SAP-00006066
`
`

`
`Copyrights
`
`@1994 SAP AG. All rights reserved.
`Neither this documentation nor any part of it may be copied or reproduced in any form or by any
`means or translated into another language, without the prior consent of SAP AG.
`SAP AG makes no warranties or representations with respect to the content hereof and specifically
`disclaims any implied warranties of merchantability or fitness for any particular purpose. SAP AG
`assumes no responsibility for any errors that may appear in this document. The information
`contained in this document is subject to change without notice. SAP AG reserves the right to
`make any such changes without obligation to notify any person of such revision or changes. SAP
`AG makes no commitment to keep the information contained herein up to date.
`
`SAP-00006067
`
`

`
`Introduction to Profitability Analysis
`
`This section describes the purpose of Profitability Analysis in the CO-PA System.
`the functionality and different ways of implementing the system.
`It contains the following topics:
`
`It also explains
`
`SAP-00006068
`
`

`
`Purpose of the System
`
`The CO-PA System is used to evaluate market segments (classified according to products,
`customers, orders and various other user-defined segments), or strategic business units such as
`company codes, business areas or profit centers with respect to your company’s profit or
`contribution margin.
`
`Aim of the System
`
`The aim of the system is to provide the sales, marketing, product management and corporate
`planning departments with information for the purposes of controlling and decision-making.
`The CO-PA System can be implemented in companies in any branch of industry (mechanical
`engineering, chemical, service industries and so on) and with any form of production (repetitive
`manufacturing, make-to-order manufacturing, process manufacturing). The profitability report can
`be created by period, order or project. Your company’s profit can be calculated using cost-of-sales
`accounting or period accounting.
`
`Cost of Sales Accounting
`
`In cost-of-sales accounting, the cost of sales are set off against revenue using either direct costing
`or full absorption methods. Fixed costs can be allocated on a proportional basis or en bloc to any
`level(s) of a report hierarchy. For the purposes of an interim profitability calculation, you can use
`standard costs to value the cost of sales. For the purposes of reconciliation with Financial
`Accounting (FI), you can use actual costs. (This function will be available as of a later release).
`
`Period Accounting
`
`In period accounting, the performance of a particuar strategic business unit (profit center), that is,
`revenues, changes in inventory and capitalized services, are set off against the total costs of the
`period. You will find further information on this topic in Profit Center Accounting.
`
`SAP-00006069
`
`

`
`Functionality of the System
`
`In Release 2.1, the basic data and structures required in Profitability Analysis can be maintained
`(see Basic Data). In addition
`¯ Actual data
`(see Basic Data) and
`¯ Plan data
`(see Planning)
`can be transferred to CO-PA, valued and posted there.
`provides you with a tool to analyze and evaluate your data.
`
`Basic Data
`
`Basic data consists of the definition of your classifications (criteria) and how these are to be
`quantified (value fields) for the purposes of analyzing profit.
`
`Criteria
`
`You can use both criteria defined in the SAP System and criteria defined specifically for your
`business requirements. Characteristics of the criteria in the SAP System can be derived
`automatically during the transfer of actual data and in planning. For the criteria defined within your
`business, you can create derivation rules to do this.
`
`Value Fields
`
`In addition to the criteria, corresponding value fields must be created in order to analyze
`profitability. Data from various areas can be used to do this, for example
`¯
`revenue and sales deductions from the Sales and Distribution System (SD) or from an external
`billing system,
`¯ manufacturing costs from Product Costing (CO-PC),
`¯ overhead costs from Cost Center Accounting (CO-CCA),
`¯
`special direct costs from Financial Accounting (FI),
`¯ order and project costs from Internal Orders (CO-OPA) and Project Systems (MM-PS)
`respectively.
`Line items can also be posted manually.
`All these fields must first be defined in the data structure irrespective of whether the data is to be
`posted directly to Profitability Analysis (CO-PA) or whether it is to be calculated there automatically
`by means of valuation.
`
`Data Transfer
`
`Billing data is transferred online from SD to Profitability Analysis. In the process, the relevant
`characteristics are derived and estimate sales deductions and estimate costs are calculated.
`For those customers using a non-SAP sales/billing system, an interface exists which imports an
`external dataset into the SAP System. This dataset is validated and where necessary derived
`from SAP master data records (customer master, material master). A valuation can be performed
`if necessary.
`It is also possible to transfer costs from cost centers, orders, and projects as well as perform direct
`postings from FI to CO-PA.
`
`SAP-00006070
`
`

`
`Planning
`
`In Release 2.1, you can set up a sales/profit plan within the CO-PA System. You can calculate
`both planned revenue and planned manufacturing costs using the automatic valuation function
`based on a planned sales quantity.
`Within complete planning, you can copy and revalue actual and planned data for several different
`combinations of criteria (so-called business segments) at the same time.
`The planned sales quantities can be transferred to Sales and Operations Planning (SOP) on the
`basis of products or product ranges.
`
`Reporting
`
`The reporting tool in Profitability Analysis provides a flexible, easy to use range of functions for
`analyzing datasets. The emphasis is on the dynamic analysis of multidimensional business
`segments for the purposes of measuring profitability (ranking lists with any sort order, user-defined
`contribution margin report structures, comparisons between plan and actual data or between
`periods, top n lists, data selection using threshhold values etc.). Within a particular
`"multidimensional data model", you can navigate your way through the data in several different
`ways (for example, using drill-down techniques, moving through a hierarchy and so on).
`Profitability reports can be displayed in spreadsheet form or graphic form on the screen or they can
`be printed. They can be sent via electronic mail or loaded on a PC for processing as an EXCEL
`file.
`You set the report parameters yourself within the report. Any reports your define can be stored in
`a report library along with any sort order settings, value display settings etc. which you may have
`made. The report can then be accessed at any time.
`
`SAP-00006071
`
`

`
`Basic Data
`
`SAP-00006072
`
`

`
`KDefinition of an Operating Concern
`
`An operating concern is an organizational entity in your company, used mainly to classify sales. It
`represents the highest reporting level in Profitability Analysis.
`The form of your operating concern(s) in the CO-PA System is largely defined by the criteria
`(business segments) and the appropriate value fields you choose to use (revenue, sales
`deductions, costs, quantities and so on).
`As this structure may vary greatly from business to business (for example, the structure of total
`production costs in a manufacturing company differs from that in a trading company),
`CO-Profitability Analysis is "modelled" during implementation using the configuration menu. This
`means that, by using more than one operating concern, you can maintain more than one structure.
`From a technical point of view, you are defining the structures of the line-item and segment files in
`which the CO-PA transaction data is to be saved. In addition, further objects related to the
`structure will be generated automatically.
`
`Creating an Operating Concern
`
`The operating concern must have been created in the configuration menu under Environment-->
`Maintain op. concern. In the process, you define
`¯ the name,
`¯ the currency,
`¯ the fiscal year variant and
`¯ a period type for the operating concern.
`
`Assigning an Operating Concern
`
`When transferring data to Profitability Analysis, the appropriate operating concern is derived from
`the controlling area and the controlling area, in turn, from the company code. The following
`diagram illustrates an example of the relationship between the following organizational entities:
`company code, controlling area and operating concern.
`
`ICoCde 01
`
`ICoCdeD4 1
`1COAr 0020
`
`I
`
`SAP-00006073
`
`!~p.Concern 000~
`
`

`
`You maintain the relationship between these entities in the general configuration menu under
`
`Org. structure --> Mappings --> Accounting --> Controlling --> COAr -->Op.concem.
`One operating concern should normally be sufficient for your entire business.
`Every CO-PA user should be assigned the required operating concern as a permanent user
`parameter (parameter ERB). You do this in the configuration menu using
`
`Environment-~ Maintain user-~ User--> Goto -~ Parameters.
`You should assign an operating concern to the users even if only one operating concern exists in
`the system. By doing this, the user no longer needs to enter the operating concern when he or
`she uses Profitability Analysis. If you do not set parameter ERB, the system requires you to enter
`the operating concern every time you log on to the CO-PA System and stores this entry until you
`log off.
`It is also possible to switch to another operating concern while you are working in the system using
`
`Environment -~ Set op. concern.
`Specific criteria and value fields are valid for each operating concern. You can define these
`using various methods.
`
`IDefinition of op. concern
`I
`
`I
`
`I
`I
`I
`I Definition of criteria
`I Definitionofvaluefields I
`II
`I
`I
`I I
`Monuo,
`Cho ocr,,or,o II Cho ocr,,or, o II M°nu°’ I
`I
`
`I
`
`fromexisllngfields
`
`fromSAPtables
`
`enW
`
`| fromexisSingfields |
`
`entry
`
`You choose this function in the configuration menu using
`
`Basic data --> Criteria/Value fields.
`Note
`Where an operating concern already has tables defined in the database system or where tables
`have been generated for the operating concern, you may only add new fields to the structure. You
`are then required to regenerate the operating concern. Existing data records will not contain
`values for the new fields.
`
`Defining the Criteria
`
`SAP-00006074
`
`

`
`Several basic criteria are contained in every operating concern. These include material, plant,
`customer, controlling area. The complete list is contained in the online description for the data
`element RKE FNAIMIE.
`In addition to the fixed criteria, you can define up to 30 further criteria. It is usually possible to fulfill
`your controlling requirements in Profitability Analysis using 10 to 20 criteria.
`You define the criteria per operating concern in the configuration menu. There are three methods
`of defining criteria.
`¯ Select from existing criteria
`¯ Select from SAP tables
`¯ Manual entries
`
`Selecting from a List of Existing Criteria
`
`The list of proposals contains a selection of criteria from the customer and material master files.
`You access this function using
`
`Edit --> Choose criteria.
`The list of proposals contains criteria which are particularly relevant when defining business
`segments in Profitability Analysis, for example, customer group, country, material group.
`When you confirm these fields in your operating concern structure, it means that these criteria will
`be derived automatically from the master data files when actual data is posted. You might, for
`example, enter the customer number when creating a Profitability Analysis line item. If’Country’
`has been saved as a criterion in your structure, the system reads the relevant customer master
`record and enters the country code in the line item.
`
`Selecting from SAP Tables
`
`In addition to the fields contained in the list of proposals, you can choose any fields from certain
`SAP tables to use as criteria in Profitability Analysis. To perform this, use
`
`Edit--> Choose add. criteria.
`You can choose fields from the following tables to save in your operating concern:
`
`- MARA Material master: General data
`
`- MVKE Material master: Sales data
`- MARC Material master: Plant segment
`
`- KNA1
`
`Customer master: General data
`
`- KNVV
`
`Customer master: Sales data
`
`Customer master: Company code
`- KNB1
`Criteria chosen for the operating concern in this way will also be derived automatically from the
`relevant master data table when you create a line item.
`
`Manual Entry
`
`You only need to enter criteria manually when they are used for Profitability Analysis purposes only.
`As well as the field name and description, you must enter the field type and the length of the field.
`It is also possible to carry out a specific type of automatic derivation for criteria entered manually
`(see Defininq Derivation Structures )
`
`SAP-00006075
`
`

`
`Defining Value and Quantity Fields
`
`As with criteria, you define value fields per operating concern in the configuration menu. There are
`two methods of defining value fields:
`¯ Select from existing fields
`¯ Manual entry
`Consider all the fields which are transferred to the operating concern or posted, as well as those
`which are automatically calculated in the operating concern. It may, for example, also be
`necessary to enter new value fields manually so that estimate costs or sales deductions can be
`calculated for the purposes of estimating profitability accurately. The number of value and quantity
`fields is limited to 160 fields depending on the blocking factor defined for your operating concern.
`Refer to online documentation for more information.
`
`SAP-00006076
`
`

`
`Saving an Operating Concern
`After you have saved an operating concern, it is still possible to enlarge your selection of value and
`quantity fields at a later date.
`
`Generating an Operating Concern
`
`When you have completed your selection of the criteria and value fields, you must perform the
`function Generate under the menu options Criteria or Value fields. The following occurs when you
`execute this function:
`The system generates tables, data elements, domains, lock objects and views in the data
`dictionary for the criteria and value fields defined.
`Check tables are generated for the criteria. Special views are generated for the check tables to
`support the entry of characteristics (see next section).
`As the criteria and value fields are defined dynamically, the relevant screens are automatically
`generated for the operating concern.
`Caution
`Having generated an operating concern in a given client, the generated structures can also be used
`in any other client. This does, however, mean that if you make changes to an operating concern in
`one client, they will automatically be valid for all other clients.
`
`Creating Tables in the Database System
`
`When you have generated the tables for a new operating concern, the tables
`C E 1 xxxx
`CE2xxxx
`CE3xxxx
`CE4xxxx (where xxxx = operating concern)
`must be created in the database system. To do this, use Transaction SE14.
`
`Generating Views
`
`For any criteria entered manually, you must generate views yourself. A list of the views to be
`generated is displayed when you choose Save.
`Using program RSVIEWGN (function Generate), you can generate the views online or in the
`background by entering the view name as the parameter.
`
`Maintaining Characteristics
`
`For each criterion saved in the operating concern, you must define characteristics. When a line
`item is created, the system checks against these characteristics (see .ActuaLD.ata T[.ansfer.) You
`can maintain the tables of characteristics in the Profitability Analysis menu.
`Here, you define characteristics for the criteria defined in your system (for example, ’Customer
`group’). When you choose this criterion, the system branches to a view of the customer group
`table. Customer groups are defined centrally in this table for all SAP applications.
`You also define characteristics for those criteria which you created manually and which therefore
`exist only in the CO-PA System.
`
`SAP-00006077
`
`

`
`Enter the characteristics in the tables you generated specially for these criteria.
`
`SAP-00006078
`
`

`
`Derivation of Criteria
`
`Overview
`
`If many of the criteria used in Profitability Analysis are linked to other criteria, it is usually possible
`to derive them from ’Customer’ and ’Product’. For example, both ’Customer group’ and ’Sales
`area’ can be derived from the master data. If these criteria have been selected from the
`corresponding SAP tables, then other criteria will automatically be derived from them.
`It will also be necessary to derive criteria in the following cases:
`You have defined new fields as criteria for the purposes of Profitability Analysis. If these are
`linked to other criteria, you can define special derivation rules. For example, the criterion
`’Customer classification’ and its characteristics ’Large-volume customers’, ’Mid-size customers’,
`’Small volume customers’ may be dependent on the criterion ’Customer’.
`If costs and revenues cannot be allocated on customer and product level (for example, in the
`case of an advertizing campaign for a specific product range in a certain region), then the
`criteria ’Customer’ and ’Product’ can no longer be used as a basis for the derivation of other
`criteria. This is also the case in sales and profit planning when planning is carried out on a
`higher level (for example, on customer group or product range level). In these cases, the
`derivation of criteria can only be carried out within CO-PA itself.
`The derivation of criteria in CO-PA first requires you to define so-called:
`
`D.efk~ing.D.e.r.i.v.ati.on..Rul.~.s
`
`SAP-00006079
`
`

`
`Defining Derivation Structures
`
`Before you can define the individual derivation rules, you must first define a hierarchichal structure
`of criteria to be derived. You choose this function in the configuration menu using
`
`Basic data --> Derivation structure.
`Here, for example, you specify that the criterion ’Customer classification’ (target field) is to be
`derived from the criterion ’Customer’ (source field).
`All criteria defined in Profitability Analysis can be involved in the derivation process. You can
`define up to three source fields as a basis for derivation (for example, ’Sales representative group’
`from ’Product category’/’Customer group’). It is possible to derive up to five target fields at once.
`Each derivation structure must be given a sequential number. This determines the order for
`processing and is necessary where derivation structures overlap.
`Example:
`The state is derived from the sales area and the region derived from the state. This means that
`the state must have been derived before the region can be derived. This is controlled by the
`sequence.
`When you save the derivation structure, the program automatically generates a table in which the
`derivation rules are stored, e.g. region ’Southeast’ is derived from state ’Florida’. In addition, an
`entry screen for the maintenance of the derivation rules is created.
`
`SAP-00006080
`
`

`
`Defining Derivation Rules
`
`After you have created the derivation structure, you can define the corresponding derivation rules.
`For example, customer classification ’10’ (large volume customers) is to be derived from customer
`number range 10000000 to 19999999, ’20’ (mid-volume customers) from number range 20000000
`to 29999999 and so on.
`You always maintain the derivation rules for a specific valid period. This means that when setting
`up the derivation rules, you can take into account a structural change which is to take place in the
`future (for example, a reorganization of sales areas with regions). This is particularly important in
`sales and profit planning if you wish to plan several fiscal years ahead and need to see the effects
`of structural changes immediately.
`When creating new derivation rules, you can reference existing valid periods. If, for example, a
`valid period (01/01/1993 to 12/31/1993) exists for derivation rule ’T20’ you can use this period as a
`reference for another period (01/01/1994 to 06/30/1994).
`An existing valid period can also be "split" when you change a derivation rule. If valid period
`01/01/1993 to 12/31/1999 has been defined for derivation rule ’U02’ and you wish to make a
`different assignment for the period 01/01/1995 to 12/31/1995, you can, for example, divide the
`existing period into three shorter ones:
`Period 1 from 01/01/1993 to 12/31/1994
`Period 2 from 01/01/1995 to 12/31/1995 and
`Period 3 from 01/01/1996 to 12/31/1999.
`
`SAP-00006081
`
`

`
` Valuation
`
`Overview
`
`Within Profitability Analysis, you can calculate values automatically using a valuation routine. This
`is necessary, for example, for values which are not known when the billing document is issued, but
`are important for evaluating the sales transaction (for example, commission, license fees, freight,
`rebates).
`Values can be calculated for both actual and plan data on the basis of
`- a percentage rate (basis is a value field, e.g. 2% of gross revenue)
`- an absolute amount (e.g. USD 50.00) or
`
`- a quota (basis is a quantity field, e.g. USD 3.00 per item).
`In addition, valuations can be performed on a scale basis and dependent on certain criteria. You
`can use all the criteria in Profitability Analysis as well as other fixed fields (for example, company
`code, posting period, sales organization) as source fields.
`A valuation of the manufacturing costs on the basis of product costing estimates from CO-PC can
`be executed for actual and plan data (see implementation guidelines).
`For valuation in sales and profit planning, you can use not only the conditions created in CO-PA but
`also those conditions created in the SD pricing mechanism. These can be used to calculate
`revenue and sales deductions, for example.
`If you require valuation data not covered by the standard SAP System, it is possible to use your
`own user exits to access your own valuation routines.
`
`Valuation Control
`
`Automatic valuation for actual and plan data can be run differently.
`the configuration menu under Basic data --> Valuation:
`
`You can control valuation in
`
`Valuation --~ Control --> Act, data valuation and
`
`Valuation --> Control --> Plan data valuation.
`For actual data, you can execute several valuations per record type. For plan data, you can
`execute several valuations per plan version. In both cases you must define the sequence in which
`valuations are to be performed. Note the following:
`To use product costing estimate values, check off the relevant field and enter the name of the
`value field to be used as a quantity for the calculation.
`To calculate values using conditions, enter the name of the costing sheet you wish to use. If
`you wish to use several costing sheets, you must make several entries with a sequential
`number. In planning, it is also possible to use conditions created in SD. For this reason, you
`must enter the application in which the conditions were originally created in the control screen
`for planning.
`To activate your own valuation routine, enter a three-figure ID as the exit number. Your
`company’s specific valuation will be performed under this number (see the online documentation
`for guidelines on naming user exits).
`
`Valuation using Product Costing
`
`SAP-00006082
`
`

`
`The automatic valuation of value fields using a product costing estimate can be different for actual
`and plan data. It can also be different per plan version. You define this in an Analysis path.
`The analysis path defines which product costing estimate should be used as the basis for the
`valuation of each material or material type for a specific period of time. To do this, you enter the
`key to be used to access the product costing data.
`The cost component layouts in the system (by which the production costs are structured) must be
`assigned to the relevant value fields in Profitability Analysis. The costs can be separated
`according to whether they are fixed or variable.
`
`Valuation using Conditions
`
`Value fields are calculated using an interface to the calculation of conditions in the Sales and
`Distribution (SD) System. The valuation structure is flexible.
`
`Condition Types
`
`Whenever you calculate value fields in Profitability Analysis, you must use condition types.
`The condition type defines how the system calculates certain value fields. If, for example, you
`define a condition type for license fees, the system can calculate a fixed amount for those license
`fees (e.g. USD 1.00 per unit). You can also, however, have the system calculate the fees on a
`percentage basis (e.g. 1.5% of sales revenue).
`Caution
`All condition types used to calculate base amounts for the addition of a supplement (e.g. the
`condition type ’KB00’ based on the value field ’Revenue’) must be created with condition category K
`(basic amount excl. tax), calculation type B (fixed amount) and condition class B (prices). Such
`condition types do not need an access sequence.
`Two other condition types besides K are supported:
`E
`Cash discount
`This condition type determines the percentage from the payment key stored in the customer
`master record. For this reason, this condition is only effective when you enter a customer in
`whose master record a payment key has been defined.
`Cost price
`Using this condition type, either the standard price (with price control S) or the moving average
`price (with price control V) is derived from the customer master record.
`Neither of these condition types require an access sequence.
`
`G
`
`Value Field Assignment
`
`All condition types defined in the system and used in costing sheets must be assigned to the
`corresponding value fields in CO-PA. Condition type ’LICN’ (license fees) is, for example,
`assigned to value field ’LICNS’.
`
`Condition Tables
`
`Condition tables play an important role in the defining and editing of individual condition records
`during valuation.
`A condition table defines the fields (keys) which appear in each individual condition record of a
`condition type. The key to a condition table contains the combination of these fields.
`In the above example, the table contains just one field, the material number. If you create
`condition records for the condition type ’License fees’, you can, for example, define different
`
`SAP-00006083
`
`

`
`percentages in the system for the products sold.
`
`Access Sequences
`
`Every condition type for which you create condition records is assigned an access sequence.
`Using the access sequence, the system searches for the valid data records during valuation.
`The access sequence defines the strategy for searching for the relevant condition types. In
`particular, it defines the sequence in which the system searches for condition records.
`Using the access sequence, you can define, for example, that the system looks first for specific
`condition records, such as sales deductions defined for a specific customer. If nothing is found,
`the system searches for more general records such as sales deductions defined for the customer
`group and so on.
`
`Costing Sheets
`
`Conditions which you have defined for valuation can be combined in costing sheets. A costing
`sheet is used to define a particular sequence within a group of condition types. This defines:
`¯ which subtotals are calculated,
`¯ on what basis the system calculates supplements and discounts.
`For example, the license fees and sales commission are calculated on the basis of revenue using
`the following entries
`Step
`CndTy Description
`10
`KB00 Revenue
`20
`LICN License fees 10
`30
`COMM Sales comm. 10
`The calculation can also be based on user-defined subtotals.
`
`From
`
`SAP-00006084
`
`

`
`Authorizations
`
`Authorization Objects
`
`During the implementation of CO-PA, profiles must be created for the users of Profitability Analysis.
`In the profile K_RKE_ALL delivered with the system, all the authorization objects are combined:
`¯ Set operating concern
`K_KEA_ERG
`¯ Operating concern: Structure maintenance
`K_KEA_TC
`¯ Maintenance of derivation structures
`K KES TC
`¯ Maintenance of derivation rules
`K KER TC
`¯ Transfer of data to CO-PA
`K KEDT TC
`¯ Actual data in CO-PA
`K KEI TC
`¯ Condition maintenance in CO-PA
`K KEKD TC
`¯ Profit planning
`K_KEPL_TC
`¯ Plan versions
`K KEPL VER
`¯ Row/column structure in profit planning
`K_KEPL_RC
`¯ Profit planning: Authorization objects
`K_KEPL_BER
`¯ Reporting
`K_KEB_TC
`¯ Row/column structure in profitability report
`K_KEB_RC
`¯ Profitability report names
`K_KEB_REP
`¯ Profitability report: Authorization objects
`K_KEB_BER
`In addition, authorizations for the following objects are required in the profile:
`¯ CO: Cost element master
`¯ RK-C: Authorizations for structures and key figures in SAP-EIS
`¯ RK-C: Authorization for function code
`¯ Number range maintenance
`¯ Table maintenance (using standard tools such as SM31).
`Refer to the documentation on the individual objects in the implementation guidelines.
`In addition, it is possible to create authorization objects for combinations of criteria and key figures
`in planning and reporting. To do this, choose the relevant menu options in the menus Planning or
`Profitability report.
`The authorization object is used within the current operating concern to protect combinations of
`criteria from unauthorized access. Within one authorization object, you can specify a combination
`of up to ten objects. All other objects are then treated as if they were entered with * (i.e. the user
`has all the authorizations for these criteria). By making several selections of up to ten criteria, you
`can generate various authorization objects.
`As the authorization check is performed for all authorization objects of an application (reporting,
`planning) within one operating concern, all the objects created are linked to one another. This
`means that authorizations must be created for all authorization objects in an application. If the
`user lacks an authorization for just one object, his or her request will be refused.
`
`SAP-00006085
`
`

`
`The following types of authorizations are possible for an object:
`¯ Normal characteristics or key figures
`¯ All characteristics of the criterion (*)
`¯ Total of characteristics for the criterion (:)
`¯ Blank characteristics (&)
`If intervals have been defined in the row/column structures, the user requires the * authorization.
`The validation of the entry against an authorization object per field in the object is illustrated below:
`
`Content of entry field
`
`*
`
`Y
`
`Blank Does not exist
`
`X
`
`X X
`
`X
`
`X X
`
`Authorization
`
`(A,Z)
`
`X &
`
`Note
`By creating an authorization object for Customer and Product, you can avoid reports which have a
`negative impact on performance. You create 2 authorizations for this object:
`
`a) Customer*
`Product 01000000 to 01900000 (or allowed values)
`
`and
`
`b) Customer4500000 to 4800000 (or allowed values)
`Product *
`
`Using these two authorizations, the user can create a list of products for the customers entered and
`a list of customers for the products entered. However, all customers and all products cannot be
`listed at the same time which would result in poor performance.
`You will find more detailed information in the implementation guidelines.
`
`SAP-00006086
`
`

`
`Number Ranges
`Number ranges must be maintained for the assignment of document numbers to actual and plan
`line items.
`Internal number ranges are need for planning as well as for the assessment of cost center costs.
`The maintenance of an internal and/or an external number range for the actual line items is
`optional. The number ranges are directly linked to the operating concern and the record type.
`
`Operating con cern
`
`Record type
`
`Number range group
`
`You access the maintenance transaction from the configuration menu.
`for an operating concern, you must perform the following steps.
`¯ Enter the operating concern
`¯ Create a group
`Group -~ Maintain -~ Group --> Insert
`A group is a combination of internal or external number ranges.
`¯ Assign a record type to the group
`
`To create number ranges
`
`Edit --> Select element
`and
`Edit --> Assign element group.
`
`SAP-00006087
`
`

`
`Actual Data Transfer
`
`SAP-00006088
`
`

`
`Automatic Transfer of Billing Data
`
`Posting Invoiced Revenue, Sales Deductions and Costs Online to CO-PA
`
`The revenue is calculated during billing by the logistics system with the help of a pricing mechanism
`and is then entered on the billing document. Where sales deductions are known (for example,
`rebate given, planned discount), these are also recorded on the billing document.
`In addition, the cost price (landed price for trade goods or cost of goods manufactured for in-house
`products) can be calculated. When the billing data is posted, these