2.12 Customer to Liability Link Maintenance

This topic describes about the procedure to maintain customer to liability link.

Note:

The fields, which are marked with an asterisk, are mandatory.

Multiple customers can be linked to a liability. Also one customer can be linked to multiple liabilities. First time linkage of a customer to a liability will be through GEDCULIK which will be updated as default linkage in linked customers sub-system of liability maintenance and any subsequent linkage to other liabilities has to be done through linked customers sub-system.

1. On the Home screen, specify GEDCULIK in the text box and click the icon.
   The Customer to Liability Link Maintenance screen displays.

   Figure 2-38 Customer to Liability Link Maintenance

   
   

   
   Description of "Figure 2-38 Customer to Liability Link Maintenance"

   
   
2. On Customer to Liability Link Maintenance screen, click New and specify the fields.
   For more information on fields, refer to the field description table.

   Table 2-34 Customer to Liability Link Maintenance - Field Description

   Field	Description
   Branch Code	The branch code of the branch in which the customer to liability link maintenance is done gets defaulted.
   Customer No	Click the icon and select the customer number to which the liability has to be linked.
   Customer Name	This field is automatically populated based on the selected customer number.
   Liability No	Click the icon and select the number of the liability to be linked to the customer.
   Liability Name	This field is automatically populated based on the liability number.
   Issuer
   Customer Exposures	Specify different Exposure Types for the customer.
   Exposure Type	The exposure type for the exposure, as maintained in the Track Exposure Maintenance screen gets defaulted here based on the Exposure Name selected.
   Exposure Type Code	The exposure type code to which the selected exposure type belongs gets defaulted.
   Exposure Name	Select the required exposure name. The exposure codes maintained in the Track Exposure Maintenance and Bulk Track Exposure Input screen are listed in the list of values.
   Exposure Description	The description for the exposure, as maintained in the Track Exposure Maintenance screen gets defaulted here based on the Exposure Name selected.
   Customer Common Attributes	Specify the customer common attribute for the customer.
   Attribute Code	Select the required attribute code from the list of values maintained in GEDTRKMT.
   Attribute Type Code	This code gets defaulted based on attribute code selection.
   Attribute Value	Select the required attribute value from the list of values maintained in GEDTRKMT.
   Attribute Description	The description provided in GEDTRKMT for the selected attribute value gets defaulted.

   Note:

   • The Customer to Liability Link Maintenance is mandatory, when limits tracking are required under any of the Oracle FLEXCUBE modules.
   • In the Customer Exposures section, the Exposure Name LOV displays the exposures having utilization type as Customer maintained in the Track Exposure Maintenance (GEDTREXP) screen.
   • The Customer to Liability Link Maintenance is mandatory, when account for the customer is created using account class, for which limit check flag is set as Y at preference sub-system screen.
   • When account for the customer is created without maintaining liability and later the liability is created and linked to the customer, the Limits tracking option at the customer level would be automatically selected by the system.
   • We recommend you to use the Common Attribute Bulk Maintenance screen (GEDTRKMT) for any exposure related activities.

   Note:

   In case of granular access, link customers to liabilities details maintained for allowed list of customers are allowed to view, query, modify, authorize, re-open, copy, delete, and so on based on the user/users preferences selected in Access Group Restriction tab available in the User Maintenance screen. For more information, refer to Common Core - Security Management System User Guide.
3. Click Save to save the record.

• Change Log
  The topic describes about the detailed information on the change log details.