Documentation >
MAC-PAC Technical Library >
Manufacturing >
Manufacturing Engineering >
Programs >
Routing Maintenance - Off-line - Purpose >
Routing Maintenance - Off-line - Calculations
Routing Maintenance - Off-line - Calculations
ME125E
A. Housekeeping
1. See Section 2.1 (Common Processing Routines - Housekeeping) for a general discussion of this subroutine. Processing specific to this program is discussed below.
2. The company name record (COMNAM) is obtained from the System Control file (CT100M).
3. The Applications Installed (category 012), the Date Format (category 049), and the Quantity Field Sizes (category 446) are retrieved from the Reference file.
B. Mainline
1. This program processes off-line transactions by plant and part.
a. Two off-line transaction files, ME120AP1 and ME120AP2, must be populated by the user. No maintenance conversation is provided to populate these files. When these files are populated, the fields CZTRAN and PSTSE must contain the appropriate values as shown below. Note, if you are maintaining routings for JIT parts, populate ME120AP2 only, do not update ME120AP1 at all.
|
|
|
|
|
OA1
|
Routing Addition - MRP Part
(ME120AP1)
|
004
|
|
OA1
|
Routing Addition - JIT Part
(ME120AP2)
|
004
|
|
OA2
|
Misc Cost Addition
|
005
|
|
OA3
|
Comment Addition
|
006
|
|
OC1
|
Routing Change
|
007
|
|
OC2
|
Misc Cost Change
|
008
|
|
OC3
|
Comment/Fixed Time Chg
|
009
|
|
OD1
|
Routing Deletion
|
001
|
|
OD3
|
Comment Deletion
|
002
|
|
OM1
|
Mass Deletion
|
003
|
b. For each transaction read from the Off-line Transaction file (ME120AL), an ME transaction register record (ME120CP1 or ME120CP2) is written. The Plant, Part Number and other key fields are then validated. If there are no errors from these validations, all detail fields are validated. For each error found during validation an ME Transaction Error Register record (ME515AP) is written.
c. If no errors are found, the Routing file (ME120M) is updated and report records are written to the ME Maintenance Audit Trail (ME120BL - ME120BP1 or ME120BP2).
d. After all transactions have been processed for a part in a particular plant, the related record on the Part Master file (DE100M) is updated, and transactions are processed for the next part.
e. The process is repeated for all transactions in the Off-line Transaction file (ME120AL).
2. Addition.
a. An ME Transaction Register record (ME120CP1 for MRP parts, or ME120CP2 for JIT parts) is written.
b. All required fields and desired optional fields are validated. See the Manufacturing User Manual Screen Section for validation rules.
c. The transaction batch quantity (RZBTQT) is formatted from the plant/part batch quantity (PMBTQT).
d. A new routing record is added to the Routing file. When the addition is complete, the routing flag (OLFLG4) and, if necessary, the cost flag (OLFLG0) are set to 1 on the parent part master record. If CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y on the parent part master record for all primary routings excluding masters.
e. If the addition is valid, an ME Maintenance Audit Trail (ME120BP1) Report record is written to record data base activity.
3. Miscellaneous Cost Addition
a. An ME Transaction Register record (ME120CP1 for MRP parts, or ME120CP2 for JIT parts) is written.
b. All required fields and desired optional fields are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.
c. A new routing record is added to the Routing file. When the addition is complete, the routing flag (OLFLG4), and if necessary, the cost flag (OLFLG0), are set to 1 on the parent part master record. If CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y on the parent part master record for all primary routings.
d. If the addition is valid, an ME Maintenance Audit Trail Report record (ME120BP1) is written.
4. Change
The following processing occurs for each routing change transaction:
a. An ME Transaction Register record (ME120CP1) is written.
b. The Routing file is read for inquiry. If the record is found, the previous fields are formatted on the audit trail record. All transaction fields are then validated according to rules detailed above for addition. Only the key fields of Plant, Part Number, Operation Number and Comment Number are required, since only those fields to be changed are specified for a change transaction. If the transaction does not involve any changes it is rejected as invalid.
c. If the transaction batch quantity (PMBTQT) of the transaction plant/part has changed, update the transaction batch quantity (RZBTQT) of the routing record.
d. If the change is valid, the routing record and the part master flags are updated. An ME Maintenance Audit Trail Report record (ME120BP2) is then written to record data base activity.
If one or more of the following fields is/are changed on a primary routing, and CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y on the parent part master record:
(i) operation type
(ii) workcenter number
(iii) crew operation flag
(iv) setup hours
(v) piece rate
(vi) number of persons
(vii) overlap percent/overlap quantity for operation type = '4' or '5'
(viii) number of machines
(ix) effectivity in-date
(x) effectivity out-date
(xi) labor hours for operation type = '6' or '7'
(xii) machine hours for operation type = '6' or '7'
(xiii) sensitivity flag for operation type = '6' or '7'
(xiv) sensitivity factor for operation type = '6' or '7'
(xv) batch quantity for sensitivity flag = 'Y' for operation type = '6' or '7'
5. Miscellaneous Cost Change
The following processing occurs for each routing change transaction:
a. An ME Transaction Register Record (ME120CP2) is written.
b. The Routing File record is read for inquiry. The current Routing file values are formatted in the "previous" fields of the audit trail record. All transaction fields are then validated according to the rules detailed above for miscellaneous cost addition. The key fields (Plant, Part Number, Operation Number, and Line Number) are required, in addition to those fields to be changed. A blank field indicates that no changes are to be made. If the transaction does not involve any changes, it is rejected as invalid.
c. If the change is valid, the routing record and the part master flags are updated. An ME Maintenance Audit Trail Report record (ME120BP2) is then written to record data base activity.
If one or more of the following fields is/are changed on a primary routing, and CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y on the parent part master record:
(i) workcenter number
(ii) operation leadtime days
(iii) effectivity in-date
(iv) effectivity out-date
6. Deletion
a. The routing record is read for inquiry to obtain the operation description.
b. An ME Transaction Register record (ME120CP1) is written.
c. All required fields and desired optional fields are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.
d. All comment routings associated with the routing requested for deletion are deleted, along with the routing itself. The routing flag (OLFLG4) and the cost flag (OLFLG0) are both set to 1 on the part master record. If CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y.
e. For each routing (that is, parent or comment) deleted from the file, an ME Maintenance Audit Trail Report record (ME120BP1) is written.
7. Mass Deletion
a. Mass deletion is possible at two levels: at the operation level, where all routings with a specified operation number are deleted for a part in a particular plant; and at the part level, where all routings for a part in a particular plant are deleted.
b. An ME Transaction Register record (ME120CP1) is written.
c. All required fields and desired optional fields are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.
d. The Routing file is checked to ensure that at least one routing record exists for the specified plant/part at the requested deletion level. All routings for the plant/part are deleted at the requested level from the Routing file.
e. The routing flag (OLFLG4) and the cost flag (OLFLG0) are both updated on the part master record. If CPINST = Y, the labor requirements reschedule flag (PMLRCP) is set to Y.
f. For each routing (that is, parent or comment) deleted from the file, an ME Maintenance Audit Trail Report record (ME120BP1) is written.
8. Comment Maintenance
a. Comments may be maintained for an existing routing record. Additions, changes, and deletions of comments are allowed.
b. An ME Transaction Register Report record (ME120CP1 - for non- miscellaneous routings or ME120CP2 - for miscellaneous routings) is written.
c. The Routing file is read for inquiry to see that the parent routing (Comment Number = 00) exists.
d. All required fields and desired optional fields are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.
e. The addition, change, or deletion of comments is then processed. The Routing file is read for inquiry. For a comment addition, the comment record must not exist. For a comment change or deletion, the comment record must already exist. If an existing comment is being changed, the "previous" fields are formatted on the ME Maintenance Audit Trail record (ME120BP2).
f. Once validation is complete, the Routing file is updated and the routing flag (OLFLG4) on the part master is set to 1.
g. An ME Maintenance Audit Trail (ME120BL) Report record is written (ME120BP1 for addition or deletion; ME120BP2 for change).
h. JIT routing comments that need machine and/or tool fields altered should have their additions, changes, and deletions performed via transactions entered into ME120AP1, not ME120AP2.
i. In order to blank out the Machine and/or Tool fields, special characters of "*BLNK" (5 alphanumeric digits) should be formatted into the Machine and/or Tool transaction fields (CDPPMN and CDTOCO, respectively) on ME120AP1 for change transactions. This is valid for JIT or MRP production-type routings.