[Home] [Help]
8:
9: /*
10: * The purpose of this procedure is to check if there is any open
11: * transaction which are due. If there is, it will insert a row into
12: * the iby_batches_all table to keep track of the batch status, and
13: * change the transactions status to other status. So, the open
14: * transactions will be sent as part of future batch close. Also, it
15: * will not allow any modification and cancellation to these transactions.
16: */
29: IS
30:
31: numrows NUMBER;
32: l_mpayeeid iby_payee.mpayeeid%type;
33: l_mbatchid iby_batches_all.mbatchid%type;
34:
35: BEGIN
36:
37: SELECT
62: DUAL;
63:
64: iby_accppmtmthd_pkg.getMPayeeId(merchant_id_in, l_mpayeeid);
65:
66: INSERT INTO iby_batches_all
67: (MBATCHID,
68: BATCHID,
69: MPAYEEID,
70: PAYEEID,
135:
136: /*
137: * The purpose of this procedure is to check if there is any open
138: * transaction which are due. If there is, it will insert a row into
139: * the iby_batches_all table to keep track of the batch status, and
140: * change the transactions status to other status. So, the open
141: * transactions will be sent as part of future batch close. Also, it
142: * will not allow any modification and cancellation to these transactions.
143: */
142: * will not allow any modification and cancellation to these transactions.
143: */
144: PROCEDURE createBatchCloseTrxnsNew(
145: merch_batchid_in IN VARCHAR2,
146: profile_code_in IN iby_batches_all.
147: process_profile_code%TYPE,
148: merchant_id_in IN VARCHAR2,
149: vendor_id_in IN NUMBER,
150: vendor_key_in IN VARCHAR2,
152: oldstatus_in IN NUMBER,
153: batchstate_in IN NUMBER,
154: settlement_date_in IN DATE,
155: req_type_in IN VARCHAR2,
156: instr_type_in IN iby_batches_all.
157: instrument_type%TYPE,
158: br_disputed_flag_in IN iby_batches_all.
159: br_disputed_flag%TYPE,
160: f_pmt_channel_in IN iby_trxn_summaries_all.
154: settlement_date_in IN DATE,
155: req_type_in IN VARCHAR2,
156: instr_type_in IN iby_batches_all.
157: instrument_type%TYPE,
158: br_disputed_flag_in IN iby_batches_all.
159: br_disputed_flag%TYPE,
160: f_pmt_channel_in IN iby_trxn_summaries_all.
161: payment_channel_code%TYPE,
162: f_curr_in IN iby_trxn_summaries_all.
176: IS
177:
178: numrows NUMBER;
179: l_mpayeeid iby_payee.mpayeeid%type;
180: l_mbatchid iby_batches_all.mbatchid%type;
181: l_module_name CONSTANT VARCHAR2(200) :=
182: G_PKG_NAME || '.createBatchCloseTrxnsNew';
183:
184: l_batches_tab IBY_TRANSACTIONCC_PKG.batchAttrTabType;
259:
260: /*
261: * After grouping it is possible that multiple batches were
262: * created. Each batch will be a separate row in the
263: * IBY_BATCHES_ALL table with a unique mbatchid.
264: *
265: * The user may have provided a batch id (batch prefix), we will
266: * have to assign that batch id to each of the created batches.
267: *
339:
340: print_debuginfo(l_module_name, 'Going to insert batch '
341: || l_batches_tab(i).mbatch_id);
342:
343: INSERT INTO iby_batches_all
344: (MBATCHID,
345: BATCHID,
346: MPAYEEID,
347: PAYEEID,
479: * This is the overloaded form of the previous API. This takes an array of
480: * profile codes as input parameter (instead of a single one)
481: * The purpose of this procedure is to check if there is any open
482: * transaction which are due. If there is, it will insert a row into
483: * the iby_batches_all table to keep track of the batch status, and
484: * change the transactions status to other status. So, the open
485: * transactions will be sent as part of future batch close. Also, it
486: * will not allow any modification and cancellation to these transactions.
487: */
495: oldstatus_in IN NUMBER,
496: batchstate_in IN NUMBER,
497: settlement_date_in IN DATE,
498: req_type_in IN VARCHAR2,
499: instr_type_in IN iby_batches_all.
500: instrument_type%TYPE,
501: br_disputed_flag_in IN iby_batches_all.
502: br_disputed_flag%TYPE,
503: f_pmt_channel_in IN iby_trxn_summaries_all.
497: settlement_date_in IN DATE,
498: req_type_in IN VARCHAR2,
499: instr_type_in IN iby_batches_all.
500: instrument_type%TYPE,
501: br_disputed_flag_in IN iby_batches_all.
502: br_disputed_flag%TYPE,
503: f_pmt_channel_in IN iby_trxn_summaries_all.
504: payment_channel_code%TYPE,
505: f_curr_in IN iby_trxn_summaries_all.
519: IS
520:
521: numrows NUMBER;
522: l_mpayeeid iby_payee.mpayeeid%type;
523: l_mbatchid iby_batches_all.mbatchid%type;
524: l_module_name CONSTANT VARCHAR2(200) :=
525: G_PKG_NAME || '.createBatchCloseTrxnsNew';
526:
527: l_batches_tab IBY_TRANSACTIONCC_PKG.batchAttrTabType;
635:
636: /*
637: * After grouping it is possible that multiple batches were
638: * created. Each batch will be a separate row in the
639: * IBY_BATCHES_ALL table with a unique mbatchid.
640: *
641: * The user may have provided a batch id (batch prefix), we will
642: * have to assign that batch id to each of the created batches.
643: *
719: * Modified to insert null values for bepkey, currency and
720: * profile code columns since these could have multiple values
721: * for a batch.
722: */
723: INSERT INTO iby_batches_all
724: (MBATCHID,
725: BATCHID,
726: MPAYEEID,
727: PAYEEID,
877: BEGIN
878: -- reset the OBJECT VERSION NUMBER, since we not using it
879: -- the purpose of this, it is to keep track the EFT batchseq number
880:
881: UPDATE iby_batches_all SET
882: SENTCOUNTERDAILY = 0
883: WHERE batchid = merch_batchid_in
884: AND payeeid = merchant_id_in
885: AND trunc(LAST_UPDATE_DATE) < trunc(sysdate);
884: AND payeeid = merchant_id_in
885: AND trunc(LAST_UPDATE_DATE) < trunc(sysdate);
886:
887:
888: UPDATE iby_batches_all SET
889: BATCHSTATUS = batchstate_in,
890: BATCHSTATEID = batchstate_in,
891: NUMTRXNS = numtrxns_in,
892: