source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0082.txt@ 779

Last change on this file since 779 was 604, checked in by George Lilly, 15 years ago

Internationalization

File size: 15.2 KB
Line 
1English French Notes Complete/Exclude
2Multiple fields can occur many times within one EQUIPMENT CATEGORY
3(#6911) file record. All occurrences of these fields are examined.
4The index number of the multiple with invalid data is displayed on
5this report.
6If any lookup field on this report is left with invalid data, it
7will be converted as empty into CoreFLS.
8CoreFLS Data Cleansing Report Instructions
9in the CoreFLS system. If fields appearing on this report are left empty, the
10This report examines the following non-required fields:
11 TECHNICIAN (RESPONSIBLE SHOP Multiple) (#6911.01,1)
12 FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01)
13 PROCEDURE (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,4)
14 file that fall between the beginning and ending names entered
15The report lists records in alphabetical order by Equipment Category name.
16FIELD NAME - name of the non-required field
17 (Note: Frequency and Procedure fields may display a set of two multiple
18 numbers separated by a comma. The first number represents the Responsible
19 Shop multiple number. The second number represents the Frequency multiple
20 number. If the second multiple number (Frequency multiple number) for
21 these two fields is missing, there are no occurrences of the field's
22 Frequency or Procedure for the Responsible Shop. There must be a
23 Frequency and Procedure for each Responsible Shop in order for a PM to
24 be generated for the Equipment Category.)
25** Special Note *************************************************
26The index number of the multiple with missing data is displayed on
27If these non-required fields remain empty, the following will
28occur during CoreFLS conversion:
29TECHNICIAN (#6911.01,1) - will be converted into CoreFLS as empty
30FREQUENCY (#6911.13,.01) - a PM will not be created for the
31 Equipment Category
32PROCEDURE (#6911.13,4) - the PM description will be defaulted to
33 the FREQUENCY (#6911.13,.01) followed by
34 a hyphen (dash) and Equipment Category
35EQUIPMENT CATEGORY (#6911) file that have invalid or missing (empty) values in
36the fields that are being converted into the CoreFLS system. The report
37examines five fields to determine if there is a valid value in each. If there
38is no value in the field, it is considered to be empty. If there is a value in
39a lookup-type (a.k.a. pointer) field, the report examines the value to ensure
40that it is valid.
41 FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01)
42This report lists the overall count of the number of problem records and
43fields detected.
44 have at least one empty required field
45 have invalid data in any of the lookup fields
46 that have nothing in at least one non-required field
47 INV: invalid data
48FIELD NAME - name of the field from the EQUIPMENT CATEGORY (#6911) file
49LOOKUP FIELDS W/ INVALID DATA - count of the number of lookup fields that
50 contain an invalid value (
51 appears in this column if the field is
52 not a lookup field.)
53displayed on the detail reports.
54Equipment Inventory compile in progress. Please try again later.
55Last Equipment Inventory compile done on
56*** Warning: Please compile the list of Equipment Inventory first ***
57This report is sorted by station. You may select a single station number or ALL.
58Please select a station (1-
59 The list below contains the stations that have been found in the
60 STATION (#60) field in the EQUIPMENT INV. (#6914) file.
61ZZ no station
62 to display the records with no entry in the
63CoreFLS Data Cleansing Report (File# 6914 - EQUIPMENT INV.)
64Do you wish to queue the Equipment Inventory compile?
65Enter 'YES' to queue the Equipment Inventory compile or '^' to abort the compile.
66<Equipment Inventory Compile Aborted>
67CoreFLS Data Cleansing Reports Equipment Inventory List
68Compile's TaskMan ID is
69Compiling Equipment Inventory list ...
70*** Aborted: another Equipment Inventory compile is currently running ***
71CoreFLS Equipment Inventory List by Field
72CoreFLS Equipment Inventory List by Record
73the CoreFLS system. If fields appearing on this report are left empty, the
74Before you use this report, you may want to run the compile to ensure you
75are viewing the most recent modifications.
76next to the field number
77 TOTAL ASSET VALUE (#12) -
78Total Asset Val
79 USE STATUS (#20)
80 STARTING MONTH (RESPONSIBLE SHOP Multiple) (#6914.04,2)
81 CRITICALITY (RESPONSIBLE SHOP Multiple) (#6914.04,2.7)
82 LEVEL (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6914.43,3)
83 STANDARD GENERAL LEDGER (#38) -
84 STATION NUMBER (#60) -
85 BUDGET OBJECT CODE (#61) -
86Admin Office
87The report is sorted by station number. When printing or viewing this
88report, you may select a single station number or ALL. Select
89to display the records with no entry in the STATION (#60) field.
90The totals for each station are as follows:
91 file assigned to the station
92 that have one or more empty non-required fields
93 fields that are empty
94REC IEN - lists the EQUIPMENT INV. (#6914) file internal record number
95MFGR. EQUIPMENT NAME - name of the equipment (if there is a value in this
96 field, you may use it to select the Equipment Inventory item)
97 (Note: Frequency, Level, and Procedure fields may display a set of two
98 multiple numbers separated by a comma. The first number represents the
99 Responsible Shop multiple number. The second number represents the
100 Frequency multiple number.)
101*** Special Note ************************************************
102 STARTING MONTH (#6914.04,2)
103(#6914) file record. All occurrences of these fields are examined.
104on this report.
105If the non-required fields are left empty, the following will occur
106during CoreFLS conversion:
107 FREQUENCY (#6914.43,.01) - a PM will not be created for the
108 equipment item
109 PROCEDURE (#6914.43,4) - the PM description will be defaulted to
110 the FREQUENCY (#6914.43,.01) followed by
111 a hyphen (dash) and Equipment Category
112All other non-required fields will be converted as empty.
113EQUIPMENT INV. (#6914) -
114Totals for Station
115with Required Fields Missing Data
116with Lookup Fields w/ Invalid Data
117with Non-Required Fields Missing Data
118Total records
119Total fields
120Level
121Work Performed
122Resp Shop
123Criticality
124Starting Month
125MFGR. EQUIPMENT
126W/INVALID DATA
127EQUIPMENT INV. (#6914) file that have invalid or missing (empty) values in
128examines 30 fields to determine if there is a valid value in each. If there
129viewing the most recent modifications.
130 ENTRY NUMBER (#.01)
131 PARENT SYSTEM (#2)
132 MFGR. EQUIPMENT NAME (#3) -
133Mfgr Equip Name
134 EQUIPMENT CATEGORY (#6) -
135Equip Category
136 TYPE OF ENTRY (#7)
137 VENDOR POINTER (#10) -
138Vendor
139 ACQUISITION SOURCE (#13.5) -
140Acq Source
141 CATEGORY STOCK NUMBER (#18) -
142Cat Stock Number
143 SERVICE POINTER (#21) -
144Service Ptr
145 RESPONSIBLE SHOP (Multiple) (#6914.04,.01) -
146 INVESTMENT CATEGORY (#34) -
147Investment Cat
148 WORK PERFORMED (EQUIPMENT HISTORY Multiple) (#6914.02,9)
149The report is sorted by station number. When printing or viewing this report,
150you may select a single station number or ALL. Select
151display the records with no entry in the STATION (#60) field. The report lists
152the overall count of the number of problem records and fields detected.
153 file assigned to the station
154 that have invalid data in any of the lookup fields
155 appears in this column if the field
156 is not a lookup field.)
157 non-required fields (
158 appears in this column if non-required
159 does not apply to this field.)
160 RESPONSIBLE SHOP (#6914.04,.01)
161 WORK PERFORMED (#6914.02,9)
162system. CoreFLS is unable to function when a required field is empty;
163Mfr Equip Name
164 assigned to the station
165 one or more empty required fields
166FIELD NAME - name or abbreviation of the required field
167The only two fields that you cannot correct in this manner are the ENTRY
168NUMBER (#.01) and the WORK PERFORMED (#6914.02,9) fields. To correct these
169fields, contact the IRM or ADPAC for assistance.
170The following is a multiple-type field:
171If the required fields are left empty, the following will occur
172 ENTRY NUMBER (#.01) - the entire record will not be converted
173 MFGR. EQUIPMENT NAME (#3) - the EQUIPMENT CATEGORY (#6) field
174 will be used as a default
175 CMR (#19) - two dashes (--) will be used as a default
176 LOCATION (#24) - the station number will be used as a default
177 WORK PERFORMED (#6914.02,9) - the equipment work order will not
178All other required fields will be converted as empty.
179INV. (#6914) file that contain an invalid value in a lookup-type or pointer
180This report is sorted by station number. When printing or viewing this
181 file assigned to the station.
182 have an invalid value in one or more of the lookup fields
183FIELD NAME - name or abbreviation of the lookup field
184 multiple number.)
185SHOP (#6914.04,.01) field. To correct this field, contact the IRM or ADPAC
186for assistance.
187If any of the lookup fields on this report is left with invalid
188Fund
189Serial #
190Type of Entry
191Entry Number
192Parent System
193WORK ORDER # (#6920)
194Work Order compile in progress. Please try again later.
195Last Work Order compile done on
196*** Warning: Please compile the list of Work Orders first ***
197 found in the LOCATION (#3) field in the WORK ORDER #
198 no entry in the LOCATION (#3) field.
199CoreFLS DATA QUALITY REPORT (File# 6920 - WORK ORDER)
200Do you wish to queue the Work Order compile?
201Enter 'YES' to queue the Work Order compile or '^' to abort the compile.
202<Work Order Compile Aborted>
203CoreFLS Data Cleansing Reports Work Order List
204Compiling Work Order list ...
205*** Aborted: another Work Order compile is currently running ***
206CoreFLS Work Order List by Field
207CoreFLS Work Order List by Record
208WORK ORDER
209ORDER # (#6920) file that contain an invalid value in a lookup-type or pointer
210field. An invalid value is defined as a value that either does not have an
211 ENTERED BY (#7.5)
212 ASSIGNED TECH (TECHNICIANS ASSIGNED Multiple) (#6920.02,.01)
213 SHOP (TECHNICIANS ASSIGNED Multiple) (#6920.02,2) -
214Tech Assigned- Shop
215 EQUIPMENT ID# (#18)
216 WORK ACTION (Multiple) (#6920.035,.01)
217 WORK CENTER CODE (#35.5)
218records with no entry in the LOCATION (#3) field.
219 an invalid value in one or more of the lookup fields
220 invalid data
221REC IEN - lists the WORK ORDER # (#6920) file internal record number
222WORK ORDER NUMBER - WORK ORDER # (#.01) field
223Use AEMS/MERS to enter a valid value in the lookup field. If you have any
224difficulties correcting these fields, contact the IRM or ADPAC for assistance.
225 ASSIGNED TECH (#6920.02,.01)
226 WORK ACTION(#6920.035,.01)
227(#6920) file record. All occurrences of these fields are examined.
228**** Conversion Note *********************************************
229WORK ORDER # (#6920) file that have invalid or missing (empty) values in the
230fields that are being converted into the CoreFLS system. The compile examines
23112 fields to determine if there is a valid value in each. If there is no
232value in the field, it is considered to be empty. If there is a value in a
233lookup-type (a.k.a. pointer) field, the compile examines the value to ensure
234 TASK DESCRIPTION (#6)
235 WORK PERFORMED (#39)
236This report is sorted by division. When printing or viewing this report, you
237contain an invalid value (
238 to this field.)
239LOCATION and EQUIPMENT ID# are two fields that are checked
240together. It is required that at least one of these two fields
241have data for CoreFLS. In other words if both fields are empty
242for a record, the record is flagged to be corrected. Entering data
243in either of the two fields corrects the record so it no longer
244appears on the report. These fields are noted on this report as
245Location/Equip ID#
246the detail reports.
247Entered By
248Shop
249Work Center Code
250Work Action
251Assigned Tech
252the CoreFLS system. If fields appearing on this report are left empty, the
253Each row contains the following columns:
254*** Conversion Note *********************************************
255TASK DESCRIPTION (#6) - Data in WORK PERFORMED (#39) will be used
256 as the default. If both fields are empty
257 then the Task Description will be
258 converted as empty
259ENTERED BY (#7.5) - Default is
260PRIORITY (#17) - Default is 0 (zero)
261STATUS (#32) - when STATUS is empty and:
262 DATE COMPLETED is: DATE STARTED is: DEFAULT STATUS is:
263 empty not empty
264In Progress
265 empty empty
266Waiting for Approval
267 not empty > 6 months*
268 not empty =< 6 months*
269 *from the scheduled deployment date
270 WARNING: Fields in
271 orders may not be editable after
272 conversion to CoreFLS
273WORK CENTER CODE (#35.5) - If the first two characters of the
274 Work Order # is
275 then the default
276 will be
277, otherwise the default
278WORK ORDER # (#6920) -
279 Enter RETURN to continue
280you must enter valid data in these fields prior to conversion.
281the records with no entry in the LOCATION (#3) field.
282 file assigned to the division
283Use AEMS/MERS to enter a valid value in either of these two fields. If you
284have any difficulties correcting these fields, contact the IRM or ADPAC
285together. It is required that at least one of these two fields
286have data for the CoreFLS conversion. In other words, if both
287fields are empty for a record, the record is flagged to be
288corrected. Entering data in either of the two fields corrects the
289record so it no longer appears on the report. These fields are
290noted on this report as
291converted into CoreFLS.
292 found in the DIVISION (#.6) field in the ENG SPACE
293 to display the records with no
294 entry in the DIVISION (#.6) field.
295CoreFLS DATA QUALITY REPORT (File# 6928 - ENG SPACE)
296ENG SPACE (#6928) file that have invalid or missing (empty) values
297in the fields that are being converted into the CoreFLS system. The report
298examines eight fields to determine if there is a valid value in each. If there
299in a lookup-type (a.k.a. pointer) field, the report examines the value to
300ensure that it is valid.
301 ROOM NUMBER (#.01)
302 BUILDING FILE POINTER (#.51) -
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.