F32921UpdateRuleValues

F32921 Update Rule Values

Major Business Rule

Object Name: B3200160

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This function will update insert new row into the Rule Values table (F32921). Since all table columns
are part of the primary key, the "old" record must be deleted before the "new" record is inserted
with this function.

1.2Setup Notes and Prerequisites
There is no special setup for this function.

1.3Special Logic
There is no special logic within this function.

2.Technical Specifications
2.4Processing
A. Using key values (FCOD, KIT, MCU, ATO#, ATOS, SGVL), delete the old row from the table .
If the "old" Segment value (SGVL) is blank, this step can be skipped.
B. Using the key values (FCOD, KIT, MCU, ATO#, ATOS, SGVL), insert a new row into the table.

Data Structure

D3200160 - F32921 Update Rule 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.

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.

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.

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

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.

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.

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.

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.

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.

szUserId USER char OPT NONE

The code that identifies a user profile.

szProgramId PID char OPT NONE

The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.

szWorkStationId JOBN char OPT NONE

The code that identifies the work station ID that executed a particular job.

jdDateUpdated UPMJ JDEDATE OPT NONE

The date that specifies the last update to the file record.

mnTimeOfDay TDAY MATH_NUMERIC OPT NONE

The computer clock in hours:minutes:seconds.

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.
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.
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.
szNewRuleSegmentValue	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.
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.
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.
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.
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.
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.
szUserId	USER	char	OPT	NONE
The code that identifies a user profile.
szProgramId	PID	char	OPT	NONE
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
szWorkStationId	JOBN	char	OPT	NONE
The code that identifies the work station ID that executed a particular job.
jdDateUpdated	UPMJ	JDEDATE	OPT	NONE
The date that specifies the last update to the file record.
mnTimeOfDay	TDAY	MATH_NUMERIC	OPT	NONE
The computer clock in hours:minutes:seconds.