APPS.IBY_PAYINSTR_PUB dependencies on DUAL

Line 1618: * Individual payment instructions contain the profile id

1614:
1615: /*
1616: * Get the mapping between profile ids and system profile codes.
1617: *
1618: * Individual payment instructions contain the profile id
1619: * as an attribute. However, the config tables like
1620: * pmt instruction creation rules etc. contain settings
1621: * based on system profile codes.
1622: *

Line 2815: DUAL

2811: IBY_PAY_INSTRUCTIONS_ALL_S.NEXTVAL
2812: INTO
2813: x_pmtInstrID
2814: FROM
2815: DUAL
2816: ;
2817:
2818: END getNextPaymentInstructionID;
2819:

Line 2865: * reference individual fields of the PL/SQL record.

2861:
2862: /*
2863: * Update the payments. We cannot use bulk update here
2864: * because the bulk update syntax does not allow us to
2865: * reference individual fields of the PL/SQL record.
2866: *
2867: * TBD: Is there any way to optimize this update?
2868: */
2869: FOR i in p_pmtsInPayInstTab.FIRST..p_pmtsInPayInstTab.LAST LOOP

Line 3585: * Update individual payments with their document sequence numbers

3581: performSortedPaymentNumbering(x_pmtInstrTab, l_sorted_pmts_tab,
3582: p_profileMap, x_docErrorTab, x_errTokenTab);
3583:
3584: /*
3585: * Update individual payments with their document sequence numbers
3586: * and payment references.
3587: */
3588: updatePmtsWithSeqNumPmtRef(l_sorted_pmts_tab);
3589:

Line 4333: DUAL

4329: IBY_EVENT_KEY_S.NEXTVAL
4330: INTO
4331: l_event_key
4332: FROM
4333: DUAL
4334: ;
4335:
4336: /*
4337: * Raise a business event with the list of failed

Line 5137: * unique sequence numbers to the individual

5133:
5134: /*
5135: * STEP II:
5136: * Invoke the document sequencing API to assign
5137: * unique sequence numbers to the individual
5138: * payments of the instruction.
5139: */
5140: assignSequenceNumbers(x_sortedPmtTab, x_docErrorTab, x_errTokenTab);
5141:

Line 7665: 'SELECT decode(IBY_FD_EXTRACT_EXT_PUB.payment_completion_validation,''Y'',''Y'',''N'') FROM DUAL'

7661: print_debuginfo(l_module_name, 'Evaluating whether or not to call payment_completion_validation');
7662: END IF;
7663:
7664: EXECUTE IMMEDIATE
7665: 'SELECT decode(IBY_FD_EXTRACT_EXT_PUB.payment_completion_validation,''Y'',''Y'',''N'') FROM DUAL'
7666: INTO x_call_pmt_comp_validation;
7667:
7668: IF ( G_LEVEL_STATEMENT >= G_CURRENT_RUNTIME_LEVEL) THEN
7669: print_debuginfo(l_module_name, 'payment_completion_validation logic is to be triggered');