ActualCostBuildBOMExplosion_76H

Actual Cost Build BOM Explosion - CHI - 41 - 76H

Minor Business Rule

Object Name: B76H6810

Parent DLL: CLOC

Location: Client/Server

Language: C

Data Structure

D76H6810 - Actual Costing Build BOM Explosion - CHI - 41 - 76H

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cRollCoByProducts	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cSingleLevelRollup	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
mnJobNumber	JOBS	MATH_NUMERIC	OPT	NONE
The job number (work station ID) which executed the particular job.
cSuppressErrorMessages	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
szErrorMessageID	DTAI	char	OPT	NONE
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
jdEffectiveFromDate	EFFF	JDEDATE	OPT	NONE
A date that indicates one of the following: o When a component part goes into effect on a bill of material o When a routing step goes into effect as a sequence on the routing for an item o When a rate schedule is in effect The default is the current system date. 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.
cClearCalcCoByCosts	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
szTypeBill	TBM	char	OPT	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.

Related Functions

Related Tables