[Home] [Help]
34: -- module (payment instruction creation flow).
35: --
36: DOC_STATUS_PAY_CREATED CONSTANT VARCHAR2(100) := 'PAYMENT_CREATED';
37:
38: -- Transaction types (for inserting into IBY_TRANSACTION_ERRORS table)
39: TRXN_TYPE_INSTR CONSTANT VARCHAR2(100) := 'PAYMENT_INSTRUCTION';
40:
41: --
42: -- List of valid processing types on the payment profile.
3601: updatePaymentInstructions(x_pmtInstrTab);
3602:
3603: /*
3604: * If any payment instructions/payments were failed, the
3605: * IBY_TRANSACTION_ERRORS table must be populated with the
3606: * corresponding error messages.
3607: */
3608: IBY_VALIDATIONSETS_PUB.insert_transaction_errors('N', x_docErrorTab,
3609: x_errTokenTab);
3667: l_valSetsTab instructionValSetsTab;
3668: l_stmt VARCHAR2(200);
3669: l_result NUMBER := 0;
3670:
3671: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
3672: l_error_code VARCHAR2(100);
3673: l_error_msg VARCHAR2(500);
3674:
3675: l_call_pmt_comp_validation VARCHAR2(100);
3838: IBY_PAY_INSTRUCTIONS_ALL pmt_instr,
3839: IBY_PAYMENT_PROFILES prof,
3840: IBY_TRANSMIT_CONFIGS_VL txconf,
3841: IBY_TRANSMIT_PROTOCOLS_VL txproto,
3842: IBY_TRANSACTION_ERRORS txerrors
3843: WHERE
3844: pmt_instr.payment_instruction_id = p_instr_id
3845: AND val.validation_set_code = val_asgn.validation_set_code
3846: AND val.validation_level_code = 'DISBURSEMENT_INSTRUCTION'
3967: *
3968: * However, make sure to delete the PLSQL table of
3969: * errors. These errors were generated by the validation
3970: * sets and would have already been written into the
3971: * IBY_TRANSACTION_ERRORS table.
3972: *
3973: * If we don't clear out these errors here, the PICP
3974: * will try to insert these errors again in
3975: * performDBUpdates(..) and will fail with a unique
4052:
4053: l_stmt VARCHAR2(200);
4054: l_result NUMBER := 0;
4055:
4056: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
4057: l_error_code VARCHAR2(100);
4058: l_error_msg VARCHAR2(500);
4059: l_call_pmt_comp_validation VARCHAR2(100);
4060:
4064: IS
4065: SELECT
4066: *
4067: FROM
4068: IBY_TRANSACTION_ERRORS
4069: WHERE
4070: transaction_id = p_instr_id AND
4071: transaction_type = TRXN_TYPE_INSTR AND
4072: error_status <> 'INACTIVE'
4080: *
4081: * Before doing any validations, set any
4082: * existing validation error messages that
4083: * exist against this instruction to 'inactive'
4084: * status in the IBY_TRANSACTION_ERRORS table.
4085: *
4086: * Unless we do this, the old errors will
4087: * continue to show up against this instruction
4088: * in the IBY UI even if the instruction is validated
4237: /*
4238: * Fix for bug 5482490:
4239: *
4240: * Fetch all active error messages stored in
4241: * IBY_TRANSACTION_ERRORS for this payment instruction.
4242: *
4243: * The count of these error messages is used to determine
4244: * whether the payment instruction is valid or not.
4245: */
5378: l_sequence_number NUMBER(38) := NULL;
5379: l_sequence_id fnd_document_sequences.doc_sequence_id%TYPE;
5380: v_profVal VARCHAR2(40);
5381: l_module_name VARCHAR2(200) := G_PKG_NAME || '.assignSequenceNumbers';
5382: l_doc_err_rec IBY_TRANSACTION_ERRORS%ROWTYPE;
5383: l_error_code VARCHAR2(100);
5384: l_error_msg VARCHAR2(500);
5385:
5386: BEGIN