IBY_FNDCPT_TRXN_PUB.CREATE_TRANSACTION_EXTENSION Does Not Create Extension When Dummy Parameters Are Passed
(Doc ID 2072128.1)
Last updated on FEBRUARY 20, 2018
Applies to:Oracle Payments - Version 12.1.3 and later
Information in this document applies to any platform.
We are using IBY_FNDCPT_TRXN_PUB.CREATE_TRANSACTION_EXTENSION to create an authorization.
We are creating a credit card authorized without it being tied to an actual transaction (like an order, invoice).
We have put dummy information into the API:
l_TrxnExtension_rec_type.Originating_Application_Id := 673;
l_TrxnExtension_rec_type.Order_Id := 12345; -- this is not validated but must be entered a unique number
l_TrxnExtension_rec_type.Trxn_Ref_Number1 := 'RECEIPT';
l_TrxnExtension_rec_type.Trxn_Ref_Number2 := '12345';
l_TrxnExtension_rec_type.Instrument_Security_Code := 123;
The issue is that no row is being inserted into the IBY_FNDCPT_TX_EXTENSIONS table for this authorization.
We are expecting a row to be inserted into the table.
The Extension_Valid is returning false making the response code to be set to G_RC_INVALID_EXTENSION_ATTRIB. However, later it is again set to
x_response.Result_Code := IBY_FNDCPT_COMMON_PUB.G_RC_SUCCESS;
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!