Common Master

Common Master
Table Name bas_cm_cus_callsign_info

Table Comment Stores Customer Call sign information
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
Csgn_ouinstance	numeric(28)	NOT NULL	To Store the Ouinstance of the Customer Call Information.	Yes	No
Csgn_Cus_CalSgn	varchar(20)	NOT NULL	To Store the Customer Call Sign Reference Code.	Yes	No
Csgn_Customer_Code	varchar(45)	NULL	To store the Customer Code.	No	No
Csgn_Calsgn_Type	varchar(20)	NULL	To Store the Customer Call Type as Special or Regular.	No	No
Csgn_Remarks	varchar(255)	NULL	To Store the Customer Remarks.	No	No
Csgn_Status	varchar(15)	NULL	To Store the Customer Call Status as ’Active’ or ’InActive’.	No	No
Csgn_Created_by	varchar(30)	NULL	To store the User Name who has created the Customer Call.	No	No
Csgn_Creationdate	datetime	NULL	To store the Created Date on which the Customer Call is created..	No	No
Csgn_modified_by	varchar(30)	NULL	To store the User Name who has modified the Customer Call.	No	No
Csgn_modified_date	datetime	NULL	To store the Modified Date on which the Customer Call is modified.	No	No
Csgn_Timestamp	numeric(28)	NULL	To store Timestamp information	No	No
Table Name bas_cm_incident_info
Table Comment Stores Incident information like Poor weather condition, Human Error, Bird Hit etc.,
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
Inc_Ouinstance	numeric(28)	NOT NULL	To Store the Ounistance Value of the Incident Information.	Yes	No
Inc_Incident_No	varchar(16)	NOT NULL	To Store the Incident code.	Yes	No
Inc_Incident_Type	varchar(25)	NULL	To Store the Incident Type	No	No
Inc_Incident_Desc	varchar(80)	NULL	To Store the Incident Description.	No	No
Inc_Ata_No	varchar(16)	NULL	To store the Ata Chapter Number Value for the Incident Number.	No	No
Inc_Status	varchar(15)	NULL	To store the Status of the Incident Number code.	No	No
Inc_created_by	varchar(30)	NULL	To store the User Name who has created the Incident Information.	No	No
Inc_creationdate	datetime	NULL	To store the creation date on which the Incident Information is created.	No	No
Inc_modified_by	varchar(30)	NULL	To store the User Name who has Modified the Incident Information.	No	No
Inc_modifieddate	datetime	NULL	To store the modified date on which the Incident Information is modified.	No	No
Inc_Timestamp	numeric(28)	NULL	Timestamp	No	No
INC_TECHNICAL	varchar(5)	NULL	To store the Technical? with values Y’ - Yes, ’N’- No	No	No
INC_RELANALYIS	varchar(5)	NULL	To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required	No	No
Table Name BAS_CM_NOTE_HIS
Table Comment This table is used to store the various remarks given for the particular record.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
NOTE_REMARKSID	char(18)	NOT NULL	NOTE_REMARKSID	Yes	No
NOTE_OUINSTANCE	numeric(10,0)	NOT NULL	NOTE_OUINSTANCE	No	No
NOTE_REMARKS	varchar(2000)	NULL	NOTE_REMARKS	No	No
NOTE_UPDATEDBY	varchar(30)	NULL	NOTE_UPDATEDBY	No	No
NOTE_UPDATEDDATE	datetime	NULL	NOTE_UPDATEDDATE	No	No
NOTE_TRAN_ID	varchar(150)	NULL	NOTE_TRAN_ID	No	No
Table Name bas_cm_parameter_details
Table Comment This table holds the meta data for the component. This table will exist in all the component as part of the component. This table will hold the static values like combos, combo defaults, guidance text etc. Values are stored against the screen control.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
cm_componentname	varchar(80)	NOT NULL	Name of the component - BASCM	Yes	No
cm_paramcategory	varchar(15)	NOT NULL	This field will capture the category of the static value. The static values could be to fill up combo, text field, guidance text, combo default etc.	Yes	No
cm_paramtype	varchar(15)	NOT NULL	Normally param type is the name of the control. This will allow us to store all the possible values for a combo in multiple rows.	Yes	No
cm_paramCode	varchar(5)	NOT NULL	Param code is the value to be filled in the combo box or guidance text. This is actually the meta data of this component	Yes	No
cm_paramdesc	varchar(80)	NOT NULL	Description of the parameter value	No	No
cm_langid	numeric(10)	NOT NULL	Language id. This is the language id of the record.	No	No
cm_sortby	numeric(10)	NULL	The order in which the quick codes are fetched.	No	No
cm_creationdate	datetime	NULL	Created date of the record.	No	No

