F3292UpdateCrossSegmentEdit

F3292 Update Cross Segment Edit

Major Business Rule

Object Name: B3200060

Parent DLL: CMFG

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
This function will update the Cross Segment Edit Rules table (F3292). If the specified row in the
table is found, the values passed in the input parameters are updated to the F3292 table; if the
requested record is not found, a new row is inserted with the supplied values.

1.2Setup Notes and Prerequisites
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 (KIT, MCU, ATO#, ATOS) passed in as input parameters,    retrieve the
specified row from the F3292 table.
B. If the row is found, move all input parameters to their associated field on    the table and
update the row.
C. If the row is not found, insert a new row with the values passed in as input    parameters.

Updates one row on the Cross-Segment Edit Rules table (F3292) based on values passed in as input
parameters.

Data Structure

D3200060 - F3292 Update Cross-Segment Edit

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

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

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

mnAtorulenumber ATO# MATH_NUMERIC NONE NONE

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

szIdentifier2nditem LITM char NONE NONE

A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to
alternative item numbers. The three types of item numbers are: Item Number (short) An 8-digit, computer-assigned item number. 2nd Item Number A
25-digit, user defined, alphanumeric item number. 3rd Item Number Another 25-digit, user defined, alphanumeric item number. In addition to
these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous
cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, bar codes, customer numbers, or
supplier numbers.

szIdentifier3rditem AITM char NONE NONE

The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item
numbers are as follows: 1.  Item Number (short) - An 8-digit, computer-assigned 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. In addition to
these three basic item numbers, an extensive cross-reference search capability has been provided (see XRT). Numerous cross references to
alternate part numbers can be user defined, such as substitute item numbers, replacements, bar codes, customer numbers, or supplier
numbers.

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.

jdEffectivefromdate EFFF JDEDATE NONE 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 NONE 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.

mnParentsegmentnumber PEL MATH_NUMERIC NONE NONE

A number that establishes the sequence in which the segments were defined in the system. Segment numbers are user
defined. Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration. Assembly inclusion rules
reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.

mnAtosegmentproductfamilyn PSIN MATH_NUMERIC NONE NONE

The configured item that a segment in an Assembly Inclusion Rule references.

szCostcenterheader EMCU char NONE NONE

A business unit is an accounting entity required for management reporting. It can be a profit center, department, warehouse location, job,
project, work center, branch/plant, and so forth. This business unit is from the business unit entered on the header of a sales/purchase order for
reporting purposes. This data is always right justified on entry (for example, CO123 would appear as _______CO123).  A security mechanism
has been provided to inhibit users from entering or locating business units outside the scope of their authority.

szRelationship VALR char NONE NONE

A user defined code (00/VA) that indicates the relationship between the ranges of variances that you display. Valid values are: EQ Equal
to LT Less than LE Less than or equal to GT Greater than GE Greater than or equal to NE Not equal to NL Not less than NG Not greater than CT
Contains (only allowed in selection for Open Query File function) CU Same as "CT" but converts all input data to uppercase letters

cAndorselection AO char NONE NONE

A code that determines whether compound data selection logic is based on an A  = AND condition or an O = OR condition.

szAndorselectionbeginning AO5B char NONE NONE

A collection of open and closed brackets to group conditional configurator rules. For example, to define the condition (Seg 1 = A OR Seg 2 =
B) AND Seg 3 = C,use the following brackets: (Seg 1 = A O Seg 2 = B) A Seg 3 = C

szAndorselectionending AO5E char NONE NONE

A collection of open and closed brackets to group conditional configurator rules. For example, to define the condition (Seg 1 = A OR Seg 2 =
B) AND Seg 3 = C,use the following brackets: (Seg 1 = A O Seg 2 = B) A Seg 3 = C

cRequiredtobe ATRQ char NONE NONE

A code that specifies whether a segment is required or optional in a configuration, or whether the system must calculate it to specification
when you enter an order. Valid codes are: R Segment answer is required during order entry. O Segment answer is optional during order
entry. C Segment is calculated during order entry. You define the calculation with assembly inclusion rules.

cCustommessage CSMG char NONE NONE

A user defined code (32/CM) that specifies the cross-segment error message that appears. Valid values are: 0 Only the standard
cross-segment error message appears 1 Only the custom error message appears 2 Both the cross-segment and custom error messages appear

szUserreservedcode URCD char NONE 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 NONE 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 NONE 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 NONE 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 NONE 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.

szUpdatedby UPID char NONE NONE

This field is updated with the name of the person who last updated the tag.

szWorkstationid JOBN char NONE NONE

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

szUserid USER char NONE NONE

The code that identifies a user profile.

jdDateupdated UPMJ JDEDATE NONE NONE

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

mnTimeofday TDAY MATH_NUMERIC NONE NONE

The computer clock in hours:minutes:seconds.

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.

mnTempSequenceNumber RCK9 MATH_NUMERIC NONE NONE

This field is used to create a unique key within a file.  If you are using a program which will allow you to resequence the records, we
recommend you use one of the following data dictionary items:  DSS5, DSS7, DSS9.

szExternalProgramID EPGM char OPT NONE

The name of the external program written by your MIS department, that will be providing values for external variables.

szSelectionValueAtoIf ATIV char OPT NONE

An answer that is valid for the segment and rule relationship. You can enter a specific UDC value or one of the following values: *VALUES
The system provides multiple values lists for you to use in the logic rule. You can enter up to 45 values.    *BLANK The system uses a blank
value in the logic rule. *ZERO The system searches for amounts equal to zero as part of the logic rule. *RANGE The system uses a range of
values (for example, 1 to 50) in the logic rule. You enter the range of values. The first value in the range must be less than the second value. *ALL
The system uses all values in the logic rule.

Related Functions

None

Related Tables

F3292 Cross Segment Editing Rules

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnItemnumbershortkit	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.
szCostcenter	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.
mnAtorulenumber	ATO#	MATH_NUMERIC	NONE	NONE
The number associated with a set of cross-segment editing rules or assembly inclusion rules.
szIdentifier2nditem	LITM	char	NONE	NONE
A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to alternative item numbers. The three types of item numbers are: Item Number (short) An 8-digit, computer-assigned item number. 2nd Item Number A 25-digit, user defined, alphanumeric item number. 3rd Item Number Another 25-digit, user defined, alphanumeric item number. In addition to these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, bar codes, customer numbers, or supplier numbers.
szIdentifier3rditem	AITM	char	NONE	NONE
The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item numbers are as follows: 1. Item Number (short) - An 8-digit, computer-assigned 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. In addition to these three basic item numbers, an extensive cross-reference search capability has been provided (see XRT). Numerous cross references to alternate part numbers can be user defined, such as substitute item numbers, replacements, bar codes, customer numbers, or supplier numbers.
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.
jdEffectivefromdate	EFFF	JDEDATE	NONE	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	NONE	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.
mnParentsegmentnumber	PEL	MATH_NUMERIC	NONE	NONE
A number that establishes the sequence in which the segments were defined in the system. Segment numbers are user defined. Cross-segment editing rules reference the segment numbers to ensure that the set of values defines a valid configuration. Assembly inclusion rules reference segment numbers and their associated values to define prices, component parts, routing, and calculated values for configured items.
mnAtosegmentproductfamilyn	PSIN	MATH_NUMERIC	NONE	NONE
The configured item that a segment in an Assembly Inclusion Rule references.
szCostcenterheader	EMCU	char	NONE	NONE
A business unit is an accounting entity required for management reporting. It can be a profit center, department, warehouse location, job, project, work center, branch/plant, and so forth. This business unit is from the business unit entered on the header of a sales/purchase order for reporting purposes. This data is always right justified on entry (for example, CO123 would appear as _______CO123). A security mechanism has been provided to inhibit users from entering or locating business units outside the scope of their authority.
szRelationship	VALR	char	NONE	NONE
A user defined code (00/VA) that indicates the relationship between the ranges of variances that you display. Valid values are: EQ Equal to LT Less than LE Less than or equal to GT Greater than GE Greater than or equal to NE Not equal to NL Not less than NG Not greater than CT Contains (only allowed in selection for Open Query File function) CU Same as "CT" but converts all input data to uppercase letters
cAndorselection	AO	char	NONE	NONE
A code that determines whether compound data selection logic is based on an A = AND condition or an O = OR condition.
szAndorselectionbeginning	AO5B	char	NONE	NONE
A collection of open and closed brackets to group conditional configurator rules. For example, to define the condition (Seg 1 = A OR Seg 2 = B) AND Seg 3 = C,use the following brackets: (Seg 1 = A O Seg 2 = B) A Seg 3 = C
szAndorselectionending	AO5E	char	NONE	NONE
A collection of open and closed brackets to group conditional configurator rules. For example, to define the condition (Seg 1 = A OR Seg 2 = B) AND Seg 3 = C,use the following brackets: (Seg 1 = A O Seg 2 = B) A Seg 3 = C
cRequiredtobe	ATRQ	char	NONE	NONE
A code that specifies whether a segment is required or optional in a configuration, or whether the system must calculate it to specification when you enter an order. Valid codes are: R Segment answer is required during order entry. O Segment answer is optional during order entry. C Segment is calculated during order entry. You define the calculation with assembly inclusion rules.
cCustommessage	CSMG	char	NONE	NONE
A user defined code (32/CM) that specifies the cross-segment error message that appears. Valid values are: 0 Only the standard cross-segment error message appears 1 Only the custom error message appears 2 Both the cross-segment and custom error messages appear
szUserreservedcode	URCD	char	NONE	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	NONE	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	NONE	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	NONE	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	NONE	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.
szUpdatedby	UPID	char	NONE	NONE
This field is updated with the name of the person who last updated the tag.
szWorkstationid	JOBN	char	NONE	NONE
The code that identifies the work station ID that executed a particular job.
szUserid	USER	char	NONE	NONE
The code that identifies a user profile.
jdDateupdated	UPMJ	JDEDATE	NONE	NONE
The date that specifies the last update to the file record.
mnTimeofday	TDAY	MATH_NUMERIC	NONE	NONE
The computer clock in hours:minutes:seconds.
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.
mnTempSequenceNumber	RCK9	MATH_NUMERIC	NONE	NONE
This field is used to create a unique key within a file. If you are using a program which will allow you to resequence the records, we recommend you use one of the following data dictionary items: DSS5, DSS7, DSS9.
szExternalProgramID	EPGM	char	OPT	NONE
The name of the external program written by your MIS department, that will be providing values for external variables.
szSelectionValueAtoIf	ATIV	char	OPT	NONE
An answer that is valid for the segment and rule relationship. You can enter a specific UDC value or one of the following values: VALUES The system provides multiple values lists for you to use in the logic rule. You can enter up to 45 values. BLANK The system uses a blank value in the logic rule. ZERO The system searches for amounts equal to zero as part of the logic rule. RANGE The system uses a range of values (for example, 1 to 50) in the logic rule. You enter the range of values. The first value in the range must be less than the second value. *ALL The system uses all values in the logic rule.