Routing Maintenance - Online - Calculations

ME120E

A. Housekeeping

1. See Section 2.1 (Common Processing Routines - Housekeeping) for a general discussion of this subroutine. Processing specific to this program is described below.

2. The company name record (COMNAM) is obtained from the System Control file (CT100M).

3. Applications Installed (category 012), the Date Format (category 049), and the Quantity Field Sizes (category 446) are retrieved from the Reference file.

4. The Reference File category 409 is read to determine if the user is authorized to all plants.

· The Reference File category 428 is read to determine the workstations default plant.

· The plant validation subroutine is called to validate the default or fast path plant.

5. Fast path fields are retrieved from the fast path data structure. If the program has been entered via fast path, then the appropriate action is taken dependent upon the contents of the fields passed as parameters. This program may be entered from the Manufacturing Engineering Routing Retrieval program (ME810E) by pressing F9 (Enter Maintenance). In such a case, the fast path data structure will contain all the fields necessary to proceed to the required maintenance screen.

B. Mainline

1. This program is directed by the program Status field.

a. The program performs key field validation and retrieves current Routing file values for display when the program Status contains PMT.

b. If a valid Maintenance Code has been entered, but the key fields are not valid, the program displays a partial screen (program Status field contains PTL) for the transaction type selected and continues to validate the key fields entered.

c. Once all key fields entered have been validated, the program displays the full screen (program Status Field contains FUL). After the user has entered data, detailed field validation is performed and the transaction, if valid, is posted. For all transactions (except the copying of a routing from one part to another) report records are written to the Maintenance Audit Trail (ME120BL) and the Transaction Register (ME120CL) files. If the transaction is invalid, all errors are displayed and the Routing file is not updated. For copy routing transactions, an Asynchronous Transaction Record (ME120DP) and a message are sent to the asynchronous message queue.

d. If maintenance code of '2' is entered from the Copy Routing Prompt screen, the program displays the Copy Routing detail select screen (program Status Field contains SL1). After the user has selected operations, validation is performed and the transaction, if valid and part number was entered from the Copy Routing Prompt screen, is posted. Asynchronous copy transaction records are written to the Asynchronous file (ME120DP) for each operation selected and a message is sent to the asynchronous message queue for the part, if entered from the Copy Routing Prompt Screen.

e. If the part to be created is not entered from the Copy Routing Prompt screen, the program displays the Copy Routing Part Select screen (program Status Field contains SL2). After the user has selected parts, validation is performed and the transaction is posted. Asynchronous copy transaction records are written to the Asynchronous file (ME120DP) for each part selected and a message is sent to the asynchronous message queue for each part selected.

f. When the user wants to exit the program, END is moved to the program Status field.

2. Function Select

a. The plant, maintenance code, part number, operation number and operation line number are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.

b. A Reference Number may be specified for transactions. The default value is the user profile name.

3. Addition

a. All required fields and desired optional fields that were entered are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.

b. The Part Master (DE100MU) and Workcenter (ME100MU) File records are read for update. A new routing record is added to the Routing file. When the addition is complete, the routing flag (OLFLG4) and 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.

c. Manufacturing Engineering Transaction Register (ME120CP1) and Maintenance Audit Trail (ME120BP1) report records are written.

d. The Engineering Change Order - In and Out and Engineering Effectivity Date In and Out fields are validated against the Engineering Change Order file and Reference File category N38 (Routing ECO Date Option).

(1) If category N38 is equal to 1, one of the Engineering Change Order In and Out fields is required and the Engineering Effectivity Date In and Out fields are defaulted from the Engineering Change Order file.

(2) If category N38 is equal to 2, the Engineering Change Order In and Out fields and Engineering Effectivity Date In and Out fields are optional. If the Engineering Change Order in and/or Out fields are entered, the Engineering Effectivity Date In and/or Out fields are defaulted from the ECO file. If the Engineering Effectivity Date In and/or Out fields are entered, the Engineering Change Order In and Out fields cannot be entered.

(3) If category N38 is equal to 3, the Engineering Change Order In and Out fields and Engineering Effectivity Date In and Out fields are optional. If the Engineering Change Order field is entered and the Effectivity Date is left blank, the effectivity date will be defaulted from the ECO file.

4. Miscellaneous Cost Addition

a. All required fields and desired optional fields that were entered are validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.

b. The Part Master and Workcenter File records are read for update. A new routing record is added to the Routing file. When the addition is complete, the routing flag (OLFLG4) and 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.

c. Manufacturing Engineering Transaction Register (ME120CP1) and Maintenance Audit Trail (ME120BP1) report records are written.

5. Change

a. The Routing File (ME120M) record is read for inquiry. All transaction fields are formatted for display on the screen. The current Routing file values are formatted in the previous fields on the audit trail record. See the Manufacturing Engineering User Manual, Screen Section for validation rules. If the user has not made any changes, then the transaction is rejected as invalid.

If the routing MPE is fixed or JIT and the sensitivity flag is Y, a warning message is sent if the batch quantities have changed.

b. The Routing File (ME120MU) record is read for update after field validation is complete. The parent part master record on the Part Master file (DE100MU) is read for update in order to update the routing flag (OLFLG4) and, if necessary, the cost flag (OLFLG0). If the Workcenter Number on the routing has changed, the workcenter record on the Workcenter file (ME100MU) is read for update, in order to lock the record. If another user has updated this routing since the transaction was initiated (intervening update), a warning message is output. The routing record is updated.

If one or more of the following fields is/are changed on a primary routing, and CPINST = Y, the LR 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) number of machines

(viii) overlap percent/overlap quantity for operation types '4' or '5'

(ix) effectivity in-date

(x) effectivity out-date

(xi) sensitivity flag

(xii) sensitivity factor

(xiii) batch quantity when sensitivity flag = Y labor or machine hours

c. Manufacturing Engineering Transaction Register (ME120CP1) and Maintenance Audit Trail (ME120BP2) report records are written.

6. Miscellaneous Cost Change

a. The Routing File (ME120M) record is read for inquiry. All routing fields are formatted for display on the screen. See the Manufacturing Engineering User Manual, Screen Section for validation rules. If the user has not made any changes, then the transaction is rejected as invalid.

b. The Routing File (ME120MU) record is read for update after field validation is complete. The parent part master record on the Part Master file (DE100MU) is read in order to update the routing flag (OLFLG4) and, if necessary, the cost flag (OLFLG0). If the workcenter has changed, the workcenter record on the Workcenter file (ME100MU) is read for update, in order to lock the record. If another user has updated this record since the transaction was initiated (intervening update), a warning message is output. The routing record is updated.

If one or more of the following fields is/are changed on a primary routing, and CPINST = Y, the LR 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

c. Manufacturing Engineering Transaction Register (ME120CP2) and Maintenance Audit Trail (ME120BP2) report records are written.

7. Deletion

a. The Routing File (ME120M) record is read for inquiry. A warning message is displayed requesting the user to press the ENTER key in order to process the deletion.

b. All comment routings associated with the routing requested for deletion are also deleted. The parent part master record (on the Part Master file (DE100MU)) is read for update to prevent maintenance by other users. The detail routing and all associated routings are deleted. The parent part master record is released from the lock after the routing flag (OLFLG4), the cost flag (OLFLG0), and, if CPINST = Y, the labor requirements reschedule flag (PMLRCP), have been updated on the part master record.

c. Manufacturing Engineering Transaction Register (ME120CP1) and ME Maintenance Audit Trail (ME120BP1) report records are written.

8. Mass Deletion

a. Mass deletion may be performed: at the operation level, where all routings with a specified Operation Number are deleted for a particular part; or at part level, where all routings for a part are deleted.

b. The Routing file is checked to ensure that at least one routing record exists for the specified part at the requested deletion level. A warning message is displayed requesting the user to press the ENTER key to process the transaction. If the ENTER key is pressed, the part master record is read and locked to prevent maintenance by other users. All routings for the part are deleted at the requested level. The routing flag (OLFLG4), the cost flag (OLFLG0), and, if CPINST = Y, the labor requirements reschedule flag (PMLRCP), are updated on the part master record.

c. The Manufacturing Engineering Transaction Register (ME120CP1) and Maintenance Audit Trail (ME120BP1) report records are written.

9. Copy Routing

a. A routing may be copied from one part to another. However, a part's routing can only be copied to a part with the same production type. An Effectivity Date must be specified for the routings to be copied. A created Effectivity Date may be also specified. The routing records will have the specified Effectivity Date.

b. The part master record associated with the routing to be copied is read for inquiry to validate the part. It must be an active, manufacturing part. The Routing file is then checked to ensure that the part has routing records. If no routings exist, an error message is displayed.

c. The part master record for the routing to be created is read for inquiry to validate the part if entered. It must be an active, manufacturing part. The Routing file is then read to see that the part has no operations which exists in the part to be copied for the operation range specified if maintenance code of '1' is entered. The Asynchronous Transaction file (ME120DP) is read for inquiry, to ensure that no transactions already exist for the part.

If part is not entered and maintenance code is '1', Copy Routing Part Select is displayed. Each part selected will be validated such that it has no operations which exists in the Part to be Copied for the operations range specified. If valid, the Asynchronous Transaction file (ME120DP) is read for inquiry, to ensure that no transactions already exist each part selected.

If maintenance code of '2' is entered, the Copy Routing Detail Select (MRP or JIT) is displayed. Each operation selected will be validated such that the operation selected does not exist in the part entered from the Copy Routing Prompt screen. If valid, the Asynchronous Transaction file (ME120DP) is read for inquiry, to ensure that no transactions already exist for the part.

If maintenance code of '2' is entered and part is not specified, the Copy Routing Part Select screen is displayed after an operation selection is made. Each part selected will be validated such that the operations selected do not exist in these parts. If valid, the Asynchronous Transaction file (ME120DP) is read for inquiry, to ensure that no transactions already exist for each part selected.

d. Once validated, a copy routing transaction record is written to the Asynchronous Transactions file (ME120DP), and a message is sent to the appropriate message queue which was specified on Reference File category N37. The transaction is then processed asynchronously by the Copy Routing program (ME130E).

If maintenance code is '1' and a part is entered from the Copy Routing prompt screen, a copy transaction record is written to the Asynchronous transaction file specifying the operation range, if entered in the Copy Routing Prompt screen and a message is sent to the message queue.

If maintenance code is '1' and part is not entered from the Copy Routing Prompt screen, a copy transaction record is written to the Asynchronous transaction file for each part selected from the Copy Routing Part Select screen with the operation range specified, if entered in the Copy Routing Prompt screen and a message is sent to the message queue also for each part selected.

If maintenance code is '2' and part is entered from the Copy Routing Prompt screen, a copy transaction record is written to the Asynchronous transaction file for each operation selected from the Copy Routing Detail Select screen and a message is sent to the message queue for the part entered.

If maintenance code is '2' and part is not entered from the Copy Routing Prompt screen, a copy transaction record is written to the Asynchronous transaction file for each operation selected from the Copy Routing Detail Select screen for each part selected from the Copy Routing Part Select screen and a message is sent to the message queue for each part selected.

If the batch quantities differ for the 'From' and 'To' parts, a warning message is sent to tell the user that rates will not be adjusted.

10. Comment Maintenance

a. Comment records may be added, changed, or deleted for existing routing records. An existing routing record has a default Comment Number of 00 or blank for a JIT part.

b. The Routing file is read for inquiry to see that the parent routing exists (Comment Number = 00). This record is then locked during comment maintenance.

c. The addition, change, or deletion transaction is validated. See the Manufacturing Engineering User Manual, Screen Section for validation rules.

d. If the transaction is valid, the update cycle is performed as follows:

(1) The Part Master Record is locked.

(2) The requested comment update is performed.

(3) The parent routing (Comment Number = 00) is relocked.

(4) The Part Master Record is released.

e. Manufacturing Engineering Transaction Register (ME120CL) and Maintenance Audit Trail (ME120BL) report records are written.

11. Record locks that are unique to this program are described below.

Application Function	File	Lock Type	Reason for Lock
Addition	Part Master DE100M	Update	To update flags and to prevent deletion.
	Workcenter ME100M	Application	To prevent deletion.
Addition (miscellaneous cost)	Part Master DE100M	Update	To update flags and to prevent deletion.
	Workcenter ME100M	Application	To prevent deletion.

Application Function	File	Lock Type		Reason for Lock
Change	Part Master DE100M	Update	To update flags and to prevent deletion.
	Workcenter ME100M	Application	To prevent deletion.
Change (miscellaneous cost)	Part Master DE100M	Update	To update flags.
	Workcenter ME100M	Application	To prevent deletion.
Deletion	Part Master Update DE100M	To update flags.
Mass Deletion	Part Master DE100M	Update	To update flags.
Copy Routing		NO RECORD LOCKS
Comment Maintenance	Part Master DE100M	Application	To prevent deletion.
	Routing ME120M	Application	To prevent maintenance by other users.

Menu

Routing Maintenance - Online - Calculations

ME120E Program Menu