SAP ABAP Data Element KUND_HIERA (Processing of Sales Order Structure in Results Analysis)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-CIC (Application Component) Interaction Center WinClient
     ⤷ KKAG (Package) Period costing individual case
Basic Data
Data Element KUND_HIERA
Short Description Processing of Sales Order Structure in Results Analysis  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KUND_HIERA    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 SlsOrd str 
Medium 15 SlsOrd structur 
Long 20 SalesOrder structure 
Heading 0   
Documentation

Definition

The sales order structure indicator specifies how results analysis handles the data of sales order items.

Use

You use this indicator when you have both costs and revenues on more than one item and the costs and revenues can be carried on the same item or on different items.

Procedure

If you are carrying the costs on the same items as the revenues, you can perform results analysis separately for each item. In this case you either leave the sales order structure indicator blank or set it to E.

If you want to perform results analysis for the cumulative data or for each order, or if you are carrying the costs and revenues on different items, set the sales order structure indicator to A, B, or K depending on your requirements.

  • If you want to perform results analysis on one of the items in a sales order independently of the sales order structure, you use a representative item as follows:
    • Set the sales order structure indicator to K.
    • Enter a results analysis key in the account assignment view of the sales order item for which you want to perform results analysis.

      Make sure that settlement is only allowed for the representative item. Otherwise, the costs will be settled to Profitability Analysis (CO-PA) twice. Because the settlement profile is stored in the requirements class and the requirements class is determined through the requirements type, make sure that you are using a different requirements type for the representative item than for the other items. You must also specify a settlement profile that prohibits settlement in the requirements class of the items for which no results analysis is to be performed.

  • In set processing, the individual items are in a predefined relationship to each other and constitute a sales order structure.
    • If you want to perform results analysis for one or more items after summarizing the planning data and actual data of one or more items below them, set the sales order structure indicator to A.
      Any results analysis data on lower items will not be included. Enter a results analysis key only in the account assigment view of the top item or items for which you want to perform results analysis.
    • If you want to perform results analysis on one or more items after summarizing all data, depending on the sales order structure and including any data on items below those items determined by results analysis, set the sales order structure indicator to B.
      If you have entered results analysis keys for the lower items, the data determined for these items are included in results analysis for the highest item. As with "A", in this case you have complete results for the structure as a whole. However, not all results analysis data are updated to the top item. Instead, the top item receives only the difference between the results analysis data of the top item and the results analysis data of the lower items that have already been updated.
      Make sure that you have entered a results analysis key in the account assignment view of the items for which you want to perform results analysis. All lower-level items with a results analysis key must be processed before you perform results analysis for the top item. In collective processing, this is only assured when lower-level items have a higher item number than the higher-level items.
      Sales order structure indicator B is recommended when you are interested in both the result of the sales order and in the result of individual items, for example because these items have materials of different profit centers.

In set processing, make sure that settlement is only allowed for the items for which a results analysis key has been specified. Lower items should have a settlement profile that prohibits settlement.

Since the settlement profile is specified in the requirements class and the requirements class is determined through the requirments type, make sure that the item to be settled is not using the same requirements type as for the other items. Make sure that a settlement profile that prohibits settlement has been specified in the requirements classes of the items for which no results analysis is to be performed.

The system summarizes the data to the corresponding item automatically during results analysis. You cannot start summarization separately.

Remember that in Profitability Analysis (CO-PA) only the characteristics of the items for which results analysis was performed are visible.

Examples

  • For results analysis with set processing when the costs and revenues are on different items:
    • On the main (higher-level) item you only have revenues. The costs arise on the lower items.
    • You have revenues on the main item and on lower items. The costs arise only on the main item.
  • For results analysis with a representative item:
    • The total of a sales order is to be billed to an item. Costs are incurred on all items.

Dependencies

History
Last changed by/on SAP  19971104 
SAP Release Created in