Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_CMS_REL_TYP | Define Relationship Types |
Transaction Code | S_PLN_62000581 | (empty) |
Created on | 20040430 | |
Customizing Attributes | SIMG_CMS_REL_TYP | Define Relationship Types |
Customizing Activity | SIMG_CMS_REL_TYP | Define Relationship Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CMS_REL_TYP |
Use
In this IMG activity, you can define the relationship types that determine the logistics in a relationship. This data is then interpreted internally for executing collateral processes. For each of the relationship types, you must specify the following:
- Relationship category : It characterizes the features of the relationship between two collateral agreements.
Note: Normally, relationships can be either be one-way or reversible. Collateral Management supports only one-way relationships. Further, you can only define a relationship for a portion of a collateral agreement, to another collateral agreement. You cannot define relationships between two whole collateral agreements.
For example, you can define a relationship such that a collateral agreement portion is a member of a collateral pool. However, you cannot define a relationship wherein a collateral pool is a member of a collateral agreement portion.
The relationship can be either of the two relationship categories
000001 - Collateral pools
000002 - Backups
- Cardinality : The cardinality (n : m) describes the relationship with respect to the number of possible source-to-destination collateral agreements in a relationship.
- Source cardinality : It is the cardinality (m) as viewed from the source. It (m) is the number of destination collateral agreements that can be assigned to the source in this relationship. You can provide a text description for the source.
- Destination cardinality : It is the cardinality (n) as viewed from the destination. It (n) is the number of source collateral agreements that can be assigned to the destination collateral agreement. You can provide a text description for the destination.
Note: The cardinality value set to zero (0) means that infinite number of relationships are possible for the relationship type.
- Calculation type: You can choose from the two calculation types provided in the standard system, namely the Pool/Member and Backup/Backed up. Appropriate calculation scenarios are defined for the above scenarios. The relationship details are used internally to select the relevant calculation sequence.
Requirements
Standard settings
Activities
- Determine the combinations of source and target collateral agreement types for which relationships are possible.
- Check the delivered relationship types and change if necessary.
- If necessary, define new relationship types.
Example
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CMS_REL_TYP | 0 | ALN0000074 | Collateral Agreement |
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 |
V_TCMS_REL_TYP | V - View | SM30 |
History
Last changed by/on | SAP | 20040501 |
SAP Release Created in | 500 |