English French Notes Complete/Exclude Multiple fields can occur many times within one EQUIPMENT CATEGORY (#6911) file record. All occurrences of these fields are examined. The index number of the multiple with invalid data is displayed on this report. If any lookup field on this report is left with invalid data, it will be converted as empty into CoreFLS. CoreFLS Data Cleansing Report Instructions in the CoreFLS system. If fields appearing on this report are left empty, the This report examines the following non-required fields: TECHNICIAN (RESPONSIBLE SHOP Multiple) (#6911.01,1) FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01) PROCEDURE (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,4) file that fall between the beginning and ending names entered The report lists records in alphabetical order by Equipment Category name. FIELD NAME - name of the non-required field (Note: Frequency and Procedure fields may display a set of two multiple numbers separated by a comma. The first number represents the Responsible Shop multiple number. The second number represents the Frequency multiple number. If the second multiple number (Frequency multiple number) for these two fields is missing, there are no occurrences of the field's Frequency or Procedure for the Responsible Shop. There must be a Frequency and Procedure for each Responsible Shop in order for a PM to be generated for the Equipment Category.) ** Special Note ************************************************* The index number of the multiple with missing data is displayed on If these non-required fields remain empty, the following will occur during CoreFLS conversion: TECHNICIAN (#6911.01,1) - will be converted into CoreFLS as empty FREQUENCY (#6911.13,.01) - a PM will not be created for the Equipment Category PROCEDURE (#6911.13,4) - the PM description will be defaulted to the FREQUENCY (#6911.13,.01) followed by a hyphen (dash) and Equipment Category EQUIPMENT CATEGORY (#6911) file that have invalid or missing (empty) values in the fields that are being converted into the CoreFLS system. The report examines five fields to determine if there is a valid value in each. If there is no value in the field, it is considered to be empty. If there is a value in a lookup-type (a.k.a. pointer) field, the report examines the value to ensure that it is valid. FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01) This report lists the overall count of the number of problem records and fields detected. have at least one empty required field have invalid data in any of the lookup fields that have nothing in at least one non-required field INV: invalid data FIELD NAME - name of the field from the EQUIPMENT CATEGORY (#6911) file LOOKUP FIELDS W/ INVALID DATA - count of the number of lookup fields that contain an invalid value ( appears in this column if the field is not a lookup field.) displayed on the detail reports. Equipment Inventory compile in progress. Please try again later. Last Equipment Inventory compile done on *** Warning: Please compile the list of Equipment Inventory first *** This report is sorted by station. You may select a single station number or ALL. Please select a station (1- The list below contains the stations that have been found in the STATION (#60) field in the EQUIPMENT INV. (#6914) file. ZZ no station to display the records with no entry in the CoreFLS Data Cleansing Report (File# 6914 - EQUIPMENT INV.) Do you wish to queue the Equipment Inventory compile? Enter 'YES' to queue the Equipment Inventory compile or '^' to abort the compile. CoreFLS Data Cleansing Reports Equipment Inventory List Compile's TaskMan ID is Compiling Equipment Inventory list ... *** Aborted: another Equipment Inventory compile is currently running *** CoreFLS Equipment Inventory List by Field CoreFLS Equipment Inventory List by Record the CoreFLS system. If fields appearing on this report are left empty, the Before you use this report, you may want to run the compile to ensure you are viewing the most recent modifications. next to the field number TOTAL ASSET VALUE (#12) - Total Asset Val USE STATUS (#20) STARTING MONTH (RESPONSIBLE SHOP Multiple) (#6914.04,2) CRITICALITY (RESPONSIBLE SHOP Multiple) (#6914.04,2.7) LEVEL (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6914.43,3) STANDARD GENERAL LEDGER (#38) - STATION NUMBER (#60) - BUDGET OBJECT CODE (#61) - Admin Office The report is sorted by station number. When printing or viewing this report, you may select a single station number or ALL. Select to display the records with no entry in the STATION (#60) field. The totals for each station are as follows: file assigned to the station that have one or more empty non-required fields fields that are empty REC IEN - lists the EQUIPMENT INV. (#6914) file internal record number MFGR. EQUIPMENT NAME - name of the equipment (if there is a value in this field, you may use it to select the Equipment Inventory item) (Note: Frequency, Level, and Procedure fields may display a set of two multiple numbers separated by a comma. The first number represents the Responsible Shop multiple number. The second number represents the Frequency multiple number.) *** Special Note ************************************************ STARTING MONTH (#6914.04,2) (#6914) file record. All occurrences of these fields are examined. on this report. If the non-required fields are left empty, the following will occur during CoreFLS conversion: FREQUENCY (#6914.43,.01) - a PM will not be created for the equipment item PROCEDURE (#6914.43,4) - the PM description will be defaulted to the FREQUENCY (#6914.43,.01) followed by a hyphen (dash) and Equipment Category All other non-required fields will be converted as empty. EQUIPMENT INV. (#6914) - Totals for Station with Required Fields Missing Data with Lookup Fields w/ Invalid Data with Non-Required Fields Missing Data Total records Total fields Level Work Performed Resp Shop Criticality Starting Month MFGR. EQUIPMENT W/INVALID DATA EQUIPMENT INV. (#6914) file that have invalid or missing (empty) values in examines 30 fields to determine if there is a valid value in each. If there viewing the most recent modifications. ENTRY NUMBER (#.01) PARENT SYSTEM (#2) MFGR. EQUIPMENT NAME (#3) - Mfgr Equip Name EQUIPMENT CATEGORY (#6) - Equip Category TYPE OF ENTRY (#7) VENDOR POINTER (#10) - Vendor ACQUISITION SOURCE (#13.5) - Acq Source CATEGORY STOCK NUMBER (#18) - Cat Stock Number SERVICE POINTER (#21) - Service Ptr RESPONSIBLE SHOP (Multiple) (#6914.04,.01) - INVESTMENT CATEGORY (#34) - Investment Cat WORK PERFORMED (EQUIPMENT HISTORY Multiple) (#6914.02,9) The report is sorted by station number. When printing or viewing this report, you may select a single station number or ALL. Select display the records with no entry in the STATION (#60) field. The report lists the overall count of the number of problem records and fields detected. file assigned to the station that have invalid data in any of the lookup fields appears in this column if the field is not a lookup field.) non-required fields ( appears in this column if non-required does not apply to this field.) RESPONSIBLE SHOP (#6914.04,.01) WORK PERFORMED (#6914.02,9) system. CoreFLS is unable to function when a required field is empty; Mfr Equip Name assigned to the station one or more empty required fields FIELD NAME - name or abbreviation of the required field The only two fields that you cannot correct in this manner are the ENTRY NUMBER (#.01) and the WORK PERFORMED (#6914.02,9) fields. To correct these fields, contact the IRM or ADPAC for assistance. The following is a multiple-type field: If the required fields are left empty, the following will occur ENTRY NUMBER (#.01) - the entire record will not be converted MFGR. EQUIPMENT NAME (#3) - the EQUIPMENT CATEGORY (#6) field will be used as a default CMR (#19) - two dashes (--) will be used as a default LOCATION (#24) - the station number will be used as a default WORK PERFORMED (#6914.02,9) - the equipment work order will not All other required fields will be converted as empty. INV. (#6914) file that contain an invalid value in a lookup-type or pointer This report is sorted by station number. When printing or viewing this file assigned to the station. have an invalid value in one or more of the lookup fields FIELD NAME - name or abbreviation of the lookup field multiple number.) SHOP (#6914.04,.01) field. To correct this field, contact the IRM or ADPAC for assistance. If any of the lookup fields on this report is left with invalid Fund Serial # Type of Entry Entry Number Parent System WORK ORDER # (#6920) Work Order compile in progress. Please try again later. Last Work Order compile done on *** Warning: Please compile the list of Work Orders first *** found in the LOCATION (#3) field in the WORK ORDER # no entry in the LOCATION (#3) field. CoreFLS DATA QUALITY REPORT (File# 6920 - WORK ORDER) Do you wish to queue the Work Order compile? Enter 'YES' to queue the Work Order compile or '^' to abort the compile. CoreFLS Data Cleansing Reports Work Order List Compiling Work Order list ... *** Aborted: another Work Order compile is currently running *** CoreFLS Work Order List by Field CoreFLS Work Order List by Record WORK ORDER ORDER # (#6920) file that contain an invalid value in a lookup-type or pointer field. An invalid value is defined as a value that either does not have an ENTERED BY (#7.5) ASSIGNED TECH (TECHNICIANS ASSIGNED Multiple) (#6920.02,.01) SHOP (TECHNICIANS ASSIGNED Multiple) (#6920.02,2) - Tech Assigned- Shop EQUIPMENT ID# (#18) WORK ACTION (Multiple) (#6920.035,.01) WORK CENTER CODE (#35.5) records with no entry in the LOCATION (#3) field. an invalid value in one or more of the lookup fields invalid data REC IEN - lists the WORK ORDER # (#6920) file internal record number WORK ORDER NUMBER - WORK ORDER # (#.01) field Use AEMS/MERS to enter a valid value in the lookup field. If you have any difficulties correcting these fields, contact the IRM or ADPAC for assistance. ASSIGNED TECH (#6920.02,.01) WORK ACTION(#6920.035,.01) (#6920) file record. All occurrences of these fields are examined. **** Conversion Note ********************************************* WORK ORDER # (#6920) file that have invalid or missing (empty) values in the fields that are being converted into the CoreFLS system. The compile examines 12 fields to determine if there is a valid value in each. If there is no value in the field, it is considered to be empty. If there is a value in a lookup-type (a.k.a. pointer) field, the compile examines the value to ensure TASK DESCRIPTION (#6) WORK PERFORMED (#39) This report is sorted by division. When printing or viewing this report, you contain an invalid value ( to this field.) LOCATION and EQUIPMENT ID# are two fields that are checked together. It is required that at least one of these two fields have data for CoreFLS. In other words if both fields are empty for a record, the record is flagged to be corrected. Entering data in either of the two fields corrects the record so it no longer appears on the report. These fields are noted on this report as Location/Equip ID# the detail reports. Entered By Shop Work Center Code Work Action Assigned Tech the CoreFLS system. If fields appearing on this report are left empty, the Each row contains the following columns: *** Conversion Note ********************************************* TASK DESCRIPTION (#6) - Data in WORK PERFORMED (#39) will be used as the default. If both fields are empty then the Task Description will be converted as empty ENTERED BY (#7.5) - Default is PRIORITY (#17) - Default is 0 (zero) STATUS (#32) - when STATUS is empty and: DATE COMPLETED is: DATE STARTED is: DEFAULT STATUS is: empty not empty In Progress empty empty Waiting for Approval not empty > 6 months* not empty =< 6 months* *from the scheduled deployment date WARNING: Fields in orders may not be editable after conversion to CoreFLS WORK CENTER CODE (#35.5) - If the first two characters of the Work Order # is then the default will be , otherwise the default WORK ORDER # (#6920) - Enter RETURN to continue you must enter valid data in these fields prior to conversion. the records with no entry in the LOCATION (#3) field. file assigned to the division Use AEMS/MERS to enter a valid value in either of these two fields. If you have any difficulties correcting these fields, contact the IRM or ADPAC together. It is required that at least one of these two fields have data for the CoreFLS conversion. In other words, if both fields are empty for a record, the record is flagged to be corrected. Entering data in either of the two fields corrects the record so it no longer appears on the report. These fields are noted on this report as converted into CoreFLS. found in the DIVISION (#.6) field in the ENG SPACE to display the records with no entry in the DIVISION (#.6) field. CoreFLS DATA QUALITY REPORT (File# 6928 - ENG SPACE) ENG SPACE (#6928) file that have invalid or missing (empty) values in the fields that are being converted into the CoreFLS system. The report examines eight fields to determine if there is a valid value in each. If there in a lookup-type (a.k.a. pointer) field, the report examines the value to ensure that it is valid. ROOM NUMBER (#.01) BUILDING FILE POINTER (#.51) - #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### ####################