SAP ABAP Data Element HIERA_VERA (Project Structure Processing 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 HIERA_VERA
Short Description Project Structure Processing in Results Analysis  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type HIERA_VERA    
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 ProjStruct 
Medium 15 Project Struct. 
Long 20 Project Structure 
Heading 0   
Documentation

Definition

The project structure indicator determines how the data of individual WBS elements is handled in results analysis.

Use

You use this indicator when you want to transfer the revenues of a billing element and the relevant data of subordinate WBS elements onto one level for results analysis purposes.

The work breakdown structure arranges the project into a hierarchy of WBS elements whose attributes are defined through operative indicators. You can define a WBS element to be a billing element, a planning element, or an account assignment element. The billing element is normally the WBS element at the highest level, above the planning elements and account assignement elements. However, you can also arrange individual billing elements into a hierarchical relationship.

  • If you want to perform results analysis for individual higher-level billing elements on the basis of data of the subordinate WBS elements that has been summarized at those billing elements, and are not interested in seeing results analysis data for each WBS element, set the project structure indicator to A or C. In this case, you perform results analysis mainly for the purpose of comparing costs and revenues for the project.
  • If you are interested in determining the work in process for individual WBS elements that are not billing elements, set the project structure indicator to T or U. This is appropriate when your project structure covers multiple company codes, or when individual WBS elements are assigned to different profit centers and you are using a nonvaluated sales order stock in engineer-to-order. In this case, you perform results analysis mainly to valuate your inventories.

If you are interested in performing results analysis or calculating work in process for each WBS element in a project definition, it is recommended that you use project structure indicator E for performance reasons.

For more information on the effects of the above indicators and on the indicators B and Q, refer to the text below.

Procedure

Depending on your requirements, set one of the following indicators:

  • If you want to perform results analysis for individual higher-level billing elements, set the project structure indicator to A or C. In this case, results analysis is only possible for WBS elements that are billing elements; results analysis for subordinate WBS elements is not possible.
    Make sure that a results analysis key is only specified for the billing elements for which you want the system to calculate results analysis data.
    Make sure that settlement is only allowed for the highest billing element for which results analysis is performed on the basis of the summarized data.
    The data on the corresponding items is summarized automatically during results analysis - you don't have to start summarization separately.

    Make sure that there are no billing elements above or below the billing elements for which you want to perform results analysis.

    • If you have only assigned planning elements and account assignment elements below your billing elements and want to perform results analysis on one or more billing elements including all planning data and actual data of the subordinate WBS elements, set the project structure indicator to A. (If you don't make an entry, the system will proceed as if you had entered A.)
    • If you want to use the exact same processing except that when the WBS element has the status TECO (technically completed) you want to use actual values instead of planned values for the WBS element for which the project structure indicator is set and for all subordinate WBS elements, set the project structure indicator to C. Proceed in other respects as with project structure indicator A.
  • If you want to perform results analysis on one or more billing elements and summarize onto these billing elements the data of billing elements located below them (including any values on them calculated by results analysis), set the project structure indicator to B.
    If you have specified results analysis keys for subordinate billing elements, the values calculated there are included in results analysis for the higher-level billing element. The results analysis data calculated for each element includes all planning data and actual data for that element plus the subordinate elements.

    Results analysis data is updated for each element for which a results analysis key has been specified. The difference between the results analysis data of the higher-level element and the results analysis data of the subordinate elements is updated to the higher-level element. You can view the total of the results analysis data, planning data, and actual data of the subordinate elements on the higher-level billing element. Inclusion of the results analysis data of subordinate elements is only possible for the higher-level billing element in each case. It is not possible to include the results analysis data of multiple subordinate levels when calculating the difference shown on the higher-level billing element.

    Make sure that a results analysis key has been specified for the WBS elements for which results is to be performed. First perform results analysis within the project hierarchy for the subordinate elements and then for the higher-level elements. In collective processing, the elements are processed in the proper order automatically.

    Setting the project structure indicator to B is appropriate when you are interested both in the result of the project as a whole and in the results of intermediate steps.

  • If you are using a nonvaluated sales order stock and want to determine work in process for individual WBS elements (these can be subordinate elements), set the project structure indicator to Q, T, or U . In this case, results analysis data is calculated for individual subareas. This is appropriate for example when the structure of your project covers more than one company code, or when individual WBS elements are assigned to different profit centers.

    If you are using indicators T and U, results analysis data calculated for individual elements, like the actual data, is not automatically summarized to the higher-level elements during results analysis.

    Remember that there can still be work in process on subordinate WBS elements even if the overall project has the statuses "final delivery" and "final billing".
    Make sure that a results analysis key has been specified for all WBS elements for which you want to calculate results analysis data.
    Make sure that settlement is allowed for all billing elements and for all elements for which work in process is determined.

    • If you want to perform results analysis on each individual billing element and for the subordinate WBS elements (in the case of the subordinate WBS elements, results analysis is performed for the purpose of calculating WIP), set the project structure indicator to T. All planning data and actual data are summarized to the next-highest external billing element or WIP element. Any data on billing elements below the billing element for which results analysis is performed is not included. This ensures that the data of each billing element is only included once.
    • If you want to use the scenario of project structure indicator T but want to summarize all the planning data of all subordinate elements onto a billing element, set the project structure indicator to U. This is appropriate when you want to calculate work in process for individual elements of a project - such as because the WBS elements of the project structure are assigned to different company codes. You want to compare the total actual cost of the project with the planned cost of the project at a later time. You settle the actual costs in accordance with the settlement rule. When you settle, make sure that you settle to the billing element or to a subordinate WBS element.
    • If transfer prices have been arranged and each subproject (WBS element) has its own budget responsibility, results analysis can be performed separately for such subprojects. In this case, set the project structure indicator to Q. This has the following effects:
      • - In Profit Center valuation, all planning data and actual data are rolled up to the next internal or external billing element
      - In the other valuation views, all planning data and actual data are rolled up to the next internal or external billing element
      The data are automatically summar
History
Last changed by/on SAP  19971104 
SAP Release Created in