Batch Part Master Maintenance - Calculations

DE110E

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 applications installed records (categories 011 and 012) on the Reference file are retrieved to determine if the CONBON module, the Expert Configurator module, Repetitive Supply module, and the Inventory Control module are installed. If the Inventory Control module is not installed, the system defaults to a non lot-controlled environment. If the module is installed, the Inventory Control record (ICCTL1) is retrieved from the System Control file. If the Repetitive Supply module is installed, the PO generation mode is validated to determine whether the part is to be handled by Repetitive Supply.

(1) If the Lot Option (LOTOPT) on the Inventory Control record (ICCTL1) is Y, part master maintenance is in a lot-controlled environment and an indicator is set to condition processing of lot information.

(2) If the Lot Option is N, the system is not in a lot-controlled environment.

(3) If the Potency Option (POTOPT) is Y, part master maintenance is in a potency controlled environment. Note that an environment can be potency controlled only if it is lot-controlled.

b. The Entity Name (category 002) on the Reference file is retrieved to determine the company name. If this record is not found, the company name defaults to COMPANY NAME MISSING.

c. 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.

d. The Quantity Field Sizes (category 446) on the Reference file is retrieved to determine the default number of decimal positions for order quantity fields. If this record is not found, a message is sent to the system operator and the program aborts.

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

4. The following validation arrays are loaded from the Reference file (REFERP).

Array Name	Array Description	REFERP Category	Purpose
AUMC	Unit of Measure	005	Used to validate unit of measure values.
AOPC	Order Policy Code	404	Used to validate order policy code values.
APTC	Part Type Code	405	Used to validate part type values.
AACC	Accounting Code	433	Used to validate accounting code values.
ACMC	Commodity Code	434	Used to validate commodity code values.
CCC	CONBON Control Codes	C03	Used to validate CONBON control codes.
PDC	Production Type Codes	C01	Used to validate production types.
ROC	Relief Type Codes	C02	Used to validate relief types.

B. Mainline

1. This program is directed by the Program Status field (PGMSTS). When the status is PMT (prompt subroutine) the program validates the Function Request and Part Number/Plant on the input transaction.

a. There are eleven valid functions. These functions are expected to be input in the sequence (PSTSEQ): delete, add, reactivate, change description, change distribution, change control, change planning, change productivity, change purchasing, and change configuration. The validation is determined by the value of the Program Status field. The functions and their corresponding routine and program status values are shown below.

Maintenance Function	Program Routine Name	Status
Addition	Engineering	ENG
Change Description	Engineering	ENG
Change Distribution	Distribution	DST
Change Control	Control	CTL
Change Cost	Cost	CST
Change Planning	Planning	PLN
Change Productivity	Productivity	PRD
Change Purchasing	Purchasing	PUR
Change Configuration	Configuration	CFG
Deletion	Engineering	ENG
Reactivation	Engineering	ENG
User-Defined Fields	User-Defined	USR

b. No maintenance conversation is provided to populate the transaction files needed for this conversation. The fields are populated by the user via a custom program, utility, etc. The figure below shows the field values necessary for each function as well as the necessary files. The records are read in posting sequence.

Transaction Code (CZTRAN)	Posting Description	Sequence (PSTSEQ)	File
PA1	Addition	08	DE100AP1
PA1	Transfer Part Addition	09	DE100AP1
PA2	Reactivate	10	DE100AP1
PD1	Delete	04	DE100AP1
PC1	Change Description	12	DE100AP1
PC2	Change Control	16	DE100AP2
PC3	Change Planning	18	DE100AP3
PC4	Change Cost	20	DE100AP4
PC5	Change Distribution	14	DE100AP5
PC6	Change Productivity	19	DE100AP6
PC7	Change Purchasing	21	DE100AP7
PC8	Change Configuration	22	DE100AP8
PC9	Change User-Defined Fields	23	DE100AP9

c. After data is read for a specific function, detailed field validation is performed. The transaction is posted if all the required fields are valid. If the transaction is in error only on optional fields, the transaction is considered valid for posting, the optional fields in error are posted as blanks, and errors are written to the DE Transaction Error file (DE545AP). Report records are written for the Maintenance Audit Trail report (DE540) and the Transaction Register report (DE550). If the transaction is invalid, all errors are output and the Part Master file is not updated.

d. When the last transaction is read, END is moved to the Program Status field and windup processing is performed.

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

a. All required fields or desired optional fields entered are validated. See the Design Engineering User Manual for validation rules.

b. If a new record is added to the Part Master file, the following fields default to the value specified.

Field Name	Field	Default Value
IZACD	Activity Code	1, if not entered.
PMJCFL	Job Control Option	N, if not entered
PMPDTP	Production Type	1, if not entered.
AMERL	Revision Level	000, if not entered.
PMRVGN	Revision Level Generation	N, if not entered.
PMREFF	Flag Revision Effectivity Date	0, if revision level not entered. System date, if revision level entered, but not date.
PMCBCC	CONBON Control Code	2, if CONBON installed. 0, if CONBON not installed.
PMRLFT	Relief Type	1
AISSCD	Issue Code	R
	Part Type 1-8
	B-C	S
MOPOC	Order Policy Code	1
MOPOQ	Order Policy Quantity	0
PMOPIN	Order Policy Increment	0
AMSKLC	Primary Stock Location	NOPRLOC
OLFLG0	Cost Activity Flag	1
PMUPDT	Part Master Update Level	00001
IZLCF	Lot Control Option	N
PMPTCF	Potency Control Option	N
PMSTPT	Standard Potency	100
PMSCFL	Serial Control Flag	N, if part not yet existing in other plants. Otherwise, default value in other plants.
AMSIRL	SIR Stock Location	NOSRLOC
PMNCFL	Part Master Net Change Flag	0
PMSLD1	Description Line 1	(CMDESC)
PMPSRC	Search	(CMDESC)
PMDMND	Demand Code	M
MPEGCD	Force Print Flag	N
RPORDQ	MS Order Quantity	0
OLFLG1	Cost Rollover Code	0
OLFLG2	Cost Rollup Code	0
AMORDQ	Average Order Quantity	1
PMMSFL	Master Scheduling Generation Flag.	0
PMNETF	Inventory Netting Flag	Y
PMAUTQ	Authorized Production Quantity	1, if not entered.
PMCELL	Producing Cell	NOPDCTR, MRP part (Reference File category K03 default), JIT Part
AMLTC	Lead Time Code	F
PMVOCM	Order Processing Configuration	N
PMVOMF	Manufacturing Order Configuration	N
PMFAMR	Product Reference Code	0
PMGNFL	PO Automatic Generation Flag	N, if not entered
PMBTQT	Batch Quantity	1
PMCFCO	Configuration Code Option	0
CDWPAC	WIP Accounting Code	Inventory Accounting Code
PMALT	Alternate Part Number	Blanks, if not entered.
PMUPC	Universal Product Code	Blanks, if not entered.
PMRPL	Replacement Part Number	Blanks, if not entered.
PMPRGR	Pricing Group	Blanks, if not entered.
PMDVID	Division ID	Blanks, if not entered.
PMSCID	Section ID	Blanks, if not entered.
PMAXMO	Maximum Order Quantity	0
PMFCCD	Consumption Code	0 (No Consumption)
PMFHDY	RP Firm Horizon Days	0
PMMLFC	Multi-Level Forecast Flag	N

c. A warehouse balance record is automatically created for the part in the manufacturing company/warehouse (if inventory control is installed).

d. Report records are written to the Design Engineering Transaction Register (DE100CP1) and Maintenance Audit Trail file (DE100BP1) to record data base activity.

e. The part/revision level combination is written to the revision level file (DE170M). If no revision level is entered, it is defaulted to '000'. The revision effectivity date is defaulted to the current system date and the revision description defaults to 'P/M ADDED REVISION LEVEL'.

3. Change: The following processing occurs for each change transaction. These transactions include changes to descriptive, distribution, control, planning, productivity, cost data, and configuration.

a. The part 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 have been made, the transaction is invalid.

b. Relational validation is performed. Relational validation ensures that changes are compatible with information currently on the data base.

(1) Change Description

If the production type is changed from MRP to JIT, the part cannot be a non-standard type part and cannot be configured or have a configuration code. When the production type is changed, the planning policy code (MOPOC) is reset to 1 if the previous planning policy code was not 2, 3, or 5.

If the production type is changed from JIT to MRP, a warning message is sent if any FA exists for this part.

If the production type is changed from MRP to JIT or from JIT to MRP, the part's run units and fixed lead time are reset to zero.

If the production type is changed, the Routing file (ME120M) is checked. If a routing exists, the production type cannot be changed.

If the part type is changed, the following conditions are verified.

