Documentation >
MAC-PAC Technical Library >
Manufacturing >
Design Engineering >
Programs >
Engineering Change Maintenance - Purpose >
Engineering Change Maintenance - Calculations
Engineering Change Maintenance - Calculations
DE160E
A. Housekeeping
1. See the Common Processing Routines Section for a general discussion of this subroutine. Processing specific to this program is described below.
2. Parameter lists and key lists needed by the program are defined. Work fields and constants are defined an initialized.
3. The following information is retrieved from the Reference file (REFERP):
a. The date format (category 049) on the Reference file is retrieved. If this record is not found, a message is sent to the system operator, the date format defaults to MMDDYY, and processing continues.
4. This program is directed by the Next Step Processing Subroutine. The Program Previous Status Field (PRVSTS) is loaded as well as the Next Processing Status Field (NXTPRC) to prepare for next step processing.
B. Mainline
1. This program is directed by the Program Status Field (PGMSTS). When the status is PMT (prompt subroutine) the program validates the Maintenance Code and Engineering Change Order Number on the Function Select screen (DE160S01).
a. There are three functions to choose from on the Function Select screen. These functions are processed on one of the two screens. The screen flow is determined by the value of the Program Status field. The functions and their corresponding screen and program status values are shown below.
|
|
|
|
|
|
|
1
|
Add Engineering Change Order
|
DE160S02
|
Addition
|
DTL
|
|
2
|
Change Engineering Change Order
|
DE160S02
|
Change
|
DTL
|
|
3
|
Delete Engineering Change Order
|
DE160S02
|
Delete
|
DTL
|
b. After data is entered for a specific function, detailed field validation is performed. The transaction is posted if all the fields are valid. If the transaction is invalid, all errors are displayed and the Engineering Changes file is not updated.
c. Upon completion of a function, a partial screen is displayed to continue processing the same maintenance function without having to reenter a maintenance code. This is to help save data entry time. Once the Engineering Change Order Number is entered and validated on the partial screen, the detail screen is displayed. The same validation rules applied to the Function Select screen are applied to the detail screen.
d. When the user exits the program, END is moved to the Program Status Field and windup processing is performed.
2. Function Select
a. The Maintenance Code and the Engineering Change Order Number are entered and validated.
b. The maintenance function is repeated until a new function.
c. From the Function Select screen, command keys are available to exit, fast path, and transfer to the Engineering Changes Inquiry program (DE860E). Also, a new Reference ID can be entered via F21 (New Reference ID).
3. Addition: The following processing occurs for each addition transaction.
a. All required fields and desired optional fields entered are validated. See the Design Engineering User Manual for validation rules.
b. Report records are written to the Maintenance Transaction Register file (DE130CP).
c. Report records are written to the Maintenance Audit Trail file (DE160BP) to record data base activity.
d. Commitment control is executed.
4. Change: The following processing occurs for each change transaction.
a. The Engineering Changes file record is read for inquiry to retrieve current master file values. See the Design Engineering User Manual for validation rules. If no changes are made, the transaction is invalid.
b. If the ECO effectivity date changes and the ECO date update option (category C12) is 1 or 2 (system maintained), the product structure link with the input ECO number on the Product Structure INECO file (DE120ML2) and OUTECO file (DE120ML3) are updated to reflect the new ECO effectivity date. Report records are written to the Product Structure Transaction Register file (DE120CP) and Product Structure Audit Trail file (DE120BP) to record data base activity.
c. After validation is complete, the Engineering Changes file is read for update. While being read for update, the record is locked; thus preventing others from maintaining the same record on the Engineering Changes file.
d. The engineering changes master record is updated.
e. Report records are written to the Maintenance Transaction Register file (DE130CP).
f. Report records are written to the Maintenance Audit Trail file (DE160BP) to record data base activity.
g. Commitment control is executed.
5. Deletion
a. The Engineering Changes file is read to ensure that the ECO actually exists. Then the Product Structure file (DE120M) is read to see if that engineering change has been assigned to any parts. On the Product Structure file, there is an engineering change associated with a part, that can either be an Engineering Change Order - In (INECO) or and Engineering Change Order - Out (OUTECO). If the ECO number for deletion exists for a part in the Product Structure file (DE120M), that ECO is not eligible for deletion.
b. If the engineering change order number is eligible for deletion, a warning message is displayed, requesting the user to press the ENTER key to process the deletion.
c. The engineering change order number is physically deleted from the Engineering Changes file.
d. Report records are written to the Maintenance Transaction Register file (DE160CP).
e. Report records are written to the Maintenance Audit Trail file (DE160BP) to record data base activity.
f. Commitment control is executed.
6. Detail Screen
a. From the detail screen, command keys are available to exit, fast path, prompt, rekey data, select function, and transfer to the Engineering Changes Inquiry program (DE860E).