MAC-PAC Homecontact ussupport login 
Documentation > MAC-PAC Technical Library > Manufacturing > Design Engineering > Programs > Product Structure Maintenance - Multi-Line - Purpose > Product Structure Maintenance - Multi-Line - Calculations

Product Structure Maintenance - Multi-Line - Calculations

DE200E

A.   Housekeeping

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

2.   The following records are retrieved from the Reference file (REFERP):

·     ECO Date Update Option (category C12)

·     CPF File Access Status Code (category 015)

·     Date Format (category 049)

·     Quantity Field Sizes (category 446)

·     User Company/Warehouse Authorization (category 409)

·     Workstation Assignment:  Default company, warehouse, plant (category 428)

3.   A check is made to determine if a part number was passed to this program during an entry from another program.  A valid plant must be passed for the program to validate the part number.

a.   If no part number was passed, the Function Select screen is displayed, allowing the user to enter the part number.

b.   If a part number was passed, the part number is validated.  See the Design Engineering User Manual for validation rules.

·     If the part number is not valid, the Function Select screen (DE200S01) is displayed with an error message.

·     If the part number is valid, the effectivity date defaults to ALL, the Product Structure file (DE120M) is read for the part, the Part Master file (DE100M) is read to retrieve information for each first-level component of the part, and the detail subfile (DE200SF2) is loaded with this information.  The selection screen (DE200S03) is then displayed.

c.   Reference File category 409 is read to determine to which plants the user is authorized.

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

B.   Mainline

1.   The Function Select screen (DE200S01) is displayed, allowing the user to enter the part number whose bill of material is to be modified.    The user can view valid values of the field prompted (part number) by pressing F4.

2.   After a part number is entered from the Function Select screen, the part number is validated.  See the Design Engineering User Manual for validation rules.  If the part number is not valid, the Function Select screen is displayed with an error message.

3.   If the part number entered on the Function Select screen is valid:

a.   The Product Structure file (DE120M) is read to determine each component of the part.

b.   Each component is checked against the effectivity date entered on the Function Select screen. 

c.   The Part Master file (DE100M) is read for each effective component.  The unit of measure is retrieved from the file.

d.   The detail subfile (DE200SF2) is loaded with information for each effective component.  Depending on the amount of information, each component has one or two lines on the subfile.  Each line is assigned a sequence number to identify it for updating.

e.   The selection screen (DE200S03) is displayed from the subfile.

4.   On the selection screen, the user enters a sequence number, component part number, and transaction code (A for Add, C for Change, or D for Delete).  The fields are validated and the work line is displayed as described below.  The work line contains the following fields:  Quantity Per, Scrap Factor, Usage Code, Reference Code, Component Offset Days, Operation Number, Deduct Operation, Engineering Change Order-In, Engineering Effectivity Date-In, Engineering Change Order-Out, and Engineering Effectivity Date-Out.

a.   For Add transactions, the program verifies that the specified sequence number and component part number do not already exist.  If they do, the selection screen is redisplayed with an error message.  If the sequence number does not exist, the work line fields are loaded with blanks, and the work line is displayed.  The user can then enter information in the blank fields.  The user presses ENTER after information has been typed into all fields.

b.   For Update transactions, the program verifies that the specified sequence number and component part number exist.  If they do not, the selection screen is redisplayed with an error message.  If the sequence number and component part number exist, the Product Structure file (DE120M) is read for the component in the indicated line.  The work line is loaded with the product structure information and displayed.  The user can then change information in any of the work line fields.  The user presses ENTER to process the changes.

c.   For Delete transactions, the program verifies that the specified sequence number and component part number exist.  If they do not, the selection screen is redisplayed with an error message.  If the sequence number and component part number exist, the Product Structure file (DE120M) is read for the component in the indicated line.  The work line is loaded with the product structure information, all fields are protected (so the user cannot change them), and the work line is displayed.  The user presses ENTER to verify that the displayed line is to be deleted.

5.   The only fields on the Product Structure file that are not displayed on the work line are the Delivery Frequency Code and the BON Safety Stock.

a.   When a line is added, the Decimal Control Code is set equal to the number of decimal places in the Quantity Per field.

b.   If the Quantity Per field is changed, the program compares the number of decimal places in the new Quantity Per with the Decimal Control Code.  If the Quantity Per field has more decimal places, the Decimal Control Code is increased to that number.  If the Quantity Per field has more than seven decimal places, the work line is redisplayed with an error (since the Decimal Control Code cannot be more than seven).

c.   When a line is added, the Delivery Frequency and the BON Safety Stock default to zero.

6.   From the selection screen, the user can press F5 to display the detail product structure maintenance screen (DE200SF05).

a.   This screen is identical to the detail screen (DE120S02) displayed by the Product Structure Maintenance program (DE120E).  It contains all of the fields as the work line as well as the Decimal Control Code and BON safety stock.

b.   When the command key is pressed, the detail screen is loaded with information from the work line.  The Decimal Control Code is loaded from the Product Structure file (DE120M).

c.   The user can then enter or change fields on the detail screen.

d.   Bill of material comments can be added at this time via F18.  The BOM Comment Maintenance program (DE215E) is called.  See Design Engineering Program Documentation for DE215E for further processing information.

e.   The user can also press F5 again to return to the selection screen.

f.    Transactions are processed the same whether they are entered from the work line or the detail screen. 

7.   The following steps are performed to update the files for each transaction.  Synchronous points are set before and after the files are updated for recovery/restart processing.

a.   All fields that are entered on the work line or detail screen are validated.  See the Design Engineering User Manual for validation rules.

b.   The part master record for the parent part is read for update.  This prevents other users from deleting the parent part.  A new product structure record is added to the file.

(1)  When the addition is complete, the product structure flag (OLFLG5) on the parent part master record is set to 1.

(2)  The cost flag (OLFLG1) is set to 1 and the part master net change flag is set for re-planning (PMNCFL = 2) unless the parent part is a planning part or the structure being added is a reference structure.

c.   The low level codes of the new structures are checked, validated, and updated on the Part Master file (DE100MU).

d.   The BOM Effectivity Date (AMCEA) is updated for the parent part on the Part Master file (DE100MU) if an effectivity date is changed that moves the BOM Effectivity Date in or out of the period marked by the Current Cost Effectivity Date (CZDAT1).

e.   The component part master record is retrieved.  If the part has been flagged for deletion or the part type has been changed to cause an invalid combination with the parent part, a critical error results; the structure is deleted and the low level codes are reversed.

(1)  Valid part types for the parent part are:  manufacturing, planning, build-thru, and transfer.  Valid part types for the component parts are:  purchased, manufacturing, raw materials, planning, reference, build-thru, transfer, by-product, and non-stocked.  If the component part is a planning part type then the parent must also be a planning part type.

(2)  If the parent part is a planning part, then the scrap factor must be zero.

(3)  If the component is not a by-product, the usage code must be consumed:  C.  Otherwise, for by-product components it can be Produced:  P or Consumed:  C.

(4)  For reference components, the reference code must be R (for Reference Product Structure).  Otherwise, it can be blank or R.

f.    If the addition is valid, report records are written to the Design Engineering Transaction Register file (DE120CL) and the Maintenance Audit Trail file (DE120BL).

Update:

a.   The Product Structure file (DE120M) and the Part Master file (DE100M) are read for inquiry.  All transaction change fields are validated.  See the Design Engineering User Manual for validation rules.  If the user has not made changes, the transaction is rejected as invalid.

b.   The Product Structure Record and the parent part master record are read for update.  If another user has updated the product structure record since this transaction was begun (intervening update), a warning message is output.

(1)  The Product Structure file (DE120MU) is updated with the changed fields. 

(2)  The product structure flag (OLFLG5) is set to 1 on the parent part master record.

(3)  If the Batch Quantity Per or the Decimal Control Code field was changed, or if the structure was changed to or from a reference structure, the cost flag (OLFLG0) is set to 1.  The cost flag may also be set to 1 if an effectivity date is changed that moves the date in or out of the period marked by the Current Cost Effectivity Date (CZDAT1) and the Part Master Bill of Material Effectivity Date (AMCEA).

(4)  If the parent part is a planning or build-thru part type or if the structure is a reference structure, the cost flag (OLFLG0) is not set to 1.

(5)  The bill of material effectivity date (AMCEA) may also be updated if a new effectivity date is less than the current Bill of Material Effectivity Date.

(6)  If the Batch Quantity Per, Decimal Control Code, Scrap Factor, Usage Code, Reference Code, Component Offset Days, Deduct Operation, Effectivity Date-In or Effectivity Date-Out is changed, the parent part master net change flag is set for replanning (PMNCFL = 2).  The net change flag is not set for replanning if the parent part is a planning part or if the product structure changed is a reference product structure.  After the successful update of the product structure record, the parent part master record is updated.

c.   Report records are written during online and off-line processing to record data base activity. 

(1)  Report records are written to the Transaction Register file (DE120CL) and the Maintenance Audit Trail file (DE120BL).

Delete

a.   The product structure record is read for inquiry.  A warning message is displayed requesting the user to press the ENTER key in order to process the transaction.

b.   The product structure record and the parent part master record are read for update.  The product structure record is physically deleted from the file.  The parent part master structure flag (OLFLG5) and cost flag (OLFLG0) are set to 1 , the net change flag is set for re-planning (PMNCFL = 2) for non-reference parts, and the record is updated.  (Data Entry processing outputs a transaction record to file DE120AP1 instead of updating the files.)

c.   Report records are written to the Transaction Register file (DE120CL) and the Maintenance Audit Trail file (DE120BL).

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

Application Function


File


Type


Reason for Lock

Addition

Part Master DE100M

Update

To update low level codes and flags and to prevent deletion.

Change

Part Master DE100M

Product Structure DE120M

Update

To update flags.


To prevent other users from updating this record.

Deletion

Part Master DE100M

Product Structure DE120M

Update

To update flags.


To prevent other users from updating this record.

9.   After the files are updated, the selection screen is displayed, allowing the user to perform additional maintenance on the current product structure.

10.  From any screen in the conversation, the user can press F9 to transfer to the Bill of Material Single-Level Explosion Inquiry program (DE810E).  The parent part number entered on the Function Select screen is passed when this program ends.

11.  From the Function Select screen, the user can press F11 to transfer to the Product Structure Maintenance program (DE120E).

12.  From the Function Select screen, the user can press F17 to change the plant.  Plant validation is executed again as it was to validate the fast path plant or the default plant in housekeeping.