| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnIdentifierShortItem | ITM | MATH_NUMERIC | OPT | INPUT |
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 | MCU | char | OPT | INPUT |
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 | OPT | INPUT |
The storage location from which goods will be moved. |
| szLot | LOTN | char | OPT | INPUT |
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics. |
| cCostLevel | CLEV | char | OPT | INPUT |
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 |
| szLedgType | LEDG | char | OPT | INPUT |
A user defined code (40/CM) that specifies the basis for calculating item costs. Cost methods 01 through 19 are reserved for J.D. Edwards
use.
|
| mnAmountUnitCost | UNCS | MATH_NUMERIC | OPT | INPUT |
The amount per unit, derived by dividing the total cost by the unit quantity. |
| szErrorCode | DTAI | char | OPT | OUTPUT |
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.
|
| cSuppressErrorMessage | SUPPS | char | OPT | INPUT |
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.
0 = allow
runtime error message handling.
1 = suppress runtime error message handling. |
| mnJobnumberA | JOBS | MATH_NUMERIC | OPT | INPUT |
The job number (work station ID) which executed the particular job. |
| szComputerID | CTID | char | OPT | INPUT |
|
| szIdentifier2ndItem | LITM | char | OPT | INPUT |
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.
|
| mnNetQuantity | NQ01 | MATH_NUMERIC | OPT | INPUT |
The net transaction quantity from all transactions for an Item for Period 01. |
| szGlCategory | GLPT | char | OPT | INPUT |
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. |