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.AHL_UC_TREE_PVT dependencies on FND_LOOKUPS

Line 354: l_pos_ref FND_LOOKUPS.meaning%TYPE;

350: l_child_inst_tbl t_id_tbl;
351: l_child_rel_tbl t_id_tbl;
352: l_child_matchflag_tbl t_flag_tbl;
353: l_child_partinfo_tbl t_partinfo_tbl;
354: l_pos_ref FND_LOOKUPS.meaning%TYPE;
355: l_root_mc_hdr_id NUMBER;
356: l_root_mc_part BOOLEAN;
357: l_root_ata_code AHL_MC_RELATIONSHIPS.ATA_CODE%TYPE; -- SATHAPLI::Enigma code changes, 02-Sep-2008
358:

Line 417: -- Fetch the position reference meaning and necessity from fnd_lookups too.

413: --Given an relationship_id, get all of its immediate children from MC
414: --display_order will determine the sequence of installed and empty sibling nodes
415: -- rbhavsar::FP Bug# 6268202, performance tuning
416: -- Fetch the mc_header_id.
417: -- Fetch the position reference meaning and necessity from fnd_lookups too.
418: -- SATHAPLI::Enigma code changes, 02-Sep-2008 - fetch the ata_code as well
419: CURSOR get_mc_children(c_relationship_id NUMBER) IS
420: SELECT rel.mc_header_id,
421: rel.parent_relationship_id parent_rel_id,

Line 426: FROM fnd_lookups fnd

422: rel.relationship_id,
423: rel.display_order,
424: rel.ata_code,
425: (SELECT fnd.meaning
426: FROM fnd_lookups fnd
427: WHERE fnd.lookup_type = 'AHL_POSITION_REFERENCE'
428: AND fnd.lookup_code = rel.position_ref_code
429: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
430: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)

Line 433: FROM fnd_lookups fnd

429: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
430: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)
431: ) pos_ref_meaning,
432: (SELECT fnd.meaning
433: FROM fnd_lookups fnd
434: WHERE fnd.lookup_type = 'AHL_POSITION_NECESSITY'
435: AND fnd.lookup_code = rel.position_necessity_code
436: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
437: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)

Line 456: -- fetch the position reference meaning and necessity from fnd_lookups too

452: AND trunc(nvl(active_end_date, SYSDATE+1)) > trunc(SYSDATE);
453:
454: --Given an relationship_id, get all of its descendants from MC
455: -- rbhavsar::FP Bug# 6268202, performance tuning
456: -- fetch the position reference meaning and necessity from fnd_lookups too
457: -- SATHAPLI::Enigma code changes, 02-Sep-2008 - fetch the ata_code as well
458: CURSOR get_mc_descendants(c_relationship_id NUMBER) IS
459: SELECT rel.parent_relationship_id parent_rel_id,
460: rel.relationship_id,

Line 464: FROM fnd_lookups fnd

460: rel.relationship_id,
461: rel.display_order,
462: rel.ata_code,
463: (SELECT fnd.meaning
464: FROM fnd_lookups fnd
465: WHERE fnd.lookup_type = 'AHL_POSITION_REFERENCE'
466: AND fnd.lookup_code = rel.position_ref_code
467: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
468: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)

Line 471: FROM fnd_lookups fnd

467: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
468: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)
469: ) pos_ref_meaning,
470: (SELECT fnd.meaning
471: FROM fnd_lookups fnd
472: WHERE fnd.lookup_type = 'AHL_POSITION_NECESSITY'
473: AND fnd.lookup_code = rel.position_necessity_code
474: AND trunc(nvl(fnd.start_date_active, SYSDATE)) <= trunc(SYSDATE)
475: AND trunc(nvl(fnd.end_date_active, SYSDATE+1)) > trunc(SYSDATE)

Line 518: FROM ahl_mc_relationships rel, fnd_lookups fnd

514: -- rbhavsar:: FP Bug# 6268202, performance tuning
515: -- Cursor to get the position reference for a given relationship id.
516: CURSOR get_pos_ref_csr(c_relationship_id NUMBER) IS
517: SELECT fnd.meaning
518: FROM ahl_mc_relationships rel, fnd_lookups fnd
519: WHERE rel.relationship_id = c_relationship_id AND
520: fnd.lookup_code = rel.position_ref_code AND
521: fnd.lookup_type = 'AHL_POSITION_REFERENCE' AND
522: TRUNC(NVL(fnd.start_date_active, SYSDATE)) <= TRUNC(SYSDATE) AND

Line 592: l_pos_necessity_meaning fnd_lookups.meaning%TYPE;

588: l_get_mc_child get_mc_children%ROWTYPE;
589:
590: --Function to get position_necessity meaning for a given relationship_id
591: FUNCTION position_necessity(p_relationship_id NUMBER) RETURN VARCHAR2 IS
592: l_pos_necessity_meaning fnd_lookups.meaning%TYPE;
593: CURSOR get_position_necessity(c_relationship_id NUMBER) IS
594: SELECT F.meaning
595: FROM ahl_mc_relationships A,
596: fnd_lookup_values_vl F