From	To	Conditions
Purchased	Planning	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part.
Purchased	Reference or Non-stocked	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand.
Purchased	Build-thru	Part cannot be a master scheduled or service part.
Purchased	Non-standard	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be used as a component. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand.
Purchased	Non-stocked	Part cannot have sales order processing configuration.
Purchased	Manufactured	The Part Type field must be changed to manufactured. The Cost BOM and the Cost Routing flags must be changed to Y (yes) to generate the correct costs for the part.
Manufactured	Purchased or Raw	Part cannot have routings. Part cannot be used as a component. No manufacturing orders or flow authorizations may exist for the part. Part cannot have manufacturing configuration.
Manufactured	Planning	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot have components or routings. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have manufacturing configuration.
Manufactured	Reference or Non-stocked	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot have components or routings. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand. Part cannot have manufacturing configuration.
Manufactured	Build-thru	Part cannot have routings. Part cannot be a master scheduled or service part. Part cannot have manufacturing configuration.
Manufactured	Non-standard	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be a JIT part. Part cannot have components or routings. Part cannot be used as a component. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand. Part cannot have manufacturing configuration.
Manufactured	Non-stocked	Part cannot have sales order processing configuration.
Raw	Planning	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part.
Raw	Reference or Non-stocked	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand.
Raw	Build-thru	Part cannot be a master scheduled or service part.
Raw	Non-standard	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be a JIT part. Part cannot be used as a component. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand.
Raw	Non-stocked	Part cannot have sales order processing configuration.
Planning	Purchased or Manufactured or Raw or Build-thru or Transfer	Part cannot exist in another plant. Part cannot have components. Part cannot be used as a component.
Planning	Reference or Non-stocked	Part cannot exist in another plant. Part cannot have components. Part cannot be used as a component. Part cannot have projected demand.
Planning	Non-standard	Part cannot exist in another plant. Part cannot be a JIT part. Part cannot have components. Part cannot be used as a component. No inventory balance may exist for the part. Part cannot have projected demand.
Planning	Non-stocked	Part cannot have sales order processing configuration.
Reference or Non-stocked	Purchased or Manufactured or Raw or Planning or Build-thru or Transfer	Part cannot exist in another plant. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part.
Reference or Non-stocked	Non-standard	Part cannot exist in another plant. Part cannot be a JIT part. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part.
Reference	Non-stocked	Part cannot exist in another plant. Part cannot be used as a component. Part cannot have sales order processing configuration.
Non-stocked	Reference	Part cannot exist in another plant. Part cannot be used as a component.
Build-thru	Purchased or Raw	Part cannot have components. Part cannot be used as a component. No manufacturing orders of flow authorizations may exist for the part. Part cannot have manufacturing configuration.
Build-thru	Planning	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot have components. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot have manufacturing configuration.
Build-thru	Reference or Non-stocked	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot have components. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part. Part cannot have projected demand. Part cannot have manufacturing configuration.
Build-thru	Non-standard	Part cannot exist in another plant. Part cannot be lot controlled. Part cannot be a JIT part. Part cannot have components. Part cannot be used as a component. No manufacturing orders may exist for the part. No inventory balance may exist for the part. Part cannot have projected demand. Part cannot have manufacturing configuration.
Build-thru	Non-stocked	Part cannot have sales order processing configuration.
Non-standard	Purchased or Manufactured or Raw or Build-thru or Transfer	Part cannot exist in another plant. No inventory balance may exist for the part.
Non-standard	Planning or Reference or Non-stocked	Part cannot exist in another plant. Part cannot be lot controlled. No purchase orders, sales orders, or transfer orders may exist for the part. No inventory balance may exist for the part.
Non-standard	Non-stocked	Part cannot have sales order processing configuration.
Transfer	Purchased or Raw	Part cannot have components or routings. Part cannot be used as a component. No manufacturing orders or flow authorizations may exist for the part.
Transfer	Planning	Part cannot be lot controlled. Part cannot have components or routings. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part.
Transfer	Reference or Non-stocked	Part cannot be lot controlled. Part cannot have components or routings. Part cannot be used as a component. No purchase orders, sales orders, or transfer orders may exist for the part. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part. Part cannot have projected demand.
Transfer	Build-thru	Part cannot have routings. Part cannot be a master scheduled or service part.
Transfer	Non-standard	Part cannot be lot controlled. Part cannot be a JIT part. Part cannot have components or routings. Part cannot be used as a component. No manufacturing orders or flow authorizations may exist for the part. No inventory balance may exist for the part. Part cannot be a master scheduled or service part.
Transfer	Non-stocked	Part cannot have sales order processing configuration.