Table Name bas_cm_pri_priority_number
Table Comment This stores the priority number. The execution planning of different maintenance activities is based on their respective levels of urgency and importance, which is expressed through the assigned priority numbers. Various business documents such as the "Visit Package", "Work Order", "Maintenance Change Request", "Engineering Order" etc. share the same list of priority numbers which they can take. The priority number will be identified in terms of positive integer. A description can also be identified for the number. The number with lowest value will be rated as most urgent. For example in a set of priority numbers - 1, 2, 3, 4, the priority number 1 will be treated as of highest priority. The priority number can have two statuses - ’Active’ and ’Inactive’. At given point of time, only ’Active’ numbers can be used in all the downstream components.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
pri_ouinstance	decimal(10)	NOT NULL	Ouinstance	Yes	No
pri_priority	numeric(10)	NOT NULL	prioritycode. Identifies level of urgency	Yes	No
pri_description	varchar(20)	NOT NULL	Description of the priority	No	No
pri_description_up	varchar(20)	NOT NULL	Description of the Priority Stored in Upper Case for Oracle Conversion	No	No
pri_status	varchar(5)	NOT NULL	status of the priority	No	No
pri_comments	varchar(255)	NULL	comments during modification of the priority	No	No
pri_created_by	varchar(10)	NOT NULL	User Who has created the Priority	No	No
pri_modified_by	varchar(10)	NOT NULL	User who has modified the priority	No	No
pri_creationdate	datetime	NOT NULL	Creation Date	No	No
pri_modifieddate	datetime	NOT NULL	Modified Date	No	No
pri_timestamp	numeric(10)	NOT NULL	Timestamp	No	No

Table Name bas_cm_regc_regulatory_code
Table Comment This table is used to store Regulatory Authority codes. Regulatory Authorities are the statutory bodies responsible for laying down, and monitoring of standards pertaining to various functions in aviation industry. Each Regulatory Authority can be identified with a unique code The Address details and country to which the body belongs to, can also be identified. The regulatory authority code can have two statuses - ’Active’ and ’Inactive’.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
regc_ouinstance	decimal(10)	NOT NULL	Ouinstance	Yes	No
regc_regulatory_code	varchar(25)	NOT NULL	Regulatory Code	Yes	No
regc_description	varchar(80)	NOT NULL	Description of the Regulatory	No	No
regc_description_up	varchar(80)	NOT NULL	Description of the Regulatory Authority Stored in Upper Case for Oracle Conversion	No	No
regc_address	varchar(255)	NULL	Address	No	No
regc_country	varchar(20)	NULL	Country	No	No
Regc_Country_Up	varchar(20)	NULL	Country in Upper Case for Oracle Conversion	No	No
regc_status	varchar(15)	NOT NULL	status of the regulatory	No	No
regc_comments	varchar(255)	NULL	comments during modification of the regulatory	No	No
regc_creationdate	datetime	NULL	Creation Date	No	No
regc_modifieddate	datetime	NULL	Modified Date	No	No
regc_created_by	varchar(10)	NULL	User Who has created the regulatory	No	No
regc_modified_by	varchar(10)	NULL	User Who has Modified the regulatory	No	No
regc_timestamp	numeric(10)	NOT NULL	Timestamp	No	No

Table Name bas_cm_tmc_time_conv_factor
Table Comment This table is used to store the different conversion factors identified between time units (Hours, Days, Weeks and Months) which are used for converting all the units into common UOM. The multiplying factor can be any positive real number. The multiplying factor can be changed at any point of time. The conversions will be done based on the multiplying factors identified at any given point of time.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
tmc_ouinstance	decimal(10)	NOT NULL	Ouinstance	Yes	No
tmc_manhrs_in_day	numeric(28,8)	NULL	Manhours in a day	No	No
tmc_mandays_in_wk	numeric(28,8)	NULL	Mandays in a week	No	No
tmc_mandays_in_month	numeric(28,8)	NULL	Mandays in a month	No	No
tmc_work_start_time	datetime	NULL	Work Start Time	No	No
tmc_sunday_wklyoff_flag	varchar(5)	NULL	This indicates whether sunday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_monday_wklyoff_flag	varchar(5)	NULL	This indicates whether monday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_tuesday_wklyoff_flag	varchar(5)	NULL	This indicates whether tuesday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_wednesday_wklyoff_flag	varchar(5)	NULL	This indicates whether wednesday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_thursday_wklyoff_flag	varchar(5)	NULL	This indicates whether thursday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_friday_wklyoff_flag	varchar(5)	NULL	This indicates whether friday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_saturday_wklyoff_flag	varchar(5)	NULL	This indicates whether saturday is a weekly holiday or not. This will have the following values Code. Value Y -Yes, N -No	No	No
tmc_created_by	varchar(30)	NULL	User Who has created the Time conversion factor	No	No
tmc_modified_by	varchar(30)	NULL	User Who has Modified the Time conversion factor	No	No
tmc_creationdate	datetime	NULL	Creation Date	No	No
tmc_modifieddate	datetime	NULL	Modified Date	No	No
tmc_timestamp	numeric(10)	NOT NULL	Timestamp	No	No

Table Name Cm_ALOptr_Airline_Operator

