Public API IBY_FNDCPT_SETUP_PUB.CREATE_DEBIT_AUTHORIZATION () Does Not Set DIRECT_DEBIT_COUNT To 0
(Doc ID 1638446.1)
Last updated on APRIL 25, 2023
Applies to:
Oracle Payments - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When using API
IBY_FNDCPT_SETUP_PUB.CREATE_DEBIT_AUTHORIZATION (
P_API_VERSION => l_API_VERSION,
P_INIT_MSG_LIST => l_INIT_MSG_LIST,
P_COMMIT => l_COMMIT,
P_DEBIT_AUTH_REC => l_DEBIT_AUTH_REC,
P_PAYER => l_PAYER,
X_DEBIT_AUTH_ID => X_DEBIT_AUTH_ID,
X_RETURN_STATUS => X_RETURN_STATUS,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
X_RESPONSE => X_RESPONSE);
Even when initializing the parameters DIRECT_DEBIT_COUNT with an explicit value like the following:
l_DEBIT_AUTH_REC.DIRECT_DEBIT_COUNT := '0';
Find that Debit authorization is created and usable from applications but DIRECT_DEBIT_COUNT is set to "null".
EXPECTED BEHAVIOR
-----------------------
Expect the DIRECT_DEBIT_COUNT field to be initialized with a numeric value (0) instead of NULL.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Call API IBY_FNDCPT_SETUP_PUB.CREATE_DEBIT_AUTHORIZATION ()
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 |