If a part type is changed to anything other than manufactured or transfer, the change may not occur if the Issue code is equal to 'T'.

1, 3, 8 or C	Anything other than 1, 3, 8 or C	The planning order policy is set to 6 if the production type is JIT, and if the previous planning order policy was not 2 or 3.
Not 1, 3, 8 or C	1, 3, 8 or C	If the previous planning order policy code is not 2 or 3, the planning order policy is set to 1, if the production type has not been changed and the type is JIT or MRP.
Not 1, 3, 8 or C	JIT	The planning order policy is set to 6, if the previous planning order policy is not 2 or 3.

If the stockkeeping or selling unit of measure is changed, the part must have a warehouse balance of zero, it cannot be used as a component, and it cannot have any existing manufacturing or purchase orders.

If any unit of measure or unit of measure conversion factor has been changed, the relationship between units of measures and conversion factors is validated. If the stockkeeping unit of measures equals the selling unit of measure, the SKU/SU conversion factor must equal one. Similarly, if the stockkeeping unit of measure equals the purchasing or supplementary unit of measure, the corresponding SKU/PU or Suppl/SKU conversion factor must equal one.

For a transfer part type, the sourcing plant must be valid. If a part has been deleted or deactivated from a sourcing plant, it cannot be used as a transfer part. If the part is not a transfer part, the sourcing plant must be blank. The revision level field is not maintainable for a change transaction (must use Revision Level Maintenance).

(2) Change Control

Non-stocked parts must have an issued code equal to S. If the Issue Code, SIR Stock Location, or Lot Option is changed, the following conditions are verified.

Issue Code	Primary Location	SIR Location	Lot Option
R	Must be NOPRLOC or a valid location.	Must be NOSRLOC or a valid location.	Must be Y or N
S	Must be NOPRLOC or a valid location.	Must be a valid SIR location.	Must be N
			If a primary or SIR stock location is changed, its corresponding record on the Location Validation File (DE140M for primary, DE140ML1 for SIR) is read for update. This read checks for a valid location as well as prevents another user from deleting the location before the Part Master File is updated.
			If the Lot Option is changed, the part cannot exist in another plant, it cannot have a warehouse balance, it cannot be used as a component, and it cannot have existing manufacturing or purchase orders. The part must not be configuration code if the lot control option is N.
T	Must be a valid location.

If the Job Control flag is changed from N (no) to Y (yes), the part cannot be any of the following part types:

a) Planning (4)

b) Reference (5)

c) Non-standard (7)

d) Transfer (8)

e) Non-stocked (c)

The part cannot possess a JIT production type. Also, the part must have the Safety Stock set to zero, and the planning policy code must equal 1 - As Required.

Note: In order for the Job Control flag to be changed from Y (yes) to N (no), the part cannot possess any records in the following files:

IC100M - Manufacturing Orders

IC120M - Component Requirements

IC140M - Warehouse Balance

JT100M - Flow Authorization

JT120M - Flow Requirements

MS150M - Projected Demand

OP100M2 - Sales Order Line Item and Forecast

PO160M1 - Purchase Requisition

PO180M2 - Purchase Order Line Detail

PO180M3 - Purchase Order Release Detail

TC100M2 - Transfer Order Supplying Warehouse

- Transfer Order Receiving Warehouse

TC110M1 - Transfer Requisition Supplying Warehouse

- Transfer Requisition Receiving Warehouse

If the value code is 'T' (multi-level back flushing).

The part type should be manufactured or transfer.

The production type should be JIT.

The planning order policy should be 6 if type is manufactured.

The planning order policy should be 8 if type is transfer.

The production center should not be blank or equal to NOPDCR.

The production location should exist and must be valid.

The lot control should be 'N'.

The relief code should be 2.

In order for the Job Control flag to be changed from N (no) to Y (yes), the part cannot possess any records in the following files:

TC100M2 - Transfer Order Supplying Warehouse

- Transfer Order Receiving Warehouse

TC110M1 - Transfer Requisition Supplying Warehouse

- Transfer Requisition Receiving Warehouse

(3) Change Planning

