SAP ABAP IMG Activity SIMG_TICL069 (Define Structure of Own Defined Navigation Tree)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_BASIS (Package) FS-CM: General Functionality
IMG Activity
ID SIMG_TICL069 Define Structure of Own Defined Navigation Tree  
Transaction Code S_KK4_08000549   (empty) 
Created on 20021129    
Customizing Attributes SIMG_TICL069   Enhance Structure of Navigation Tree 
Customizing Activity SIMG_TICL069   Enhance Structure of Navigation Tree 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _TICL069    

Use

In this IMG activity you can define the structure of navigation tree types that you have defined yourself.

This is necessary, for example, if you want to enhance the navigation trees delivered by SAP to include own nodes. In this case, copy the navigation tree delivered by SAP to your namespace and change it to suit your requirements.

Consider the following when setting up the navigation tree:

  • Each navigation tree must have exactly one root node. The special characteristic of a root node is that it does not have any parent node. SAP delivers node category 0 as the root node.
  • You can append other subnodes under each node. You can assign a node to just one parent node.
  • You use the position number to determine the sequence of the nodes. Nodes with a lower position number appear before nodes with a higher position number.

    You do not have to assign the position numbers sequentially. On the contrary, we recommend that you assign position numbers with gaps so that when you add new nodes at a later stage, you do not have to reassign all the position numbers.

Requirements

You have created your own navigation tree type in IMG activity Enhance Navigation Tree Types.

If you want to use own node categories, you must have already defined these in IMG activity Enhance Node Categories of Navigation Tree.

Standard settings

This table contains entries that are used by the programs in the Claims Management component. Changing or deleting entries supplied by SAP constitutes a modification to the program. Such modifications are generally not necessary and should be avoided, as they can lead to errors.

You can create new entries in the customer namespace (identifier begins with "Y" or "Z"). These usually only have an effect on the component if you program using these values in the corresponding extensions of the program.

Activities

Example

0 Root node

|_ Node 1, parent node is the root node, position number 5

|_ Node 2, parent node is the root node, position number 10

|_ Node 3, parent node is node 2, position number 1

Description of example:

  • The root node has node category 0. No parent node has been defined.
  • The two nodes 1 and 2 are subnodes of the root node, node 3 is a subnode of node 2.
  • You can assign a node to just one parent node. This means that in the above example it is not possible to append a node under both node 1 and node 3.

    If you really want to assign a node to several parent nodes, you must create several node categories to be able to do so. For some nodes SAP therefore delivers two entries, such as H5 for Invoice in Subclaim and H9 for Invoice in Header.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
M_TICL069 V - View SM30  
History
Last changed by/on SAP  20021202 
SAP Release Created in 471