6 OBELCM Integration with Corporate DDA

Note:

Prerequisites:
  • Maintain the external source system (Corporate DDA) in common core in the following screen:
    • Core Maintenance -> ECA System -> Create ECA System
  • Update the Accounting System as ‘OBA’ and GL systems as‘FCUBS’ / any other GL system name (code) in the plato configuration properties under the key “host.mnt” by concatenating the system names with Host using tilde (~) ex: HOST1~OBA~FCUBS ~…. Etc.
  • Maintain the source system configuration for FCUBS and OBA in the plato configuration properties under the key “source.systems”. For a source system, maintain the config as <source system>~<service Type>~<external user Id>~<accounting entry>~<inter system bridge GL>.
  • Based on whether it is a cloud environment or not GL system will change. For cloud environment, GL system will be OBOL and for non-cloud environment, it will be FCUBS. This Plato configuration property is under the key “environment”.
  • GL system for cloud environment to be maintained under the key “cloud.gl.system” in the format <gl system>~<user id>. The handoff service name for MIS to be maintained under the key “cloud.mis.handoff.service”.
  • Accounting entry can be maintained as Single or Double – as S or D. if Double selected then specify the Inter System Bridge GL.
  • For example: For OBA, for a single accounting entry, config can be maintained as follows: OBA~REST~OBCDA_ID~S~~. For a double entry, config can be maintained as OBA~REST~OBCDA_ID~D~10011013~, where the Inter System Bridge GL is specified for this entry.
  • Configure External System Maintenance for OBA in Interconnect -> Routing Hub -> Service Consumers.
  • Configure a consumer service (CONSUMER_SERVICE_OBA_ACCHANDOFF_OBMA) for the maintained service provider (OBA_ACC_HOFF_OBMA) and choose the relevant service to be consumed.

    Figure 6-4 Service Consumers


    Description of Figure 6-4 follows
    Description of "Figure 6-4 Service Consumers"

    Figure 6-5 Service Consumer


    Description of Figure 6-5 follows
    Description of "Figure 6-5 Service Consumer"

    Figure 6-6 Service Consumer


    Description of Figure 6-6 follows
    Description of "Figure 6-6 Service Consumer"

  • Update the Source Branch Code (same branch in OB Enterprise Limits and Collateral Management and OBA) and Source System (OBA) in Branch Core Parameter Maintenance in Core Maintenance -> External Branch Parameters -> Create External Branch Parameters.
  • Maintain Source System as OBA in Customer Maintenance in the Core Maintenance -> External Customer -> Create External Customer
  • Maintain account details in Customer Account Maintenance in the Core Maintenance -> External Customer Account -> Create External Customer Account.
    • Same account number must be created in OBA.
    • External Credit Approval System must be opted as the OBA.
  • Maintain the Handoff service consumer configuration for OBA in the plato configuration properties under the key “handoff.consumer.service”. For any other source, configuration can be maintained with tilde separated values. Ex: CONSUMER_SERVICE_OBA_ACCHANDOFF_OBMA
Configure External System Maintenance for OBOL in Interconnect -> Routing Hub -> Service Consumers
Consumer Service Description:

Table 6-1 Consumer Service

Consumer Service Description
CONSUMER_SERVICE_OBA_ACCHANDOFF_OBMA Usage:

Service: : /obcdda-pp-transaction-balance-service/service/v14.8.1.0.0/transactions/accountings

Operation: createAccounting
In case of Corporate DDA without separate bridge GL for source systems - Single accounting entry:
  • For all transactions (fees) in OB Enterprise Limits and Collateral Management, only one leg of accounting entry (customer account related) will be handed over to the Corporate DDA system
  • The other leg of transaction (fee GL) will be sent to GL system

Table 6-2 ACCOUNTING ENTRY - SINGLE (WITHOUT BRIDGE GL) for ADVANCE/ARREARS FEE - FLIQ AND FACR

ACCOUNTING ENTRY - SINGLE (WITHOUT BRIDGE GL) for ADVANCE/ARREARS FEE - FLIQ AND FACR
FEE TYPE FLIQ FACR
DR CR DR CR
ADVANCE FEE CUSTOMER RECEIVED IN ADVANCE RECEIVED IN ADVANCE INCOME GL
HANDOFF TO CORP DDA GL SYSTEM GL SYSTEM GL SYSTEM
ARREARS FEE CUSTOMER RECEIVABLE GL RECEIVABLE GL INCOME GL
HANDOFF TO CORP DDA GL SYSTEM GL SYSTEM GL SYSTEM
In case of Corporate DDA with separate bridge GL for each source system - Double accounting entries:
  • For all transactions in OB Enterprise Limits and Collateral Management (fees), first pair of entry (customer account + Bridge GL) will be handed over to the Corporate DDA system
  • The second pair of entries (Bridge GL + fee GL) will be handed over to the GL system

Table 6-3 ACCOUNTING ENTRY - DOUBLE (WITH BRIDGE GL) for ADVANCE/ARREARS FEE - FLIQ AND FACR

ACCOUNTING ENTRY - DOUBLE (WITH BRIDGE GL) for ADVANCE/ARREARS FEE - FLIQ AND FACR
FEE TYPE FLIQ - PAIR 1 FLIQ - PAIR 2 FACR
DR CR DR CR DR CR
ADVANCE FEE CUSTOMER BRIDGE GL BRIDGE GL RECEIVED IN ADVANCE RECEIVED IN ADVANCE INCOME GL
HANDOFF TO CORP DDA CORP DDA GL SYSTEM GL SYSTEM GL SYSTEM GL SYSTEM
ARREARS FEE CUSTOMER BRIDGE GL BRIDGE GL RECEIVABLE GL RECEIVABLE GL INCOME GL
HANDOFF TO CORP DDA CORP DDA GL SYSTEM GL SYSTEM GL SYSTEM GL SYSTEM

Note:

All transaction in OBELCM can be viewed in daily_log_ac tables - OBELCM_PP_TB_LM_DAILY_LOG_AC (facility) and OBELCM_PP_TBS_CL_DAILY_LOG_AC (collateral).
  • The above table has a column CUST_GL with values as A (Accounting System) and G (GL system).
  • Handoff to respective systems (DDA and GL) happens based on selected accounting entry (Single/Double) and value in above column.