DBA Data[Home] [Help]

APPS.AHL_UTIL_MC_PKG dependencies on AHL_MC_RELATIONSHIPS

Line 203: FROM ahl_mc_relationships

199: p_relationship_id IN NUMBER
200: )
201: IS
202: SELECT position_ref_code
203: FROM ahl_mc_relationships
204: WHERE relationship_id = p_relationship_id AND
205: -- Since positions with active_start_date > sysdate are also displayed in the MC tree, no need to check for active_start_date
206: -- G_TRUNC_DATE between TRUNC(NVL(active_start_date, SYSDATE)) AND TRUNC(NVL(active_end_date, SYSDATE+1));
207: G_TRUNC_DATE <= TRUNC(NVL(active_end_date, SYSDATE+1));

Line 209: l_position_ref_code ahl_mc_relationships.position_ref_code%TYPE DEFAULT NULL;

205: -- Since positions with active_start_date > sysdate are also displayed in the MC tree, no need to check for active_start_date
206: -- G_TRUNC_DATE between TRUNC(NVL(active_start_date, SYSDATE)) AND TRUNC(NVL(active_end_date, SYSDATE+1));
207: G_TRUNC_DATE <= TRUNC(NVL(active_end_date, SYSDATE+1));
208:
209: l_position_ref_code ahl_mc_relationships.position_ref_code%TYPE DEFAULT NULL;
210: l_return_val BOOLEAN DEFAULT TRUE;
211:
212: BEGIN
213:

Line 244: FROM ahl_mc_relationships

240: p_relationship_id IN NUMBER
241: )
242: IS
243: SELECT 'x'
244: FROM ahl_mc_relationships
245: WHERE relationship_id = p_relationship_id AND
246: -- Since positions with active_start_date > sysdate are also displayed in the MC tree, no need to check for active_start_date
247: -- G_TRUNC_DATE between TRUNC(NVL(active_end_date, SYSDATE)) AND TRUNC(NVL(active_end_date, SYSDATE+1));
248: G_TRUNC_DATE <= TRUNC(NVL(active_end_date, SYSDATE+1));