| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | Bldg File Ptr
|
|---|
| 3 | NET SQ.FT. (#4.5)
|
|---|
| 4 | records with no entry in the DIVISION (#.6) field. The report lists the overall
|
|---|
| 5 | invalid data in any of the lookup fields
|
|---|
| 6 | file record. All occurrences of these fields are examined. The
|
|---|
| 7 | index number of the multiple with missing or invalid data is
|
|---|
| 8 | Room Number
|
|---|
| 9 | Function
|
|---|
| 10 | Key
|
|---|
| 11 | Net Sq. Ft.
|
|---|
| 12 | (#6928) file that contain an invalid value in a lookup-type or pointer
|
|---|
| 13 | that have an invalid value in one or more of the lookup fields
|
|---|
| 14 | REC IEN - lists the ENG SPACE (#6928) file internal record number
|
|---|
| 15 | ROOM NUMBER - name or number of the record (#.01 field)
|
|---|
| 16 | MULTIPLE NUM - index number of the multiple
|
|---|
| 17 | to CoreFLS. Use AEMS/MERS to enter a valid value in each lookup field listed.
|
|---|
| 18 | To do so, select the Enter New Room Space Data [ENSPROOM] option. Using this
|
|---|
| 19 | report as a reference, correct each record with invalid data in the SERVICE,
|
|---|
| 20 | KEY, FUNCTION, H-08-9 CRITERIA, or UTILITIES fields. If the value is not
|
|---|
| 21 | required, you may make the field empty (delete the existing value).
|
|---|
| 22 | *** Special Note on BUILDING FILE POINTER ***********************
|
|---|
| 23 | You cannot correct the BUILDING FILE POINTER (#.51) field using
|
|---|
| 24 | data entry in AEMS/MERS or in an editing session of VA FileMan.
|
|---|
| 25 | This field is triggered-in when you enter or edit a value in the
|
|---|
| 26 | ROOM NUMBER (#.01) field. The ROOM NUMBER format consists of:
|
|---|
| 27 | [room number]-[wing/building]-[division]
|
|---|
| 28 | Two methods are available to correct records missing a value in
|
|---|
| 29 | the BUILDING FILE POINTER:
|
|---|
| 30 | 1. You may select the record in AEMS/MERS or VA FileMan and
|
|---|
| 31 | re-type the ROOM NUMBER (#.01) field to recreate the BUILDING
|
|---|
| 32 | FILE POINTER. DO NOT ACCEPT the default value by pressing
|
|---|
| 33 | <Enter>. You must re-type the entire room number value.
|
|---|
| 34 | 2. You may request that the IRM or ADPAC re-index the 'AF'
|
|---|
| 35 | cross-reference in VA FileMan on the ROOM NUMBER (#.01) field
|
|---|
| 36 | to recreate the BUILDING FILE POINTER.
|
|---|
| 37 | If you have any difficulties contact the IRM or ADPAC for
|
|---|
| 38 | displayed on this report.
|
|---|
| 39 | NET SQUARE FEET (#4.5)
|
|---|
| 40 | that have one or more empty non-required fields
|
|---|
| 41 | correct the FUNCTION or NET SQ. FT. field by selecting the associated record
|
|---|
| 42 | in the AEMS/MERS' Enter New Room Space Data [ENSPROOM] option and entering
|
|---|
| 43 | valid data for the field that is empty.
|
|---|
| 44 | If these non-required fields are left empty, the following will
|
|---|
| 45 | occur during the CoreFLS conversion:
|
|---|
| 46 | FUNCTION (#2.6) - will be converted as empty
|
|---|
| 47 | NET SQ.FT. (#4.5) - will be defaulted to 0 (zero)
|
|---|
| 48 | REQ, INV
|
|---|
| 49 | ENG SPACE (#6928) -
|
|---|
| 50 | with missing (empty) data for the fields that are required in the CoreFLS
|
|---|
| 51 | *** Special Note on ROOM NUMBER *********************************
|
|---|
| 52 | To correct the ROOM NUMBER (#.01) field's value, select the record
|
|---|
| 53 | using the Enter New Room Space Data [ENSPROOM] option in AEMS/MERS
|
|---|
| 54 | then edit the field.
|
|---|
| 55 | re-type the ROOM NUMBER (#.01) to recreate the BUILDING FILE
|
|---|
| 56 | POINTER. DO NOT ACCEPT the default value by pressing <Enter>.
|
|---|
| 57 | You must re-type the entire room number value.
|
|---|
| 58 | ROOM NUMBER (#.01) - the record will not be converted
|
|---|
| 59 | BUILDING FILE POINTER (#.51) - the record will not be
|
|---|
| 60 | converted and will also not be
|
|---|
| 61 | included in the LOCATION
|
|---|
| 62 | This report is sorted by station. You may select a single station or ALL.
|
|---|
| 63 | found in the STATION (#2.4) field in the ENG EMPLOYEE
|
|---|
| 64 | entry in the STATION (#2.4) field.
|
|---|
| 65 | CoreFLS DATA QUALITY REPORT (File# 6929 - ENGINEERING EMPLOYEE)
|
|---|
| 66 | ENG EMPLOYEE (#6929) file that have invalid or missing (empty) values
|
|---|
| 67 | examines four fields to determine if there is a valid value in each. If there
|
|---|
| 68 | CLASSIFICATION SERIES (#10.5) -
|
|---|
| 69 | Class. Series
|
|---|
| 70 | CLASSIFICATION TITLE (#12) -
|
|---|
| 71 | Class. Title
|
|---|
| 72 | The report is sorted by station. When printing or viewing this report, you
|
|---|
| 73 | may select a single station or ALL. Select
|
|---|
| 74 | records with no entry in the STATION (#2.4) field. The report lists the overall
|
|---|
| 75 | not apply to this field.)
|
|---|
| 76 | CoreFLS system. CoreFLS is unable to function when a required field is empty;
|
|---|
| 77 | NOTE: Abbreviation for the field name used on this report appears in quotes
|
|---|
| 78 | Employee Name
|
|---|
| 79 | REC IEN - lists the ENG EMPLOYEE (#6929) file internal record number
|
|---|
| 80 | EMPLOYEE NAME - listed as
|
|---|
| 81 | FIELD NAME - abbreviation of the required field
|
|---|
| 82 | Classification Series
|
|---|
| 83 | Classification Title
|
|---|
| 84 | EMPLOYEE (#6929) file that contain an invalid value in a lookup-type or pointer
|
|---|
| 85 | an invalid value in the lookup field
|
|---|
| 86 | EMPLOYEE NAME - name of the Engineering employee (#.01 field)
|
|---|
| 87 | it will be converted as empty into CoreFLS.
|
|---|
| 88 | The missing data for these records and fields do not necessarily have to be
|
|---|
| 89 | fixed for CoreFLS. However, in doing so, it would increase the functionality
|
|---|
| 90 | of CoreFLS and provide the site with more usable data in CoreFLS after
|
|---|
| 91 | conversion. To fix these records, select the record in AEMS/MERS and enter data
|
|---|
| 92 | for the non-required fields shown on the report. Once data is entered for all
|
|---|
| 93 | non-required fields, this report should not show any remaining records to be
|
|---|
| 94 | ENG EMPLOYEE (#6929) -
|
|---|
| 95 | This report can be sorted by record number or the prefix or suffix of the
|
|---|
| 96 | PM REFERENCE (#.01) field.
|
|---|
| 97 | Please select a sort criteria (1-3)
|
|---|
| 98 | Select 1 to print the records in internal entry number (IEN) order.
|
|---|
| 99 | Select 2 to sort the PM PROCEDURES (#6914.2) records by the characters
|
|---|
| 100 | appearing to the left of the first hyphen in the PM REFERENCE (#.01) field.
|
|---|
| 101 | Select 3 to sort the PM PROCEDURES (#6914.2) records by the characters
|
|---|
| 102 | appearing to the right of the last hyphen in the PM REFERENCE (#.01) field.
|
|---|
| 103 | (For example, if the PM REFERENCE field contains
|
|---|
| 104 | AAA-bbb-ccc-DDD
|
|---|
| 105 | is the prefix and the
|
|---|
| 106 | is the suffix.)
|
|---|
| 107 | CoreFLS DATA QUALITY REPORT (File# 6914.2 - PM PROCEDURES)
|
|---|
| 108 | PM PROCEDURES (#6914.2) -
|
|---|
| 109 | PM PROCEDURES (#6914.2) file that have missing (empty) values in the fields
|
|---|
| 110 | PROCEDURE TITLE (#1)
|
|---|
| 111 | The report prints or displays in one of three sort orders: record number,
|
|---|
| 112 | prefix, or suffix. Prefix is comprised of characters appearing to the left of
|
|---|
| 113 | the first hyphen in the PM REFERENCE (#.01) field while the suffix consists
|
|---|
| 114 | of characters appearing to the right of the last hyphen in the field. (For
|
|---|
| 115 | example, if the field contains
|
|---|
| 116 | is the prefix
|
|---|
| 117 | is the suffix.) When printing or viewing this report, select one
|
|---|
| 118 | of the sort orders.
|
|---|
| 119 | The report lists the overall count of the number of problem records and
|
|---|
| 120 | within the sort order
|
|---|
| 121 | this file does not contain any lookup-type fields. This entry has been
|
|---|
| 122 | left for consistency with the other Data Cleansing reports.
|
|---|
| 123 | of the following columns:
|
|---|
| 124 | FIELD NAME - name of the field from the PM PROCEDURES (#6914.2) file
|
|---|
| 125 | by CoreFLS.)
|
|---|
| 126 | contain any lookup-type fields. This column has been left for consistency
|
|---|
| 127 | with the other Data Cleansing reports.
|
|---|
| 128 | this field)
|
|---|
| 129 | The report then lists each record in the selected sort order. Each row on the
|
|---|
| 130 | report contains the following columns:
|
|---|
| 131 | REC IEN - lists the PM PROCEDURES (#6914.2) file internal record number
|
|---|
| 132 | PM REFERENCE - PM REFERENCE (#.01) field
|
|---|
| 133 | If any PROCEDURE TITLE (#1) field remains empty at the time of
|
|---|
| 134 | conversion, the PM record in CoreFLS will not have a description.
|
|---|
| 135 | Enter RETURN to continue or '^' to exit:
|
|---|
| 136 | entire file
|
|---|
| 137 | ZZ no prefix
|
|---|
| 138 | ZZ no suffix
|
|---|
| 139 | Procedure Title
|
|---|
| 140 | Text
|
|---|
| 141 | CoreFLS system.
|
|---|
| 142 | have an empty non-required field
|
|---|
| 143 | Type <CR> to continue
|
|---|
| 144 | Type <CR> to continue, uparrow to exit:
|
|---|
| 145 | Repaint screen(Y/N): N//
|
|---|
| 146 | Carriage return to continue
|
|---|
| 147 | Repaint screen (Y/N): N//
|
|---|
| 148 | DSM-
|
|---|
| 149 | BARCODE LABEL MODULE (Equipment)
|
|---|
| 150 | LOCATION LABEL MODULE (Space File)
|
|---|
| 151 | Starting with:
|
|---|
| 152 | Property Management (PM) numbers should consist of four numbers, followed
|
|---|
| 153 | by a dash (-), followed by four more numbers. There may be an alphabetic
|
|---|
| 154 | at the end (for a grand total of ten characters), but there usually isn't.
|
|---|
| 155 | The first four numbers correspond to the Federal Supply Classification Code.
|
|---|
| 156 | The next four numbers are assigned at the site, usually by the Property
|
|---|
| 157 | Management Section in A&MM.
|
|---|
| 158 | It is the intent of VACO Program Offices to phase out PM numbers in favor of
|
|---|
| 159 | the AEMS/MERS entry number, but no official timetable has been established.
|
|---|
| 160 | Doesn't look like a standard PM number. Are you sure
|
|---|
| 161 | PM #'s look like '7025-5001'.
|
|---|
| 162 | and ending with:
|
|---|
| 163 | Your ending point does not follow your starting point. I'm confused.
|
|---|
| 164 | PM numbers look like '7025-5001'.
|
|---|
| 165 | Sorry, but there doesn't appear to be any equipment in specified range.
|
|---|
| 166 | Sort labels by LOCATION
|
|---|
| 167 | Say YES to sort labels by DIVISION, BUILDING, then by ROOM.
|
|---|
| 168 | If you say NO, labels will be sorted by VA PM #.
|
|---|
| 169 | Select BAR CODE PRINTER:
|
|---|
| 170 | NX Barcode Labels by PM #
|
|---|
| 171 | PM #
|
|---|
| 172 | Companion Printer UNAVAILABLE.
|
|---|
| 173 | MONTHLY worklist
|
|---|
| 174 | YES for a MONTHLY worklist; NO for a WEEKLY worklist.
|
|---|
| 175 | Worklist is empty.
|
|---|
| 176 | New labels only
|
|---|
| 177 | The system records the printing of equipment bar code labels. If you do not
|
|---|
| 178 | wish to have labels printed again if they have already been printed at least
|
|---|
| 179 | once, please enter 'YES' at this time.
|
|---|
| 180 | Bar Code Labels for PM Worklist
|
|---|
| 181 | Purchase Order #:
|
|---|
| 182 | There is no PURCHASE ORDER # in the Equipment File that begins with:
|
|---|
| 183 | Would you like a list of all PURCHASE ORDERS
|
|---|
| 184 | Say YES to sort labels by BUILDING, then by ROOM within BUILDING.
|
|---|
| 185 | If you say NO, labels will be sorted by EQUIPMENT ID #.
|
|---|
| 186 | Select BARCODE PRINTER:
|
|---|
| 187 | Barcode Labels by PO#
|
|---|
| 188 | PO#
|
|---|
| 189 | Bar Code Labels by SERVICE
|
|---|
| 190 | Owning Service:
|
|---|
| 191 | There is no LOCAL IDENTIFIER in the Equipment File that begins with:
|
|---|
| 192 | This will be the end point of our print job.
|
|---|
| 193 | Your entry (
|
|---|
| 194 | ) does not follow
|
|---|
| 195 | OK, including everything from
|
|---|
| 196 | If you say NO, labels will be sorted by LOCAL IDENTIFIER.
|
|---|
| 197 | All Equipment Labels (Bar Code)
|
|---|
| 198 | Local Identifier:
|
|---|
| 199 | EQUIPMENT LABEL MODULE
|
|---|
| 200 | Single Equipment Bar Code Label
|
|---|
| 201 | Single Label(s)
|
|---|
| 202 | Barcode Labels by CATEGORY
|
|---|
| 203 | Equip Cat:
|
|---|
| 204 | DVAMC
|
|---|
| 205 | Can't seem to find your Station Number. Please check File 6910 (ENG INIT
|
|---|
| 206 | PARAMETERS).
|
|---|
| 207 | Select WING:
|
|---|
| 208 | Invalid entry. Press <RETURN> to continue, '^' to exit, or
|
|---|
| 209 | for help...
|
|---|
| 210 | For all rooms in WING:
|
|---|
| 211 | Location Barcode Labels (WING)
|
|---|
| 212 | Location Barcode Labels (BUILDING)
|
|---|
| 213 | Location Barcode Label (ROOM)
|
|---|
| 214 | Location Barcode Labels (ALL)
|
|---|
| 215 | LOCATION DATA
|
|---|
| 216 | * LOCATION LABEL *
|
|---|
| 217 | LOCATION FORMAT
|
|---|
| 218 | If you say NO, labels will be sorted by Category Stock Number.
|
|---|
| 219 | Barcode Labels by CMR
|
|---|
| 220 | Would you like to specify a range of entries
|
|---|
| 221 | And ending with:
|
|---|
| 222 | You have chosen to print labels for the ENTIRE Equipment File.
|
|---|
| 223 | Equipment ID#:
|
|---|
| 224 | ENTIRE EQUIPMENT FILE
|
|---|
| 225 | Enter WING:
|
|---|
| 226 | Sorry, no such WING. Please try again or enter '^' to exit.
|
|---|
| 227 | Please select a BUILDING.
|
|---|
| 228 | Choices are:
|
|---|
| 229 | or ALL.
|
|---|
| 230 | BUILDING: ALL//
|
|---|
| 231 | There does not appear to be any equipment located on this WING
|
|---|
| 232 | ). Nothing to print.
|
|---|
| 233 | Equipment Bar Code Labels by WING
|
|---|
| 234 | WING
|
|---|
| 235 | Enter WING as defined in Space File. Would you like a list
|
|---|
| 236 | to escape...
|
|---|
| 237 | Bar Code Labels for Room
|
|---|
| 238 | Room
|
|---|
| 239 | EQUIPMENT DATA
|
|---|
| 240 | * EQUIPMENT LABEL *
|
|---|
| 241 | EQUIPMENT FORMAT
|
|---|
| 242 | NOTE: Location
|
|---|
| 243 | not properly formatted.
|
|---|
| 244 | NO BAR CODE LABEL PRINTED.
|
|---|
| 245 | You must enter a building number as it appears in the Space File. If you
|
|---|
| 246 | obtain unanticipated results, you should first check your entry against
|
|---|
| 247 | the Space File.
|
|---|
| 248 | Select a WING as defined in the Space File (#6928).
|
|---|
| 249 | Would you like to see the entries
|
|---|
| 250 | Your starting point comes after your ending point. Can't process.
|
|---|
| 251 | Would you like a companion listing for this set of labels
|
|---|
| 252 | Select PRINTER for Companion Listing:
|
|---|
| 253 | Device selected must have a MARGIN WIDTH of at least 80 char.
|
|---|
| 254 | MSM sites may not send Companion List to HOME device.
|
|---|
| 255 | Man:
|
|---|
| 256 | Servc:
|
|---|
| 257 | PM#:
|
|---|
| 258 | COMPANION LISTING (Bar Code Labels)
|
|---|
| 259 | User unknown
|
|---|
| 260 | A 'companion listing' is simply a printout on regular paper (must be at
|
|---|
| 261 | least 80 columns wide) that is intended for use in the initial application
|
|---|
| 262 | of the actual bar code labels to individual equipment items. The companion
|
|---|
| 263 | listing will contain more descriptive information than can be printed
|
|---|
| 264 | on the labels themselves, and will be sorted in the same order as the
|
|---|
| 265 | Device selection unsuccessful.
|
|---|
| 266 | Select output device:
|
|---|
| 267 | SELECT FISCAL YEAR:
|
|---|
| 268 | SELECT QUARTER:
|
|---|
| 269 | ROOM is not in proper format.
|
|---|
| 270 | The BUILDING (including DIVISION, if applicable) portion of the ROOM
|
|---|
| 271 | NUMBER must be defined in your Building File (6928.3) before this ROOM
|
|---|
| 272 | NUMBER may be added to your Space File.
|
|---|
| 273 | In this case,
|
|---|
| 274 | does not appear to be in your Building File.
|
|---|
| 275 | Enter month as an integer from 1 to 12.
|
|---|
| 276 | This CMR is not currently in use. Enter 'A' to add it to the file, 'L' to
|
|---|
| 277 | see a list of active CMR's, or '^' to abort. L//
|
|---|
| 278 | Select (1 to
|
|---|
| 279 | AUTO PRINT NEW W.O.
|
|---|
| 280 | NOTIFY W.O. REQUESTOR
|
|---|
| 281 | PM DEVICE TYPE IDENTIFIER
|
|---|
| 282 | PRINT BAR CODES ON W.O.
|
|---|
| 283 | SAFETY PRINTOUT
|
|---|
| 284 | SPACE SURVEY PRINTOUT
|
|---|
| 285 | BUILDINGS may not contain more than one hyphen.
|
|---|
| 286 | Incorrect DIVISION format.
|
|---|
| 287 | BUILDING not in proper format.
|
|---|
| 288 | <cr> to continue, '^' to stop...
|
|---|
| 289 | Responsible Official:
|
|---|
| 290 | Can't have more than four WORK ACTIONS.
|
|---|
| 291 | Can't have more than thirty (30) ALTERNATE STATION NUMBERS.
|
|---|
| 292 | This item has been reported to the Fixed Assets Package. TYPE
|
|---|
| 293 | cannot be changed until an FD document is processed.
|
|---|
| 294 | be expensed until an FD document is processed.
|
|---|
| 295 | Since this item has been reported to FAP, this field may be edited
|
|---|
| 296 | only by means of an FAP document.
|
|---|
| 297 | must follow ACQUISITION DATE
|
|---|
| 298 | Capitalized asset. DISP METHOD may be edited only by means of FAP documents.
|
|---|
| 299 | subsidiary records were set.
|
|---|
| 300 | You must use the Y2K module for this edit.
|
|---|
| 301 | ENGINEERING PROGRAM MANAGEMENT ROUTINE
|
|---|
| 302 | Sorry, but you lack the necessary SECURITY KEY!
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
