eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.IBY_TRANSACTIONEFT_PKG dependencies on IBY_BATCHES_ALL

Line 7: * If there is, it will insert a row into the iby_batches_all table

3:
4: /*
5: * The purpose of this procedure is to check if there is any open
6: * transaction which are due.
7: * If there is, it will insert a row into the iby_batches_all table
8: * to keep track of the batch status, and change the transactions status
9: * to other status. So, the open transactions will be sent as part of
10: * future batch close. Also, it will not allow any modification and
11: * cancellation to these transactions.

Line 29: * If there is, it will insert a row into the iby_batches_all table

25:
26: /*
27: * The purpose of this procedure is to check if there is any open
28: * transaction which are due.
29: * If there is, it will insert a row into the iby_batches_all table
30: * to keep track of the batch status, and change the transactions status
31: * to other status. So, the open transactions will be sent as part of
32: * future batch close. Also, it will not allow any modification and
33: * cancellation to these transactions.

Line 37: profile_code_in IN iby_batches_all.

33: * cancellation to these transactions.
34: */
35: PROCEDURE createBatchCloseTrxnsNew(
36: merch_batchid_in IN VARCHAR2,
37: profile_code_in IN iby_batches_all.
38: process_profile_code%TYPE,
39: merchant_id_in IN VARCHAR2,
40: vendor_id_in IN NUMBER,
41: vendor_key_in IN VARCHAR2,

Line 47: instr_type_in IN iby_batches_all.

43: oldstatus_in IN NUMBER,
44: batchstate_in IN NUMBER DEFAULT null,
45: settlement_date_in IN DATE DEFAULT sysdate,
46: req_type_in IN VARCHAR2 DEFAULT null,
47: instr_type_in IN iby_batches_all.
48: instrument_type%TYPE,
49: br_disputed_flag_in IN iby_batches_all.
50: br_disputed_flag%TYPE,
51: f_pmt_channel_in IN iby_trxn_summaries_all.

Line 49: br_disputed_flag_in IN iby_batches_all.

45: settlement_date_in IN DATE DEFAULT sysdate,
46: req_type_in IN VARCHAR2 DEFAULT null,
47: instr_type_in IN iby_batches_all.
48: instrument_type%TYPE,
49: br_disputed_flag_in IN iby_batches_all.
50: br_disputed_flag%TYPE,
51: f_pmt_channel_in IN iby_trxn_summaries_all.
52: payment_channel_code%TYPE,
53: f_curr_in IN iby_trxn_summaries_all.

Line 73: * the iby_batches_all table to keep track of the batch status, and

69: * This is the overloaded form of the previous API. This takes an array of
70: * profile codes as input parameter (instead of a single one)
71: * The purpose of this procedure is to check if there is any open
72: * transaction which are due. If there is, it will insert a row into
73: * the iby_batches_all table to keep track of the batch status, and
74: * change the transactions status to other status. So, the open
75: * transactions will be sent as part of future batch close. Also, it
76: * will not allow any modification and cancellation to these transactions.
77: */

Line 89: instr_type_in IN iby_batches_all.

85: oldstatus_in IN NUMBER,
86: batchstate_in IN NUMBER,
87: settlement_date_in IN DATE,
88: req_type_in IN VARCHAR2,
89: instr_type_in IN iby_batches_all.
90: instrument_type%TYPE,
91: br_disputed_flag_in IN iby_batches_all.
92: br_disputed_flag%TYPE,
93: f_pmt_channel_in IN iby_trxn_summaries_all.

Line 91: br_disputed_flag_in IN iby_batches_all.

87: settlement_date_in IN DATE,
88: req_type_in IN VARCHAR2,
89: instr_type_in IN iby_batches_all.
90: instrument_type%TYPE,
91: br_disputed_flag_in IN iby_batches_all.
92: br_disputed_flag%TYPE,
93: f_pmt_channel_in IN iby_trxn_summaries_all.
94: payment_channel_code%TYPE,
95: f_curr_in IN iby_trxn_summaries_all.