Questions Answers For Api

Here are some further questions and answers relating to the
IBY_FNDCPT_TRXN_PUB.Create_Transaction_Extension API.
Questions:
For the parameter “p_payer” : do we have to populate the customer name? or the id?
For the parameter “p_payer_equivalency” : I do not understand the meaning and what to populate inside?
For the parameter “p_pmt_channel” : I do not understand the meaning and what to populate inside?
For the parameter “p_instr_assignment” : do we have to populate the customer bank account name? or
the id?
For the parameter “p_trxn_attribs” : I do not understand the meaning and what to populate inside?
Answers:
i)p_payer should be of the type IBY_FNDCPT_COMMON_PUB.PayerContext_rec_type.
Following is the record type.
TYPE PayerContext_rec_type IS RECORD

(
Payment_Function VARCHAR2(30),
Party_Id NUMBER,
Org_Type VARCHAR2(30),
Org_Id NUMBER,
Cust_Account_Id NUMBER,
Account_Site_Id NUMBER
)
ii) p_payer_equivalency should be hard coded as

IBY_FNDCPT_COMMON_PUB.G_PAYER_EQUIV_UPWARD
iii) p_pmt_channel iby_fndcpt_pmt_chnnls_b.payment_channel_code

It denotes the payment channel for the instrument type.
iv)p_instr_assignment iby_pmt_instr_uses_all.instrument_payment_use_id
It denotes the instrument assignment id.
v)p_trxn_attribs should be of type TrxnExtension_rec_type
Following is the record type.

TYPE TrxnExtension_rec_type IS RECORD
(
Originating_Application_Id NUMBER,
Order_Id VARCHAR2(75),
PO_Number VARCHAR2(100),
PO_Line_Number VARCHAR2(25),
Trxn_Ref_Number1 VARCHAR2(20),
Trxn_Ref_Number2 VARCHAR2(20),
Instrument_Security_Code VARCHAR2(30),
VoiceAuth_Flag VARCHAR2(1),
VoiceAuth_Date DATE,
VoiceAuth_Code VARCHAR2(100),
Additional_Info VARCHAR2(255),
Copy_Instr_Assign_Id NUMBER
For parameter v), record type TrxnExtension_rec_type will be used to set transaction extension attributes
when an extension entity is created.
Since it will support the attributes of all possible payment channels, only some of its fields will be
applicable for channels of a particular instrument type.
Its structure:
Originating_Application_Id - Originating application of the transaction

Must be a valid application id from FND_APPLICATION
Order_Id - Transaction order identifier; typically it is this value that will appear on the payer's financial
statement.
Must be a unique identifier within the application when (optionally) combined with Trxn_Ref_Number1
and Trxn_Ref_Number2
Within EBS generally the order id is generated from some character prefix followed by a sequence value.
Order_id is ultimately the payment system order identifier- i.e. the order identifier which the payment
system sees and which will be reflected on the payer's billing statements (e.g. credit card billing
statement). It is not necessary to tie this value in to other identifiers in the system and strictly speaking the
only requirement for this field is that it be unique. It is up to the customer to determine how much effort
they would like to put into creating an association between the order_id and other transaction identifiers in
their system.
PO_Number - Purchase order number
PO_Line_Number - Purchase order line number
Trxn_Ref_Number1 - Transaction reference number 1; optional transaction identifier used within the
calling application
Trxn_Ref_Number2 - Transaction reference number 2; optional transaction identifier used within the
calling application
Instrument_Security_Code - The payment instrument's security value, knowledge of which is used to

prove ownership of the instrument;
used only for credit cards, where it corresponds to the CVV2 number printed on the card's reverse
VoiceAuth_Flag - If ‘Y' then the transaction was "voice" authorized (i.e. outside Payments)
VoiceAuth_Date - Date of the voice authorization
VoiceAuth_Code - Reference code for the successful voice authorization
Additional_Info - Free-text field for additional information; can be used to capture any information related
to a manual payment, such as the check number and check date
Note:
Transaction identifiers are passed in attributes Order_Id , Trxn_Ref_Number1, and Trxn_Ref_Number2 ,
which together must provide a unique transaction identifier for the application. Note that only Order_Id is
mandatory, and so if Trxn_Ref_Number1 and Trxn_Ref_Number2 are not passed then it must be unique
within the application. Whenever supported by the payment system, Oracle Payments will use the
concatenation of the shortname of the source application and the Order_Id parameter, and the other two
reference parameters (if provided) to identify transactions in the financial statements sent to the payer.
Therefore, the user should be able to query back transactions in the source product using the value
passed in the Order_Id parameter. Products that support multiple transaction types (e.g. invoices and
receipts in AR) are recommended to pass a short code that describes the transaction type in one of the
two reference parameters. This will make it easier for the user to know where they need to go within the
source application to query back the transaction in question.

Questions Answers For Api

Uploaded by

Copyright:

Available Formats

Questions Answers For Api

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Questions Answers For Api

Uploaded by

Copyright:

Available Formats

Here are some further questions and answers relating to the

Following is the record type.

TYPE PayerContext_rec_type IS RECORD

ii) p_payer_equivalency should be hard coded as

iii) p_pmt_channel iby_fndcpt_pmt_chnnls_b.payment_channel_code

v)p_trxn_attribs should be of type TrxnExtension_rec_type

Following is the record type.

Originating_Application_Id - Originating application of the transaction

PO_Number - Purchase order number

PO_Line_Number - Purchase order line number

Instrument_Security_Code - The payment instrument's security value, knowledge of which is used to

VoiceAuth_Date - Date of the voice authorization

VoiceAuth_Code - Reference code for the successful voice authorization

You might also like