Table Comment This table is used to store the Airline operators in the system.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
ALOptr_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
ALOptr_Operator_Code	varchar(32)	NOT NULL	Airline Operator code	Yes	No
ALOptr_Operator_Name	varchar(150)	NULL	Airline Operator Name	No	No
ALOptr_Operator_Name_Up	varchar(150)	NULL	Airline Operator Name in Upper Case for Oracle conversion	No	No
ALOptr_Operator_Type	varchar(15)	NULL	Airline Operator Type which takes values, IA - IATA, IC - ICAO OTH - Others	No	No
ALOptr_Operator_Status	varchar(5)	NULL	Airline Operator Status	No	No
ALOptr_IATA_Code_Ref	varchar(32)	NULL	Airline operator code for the Type ’IATA’	No	No
ALOptr_ICAO_Code_Ref	varchar(32)	NULL	Airline operator code for the Type ’ICAO’	No	No
ALOptr_Others_Code_Ref	varchar(32)	NULL	Airline operator code for the Type ’Others’	No	No
ALOptr_Maintenance_Base	varchar(32)	NULL	Maintenance Base is one of the attribute that represents that Airline Operator.	No	No
ALOptr_Maintenance_Base_Up	varchar(32)	NULL	Maintenance Base in Upper Case for Oracle conversion	No	No
ALOptr_Call_Sign	varchar(32)	NULL	Call sign is one of the attribute that represents that Airline Operator.	No	No
ALOptr_Call_Sign_Up	varchar(32)	NULL	Call sign in Upper Case for Oracle conversion	No	No
ALOptr_Created_By	varchar(32)	NULL	User who created the Airline Operator	No	No
ALOptr_CreatedDate	datetime	NULL	Date at which the Airline Operator Code Details are created.	No	No
ALOptr_Modified_By	varchar(32)	NULL	User who modified the Airline Operator	No	No
ALOptr_ModifiedDate	datetime	NULL	Date at which the Airline Operator Code Details are modified.	No	No
ALOptr_Timestamp	numeric(10)	NULL	TimeStamp	No	No

Table Name Cm_CmBay_AIS_Hanger_Bay_Map

Table Comment This table stores all Bays associated to hangers. Note: Bay in AIS is referred to as ’Child WorkCenter’ in E.Apps
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CmBay_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	Yes
CmBay_Station_Code	varchar(32)	NOT NULL	Station Number	Yes	Yes
CmBay_Hanger_No	varchar(30)	NOT NULL	Hanger No is E.App’s WorkCenter Code	Yes	Yes
CmBay_Bay_No	varchar(30)	NOT NULL	This is equivalent to E.Apps child workcenter	Yes	No
CmBay_Bay_Desc	varchar(150)	NULL	This is description given to the child workcenter	No	No
CmBay_Bay_Status	varchar(5)	NULL	Will be ’I’ for ’InActive’ and ’A’ for ’Active’	No	No

Table Name CM_Cmgate_gate_dtl

Table Comment This table is used to store the Gate details of the stations where maintenance actions can be performed on the aircraft.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CMGate_Created_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	Yes
CMGate_Station_No	varchar(32)	NOT NULL	Station Number	Yes	Yes
CMGate_Gate	varchar(32)	NOT NULL	Gate no	Yes	No
CMGate_Terminal	varchar(32)	NULL	Terminal no	No	No
CMGate_Status	varchar(15)	NULL	gate status	No	No
CMGate_Created_By	varchar(15)	NULL	User who created the Gate	No	No
CMGate_Created_Date	datetime	NULL	Date at which the gate is created	No	No
CMGate_Modified_By	varchar(15)	NULL	User who modified the Gate	No	No
CMGate_Modified_Date	datetime	NULL	Date at which the gate is modified	No	No
CMGate_Timestamp	int	NULL	TimeStamp	No	No
CMGATE_PREFIX	varchar(6)	NULL	Prefix	No	No
CMGATE_SEQNO	int	NULL	Sequence Number	No	No

Table Name CM_CMHNBYTMP_AIS_TMP
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CMHNBYTMP_GUID	varchar(40)	NOT NULL	Guid	No	No
CMHNBYTMP_STNOUINSTANCE	numeric(10)	NULL	Station Ouinstance	No	No
CMHNBYTMP_HANGERCODE	varchar(30)	NULL	Hangar Code	No	No
CMHNBYTMP_HANGERDESC	varchar(150)	NULL	Hangar Description	No	No
CMHNBYTMP_BAYNO	varchar(30)	NULL	Bay Code	No	No
CMHNBYTMP_BAYDESC	varchar(150)	NULL	Bay description	No	No
CMHNBYTMP_MODEFLAG	varchar(5)	NULL	Flag which takes value ’D’ - Delete ’I’ - Insert ’U’ - Update	No	No
CMHNBYTMP_FLAG	varchar(5)	NULL	Flag which takes values ’B’ - Bay ’H’ - Hangar	No	No

Table Name Cm_CmHng_AIS_Stn_Hanger_Map

Table Comment This table stores all hangers associated to stations/Base. Note: Hanger in AIS is referred to as ’WorkCenter’ in E.Apps
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CmHng_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	Yes
CmHng_Station_Code	varchar(32)	NOT NULL	Station Number	Yes	Yes
CmHng_Hanger_No	varchar(30)	NOT NULL	Hanger No is E.APPs WorkCenter Code	Yes	No
CmHng_Hanger_Desc	varchar(150)	NULL	Hanger description is E.Apps WorkCenter Description	No	No
CmHng_Hanger_Status	varchar(5)	NULL	Will be ’I’ for ’InActive’ and ’A’ for ’Active’	No	No