If the planning policy code of a part is changed, the planning policy quantity and increment currently on the part master record must be valid for the new code or a new quantity and increment must be specified. Similarly, if the planning policy quantity or increment is changed, the planning policy code on the part master record must be valid for the new quantity or increment, or a new code must be specified. The combinations that are valid depend on the production type.

For a job-controlled part, the planning policy must remain As Required.

For a manufactured part with an issue code 'T', the planning policy code must remain As Partial.

For a transfer part with an issue code 'T', the planning policy code must remain As Required.

For an MRP part, the following combinations are valid:

Order Policy	Code	Quantity	Increment
As Required (A/R)	1	Zero	Zero
Fixed Time Period (F/T)	2	Nonzero	Zero
Fixed Quantity (F/Q)	3	Nonzero Numeric	Valid
Physical Control (P/C)	4	Zero	Zero

For a JIT part, the following combinations are valid:

Planning Policy	Code	Quantity	Increment
Partial	6	Zero	Zero
Average	7	Zero	Zero
Fixed Time Period (F/T)	2	Nonzero	Valid Numeric
Fixed Quantity (F/Q)	3	Nonzero	Valid Numeric

For MRP and JIT parts, the batch quantity must be greater than or equal to one.

(4) Change Productivity

For MRP parts, the production center (PMCELL) defaults to NOPDCTR. For JIT parts, the production center defaults to the plant-specific default production center on Reference File category K03. The plant-specific default production center must exist on the Production Center file (JT180M); otherwise, the production center defaults to NOPDCTR.

The CONBON Control code defaults to 0 if CONBON is not installed or 2 if CONBON is installed. In a dual/single card environment, a message warns the user if the CONBON Control code indicates a dual or single card and the container code is not entered.

For a 'T' issue code, the production center must be valid and not NOPDCTR.

If either the container code or the container quantity is changed, the following conditions must be met.

Container Code	Container Quantity
Blank	Blanks or Zero
Non-Blank	Valid Numeric or Blanks or Zero (if blank or zero, defaults to quantity on container file)

For a purchased, manufactured, raw, build-thru, or transfer JIT part, if changing similar fields of the Part/Production Center Relationship file (JT160M), the part/production center relationship is updated. Also, a transaction image is recorded on the Part/Production Center Relationship Audit Trail file.

(5) Change Configuration

If the standard routing default part, standard BOM default part, or reference routing part is changed, the new part must exist on the Part Master file in the chosen plant. Similarly, if any group or subgroup is changed, the new group or subgroup must be defined in the correct Reference File category (Y21, Y22, Y23, Y24, Y25, or Y26). These Reference File categories are plant specific.

A part must be Sales Order Configured before it can use Configuration Codes. Only Part Types 1, 2, 6, and 8 can have a Configuration Code Option of non-zero. Valid configuration Code options are:

Configuration Code Option	Number of Lots Used	Costing Type Used
0	Not Configured
1	Single Lot	Standard
2	Multiple Lots	Standard
3	Single Lot	Configuration
4	Multiple Lots	Configuration

Configuration Codes cannot be changed is inventory exists for the part. Configuration Code Options of 1 or 2 cannot be changed to 3 or 4 if the Previous Period Accounting Balance on the Configuration Code file (EC140M) is not zero. This is also true for changes from 3 or 4 to 0, 1, or 2.

If a part uses Configuration Codes it must also have a Template Code. This must be a valid Template Code from the Configuration Template Master (EC160M) and the part must be lot-controlled or lot-assignable. The part cannot have a production type of JIT if it is configured.

(6) Change Cost

The change cost batch transaction allows the user to change the following information: the current to standard rollover code, the standard rollup code, the simulated rollover code, and the average order quantity. When a new part is added, these fields default to N, N, N, and 1, respectively.

c. After validation is complete, the Part Master 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 written to the Transaction Error file.

d. The part master net change flag (PMNCFL) and cost activity flag (OLFLG0) are reset when certain part master fields are changed. The part master net change flag is used by the Requirements Planning module. The cost activity flag is used by the Product Costing module.

(1) If any of the following fields are changed when the part type is not planned, reference, non-standard, or non-stocked the net change flag is set for re-planning (PMNCFL=2).

· IC Scrap Factor (RPSCRP)

· Issue Code (AISSCD)

· Planning Policy Code (MOPOC)

· Planning Policy Quantity (MOPOQ)

· Lead time Code (AMLTC)

· Fixed Lead time Days (MLTPU)

