| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnIdentifierShortItem | ITM | MATH_NUMERIC | OPT | 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 |
| szSupplying_LOCN | LOCN | char | OPT | NONE |
The storage location from which goods will be moved. |
| szConsuming_TLOC | TLOC | char | OPT | NONE |
The storage location to which goods will be moved. |
| szSupplyingBranch_MCU | 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.
|
| szConsumingBr_MMCU | MMCU | char | OPT | 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. |
| mnNumofKanbans_MATH01 | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
| mnCapacity | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
| mnDemand | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
| mnDifference | MATH01 | MATH_NUMERIC | OPT | NONE |
- - - Good Performance Low Value.
|
| mnKanbansizequantity | KBQT | MATH_NUMERIC | OPT | NONE |
The total size of the kanban. |
| jdEndDate_DRQJ | DRQJ | JDEDATE | OPT | NONE |
The date that an item is scheduled to arrive or that an action is scheduled for completion.
|
| jdStartDate_STRT | STRT | JDEDATE | OPT | NONE |
The start date for the order. You can enter this date manually, or have the system calculate it using a backscheduling routine. The routine
starts with the required date and offsets the total leadtime to calculate the appropriate start date.
|
| cAdhocCardExists_EV01 | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| 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.
|