2.1 ECA System Maintenance

  1. Create Source System in the STDECAMT screen for OBA (Oracle Banking Accounts).

    Figure 2-1 ECA System Maintenance


    Description of Figure 2-1 follows
    Description of "Figure 2-1 ECA System Maintenance"

  2. Map the ECA system ‘OBA’ in the PMDECAMT screen.
  3. Maintain External Credit Approval System in the PMDECAMT screen.

    Figure 2-2 External Credit Approval System Detailed


    Description of Figure 2-2 follows
    Description of "Figure 2-2 External Credit Approval System Detailed"

  4. Maintain ECA System with system class as OBA Communication Type should be ReST & Communication Method as Synchronous.

    Maintain header profile in MSDHPROF & to be mapped.

    Maintain service profile in PMDSPROF & to be mapped.

    Rest URL should point to OBA where the ECA block will be done or should be routed to the OBRH system.

  5. Maintain the Service Profile in the MSDHPROF screen.

    Figure 2-3 HTTP Header Parameters


    Description of Figure 2-3 follows
    Description of "Figure 2-3 HTTP Header Parameters"

  6. Profile Name should be mapped with PMDECAMT Header Profile. Request method is POST.

    Header attributes like Content-Type, SERVICE-CONSUMER, SERVICE-CONSUMER-SERVICE, appId, branchCode, entityId & userId values should be mapped based on OBRH System configuration for OBA. Same can be mapped in Service profile.

  7. Maintain the Service Profile in PMDSPROF screen.
  8. Service Type should be ‘ReST’ and Service Profile ID should be mapped with PMDECAMT.

    OBPM build the ECA request with details and post to OBA System via OBRH and call the ECA block process to create ECA block. Once the process is completed, the OBA system posts the response to OBPM.

    Following ReST end point used by OBPM to post into OBA for amount block.

    <host><port>/obcdda-pp-transaction-balance-service/ob/oba/tbs/v1/transactions/amountBlocks

Parent topic: Maintenance to be done in Oracle Banking Payments (OBPM)