Kontakt

Ansicht
Dokumentation

LCM_VRELCONFIG - Define Relationship Types, Relationships, and Use Cases

LCM_VRELCONFIG - Define Relationship Types, Relationships, and Use Cases

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Define relationships, relationship types and use cases for defined relations for legal contexts and legal transactions.

In this configuration activity, you define the following settings to define relationship among legal transactions in Manage Contexts and Manage Legal Transactions applications:

Relationship Types: Here you can define the type of relationship between the legal transactions. If you have, for example, a legal transaction for a new purchasing contract for Spain, this legal transaction can have a relationship (type Related To) with several other legal transactions that cover the single documents belonging to the purchasing contract. You can select a type of relationship based on your business requirement. The type of relationship you select determines the direction of the relationship. The following are the directions to a relationship:

  • Neutral to Neutral: The influence and dependency between the two transactions that are in a relationship is equipotential.
  • Strong to Weak: The strong legal transaction has an influence on or is leading the other legal transaction (weak) that is dependent on the strong legal transaction in one way or another.
  • Weak to Strong: The weak legal transaction is related to the strong legal transaction but does not have any influence on the strong legal transaction.
Pairs of Relationships Direction
Parent of Child to Strong-Weak
Prerequisite for Dependent of Strong-Weak
Amendment to Amended by Strong-Weak
Replacement to Replaced by Strong-Weak
Child to Parent of Weak-Strong
Dependent of Prerequisite for Weak-Strong
Amended by Amendment to Weak-Strong
Replaced by Replacement to Weak-Strong

In a neutral relationship, there is no hierarchy between the related legal transactions. Both the legal transactions are equally strong.

Status Synchronization: Once a relationship is established between two transactions, any change to the status of one transaction affects the status of the related transactions. This process is called Status Synchronization. For example, if the health of the legal transaction for Master Agreement is changed to 'Terminated', all the related legal transactions for purchase orders are set to the same status. Whenever there is a change in status, the system sends a notification to the concerned team members monitoring the strong transactions and its related transactions. If configured, the team member monitoring neutral transactions will also receive notification when the status is synchronized. Note that status synchronization is processed only if the relationship use case for status synchronization has been enabled.

Relationship: Here you can define the relationship between the relationship types. For example, you can specify if the relationship is a forward relationship type or a reverse relationship type.

Use Cases for Defined Relations: Relationships are defined based on the configuration setting - Relationship Use Case. For example, the Health Synchronization use case is readily available and hence you can trigger the health synchronization of related legal transactions. Similarly, use case for showing the document links for related mandatory documents has been provided. Configuring this use case enables you to see all the mandatory documents of the related legal transactions.

Weak-Strong

Weak-Strong

Weak-Strong
  1. Define Relationship Types.
    1. Enter a Relationship Type.
    2. Select the direction of the Relationship from the dropdown for each Relationship Type.
    3. Enter a meaningful description in the Long Textfield.
  2. Define Relationship
    1. Enter the Relationshipname.
    2. Select a Forward Relationship Typeby selecting a relation type using value help.
    3. Select a Reverse Relationship Typeby selecting a relation type using value help.
    4. Enter a meaningful description in the Long Textfield.
  3. Define Use Cases for Relationships
    1. Select Relationship name from the value help.
    2. Select Use Case for relationship from the value help.
Weak-Strong






BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 6394 Date: 20240523 Time: 193009     sap01-206 ( 96 ms )