Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szItemDescription1 | DSC1 | char | NONE | NONE |
Brief information about an item; a remark or an explanation.
|
szItemDescription2 | DSC2 | char | NONE | NONE |
A second, 30-character description, remark, or explanation.
|
szSalesReportingCode1 | SRP1 | char | NONE | NONE |
One of ten category codes for sales coding purposes. These codes can represent such classifications as color, material content, or use. |
szSearchText | SRTX | char | NONE | NONE |
A field that lets you specify how the system searches for an item. Your entry should be specific and descriptive of the item. Type the words
in the order a user is likely to enter them.
In single-byte environments, where computer storage space can hold only Latin-based language
character sets, the system inserts the first 30 characters from the item's description if you do not enter search text.
In double-byte environments,
where computer storage space can hold more complex language character sets (in languages such as Japanese, Chinese, and Korean),
you must complete this field. It is a single-byte field that you complete with single-byte characters to phonetically represent the item
description (which can be single-byte, double-byte, or both). |
szSearchTextCompressed | ALN | char | NONE | NONE |
The compressed version of the thirty character alpha search field, with all blanks removed. |
szSalesReportingCode2 | SRP2 | char | NONE | NONE |
One of ten category codes for sales coding purposes. These codes can represent such classifications as color, material content, or
use.
This field represents one of ten property type categories available for sales purposes. |
szSalesReportingCode3 | SRP3 | char | NONE | NONE |
One of ten category codes for sales coding purposes. These codes can represent such classifications as color, material content, or use. |
szSalesReportingCode4 | SRP4 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These codes can represent such classifications as color, material
content, or use. |
szSalesReportingCode5 | SRP5 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These codes can represent such classifications as color, material
content, or use. |
szSalesReportingCode6 | SRP6 | char | NONE | NONE |
One of ten category codes for sales coding purposes. These can represent such classifications as color, material content, or use. |
szSalesReportingCode7 | SRP7 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These can represent such things as color, material content, or use. |
szSalesReportingCode8 | SRP8 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These can represent such things as color, material content, or use. |
szSalesReportingCode9 | SRP9 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These can represent such things as color, material content, or use. |
szSalesReportingCode0 | SRP0 | char | NONE | NONE |
One of ten category codes to be used for sales coding purposes. These can represent such things as color, material content, or use. |
szPurchaseReportingCode1 | PRP1 | char | NONE | NONE |
A code (table 41/P1) that represents an item property type or classification,such as commodity type, planning family, or so forth. The
system uses this code to sort and process like items.
This field is one of six classification categories available primarily for purchasing purposes. |
szPurchaseReportingCode2 | PRP2 | char | NONE | NONE |
A code (table 41/P2) that represents an item property type or classification,such as commodity type, planning family, or so forth. The
system uses this code to sort and process like items.
This field is one of six classification categories available primarily for purchasing purposes. |
szPurchaseReportingCode3 | PRP3 | char | NONE | NONE |
A code (UDC table 41/P3) that represents an item property type or classification, such as commodity type, planning family, or so forth. The
system uses this code to sort and process like items.
This field is one of six classification categories available primarily for purchasing
purposes. |
szPurchaseReportingCode4 | PRP4 | char | NONE | NONE |
A user defined code (41/P4) that represents an item property type or classification, such as commodity type or planning family. The system
uses this code to sort and process like items.
This field is one of six classification categories available primarily for purchasing purposes. |
szPurchaseReportingCode5 | PRP5 | char | NONE | NONE |
A user defined code (41/P5) that indicates the landed cost rule for an item.
The landed cost rule determines purchasing costs that exceed
the actual price of an item, such as broker fees or commissions. You set up landed cost rules on the Landed Cost Revisions form. |
szPurchaseReportingCode6 | PRP6 | char | NONE | NONE |
A code (system 41/type 01) that identifies a group of items that share the same dimensions. An item dimension group defines the
dimensions for all items that belong to the group. After you set up an item dimension group, you can assign items to the group through Classification
Codes (41011). |
szPurchaseReportingCode7 | PRP7 | char | NONE | NONE |
A user defined code (41/02) that identifies a group of items that you want to move the same way. A process group determines what
movement instructions the system uses for putaway, picking, and replenishment. You use the Classification Codes program (P41011) to assign
items to process groups. |
szPurchaseReportingCode8 | PRP8 | char | NONE | NONE |
A user defined code (41/02) that identifies a group of items that you want to move the same way. A process group determines what
movement instructions the system uses for putaway, picking, and replenishment. You use the Classification Codes program (P41011) to assign
items to process groups. |
szPurchaseReportingCode9 | PRP9 | char | NONE | NONE |
A user defined code (41/02) that identifies a group of items that you want to move the same way. A process group determines what
movement instructions the system uses for putaway, picking, and replenishment. You use the Classification Codes program (P41011) to assign
items to process groups. |
szPurchaseReportingCode0 | PRP0 | char | NONE | NONE |
A code (table 41/P0) that represents an item property type or classification,such as commodity type, planning family, or so forth. The
system uses this code to sort and process like items.
This field is one of six classification categories available primarily for purchasing purposes. |
szCommodityCode | CDCD | char | NONE | NONE |
The commodity code number for the item. |
szItemPriceGroup | PRGR | char | NONE | NONE |
A user defined code (system 40/type PI) that identifies an inventory price group for an item.
Inventory price groups have unique pricing
structures that direct the system to incorporate discounts or markups on items on sales and purchase orders. The discounts or markups are
based on the quantity, dollar amount, or weight of the item ordered. When you assign a price group to an item, the item takes on the same pricing
structure defined for the inventory price group.
You must assign an inventory price group to the supplier or customer, as well as to the item, for
the system to interactively calculate discounts and markups on sales orders and purchase orders. |
szBasketRepriceGroup | RPRC | char | NONE | NONE |
You can assign items with common repricing characteristics to a reprice category on Item Branch/Plant Revisions. You can define different
categories based on location. Repricing is a technique that the system uses to:
o Accumulate items on order that belong to a common
repricing category during a batch program
o Compare the aggregate quantities of items on order to the appropriate quantity breaks in the
reprice category
If the items qualify for an additional discount, that discount is reflected as a change in unit and extended price for each
qualifying item in the original order line. |
szDrawingNumber | DRAW | char | NONE | NONE |
An engineering drawing number. It might be the same as the part or item number. |
szLastRevisionNumber | RVNO | char | NONE | NONE |
A subset to the drawing number. It provides an additional description of the drawing and is useful if the system uses an engineering drawing
as a reference for this item. |
cDrawingSize | DSZE | char | NONE | NONE |
A code that represents the engineering drawing size. For example:
A A-size drawing
D D-size drawing |
szPrimaryUnitOfMeasure | UOM1 | char | NONE | NONE |
A user defined code (00/UM) that identifies the unit of measure that the system uses to express the quantity of an item, for example, EA
(each) or KG (kilogram). |
szSecondaryUnitOfMeasure | UOM2 | char | NONE | NONE |
A user defined code (00/UM) that indicates an alternate unit of measure for the item. |
szPurchasingUnitOfMeasure | UOM3 | char | NONE | NONE |
A code (table 00/UM) that identifies the unit of measure in which you usually purchase the item. |
szPricingUnitOfMeasure | UOM4 | char | NONE | NONE |
A user defined code (00/UM) that indicates the unit of measure in which you usually price the item. |
szShippingUnitOfMeasure | UOM6 | char | NONE | NONE |
A user defined code (00/UM) that indicates the unit of measure in which you usually ship the item. |
szProductionUnitOfMeasure | UOM8 | char | NONE | NONE |
A user defined code (00/UM) that indicates the unit of measure in which you produce the item. |
szComponentUnitOfMeasure | UOM9 | char | NONE | NONE |
A user defined code (00/UM) that indicates the unit of measure for an item when the item serves as a component, for example, for a bill of
material or work order parts list. |
szWeightUnitOfMeasure | UWUM | char | NONE | NONE |
A user defined code (00/UM) that identifies the unit of measure that the system uses to indicate weight for this item. You can specify ounces,
grams, kilograms, and so on, as weight standards. The system uses this unit of measure for the item or overrides it for an individual item or
container. |
szVolumeUnitOfMeasure | UVM1 | char | NONE | NONE |
A user defined code (00/UM) that indicates the unit of measure by metric conversion for ambient volume. For example, the unit of measure
code for a gallon might be GL, or for a liter it might be LT. |
szShippingConditionsCode | SHCN | char | NONE | NONE |
A code (table 41/C) that represents an item property type or classification,such as special shipping conditions. The system uses this code
to sort and process like items.
This field is one of three classification categories available primarily for inventory and shipping purposes. |
szShippingCommodityClass | SHCM | char | NONE | NONE |
A user defined code (41/E) that represents an item property type or classification (for example, international shipment handling). The
system uses this code to sort and process similar items. This field is one of three classification categories available primarily for inventory and
shipping purposes.
|
szStockingUnitOfMeasure | SUTM | char | NONE | NONE |
The unit of measure commonly used to store the item. |
szCycleCountCategory | CYCL | char | NONE | NONE |
A code (table 41/8) that represents the family or cycle in which an item is counted. Cycle counting means that you count different inventory
items at different times. Cycle codes commonly represent item values, item locations, time frames, or product groups. |
cInventoryCostLevel | CLEV | char | NONE | NONE |
A code that indicates whether the system maintains one overall inventory cost for the item, a different cost for each branch/plant, or a
different cost for each location and lot within a branch/plant. The system maintains inventory costs in the Inventory Cost table (F4105).
Valid codes
are:
1 Item level
2 Item/Branch level
3 Item/Branch/Location level |
cSalesPriceLevel | PLEV | char | NONE | NONE |
A code that indicates whether the system maintains standard sales prices for an item, different sales prices for each branch/plant, or
different sales prices for each location and lot within a branch/plant. The system maintains sales prices in the Base Price file (F4106). Valid codes
are:
1 Item level
2 Item/Branch level
3 Item/Branch/Location level |
cPurchasePriceLevel | PPLV | char | NONE | NONE |
A code that indicates where to retrieve the purchase price for an item when you enter a purchase order. Valid codes are:
1 Use the
supplier/item price from the Purchase Price table (F41061).
2 Use the supplier/item/branch price from the Purchase Price table (F41061).
3 Use
the inventory cost from the Inventory Cost table (F4105). This cost is based on the inventory cost level and the purchasing cost method you
specify for the item.
The first two codes are applicable only if you set up supplier costs in the Procurement system. If you do not set up
supplier costs, the system uses the inventory cost as the default for the purchase order. |
cSourceLayerCode | SRCE | char | NONE | NONE |
A code that indicates whether lot or serial number is assigned. Lot and serial number processes use the Lot Master table (F4108).
Valid
codes are:
0 Lot assignment is optional. You can manually assign numbers. Quantity can be greater than one. (Default)
1 Lot assignment is
required. The system assigns numbers using the system date in YYMMDD format. Quantity can be greater than one.
2 Lot assignment is
required. The system assigns numbers in ascending order using Next Numbers. Quantity can be greater than one.
3 Lot assignment is
required. You must manually assign numbers. Quantity can be greater than one.
4 Serial number assignment is optional except during shipment
confirmation. Quantity must not exceed one.
5 Serial number assignment is required. The system assigns numbers using the system date
in YYMMDD format. Quantity must not exceed one.
6 Serial number assignment is required. The system assigns numbers in ascending
order using Next Numbers. Quantity must not exceed one.
7 Serial number assignment is required. You must manually assign numbers.
Quantity must not exceed one. |
cComponentType | COTY | char | NONE | NONE |
The component type determines what the component is used for in a bill of material. For example:
A Active ingredient
C Standard
Component
F Filler ingredient |
cStockingType | STKT | char | NONE | NONE |
A user defined code (41/I) that indicates how you stock an item, for example, as finished goods or as raw materials. The following stocking
types are hard-coded and you should not change them:
0 Phantom item
B Bulk floor stock
C Configured item
E Emergency/corrective
maintenance
F Feature
K Kit parent item
N Nonstock
The first character of Description 2 in the user defined code table indicates if the item
is purchased (P) or manufactured (M). |
szLineType | LNTY | char | NONE | NONE |
A code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as
General Ledger, Job Cost, Accounts Payable, Accounts Receivable, and Inventory Management. It also specifies the conditions under
which a line prints on reports, and it is included in calculations. Codes include the following:
S
Stock item
J
Job cost
N
Nonstock item
F
Freight
T
Text information
M
Miscellaneous charges and credits
W
Work order |
cContractItem | CONT | char | NONE | NONE |
An indication, updated internally, that there are one or more formal contracts in place which specify a quantity and price at which this item is
to be sold to specific customers. |
szPrintMessage | INMG | char | NONE | NONE |
A user defined code that you assign to each print message. Examples of text used in messages are engineering specifications, hours of
operation during holiday periods, and special delivery instructions. |
cABCCodeForSales | ABCS | char | NONE | NONE |
A code that specifies this item's ABC ranking by sales amount.
Valid values are:
A Assign this item to the first (largest) amount ranking
B
Assign this item to the second (intermediate) amount ranking
C Assign this item to the third (smallest) amount ranking
D Do not include this
item when you run ABC Analysis There are three types of ABC analysis-sales, margin, and on-hand value. Within each type of analysis, you
can have three groups-A, B, and C.
The ABC Code fields contain a percentage that tells the system how to define the A, B, and C groups for
categorizing items during ABC analysis. Each group measures a total within the type of analysis.
For all groups, the system compares the
appropriate sales, margin, or on-hand value totals of a single item to the appropriate total for all items and calculates the value of each item. An
item's value is its percentage of the appropriate total. The system then arranges the values of all items from highest to lowest value and
accumulates the percentages. What happens next depends on the group:
A group: If an item's value causes the accumulated total to exceed the
A accumulated percentage, the system assigns the item to the B group.
B group: When the accumulated total reaches the percentage you
entered for items in the A group, it continues adding values until it reaches the percentage you entered for items in the B group. The system
assigns all items whose value falls between the A and B percentages to the B group.
C group: The C group consists of items whose
accumulated value exceeds the B percentage. The percentage that you usually enter for the C group is .999. |
cABCCodeForMargin | ABCM | char | NONE | NONE |
Code indicating this item's ABC ranking by margin amount. Valid values are:
A Assign this item to the first amount ranking
B Assign this
item to the second amount ranking
C Assign this item to the third amount ranking
D Skip this item in the ABC Analysis There are three types of
ABC analysis--sales, margin, and on-hand value.
Within each type of analysis, you can have three groups--A, B, and C.
The ABC Code fields
contain a percentage that tells the system how to define the A, B, and C groups for categorizing items during ABC analysis. Each group
measures a total within the type of analysis.
For all groups, the system compares the appropriate sales, margin, or on-hand value totals of a
single item to the appropriate total for all items and calculates the value of each item. An item's value is its percentage of the appropriate total.
The system then arranges the values of all items from highest value to lowest value and accumulates the percentages. What happens next
depends on the group:
A group: When the accumulated total reaches the percentage you entered, the system assigns the items whose values
are included in the A group. If an item's value causes the total to exceed the A accumulated percentage, the system assigns the item to the B
group.
B group: When the accumulated total reaches the percentage you entered, the system assigns the items whose values are
included in the A group. If an item's value causes the total to exceed the A accumulated percentage, the system assigns the item to the B group.
C
group: The C group consists of items whose accumulated value exceeds the B percentage. The percentage that you usually enter for the C
group is .999. |
cABCCodeForInvestment | ABCI | char | NONE | NONE |
Code indicating this item's ABC ranking by investment in inventory. Valid values are:
A Assign this item to the first amount ranking
B
Assign this item to the second amount ranking
C Assign this item to the third amount ranking
D Skip this item in the ABC Analysis There are three
types of ABC analysis--sales, margin, and on-hand value.
Within each type of analysis, you can have three groups--A, B, and C.
The ABC
Code fields contain a percentage that tells the system how to define the A, B, and C groups for categorizing items during ABC analysis. Each
group measures a total within the type of analysis.
For all groups, the system compares the appropriate sales, margin, or on-hand value totals
of a single item to the appropriate total for all items and calculates the value of each item. An item's value is its percentage of the appropriate
total. The system then arranges the values of all items from highest value to lowest value and accumulates the percentages. What
happens next depends on the group:
A group: When the accumulated total reaches the percentage you entered, the system assigns the items
whose values are included in the A group. If an item's value causes the total to exceed the A accumulated percentage, the system assigns the
item to the B group.
B group: When the accumulated total reaches the percentage you entered for items in the A group, it continues adding
values until it reaches the percentage you entered for items in the B group. The system assigns all items whose value falls between the A and
B percentages to the B group.
C group: The C group consists of items whose accumulated value exceeds the B percentage. The
percentage that you usually enter for the C group is .999. |
cABCCodeOverride | OVR | char | NONE | NONE |
Maintained automatically by the program, a value here indicates that one or more aspects of an individual item's ABC classification has
been changed by a user from the codes generated by the ABC analysis program. |
szWarrantyType | WARR | char | NONE | NONE |
A code that identifies the length and extent of a particular warranty. (Future use) |
szCommissionCategory | CMCG | char | NONE | NONE |
Items with common commission characteristics are assigned to a common category. The assignment is made in the Item Master
Revisions or may be made at the individual item location level. For more information, see Commission/Royalty Information. |
cSerialNumbeRequired | SRNR | char | NONE | NONE |
A code that specifies whether you must attach a serial number to this item at receipt or sale for basic serial number processing, or whether
memo lot information is required for advanced serial number processing. Advanced serial number processing allows you to use a serial
number to track an item through purchasing and sales. For basic serial number processing, valid values are:
Y
Yes, the system requires a serial
number for all transactions pertaining to this item in related inventory, sales, and purchase order programs.
N
No, the system does not require
a serial number.
To specify lots for items with serial numbers, valid values are:
3
Supplier lot number is required (purchasing only).
4
Supplier
lot number is required (purchasing only). Memo lot 1 is also required.
5
Supplier lot number is required (purchasing only). Memo lot 1 and
memo lot 2 are also required.
6
Non-serialized item number (CSMS only).
Values 3 through 5 specify whether lot assignment is required for items
with serial numbers. You can require assignment of up to three lot numbers, including supplier lot, memo lot 1, and memo lot 2.
|
cKitPricingMethod | PMTH | char | NONE | NONE |
A code that determines how the system calculates the price for kit items or configured items. Valid values are:
Blank
Use for items that are
neither kit items nor configured items.
1
The system accumulates the base prices of components with the configured price adjustments, and
then discounts the total.
2
The system accumulates the base price of the parent item with the configured price adjustments, and then discounts
the total.
3
The system accumulates the configured price adjustments, and then discounts the total.
4
The system accumulates the individually
discounted price of the components with the configured price adjustments.
Note: Configured price adjustments are only included in the
calculation for a configured item. Also, the system only discounts costs if you are using the Advanced Pricing system.
The following is an example of
how the system uses the various methods:
Parent Item: 125
Component A: 50
Component B: 100
Configured Cost Adjustment 1: 15
Configured
Cost Adjustment 2: 10
Advanced Price Discount: 10%
Methods:
1: 50 + 100 = 150 + 15 + 10 = 175 - 17.50 = 157.5
2: 125 + 15 + 10 = 150 - 15 = 135
3:
15 + 10 + 25 - 2.5 = 22.5
4: (50 - 5) + (100 - 10) = 135 + 15 + 10 = 160
|
cLotStatusCode | LOTS | char | NONE | NONE |
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes
indicate that the lot is on hold.
You can assign a different status code to each location in which a lot resides on Item/Location Information or
Location Lot Status Change. |
cPlanningCode | MPST | char | NONE | NONE |
A code that indicates how Master Production Schedule (MPS), Material Requirements Planning (MRP), or Distribution Requirements
Planning (DRP) processes this item. Valid codes are:
0 Not Planned by MPS, MRP, or DRP
1 Planned by MPS or DRP
2 Planned by MRP
3 Planned by MRP with additional independent forecast
4 Planned by MPS, Parent in Planning Bill
5 Planned by MPS, Component in
Planning Bill
These codes are hard coded. |
szPartStatusCode | PTSC | char | NONE | NONE |
A code (table 31/MS) that designates the status of an item. |
cRoundToWholeNumber | SNS | char | NONE | NONE |
A code that determines whether the system performs rounding for planning purposes. Valid values are:
R Round either up or down to the
nearest whole number.
U Round up to the nearest whole number.
Blank Do not round.
Example of value R: If the calculated requirements for
an item are 4.6, the system rounds the quantity required to 5.0. If the calculated requirements are 4.4, the system rounds the quantity required
to 4.0.
Example of value U: If the calculated requirements for an item are greater than 4.0 and less than or equal to 5.0, the system rounds the
quantity required to 5.0. |
cOrderPolicyCode | OPC | char | NONE | NONE |
A code that specifies the rules for inventory reordering in the Requirements Planning and Procurement systems. Valid values are:
0
Reorder
point (Not planned by MPS/MRP/DRP)
1
Lot-for-lot or as required
2
Fixed order quantity
3
Economic order quantity (EOQ)
4
Periods of
supply
5
Rate scheduled item
Note: These values are hard-coded.
|
cPlanningFenceRule | MPSP | char | NONE | NONE |
A code (system 34, table TF) that the system uses in conjunction with the Planning Time Fence Days field to determine how forecast
demand or actual customer demand is used.
For example:
S tells the system to plan using customer demand before the time fence and forecast
after the time fence
F tells the system to plan using forecast before the time fence and forecast plus customer demand after the time fence
If
you enter 5 in the Planning Time Fence Days field and S in this field, then the system uses only customer demand for the regeneration for the
first 5 days. After 5 days, the system uses the forecast for the regeneration.
Valid codes are:
C Customer demand before, greater of forecast
or customer demand after
F Forecast before, forecast plus customer demand after
G Greater of forecast or customer demand before,
forecast after
S Customer demand before, forecast after
1 Zero before, forecast after
3 Zero before, forecast plus customer demand after |
cLeadtimeType | MRPP | char | NONE | NONE |
A code that determines whether the system uses fixed or variable leadtimes.
This code works in conjunction with the value from either the
Level Leadtime field or the Leadtime Per Unit field. Valid codes are:
F Fixed leadtime - The system calculates work order start dates using the
value from the Leadtime Level field.
V Variable leadtime - The system calculates work order start dates using the value from the Leadtime
Per Unit field. |
cBackordersAllowed | BACK | char | NONE | NONE |
An option that specifies whether to allow backorders for this item. You can allow backorders by item using the Item Master (P4101) or Item
Branch/Plant (P41026) programs, by customer using the Customer Billing Instructions program (P03013), or by branch/plant using the
Branch/Plant Constants program (P41001). Valid values are:
On
Allow backorders for this item.
Off
Do not allow backorders for this item, regardless of
the backorders code that is assigned to the customer.
|
szItemFlashMessageIO | IFLA | char | NONE | NONE |
User defined code system 40, type FL, which is used to flash a warning message about a particular item. |
cFifoProcessing | FIFO | char | NONE | NONE |
|
cIssueTypeCode | ITC | char | NONE | NONE |
A code that indicates how the system issues each component in the bill of material from stock. In Shop Floor Management, it indicates how
the system issues a part to a work order. Valid values are:
I Manual issue
F Floor stock (there is no issue)
B Backflush (when the part is
reported as complete)
P Preflush (when the parts list is generated)
U Super backflush (at the pay-point operation)
S Sub-contract item (send
to supplier)
Blank Shippable end item
You can issue a component in more than one way within a specific branch/plant by using different
codes on the bill of material and the work order parts list. The bill of material code overrides the branch/plant value. |
cOrderWithCode | ORDW | char | NONE | NONE |
Future use. The Order With code determines if work order generation (P31410) will explode this items bill of material to create orders for this
items components. |
cMakeBuyCode | MAKE | char | NONE | NONE |
This code is used in conjunction with the stocking type code to define the origin of the part. |
cCoOrByProduct | COBY | char | NONE | NONE |
A code that distinguishes standard components or ingredients from co-products,by-products, and intermediates. Co-products are
(concurrent) end items as the result of a process. By-products are items that can be produced at any step of a process, but were not planned.
Intermediate products are items defined as a result of a step but are automatically consumed in the following step.
Generally, intermediates are
nonstock items and are only defined steps with a pay-point for reporting purposes. Standard components (Discrete Manufacturing)
or ingredients
(Process Manufacturing) are consumed during the production process. Valid values are:
C Co-products
B By-products
I Intermediate
products
Blank Standard components or ingredients |
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. |
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.
|
cBulkPackedFlag | BPFG | char | NONE | NONE |
A code that indicates if the item is a bulk liquid product. If it is a bulk product, you must perform temperature and density/gravity
conversions. To record the movement of bulk products, you must use forms designed specifically for bulk products. If you try to record movement using
standard inventory forms, the system prevents the movement. Valid values are:
P Packaged
B Bulk liquid
If you leave this field blank, the
system uses P. |
cPotencyControl | OT1Y | char | NONE | NONE |
A code that indicates whether you control the item by potency. |
cGradeControl | OT2Y | char | NONE | NONE |
A code that indicates whether you control the item by grade. |
szStandardGrade | STDG | char | NONE | NONE |
A code (table 40/LG) that represents the normal grade for an item. |
szFromGrade | FRGD | char | NONE | NONE |
A user defined code (40/LG) that indicates the minimum grade that is acceptable for an item.
The system displays a warning message if
you try to purchase or issue items with grades that do not meet the minimum grade acceptable. The system does not allow you to sell items
with grades that do not meet the minimum acceptable level. |
szThruGrade | THGD | char | NONE | NONE |
A user defined code (40/LG) that indicates the maximum grade that is acceptable for an item.
The system displays a warning message if
you try to purchase or issue items with grades that exceed the maximum grade acceptable. The system does not allow you to sell items with
grades that exceed the maximum grade acceptable. |
cCommitmentMethod | CMGL | char | NONE | NONE |
A code that indicates the method that the system uses to commit lot items from inventory. Valid codes are:
1 The normal commitment
method for inventory. The system commits inventory from the primary location and then from secondary locations.
The system commits
inventory from the locations with the most inventory before committing inventory from locations with the least. The system commits backorders to
the primary location.
2 The inventory commitment method by lot number. The system commits inventory by lot number, starting with the
lowest lot number and committing orders to available lots.
3 The inventory commitment method by lot expiration date. The system commits
inventory from the locations with the earliest expiration date first. The system considers only locations with expiration dates greater than or equal
to the sales order or parts list requested date. |
cCheckAvailability | CKAV | char | NONE | NONE |
A code that specifies whether the system performs availability checking. You might want to turn on availability checking for certain items.
For other items, if you assume that an adequate supply is available, leave availability checking turned off. For PeopleSoft World, valid values
are:
Y
The system performs availability checking.
N
The system does not perform availability checking.
For PeopleSoft EnterpriseOne, a
check mark indicates that availability checking is turned on.
|
szProductGroup | PDGR | char | NONE | NONE |
A line of products whose similarity allows them to be grouped together. This grouping can be used to select products for other tasks or
processes such as reporting with DREAM Writer. |
szDispatchGroup | DSGP | char | NONE | NONE |
A user defined code that identifies the dispatch group. A dispatch group is a grouping you make for products according to the physical
characteristics that are important when storing and transporting those products.
During the trip building process, the system checks if the dispatch
group for the item and the vehicle are compatible. The system only allows products belonging to the allowed dispatch groups to be
assigned to the vehicle. |
mnBuyerNumber | BUYR | MATH_NUMERIC | NONE | NONE |
The address number of the person responsible for setting up and maintaining the correct stocking levels for the item. |
mnVolumeDimensions | VCUD | MATH_NUMERIC | NONE | NONE |
The numeric value of the cubic volume of this item - computed by the Item Master Revisions program. |
mnCarrierNumber | CARS | MATH_NUMERIC | NONE | NONE |
The address number for the preferred carrier of the item. The customer or your organization might prefer a certain carrier due to route or
special handling requirements. |
mnPreferredCarrier | CARP | MATH_NUMERIC | NONE | NONE |
The address book number for the preferred carrier of the item. The supplier or your organization might prefer a certain carrier because of
route or special handling requirements. |
mnStandardPotency | STDP | MATH_NUMERIC | NONE | NONE |
The percentage of active ingredients normally found in an item. |
mnFromPotency | FRMP | MATH_NUMERIC | NONE | NONE |
A number that indicates the minimum potency or percentage of active ingredients acceptable for an item.
The system displays a warning
message if you try to purchase or issue items that do not meet the minimum acceptable potency. The system does not allow you to sell items
that do not meet the minimum acceptable potency. |
mnThruPotency | THRP | MATH_NUMERIC | NONE | NONE |
A number that indicates the maximum potency or percentage of active ingredients that is acceptable for an item.
The system displays a
warning message if you try to purchase or issue items that have a potency that exceeds the maximum potency acceptable. The system does
not allow you to sell items that have a potency that exceeds the maximum potency acceptable. |
mnShelfLifeDays | SLD | MATH_NUMERIC | NONE | NONE |
The number of days that an item can remain in inventory before it expires. The system adds this number to the date that the item is received
to determine the expiration date for the item. If you do not enter a value here, you must enter an expiration date each time you receive the lot
item. |
mnPlanningCode | ANPL | MATH_NUMERIC | NONE | NONE |
The address number of the material planner for this item. |
mnPercentMargin | PCTM | MATH_NUMERIC | NONE | NONE |
As used in the Item Location (F41021) file, a facility the system uses to maintain a consistent profit margin on items whose costs change
frequently. By specifying a value, any change to the item's cost causes the system to adjust the list price.
As used in a variety of sales reports,
the percent margin represents the ratio between the gross profit earned on a sale and the total amount of the sale itself. |
mnMarginMaintenance | MMPC | MATH_NUMERIC | NONE | NONE |
This field is used as a method to automatically maintain a desired margin. If a value is entered in this field, every purchase order receipt will
add the margin percentage to the item's cost, if the costing method is 1, 2, or 6, in order to generate a new list price.
For example: Item cost =
56.00, and Margin Maintenance % = 20, then the new list price will be as follows:
56 * ( 1 + .20 ) = 67.20 |
mnLeadtimeLevel | LTLV | MATH_NUMERIC | NONE | NONE |
A value that represents the leadtime for an item at its assigned level in the production process, as defined on Plant Manufacturing Data.
The system uses this value to calculate the start dates for work orders using fixed leadtimes.
Level leadtime is different for purchased and
manufactured items:
Purchased - The number of calendar days required for the item to arrive at your branch/plant after the supplier receives your
purchase order.
Manufactured - The number of workdays required to complete the fabrication or assembly of an item after all the
components are available.
You can enter level leadtime manually on Manufacturing Values Entry, or you can use the Leadtime Rollup program to
calculate it. To calculate level leadtime using the Leadtime Rollup program, you must first enter a quantity in the Manufacturing Leadtime Quantity
field in the Item Branch table (F4102). |
mnLeadtimeManufacturing | LTMF | MATH_NUMERIC | NONE | NONE |
The total number of days required to build an item from its lowest level components to the final assembly. This value is the total of the level
leadtimes for all manufactured items, plus the highest manufacturing leadtime for all its components.
If all components are purchased, the
manufacturing leadtime equals the item's level leadtime. Purchased item leadtimes are not included in the calculation of manufacturing
leadtimes.
You can enter the manufacturing leadtime manually or you can have the system calculate it when you run the Leadtime Rollup program. |
mnLeadtimeCummulative | LTCM | MATH_NUMERIC | NONE | NONE |
The total number of days required to build an item from its lowest level components to the final assembly. The system calculates the value
differently for manufactured and purchased items.
Manufactured - The total of all level leadtimes for all manufactured items,plus the highest
cumulative leadtime of all its components.
Purchased - The item's level leadtime. Purchased item leadtimes are included in the calculation of
cumulative leadtimes.
You can enter this value manually or you can have the system calculate it when you run the Leadtime Rollup program. |
mnValueOrderPolicy | OPV | MATH_NUMERIC | NONE | NONE |
A value that the system uses in conjunction with the order policy code to represent one of the following:
o When you select order policy
code 2 (fixed order quantity), this value represents the fixed order quantity.
o When you select order policy 4 (periods of supply), this value
represents the number of days of net requirements that the system uses to determine order size.
o When you select order policy code 5 (rate
scheduled item), this value represents the desired inventory level. When the ending available quantity is less than the desired inventory level,
then the system issues an "increase rate to" message. When the ending available quantity is greater than the desired inventory level, then
the system issues a "decrease rate to" message.
|
mnAccountingCostQuantity | ACQ | MATH_NUMERIC | NONE | NONE |
An amount that the system uses in the Cost Rollup program to determine the allocation of setup costs. The system totals the setup costs
and divides the sum by this quantity to determine a unit setup cost. The default is 1. |
mnMfgLeadtimeQuantity | MLQ | MATH_NUMERIC | NONE | NONE |
The quantity that determines the leadtime level for a manufactured item. Each of the routing steps for the item are extended by this quantity.
For the system to calculate the leadtime level, the quantity in this field must be a value other than zero. |
mnLeadtimePerUnit | LTPU | MATH_NUMERIC | NONE | NONE |
The total number of hours required to build one unit as specified on the routing. This value is factored by the time basis code.
You can enter
this value manually or you can have the system calculate it when you run the Leadtime Rollup program. The system overwrites this value
when you run the Leadtime Rollup program.
The system uses this field to calculate start dates for work orders when you use variable leadtimes. |
mnPlanningtimeFence | MTF1 | MATH_NUMERIC | NONE | NONE |
The number of days that the system uses in conjunction with the time fence rule to determine how the forecast is used. Enter the number of
days after the start date when the time fence rule changes from the first rule to the second rule.
For example, if the time fence rule is S (customer
demand before the time fence, forecast after the time fence), the generation start date is 01/03/05,and the planning time fence is 3 days, the
system plans using customer demand through 01/06/05. Beginning on 01/07/05, the system plans using the forecast.
Note that:
o The
system does not count the generation start date; that is, the day after the generation start date is day 1.
o For manufactured items, the system
counts working days, as defined in the Shop Floor Calendar.
o For purchased items, the system counts calendar days. |
mnFreezeFence | MTF2 | MATH_NUMERIC | NONE | NONE |
The number of days from the generation start date within which the system does not generate action messages.
For example, if the
generation start date is 01/03/05, and the freeze time fence is 3 days, the planning system does not generate messages with required dates that are
less than or equal to 01/06/05.
Note:
o The system does not count the generation start date; that is, the day after the generation start date is
day 1.
o For manufactured items, the system counts working days, as defined in the shop floor calendar.
o For purchased items, the system
counts calendar days.
|
mnMessageDisplayFence | MTF3 | MATH_NUMERIC | NONE | NONE |
The number of days after the generation start date within which the system should display order messages.
For example, if the generation
start date is 01/01/05, and the message time fence is 30 days, the system displays messages with dates less than or equal to 01/31/05. The
system does not display messages with dates of 02/01/05 or later. However, the planning horizon for orders continues past this date and is
reflected in available to promise totals.
Note that:
o The system does not count the generation start date; that is, the day after the generation
start date is day 1.
o For manufactured items, the system counts working days, as defined in the Shop Floor Calendar.
o For purchased
items, the system counts calendar days. |
mnTimeFence | MTF4 | MATH_NUMERIC | NONE | NONE |
Manufacturing time fence 4 - Future use. |
mnShipmentLeadtimeOffset | MTF5 | MATH_NUMERIC | NONE | NONE |
Manufacturing time fence 5 - Future use. |
mnExpediteDamperDays | EXPD | MATH_NUMERIC | NONE | NONE |
|
mnDeferDamperDays | DEFD | MATH_NUMERIC | NONE | NONE |
|
mnSafetyLeadtime | SFLT | MATH_NUMERIC | NONE | NONE |
The safety leadtime is used in DRP/MPS/MRP processing as a safety leadtime for the item. The safety leadtime is used as cusion to the
level leadtime. |
mnLowLevelCode | LLX | MATH_NUMERIC | NONE | NONE |
This identifies the lowest level in any bill of material at which a particular component may appear.. |
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. |
szGLCategory | GLPT | char | NONE | NONE |
A user defined code (41/9) that identifies the G/L offset that system uses when it searches for the account to which it posts the transaction. If
you do not want to specify a class code, you can enter **** (four asterisks) in this field.
You can use automatic accounting instructions (AAIs) to
predefine classes of automatic offset accounts for the Inventory Management, Procurement, and Sales Order Management systems. You
might assign G/L class codes as follows:
IN20 Direct Ship Orders
IN60 Transfer Orders
IN80 Stock Sales
The system can generate
accounting entries based upon a single transaction. For example, a single sale of a stock item can trigger the generation of accounting entries
similar to the following:
Sales-Stock (Debit) xxxxx.xx
A/R Stock Sales (Credit) xxxxx.xx
Posting Category: IN80
Stock Inventory
(Debit) xxxxx.xx
Stock COGS (Credit) xxxxx.xx
The system uses the class code and the document type to find the AAI. |
szOrderRepriceGroup | ORPR | char | NONE | NONE |
Items with common order repricing characteristics are assigned to an order reprice category on the Item Master Revisions screen.
Categories can be varied at the Location level (fold area). Order repricing is a technique in which items within an order that belong to the same
repricing category are accumulated during a batch program and their aggregate quantities are compared to the appropriate quantity "breaks" in
the reprice category. Typical quantity breaks in this situation might be the total weight or the total dollar value of the order as whole. If the
items qualify for additional discount, that discount is reflected as a flat dollar amount in a new discount line. This facility supplements the repricing
function and operates in the same batch program. |