APPS.IBY_PAYINSTR_PUB dependencies on DUAL

Line 1452: * Individual payment instructions contain the profile id

1448:
1449: /*
1450: * Get the mapping between profile ids and system profile codes.
1451: *
1452: * Individual payment instructions contain the profile id
1453: * as an attribute. However, the config tables like
1454: * pmt instruction creation rules etc. contain settings
1455: * based on system profile codes.
1456: *

Line 2563: DUAL

2559: IBY_PAY_INSTRUCTIONS_ALL_S.NEXTVAL
2560: INTO
2561: x_pmtInstrID
2562: FROM
2563: DUAL
2564: ;
2565:
2566: END getNextPaymentInstructionID;
2567:

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

2605:
2606: /*
2607: * Update the payments. We cannot use bulk update here
2608: * because the bulk update syntax does not allow us to
2609: * reference individual fields of the PL/SQL record.
2610: *
2611: * TBD: Is there any way to optimize this update?
2612: */
2613: FOR i in p_pmtsInPayInstTab.FIRST..p_pmtsInPayInstTab.LAST LOOP

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

3144: performSortedPaymentNumbering(x_pmtInstrTab, l_sorted_pmts_tab,
3145: p_profileMap, x_docErrorTab, x_errTokenTab);
3146:
3147: /*
3148: * Update individual payments with their document sequence numbers
3149: * and payment references.
3150: */
3151: updatePmtsWithSeqNumPmtRef(l_sorted_pmts_tab);
3152:

Line 3790: DUAL

3786: IBY_EVENT_KEY_S.NEXTVAL
3787: INTO
3788: l_event_key
3789: FROM
3790: DUAL
3791: ;
3792:
3793: /*
3794: * Raise a business event with the list of failed

Line 4554: * unique sequence numbers to the individual

4550:
4551: /*
4552: * STEP II:
4553: * Invoke the document sequencing API to assign
4554: * unique sequence numbers to the individual
4555: * payments of the instruction.
4556: */
4557: assignSequenceNumbers(x_sortedPmtTab, x_docErrorTab, x_errTokenTab);
4558: