Documentation >
MAC-PAC Technical Library >
Manufacturing >
Design Engineering >
Programs >
Revision Level Daily Update - Purpose >
Revision Level Daily Update - Calculations
Revision Level Daily Update - Calculations
DE180E
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 System Control file (CT100M) and the Reference file (REFERP).
a. The operating system's file status codes (category 015) are retrieved to check file status on I/O routines. If the 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. The COMNAM record of the System Control file is retrieved to determine the company name. If this record is not found, the company defaults to blanks.
d. The Design Engineering control record on the System Control file is retrieved for the Revision Level Daily Update Pending Flag (RDUPEN). If this flag is N, an error message is generated and the program terminates.
|
|
|
|
|
DE100M
|
Part Master
|
MLTPU
|
|
DE170M
|
Revision Level
|
RVVER
|
B. Mainline
1. The next valid shop day is determined (NXTDAY). All non-historical revision levels effective on or before this day will be processed. If the next shop day is beyond the calendar file, the current system date is used.
2. The Revision Level logical file (DE170ML1) is organized by plant, effectivity date and part number. If the first revision level retrieved has an effectivity date greater than NXTDAY, the program will skip to the next plant. The program terminates if there are no revisions on file.
3. The following processing occurs for each revision level on the Revision Level file.
a. The corresponding part record is retrieved from the Part Master file (DE100M). If the part is not found, an error message is generated and no further processing occurs for this revision level.
b. If the Part Master record (DE100M) is found, the revision level (AMERL) and effectivity date (PMREFF) on the record are compared to the revision level (RVLVL) and effectivity date (RVEFF) on the Revision Level file (DE170M). If they are the same, then this revision level is already on the Part Master record and no updates are needed. If they are not the same, then the Part Master record needs to be updated. A record is written to the work file, indicating the change, prior to the Part Master update. If the Part's Automatic Revision Level Generation flag (PMRVGN) is 'Y' and the Revision Level is alphanumeric, an error message is written to the work file.
c. If the effectivity date of the previous revision level on the Part Master file is less than the one replacing it, the History Flag (RVHFLG) on the previous revision level record is updated to Y on the Revision Level file.
d. The next revision level is read from the Revision Level file, and steps and are repeated until the end of the file or until the revision effectivity date is greater than NXTDAY.
4. After all revision levels have been processed, a report is generated from the work file indicating the Part Master revision level changes that have taken place.
5. In windup processing, the Revision Level Daily Update Pending Flag (RDUPEN) on the DECTL1 record of the System Control file is updated with blanks.