F3281GetRuleDefinitionRow

F3281 Get Rule Definition Row

Major Business Rule

Object Name: N3200920

Parent DLL: CMFG

Location: Client/Server

Language: NER

1.Functional Description

1.1Purpose
This named E/R function will retrieve a row on the Rule Table Definition table (F3281) and return all row values. The error message 2838 will be
returned if the record does not exist for the key values specified. The calling program will be responsible for processing this error code, i.e. sending or
printing an error message to the user.
If BF ConfiguredTableID >= ZERO

Key:

•
Configured Table ID (MFGTID)

•
FetchSingle from F3281

•
• Else
•
Key:

•
Rules Table Name (TBLC)
• Branch Plant (MCU)
• Rules Table Type (RTBT)

'b7FetchSingle from F3281

EndIf
If FetchError > BLANK
    If BF cSuppessError != 1
         Set Error
    EndIf
EndIf

1.2Setup Notes and Prerequisites
No special setup instructions.

1.3Special Logic
No special logic.

Data Structure

D3200920 - F3281 Get Rule Definition Row

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

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.

szRuleTableName TBLC char NONE NONE

The name of a collection of data that you set up to minimize the number of assembly inclusion rules that you need for a configured item. You
must define rule table names in user defined code table 32/TN. A rule table can be accessed by 1 to 20 keys and can return up to 99
values. When you reference a rule table in an assembly inclusion rule, the system uses the rule keys to retrieve the values that are associated
with the rule table. For example, if you defined segment 10 to be the color of an item, you could set the table to retrieve item Red Component
when the customer enters Red for segment 10. In this example, the table would be:        Item Color = Value        Red = Red Component The table
would include the following: If the color segment value = red, then use item number Red Component on the configured item sales order and
work order parts list.

szDescriptionLine1 DSC1 char NONE NONE

Brief information about an item; a remark or an explanation.

cRulesTableType RTBT char NONE NONE

A value that identifies the type of rule table. Valid values are:    P Part list (on sales order and work order)    Q Work order component (on
work order only)    C Calculated values    H Hot Spot    X Price/Cost adjustment

mnNumberofSegments NSEG MATH_NUMERIC NONE NONE

Indicates how many keys (segments) are used to access the table. Key values must be on the current level or a previous level of the
configured item.

mnNumberofValues NVAL MATH_NUMERIC NONE NONE

Specifies how many values the system returns from the rules table when a match is found on the table keys. If you enter more than one
return value for a C (calculated) rule, you must indicate the segment numbers to return the values to.

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.

szUserId USER char NONE NONE

The code that identifies a user profile.

szProgramId PID char NONE 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 NONE NONE

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

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.

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

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.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
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.
szRuleTableName	TBLC	char	NONE	NONE
The name of a collection of data that you set up to minimize the number of assembly inclusion rules that you need for a configured item. You must define rule table names in user defined code table 32/TN. A rule table can be accessed by 1 to 20 keys and can return up to 99 values. When you reference a rule table in an assembly inclusion rule, the system uses the rule keys to retrieve the values that are associated with the rule table. For example, if you defined segment 10 to be the color of an item, you could set the table to retrieve item Red Component when the customer enters Red for segment 10. In this example, the table would be: Item Color = Value Red = Red Component The table would include the following: If the color segment value = red, then use item number Red Component on the configured item sales order and work order parts list.
szDescriptionLine1	DSC1	char	NONE	NONE
Brief information about an item; a remark or an explanation.
cRulesTableType	RTBT	char	NONE	NONE
A value that identifies the type of rule table. Valid values are: P Part list (on sales order and work order) Q Work order component (on work order only) C Calculated values H Hot Spot X Price/Cost adjustment
mnNumberofSegments	NSEG	MATH_NUMERIC	NONE	NONE
Indicates how many keys (segments) are used to access the table. Key values must be on the current level or a previous level of the configured item.
mnNumberofValues	NVAL	MATH_NUMERIC	NONE	NONE
Specifies how many values the system returns from the rules table when a match is found on the table keys. If you enter more than one return value for a C (calculated) rule, you must indicate the segment numbers to return the values to.
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.
szUserId	USER	char	NONE	NONE
The code that identifies a user profile.
szProgramId	PID	char	NONE	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	NONE	NONE
The code that identifies the work station ID that executed a particular job.
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.
cSuppressErrorMsgs	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.
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.