1. Troubleshooting Guide
  2. Troubleshooting Application Workflows
  3. FLEXCUBE Host Integration Troubleshooting

FLEXCUBE Host Integration Troubleshooting

This topic describes the possible issues that may occur in FLEXCUBE Universal Banking Solution integration.

The possible issues and causes are described in the following subsections:

Host Calls Failing

Host call failure may be due to various reasons ranging from improper Oracle Banking Routing Hub configuration to absence of maintenance in the Oracle FLEXCUBE Universal Banking environment. Host call may fail during Business Product Host Product listing, Interest or Charge Details data-segment fetch or during Oracle FLEXCUBE Universal Banking Account creation time.

To find the root issue, follow the below steps:

  1. Check Oracle Banking Routing Hub Audit Request to see if any Oracle Banking Routing Hub calls to Oracle FLEXCUBE Universal Banking Module has failed.
    1. On Home screen, click Core Maintenance. Under Core Maintenance, click Routing.
    2. Under Routing, click Service Consumers. Under Service Consumers, Click RPM_ORIGINATION.
    3. Under RPM_ORIGINATION, click FCUBS.

      Note:

      If you do not find any Oracle Banking Routing Hub configuration for Oracle FLEXCUBE Universal Banking, that means, the Oracle Banking Routing Hub configurations are not fully imported. Import the Oracle Banking Routing Hub configuration available in the source folder.
    4. From the Actions, click on Request Audit.

      Figure 3-12 Service Consumer


      This figure displays the Service Consumer.

    5. Check the latest Transformation for which you have performed the operation.

      Figure 3-13 Request Audit


      This figure displays the Request Audit.

    6. Click on the Request ID and check the Provider Response to check for any errors.
  2. If there is no Oracle Banking Routing Hub call but, still Host call is failing (especially for Account Creation), then failure might be in the workflow task level. In order to debug this scenario, follow the below steps:
    1. Using the Application Number, call the plato-orch-service search API (API details given below) using Postman.
      API Url: http://whf00dtm.in.example.com:7011/plato-orch-service/api/v1/extn/custom-actions/queries/tasks?offset=0&limit=100

      Figure 3-14 Body


      This figure displays the Body.

      Headers:

      Content-Type:application/json

      userId:

      appId:platoorch

      branchCode:

      entityId:DEFAULTENTITY

    2. From the response, search for subWorkflowId.

      Figure 3-15 subWorkflowId


      This figure displays the subWorkflowId

    3. Use this subWorkflowId as parameter in the below API.
      API Url: http://whf00dtm.in.example.com:7011/plato-orch-service/api/workflow/ad194dd5-738f-4ce3-b9b9-2a9f72bb59c6

      Headers:

      Content-Type:application/json

      userId:

      appId:platoorch

      branchCode:

      entityId: DEFAULTENTITY

    4. The response shows the actual error for HTTP task to fail.

Parent topic: Troubleshooting Application Workflows