DBA Data[Home] [Help]

APPS.AHL_UTIL_MC_PKG dependencies on AHL_MC_RELATIONSHIPS

Line 201: FROM ahl_mc_relationships

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

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

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

Line 242: FROM ahl_mc_relationships

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