Data Dictionary -- Common Master | ||||||||
Srl. No. | Table Name | Comment |
1 | BAS_CM_CFMTASK_DTLS | BAS_CM_CFMTASK_DTLS |
2 | BAS_CM_CUS_CALLSIGN_INFO | Stores Customer Call sign information |
3 | BAS_CM_DOC_ATT_PARAM_MST | BAS_CM_DOC_ATT_PARAM_MST |
4 | BAS_CM_DOC_CLASSIFICATION_LIST | BAS_CM_DOC_CLASSIFICATION_LIST |
5 | BAS_CM_DOC_CLASSI_ATT_DET | BAS_CM_DOC_CLASSI_ATT_DET |
6 | BAS_CM_INCIDENT_INFO | Stores Incident information like Poor weather condition, Human Error, Bird Hit etc., |
7 | BAS_CM_NOTE_HIS | BAS_CM_NOTE_HIS |
8 | BAS_CM_PARAMETER_DETAILS | 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. |
9 | BAS_CM_PRI_PRIORITY_NUMBER | 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 " |
10 | BAS_CM_REGC_REGULATORY_CODE | 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 ident |
11 | BAS_CM_TMC_TIME_CONV_FACTOR | 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 multiply |
12 | cm_accountinfo_dtl | cm_accountinfo_dtl |
13 | cm_accountinfo_hdr | cm_accountinfo_hdr |
14 | CM_AIRCRAFT_MOD_HDR | CM_AIRCRAFT_MOD_HDR |
15 | CM_ALOPTR_AIRLINE_OPERATOR | This table is used to store the Airline operators in the system. |
16 | CM_CMBAY_AIS_HANGER_BAY_MAP | This table stores all Bays associated to hangers. Note: Bay in AIS is referred to as Child WorkCenter in E.Apps |
17 | CM_Cmgate_gate_dtl | This table is used to store the Gate details of the staions where maintenance actions can be performed on the aircraft. |
18 | CM_CMHNG_AIS_STN_HANGER_MAP | This table stores all hangers associated to stations/Base. Note: Hanger in AIS is referred to as WorkCenter in E.Apps |
19 | CM_CMOPSET_OPTION_SETTINGS | 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 |
20 | CM_CMQC_QUICK_CODES | The Commom 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 lik |
21 | CM_CmReg_Region_dtl | This table is used to store the Region details |
22 | CM_CMSYSPRM_OPTION_SETTINGS | Stores System Parameter Option Settings. |
23 | CM_DLYCD_DELAY_CODE_DTL | This table is used to record the Delays. During the Time of Arrival and Departure of Aircrafts delays can occur. To record the delay information of Aircrafts, Delay codes can be used. Delay codes can be identified with Delay Description and Delay Type. D |
24 | cm_dunning_dtl | cm_dunning_dtl |
25 | cm_dunning_hdr | cm_dunning_hdr |
26 | cm_entity_event_mapping | cm_entity_event_mapping |
27 | CM_GLI_MST | CM_GLI_MST |
28 | CM_MDOCTYP_MCR_DOC_TYPE_DTL | 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 Requ |
29 | CM_MMNTEVNT_MAINT_EVNT_DTL | CM_MMNTEVNT_MAINT_EVNT_DTL |
30 | CM_MNTDIATT_MNT_DIATT_DTL | CM_MNTDIATT_MNT_DIATT_DTL |
31 | CM_MNTTYP_MAINT_TYPE_DTL | 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 |
32 | CM_OTHOPTR_OTH_OPERATOR_DTL | 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 |
33 | CM_RDOCTYP_REF_DOC_TYPE_DTL | 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 ar |
34 | CM_RMVRSN_REMOVAL_REASONS | This table is used to store the various remarks given for the particular record. |
35 | CM_STNDTL_STATION_DTL | This table is used to store the Staions 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 ca |
36 | CM_STNMDLEFF_STN_MODEL_EFF | 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. |
37 | CM_STNNVADS_STN_NAVAIDS | 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 at |
38 | CM_TZDLS_DAYLIGHTSAVING_DTL | This table Stores the Day Light Saving Details. |
39 | CM_TZDTL_TIMEZONE_DTL | 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 Savin |
Table Name : | |
Comment : | BAS_CM_CFMTASK_DTLS |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CFMTASK_OUINSTANCE | udd_ctxt_ouinstance | int(4) | No | ouinstance | No |
CFMTASK_SRCCOMPONENT | udd_ctxt_component | varchar(20) | No | source component | No |
CFMTASK_ACTIVITY | udd_activity_name | varchar(40) | No | Task Activity | No |
CFMTASK_ACTIVITY_DESC | udd_activitydesc | varchar(128) | No | Task Activity Description | No |
CFMTASK_TASK | udd_workunitcode | varchar(30) | No | Task # | No |
CFMTASK_TSKCONFRM | _int_0 | int(0) | No | Confirm Task | No |
replication_key | _bigint_8 | Bigint(8) | No | Replication Key | Yes |
Table Name : | |
Comment : | Stores Customer Call sign information |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CSGN_OUINSTANCE | _numeric_28_0 | numeric(28) | No | To Store the Ouinstance of the Customer Call Information. | Yes |
CSGN_CUS_CALSGN | _varchar_20 | varchar(20) | No | To Store the Customer Call Sign Reference Code. | Yes |
CSGN_CUSTOMER_CODE | _varchar_45 | varchar(45) | Yes | To store the Customer Code. | No |
CSGN_CALSGN_TYPE | _varchar_20 | varchar(20) | Yes | To Store the Customer Call Type as Special or Regular. | No |
CSGN_REMARKS | _varchar_255 | varchar(255) | Yes | To Store the Customer Remarks. | No |
CSGN_STATUS | _varchar_15 | varchar(15) | Yes | To Store the Customer Call Status as Active or InActive. | No |
CSGN_CREATED_BY | _varchar_30 | varchar(30) | Yes | To store the User Name who has created the Customer Call. | No |
CSGN_CREATIONDATE | _datetime_8 | datetime(8) | Yes | To store the Created Date on which the Customer Call is created.. | No |
CSGN_MODIFIED_BY | _varchar_30 | varchar(30) | Yes | To store the User Name who has modified the Customer Call. | No |
CSGN_MODIFIED_DATE | _datetime_8 | datetime(8) | Yes | To store the Modified Date on which the Customer Call is modified. | No |
CSGN_TIMESTAMP | _numeric_28_0 | numeric(28) | Yes | To store Timestamp information | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | BAS_CM_DOC_ATT_PARAM_MST |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_DOC_CLASSIFCATION | udd_designparamcode | varchar(5) | No | document classification | Yes |
CM_ATT_CODE | udd_designparamcode | varchar(5) | No | Attribute code | Yes |
CM_ATT_DESC | udd_txt150 | varchar(150) | No | Attribute description | No |
CM_ATT_PERMITTED_DET_DESC | udd_txt255 | varchar(255) | No | Permitted values for the attribute | No |
CM_LANGUAGE_ID | udd_ctxt_language | int(4) | No | Language id | No |
CM_SORTBY | udd_count | int(4) | No | The order in which the quick codes are fetched. | No |
Table Name : | |
Comment : | BAS_CM_DOC_CLASSIFICATION_LIST |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_OUINSTANCE | udd_ctxt_ouinstance | int(4) | No | ouinstance | Yes |
CM_KEY | udd_guid | varchar(40) | No | Key to define the Entity | Yes |
CM_DOC_CLASSIFCATION | udd_quickcodes | varchar(25) | No | Document classification | No |
CM_DOC_TYPE | udd_quickcodes | varchar(25) | No | Document type | No |
CM_DOC_STATUS | udd_designparamcode | varchar(5) | No | Document status | No |
CM_DOC_ATT_DEF_FLAG | udd_designparamcode | varchar(5) | No | Deferement Flag | No |
CM_TIMESTAMP | udd_timestampint | int(4) | No | Time stamp | No |
CM_CREATED_BY | udd_ctxt_user | varchar(30) | Yes | Created by | No |
CM_CREATED_DATE | _datetime_8 | datetime(8) | Yes | Created date | No |
CM_MODIFIED_BY | udd_ctxt_user | varchar(30) | Yes | Modified by | No |
CM_MODIFIED_DATE | _datetime_8 | datetime(8) | Yes | Modified date | No |
CM_DOC_DESCRIPTION | udd_txt150 | varchar(150) | Yes | Document Description | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |
Table Name : | |
Comment : | BAS_CM_DOC_CLASSI_ATT_DET |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_OUINSTANCE | udd_ctxt_ouinstance | int(4) | No | Ouinstance | Yes |
CM_KEY | udd_guid | varchar(40) | No | Key to define the Entity | Yes |
CM_ATT_CODE | udd_designparamcode | varchar(5) | No | Attribute code | Yes |
CM_ATT_VALUE | udd_txt1000 | varchar(1000) | Yes | Attribute cvalue | No |
CM_DOC_CLASS | udd_designparamcode | varchar(5) | No | Document classification | No |
CM_DOC_TYPE | udd_documenttype | varchar(40) | No | Document type | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |
Table Name : | |
Comment : | Stores Incident information like Poor weather condition, Human Error, Bird Hit etc., |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
INC_OUINSTANCE | _numeric_28_0 | numeric(28) | No | To Store the Ounistance Value of the Incident Information. | Yes |
INC_INCIDENT_NO | _varchar_16 | varchar(16) | No | To Store the Incident code. | Yes |
INC_INCIDENT_TYPE | _varchar_25 | Varchar(25) | Yes | To Store the Incident Type | No |
INC_INCIDENT_DESC | _varchar_80 | varchar(80) | Yes | To Store the Incident Description. | No |
INC_ATA_NO | _varchar_16 | varchar(16) | Yes | To store the Ata Chapter Number Value for the Incident Number. | No |
INC_STATUS | _varchar_15 | varchar(15) | Yes | To store the Status of the Incident Number code. | No |
INC_CREATED_BY | _varchar_30 | varchar(30) | Yes | To store the User Name who has created the Incident Information. | No |
INC_CREATIONDATE | _datetime_8 | datetime(8) | Yes | To store the creation date on which the Incident Information is created. | No |
INC_MODIFIED_BY | _varchar_30 | varchar(30) | Yes | To store the User Name who has Modified the Incident Information. | No |
INC_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | To store the modified date on which the Incident Information is modified. | No |
INC_TIMESTAMP | _numeric_28_0 | numeric(28) | Yes | Timestamp | No |
INC_TECHNICAL | designparamcode | varchar(5) | Yes | To store the Technical? with values "Y" - Yes, "N"- No | No |
INC_RELANALYIS | designparamcode | varchar(5) | Yes | To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | BAS_CM_NOTE_HIS |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
NOTE_OUINSTANCE | udd_ctxt_ouinstance | int(4) | No | Ouinstance | No |
NOTE_REMARKS | udd_notes | varchar(2000) | Yes | Remarks | No |
NOTE_REMARKSID | udd_guid | varchar(40) | Yes | Remarks id | No |
NOTE_UPDATEDBY | udd_ctxt_user | varchar(30) | Yes | Updated by the user | No |
NOTE_UPDATEDDATE | _datetime_8 | datetime(8) | No | Updated date and time | No |
NOTE_TRAN_ID | udd_txt150 | varchar(150) | Yes | Transcation id | No |
replication_key | _bigint_8 | Bigint(8) | No | replication key | Yes |
Table Name : | |
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. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_COMPONENTNAME | _varchar_80 | varchar(80) | No | Name of the component - BASCM | Yes |
CM_PARAMCATEGORY | _varchar_15 | varchar(15) | No | 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 |
CM_PARAMTYPE | _varchar_15 | varchar(15) | No | 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 |
CM_PARAMCODE | _varchar_5 | varchar(5) | No | 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 |
CM_PARAMDESC | _varchar_80 | varchar(80) | No | Description of the parameter value | No |
CM_LANGID | _decimal_10_0 | decimal(10) | No | Language id. This is the language id of the record. | No |
CM_SORTBY | _decimal_10_0 | decimal(10) | Yes | The order in which the quick codes are fetched. | No |
CM_CREATIONDATE | _datetime_8 | datetime(8) | Yes | Created date of the record. | No |
Table Name : | |
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 " |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
PRI_OUINSTANCE | _decimal_10_0 | decimal(10) | No | Ouinstance | Yes |
PRI_PRIORITY | _decimal_10_0 | decimal(10) | No | prioritycode.Identifies level of urgency | Yes |
PRI_DESCRIPTION | _varchar_20 | varchar(20) | No | Description of the priority | No |
PRI_DESCRIPTION_UP | _varchar_20 | varchar(20) | No | Description of the Priority Stored in Upper Case for Oracle Conversion | No |
PRI_STATUS | _varchar_5 | varchar(5) | No | status of the priority | No |
PRI_COMMENTS | _varchar_255 | varchar(255) | Yes | comments during modification of the priority | No |
PRI_CREATED_BY | _varchar_10 | varchar(10) | No | User Who has created the Priority | No |
PRI_MODIFIED_BY | _varchar_10 | varchar(10) | No | User who has modified the priority | No |
PRI_CREATIONDATE | _datetime_8 | datetime(8) | No | Creation Date | No |
PRI_MODIFIEDDATE | _datetime_8 | datetime(8) | No | Modified Date | No |
PRI_TIMESTAMP | _decimal_10_0 | decimal(10) | No | Timestamp | No |
created_area_code | _varchar_40 | varchar(40) | No | Area code | No |
Table Name : | |
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 ident |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
REGC_OUINSTANCE | _decimal_10_0 | decimal(10) | No | Ouinstance | Yes |
REGC_REGULATORY_CODE | _varchar_25 | Varchar(25) | No | Regulatory Code | Yes |
REGC_DESCRIPTION | _varchar_80 | varchar(80) | No | Description of the Regulatory | No |
REGC_DESCRIPTION_UP | _varchar_80 | varchar(80) | No | Description of the Regulatory Authority Stored in Upper Case for Oracle Conversion | No |
REGC_ADDRESS | _varchar_255 | varchar(255) | Yes | Address | No |
REGC_COUNTRY | udd_country | varchar(40) | Yes | Country | No |
REGC_COUNTRY_UP | udd_country | varchar(40) | Yes | Country in Upper Case for Oracle Conversion | No |
REGC_STATUS | _varchar_15 | varchar(15) | No | status of the regulatory | No |
REGC_COMMENTS | _varchar_255 | varchar(255) | Yes | comments during modification of the regulatory | No |
REGC_CREATIONDATE | _datetime_8 | datetime(8) | Yes | Creation Date | No |
REGC_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Modified Date | No |
REGC_CREATED_BY | udd_ctxt_user | varchar(30) | Yes | User Who has created the regulatory | No |
REGC_MODIFIED_BY | udd_ctxt_user | varchar(30) | Yes | User Who has Modified the regulatory | No |
REGC_TIMESTAMP | _decimal_10_0 | decimal(10) | No | Timestamp | No |
Table Name : | |
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 multiply |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
TMC_OUINSTANCE | _decimal_10_0 | decimal(10) | No | Ouinstance | Yes |
TMC_MANHRS_IN_DAY | _decimal_28_0 | decimal(28) | Yes | Manhours in a day | No |
TMC_MANDAYS_IN_WK | _decimal_28_0 | decimal(28) | Yes | Mandays in a week | No |
TMC_MANDAYS_IN_MONTH | _decimal_28_0 | decimal(28) | Yes | Mandays in a month | No |
TMC_WORK_START_TIME | _datetime_8 | datetime(8) | Yes | Work Start Time | No |
TMC_SUNDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether sunday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_MONDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether monday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_TUESDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether tuesday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_WEDNESDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether wednesday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_THURSDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether thursday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_FRIDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether friday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_SATURDAY_WKLYOFF_FLAG | _varchar_5 | varchar(5) | Yes | This indicates whether saturday is a weekly holiday or not. This will have the following values Code Value -------- -------- Y Yes N No | No |
TMC_CREATED_BY | _varchar_30 | varchar(30) | Yes | User Who has created the Time Conversion Factor | No |
TMC_MODIFIED_BY | _varchar_30 | varchar(30) | Yes | User Who has Modified the Time Conversion Factor | No |
TMC_CREATIONDATE | _datetime_8 | datetime(8) | Yes | Creation Date | No |
TMC_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Modified Date | No |
TMC_TIMESTAMP | _decimal_10_0 | decimal(10) | No | Timestamp | No |
created_area_code | _varchar_40 | varchar(40) | Yes | area code | No |
Table Name : | |
Comment : | cm_accountinfo_dtl |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
company_code | fin_companycode | varchar(10) | Yes | company_code | No |
tran_no | fin_documentnumber | varchar(18) | Yes | tran_no | No |
sequence_no | fin_sequence | int(4) | Yes | sequence_no | No |
timestamp | _Int_0 | int(0) | Yes | timestamp | No |
account_code | fin_accountcode | varchar(32) | Yes | account_code | No |
crdr_flag | fin_cmbflag | varchar(4) | Yes | crdr_flag | No |
currency | fin_currencycode | varchar(5) | Yes | currency | No |
tran_amt | fin_amount | numeric(13) | Yes | tran_amt | No |
fb_id | fin_financebookid | varchar(20) | Yes | fb_id | No |
costcenter_code | fin_costcentercode | varchar(10) | Yes | costcenter_code | No |
analysis_code | fin_analysiscode | varchar(5) | Yes | analysis_code | No |
subanalysis_code | fin_subanalysiscode | varchar(5) | Yes | subanalysis_code | No |
base_erate | fin_exchangerate | numeric(9) | Yes | base_erate | No |
base_amt | fin_amount | numeric(13) | Yes | base_amt | No |
pbc_erate | fin_exchangerate | numeric(9) | Yes | pbc_erate | No |
pbase_amt | fin_amount | numeric(13) | Yes | pbase_amt | No |
tran_type | fin_transactiontype | varchar(40) | Yes | tran_type | No |
createdby | fin_ctxt_user | varchar(30) | Yes | createdby | No |
createddate | _datetime_8 | datetime(8) | Yes | createddate | No |
modifiedby | fin_ctxt_user | varchar(30) | Yes | modifiedby | No |
modifieddate | _datetime_8 | datetime(8) | Yes | modifieddate | No |
replication_key | _bigint_8 | Bigint(8) | No | replication key | Yes |
Table Name : | |
Comment : | cm_accountinfo_hdr |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
company_code | fin_companycode | varchar(10) | Yes | company_code | No |
tran_no | fin_documentnumber | varchar(18) | Yes | tran_no | No |
timestamp | _Int_0 | int(0) | Yes | timestamp | No |
tran_type | fin_transactiontype | varchar(40) | Yes | tran_type | No |
tran_date | _datetime_8 | datetime(8) | Yes | tran_date | No |
post_date | _datetime_8 | datetime(8) | Yes | post_date | No |
ref_tranno | fin_documentnumber | varchar(18) | Yes | ref_tranno | No |
type_flag | fin_cmbflag | varchar(4) | Yes | type_flag | No |
resou_id | fin_ouinstid | int(4) | Yes | resou_id | No |
createdby | fin_ctxt_user | varchar(30) | Yes | createdby | No |
createddate | _datetime_8 | datetime(8) | Yes | createddate | No |
modifiedby | fin_ctxt_user | varchar(30) | Yes | modifiedby | No |
modifieddate | _datetime_8 | datetime(8) | Yes | modifieddate | No |
replication_key | _bigint_8 | Bigint(8) | No | Replication Key | Yes |
Table Name : | |
Comment : | CM_AIRCRAFT_MOD_HDR |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_AIRMOD_CREATED_OUINST | _decimal_10_0 | decimal(10) | No | ouinstance | No |
CM_AIRMOD_NO | _varchar_32 | varchar(32) | No | Aircraft Mod no | No |
CM_AIRMOD_DESC | _varchar_150 | varchar(150) | Yes | Mod description | No |
CM_AIRMOD_STATUS | _varchar_5 | varchar(5) | Yes | Mod status | No |
CM_AIRMOD_REMARKS | _varchar_150 | varchar(150) | Yes | Mod Remarks | No |
CM_AIRMOD_MODIFIED_BY | _varchar_15 | varchar(15) | Yes | Mod attributes modified by | No |
CM_AIRMOD_MODIFIED_DATE | _datetime_8 | datetime(8) | Yes | Mod attributes modified date | No |
CM_AIRMOD_CREATED_BY | _varchar_15 | varchar(15) | Yes | Mod attributes Created by | No |
CM_AIRMOD_CREATED_DATE | _datetime_8 | datetime(8) | Yes | Mod attributes created date | No |
CM_AIRMOD_TIMESTAMP | _int_0 | int(0) | Yes | Time stamp | No |
CM_AIRMOD_ModCls | udd_flag2 | varchar(25) | Yes | Mod classification | No |
CM_AIRMOD_ModCat | udd_flag2 | varchar(25) | Yes | Mod catergory | No |
CM_AIRMOD_ModATA | udd_atanumber | varchar(16) | Yes | Mod ATA | No |
CM_AIRMOD_MNOBJECT | udd_designparamcode | varchar(5) | Yes | Mod Maintenance object | No |
replication_key | _bigint_8 | Bigint(8) | No | Replication Key | Yes |
Table Name : | |
Comment : | This table is used to store the Airline operators in the system. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
ALOPTR_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
ALOPTR_OPERATOR_CODE | _varchar_32 | varchar(32) | No | Airline Operator code | Yes |
ALOPTR_OPERATOR_NAME | _varchar_150 | varchar(150) | Yes | Airline Operator Name | No |
ALOPTR_OPERATOR_NAME_UP | _varchar_150 | varchar(150) | Yes | Airline Operator Name inUpper Case for Oracle conversion | No |
ALOPTR_OPERATOR_TYPE | _varchar_15 | varchar(15) | Yes | Airline OperatorType which takes values, IA - IATA, IC - ICAO OTH - Others | No |
ALOPTR_OPERATOR_STATUS | _varchar_5 | varchar(5) | Yes | Airline Operator Status | No |
ALOPTR_IATA_CODE_REF | _varchar_32 | varchar(32) | Yes | Airline operator code for the Type "IATA" | No |
ALOPTR_ICAO_CODE_REF | _varchar_32 | varchar(32) | Yes | Airline operator code for the Type "ICAO" | No |
ALOPTR_OTHERS_CODE_REF | _varchar_32 | varchar(32) | Yes | Airline operator code for the Type "Others" | No |
ALOPTR_MAINTENANCE_BASE | _varchar_32 | varchar(32) | Yes | Maintenance Base is one of the attribute that represets that Airline Operator. | No |
ALOPTR_MAINTENANCE_BASE_UP | _varchar_32 | varchar(32) | Yes | Maintenance Base in UpperCase for Oracle conversion | No |
ALOPTR_CALL_SIGN | _varchar_32 | varchar(32) | Yes | Call sign is one of the attribute that represets that Airline Operator. | No |
ALOPTR_CALL_SIGN_UP | _varchar_32 | varchar(32) | Yes | Call sign in Upper Case for Oracle conversion | No |
ALOPTR_CREATED_BY | _varchar_32 | varchar(32) | Yes | User who created the Airline Operator | No |
ALOPTR_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Airline Operator Code Details are created. | No |
ALOPTR_MODIFIED_BY | _varchar_32 | varchar(32) | Yes | User who modified the Airline Operator | No |
ALOPTR_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Airline Operator Code Details are modified. | No |
ALOPTR_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | This table stores all Bays associated to hangers. Note: Bay in AIS is referred to as Child WorkCenter in E.Apps |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMBAY_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
CMBAY_STATION_CODE | _varchar_32 | varchar(32) | No | Station Number | Yes |
CMBAY_HANGER_NO | _varchar_30 | varchar(30) | No | Hanger No is E.Apps WorkCenter Code | Yes |
CMBAY_BAY_NO | _varchar_30 | varchar(30) | No | This is equivalent to E.Apps child workcenter | Yes |
CMBAY_BAY_DESC | _varchar_150 | varchar(150) | Yes | This is description given to the child workcenter | No |
CMBAY_BAY_STATUS | _varchar_5 | varchar(5) | Yes | Will be "I" for "InActive" and "A" for "Active" | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | This table is used to store the Gate details of the staions where maintenance actions can be performed on the aircraft. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMGate_Created_OUInstance | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
CMGate_Station_No | _varchar_32 | varchar(32) | No | Station Number | Yes |
CMGate_Gate | _varchar_32 | varchar(32) | No | Gate no | Yes |
CMGate_Terminal | _varchar_32 | varchar(32) | Yes | Terminal no | No |
CMGate_Status | _varchar_15 | varchar(15) | Yes | gate status | No |
CMGate_Created_By | _varchar_15 | varchar(15) | Yes | User who created the Gate | No |
CMGate_Created_Date | _datetime_8 | datetime(8) | Yes | Date at which the gate is created | No |
CMGate_Modified_By | _varchar_15 | varchar(15) | Yes | User who modified the Gate | No |
CMGate_Modified_Date | _datetime_8 | datetime(8) | Yes | Date at which the gate is modified | No |
CMGate_Timestamp | _int_0 | int(0) | Yes | TimeStamp | No |
CMGATE_PREFIX | _varchar_6 | varchar(6) | Yes | Prefix | No |
CMGATE_SEQNO | _int_0 | int(0) | Yes | Sequence Number | No |
created_area_code | _varchar_40 | varchar(40) | Yes | area code | No |
Table Name : | |
Comment : | This table stores all hangers associated to stations/Base. Note: Hanger in AIS is referred to as WorkCenter in E.Apps |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMHNG_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
CMHNG_STATION_CODE | _varchar_32 | varchar(32) | No | Station Number | Yes |
CMHNG_HANGER_NO | _varchar_30 | varchar(30) | No | Hanger No is E.APPs WorkCenter Code | Yes |
CMHNG_HANGER_DESC | _varchar_150 | varchar(150) | Yes | Hanger description is E.Apps WorkCenter Description | No |
CMHNG_HANGER_STATUS | _varchar_5 | varchar(5) | Yes | Will be "I" for "InActive" and "A" for "Active" | No |
created_area_code | _varchar_40 | varchar(40) | Yes | area code | No |
Table Name : | |
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 |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMOPSET_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
CMOPSET_STATION_CODE_TYPE | _varchar_25 | Varchar(25) | No | Station CodeType | Yes |
CMOPSET_CREATED_BY | _varchar_15 | varchar(15) | Yes | The User who had set the options | No |
CMOPSET_ARLNOPTR_CODE_TYPE | _varchar_25 | Varchar(25) | No | Airline Operatory Code Type | Yes |
CMOPSET_CREATEDDATE | _datetime_8 | datetime(8) | No | Date at which the Options are set by the user | No |
CMOPSET_MODIFIED_BY | _varchar_15 | varchar(15) | Yes | The User who had modified the options settings. | No |
CMOPSET_MODIFIEDDATE | _datetime_8 | datetime(8) | No | Date at which the Options are modified by the user | No |
CMOPSET_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for the concurrency check | No |
CMOPSET_MULTILVL_WBS | udd_txt20 | varchar(20) | Yes | Multi-level WBS Code | No |
CMOPSET_SOS_PRG_APP | udd_txt20 | varchar(20) | Yes | SOS Program Applicability | No |
CMOPSET_RES_SUS_REM | udd_txt20 | varchar(20) | Yes | Restrictions for Suspected Removals | No |
CMOPSET_OPTR_CODE_REF | udd_txt20 | varchar(20) | Yes | Operator Effectivity | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | The Commom 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 lik |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMQC_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
CMQC_QUICK_CODE | _varchar_25 | Varchar(25) | No | Quick code to define parameters or attributes to describe the status or classification of some business items | Yes |
CMQC_TYPE | _varchar_5 | varchar(5) | No | Quick Code Type will be FuelType/ShutDownType as of now. This is used in Flight Log component. | Yes |
CMQC_DESC | _varchar_80 | varchar(80) | Yes | Quick Code Description | No |
CMQC_STATUS | _varchar_5 | varchar(5) | Yes | Quick Code Status which can be ether "Active" or "Inactive" | No |
CMQC_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the user has created the quick code | No |
CMQC_CREATED_BY | varchar | Char(10) | Yes | The user who created the Quick Code | No |
CMQC_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the user has modified the quick code | No |
CMQC_MODIFIED_BY | varchar | Char(10) | Yes | The user who modified the Quick Code | No |
CMQC_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for the concurrency check. | No |
created_area_code | _varchar_40 | varchar(40) | Yes | area code | No |
Table Name : | |
Comment : | This table is used to store the Region details |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMReg_Created_OUInstance | _decimal_10_0 | decimal(10) | No | Ouinstance | Yes |
CMReg_Region | _varchar_32 | varchar(32) | No | Region | Yes |
CMReg_Region_desc | _varchar_150 | varchar(150) | Yes | Region Description | No |
CMReg_Status | _varchar_15 | varchar(15) | Yes | Region Status 1. Active 2. Inactive | No |
CMReg_Created_By | _varchar_15 | varchar(15) | Yes | User who created the Region | No |
CMReg_Created_Date | _datetime_8 | datetime(8) | Yes | Date at which the Region is created | No |
CMReg_Modified_By | _varchar_15 | varchar(15) | Yes | User who modified the Region | No |
CMReg_Modified_Date | _datetime_8 | datetime(8) | Yes | Date at which the Region is modified | No |
CMReg_Timestamp | _int_0 | int(0) | Yes | Timestamp | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | Stores System Parameter Option Settings. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CMSYSPRM_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OU Instance | Yes |
CMSYSPRM_OPTION_CODE | _varchar_5 | varchar(5) | No | System Parameter Option Code | Yes |
CMSYSPRM_OPTION_VALUE | _varchar_80 | varchar(80) | No | Option Value | Yes |
CMSYSPRM_CREATEDDATE | _datetime_8 | datetime(8) | No | Created Date | No |
CMSYSPRM_CREATED_BY | _varchar_10 | varchar(10) | No | Created By | No |
Table Name : | |
Comment : | This table is used to record the Delays. During the Time of Arrival and Departure of Aircrafts delays can occur. To record the delay information of Aircrafts, Delay codes can be used. Delay codes can be identified with Delay Description and Delay Type. D |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
DLYCD_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
DLYCD_DELAY_CODE | _varchar_25 | Varchar(25) | No | Delay Code | Yes |
DLYCD_CATEGORY | _varchar_25 | Varchar(25) | No | Delay Category | Yes |
DLYCD_DESC | _varchar_80 | varchar(80) | Yes | Description of the Delay Code. | No |
DLYCD_DESC_UP | _varchar_80 | varchar(80) | Yes | Description of the Delay Code in Upper case. | No |
DLYCD_STATUS | _varchar_5 | varchar(5) | Yes | Status of the delay. | No |
DLYCD_DELAY_TYPE | _varchar_5 | varchar(5) | Yes | 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 |
DLYCD_DELAY_ON | _varchar_5 | varchar(5) | Yes | This will be either "Departure" or "Arrival" | No |
DLYCD_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Delay code is recorded | No |
DLYCD_CREATED_BY | udd_ctxt_user | varchar(30) | Yes | The user who created the Delay Code | No |
DLYCD_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Delay code is modified. | No |
DLYCD_MODIFIED_BY | udd_ctxt_user | varchar(30) | Yes | The user who modified the Delay Code | No |
DLYCD_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp | No |
DLYCD_RELANALYIS | designparamcode | varchar(5) | Yes | To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | cm_dunning_dtl |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
company_code | fin_companycode | varchar(10) | No | company code | Yes |
dunning_date | _datetime_8 | datetime(8) | No | dunning date | Yes |
sequence_no | fin_lineno | int(4) | No | sequence no | Yes |
fb_id | fin_financebookid | varchar(20) | No | fb_id | Yes |
doc_no | fin_documentnumber | varchar(18) | No | document no | Yes |
doc_type | fin_cmbflag | varchar(4) | No | document type | Yes |
term_no | fin_paytermcode | varchar(15) | No | term no | Yes |
cust_area | fin_ouinstid | int(4) | No | customer area | Yes |
timestamp | _Int_0 | int(0) | No | timestamp | No |
cust_code | fin_customer_id | varchar(18) | Yes | customer code | No |
doc_date | _datetime_8 | datetime(8) | Yes | document date | No |
due_date | _datetime_8 | datetime(8) | Yes | due_ date | No |
due_amt | fin_amount | numeric(13) | Yes | due amount | No |
overdue_days | fin_integer8 | int(4) | Yes | overdue days | No |
currency | fin_currency | varchar(5) | Yes | currency | No |
overdue_amt | fin_amount | numeric(13) | Yes | overdue amount | No |
prev_dunlevel | fin_number | int(4) | Yes | previous dunlevel | No |
dunning_level | fin_number | int(4) | Yes | dunning level | No |
dunning_charge | fin_amount | numeric(13) | Yes | dunning charge | No |
custgrp_code | fin_customeraccountgroup | varchar(20) | Yes | custgrp_code | No |
bu_id | fin_buid | varchar(20) | Yes | bu_id | No |
crdr_note_no | fin_transactionnumber | varchar(18) | Yes | noteno | No |
createdby | fin_ctxt_user | varchar(30) | Yes | createdby | No |
createddate | _datetime_8 | datetime(8) | Yes | createddate | No |
modifiedby | fin_ctxt_user | varchar(30) | Yes | modifiedby | No |
modifieddate | _datetime_8 | datetime(8) | Yes | modifieddate | No |
Table Name : | |
Comment : | cm_dunning_hdr |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
company_code | fin_companycode | varchar(10) | No | company code | Yes |
dunning_date | _datetime_8 | datetime(8) | No | dunning date | Yes |
sequence_no | fin_lineno | int(4) | No | sequence no | Yes |
timestamp | _Int_0 | int(0) | No | timestamp | No |
cost_center | fin_costcentercode | varchar(10) | Yes | cost center | No |
analysis_code | fin_analysiscode | varchar(5) | Yes | analysis code | No |
subanalysis_code | fin_subanalysiscode | varchar(5) | Yes | subanalysis code | No |
resou_id | fin_ouinstid | int(4) | Yes | resou_id | No |
createdby | fin_ctxt_user | varchar(30) | Yes | createdby | No |
createddate | _datetime_8 | datetime(8) | Yes | createddate | No |
modifiedby | fin_ctxt_user | varchar(30) | Yes | modifiedby | No |
modifieddate | _datetime_8 | datetime(8) | Yes | modifieddate | No |
Table Name : | |
Comment : | cm_entity_event_mapping |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
swohdv_group_name | udd_quickcode | varchar(25) | Yes | Group name | No |
swohdv_event_id | udd_quickcode | varchar(25) | Yes | Event id | No |
swohdv_validate_flag | _bit_1 | Bit(1) | Yes | Validate flag | No |
swohdv_err_msg | udd_txt255 | varchar(255) | Yes | error msg description | No |
swohdv_group_desc | udd_txt255 | varchar(255) | Yes | group description | No |
swohdv_event_desc | udd_txt255 | varchar(255) | Yes | Event description | No |
replication_key | _bigint_8 | Bigint(8) | No | replication key | Yes |
Table Name : | |
Comment : | CM_GLI_MST |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
CM_OU_NAME | _varchar_16 | varchar(16) | No | ouinstance | No |
CM_GLI_DOMAIN | _varchar_20 | varchar(20) | Yes | CM_GLI_DOMAIN | No |
CM_GLI_ID | _varchar_20 | varchar(20) | Yes | CM_GLI_ID | No |
CM_REMARKS | _varchar_255 | varchar(255) | Yes | CM_REMARKS | No |
CM_ADDL_DETAILS | _varchar_255 | varchar(255) | Yes | CM_ADDL_DETAILS | No |
CM_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | Time stamp | No |
CM_REC_DATE | _datetime_8 | datetime(8) | Yes | CM_REC_DATE | No |
replication_key | _bigint_8 | Bigint(8) | No | Replication Key | Yes |
Table Name : | |
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 Requ |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
MDOCTYP_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
MDOCTYP_MDOC_TYPE | _varchar_15 | varchar(15) | No | Represent the types of documents that communicate the Engineering change requirements | Yes |
MDOCTYP_DESC | _varchar_150 | varchar(150) | Yes | Maintenmance Change Request Type Description | No |
MDOCTYP_PRIORITY_NO | _decimal_10_0 | decimal(10) | Yes | Priority defined for Reference Document | No |
MDOCTYP_SOURCE_CAT | _varchar_5 | varchar(5) | Yes | Signifies the source of a given MCR Document type as either "Internal" or "External" | No |
MDOCTYP_STATUS | _varchar_5 | varchar(5) | Yes | Status of the Reference Document which can be "Active" and "Inactive" | No |
MDOCTYP_CREATED_BY | _varchar_10 | varchar(10) | Yes | User who created the Reference Document. | No |
MDOCTYP_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which Reference Document is created | No |
MDOCTYP_MODIFIED_BY | _varchar_10 | varchar(10) | Yes | User who modified the Reference Document. | No |
MDOCTYP_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which Reference Document is modified. | No |
MDOCTYP_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | Timestamp | No |
MDOCTYP_APPLICABLEFOR | udd_designparamcode | varchar(5) | Yes | Applicable for | No |
MDOCTYP_MCRPROCESSING | udd_designparamcode | varchar(5) | Yes | MCR Processing | No |
MDOCTYP_DEFENGDOCTYPE | udd_flag | varchar(25) | Yes | Document type | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | CM_MMNTEVNT_MAINT_EVNT_DTL |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
MMNTEVNT_OUINSTANCE | _decimal_10_0 | decimal(10) | No | Organisation Unit | Yes |
MMNTEVNT_EVENT_CODE | _varchar_30 | varchar(30) | No | Regulatory Code | Yes |
MMNTEVNT_EVENT_DESC | _varchar_80 | varchar(80) | No | Description of the Regulatory | No |
MMNTEVNT_STATUS | _varchar_5 | varchar(5) | Yes | Address | No |
MMNTEVNT_CREATED_BY | _varchar_30 | varchar(30) | Yes | Country | No |
MMNTEVNT_CREATED_DATETIME | _datetime_8 | datetime(8) | Yes | Country in Upper Case for Oracle Conversion | No |
MMNTEVNT_MODIFIED_BY | _varchar_30 | varchar(30) | No | status of the regulatory | No |
MMNTEVNT_MODIFIED_DATETIME | _datetime_8 | datetime(8) | Yes | comments during modification of the regulatory | No |
MMNTEVNT_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | Creation Date | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |
Table Name : | |
Comment : | CM_MNTDIATT_MNT_DIATT_DTL |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
MNTDIATT_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OU Instance | Yes |
MNTDIATT_DIATT_TYPE | _varchar_25 | Varchar(25) | No | Maintenance Event Type like RECAT MRCL DPCAT | Yes |
MNTDIATT_DIATT_CODE | _varchar_25 | Varchar(25) | No | Maintenance Event Code | Yes |
MNTDIATT_DIATT_DESC | _varchar_80 | varchar(80) | No | Description of the Maintenance Event Code | No |
MNTDIATT_STATUS | _varchar_5 | varchar(5) | Yes | Status of Maintenance Event Code | No |
MNTDIATT_CREATED_BY | _varchar_30 | varchar(30) | Yes | Created User | No |
MNTDIATT_CREATED_DATETIME | _datetime_8 | datetime(8) | Yes | Date on which it is created | No |
MNTDIATT_MODIFIED_BY | _varchar_30 | varchar(30) | No | Modified User | No |
MNTDIATT_MODIFIED_DATETIME | _datetime_8 | datetime(8) | Yes | Date on which it is modified | No |
MNTDIATT_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | Timestamp | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |
Table Name : | |
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 |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
MNTTYP_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
MNTTYP_MAINT_TYPE_NO | _varchar_25 | Varchar(25) | No | Maintenance Type Number | Yes |
MNTTYP_REMARKS | _varchar_255 | varchar(255) | Yes | Remarks | No |
MNTTYP_STATUS | _varchar_5 | varchar(5) | Yes | Maintenance Type Status | No |
MNTTYP_CREATED_BY | _varchar_10 | varchar(10) | Yes | User who created the Maintenance Type | No |
MNTTYP_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Maintenance Type is created | No |
MNTTYP_MODIFIED_BY | _varchar_10 | varchar(10) | Yes | User who modified the Maintenance Type | No |
MNTTYP_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the Maintenance Type is modified | No |
MNTTYP_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for the comcurrency check | No |
Table Name : | |
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 |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
OTHOPTR_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
OTHOPTR_OPERATOR_CODE | _varchar_30 | varchar(30) | No | Airline Operator code | Yes |
OTHOPTR_OPERATOR_NAME | _varchar_150 | varchar(150) | Yes | Airline Operator Name | No |
Table Name : | |
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 ar |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
RDOCTYP_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
RDOCTYP_RDOC_TYPE | _varchar_15 | varchar(15) | No | Represent the various types of Documents (typically Manuals) which are referred in other business documents. | Yes |
RDOCTYP_DESC | _varchar_150 | varchar(150) | Yes | Reference Document Type Description | No |
RDOCTYP_STATUS | _varchar_5 | varchar(5) | Yes | Reference Document Type Status | No |
RDOCTYP_APPLICABILITY | _varchar_5 | varchar(5) | Yes | Applicability. It takes values C - Component A - Aircraft E - Engine N - None | No |
RDOCTYP_CREATEDBY | udd_ctxt_user | varchar(30) | Yes | User who created the Reference document | No |
RDOCTYP_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date of creation of Reference Document. | No |
RDOCTYP_MODIFIEDBY | udd_ctxt_user | varchar(30) | Yes | User who modified the Reference document | No |
RDOCTYP_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date of modification of Reference Document. | No |
RDOCTYP_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for concurrency check | No |
RDOCTYP_MAINTLIB | _varchar_5 | varchar(5) | Yes | Library Maintenace Flag | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | This table is used to store the various remarks given for the particular record. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
RMVRSN_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
RMVRSN_REASON_CODE | _varchar_20 | varchar(20) | No | Represents the various reasons for removal of a component from the aircraft. | Yes |
RMVRSN_DESC | _varchar_255 | varchar(255) | Yes | Description of the reason for Removal | No |
RMVRSN_DESC_UP | _varchar_255 | varchar(255) | Yes | Description of Reason for Removal in Upper Case for Oracle Conversion | No |
RMVRSN_STATUS | _varchar_5 | varchar(5) | Yes | Removal Reason Staus which takes value either "Active" or "Inactive" | No |
RMVRSN_CATEGORY | _varchar_25 | Varchar(25) | Yes | Reason Category is to categorize various reasons identified. | No |
RMVRSN_CREATED_BY | _varchar_10 | varchar(10) | Yes | The user who created the record | No |
RMVRSN_CREATEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the reason for removal is created. | No |
RMVRSN_MODIFIED_BY | _varchar_10 | varchar(10) | Yes | The user who modified the record | No |
RMVRSN_MODIFIEDDATE | _datetime_8 | datetime(8) | Yes | Date at which the reason for removal is modified. | No |
RMVRSN_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp | No |
RMVRSN_RELANALYIS | designparamcode | varchar(5) | Yes | To Store the Reliability Analysis ? with values RE- Required, NREQ- Not Required | No |
RMVRSN_REMTYPE | designparamcode | varchar(5) | Yes | To store the Removal Type with values "SCH" - Scheduled, "UNSCH"- Unscheduled, "OTH"- Others | No |
RMVRSN_BASISREMOVAL | designparamcode | varchar(5) | Yes | To store the Basic Removal? with values "Y"- Yes, "N"- No | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
Comment : | This table is used to store the Staions 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 ca |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
STNDTL_CREATED_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
STNDTL_STATION_NO | _varchar_32 | varchar(32) | No | Station Number | Yes |
STNDTL_STATION_DESC | _varchar_150 | varchar(150) | Yes | Station Description | No |
STNDTL_STATION_DESC_UP | _varchar_150 | varchar(150) | Yes | STNDTL_STATION_DESC_UP | No |
STNDTL_STATION_STATUS | _varchar_5 | varchar(5) | Yes | Status of the Station which takes values either "Active" or "Inactive" | No |
STNDTL_STATION_CODE_TYPE | _varchar_15 | varchar(15) | Yes | Station code types which identifies Station takes values such as IATA, ICAO and any other Codes | No |
STNDTL_STATION_TIMEZONE_NO | _varchar_30 | varchar(30) | Yes | Represent the Time Zone Number | No |
STNDTL_STATION_OUINSTANCE | _decimal_10_0 | decimal(10) | Yes | Station OUInstance is the OUInstance to which this station belongs to | No |
STNDTL_IATA_STATION_REF | _varchar_32 | varchar(32) | Yes | Station Code for the Type "IATA" | No |
STNDTL_ICAO_STATION_REF | _varchar_32 | varchar(32) | Yes | Station Code for the Type "ICAO" | No |
STNDTL_OTHERS_STATION_REF | _varchar_32 | varchar(32) | Yes | Station Code for the Type "Others" | No |
STNDTL_CITY | _varchar_32 | varchar(32) | Yes | City at which Maintenance actions can be performed on the Aircraft | No |
STNDTL_CITY_UP | _varchar_32 | varchar(32) | Yes | STNDTL_CITY_UP | No |
STNDTL_COUNTRY | _varchar_20 | varchar(20) | Yes | Country at which Maintenance actions can be performed on the Aircraft | No |
STNDTL_COUNTRY_UP | _varchar_20 | varchar(20) | Yes | STNDTL_COUNTRY_UP | No |
STNDTL_LONGEST_RUNWAY | _varchar_32 | varchar(32) | Yes | Longest Runway. It is one geographical attribute where maintenance actions can be performed on the Aircraft. | No |
STNDTL_RUNWAY_WIDTH | _varchar_32 | varchar(32) | Yes | Runway width. It is one geographical attribute where maintenance actions can be performed on the Aircraft. | No |
STNDTL_LATITUDE | _varchar_32 | varchar(32) | Yes | Latitude at which maintenance actions can be performed on the Aircraft. | No |
STNDTL_LONGITUDE | _varchar_32 | varchar(32) | Yes | Longitude at which maintenance actions can be performed on the Aircraft. | No |
STNDTL_OVERLOAD_CAPABILITY | _varchar_5 | varchar(5) | Yes | Required for Third Party Integration. This will be either "Yes" or "No". | No |
STNDTL_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | Timestamp for Concurrency Check. | No |
StnDtl_Region | _varchar_32 | varchar(32) | Yes | Region | No |
STNDTL_CREATED_BY | _varchar_15 | varchar(15) | Yes | Created by | No |
STNDTL_CREATED_DATE | _datetime_8 | datetime(8) | Yes | Creation Date | No |
STNDTL_MODIFIED_BY | _varchar_15 | varchar(15) | Yes | Modified By | No |
STNDTL_MODIFIED_DATE | _datetime_8 | datetime(8) | Yes | Modified On | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
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. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
STNMDLEFF_CREATED_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
STNMDLEFF_STATION_NO | _varchar_32 | varchar(32) | No | Station Code | Yes |
STNMDLEFF_MODEL_OU | _decimal_10_0 | decimal(10) | No | Model OUInstance | Yes |
STNMDLEFF_MODEL_NO | _varchar_32 | varchar(32) | No | Model Number | Yes |
created_area_code | _varchar_40 | varchar(40) | No | Area code | Yes |
Table Name : | |
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 at |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
STNNVADS_CREATED_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
STNNVADS_STATION_NO | _varchar_32 | varchar(32) | No | Station code | Yes |
STNNVADS_NAVAIDS_NO | _varchar_30 | varchar(30) | No | NAVAIDS Number. | Yes |
STNNVADS__NAVAIDS_TYPE | _varchar_20 | varchar(20) | Yes | NAVAIDS TYPE | No |
STNNVADS_CLASS | _varchar_20 | varchar(20) | Yes | NAVAIDS Class. It is one of the attribute which represents NAVAIDS | No |
STNNVADS_UPDATE_FREQ | _decimal_10_0 | decimal(10) | Yes | NAVAIDS Update Frequency. It is one of the attribute which represents NAVAIDS. | No |
STNNVADS_TACAN_CHANNEL | _varchar_20 | varchar(20) | Yes | TACAN channel. It is one of the attribute which represents NAVAIDS. | No |
STNNVADS_VOICE_FLAG | _varchar_5 | varchar(5) | Yes | It is one of the attribute which represents NAVAIDS. | No |
STNNVADS_STATION_CALL_NAME | _varchar_80 | varchar(80) | Yes | Station Call name. It is one of the attribute which represents NAVAIDS. | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |
Table Name : | |
Comment : | This table Stores the Day Light Saving Details. |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
TZDLS_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUInstance | Yes |
TZDLS_TIMEZONE_NO | _varchar_30 | varchar(30) | No | Time Zone Number | Yes |
TZDLS_CAL_YEAR_NO | _decimal_10_0 | decimal(10) | No | Calendar Year Number | Yes |
TZDLS_START_MONTH_CODE | _varchar_5 | varchar(5) | Yes | Starting Month | No |
TZDLS_START_DATETIME | _datetime_8 | datetime(8) | Yes | Starting Date | No |
TZDLS_ENDING_MONTH_CODE | _varchar_5 | varchar(5) | Yes | Ending Month | No |
TZDLS_ENDING_DATETIME | _datetime_8 | datetime(8) | Yes | Ending Date | No |
TZDLS_DIFF_FROM_UTC | _float_53 | float(53) | Yes | This field will have the difference value from UTC as what the user enters | No |
TZDLS_DIFF_FROM_UTC_INMIN | _float_53 | float(53) | Yes | Difference from UTC stored in minutes | No |
TZDLS_TIME_UNIT | _varchar_5 | varchar(5) | Yes | Time Unit Code - Can be Days or Minutes | No |
TZDLS_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for the Concurrency Check | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area code | No |
Table Name : | |
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 Savin |
Column Name | UDD | Data Type | Is NULL? | Comment | Is PK? |
TZDTL_OUINSTANCE | _decimal_10_0 | decimal(10) | No | OUinstance | Yes |
TZDTL_TIMEZONE_NO | _varchar_30 | varchar(30) | No | Time Zone No | Yes |
TZDTL_TIMEZONE_DESC | _varchar_150 | varchar(150) | Yes | Time Zone Description | No |
TZDTL_TIMEZONE_DESC_UP | _varchar_150 | varchar(150) | Yes | Time Zone Description in Upper Case for Oracle Conversion | No |
TZDTL_TIMEZONE_STATUS | _varchar_5 | varchar(5) | Yes | Status of Time Zone | No |
TZDTL_GMT_CONV_FACTOR | _float_53 | float(53) | Yes | 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 fiel | No |
TZDTL_DIFF_FROM_UTC | _float_53 | float(53) | Yes | This field will have the difference value from UTC as what the user enters | No |
TZDTL_DIFF_FROM_UTC_INMIN | _decimal_10_0 | decimal(10) | Yes | Difference from UTC stored in minutes | No |
TZDTL_TIME_UNIT | _varchar_10 | varchar(10) | Yes | Time Unit Code - Can be Days or Minutes | No |
TZDTL_CREATED_BY | varchar | Char(10) | Yes | User who created the Time Zone. | No |
TZDTL_CREATED_DATE | _datetime_8 | datetime(8) | Yes | Date at which the Time Zone is created | No |
TZDTL_MODIFIED_BY | varchar | Char(10) | Yes | User who modified the Time Zone. | No |
TZDTL_MODIFIED_DATE | _datetime_8 | datetime(8) | Yes | Date at which the Time Zone is modified. | No |
TZDTL_TIMESTAMP | _decimal_10_0 | decimal(10) | Yes | TimeStamp for the concurrency check | No |
created_area_code | _varchar_40 | varchar(40) | Yes | Area Code | No |