Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCommunity_HBMCUS | HBMCUS | char | REQ | INPUT |
A value that specifies a community, project, or subdivision. A community is a distinct grouping of lots which can be grouped together
through user-defined specifications, for example, product offering, geography, and so on. A subset of the builder's plans and options are typically
included within a community.
|
szLotNumber_HBLOT | HBLOT | char | REQ | INPUT |
The specific lot upon which the home will be constructed.
|
cErrorFlag_EV01 | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
szDocumentType_DCT | DCT | char | REQ | INPUT |
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are:
P
Accounts payable
documents
R
Accounts receivable documents
T
Time and Pay documents
I
Inventory documents
O
Purchase order documents
S
Sales order
documents
|
mnDocumentNumber_DOCO | 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. |
jdCloseDate_DGJ | DGJ | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction will be posted. You define financial periods for a date pattern code that you
assign to the company record. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the
company to retrieve the appropriate fiscal period number, as well as to perform date validations. |
szExplanation_EXA | EXA | char | OPT | INPUT |
A description, remark, explanation, name, or address. |
szCompany_CO | 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.
|
szProgramId_PID | 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.
|
cUserResponse_EV01 | EV01 | char | OPT | OUTPUT |
An option that specifies the type of processing for an event.
|
mnBatchNumber_NUMR | NUMR | MATH_NUMERIC | OPT | OUTPUT |
The equipment number or work order number associated with a change of status. |
szJEVersion | VERS | char | OPT | NONE |
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined
processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a
menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version. |