|
0. Table of Contents
- 1. Introduction
- 2. How Does the Logical Database Work?
2.1 General Information
2.2 Table Structure of the Logical Database PSJ
2.2.1 Structure
2.2.2 Structure including GET LATE
2.2.3 Structure with Access to Cost Collectors
2.3 Criteria for Hierarchy Structure
2.3.1 The "Normal" Hierarchy
2.3.2 Alternative Hierarchies
- 3. Profiles
3.1 Database Profile TCNDB
3.2 Structure Profile TCNDS
- 4. Programming Tips
- 5. Authorization Check
5.1 General Information
5.2 Checked Authorization Objects
5.3 Authorization Check in Detail
5.4 Authorization Check Log
- 6. Migration from CNJ to PSJ
6.1 General Information
- 6.2 Adapting Reports During Migration
1. Introduction
The logical database (LDB) PSJ is used throughout the Project System inselecting data from the physical database. The logical database alsoprovides the data for customer-specific reports.
As of Release 3.0, the logical database PSJ replaces CNJ. For moreinformation, see chapter 6. 2. How Does the Logical Database Work? 2.1 General Information
The scope of the data selected by LDB PSJ and the structure of thehierarchy is described in two profiles, defeind in tables TCNDB andTCNDS. You can us target restrictions on the data to be selected toimprove the performance of your evaluation reports. See chapter 4 formore information.
As far as the hierarchical arrangement of the tables and structures inLDB PSJ is concerned, not the following:
- With LDB PSJ, you can set up the hierarchy from different viewpoints.
The result is that the hierarchical arrangement of the database tablesis as defined in SE36; this is not necessarily the same as the order inwhich the individual GETs are processed.
- The tables for the CO objects (cost/revenue/financial data) are
accessed using a PERFORM.2.2 Table Structure of the Logical Database PSJ
The basic concept of the logical database PSJ is to have a hierarchicalarrangement of tables but now only subordinate to certain objects.These objects include: Project definitions (PROJ), sales documents(VBAK), sales document items (VBAP), WBS elements (PRPS_R), orders ornetworks (AUFK), activities (ACT01), and capital investment programs(IMTP).
The processing of these events is not triggered by a database mechanismitself, rather through an explicit PERFORM for the relevant PUT events.The information on the events to be processed is available in thehierarchy table (RSTHIE), which is the first to be created after theevent START-OF-SELECTION.
Because of this processing logic, the processing of the GET LATEstatements for the above-mentioned tables must be handled exclusivelyusing dummy structures. These structures are named PSDYXX (where XX isthe short ID of the object type).
The system accesses the cost collector using a PERFORM for the routinePUT_ELM_PS. This routine is called for the previously mentionedobjects.
,,Object Type,,Description
,,PD,,Project definition
,,PR,,WBS element
,,NP,,Network header
,,OR,,Material component
,,NV,,Network activity
,,OV,,Order activity
,,VK,,Sales document
,,VB,,Sales document item 2.2.1 Structure
The following example should clarify the information in 2.2. Onlyoriginal data is selected from the database and is displayed in the"normal" structure view.
Simplified structure of the logical database PSJ:
ARKOPF Archive header
VSKOPF Version header
RSTHIE Hierarchy table
PROJ Project definition
VBAK Sales document header
PRPS_R WBS element
AUFK Order
ACT01 Activity
IMTP Capital investment program
ELM_PS Additional PS data
..
Cost collector
Assume that, for example, a project consists of:
- a project definition "Project def.",
- a work breakdown structure with three WBS elements
"WBS element 1" (WBS level 1),
"WBS element 1-1" (WBS level 2) and
"WBS element 1-2" (WBS level 2), as well as
- a network "Network 1", which is assigned to WBS element "WBS element
1-2"
- a network activity "Network activity 1" for "Network 1" and
- a PS text for WBS element "WBS element 1".
Sample report:
REPORT PSJDOKU1.
TABLES: RSTHIE, PROJ, PRPS_R, AUFK, ACT01.
GET PROJ.
WRITE: / 'PROJ', PROJ-PSPID.
GET PRPS_R.
WRITE: / 'PRPS', PRPS_R-POSID.
GET PSTX.
WRITE: / 'PSTX', PSTX-PSTXTKY.
GET AUFK.
WRITE: / 'AUFK', AUFK-AUFNR.
GET ACT01.
WRITE: / 'ACT01', ACT01-AUFPL, ACT01-APLZL.
The following table shows you some of the fields from the RSTHIE tableof this sample project.
RSTHIE-ID,,RSTHIE-TYPE,,RSTHIE-NAME,,,,RSTHIE-TLEVEL
000001,,PD,,Project def.,,,,0
000002,,PR,,WBS element 1,,,,1
000003,,PR,,WBS element 1-1,,,,2
000004,,PR,,WBS element 1-2,,,,2
000005,,NP,,Network 1,,,,3
000006,,NV,,Network activity 1,,,,4
When the report is started, the system first looks for the databaseprofile. In the profile you have specified which data should beselected from the database and how it should be displayed. Use profile"000000000001" for the sample report. Afterwards the selection screenof the PSJ logical database should be displayed. If you enter theproject definition "Project def.", you will get a list which lookssomething like this:
'PROJ' Project def.
'PRPS' WBS element 1
'PSTX' Internal text number
'PRPS' WBS element 1-1
'PRPS' WBS element 1-2
'AUFK' Network 1
'ACT01' Network 1 Network activity 1
Internally, the logical database PSJ handles the project as follows:
- There are GETs for the tables in the selection report, which are below
ARKOPF and VSKOPF in the hierarchy. For this reason PUT_ARKOPF andPUT_VSKOPF are processed. (PUT_XXX is a form routine that is processedwhen there is a GET XXX in the application report.) Since this isoriginal data, ARKOPF and VSKOPF have initial value. During theprocessing of PUT_VSKOPF the data for the project definition, WBSelements, orders and network activities is selected from the databaseand saved in internal tables.
- A PUT_RSTHIE is processed. The logic of PSJ ensures that event
processing for RSTHIE is always carried out, even if GET RSTHIE is notstated explicitly in the selection report. The system reads thehierarchy table in the form routine PUT_RSTHIE. The table will beprocessed in a loop and then a different form routine will be called byobject type (RSTHIE-TYPE) such as PUT_PROJ for project definitions,PUT_PRPS_R for WBS elements, PUT_AUFK for orders and PUT_ACT01 foractivities.
- Within these form routines the normal LDB logic is used. As soon as the
selection report contains a GET for a table that is subordinate in thehierarchy to the structure or table currently being processed, thesystem processes the appropriate form routine from the LDB. In theexample, this is a GET PSTX which causes the PS text related to "WBSelement 1" to be displayed after the WBS element.2.2.2 The Structure Including GET LATE
If you include LATE processing in report PSJDOKU1 by adding a GET LATEfor the GET events used, the system does not produce the results youexpect in the list output. The reason for this is explained by the PSJprocessing logic described in 2.2.1. For example, after the event PROJhas been processed, the LDB returns to the processing for RSTHIE. Thisway the database tool works directly after the GET PROJ to the GET LATEstatement because, strictly speaking, there are no more subordinateobjects in the hierarchy below table PROJ. Logically, however, this isnot correct. For this reason, event processing was changed so that aGET LATE is carried out at the correct logical event. To achieve this,the dummy structures PSDYPD, PSDYVK, PSDYVB, PSDYPR, PSDYNP, PSDYNV,PSDYPG and PSDYIP have been created. Include them in your selectionreport. The system starts with these dummy nodes and branches for theprocessing of the structure RSTHIE, which means that the LATE event canonly be processed once the PSJ returns from the PUT routine for RSTHIEto the dummy nodes.
Sample report:
REPORT PSJDOKU2.
TABLES: RSTHIE, PROJ, PRPS_R, AUFK, ACT01,
PSDYPD, PSDYPR, PSDYNP, PSDYNV.
GET PROJ.
WRITE: / 'PROJ', PROJ-PSPID.
GET PROJ LATE.
WRITE: / 'PROJ LATE', PROJ-PSPID.
GET PRPS_R.
WRITE: / 'PRPS', PRPS_R-POSID.
GET PRPS_R LATE.
WRITE: / 'PRPS LATE', PRPS_R-POSID.
GET PSTX.
WRITE: / 'PSTX', PSTX-PSTXTKY.
GET PSTX LATE.
WRITE: / 'PSTX LATE', PSTX-PSTXTKY.
GET AUFK.
WRITE: / 'AUFK', AUFK-AUFNR.
GET AUFK LATE.
WRITE: / 'AUFK LATE', AUFK-AUFNR.
GET ACT01.
WRITE: / 'ACT01', ACT01-AUFPL, ACT01-APLZL.
GET ACT01 LATE.
WRITE: / 'ACT01 LATE', ACT01-AUFPL, ACT01-APLZL.
GET PSDYPD.
GET PSDYPR.
GET PSDYNP.
GET PSDYNV.
The project is the same as the example described under 2.2.1.
The report is started with the same parameters as in 2.2.1 and you willget a list that looks something like this: (for easier reading, thelines have been indented according to hierarchy level)
'PROJ' Project def.
'PRPS' WBS element 1
'PSTX' Internal text number
'PSTX LATE' Internal text number
'PRPS LATE' WBS element 1
'PRPS' WBS element 1-1
'PRPS LATE' WBS element 1-1
'PRPS' WBS element 1-2
'AUFK' Network 1
'ACT01' Network 1 Network activity 1
'ACT01 LATE' Network 1 Network activity 1
'AUFK LATE' Network 1
'PRPS LATE' WBS element 1-2
'PROJ LATE' Project def.
Without the statements GET PSDYPD, GET PSDYPR, GET PSDYNP and GETPSDYNV, the list would have looked like this:
'PROJ' Project def.
'PROJ LATE' Project def.
'PRPS' WBS element 1
'PRPS LATE' WBS element 1
'PSTX' Internal text number
'PSTX LATE' Internal text number
'PRPS' WBS element 1-1
'PRPS LATE' WBS element 1-1
'PRPS' WBS element 1-2
'PRPS LATE' WBS element 1-2
'AUFK' Network 1
'AUFK LATE' Network 1
'ACT01' Network 1 Network activity 1
'ACT01 LATE' Network 1 Network activity 1 2.2.3 The Structure with Access to the Cost Collector
In the logical database PSJ, the tables and structures of the costcollector are only included in the table hierarchy once. No distinctionis drawn between cost tables for WBS elements, networks, andactivities. Take a look at the project in 2.2.1. The WBS element "WBSelement 1" and the network header "Network 1" should have the costsfrom external postings. With the following report you can display thesecosts.
Sample report:
REPORT PSJDOKU3.
TABLES: RSTHIE, PROJ, PRPS_R, AUFK, ACT01,
PSDYPD, PSDYPR, PSDYNP, PSDYNV,
COSP1.
GET PROJ.
WRITE: / 'PROJ', PROJ-PSPID.
GET PROJ LATE.
WRITE: / 'PROJ LATE', PROJ-PSPID.
GET PRPS_R.
WRITE: / 'PRPS', PRPS_R-POSID.
GET PRPS_R LATE.
WRITE: / 'PRPS LATE', PRPS_R-POSID.
GET PSTX.
WRITE: / 'PSTX', PSTX-PSTXTKY.
GET PSTX LATE.
WRITE: / 'PSTX LATE', PSTX-PSTXTKY.
GET AUFK.
WRITE: / 'AUFK', AUFK-AUFNR.
GET AUFK LATE.
WRITE: / 'AUFK LATE', AUFK-AUFNR.
GET ACT01.
WRITE: / 'ACT01', ACT01-AUFPL, ACT01-APLZL.
GET ACT01 LATE.
WRITE: / 'ACT01 LATE', ACT01-AUFPL, ACT01-APLZL.
GET PSDYPD.
GET PSDYPR.
GET PSDYNP.
GET PSDYNV.
GET COSP1.
WRITE: / 'COSP1', COSP1-KSTAR, COSP-WTG001.
The report is started with the same parameters as in 2.2.1 and you willget a list that looks something like this: (for easier reading, thelines have been indented according to hierarchy level)
'PROJ' Project def.
'PRPS' WBS element 1
'PSTX' Internal text number
'PSTX LATE' Internal text number
'COSP1' Cost element, Value
'PRPS LATE' WBS element 1
'PRPS' WBS element 1-1
'PRPS LATE' WBS element 1-1
'PRPS' WBS element 1-2
'AUFK' Network 1
'COSP1' Cost element, Value
'ACT01' Network 1 Network activity 1
'ACT01 LATE' Network 1 Network activity 1
'AUFK LATE' Network 1
'PRPS LATE' WBS element 1-2
'PROJ LATE' Project def.
When evaluating the costs, you can program the processing for the LATEevent in the tables PRPS_R and AUFK. You can get additional informationon the element in the hierarchy that is currently being processed byexpanding the sample report with GET RSTHIE and GET ELM_PS. The fieldscontained in these structures can be found in the structure view intransaction SE36 or in the data dictionary. When you analyze the data,please rememeber that the cost collector table will be processed evenif the dummy structures PSDYXX are missing. In this case, the LATEevents will be processed before GET COSP1. 2.3 Criteria for the Hierarchy Structure
In 2.2, you saw examples for representing a hierarchy without thedetails of the hierarchy structure criteria. Here in 2.3, you can readabout the hierarchy structure criteria.
The reporting hierarchy that is constructed in LDB PSJ is determinedboth by the data selected from the database and through thespecification of a project view.
When you carry out a report you have written yourself, you caninfluence both criteria. You can either carry out your report with thesuitable database profile or temporarily modify a database profile foryour purposes at the time you carry out the report. There are twofunction keys on the selection screen of PSJ to assist you in doingthis ("DB profile" and "Change DB profile"). SAP provides you withstandard database profiles in the table TCNDB. You can maintain them inCustomizing and can even create your own profiles.
The various individual fields in the database profile are explained indetail in 3.1. 2.3.1 The "Normal" Hierarchy
If you have set all the indicators with "X" except for "commercialreports" in the database profile and you have selected "projectstructure" as your view, the system will set up the hierarchy accordingto the following schema:
Project definition
WBS element
Sales document item
Network
Activity
Material component
Activity element
Order other than network
Network
Activity
Material component
Activity element
WBS element
Sales document item
Network
Activity
Material component
Activity element
Order other than network
Network
Activity
Material component
Activity element
You should interpret the scheme as follows: If you enter a projectdefinition on the selection screen, it will be displayed at hierarchylevel (RSTHIE-TLEVEL = 0). The WBS elements with an assignment to theproject definition are arranged on the next lower hierarchy level (i.e.RSTHIE-TLEVEL = 1). Sales document items that are assigned to WBSelements are on the hierarchy level below the corresponding WBSelement. Network headers and other orders with an assignment to a WBSelement are also one level below the WBS element. Network activitiesare another level lower in the RESHIE. Activity elements aresubordinate to the network activities in the hierarchy.
WBS elements are specially placed in the hierarchy structure since theyalready have a hierarchy of their own. The hierarchy level of thereporting structure is determined by the level of the WBS element. Thismeans that the hierarchy level of possible subordinate networks andeven further subordinated objects is determined by the WBS level (seealso the example in 2.2.1).
If you enter WBS elements on the selection screen which are notassigned to the project definition, the system places them in their ownhierarchy, starting with level 0, and all subordinate objects areincluded into this new hierarchy as described previously. In the caseof networks, which are not assigned to a project definition or to a WBSelement, the system creates another tree in the hierarchy, startingagain with level 0.
The logic is different when you set the indicator "commercialevaluation". Depending on whether the network has header or accountassignment, either the network header or the network activities will betaken into account in the hierarchy.
If you have valuated stock and activate the "Commercial evaluation"indicator (CN_COREP), the hierarchical arrangement of the materialcomponents changes. From a purely technical viewpoint, the materialcomponent is subordinate to the activity in the hierarchy, which meansthat the material component is directly subordinate to the assigned WBSelement in the hierarchy if stock is valuated and the commercialevaluation indicator is activated.
In the example below, the activity is assigned to WBS element P1 andthe material component is assigned to WBS element P2.
Commercial Evaluation,,Technical View
Project definition,,Project definition
WBS element P1,, WBS element P1
Activity,, Activity
WBS element P2,, Material component
Material component,, WBS element P2
If the project stock is not valuated, the hiearchical arrangement inthe commercial evaluation is the same as in the technical view.
When you change the database profile so that some objects are notselected, you also change the reporting structure as well. If, forexample, you do not allow any WBS elements to be selected, the networkswith an assignment to a WBS element in the selected project will bearranged one level below the project definition in the hierarchy. 2.3.2 Alternative Hierarchies
In addition to the "normal" views of the structure, there arealternative views of a project: the profit center view, cost centerview, summarization view, sales view and the view of capital investmentprograms. In these views, the hierarchy is structured primarilyaccording to the relevant criteria. For example, in the case of aprofit center view of the project, the profit center hierarchy isspecified in the project profile TCNDS (see 3.2). This hierarchy isevaluated and the objects assigned to a profit center will be displayedone level below the profit center node in the hierarchy. The hierarchyfor the objects assigned to a profit center will be created accordingto the criteria outlined in 2.3.1. Additionally, the assignment to aprofit center also determines whether the appropriate object isinserted in a certain place in the hierarchy. For example, a WBSelement that has a different profit center than the one in the projectdefinition to which it is assigned will be included in the hierarchy ina different spot than in the normal structure view.
This applies to all of the remaining alternative hierarchies. 3. Profiles
The PSJ logical database has two profiles. The database profile whosevalues are stored in table TCNDB determines the objects to be selectedfrom the database when you carry out a selection report. The PSJselection screen is set up based on the objects chosen for selection inthe profile. The profile for the project view whose values you can findin table TCNDS determines what the reporting structure will look like.
Note that the choices you make in the database profile have a majoreffect on system performance. Therefore, you should only choose thoseobjects which are absolutely necessary for the report. SAP provides youwith a tool for optimizing system performance. In the dialog box"Change DB profile temporarily", you will only be able to setindicators which are consistent with the GET events used in theselection report. 3.1 The Database Profile TCNDB
In Customizing ("Define profile for databaseselections") and using the function key "Change DB profile", you cancall up a screen in which you can adjust the database profile (TCNDB)to meet your own needs. In both cases, the screen looks the same(except for the field "DB profile") as shown below. The following showsthe field texts, variables, or indicator names which you can choose inthe database profile:
- Project view: TCNDB-DB_VIEW
Link to a project view profile defined in table TCNDS
- Maximum level: TCNDB-MAXLEVEL = "X"
Maximum hierarchy level in the reporting structure (RSTHIE); not to beconfused with the level of a WBS element
- Commercial evaluation: TCNDB-COREP = "X"
Commercial evaluation: that is, when networks and network activities/activity elements, only activities and activity elements are deliveredin the case of activity-assigned networks; for header-assignednetworks, the database returns only network headers. In the case ofvaluated project stock, the material components are arrangedhierarchically beneath the WBS element. For details on setting up thehierarchy, see chapters 2.2.1 and 2.3.1.
- Path upwards: TCNDB-PFAD_OBEN = "X"
All superior objects are included in the selection
- TCNDB-PFAD_OBEN = "X"
For example: if you choose a WBS element from level 2, but do notchoose a project definition (though TCNDB-PROJ = "X"), the databaseselects WBS elements above the WBS element you selected, along with theproject definition. Where there is valuated project stock, thisindicator is automatically set at blank.
- TCNDB-DB_VIEW
Reference to a project profile view stored in table TCNDS
- TCNDB-COREP = "X"
Commercial evaluation; i.e. when networks and networkactivities/activity elements are selected, only the activities andactivity elements with activity account assignment and the headers ofnetworks with header account assignment are taken into account inconstructing the hierarchy.
Origin of Data
- Archived data: TCNDB-SHOW_ARCH = "X"
Archived PS data is also be offered for selection.
- Version data: TCNDB-SHOW_VERS = "X"
Version data is also offered for selection.
- Standard structures: TCNDB-SHOW_STD = "X"
Standard structures are also offered for selection.
Selection Criteria
- Project definition: TCNDB-PROJ = "X"
Project definitions are selected.
- Sales documents: TCNDB-SDOR = "X"
Sales documents are selected.
- Component: TCNDB-KOMP = "X"
Material components are selected.
- TCNDB-KOMP = "X"
Components for activities/activity elements or planned orders areselected.
WBS Element Selection Criteria
- WBS element: TCNDB-PRPS = "X"
WBS elements are selected.
- Including hierarchy: TCNDB-NETZ = "X"
WBS elements are selected, with the subordinate hierarchy
- TCNDB-HIEKZ = "X"
Networks are selected, and in contrast to TCNDB-INCNP, even networkswhich are not assigned to a WBS element are selected.
- TCNDB-ACT = 'X'
Activities/activity elements are selected, and in contrast toTCNDB-INCNV, even network activities/activity elements which are notassigned to a WBS element are selected.
- TCNDB-PFAD_OBEN = 'X'
For example, if you specify a WBS element on level 2 but do not enter aproject definition (even though TCNDB-PROJ = 'X'), the system willselect all WBS elements above this element in the hierarchy as well asthe project definition from the database.
- TCNDB-HIEKZ = 'X'
If WBS elements can be selected and you enter a specific WBS element,the system selects the entire tree below this WBS element.
- With dynamic selections: TCNDB-HIE_DYN = "X"
Dynamic selections apply to all WBS elements in the hierarchy when youmake a selection including the hierarchy.
Network/Order Selection Criteria
- For WBS: TCNDB-NETZ_PSP = "X"
Networks and orders assigned to a WBS element are selected, providedthe assigned WBS element is also selected.
- Network: TCNDB-INCNT = "X"
Network headers assigned to a WBS element are selected.
- Production order: TCNDB-INCPP
Production orders assigned to a WBS element are selected.
- Other: TCNDB-NETZ = "X"
Networks and orders not assigned to a WBS element or whose WBS elementwas not included in the selection are selected here.
- PM order: TCNDB-INCIH = "X"
Plant maintenance orders are selected.
- CO order: TCNDB-INCCO = "X"
Controlling orders assigned to a WBS element are selected.
- Including subnetwork: TCNDB-INCTN = "X"
Subnetworks, order networks, and suborders are selected.
Activity Selection Criteria
- For WBS: TCNDB-ACT_PSP = "X"
Network activities and activity elements assigned to a WBS element areselected, provided the assigned WBS element is also selected.
- Activity/network: TCNDB-INCVG = "X"
Network activities assigned to a WBS element are selected.
- Activity/production order: TCNDB-INCPPVG = "X"
Activitis from production orders assigned to WBS element are selected.
- Miscellaneous: TCNDB-ACT = "X"
Activities and activity elements not assigned to a WBS element or whoseWBS elements are not selected are selected here.
- Activity/PM order: TCNDB-INCIHVG = "X"
Activities in PM orders assigned to a WBS element are selected.
- TCNDB-PLAF = 'X'
Planned orders are selected.
Other Selection Criteria
- Relationship view: TCNDB-AOBKZ = "X"
Relationships are selected.
- Capacity: TCNDB-KAPA = "X"
Capacity requirements for activities/activity elements are selected.
- TCNDB-CONF = "X"
Activity confirmations are selected.
- TCNDB-FHM = "X"
Production resources/tools for activities/activity elements areselected.
- TCNDB-MLST = "X"
Milestones for a WBS element or activity/activity element are selected.
- PS text/document: TCNDB-PSTX = "X"
PS texts for the WBS element or activity/activity element are selected.
- Purchasing: TCNDB-EBL = "X"
Purchasing documents are selected.
- Expenditure: TCNDB-COST = "X"
Cost, revenue, and finance data (cost collectors) are selected.
For more detailed information about the hierarchy structure, pleaserefer to 2.2.1 and 2.3.1.
- Subproject: TCNDB-SUBPRKZ = "X"
A subproject is offered for selection. As a result, the only WBSelements selected are those from a WBS which belong to the subprojectspecified in the selection screen for LDB PSJ. If you do not enter asubproject, all WBS elements are selected.
You can define the PDB parameters for the database profile in the userparameters.3.2 The Structure View Profile TCNDS
In Customizing, you can access the transaction for maintaining thedatabase profile (TCNDS) ("Specifyproject view") in which the project view is stored. Currently, thereare seven differenct views of a project that are stored in the valuetable for data element PS_HIERART. They are:
PS_HIERART =
1: Project structure
2: Profit center by group
3: Cost center by group
4: Characteristics hierarchy from classification
5: Capital investment program
6: Sales documents
7: Classification with single-level object list
99: Customer-defined
For profiles with PS_HIERART (field name: hierarchy type) = 1, 5, 6,you do not need any additional information. For hierarchy types 2 and3, you need to specify groups (TCNDS-HIENM) and for hierarchy types 4and 7 you should enter a summarization hierarchy (TCNDS-HIERID).
Here is a brief overview of the hierarchy structure:
- Hierarchy type 1 ("normal" structure view):
see 2.3.1
- Hierarchy types 2 and 3 (profit center view, cost center view):
The group you entered in TCNDS-HIENM is read. From the resultinghierarchy, only those nodes are displayed that have assignments toobjects in the selected project. The superior objects up to the topnode are displayed. Objects that are not assigned to a profit center ora cost center are placed in a hierarchy starting with level 0 andstructured according to the criteria in hierarchy type 1.
- Hierarchy type 4 (summarization view):
The characteristics of the summarization hierarchy entered inTCNDS-HIERID are read. As in hierachy types 2 and 3, only thosecharacteristics are displayed for which there are objects that havebeen summarized. The remaining objects are placed in a hierarchystarting with level 0 and according to the criteria of hierarchy type1.
- Hierarchy type 5 (capital investment program view):
The system reads the capital investment program items you enter on theselection screen. Orders and top WBS elements of a work breakdownstructure are associated with these items. When the hierarchy iscreated, only the WBS is included from the assigned investmentmeasures. The hierarchy below the capital investment item is createdaccording to the criteria for hierarchy type 1. Those objects which arenot below a WBS and which are assigned to an item are placed in thehierarchy starting with level 0 and structured according to thecriteria for hierarchy type 1.
- Hierarchy type 6 (sales view):
Sales document headers are displayed at level 0 and the associatedsales document items are displayed at level 1. On level 2, you find theWBS element items and their subordinate objects. The hierarchy isarranged according to the hierarchy type 1 criteria. Those objects thatare not subordinate in the hierarchy to such a WBS element arepositioned in the hierarchy starting with level 0 and structuredaccording to the criteria for hierarchy type 1.
Note the following special situation: A billing element is subordinateto another billing element in the WBS hierarchy and a sales documentitem points to this lower WBS element. In this case, the sub-treeassociated with this WBS element does not belong to the hierarchy ofthe superior WBS element.
|