(2) If any of the following fields are changed when the part type is not planned, reference, non-standard, or non-stocked and the lead time code is variable (AMLTC=V), the net change flag is set for re-planning (PMNCFL=2).

· Setup Days (MLTSU)

· Transit Days (MLTQM)

· Run Days Per Piece (MLTRH)

(3) If the Safety Stock Quantity (AMSSK) is changed and the part type is not planned, reference, non-standard, or non-stocked the net change flag is set for re-analysis (PMNCFL=1), unless it is already set for re-planning.

(4) If the part type is changed to planned, reference, non-standard, or non-stocked the net change flag is reset (PMNCFL=0) so that the part is not examined by requirements planning processing. If the part type was changed to build-thru, the net change flag is set (PMNCFL=2) so that the part is replanned by requirements planning processing.

(5) If the potency flag or standard potency is changed, the net change flag is set for re-analysis (PMNCFL=1) unless it is already set for re-planning.

(6) If the part type was changed to purchased, manufactured, raw, or build-thru, the cost activity flag is set to recost the part (OLFLG0=1). If the part type was changed to planned, reference, non-standard, or non-stocked the flag is reset (OLFLG0=0) so the part is not examined by product costing processing.

(7) If the part's consumption code is changed, the Net Change flag is set for reanalyzing (PMNCFL = 1), unless it is already reset for replanning.

(8) If the part's Target Inventory Days/Weeks field is changed, the Net Change flag is set for reanalysis (PMNCFL = 1), unless it is already set for replanning.

e. The part master record is updated.

f. Report records are written to record data base activity. Transaction register and maintenance audit trail report records are written to the transaction files listed below.

Transaction Register		Maintenance Audit Trail
Description	DE100CP1	Description	DE100BP2
Distribution	DE100CP5	Distribution	DE100BP6
Control	DE100CP2	Control	DE100BP3
Planning	DE100CP3	Planning	DE100BP4
Cost	DE100CP4	Cost	DE100BP5
Productivity	DE100CP6	Productivity	DE100BP7
Purchasing	DE100CP7	Purchasing	DE100BP8
Configuration	DE100CP8	Configuration	DE100BP9

4. Change User-Defined Fields

a. The literals for display on the screen are retrieved from Reference File categories D94, D95, D96, D97, D98, and D99. No validation is performed on these fields.

5. Deletion

a. The Part Master Validation Delete program (DE102E) will be called. A sourcing part/plant for a transfer part cannot be deleted if the transfer part is active.

b. The Part Master file is read for inquiry. If the part is active IZACD=*, the following conditions are verified.

Part does not have a Warehouse Balance file record.

Part does not have a Lot Control file record.

Part does not have a Product Structure file record and is not used in any product structure.

Part is not used in a routing.

Part is not used as a component in a manufacturing order.

Part is not on a sales order.

Part is not on a manufacturing order.

A purchase order release does not exist for the part.

A demand forecast record does not exist for the part.

A requisition does not exist for the part.

Part is not used in a planned routing.

Part is not used in an item/vendor relationship.

Part is not used in a tentative master schedule.

Part does not have a Projected Demand file record.

Part does not have a part/production center relationship.

Part does not have a valid endorsement.

Part does not have any configuration code.

c. The part is read for update and is logically deleted by updating the part's activity code to inactive status (IZACD=*). The part master net change flag is updated (PMNCFL=0) so the part is not examined in requirements planning processing. The part is physically deleted from the Part Master file only during the file reorganization process.

d. Report records are written to the Transaction Register (DE100CP1) and Maintenance Audit Trail (DE100BP1) files.

6. Reactivation

The following parts cannot be reactivated:

1. Active parts

2. Inactive transfer parts with inactive sourcing parts.

a. The part is read for update and is logically reactivated by updating the part's activity code to active status (IZACD=1).

b. Report records are written to the Transaction Register (DE100CP1) and Maintenance Audit Trail (DE100BP1) files.

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

Application Function	File	Lock Type	Reason for Lock
Change (all), Deletion and Reactivation	Part Master (DE100M)	Update	To exclude other users from updating this record.
Change Control	Location Validation (DE140M)	Application	To prevent other users from deleting the primary stock, SIR, producing, or relief location of a part.
Change Control	Location Validation (DE140ML1)	Application	To prevent other users from deleting the SIR stock location of a part.

Menu

Batch Part Master Maintenance - Calculations

DE110E Program Menu