Publication Date: 8/17/2026 Share Print

Previous Topic

Next Topic

Book Contents

Book Index

11.5 - Technical Records Switches

ACAPPROACHDEFECT

When set to Yes, TRAX will display the Defect and Item fields in the A/C Approach Survey window.

When set to No, TRAX will display the Flight Log and Leg fields in the A/C Approach Survey window.

ACAPPROACHDFMAND

When set to Yes, TRAX makes the Defect and Item fields mandatory when creating a new A/C Approach Survey entry.

Note: Switch ACAPPROACHDEFECT must be set to Yes for this switch to have functionality.

When set to No, TRAX does not make the Defect nor Item fields mandatory when creating a new A/C Approach Survey entry.

ACUNITSFLIGHT

When set to Yes, the system allows A/C Units for flight schedules with a 'closed' status to be updated. The Resolved After Flight field will be available in the Defect Report, Resolution.

When set to No, the system will not allow A/C Units for flight schedules with a 'closed' status to be updated. The 'Resolved After Flight' field will be unavailable at the closing of the Defect.

DEFECTASR

When set to Yes, the ASR field will be mandatory. When the ASR field is set to Yes, the system will send the user a system generated notification (if set up).

When set to No, the ASR field will be optional and the system will not send the user a system generated notification.

DEFECTDEFERCATEGORY

When set to Yes, the Defer Category field is not available via the Defect Report Detail, Defer tab.

Note 1: When this switch is set to Yes, it overrides the functionality of switch DEFERCAT.

Note 2: This switch functions for Defect Reports created via the New Express but_new_small button as well as the New Detail but_new_small button.

Note 3: In order to implement the use of this switch, the transaction codes via the Defer field drop down menu must also be available in the Defer Category field drop down menu. If the transaction codes available do not match, the system will display an error message.

When set to No, the Defer Category field is available via the Defect Report Detail, Defer tab.

DEFREPCATMAND

When set to Yes, when troubleshooting items are added to the Defect Report Detail, Troubleshooting tab, the Category field will be mandatory.

When set to No, when troubleshooting items are added to the Defect Report Detail, Troubleshooting tab, the Category field will not be mandatory.

DFPOSMDTRYDEFER

When set to Yes, the Position field via the Defect Report Detail, General tab will be mandatory when a Defect is deferred.

When set to Yes, the Position field via the Defect Report Detail, General tab will not be mandatory when a Defect is deferred.

MDDRDEFAULTDEFECT

When set to Yes, the Defect Number and Item for a newly created and saved Defect Report being Deferred will default to the MDDR field of the Defer tab.

Note: For this switch to have functionality, Switch MDDRAUTO must be set to Yes.

When set to No, with Switch MDDRAUTO set to Yes, the MDDR of a newly created and saved Defect Report being Deferred will default sequentially, via Switch MDDRAUTO’s Config Number. With Switch MDDRAUTO set to No, the MDDR field will not automatically populate.

MELVEFMN

When set to Yes, the system will validate that the MEL/CDL/GMM being entered exists in the MEL Master (Settings/ Update/ MEL) and will not allow the user to save the Defect Report if the entry does not exist in the system. The Config Other field is used to set up which of the three (MEL/CDL/GMM) the system will not validate, or combination of.

When set to No, the system will not validate that the MEL/CDL/GMM entered exists in the system. If the MEL/CDL/GMM entered does not exist in the system, the system will allow the user to save the Defect Report.

Note: The functionality to validate the CDL and GMM was added to this switch in TRAX 11.5 and all later releases of TRAX. The ability to validate the MEL existed in all previous releases of TRAX.

OILCONSCAL

The following functionality was added: If the Config Other is populated with 'OIL', then the notification calculation will be based on the last time oil was added, otherwise, the calculation will be based on flight hours.

See Also

11.5 - Technical Records

11.5 - Technical Records Module

11.5 - Technical Records Buttons

11.5 - Technical Records Transaction Codes

11.5 - Technical Records Security

Top of Page Publication Date: 8/17/2026 Share Print