Table Name Cm_CmOpSet_Option_Settings
Table Comment This Common Master Option Settings Table. Option Settings enables the user to set system parameters for Station Code Type and Airline Operator Code Type. These defined parameters can be used as the base values for the system. The Station Code type and Airline Operator Code type can be the types followed by the Airline Operator. Typically these types can be IATA, Airline and Others. All above said Entities will have the status as Active at the time of definition. This status can be changed to Inactive, by modifying the Entities at later point of time. Entities with Inactive Status will not be available for further transactions.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CmOpSet_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	No
CmOpSet_Station_Code_Type	varchar(25)	NOT NULL	Station CodeType	Yes	No
CmOpSet_ArLnOptr_Code_Type	varchar(25)	NOT NULL	Airline Operatory Code Type	Yes	No
CmOpSet_Created_By	varchar(10)	NULL	The User who had set the options	No	No
CmOpSet_CreatedDate	datetime	NOT NULL	Date at which the Options are set by the user	No	No
CmOpSet_Modified_By	varchar(10)	NULL	The User who had modified the options settings.	No	No
CmOpSet_ModifiedDate	datetime	NOT NULL	Date at which the Options are modified by the user	No	No
CmOpSet_Timestamp	numeric(10)	NULL	TimeStamp for the concurrency check	No	No

Table Name Cm_CmQc_Quick_Codes
Table Comment The Common Master Quick Code Table. Quick Codes is a facility provided to the user, by which he can define parameters or attributes to describe the status or classification of some business items. Quick Codes can be defined under different categories like Flight Type, Incident/Accident Type, Landing Type. Shutdown Type and Fuel Type. For example, Quick Codes defined under Landing Type, can be used in Journey Log.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CmQc_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
CmQc_Quick_Code	varchar(25)	NOT NULL	Quick code to define parameters or attributes to describe the status or classification of some business items	Yes	No
CmQc_Type	varchar(5)	NOT NULL	Quick Code Type will be FuelType / ShutDownType as of now. This is used in Flight Log component.	Yes	No
CmQc_Desc	varchar(80)	NULL	Quick Code Description	No	No
CmQc_Status	varchar(5)	NULL	Quick Code Status which can be ether ’Active’ or ’Inactive’	No	No
CmQc_CreatedDate	datetime	NULL	Date at which the user has created the quick code	No	No
CmQc_Created_By	varchar(10)	NULL	The user who created the Quick Code	No	No
CmQc_ModifiedDate	datetime	NULL	Date at which the user has modified the quick code	No	No
CmQc_Modified_By	varchar(10)	NULL	The user who modified the Quick Code	No	No
CmQc_Timestamp	numeric(10)	NULL	TimeStamp for the concurrency check.	No	No

Table Name CM_CmReg_Region_dtl

Table Comment This table is used to store the Region details
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CMReg_Created_OUInstance	decimal(10)	NOT NULL	Ouinstance	Yes	No
CMReg_Region	varchar(32)	NOT NULL	Region	Yes	No
CMReg_Region_desc	varchar(150)	NULL	Region Description	No	No
CMReg_Status	varchar(15)	NULL	Region Status 1. Active 2. Inactive	No	No
CMReg_Created_By	varchar(15)	NULL	User who created the Region	No	No
CMReg_Created_Date	datetime	NULL	Date at which the Region is created	No	No
CMReg_Modified_By	varchar(15)	NULL	User who modified the Region	No	No
CMReg_Modified_Date	datetime	NULL	Date at which the Region is modified	No	No
CMReg_Timestamp	int	NULL	Timestamp	No	No

Table Name CM_CMSYSPRM_OPTION_SETTINGS

Table Comment Stores System Parameter Option Settings.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
CMSYSPRM_OUINSTANCE	numeric(10)	NOT NULL	OU Instance	Yes	No
CMSYSPRM_OPTION_CODE	varchar(5)	NOT NULL	System Parameter Option Code	Yes	No
CMSYSPRM_OPTION_VALUE	varchar(80)	NOT NULL	Option Value	Yes	No
CMSYSPRM_CREATEDDATE	datetime	NOT NULL	Created Date	No	No
CMSYSPRM_CREATED_BY	varchar(10)	NOT NULL	Created By	No	No

