Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Complex Maintenance, Repair & Overhaul - Version 12.2.2 and later
Information in this document applies to any platform.
As per design, the API AHL_UA_FLIGHT_SCHEDULES_PVT prevents inserting past flight records because of a validation that succeeding flight records must NOT have actual flight data .. which cause issues whenever a flight record is missed due to external factors (such as de-classification approval of flight missions, human error, special missions, etc)
Current work-around is to insert past flight record is to delete all succeeding actual flight records .. this in turn, may result to additional errors as CMRO user has to manually re-enter the actual flight records
after inserting the missed flight record.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms