Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnContractNumber | DOCO | MATH_NUMERIC | REQ | INPUT |
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on. |
szContractType | DCTO | char | REQ | INPUT |
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.)
The following document types are defined by J.D. Edwards and
should not be changed:
P
Accounts Payable documents
R
Accounts Receivable documents
T
Payroll documents
I
Inventory documents
O
Purchase Order Processing documents
J
General Accounting/Joint Interest Billing documents
S
Sales Order Processing documents
|
szContractCompany | KCOO | char | REQ | INPUT |
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on).
If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document.
If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document. |
szContractChangeNumber | COCH | char | REQ | INPUT |
The change number of the contract. The change order number of the base contract is always initialized to 000. Each time you enter a
change order for a contract, the system automatically increases the change order number by one.
For example, the base contract is the change
order number 000, the first change order is 001, the second is 002, and so on. |
jdChangeDate | CHD | JDEDATE | REQ | INPUT |
The date of last change for the change order. This date will control general ledger processing for the change order. |
szChangeOrderDescription | RMK | char | REQ | INPUT |
A generic field that you use for a remark, description, name, or address.
|
szBillingLineItem | OPIM | char | REQ | INPUT |
The pay item number as defined by the owner. This field is alphanumeric and can be up to 15 characters in length. It is recommended that
you use numeric information for this pay item number. |
szBillingLineDescription | DL01 | char | REQ | INPUT |
A user defined name or remark. |
cBillingLineType | PRTP | char | REQ | INPUT |
A code that specifies the billing terms that are defined by the billing line on the contract. The system uses the predefined codes for the
pricing type to access formulas and other information related to the calculation of billing and revenue amounts for the billing line. Valid alphabetic
codes are:
B
Burden
T
Time and Materials
U
Unit Price
L
Lump Sum
F
Fee Line
C
Component
M
Milestone
P
Progress
D
Direct Draw
R
Rated
Draw
Valid numeric codes are:
0
Burden
1
Time and Materials
2
Unit Price
3
Lump Sum
4
Fee Line
5
Component
6
Milestone
7
Progress
8
Direct
Draw
9
Rated Draw
|
mnScheduleOfValues | SCOF | MATH_NUMERIC | REQ | INPUT |
The expected or budgeted amount assigned to a specific line item of the contract. The system uses this amount in conjunction with the
percent of completion to calculate billing and retainage. |
szUnitOfMeasure | UM | char | OPT | INPUT |
A user defined code (00/UM) that identifies the unit of measurement for an amount or quantity. For example, it can represent a barrel, box,
cubic meter, liter, hour, and so on. |
mnQuantity | U | MATH_NUMERIC | OPT | INPUT |
The quantity of something that is identified by a unit of measure. For example, it can be the number of barrels, boxes, cubic yards, gallons,
hours, and so on. |
mnUnitPrice | UP | MATH_NUMERIC | OPT | INPUT |
The list or base price you charge for one primary or pricing unit of this item. |
szBusinessUnit | 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.
|
szSubsidiary | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
szObject | 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. |
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
|
szProgramId | PID | char | REQ | 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.
|
cNewOrExistingChgOrder | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
cProofOrFinalMode | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
szErrorCode | 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.
|
szCrossRefBusinessUnit | 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.
|
szCrossRefObject | 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. |
szCrossRefSubsidiary | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
szCrossRefSubledger | SBL | char | REQ | 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. |
cCrossRefSubledgerType | SBLT | char | REQ | 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
|