Ansicht
Dokumentation

GRFN_MAINORGHIER - Maintain Organizational Hierarchy Relationships

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

In this Customizing activity, you can maintain the HR relationships used for organzation views, and then assign the organization views to relevant components. This process consists of the following activities:

1. Maintain Relationship Types
2. Maintain Relationship Subtypes
3. Maintain Organization View Configurations

To maintain the relationship types, do the following:

1. Select Maintain Relationship Typesand choose the Choosepushbutton.
2. Choose the New Entries pushbutton, and select a three-character assignment type. You are not permitted to create new relationship types in the SAP Namespace.
3. Double click the Allowed Relationships node in the left navigation pane.
4. Choose the New Entries pushbutton, and create the following new entries in the table:

Obj.	A/B	Rel	RelObjType
O	A	*** (3-char no.)	O
O	B	*** (3-char no.)	O

1. Save the data and exit the activity.
2. Select Maintain Relationship Subtypes,and then choose the Choosepushbutton.
3. Choose the New Entriespushbutton, and create the following new entries:

Infotype	Infotype Name	Subtype	Subtype Text
1001	Relationships	A*** (3-char no.)
1001	Relationships	B*** (3-char no.)

1. Save the data and exit the activity.
2. Select Maintain Relationship Typesand choose the Choosepushbutton.
3. Select the node Time Constraintson the left navigation pane and choose the New Entriespushbutton.
4. Create the following entries:

• ,,Object Type = O

• ,,Infotype = 1001

• ,,Subtype = A***

• ,,Time constraint = 2

• ,,Object Type = O

• ,,Infotype = 1001

• ,,Subtype = B***

• ,,Time constraint = 3

1. Save the data and exit the activity.
2. Select Maintain Organization View Configurations, where you can maintain the settings for the newly customized relationship type.

Note: The available views can be used by different components in different ways. A single view can act as either the default view, or can be the available view for none, one, or multiple components. Furthermore, each component can have one default view and multiple available views. A view that is available to a component but is not the default view for the component, is only used for hierarchical organizaion display and reporting purposes.

Relationships

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4576 Date: 20240523 Time: 184656     sap01-206 ( 43 ms )