| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szTestID | QTST | char | OPT | NONE |
The unique identification for a test to be performed on an item. For example:
COL Color test
DENS Density Test
CL-2 Clarity Test |
| szCostCenter | 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.
|
| cStatus | STAW | char | OPT | NONE |
A user-defined code (00/WS) that indicates the approval status. |
| jdEffectiveFromDate | EFFF | JDEDATE | OPT | 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 | OPT | 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. |
| cWorkFlowFlag | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cOverlapFlag | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cActionCode | ACTN | char | OPT | NONE |
A code that specifies the action that is performed. Valid values are:
A
Add
C
Change
|
| jdOriginalEffectiveFromDate | EFFF | JDEDATE | OPT | 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. |
| jdOriginalEffectiveThruDate | EFFT | JDEDATE | OPT | 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. |