Revision Level Maintenance - Calculations

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 and initialized.

3.   The following information is retrieved from the Reference file.

a.   The operating system's file status codes (category 015) are retrieved.  If this category is not found, the program terminates.

b.   The date format (category 049) 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.

c.   Reference file category 409 (user/company authorization) is read to determine the plants the user is authorized to access.

d.   The default plant is retrieved from Reference File category 428 (workstation authorization).

4.   The Program Status field (PGMSTS) is set to direct program 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 on the Function Select screen (DE170S01).

a.   There are three functions to choose on the Function Select screen.

1    -           Addition

2    -           Change 

3    -           Deletion

b.   Data may be entered in the two key fields on the Function Select screen (part number and revision level), although it doesn't have to be.  If data is entered in both key fields, validation is performed.  Otherwise, the status is changed to PTL (partial) and the partial screen is displayed.  This screen is also displayed if invalid data was entered in the key fields on the Function Select screen.

c.   After valid data is entered either on the Function Select or partial screen, the status is changed to DTL (detail) and the detail screen is displayed.  Data is added or changed, then detail field validation is performed.  The transaction is posted if all the fields are valid, and report records are written for the audit trail.  If the transaction is invalid, errors are displayed and the files are not updated.

d.   Once a valid transaction is processed, the partial screen is displayed (PGMSTS = 'PTL'), and the maintenance function is repeated until a new function is selected.

e.   When the user exits the program, END is moved to program status and windup processing is performed.

2.   Function Select

a.   The Maintenance Code is entered and validated.

b.   The Part Number and Revision Level may be entered and validated.  See the Design Engineering User Manual for validation rules.

c.   A reference number may be specified to identify transactions.  The default value is the user profile name.

3.   Addition:  The following processing occurs for each addition transaction.

a.   Part number and revision level are validated on the Function Select or partial screen.  See the Design Engineering User Manual for validation rules.

b.   Effectivity date and description are validated on the detail screen.  See the Design Engineering User Manual for validation rules.

c.   If a new record is added to the Revision Level file (DEMON), the following fields default to the value specified.

d.   Report records are written to the Revision Level Audit Trail file (DE170CP) to record data base activity.

e.   Report records are written to the Revision Level Audit Trail file (DE170BP) to record data base activity.

f.    If the part is a JIT part, the part master net change flag (PMNCFL) is set for reanalysis (PMNCFL = 1), if it is set no change.  This flag is used by the Requirements Planning module.

4.   Change:  The following processing occurs for each change transaction.

a.   The revision level master record is read for inquiry to retrieve current master file values.  The changed fields are validated.  See the Design Engineering User Manual for validation rules.  If no changes are made, the transaction is invalid.

b.   After validation is complete, the Revision Level file is read for update.  This record locking read prevents other users from updating this record.  If, however, another user has updated this record since the transaction was initiated, an intervening update message is displayed.  The partial screen is displayed with this message.

c.   If the effectivity date is changed and the part is a JIT part, the part master net change flag (PMNCFL) is set for re-analysis (PMNCFL = 1), if it is currently set no change.  This flag is used by the Requirements Planning module.

d.   The part master record is updated, and the revision level record is updated.

e.   Report records are written to the Revision Level Audit Trail file (DE170CP) to record data base activity.

f.    Report records are written to the Revision Level Audit Trail file (DE170BP) to record data base activity.

5.   Deletion:  The following processing occurs for each deletion transaction.

a.   The Revision Level file is read for inquiry.

b.   After validation is complete, the Revision Level file is read for update.  This record locking read prevents other users from updating this record.  If, however, another user has updated this record since the transaction was initiated, an intervening update message is displayed.  The partial screen is displayed with this message.

c.   If the part is eligible for deletion, a warning message is displayed, requesting the user to press the ENTER key to process the deletion.

d.   If the part is a JIT part, the part master net change flag (PMNCFL) is set for re-analysis (PMNCFL = 1), if it is already set for no change.  This flag is used by the Requirements Planning module.

e.   The part master record is updated and the record is physically deleted from the Revision Level file.

f.    Report records are written to the Revision Level Audit Trail file (DE170CP) to record data base activity.

g.   Report records are written to the Revision Level Audit Trail file (DE170BP) to record data base activity.

6.   Record locks that are unique to this program are described below:

DE170E Program Menu

• Purpose
• Calculations
• Files
• Parameters
• Screens