Table Name Cm_DlyCd_Delay_Code_Dtl
Table Comment This table is used to record the Delays. During the Time of Arrival and Departure of Aircraft delays can occur. To record the delay information of Aircraft, Delay codes can be used. Delay codes can be identified with Delay Description and Delay Type. Delay Type is the Type followed by Airline Operator, which will be one of the type like IATA, Airline and Others. These identified Delay codes can be used to report delays in Journey Log. Delay can occur due to various reasons like Passenger and Baggage, Cargo and Mail, Aircraft and Ramp Handling, Technical and Aircraft Equipment, Damage to Aircraft & EDP / Automated Equipment Failure, Flight Operation and Crewing, ’Weather, Airport and Government Authorities, Reactionary and Miscellaneous. Due to these reasons, Delay codes are defined under these different categories.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
DlyCd_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	No
DlyCd_Delay_Code	varchar(25)	NOT NULL	Delay Code	Yes	No
DlyCd_Category	varchar(25)	NOT NULL	Delay Category	Yes	No
DlyCd_Desc	varchar(80)	NULL	Description of the Delay Code.	No	No
DlyCd_Desc_up	varchar(80)	NULL	Description of the Delay Code.	No	No
DlyCd_Status	varchar(5)	NULL	Status of the delay.	No	No
DlyCd_Delay_Type	varchar(5)	NULL	Delay Type is the Type followed by Airline Operator, which will be one of the type like IA - IATA, AL - Airline and OTH - Others.	No	No
DlyCd_Delay_On	varchar(5)	NULL	This will be either ’Departure’ or ’Arrival’	No	No
DlyCd_CreatedDate	datetime	NULL	Date at which the Delay code pis recorded	No	No
DlyCd_Created_By	varchar(10)	NULL	The user who created the Delay Code	No	No
DlyCd_ModifiedDate	datetime	NULL	Date at which the Delay code is modified.	No	No
DlyCd_Modified_By	varchar(10)	NULL	The user who modified the Delay Code	No	No
DlyCd_Timestamp	numeric(10)	NULL	TimeStamp	No	No
DLYCD_RELANALYIS	varchar(5)	NULL	To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required	No	No

Table Name Cm_MDocTyp_Mcr_Doc_Type_Dtl
Table Comment This table is used to store the various Maintenance Change requirements details. Engineering Change requirements are communicated through various types of documents such as "Service Bulletins", "Airworthiness Directives" etc. The "Maintenance Change Request Document Type" attempts to classify the various types of modification documents. Each MCR Document type is assigned a unique identifier; which is further qualified through identification of the document source as either "Internal" or "External". A default priority is also set for a document type.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
MDocTyp_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
MDocTyp_Mdoc_Type	varchar(15)	NOT NULL	Represent the types of documents that communicate the Engineering change requirements	Yes	No
MDocTyp_Desc	varchar(150)	NULL	Maintenance Change Request Type Description	No	No
MDocTyp_Priority_No	numeric(10)	NULL	Priority defined for Reference Document	No	No
MDocTyp_Source_Cat	varchar(5)	NULL	Signifies the source of a given MCR Document type as either "Internal" or "External"	No	No
MDocTyp_Status	varchar(5)	NULL	Status of the Reference Document which can be ’Active’ and ’Inactive’	No	No
MDocTyp_Created_By	varchar(10)	NULL	User who created the Reference Document.	No	No
MDocTyp_CreatedDate	datetime	NULL	Date at which Reference Document is created	No	No
MDocTyp_Modified_By	varchar(10)	NULL	User who modified the Reference Document.	No	No
MDocTyp_ModifiedDate	datetime	NULL	Date at which Reference Document is modified.	No	No
MDocTyp_Timestamp	numeric(10)	NULL	Timestamp	No	No

Table Name Cm_MMntEvnt_Maint_Evnt_Dtl
Table Comment This table is used to store Regulatory Authority codes. Regulatory Authorities are the statutory bodies responsible for laying down, and monitoring of standards pertaining to various functions in aviation industry. Each Regulatory Authority can be identified with a unique code The Address details and country to which the body belongs to, can also be identified. The regulatory authority code can have two statuses - ’Active’ and ’Inactive’.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
MMntEvnt_ouinstance	decimal(10)	NOT NULL	%AttDef	Yes	No
MMntEvnt_Event_Code	varchar(30)	NOT NULL	Regulatory Code	Yes	No
MMntEvnt_Event_Desc	varchar(80)	NOT NULL	Description of the Regulatory	No	No
MMntEvnt_Status	varchar(5)	NULL	Address	No	No
MMntEvnt_Created_By	varchar(30)	NULL	Country	No	No
MMntEvnt_Created_Datetime	datetime	NULL	Country in Upper Case for Oracle Conversion	No	No
MMntEvnt_Modified_By	varchar(30)	NOT NULL	status of the regulatory	No	No
MMntEvnt_Modified_Datetime	datetime	NULL	comments during modification of the regulatory	No	No
MMntEvnt_Timestamp	numeric(10)	NULL	Creation Date	No	No

Table Name Cm_MntDIAtt_Mnt_DIAtt_Dtl
Table Comment This table is used to store Regulatory Authority codes. Regulatory Authorities are the statutory bodies responsible for laying down, and monitoring of standards pertaining to various functions in aviation industry. Each Regulatory Authority can be identified with a unique code The Address details and country to which the body belongs to, can also be identified. The regulatory authority code can have two statuses - ’Active’ and ’Inactive’.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
MntDIAtt_Ouinstance	decimal(10)	NOT NULL	%AttDef	Yes	No
MntDIAtt_DIAtt_Type	varchar(25)	NOT NULL	Maintenance Event Type like RECAT MRCL DPCAT	Yes	No
MntDIAtt_DIAtt_Code	varchar(25)	NOT NULL	Maintenance Event Code	Yes	No
MntDIAtt_DIAtt_Desc	varchar(80)	NOT NULL	Description of the Maintenance Event Code	No	No
MntDIAtt_Status	varchar(5)	NULL	Status of Maintenance Event Code	No	No
MntDIAtt_Created_By	varchar(30)	NULL	Created User	No	No
MntDIAtt_Created_Datetime	datetime	NULL	Date on which it is created	No	No
MntDIAtt_Modified_By	varchar(30)	NOT NULL	Modified User	No	No
MntDIAtt_Modified_Datetime	datetime	NULL	Date on which it is modified	No	No
MntDIAtt_Timestamp	numeric(10)	NULL	Timestamp	No	No

