Executarea CIM-ului în MFG/PRO
Scop: introducere de date în sistem prin programele de maintenance cu intrare din fisiere si nu de la tastatura.
Pasi:
analizarea ecranelor
pregatirea fiserului CIM
încarcarea fisierului CIM 36.17.1
verificare date încarcate (neprocesate 23223s1824x ) 36.17.3
procesare CIM 36.17.2
verificare date procesate si erori 36.17.3 si fisier de log.
CIM Interface - Formats and Troubleshooting Checklist
Introduction
One way MFG/PRO allows import of ASCII-format data into the system is loading files through the Computer Integrated Manufacturing (CIM) interface. CIM permits loading of output from other databases or from devices like bar code readers. The basic advantage of CIM (as opposed to data load) is that MFG/PRO programs actually load the data, which means that it is checked as it is loaded.
This entry covers CIM basic file formats and troubleshooting. For more information on CIM, consult MFG/PRO user documentation.
Assumptions and Prerequisites
The concepts in this entry apply to all MFG/PRO versions.
CIM Data Types
Input data consists of three types:
* Labels
* Values
* Logicals
Labels: Fields which do NOT have mathematical operations applied against them. They could be alpha or numeric. Descriptions (alpha) and customer codes (numeric) are examples of labels.
Values: Fields which will be used in mathematical operations. They must be numeric. They can contain a decimal place or negative sign(-), but no other symbols, like commas or dollar ($) signs.
Logicals: Fields that cause operations to occur within MFG/PRO. An example is the yes/no response to the "Is all the information correct?" prompt.
CIM Data Definitions and Entry Format
BATCH all the records that are to be loaded at any given time. A batch contains one or more groups.
GROUP The data sets contained between a @@batchload and @@end command line. A group may consist of one or more data sets. Each group may also be one or more records or transactions.
DATA SET: One line in the CIM file. The data required to complete that step in the transaction. If certain fields were being entered manually in MFG/PRO they would be highlighted at the same time. The fields that are highlighted indicate the values that are expected in that data set. (This may be at variance with some documentation which uses the word "group" to define such highlighted sets.)
Example:
poporc.p f 5.13 Purchase Order Receipts 08/10/94
|Purchase Order: 300 Supplier: 5005 Status: *Effective: 08/10/94*|
*Pack Slip: *Move to Next Operation: yes* |
| *Receiver: *Receive All: no* |
|
F1-Go 2-Hlp 3-Ins 4-End 6-Mnu 7-Rcl 8-Clr 9-Prev 10-Next 11-Buf
In the above screen, from Purchase Order Receipts (5.13), the highlighted fields are marked in this entry by leading and following asterisks (*). Those five fields that are highlighted make up one data set. In this case, it is the second data set of the group. The Purchase Order Number/Supplier/Status combination was the first.
Each BATCH session feeds MFG/PRO programs their data sets in GROUPS through the CIM batchload process. GROUPS are formatted in the style that can be handled by the MFG/PRO programs (see below). In other words, DATA SETS going into the CIM load must be delimited by groups.
For each group, the following format is used.
@@batchload
[data set(s)]
@@end
All characters must be in lower case, correctly spelled, with no spaces (except for the one between batchload and and as outlined below).
The sequence of the input data must match the order in which they would be typed if they were being typed directly into MFG/PRO.
* Hyphens (-) are used to indicate acceptance of the default value.
* An end-of-line indicates an end of data set.
* A space is used to separate each field.
* A period on a line by itself is processed as -END (F4).
* A tilde (~) marks a line continuation.
* The up caret (^) indicates a null.
(Note: F5 cannot be simulated.)
Data at the end of an update group can be skipped by ending the line.
Dates should be formatted the same way they are normally entered.
CIM Symbols and Structures
* Data are stored in an ASCII file.
* A batch may have more than one transaction. For complex transactions, it is advisable to have a single transaction per batch.
* Labels are usually surrounded by a set of double quote marks ("). The label will be accepted without quotes but may then be considered more than one input. If there is a space in the label, the quotes are mandatory.
* Values and logicals are NOT set in double quotes.
* Dates will work with or without double quotes (") or slashes (/).
Here's a real-data example of a CIM file.
A CIM file for Purchase Order receipts in Version 7.3G would be
structured as follows:
_____ _______ ______ _________
| |
| *Sample CIM File* |
| |
|------------>> @@batchload poporc.p <<----- ----- --------|
| "po1038" |
|*First* "pk1040" - 08/01/94 <<--*One Data Set* |
|*Group* 1 *Three Fields* |
10 10 no "ea" ---- 1400 |
|*One* . |
|*Transaction* no |
| yes |
|------------>> @@end |
|------------>> @@batchload poporc.p <<----- ----- ------| |
| "po1039" | |
| "pk1041" - 08/01/94 | |
| 1 *One* | |*One*
|*Second* 15 15 no "ea" ---- 1400 *Transaction* | |*Batch*
|*Group* . | |
no | |
|*Two* yes <<----- ----- ------| |
|*Transactions* "po1040" |
| "pk1042" - 08/01/94 |
| 1 |
| 20 20 no "ea" ---- 1402 |
| . |
| no |
| yes |
|------------>> @@end <<----- ----- --------|
** ** ** ** ** ** ** ** *******
TROUBLESHOOTING
* Are the values appropriate?
* Is there a line reading: @@batchload ?
* Is there a line reading: @@end?
* Are the data in the correct order?
* Are there any blank lines (an extra )?
* Are there any misplaced spaces?
* Is there an end-of-line for each data set?
* Does it complete the record?
* Is there an . that "undoes" the record?
References to Written Documentation
"MFG/PRO qad.inc System Foundations, Version 7.2; March, 1993; Pages 3-38 to 3-40.
|
