eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.IGS_EN_LGCY_PRC dependencies on DUAL

Line 383: || But the logic for that is coded in the individual procedure

379: || clean up the message table as and when necessary.
380: ||
381: || In case the deletion flag is passed as 'Y' and the record is successfully
382: || imported then all the associated error messages would also be deleted.
383: || But the logic for that is coded in the individual procedure
384: || Known limitations, enhancements or remarks :
385: || Change History :
386: || Who When What
387: || kkillams 20-12-2002 Added new validation inside the FOR LOOP

Line 418: SELECT igs_en_lgcy_err_int_s.NEXTVAL INTO l_err_msg_id FROM DUAL;

414: l_msg_count := p_msg_count;
415: l_msg_data := p_msg_data;
416:
417: IF l_msg_count =1 THEN
418: SELECT igs_en_lgcy_err_int_s.NEXTVAL INTO l_err_msg_id FROM DUAL;
419: FND_MESSAGE.SET_ENCODED(l_msg_data);
420: l_msg_text := FND_MESSAGE.GET;
421:
422: l_msg_number := NULL;

Line 439: SELECT igs_en_lgcy_err_int_s.NEXTVAL INTO l_err_msg_id FROM DUAL;

435: );
436: ELSIF l_msg_count > 1 THEN
437: FOR l_index IN 1..NVL(l_msg_count,0)
438: LOOP
439: SELECT igs_en_lgcy_err_int_s.NEXTVAL INTO l_err_msg_id FROM DUAL;
440: FND_MSG_PUB.GET(FND_MSG_PUB.G_FIRST,
441: FND_API.G_TRUE,
442: l_enc_msg,
443: l_msg_index);

Line 3724: It is also import to sort the individual records within the

3720: order in which the "IF" statments appear. This sequence is very
3721: important since the student unit attempt cannot be imported
3722: before the student program attempt is imported.
3723:
3724: It is also import to sort the individual records within the
3725: interface tables for processing. If a unit is transfered
3726: from another program then the original unit must be imported
3727: first and then the one to which it was transfered.
3728: These are taken care of in the individual procedure written in

Line 3728: These are taken care of in the individual procedure written in

3724: It is also import to sort the individual records within the
3725: interface tables for processing. If a unit is transfered
3726: from another program then the original unit must be imported
3727: first and then the one to which it was transfered.
3728: These are taken care of in the individual procedure written in
3729: this package by way of the "Order by" clause.
3730:
3731: In the second case mentioned above, only one interface table
3732: would be processed corresponding to the table code that is passed