F32921ProcessRuleValuesCache

Minor Business Rule

Object Name: B3200140

Parent DLL: CMFG

Location: Client/Server

Language: C

•
•

•
•

•

•

•
•

•

•
•
•

Data Structure

D3200140 - F32921 Process Rule Value Cache

Parameter Name Data Item Data Type Req/Opt I/O/Both

cFileCode FCOD char NONE NONE

The file code is used in the *RANGE and *VALUE file for configurations to determine if the *RANGE or *VALUE goes with a "IF" statement, a
"THEN"statement or with an assembly inclusion rule statement.

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

szBranchPlant MCU char NONE NONE

An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units
for which you have no authority.

mnRuleNumber ATO# MATH_NUMERIC NONE NONE

The number associated with a set of cross-segment editing rules or assembly inclusion rules.

mnRuleSequenceNumber ATOS MATH_NUMERIC NONE NONE

The Sequence number is the rule number within an edit group of cross-segment editing rules or assembly inclusion rules. You can insert a
line within a rule to assign a new sequence number.

nNumberOfKeys INT01 integer NONE NONE

Number of Days in Future to Query for Responses Due.

cCacheActionCode EV01 char NONE NONE

An option that specifies the type of processing for an event.

cCacheCodeError EV01 char NONE NONE

An option that specifies the type of processing for an event.

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

idCursor GENLNG ID NONE NONE

General purpose ID variable.

cReturnCursor EV01 char NONE NONE

An option that specifies the type of processing for an event.

szRuleSegmentValue SGVL char OPT NONE

An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules,
you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique
configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.

szNewRuleSegValue SGVL char OPT NONE

An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules,
you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique
configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.

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.

nIndexNumber INT01 integer OPT NONE

Number of Days in Future to Query for Responses Due.

Related Functions

None

Related Tables

F32921 Cross Segment Editing Rules - Values

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cFileCode	FCOD	char	NONE	NONE
The file code is used in the RANGE and VALUE file for configurations to determine if the RANGE or VALUE goes with a "IF" statement, a "THEN"statement or with an assembly inclusion rule statement.
mnParentItemNumber	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.
szBranchPlant	MCU	char	NONE	NONE
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
mnRuleNumber	ATO#	MATH_NUMERIC	NONE	NONE
The number associated with a set of cross-segment editing rules or assembly inclusion rules.
mnRuleSequenceNumber	ATOS	MATH_NUMERIC	NONE	NONE
The Sequence number is the rule number within an edit group of cross-segment editing rules or assembly inclusion rules. You can insert a line within a rule to assign a new sequence number.
nNumberOfKeys	INT01	integer	NONE	NONE
Number of Days in Future to Query for Responses Due.
cCacheActionCode	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cCacheCodeError	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cSuppressErrorMessage	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.
idCursor	GENLNG	ID	NONE	NONE
General purpose ID variable.
cReturnCursor	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
szRuleSegmentValue	SGVL	char	OPT	NONE
An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules, you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.
szNewRuleSegValue	SGVL	char	OPT	NONE
An answer to the configurator feature and option questions that appear during order entry. When you define cross-segment editing rules, you compare the segment answers to values to determine invalid configurations. When you define assembly inclusion rules, you create unique configurations by comparing the segment answers to values to assign parts, prices, calculated values, or routing steps.
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.
nIndexNumber	INT01	integer	OPT	NONE
Number of Days in Future to Query for Responses Due.