| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| cSuppressErrorMessage | SUPPS | char | OPT | NONE |
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. |
| szErrorMessageID | 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.
|
| szBranchPlant | MMCU | char | REQ | 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. |
| szLineCell | MCU | char | REQ | 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.
|
| jdEffectiveFromDate | EFFF | JDEDATE | REQ | 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 | REQ | 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. |
| mnCapacityStandard | CPSD | MATH_NUMERIC | REQ | NONE |
The standard capacity level at which a production line usually operates. Capacity is stated in units per hour. This level is used for repetitive
processing only.
|
| cIncludeBlankShift | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| mnJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
| cCalendarType | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cLoadResourceErrorCode | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
| cShift | SHFT | char | REQ | NONE |
A user defined code (00/SH) that identifies daily work shifts.
In payroll systems, you can use a shift code to add a percentage or amount to
the hourly rate on a timecard.
For payroll and time entry: If an employee always works a shift for which a shift rate differential is applicable,
enter that shift code on the employee's master record. When you enter the shift on the employee's master record, you do not need to enter the
code on the timecard when you enter time. If an employee occasionally works a different shift, you enter the shift code on each applicable
timecard to override the default value. |
| szWorkDayCalendarType | WDCT | char | OPT | NONE |
A user defined code (42/WD) that specifies how the calendar is used. For example, the calendar might be specific to an industry such as
banking or it might be used to schedule delivery persons for a route.
Note: If you use the default value of *, the system updates the value to
blank even though blank is not set up as a valid value in the UDC table.
|
| szWorkDayCalendarKey | WDCK | char | OPT | NONE |
A code used to classify values within a calendar type. For example, if the calendar type is ROUTE, you can enter a code that specifies a
particular route, such as Daily or Weekend.
Note: The system does not validate the code that you enter.
|