Relationships
Client Relationship is a direct association of two Clients outside of any prerequisite context. Either Client in the Relationship may be a Group Customer or non-Group Customer (e.g. company, individual, trustee, etc.) Client.
A client (Group Customer or non-Group Customer) can have an unlimited number of primary and secondary relationships. The relationships of the given primary relationship type with the current customer (Group Customer or non-Group Customer) can have one or several secondary relationship types. The Relationship screen in OIPA provides the user with the capability to add and update relationships and their associated information during case implementation. Configuration for the Relationship screen can set a maximum number of relationship by using the <Maximum> attribute in the ClientRelationshipScreen business rule.
The ClientRelationship screen gets displayed in two modes from the one business rule configured under ClientRelationshipScreen BR - 1. Group Customer Relationship: when used in group customer context, the security set up for this screen would be done through the GroupCustomerRelationship node and 2. Client Relationship: When used in an non-Group Customer context, the security set up for this screen would be done through the ClientRelationship node.
Configuration Required for Relationships
There are three steps involved in configuring relationships. First, the AsCode table needs to contain the primary and secondary relationship types. Next, the ClientRelationshipScreen business rule must be configured to control the Relationship screen in OIPA. And finally, transactions must be configured to allow changes to be made to relationships in OIPA.
AsCode Table
Relationship types are defined in the AsCode table. Both primary and secondary relationships must be defined.
- AsCodePrimaryRelationshipType: The primary relationship types are defined here. These types will be available to the user when a new primary relationship is created in OIPA.
- AsCodeSecondaryRelationshipType: The secondary relationship types are defined here. These types will be available to the user when a secondary relationship is created in OIPA.
- AsCodeChangeStatus: The system codes that define the record status of the relationship.
- • AsCodeBusinessStatus: The system codes that define the business status of the relationship. This is applicable only if the UseBusinessStatus element is set to Yes in the ClientRelationshipScreen business rule.
Client types are also referenced in the ClientRelationshipScreen business rule, so values must exist for the AsCodeClientType code name. The codes are referenced in the business rule to identify the client types that can be assigned a secondary relationship.
Business Rules
The Relationship screen is controlled by the ClientRelationshipScreen business rule. This business rule identifies the primary relationship types that are allowed and the secondary relationships that can be created with each primary relationship type. It also defines the client types that can be assigned a secondary relationship. The <Maximum> element in this rule can set a maximum number of primary and secondary relationships. This rule also defines the activity that needs to be spawned when a client relationship time slice is submitted. The transaction can either be defined at each PrimaryRelationship level or at the ClientRelationship level. The ClientRelationship spawn configuration will be used, by default, if no specific spawn configuration exists at PrimaryRelationship level.
Transactions
The transaction(s) that will be spawned when a client relationship time slice will need to be defined under the Customer Activity Plan relating to the Group Customer and to the Client Activity Plan relating to the non-Group Customer Client. The type code of the activity should be 26 - Client-RelationshipScreenUpdate.
DataBase Tables
The following database tables hold the relationship information.
AsClientRelationship: Stores the data and values for the connection between two clients.
AsClientRelationshipField: Stores the data and values for the field names related to Client Relationship details and characteristics.
Copyright © 2009, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices