3.4 FLEXCUBE Host Integration Troubleshooting

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

Host Calls Failure

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.
      The Service Consumers screen displays.

      Figure 3-23 Service Consumers


      Description of Figure 3-23 follows
      Description of "Figure 3-23 Service Consumers"

    3. On the Service Consumers, Click RPM_ORIGINATION tile.
      The RPM_ORIGINATION screen displays.

      Figure 3-24 RPM_ORIGINATION


      Description of Figure 3-24 follows
      Description of "Figure 3-24 RPM_ORIGINATION"

    4. On the RPM_ORIGINATION screen, click the Service Provider tab.
      The Service Provider tab displays.

      Figure 3-25 Service Provider


      Description of Figure 3-25 follows
      Description of "Figure 3-25 Service Provider"

    5. On the Service Provider tab, click the FCUBS tile.

      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.
      The FCUBS screen displays.

      Figure 3-26 Oracle FLEXCUBE Universal Banking


      Description of Figure 3-26 follows
      Description of "Figure 3-26 Oracle FLEXCUBE Universal Banking"

    6. From the Actions, click on Request Audit.
      The Request Audit screen displays.

      Figure 3-27 Request Audit


      Description of Figure 3-27 follows
      Description of "Figure 3-27 Request Audit"

    7. Check the most recent transformation on which the operation was performed.
    8. Click on the Request ID and check the Provider Response to check for any errors.
      The Request Audit details screen displays.

      Figure 3-28 Request Audit details


      Description of Figure 3-28 follows
      Description of "Figure 3-28 Request Audit details"

  2. If there is no Oracle Banking Routing Hub call, yet the host call is failing (especially during Account Creation), the failure may be at the workflow task level. To debug this scenario, follow the steps below.
    1. Using the Application Number, call the plato-orch-service search API (API details given below) using Postman.

      Table 3-1 API details

      API components Description
      API URL http://whf00dtm.in.example.com:7011/plato-orch-service/api/v1/extn/custom-actions/queries/tasks?offset=0&limit=100
      Body Refer to the image below.
      Headers

      • Content-Type: application/json

      • userId:

      • appId: platoorch

      • branchCode:

      • entityId: DEFAULTENTITY

      The search result displays.

      Figure 3-29 Request Body


      This figure displays the Body.

    2. From the response, search for subWorkflowId.
      The search result displays.

      Figure 3-30 subWorkflowId


      This figure displays the subWorkflowId

    3. Use this subWorkflowId as parameter in the below API.

      Table 3-2 API details

      API components Description
      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

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

Parent topic: Troubleshooting Application Workflows