| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
| nLastCacheRow | INT01 | integer | OPT | NONE |
Number of Days in Future to Query for Responses Due.
|
| cSuppressErrorMsg | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| 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.
|
| cWoPickListPrinted | SHTY | char | OPT | NONE |
A code to designate whether or not the Work Order Pick List has been printed for a Work Order. If a 1 is in this code, the Work Order Pick
List has been printed. |
| cF3009CommitmentControl | FLD1 | char | OPT | NONE |
An option that determines how the system commits inventory to a work order, and specifies the inventory location to which commitments are
made. Valid values are:
1
Primary Location
2
Split-Cross Branch Boundaries
3
Split-Don't Cross Branch Boundaries
Note: The system
activates this field only when you create hard commitments. The three available options are as follows:
o Primary Location. Make commitments to
the primary location in the branch/plant where the work order originates.
o Split-Cross Branch Boundaries. Split the parts list and
commitments to fill any component shortages. The system can cross branch boundaries to fill requirements. In this case, the system uses the next
alphabetical branch/plant listed in the table that occurs after the branch/plant on the work order header.
For example, for the branch/plants CAL,
CHI, CLE, and HOU:
If the system starts committing inventory at branch/plant CHI, it accesses CLE as the next branch/plant. If inventory is low in
all locations, the system makes the remaining commitments to the primary location of the branch/plant on the work order header.
o
Split-Don't Cross Branch Boundaries. This option is similar to Split-Cross Branch Boundaries, but the system cannot cross branch boundaries.
Note:
When you set the Commitment Method field in the Item Branch/Plant table to 2 or 3 (lot number or expiration date control), you must use the
Split-Don't Cross Branch Boundaries option.
|
| cF3009HardSoftCommit | FLD2 | char | OPT | NONE |
An option that determines how the Shop Floor Management system commits inventory. The options are as follows:
o Hard commitment at
creation of parts list. The system performs a hard commitment at the creation of the parts list. The hard commitment remains in effect until
inventory is relieved.
o Soft commitment, then changed to hard commitment when printing. The system performs a soft commitment at the
creation of the parts list.
The system then changes the commitment to a hard commitment during the pick list print process (P31410) for the
work order. The hard commitment remains in effect until inventory is relieved.
o Soft commitment at creation of parts list. The system performs a
soft commitment at creation of the parts list. The soft commitment remains in effect until inventory is relieved.
When you set the Commitment
Method field in the Branch/Plant Constants form to
2 or 3, you must use either Hard commitment at creation of parts list or Soft commitment,
then hard commitment when printing because a hard commitment must be performed.
If you want to identify substitute items when a shortage
occurs, you must choose the hard commitment at creation of parts list option.
When you choose either Soft, Hard when printing or Soft at creation
of Parts List, any line item in the parts list may be hard-committed prior to printing or relieving the inventory.
For World:
When the hard/soft
commit option is set to 2 or 3, any line item in the parts list may be hard committed prior to printing or relieving the inventory. Valid codes are:
1
Hard commitment
2 Soft commitment, hard commitment when printing (P31410)
3 Soft commitment For OneWorld:
To specify how the
program commits inventory, click one of the following options under the Hard/Soft Commit heading:
o Hard at creation of parts list
o Soft, Hard
when printing (P31410)
o Soft at creation of parts list |
| 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.
|
| cOrigWoPickListPrinted | SHTY | char | OPT | NONE |
A code to designate whether or not the Work Order Pick List has been printed for a Work Order. If a 1 is in this code, the Work Order Pick
List has been printed. |
| cPOCheckWarehouseAvailability | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| szPOWarehouseStagingLocation | LOCN | char | OPT | NONE |
The storage location from which goods will be moved. |
| cPOWMSRequestType | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| szParentBranchPlant | 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. |
| mnLastComponentNumber | CPNB | MATH_NUMERIC | OPT | NONE |
A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially
indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the
components appear.
|
| szLotGroup | LOTGRP | char | OPT | NONE |
Lot Group is the name of a user defined list of allowed non-blank lot status codes. Entry of a Lot Group name in the Processing Option will
allow this Application to process lots whose lot status code is defined within the specified Lot Group Name.
|