QualityAssignmentsCache

Quality Assignments Cache

Minor Business Rule

Object Name: B31B8560

Parent DLL: CWIM

Location: Client/Server

Language: C

Data Structure

D31B8560A - Quality Assignments Cache

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cMode	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
nNumberOfKeys	INT01	integer	OPT	NONE
Number of Days in Future to Query for Responses Due.
cReturnCacheCursor	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
idCacheCursor	GENLNG	ID	OPT	NONE
General purpose ID variable.
cCacheAction	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cErrorCode	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cSuppressErrorMessage	SUPPS	char	OPT	NONE
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function. 0 = allow runtime error message handling. 1 = suppress runtime error message handling.
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.
mnJobnumber	JOBS	MATH_NUMERIC	OPT	NONE
The job number (work station ID) which executed the particular job.
nOperationID	WOPID	integer	OPT	NONE

szTestID	QTST	char	OPT	NONE
The unique identification for a test to be performed on an item. For example: COL Color test DENS Density Test CL-2 Clarity Test
mnQASequence	QASEQ	MATH_NUMERIC	OPT	NONE

szTestResultName	TSTRSNM	char	OPT	NONE
Unique name used to group test results.
cNumeric10	NUMT	char	OPT	NONE
Determines whether a test result value will be numeric or alphanumeric. Valid values are: 1 Indicates that the result value is numeric and should be right justified. 0 Indicates that the result value is alphanumeric and should be left justified. Tests that are using alphanumeric result values can have User Defined Code tables setup that contain alpha to numeric translations. The purpose of these tables is to supply result evaluations with a way of determining whether a result is within the range of the minimum and maximum values.
szQABlendRule	QABLRUL	char	OPT	NONE
A code (31B/QB) used in the Blend Management system to indicate the blending rule for results.
szUserReservedCode	URCD	char	OPT	NONE
This is a 2 position code that is reserved for the user. JDE does not currently use this field and will not utilize this field in the future.
mnUserReservedAmount	URAT	MATH_NUMERIC	OPT	NONE
This is a 15 position code that is reserved for the user. JDE does not currently use this field and will not utilize this field in the future.
szUserReservedReference	URRF	char	OPT	NONE
A 15-position reference that is reserved for the user. J.D. Edwards does not currently use this field and does not plan to use it in the future.
mnUserReservedNumber	URAB	MATH_NUMERIC	OPT	NONE
This is a 8 position code that is reserved for the user. JDE does not currently use this field and will not utilize this field in the future.
jdUserReservedDate	URDT	JDEDATE	OPT	NONE
This is a 6 position code that is reserved for the user. JDE does not currently use this field and will not utilize this field in the future.
szPanelID	QTST	char	OPT	NONE
The unique identification for a test to be performed on an item. For example: COL Color test DENS Density Test CL-2 Clarity Test
nIndexNumber	INT01	integer	OPT	NONE
Number of Days in Future to Query for Responses Due.
szTestDescription	DSC1	char	OPT	NONE
Brief information about an item; a remark or an explanation.
cTestType	TTTY	char	OPT	NONE
A value that specifies how the system processes tests as you enter test results. Valid values are: R Required. Result values must be within the allowable range for the test to pass. The system does not allow an item to pass quality inspection until you enter results for each required test. O Optional. Result values are optional during results entry. The system does not require the entry of a result for each optional test. However, if you enter failing results, the item fails quality inspection. G Guaranteed. Result values are optional during results entry. You can control whether Guaranteed tests appear as you enter test results with the Display Test field on Test Revisions. In addition, guaranteed tests print on the Certificate of Analysis.
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.
jdEffectiveThruDate	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.
szTestCategoryCode1	QTC1	char	OPT	NONE
One of five reporting codes that can be assigned to each test defined. Use these codes to categorize tests into different groups. Category codes are user defined (System 37, types T1 through T5). Examples: Category code T1 - Test Equipment Category code T2 - Test Process
szTestCategoryCode2	QTC2	char	OPT	NONE
One of five reporting codes that can be assigned to each test defined. Use these codes to categorize tests into different groups. Category codes are user defined (System 37, types T1 through T5). Examples: Category code T1 - Test Equipment Category code T2 - Test Process
szTestCategoryCode3	QTC3	char	OPT	NONE
One of five reporting codes that can be assigned to each test defined. Use these codes to categorize tests into different groups. Category codes are user defined (System 37, types T1 through T5). Examples: Category code T1 - Test Equipment Category code T2 - Test Process
szTestCategoryCode4	QTC4	char	OPT	NONE
One of five reporting codes that can be assigned to each test defined. Use these codes to categorize tests into different groups. Category codes are user defined (System 37, types T1 through T5). Examples: Category code T1 - Test Equipment Category code T2 - Test Process
szTestCategoryCode5	QTC5	char	OPT	NONE
One of five reporting codes that can be assigned to each test defined. Use these codes to categorize tests into different groups. Category codes are user defined (System 37, types T1 through T5). Examples: Category code T1 - Test Equipment Category code T2 - Test Process
szTestError	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.

Related Functions

None

Related Tables

None