| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szEquipmentGroup | EQGP | char | REQ | INPUT |
The name corresponding to a particular equipment group to be analyzed.
|
| szEquipmentSubGroup | EQSP | char | REQ | INPUT |
The name corresponding to a particular equipment subgroup, which is in an equipment group, to be analyzed.
|
| cSuppressErrorMessage | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
| szErrorMessageID | 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.
|
| szProgramId | PID | char | OPT | INPUT |
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.
|
| jdDtFromDate | DGL | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction is to be posted.
The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
|
| jdDtThruDate | DGL | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction is to be posted.
The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
|
| cActionCode | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
| jdDtGenerated | DGL | JDEDATE | OPT | OUTPUT |
A date that identifies the financial period to which the transaction is to be posted.
The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
|
| szEquipmentCostAnalysisType | ECAT | char | REQ | INPUT |
A code that identifies a specific equipment cost analysis type. Equipment cost analysis types control the accounts that the system includes
in the analysis and which user defined columns are available. Enter a valid value from UDC 13/CT (Equipment Cost Analysis).
|