Table Name Cm_MntTyp_Maint_Type_Dtl
Table Comment Maintenance activity done on the Aircraft Component can be of the type ’Overhaul’, ’Repair’, ’Inspection". Component maintenance schedules are based on the above maintenance types in terms of the Usage values or elapsed time. Apart from the compliance values based on the Usage, other component maintenance parameters monitored during the life of the component are their Usage value sine Overhaul, Repair, Inspection. Overhaul is considered to be the top most check followed by "repair" and "Inspection". User can select maintenance type ’Others’ whenever any unscheduled maintenance activity to be performed . Once the overhauled / Repaired / Inspected component is installed on the aircraft, it starts inheriting the flying hours and flying cycles from the parent aircraft.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
MntTyp_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	No
MntTyp_Maint_Type_No	varchar(25)	NOT NULL	Maintenance Type Number	Yes	No
MntTyp_Remarks	varchar(255)	NULL	Remarks	No	No
MntTyp_Status	varchar(5)	NULL	Maintenance Type Status	No	No
MntTyp_Created_By	varchar(10)	NULL	User who created the Maintenance Type	No	No
MntTyp_CreatedDate	datetime	NULL	Date at which the Maintenance Type is created	No	No
MntTyp_Modified_By	varchar(10)	NULL	User who modified the Maintenance Type	No	No
MntTyp_ModifiedDate	datetime	NULL	Date at which the Maintenance Type is modified	No	No
MntTyp_Timestamp	numeric(10)	NULL	TimeStamp for the concurrency check	No	No

Table Name Cm_OthOptr_Oth_Operator_Dtl
Table Comment This table is used to store the Other Airline Operators. Airline investments in maintenance facilities could be huge . Given the limited resources at its disposal, an airline might like to make such capital investment decisions judiciously. Hence lots of operators strike an alliance with Other Airline Operators, in order to utilize the resources in their geographical area. This could extend from ground support operations like toilet cleaning to complete line maintenance support. These other Airline Operators can be identified as Airline Operators in the system. The Primary Operator refers to the Operator who is implementing this system. Other Airline Operators transactions like Technical log and Journey Log belonging to Other Airline Operators can also be captured in the system.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
OthOptr_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
OthOptr_Operator_Code	varchar(30)	NOT NULL	Airline Operator code	Yes	No
OthOptr_Operator_Name	varchar(150)	NULL	Airline Operator Name	No	No

Table Name Cm_RDocTyp_Ref_Doc_Type_Dtl
Table Comment This table is used to store details of the Reference Documents that specifies the various Maintenance procedures that have to be carried out. Maintenance execution procedures take references to a variety of basic documentation. The reference documents are typically the manuals provided by the OEMs. Each reference document type is identified through a unique code (Eg: CMM, AMM etc.). Entities such as "Engineering Orders", "Engineering Advice Notes" etc. describe their reference information using these "reference document types".
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
RDocTyp_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
RDocTyp_RDoc_Type	varchar(15)	NOT NULL	Represent the various types of Documents (typically Manuals) which are referred in other business documents.	Yes	No
RDocTyp_Desc	varchar(150)	NULL	Reference Document Type Description	No	No
RDocTyp_Status	varchar(5)	NULL	Reference Document Type Status	No	No
RDocTyp_Applicability	varchar(5)	NULL	Applicability. It takes values C - Component A - Aircraft E - Engine N - None	No	No
RDocTyp_CreatedBy	varchar(10)	NULL	User who created the Reference document	No	No
RDocTyp_CreatedDate	datetime	NULL	Date of creation of Reference Document.	No	No
RDocTyp_ModifiedBy	varchar(10)	NULL	User who modified the Reference document	No	No
RDocTyp_ModifiedDate	datetime	NULL	Date of modification of Reference Document.	No	No
RDocTyp_Timestamp	numeric(10)	NULL	TimeStamp for concurrency check	No	No
RDOCTYP_MAINTLIB	varchar(5)	NULL	Library Maintenance Flag	No	No

