| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szJob | MCU | char | REQ | INPUT |
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.
|
| szCostCode | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
| szCostType | OBJ | char | REQ | INPUT |
The portion of a general ledger account that refers to the division of the Cost Code (for example, labor, materials, and equipment) into
subcategories. For example, you can divide the Cost Code for labor into regular time, premium time, and burden.
Note: If you use a flexible chart of
accounts and the object account is set to 6 digits, J.D. Edwards recommends that you use all 6 digits. For example, entering 000456 is not
the same as entering 456 because if you enter 456 the system enters three blank spaces to fill a 6-digit object. |
| mnCentury | CTRY | MATH_NUMERIC | OPT | INPUT |
The calendar century associated with the year. Enter is the first two digits of
the year. For example, 19 indicates any year beginning with 19
(1998, 1999),
20 indicates any year beginning with 20 (2000, 2001), and so on.
|
| mnFiscalYear | FY | MATH_NUMERIC | OPT | INPUT |
A number that identifies the fiscal year. Generally, you can either enter a number in this field or leave it blank to indicate the current fiscal
year (as defined on the Company Setup form).
Specify the year at the end of the first period rather than the year at the end of the fiscal period.
For example, a fiscal year begins October 1, 1998 and ends September 30, 1999. The end of the first period is October 31, 1998. Specify the
year 98 rather than 99. |
| mnPeriodNumber | PN | MATH_NUMERIC | OPT | INPUT |
A number indicating the current accounting period. This number, used in conjunction with the Company Constants table (F0010) and the
General Constants table (F0009), allows the user to define up to 14 accounting periods. See General Ledger Date. The current period number
is used to determine posted before and posted after cut off warning messages. It is also used as the default accounting period in the
preparation of financial reports.
|
| szSubledger | SBL | char | OPT | INPUT |
A code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an
address book number. If you enter a subledger, you must also specify the subledger type. |
| cSubledgerType | SBLT | char | OPT | INPUT |
A user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger
editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded
or user defined. Valid values include:
A
Alphanumeric field, do not edit
N
Numeric field, right justify and zero fill
C
Alphanumeric field, right
justify and blank fill
|
| cTotalFlag | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
| szCompany | CO | char | OPT | INPUT |
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany
transactions.
Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000
for transaction entries.
|
| jdStartPeriodDate | DGL | JDEDATE | OPT | 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.
|
| jdGLDate | DGL | JDEDATE | OPT | 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.
|
| jdEndPeriodDate | DGL | JDEDATE | OPT | 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.
|
| mnActualCost | ACTCST | MATH_NUMERIC | OPT | OUTPUT |
Actual Cost represents the actual labor costs applied to a detail labor account based on the specified date range. The value is derived
from the detail labor account or can be a sum of labor accounts with a lower level of detail.
|
| mnActualHours | ACTHRS | MATH_NUMERIC | OPT | OUTPUT |
Actual Hours represents the actual labor hours applied to a detail labor account based on the specified date range. The value is derived
from the detail labor account or can be a sum of labor accounts with a lower level of detail.
|