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_UA_UNIT_SCHEDULES_PVT dependencies on AHL_VWP_VISITS_PVT

Line 58: p_visit_rec IN AHL_VWP_VISITS_PVT.Visit_Rec_Type,

54: -- Determine whether to add record in appropriate table
55: ---------------------------------------------------------------------------------
56: PROCEDURE populate_visit_schedule_rec
57: (
58: p_visit_rec IN AHL_VWP_VISITS_PVT.Visit_Rec_Type,
59: p_prev_event_type IN VARCHAR2,
60: p_window_event IN BOOLEAN,
61: p_prev_unit_schedule_rec IN AHL_UA_UNIT_SCHEDULES_PVT.Unit_Schedule_rec_type,
62: p_prev_visit_schedule_rec IN AHL_UA_UNIT_SCHEDULES_PVT.Visit_Schedule_rec_type,

Line 772: l_visit_rec AHL_VWP_VISITS_PVT.Visit_Rec_Type;

768: l_event_schedule_tbl AHL_UA_COMMON_PVT.Event_schedule_Tbl_type;
769: -- to store the flight record
770: l_flight_schedule_rec AHL_UA_FLIGHT_SCHEDULES_PVT.Flight_Schedule_Rec_Type;
771: -- to store fetched visit record
772: l_visit_rec AHL_VWP_VISITS_PVT.Visit_Rec_Type;
773: -- to store previous and current record information
774: l_prev_event_type VARCHAR2(12);
775: l_prev_unit_schedule_rec AHL_UA_UNIT_SCHEDULES_PVT.Unit_Schedule_rec_type;
776: l_prev_visit_schedule_rec AHL_UA_UNIT_SCHEDULES_PVT. Visit_Schedule_rec_type;

Line 1720: p_visit_rec IN AHL_VWP_VISITS_PVT.Visit_Rec_Type,

1716: -- Determines Maintenance Opportunity and Conflcits for the current visit record
1717: -- Prepare it with transient variable calculations
1718: -------------------------------------------------------------------------------------------
1719: PROCEDURE populate_visit_schedule_rec(
1720: p_visit_rec IN AHL_VWP_VISITS_PVT.Visit_Rec_Type,
1721: p_prev_event_type IN VARCHAR2,
1722: p_window_event IN BOOLEAN,
1723: p_prev_unit_schedule_rec IN AHL_UA_UNIT_SCHEDULES_PVT.Unit_Schedule_rec_type,
1724: p_prev_visit_schedule_rec IN AHL_UA_UNIT_SCHEDULES_PVT.Visit_Schedule_rec_type,

Line 2030: x_prec_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,

2026: x_msg_data OUT NOCOPY VARCHAR2,
2027: p_unit_config_id IN NUMBER,
2028: p_start_date_time IN DATE,
2029: p_end_date_time IN DATE,
2030: x_prec_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,
2031: x_prec_flight_schedule OUT NOCOPY AHL_UA_FLIGHT_SCHEDULES_PVT.Flight_Schedule_Rec_Type,
2032: x_is_prec_conflict OUT NOCOPY VARCHAR2,
2033: x_is_prec_org_in_ou OUT NOCOPY VARCHAR2,
2034: x_succ_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,

Line 2034: x_succ_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,

2030: x_prec_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,
2031: x_prec_flight_schedule OUT NOCOPY AHL_UA_FLIGHT_SCHEDULES_PVT.Flight_Schedule_Rec_Type,
2032: x_is_prec_conflict OUT NOCOPY VARCHAR2,
2033: x_is_prec_org_in_ou OUT NOCOPY VARCHAR2,
2034: x_succ_visit OUT NOCOPY AHL_VWP_VISITS_PVT.Visit_Rec_Type,
2035: x_succ_flight_schedule OUT NOCOPY AHL_UA_FLIGHT_SCHEDULES_PVT.Flight_Schedule_Rec_Type,
2036: x_is_succ_conflict OUT NOCOPY VARCHAR2,
2037: x_is_succ_org_in_ou OUT NOCOPY VARCHAR2
2038: )