Table Name CM_RMVRSN_REMOVAL_REASONS
Table Comment This table is used to store the various reasons for the Aircraft Component to be removed. Aircraft Component is removed due to various reasons like Inspection, damage, developmental repair etc. The "Reasons for Removal" attempts to classify various types of Reasons along with a "Reason category". Reason Category is to categorize various reasons identified. Each reason is identified with a unique code. Each Reason code can be activated or inactivated. Reasons that exist in "active" status can only be used in transactions.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
RmvRsn_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	No
RmvRsn_Reason_Code	varchar(20)	NOT NULL	Represents the various reasons for removal of a component from the aircraft.	Yes	No
RmvRsn_Desc	varchar(255)	NULL	Description of the reason for Removal	No	No
RmvRsn_Desc_UP	varchar(255)	NULL	Description of Reason for Removal in Upper Case for Oracle Conversion	No	No
RmvRsn_Status	varchar(5)	NULL	Removal Reason Status which takes value either ’Active’ or ’Inactive’	No	No
RmvRsn_Category	varchar(25)	NULL	Reason Category is to categorize various reasons identified.	No	No
RmvRsn_Created_By	varchar(10)	NULL	The user who created the record	No	No
RmvRsn_CreatedDate	datetime	NULL	Date at which the reason for removal is created.	No	No
RmvRsn_Modified_By	varchar(10)	NULL	The user who modified the record	No	No
RmvRsn_ModifiedDate	datetime	NULL	Date at which the reason for removal is modified.	No	No
RmvRsn_Timestamp	numeric(10)	NULL	TimeStamp	No	No
RMVRSN_RELANALYIS	varchar(5)	NULL	To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required	No	No
RMVRSN_REMTYPE	varchar(5)	NULL	To store the Removal Type with values ’SCH’ - Scheduled, ’UNSCH’- Unscheduled, ’OTH’- Others	No	No
RMVRSN_BASISREMOVAL	varchar(5)	NULL	To store the Basic Removal? with values ’Y’- Yes, ’N’- No	No	No

Table Name Cm_StnDtl_Station_Dtl
Table Comment This table is used to store the Stations where maintenance actions can be performed on the aircraft. From a maintenance perspective, a Station can be defined as a geographical location, where all the Maintenance actions on an Aircraft are performed. It can be represented in the system using geographical attributes like City, Country, Runway width, Latitude, Longitude and the respective Time zone to which it belongs. Station Code Types like IATA, ICAO or others, depending on the convention followed by the Airlines may be used to identify a station.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
StnDtl_Created_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	No
StnDtl_Station_No	varchar(32)	NOT NULL	Station Number	Yes	No
StnDtl_Station_Desc	varchar(150)	NULL	Station Description	No	No
StnDtl_Station_Desc_up	varchar(150)	NULL	Station Description	No	No
StnDtl_Station_Status	varchar(5)	NULL	Status of the Station which takes values either "Active" or "Inactive"	No	No
StnDtl_Station_Code_Type	varchar(15)	NULL	Station code types which identifies Station takes values such as IATA, ICAO and any other Codes	No	No
StnDtl_Station_TimeZone_No	varchar(30)	NULL	Represents the Time Zone Number	No	No
StnDtl_Station_OUInstance	decimal(10)	NULL	Station OUInstance is the OUInstance to which this station belongs to	No	No
StnDtl_IATA_Station_Ref	varchar(32)	NULL	Station Code for the Type ’IATA’	No	No
StnDtl_ICAO_Station_Ref	varchar(32)	NULL	Station Code for the Type ’ICAO’	No	No
StnDtl_Others_Station_Ref	varchar(32)	NULL	Station Code for the Type ’Others’	No	No
StnDtl_City	varchar(32)	NULL	City at which Maintenance actions can be performed on the Aircraft	No	No
StnDtl_City_up	varchar(32)	NULL	City at which Maintenance actions can be performed on the Aircraft	No	No
StnDtl_Country	varchar(20)	NULL	Country at which Maintenance actions can be performed on the Aircraft	No	No
StnDtl_Country_up	varchar(20)	NULL		No	No
StnDtl_Longest_Runway	varchar(32)	NULL	Longest Runway. It is one geographical attribute where maintenance actions can be performed on the Aircraft.	No	No
StnDtl_Runway_Width	varchar(32)	NULL	Runway width. It is one geographical attribute where maintenance actions can be performed on the Aircraft.	No	No
StnDtl_Latitude	varchar(32)	NULL	Latitude at which maintenance actions can be performed on the Aircraft.	No	No
StnDtl_Longitude	varchar(32)	NULL	Longitude at which maintenance actions can be performed on the Aircraft.	No	No
StnDtl_Overload_Capability	varchar(5)	NULL	Required for Third Party Integration. This will be either ’Yes’ or ’No’.	No	No
StnDtl_Timestamp	numeric(10)	NULL	Timestamp for Concurrency Check.	No	No
StnDtl_Region	varchar(32)	NULL	Region	No	No
STNDTL_CREATED_BY	varchar(15)	NULL	Created by	No	No
STNDTL_CREATED_DATE	datetime	NULL	Creation Date	No	No
STNDTL_MODIFIED_BY	varchar(15)	NULL	Modified By	No	No
STNDTL_MODIFIED_DATE	datetime	NULL	Modified On	No	No

Table Name Cm_StnMdleff_Stn_Model_Eff
Table Comment A Station can handle certain Models of aircraft based on the operational & maintenance Capabilities of the Station. The model handling capability can be defined using model effectivity in the system. This table is used to store the model effectivity.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
StnMdleff_Created_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	Yes
StnMdleff_Station_No	varchar(32)	NOT NULL	Station Code	Yes	Yes
StnMdleff_Model_Ou	decimal(10)	NOT NULL	Model OUInstance	Yes	No
StnMdleff_Model_No	varchar(32)	NOT NULL	Model Number	Yes	No

