[Home] [Help]
32: -- module (payment instruction creation flow).
33: --
34: DOC_STATUS_PAY_CREATED CONSTANT VARCHAR2(100) := 'PAYMENT_CREATED';
35:
36: -- Transaction types (for inserting into IBY_TRANSACTION_ERRORS table)
37: TRXN_TYPE_INSTR CONSTANT VARCHAR2(100) := 'PAYMENT_INSTRUCTION';
38:
39: --
40: -- List of valid processing types on the payment profile.
3164: updatePaymentInstructions(x_pmtInstrTab);
3165:
3166: /*
3167: * If any payment instructions/payments were failed, the
3168: * IBY_TRANSACTION_ERRORS table must be populated with the
3169: * corresponding error messages.
3170: */
3171: IBY_VALIDATIONSETS_PUB.insert_transaction_errors('N', x_docErrorTab,
3172: x_errTokenTab);
3226: l_valSetsTab instructionValSetsTab;
3227: l_stmt VARCHAR2(200);
3228: l_result NUMBER := 0;
3229:
3230: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
3231: l_error_code VARCHAR2(100);
3232: l_error_msg VARCHAR2(500);
3233:
3234: /*
3384: IBY_PAY_INSTRUCTIONS_ALL pmt_instr,
3385: IBY_PAYMENT_PROFILES prof,
3386: IBY_TRANSMIT_CONFIGS_VL txconf,
3387: IBY_TRANSMIT_PROTOCOLS_VL txproto,
3388: IBY_TRANSACTION_ERRORS txerrors
3389: WHERE
3390: pmt_instr.payment_instruction_id = p_instr_id
3391: AND val.validation_set_code = val_asgn.validation_set_code
3392: AND val.validation_level_code = 'DISBURSEMENT_INSTRUCTION'
3503: *
3504: * However, make sure to delete the PLSQL table of
3505: * errors. These errors were generated by the validation
3506: * sets and would have already been written into the
3507: * IBY_TRANSACTION_ERRORS table.
3508: *
3509: * If we don't clear out these errors here, the PICP
3510: * will try to insert these errors again in
3511: * performDBUpdates(..) and will fail with a unique
3584:
3585: l_stmt VARCHAR2(200);
3586: l_result NUMBER := 0;
3587:
3588: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
3589: l_error_code VARCHAR2(100);
3590: l_error_msg VARCHAR2(500);
3591:
3592: l_count NUMBER;
3595: IS
3596: SELECT
3597: *
3598: FROM
3599: IBY_TRANSACTION_ERRORS
3600: WHERE
3601: transaction_id = p_instr_id AND
3602: transaction_type = TRXN_TYPE_INSTR AND
3603: error_status <> 'INACTIVE'
3611: *
3612: * Before doing any validations, set any
3613: * existing validation error messages that
3614: * exist against this instruction to 'inactive'
3615: * status in the IBY_TRANSACTION_ERRORS table.
3616: *
3617: * Unless we do this, the old errors will
3618: * continue to show up against this instruction
3619: * in the IBY UI even if the instruction is validated
3698: /*
3699: * Fix for bug 5482490:
3700: *
3701: * Fetch all active error messages stored in
3702: * IBY_TRANSACTION_ERRORS for this payment instruction.
3703: *
3704: * The count of these error messages is used to determine
3705: * whether the payment instruction is valid or not.
3706: */
4777: l_sequence_number NUMBER(38) := NULL;
4778: l_sequence_id fnd_document_sequences.doc_sequence_id%TYPE;
4779: v_profVal VARCHAR2(40);
4780: l_module_name VARCHAR2(200) := G_PKG_NAME || '.assignSequenceNumbers';
4781: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
4782: l_error_code VARCHAR2(100);
4783: l_error_msg VARCHAR2(500);
4784:
4785: BEGIN