CheckForSubstituteItems

Check For Substitute Items

Major Business Rule

Object Name: B3000530

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
Check for the existence of substitute items for a Bill of Material Component based on the Parent
Branch, Parent Item, Type of Bill, Batch Quantity and Line No.

1.2Setup Notes and Prerequisites
The setup notes and prerequisites contains information that needs to be provided to the application
developer to successfully use attach the business function. Important prerequisite Business Functions
that need to be run and any additional relevant information (what event points, limitations, data
structure peculiarities) should be detailed.

• Use bullet points

1.3Special Logic
This section should be used when additional logic is used in the Business Function for application
specific functionality or exceptional situations.

2.Technical Specifications

2.4Processing
Edits:
1.)  Retrieve Bill of Material table (F3002) where MMCU = DS Parent Branch, KIT = DS Parent Item
(short), TBM = DS Type of Bill, BQTY = DS Batch Quantity, and CPNT = DS Line Number until either a record
is found where the Subsititute sequence number is not equal to 0 or no more records are found.

2.)  If substitute item is located, assign DS Substitute Item Exists = '1'.

3.)  If substitute item is not located and all records are processed, assign DS Substitute Item
Exists = '0'.

^

Data Structure

D3000530 - Check For Substitute Items

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szParentBranch	MMCU	char	NONE	NONE
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which represent lower-level business units, subordinate to it. For example: o Branch/Plant (MMCU) o Dept A (MCU) o Dept B (MCU) o Job 123 (MCU) Business unit security is based on the higher-level business unit.
mnParentItemShort	KIT	MATH_NUMERIC	NONE	NONE
The system provides for three separate item numbers. 1. Item Number (short) - An eight-digit, computer assigned, completely non-significant item number. 2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number. 3. 3rd Item Number - Another 25-digit, free form, user defined alphanumeric item number.
szTypeOfBill	TBM	char	NONE	NONE
A user defined code (40/TB) that designates the type of bill of material. You can define different types of bills of material for different uses. For example: M Standard manufacturing bill RWK Rework bill SPR Spare parts bill The system enters bill type M in the work order header when you create a work order, unless you specify another bill type. The system reads the bill type code on the work order header to know which bill of material to use to create the work order parts list. MRP uses the bill type code to identify the bill of material to use when it attaches MRP messages. Batch bills of material must be type M for shop floor management, product costing, and MRP processing.
mnBatchQuantity	BQTY	MATH_NUMERIC	NONE	NONE
The quantity of finished units that you expect this bill of material or routing to produce. You can specify varying quantities of components based on the amount of finished goods produced. For example, 1 ounce of solvent is required per unit up to 100 units of finished product. However, if 200 units of finished product is produced, 2 ounces of solvent are required per finished unit. In this example, you would set up batch quantities for 100 and 200 units of finished product, specifying the proper amount of solvent per unit.
cSubstituteItemsExist	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
jdAsOfDate	EFFT	JDEDATE	OPT	NONE
A date that indicates one of the following: o When a component part is no longer in effect on a bill of material o When a routing step is no longer in effect as a sequence on the routing for an item o When a rate schedule is no longer active The default is December 31 of the default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
cMode	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cSubEffThruDate	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
mnLineNumber	CPNB	MATH_NUMERIC	OPT	NONE
A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the components appear.

Related Functions

None

Related Tables

F3002 Bill of Material Master File