Table Name Cm_StnNvAds_Stn_NavAids
Table Comment This table is used to store Navigational Aids for the various stations. Station may have certain Navigational Aids to assist the Aircraft during Take off and Landing. This can be defined as NAVAIDS in the system. NAVAIDS can be represented by various attributes like Type, Class, Updating Frequency, TACAN Channel and Station Call Name. One station can be associated with multiple NAVAIDS.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
StnNvAds_Update_Freq	numeric(10,0)	NULL	NAVAIDS Update Frequency. It is one of the attribute which represents NAVAIDS.	No	No
StnNvAds_Class	varchar(20)	NULL	NAVAIDS Class. It is one of the attribute which represents NAVAIDS	No	No
StnNvAds_Tacan_Channel	varchar(20)	NULL	TACAN channel. It is one of the attribute which represents NAVAIDS.	No	No
StnNvAds_Voice_Flag	varchar(5)	NULL	It is one of the attribute which represents NAVAIDS.	No	No
StnNvAds_Station_Call_Name	varchar(80)	NULL	Station Call name. It is one of the attribute which represents NAVAIDS.	No	No
StnNvAds_Created_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	Yes
STNNVADS__NAVAIDS_TYPE	varchar(20)	NULL	NAVAIDS type	No	No
StnNvAds_Station_No	varchar(32)	NOT NULL	Station code	Yes	Yes
StnNvAds_NavAids_No	varchar(30)	NOT NULL	NAVAIDS Number.	Yes	No

Table Name Cm_TzDLS_DayLightSaving_Dtl
Table Comment This table Stores the Day Light Saving Details.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
TzDLS_OUInstance	decimal(10)	NOT NULL	OUInstance	Yes	Yes
TzDLS_TimeZone_No	varchar(30)	NOT NULL	Time Zone Number	Yes	Yes
TzDLS_Cal_Year_No	numeric(10)	NOT NULL	Calendar Year Number	Yes	No
TzDLS_Start_Month_Code	varchar(5)	NULL	Starting Month	No	No
TzDLS_Start_DateTime	datetime	NULL	Starting Date	No	No
TzDLS_Ending_Month_Code	varchar(5)	NULL	Ending Month	No	No
TzDLS_Ending_DateTime	datetime	NULL	Ending Date	No	No
TzDLS_Diff_From_UTC	float	NULL	This field will have the difference value from UTC as what the user enters	No	No
TzDLS_Diff_From_UTC_InMin	float	NULL	Difference from UTC stored in minutes	No	No
TzDLS_Time_Unit	varchar(5)	NULL	Time Unit Code - Can be Days or Minutes	No	No
TzDLS_Timestamp	numeric(10)	NULL	TimeStamp for the Concurrency Check	No	No

Table Name Cm_TzDtl_TimeZone_Dtl
Table Comment This table is used to store Time Zone Details. Time Zone defines various time systems globally with UTC as reference. Time Zone can be identified with Description, Difference from UTC and Time Unit along with Daylight Saving Information. Daylight Saving of Time is a change in the standard time of each time zone. For example Daylight Saving Time begins for most of the United States at 2 a.m. on the first Sunday of April and Time reverts to standard time at 2 a.m. on the last Sunday of October. To capture this Day light Saving information, chronological attributes like Year, Start Month, Date, Time, and End Month, Date and Time are identified . These identified Time zones can be associated with Station, to identify which Time Zone the Station belongs.
Table Column Name	Table Column Datatype	Table Column Null Option	Table Column Comment	Table Column Is PK	Table Column Is FK
TzDtl_OUInstance	decimal(10)	NOT NULL	OUinstance	Yes	No
TzDtl_TimeZone_No	varchar(30)	NOT NULL	Time Zone No	Yes	No
TzDtl_TimeZone_Desc	varchar(150)	NULL	Time Zone Description	No	No
TzDtl_TimeZone_Desc_up	varchar(150)	NULL	Time Zone Description in Upper Case for Oracle Conversion	No	No
TzDtl_TimeZone_Status	varchar(5)	NULL	Status of Time Zone	No	No
TzDtl_Gmt_Conv_Factor	float	NULL	Will have the difference from UTC value in hh.mm format. For e.g., If the deviation of the timezone is +5 hrs and 30 minutes, then this field will have the value 5.30. If the deviation of the timezone is -5 hrs and 30 minutes, then this field will have the value -5.30	No	No
TzDtl_Diff_From_Utc	float	NULL	This field will have the difference value from UTC as what the user enters	No	No
TzDtl_Diff_From_Utc_InMin	numeric(10)	NULL	Difference from UTC stored in minutes	No	No
TzDtl_Time_Unit	varchar(10)	NULL	Time Unit Code - Can be Days or Minutes	No	No
TzDtl_Created_By	varchar(10)	NULL	User who created the Time Zone.	No	No
TzDtl_Created_Date	datetime	NULL	Date at which the Time Zone is created	No	No
TzDtl_Modified_By	varchar(10)	NULL	User who modified the Time Zone.	No	No
TzDtl_Modified_Date	datetime	NULL	Date at which the Time Zone is modified.	No	No
TzDtl_Timestamp	numeric(10)	NULL	TimeStamp for the concurrency check	No	No