1. FCUBS-OBPM Integration Setup Guide
  2. Integration Guide
  3. FAQ

FAQ

This section describes the FAQ’s for the scenarios noticed on accounting handoff between Oracle Banking Payments & Oracle FLEXCUBE Universal Banking systems, on the Co-deployed set-up.

  1. Accounting handoff is in Pending status:

    OBPM isn’t able to post the accounting entries to UBS accounting jms queue. If in the PM debugs, shows failed to initialize jndi factory, check the following in PMSSYSPM –System parameters:

    - PM.CTX.FACTORY - weblogic.jndi.WLInitialContextFactory

    - PM_CTX_PROVIDER – Provider URL** of the app server

    1. ** Provider URL will be the http URL of the app URL. E.g.: if Application URLis https://hostname:9011/FCJNeoWeb/ , then provider URL will bet3://hostname:9010
    2. In PMDQPROF screen – Q profile – Specify the correct Initial factory &provider URL (same as above). QCF should be MDBQCF. Ensure this MBDQCF is configured in WebLogic.
    3. Update the Provider URL in Pmtm_job_param & pmtm_system_parameterstables.
    4. Do restart the application after the above changes.
  2. Accounting handoff is in Requested status:

    The accounting is passed successfully by OBPM, but response from UBS system is not received yet.

    1. Check the MDB settings as indicated above & MDB gateway log.
    2. Check gwtm_in_log & gwtm_out_log tables for the exception details & message CLOB. The correlation ID in the accounting request XML of the transaction will be key between the two systems.
  3. Accounting handoff is in Rejected status:

    Accounting entries handed off by OBPM has been rejected by UBS.

    1. In OBPM application front end, go to the view transaction (PXDOVIEW /PBDOVIEW/ PADOVIEW), query the transaction. Click on View Q action. In Queue action log the sub screen, selecting the Accounting Response row, Click View response. Check the error & take corrective action as below:
    2. If error is “No data found for source combination”  Maintain in GWDETFUN a record for source code FCUBS & CreateExtAccEcaEntries (NEW) combination.
    3. If error is “User doesn’t have rights to perform operation”  Maintain in SMDUSRDF, for SYSTEM user, add roles for the respective branch.
    4. Additionally, ensure the below maintenance are done:
      • Maintain Source as FCUBS in CODSORCE
      • Maintain Source Preference for FCUBS Source and IF Module in CODUPLDM
      • Set Correlation pattern in GWDETSYS as Correlation ID. Not Message ID.

Relevant debugs to be analyzed:

MDB_Kernel11.1_gwlog _<Date>.log : GW MDB Log

SYSTEM<Branchcode>: Db Dbg

Parent topic: Integration Guide