My Oracle Support Banner

OBDX USING PAYMENT WEBSERVICE TO FETCH DATE FOR FUNCTIONS OTHER THAN PAYMENTS (Doc ID 2517531.1)

Last updated on OCTOBER 16, 2019

Applies to:

Oracle Banking Digital Experience - Version 18.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 18.2.0.0.0 version, Implementation Support

When integrating with OBPM, OBDX uses below service for all date related functions
http://ip:port/PMWeb/FetchDateService?wsdl

After Flexcube EOD , this service does not return the next working date. While this works correctly for payments transactions, other transactions like Limits etc. use wrong date.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Flexcube EOD is executed say at 6pm and branch date becomes next working date.
2. User logs in to OBDx Application and does a transaction at 7pm.
3. OBDX will send correctly payment date as today.
4. Same service is used for other date related maintenance (like limits etc) within OBDX which expect this service to return current branch date after EOD.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.