InitActualCoByProductCache_76H

Actual Costing, Initialize CoBy Product Cache - CHI - - 76H

Minor Business Rule

Object Name: B76H6610

Parent DLL: CLOC

Location: Client/Server

Language: C

Data Structure

D76H6610 - Actual Costing, Initialize CoBy Product Cache - CHI - - 76H

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnProcessItem	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.
szProcessBranch	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.
mnProcessBatchQtyPrim	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.
szProcessUOM	UOM	char	NONE	NONE
A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).
jdAsOfDate	ASDE1	JDEDATE	NONE	NONE
The date used for effectivity checking. Enter a specific date to display documents (orders, bills of material, routings, as applicable) that are effective on or after that date. The current system date is the default, but you can enter any future or past date.
szCostType	LEDG	char	NONE	NONE
A user defined code (40/CM) that specifies the basis for calculating item costs. Cost methods 01 through 19 are reserved for J.D. Edwards use.
cCoByProductFound	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
mnProcessBatchQtyTrans	QNTY	MATH_NUMERIC	NONE	NONE
The number of units that the system applies to the transaction.
mnProcessUOMConvFactor	CONV	MATH_NUMERIC	NONE	NONE
The factor that the system uses to convert one unit of measure to another unit of measure.
cCalculateRatioPercent	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cSuppressErrorMessages	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
szErrorMessageID	DTAI	char	NONE	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.
mnJobNumber	JOBS	MATH_NUMERIC	NONE	NONE
The job number (work station ID) which executed the particular job.
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

None

Related Tables

None