| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnParentShortItemNumber | KIT | MATH_NUMERIC | OPT | 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. |
| szParent2ndItemNumber | LITM | char | OPT | 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.
|
| szParent3rdItemNumber | AITM | char | OPT | 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. |
| szBranchPlant | MCU | char | OPT | 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.
|
| mnParentSegmentNumber | PEL | MATH_NUMERIC | OPT | 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.
|
| 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. |
| szDescription | DSC1 | char | OPT | NONE |
Brief information about an item; a remark or an explanation.
|
| szDataItem | 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.
|
| cRequiredToBe | ATRQ | char | OPT | 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.
|
| szProductCode | SY | char | OPT | NONE |
A user defined code (98/SY) that identifies a system. Valid values include:
01
Address Book
03B
Accounts Receivable
04
Accounts
Payable
09
General Accounting
11
Multicurrency
|
| szRecordType | RT | char | OPT | NONE |
A code that identifies the table that contains user defined codes. The table is also referred to as a UDC type. |
| szDefaultValue | DVAL | char | OPT | NONE |
Used as the initial value on the data entry screen for the associated data item. The value entered must be the exact same length as the
data item size.
Place single quotes around the value if it contains any embedded blanks. The keywords *BLANKS and *ZEROS can be used
as the default value. When entering a numeric data item with default values, the redisplay of the data item suppresses all leading
zeros.
CAUTION: If a blank entry is allowed, default values should not be used. |
| szAllowedLowerValue | LVAL | char | OPT | NONE |
The lower allowed value of this specific segment. If you enter a value here,then you must also enter an upper allowed value. |
| szAllowedUpperValue | UVAL | char | OPT | NONE |
The upper allowed value of this specific segment. If you enter a value here,then you must also enter an lower allowed value. |
| cNumericSegmentIndicator | CNUM | char | OPT | NONE |
Determines whether a user defined code is numeric or alphanumeric.
Valid values are:
Y Indicates that the code is numeric and should be
right-justified.
N Indicates that the code is alphanumeric and should be left-justified. |
| mnDataItemSize | DTAS | MATH_NUMERIC | OPT | NONE |
The field size of the data item.
Note: All amount fields should be entered as 15 bytes, 0 decimals, and the data item type should be P
(packed). |
| cDataDisplayDecimals | CDEC | char | OPT | NONE |
A value that designates the number of decimals in the currency, amount, or quantity fields the system displays. For example, U.S. Dollars
would be 2 decimals, Japanese Yen would be no decimals, and Cameroon Francs would be 3 decimals. |
| mnAddressBookNumber | AN8 | MATH_NUMERIC | OPT | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
| cSaveSegment | ATSA | char | OPT | NONE |
A user defined code (32/YN) that specifices whether the segment value is significant enough to make the configuration unique. Valid values
are:
0
The segment value is not significant.
1
The segment value is significant.
If the configuration is unique, you must store the item in a
separate location in inventory.
|
| cDisplayItemNumber | DSPI | char | OPT | NONE |
A code that indicates whether the system prints the configured item number before the segment value information in the text string format or
the user defined format. Valid values are:
1
Print the configured item number
0
Do not print the configured item number
|
| cTextStringOrCustomFormat | TXTS | char | OPT | NONE |
A code that indicates whether the configured text string format or a user defined format appears on the sales order (pick slip and invoice
print) and work order (print parts list). You define the user defined format for each segment. You can choose to print the segment number,
description, value, or value description in the user defined format. Valid values are:
1
Configured text string
0
User defined format
|
| mnSpacesBeforeSegmentInfo | SPBN | MATH_NUMERIC | OPT | NONE |
The number of spaces that should print before the segment information in the user defined format. |
| cPrintSegmentNumber | ATSN | char | OPT | NONE |
A user defined code (32/YN) that specifies whether the system prints the segment number on the order paperwork. Valid values are:
0
Do
not print the segment number on the order paperwork.
1
Print the segment number on the order paperwork.
For a sales order, the system prints
the segment number on the pick slip and invoice print. For a work order,
the system prints the segment number on the parts list print.
|
| cPrintSegmentNumberDescription | ATSD | char | OPT | NONE |
A user defined code (32/YN) that specifies whether the system prints the segment description on the order paperwork. Valid values
are:
0
Do not print the segment description on the order paperwork.
1
Print the segment description on the order paperwork.
For a sales order, the
system prints the segment description on the pick slip and invoice print. For a work order, the system prints the segment description on the parts
list print.
|
| cPrintSegmentValue | ATSV | char | OPT | NONE |
A user defined code (32/YN) that specifies whether the system prints the segment value on the order paperwork. Valid values are:
0
Do not
print the segment value on the order paperwork.
1
Print the segment value on the order paperwork.
For a sales order, the system prints the
segment value on the pick slip and invoice print. For a work order, the system prints the segment value on the parts list print.
|
| cPrintSegmentValueDescription | ATVD | char | OPT | NONE |
A user defined code (32/YN) that specifies whether the system prints the segment value description on the order paperwork. Valid values
are:
0
Do not print the segment value description on the order paperwork.
1
Print the segment value description on the order paperwork.
For a
sales order, the system prints the segment value description on the pick slip and invoice print. For a work order, the system prints the segment
value description on the parts list print.
|
| mnSpacesAfterSegmentInfo | SPAN | MATH_NUMERIC | OPT | NONE |
The number of spaces that should print after the segment information in the user defined format. |
| cReturnAndStartNewLine | RTNL | char | OPT | NONE |
A user defined code (32/YN) that indicates whether the system starts a new line after it prints the segment nformation. Valid values
are:
1
Start a new line after the segment information.
0
Continue printing on the same line.
If the system does not start a new line, it prints the configurator
segment delimiter from the configurator constants.
|
| cRoundDerivedCalculation | RNDC | char | OPT | NONE |
This field will be used to indicate how many positions to the right of the decimal a derived calculation should be rounded.
For example,
o If
the result of a derived calculation is 2190.123456789, enter 0 to round to the whole number 2190.
o Enter 4 to round up to 2190.1235.
o
Leave the Derived Calculation Round field blank to avoid rounding.
The system rounds up by one any digit followed by 5 through 9. The system
does not round any digit followed by 0 through 4. |
| szUpdateCategoryCode | UPCC | char | OPT | NONE |
A code that specifies which work order category code that the system populates with the segment value during order entry.
|
| 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. |
| mnTimeUpdated | TDAY | MATH_NUMERIC | OPT | NONE |
The computer clock in hours:minutes:seconds. |