| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnShortItemNumber | ITM | MATH_NUMERIC | NONE | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
| szCostCenter | MMCU | char | NONE | NONE |
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:
o Branch/Plant (MMCU)
o Dept A (MCU)
o Dept B (MCU)
o Job 123
(MCU)
Business unit security is based on the higher-level business unit. |
| szCostType | COST | char | NONE | NONE |
A code that designates each element of cost for an item. Examples of the cost object types are:
o A1 Purchased raw material
o B1
Direct labor routing rollup
o B2 Setup labor routing rollup
o C1 Variable burden routing rollup
o C2 Fixed burden routing rollup
o Dx Outside
operation routing rollup
o Xx Extra add-ons, such as electricity and water
The optional add-on computations usually operate with the type
Xx extra add-ons. This cost structure allows you to use an unlimited number of cost components to calculate alternative cost rollups. The
system then associates these cost components with one of six user defined summary cost buckets.
|
| jdFromDate | 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. |
| szLandedCostRule | 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. |
| mnItemNumber | ITM | MATH_NUMERIC | NONE | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
| szSecondItemNumber | 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.
|
| szThirdItemNumber | 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. |
| szBranchPlant | MCU | char | NONE | NONE |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
| szLocation | LOCN | char | NONE | NONE |
The storage location from which goods will be moved. |
| szLot | LOTN | char | NONE | NONE |
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics. |
| szCostLevel | LVLA | char | NONE | NONE |
User defined code (table 40/CA) designating an add-on cost. This code also specifies the sequence of the cost add-ons for a particular
item or group of items. |
| szBasedOnLevel | LVLB | char | NONE | NONE |
User defined code (table 40/CA) designating the basis of cost for an item. If you use this code, you can roll costs based on a previous level
total. |
| mnCostAddOn | PCST | MATH_NUMERIC | NONE | NONE |
Percentage of the item's primary purchasing cost that the system add as a landed cost component to the base cost of the item as indicated
on a purchase order. |
| mnAmountAddOn | PAMT | MATH_NUMERIC | NONE | NONE |
An amount to be added to the indicated cost to equal the total cost amount. |
| mnFreightAddOn | RATF | MATH_NUMERIC | NONE | NONE |
The system multiplies the rate you add to this field by the unit weight you specify for an inventory item to calculate a landed cost
component. |
| mnVolumeRate | RATV | MATH_NUMERIC | NONE | NONE |
The system multiplies the rate you add to this field by the unit volume you specify for an inventory item to calculate a landed cost
component. |
| mnSupplier | AN8 | MATH_NUMERIC | NONE | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
| szGLClass | GLC | char | NONE | NONE |
A code that determines the trade account that the system uses as the offset when you post invoices or vouchers. The system concatenates
the value that you enter to the AAI item RC (for Accounts Receivable) or PC (for Accounts Payable) to locate the trade account. For
example, if you enter TRAD, the system searches for the AAI item RCTRAD (for receivables) or PCTRAD (for payables).
You can assign up to four
alphanumeric characters to represent the G/L offset or you can assign the three-character currency code (if you enter transactions in a
multicurrency environment). You must, however, set up the corresponding AAI item for the system to use; otherwise, the system ignores the G/L
offset and uses the account that is set up for PC or RC for the company specified.
If you set up a default value in the G/L Offset field of the
customer or supplier record, the system uses the value during transaction entry unless you override it.
Note: Do not use code 9999. It is reserved for
the post program and indicates that offsets should not be created.
|
| 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. |
| 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. |
| cTaxable | TX | char | NONE | NONE |
A code that indicates whether the item is subject to sales tax when you purchase it. The system calculates tax on the item only if the supplier
is also taxable. |
| cIncludeInUnitCost | INYN | char | NONE | NONE |
Code indicating whether you want the landed cost to be added to the item's unit cost. Valid codes are:
Y Add the landed cost to the unit
cost
N Do not add the landed cost to the unit cost |
| cVoucher | RCYN | char | NONE | NONE |
Code indicating whether the landed cost is to be displayed during Voucher Match or not. The possible values are as follows:
Y A receipt
record (F43121) is created, and the landed cost may be vouchered in the Voucher Match program. The Landed Cost Code (LAND) field in
the receipt record will contain a value of 2.
N A receipt record (F43121) is created, but the landed cost is not allowed to be vouchered in the
Voucher Match program. The Landed Cost Code (LAND) field in the receipt record will contain a value of 3. The receipt record is necessary if
the receipt is reversed.
NOTE: Journal entries are still created when the value is N. As a result, you may want the Landed Cost AAI's
(4385/4390) pointed to the same G/L account, in order to cancel out the entries. |
| szAisle | AISL | char | NONE | NONE |
A code that identifies a location in a warehouse. This code is used in conjunction with a bin and lot identifier, to indicate a specific, tangible
storage area within a warehouse or yard. |
| szBin | BIN | char | NONE | NONE |
A specific storage location within a warehouse or store. The system uses the bin with an aisle location to identify a storage area whose
width, depth, and height can be readily measured. |