Last updated on JULY 25, 2017
Applies to:Oracle Trade Management - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.5 version, All Others
When we run Auto-Pay program to automatically summarize Utilizations for a period and create a Claim, the OZF_CLAIM_LINES_UTIL_ALL.UTIL_CURR_AMOUNT is being set to a value that is different than the corresponding OZF_FUNDS_UTILIZED_ALL_B.AMOUNT. This is causing the OZF_FUNDS_UTILIZED_ALL_B.AMOUNT_REMAINING to be assigned the difference allowing the Utilization to be open to be included in future claims. If we are running Auto-Pay to automatically create Claims for the full Utilization the OZF_FUNDS_UTILIZED_ALL_B.AMOUNT_REMAINING should be zero.
During the Funds Accrual Engine program to create the Utilizations originally the GL Date, Adjustment Date, and FX rate date are all set to System Date. We have business requirements to set the GL Date, Adjustment Date and FX rate date differently for business processing and accounting purposes. We are intercepting this after the initial Funds Accrual Engine run and updating those dates as well as re-calculating the fx conversion if any are needed on the OZF_FUNDS_UTILIZED_ALL_B table.
We need some assistance in determining the logic for how the OZF_CLAIM_LINES_UTIL_ALL.UTIL_CURR_AMOUNT is being calculated and assigned as that seems to be at the root of how the OZF_FUNDS_UTILIZED_ALL_B. AMOUNT_REMAINING is being assigned (as the difference between the OZF_FUNDS_UTILIZED_ALL_B.AMOUNT and the OZF_CLAIM_LINES_ALL.UTIL_CURR_AMOUNT).
The issue can be reproduced at will with the following steps:
1. Login as Trade Management responsibility
2. Ran the Auto-Pay program
3. AMOUNT_REMAINING is not zero for some claims
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms