Multi-line Routing Maintenance - Online - Calculations

A.   Housekeeping

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

2.   The following information is retrieved from the Reference file:

a.   The number of decimals for quantity fields, category 446.

b.   The applications installed, category 012.

3.   A flag is set to start processing (PRVSTS set to HSKPGS).

B.   Mainline

1.   The select screen (ME135S01) is displayed, allowing the user to enter the part number whose routing subfile is to be maintained. 

2.   After a part number is entered on the select screen, it is validated.  To be valid, the part must be on the Part Master file (DE100M), it must be active, it must be a manufactured or transfer part, and a routing copy must not be requested for the part.  If the part number is not valid, the select screen is displayed with the part number highlighted and an error message in the error message subfile.

3.   Once the part number is validated, the program reads the appropriate screen depending on whether the part is a JIT part or a MRP part.  Different screens are read because the routing data for JIT parts differs from that of MRP parts.  For MRP parts, ME135S02 is read.  For JIT parts, ME135S08 is read.  The selection screen is displayed with the routings for the part.

4.   If a command key is pressed, the appropriate function is performed.  When the ENTER key is pressed, the program validates the sequence number and maintenance code entered by the user.  If the sequence number or the maintenance code is invalid, the select screen is re-displayed with an error message in the error message subfile as described below:

a.   For update and delete transactions, the sequence number must exist and must not be blank.  For add transactions, the sequence number must be blank.  The maintenance code must be valid for each transaction (as described in the Purpose).

5.   Two different work lines are displayed depending on the routing, one for Primary/Alternate routings and one for Master/Comment routings.  The user may change any of the fields if updating an operation, add data for new operations, or confirm deletion of the line if deleting an operation.  Once the ENTER key is pressed, all changes, additions, and deletions are validated (validation for the detail screen is the same as the validation for Primary/Alternate routings).  If any fields are invalid, the work line is re-displayed with an error message.  Validation for each transaction is described below:

Primary/Alternate Routings:

a.   The overlap percentage or quantity is formatted if the part is not a JIT part.

b.   The following fields from the work line are validated for non-JIT parts:  operation number, operation line number, description, operation type, workcenter number, crew operation flag, setup hours, fixed time load, sensitivity flag, sensitivity factor, labor hours, machine hours, number of persons, number of machines, tool number, machine number, overlap percent and quantity, overlap type, effectivity in/out dates.

c.   For non-JIT parts, the piece rate is validated if the routing is not a miscellaneous piece routing; otherwise, the operation leadtime days is validated.

d.   The following fields from the work line are validated for JIT parts:  operation number, description field, workcenter number, workcenter type, operation leadtime days, labor hours, machine hours, sensitivity flag, sensitivity factor, effectivity in/out dates.

e.   If the transaction is a change transaction and the part is not a JIT part, the following validation is performed:

(1)  Required screen fields are formatted to numeric form.

(2)  If the operation is fixed, a change in only the batch quantity is valid.

(3)  Operation leadtime days is checked if routing is a miscellaneous cost; otherwise, piece rate is checked.

Master/Comment Routings:

a.   If the transaction is a change transaction, then the fields are checked to ensure that a change was made.  If no changes were made, the following validation is not performed.

b.   The operation number is validated.

c.   If the transaction is a change transaction, the part is not a JIT part, and the sub field hidden field is not equal to comment, the description is validated.

d.   If the transaction is a change transaction, the part is not a JIT part, and the routing is a master routing, the description and effectivity in/out date are validated.

e.   If the transaction is a change transaction, the part is not a JIT part, and the routing is a comment routing, the operation line number and comment number are validated.

f.    If the part is not a JIT part, the machine number and the tool number are validated.

g.   If the part is a JIT part, and the transaction is a change transaction, the following is performed.

(1)  If the subfile hidden field is not equal to comment, the description is validated.

(2)  If the routing is a master routing, the description, workcenter, labor hours, machine hours, and effectivity in/out dates are validated.

(3)  If the routing is a comment routing, the operation line number and the comment number are validated.

6.   Once the work line is validated, the master files are updated online to reflect the changes, and the selection screen is re-displayed.  File updating for each type of transaction is described below:

a.   The appropriate fields are saved depending on whether the part is a JIT part or not (the fields saved correspond to the fields validated in step 5 above).

b.   The routing record is retrieved from the Routing file (ME120M), and is validated against the Routing Update file (ME120MU).  If an error occurs, select screen is re-displayed with an error message and no updates are made.

c.   The Part Master Redefinition for Update file (DE100MU) is read to prevent deletion.  If the part master record is not found, the part is inactive, or the part is not manufactured, then the select screen is re-displayed with an error message and no updates are made.  The Part Master Labor Requirements/Capacity Planning Reschedule Flag (PMLRCP) and the Part Master Recost Flag (OLFLGO) are set for labor requirements rescheduling and recosting when a routing step is deleted, changed, or added.

Add Transactions

a.   If not a master routing, the workcenter is retrieved for update.

b.   The master files are updated:  Part Master Redefinition for Update (DE100MU), Routing Redefinition For Update (ME120MU).

c.   The audit trails are written to the Audit Trail file (ME120BL).

Change Transactions

a.   The audit trail previous records are formatted, and master files are updated.  If an intervening update occurred to a non-comment routing, the select screen is re-displayed with an error message and no updates are made.

Delete Transactions

a.   The master files are updated to reflect the deletion.

7.   If errors occurred during master file updating, the master files are unlocked; otherwise, the Copy Routing Transaction Register (ME120CL) is updated for the transaction.

8.   The routing record fields are cleared, and the Function Select screen is re-displayed.

ME135E Program Menu

• Purpose
• Calculations
• Files
• Screens