Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCountry | CTR | char | OPT | NONE |
A user defined code (00/CN) that identifies a country. The country code has no effect on currency conversion.
The Address Book system
uses the country code for data selection and address formatting. |
szCompany | CO | char | OPT | NONE |
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.
|
szCallingAppl | PID | char | OPT | NONE |
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.
|
szCallingVers | 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. |
szCallingForm | FID | char | OPT | NONE |
The Form ID refers to the report (R), form (V), or table number (F). |
szFormAction | FATN | char | OPT | NONE |
Form Action for Localization Exits UDC 00/FA
1 ADD Add
2 CHG Change
3 DEL Delete
4 XIT Hypercontrol Exit |
mnKey1_DocVoucherInvoiceE | DOC | MATH_NUMERIC | OPT | NONE |
A number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document
number or let the system assign it using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents
in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are:
Accounts Payable
o
Original document - voucher
o Matching document - payment
Accounts Receivable
o Original document - invoice
o Matching document -
receipt
Note: In the Accounts Receivable system, the following transactions simultaneously generate original and matching documents:
deductions, unapplied receipts, chargebacks, and drafts. |
szKey2_DocumentType | DCT | char | OPT | NONE |
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
|
szKey3_CompanyKey | KCO | char | OPT | NONE |
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher,
or journal entry.
If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the
document company to retrieve the correct next number for that company.
If two or more original documents have the same document number and
document type, you can use the document company to locate the desired document. |
szKey4_Company | CO | char | OPT | NONE |
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.
|
jdKey5_DateForGLandVoucher | DGJ | JDEDATE | OPT | NONE |
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. |
mnKey6_FiscalYear | FY | MATH_NUMERIC | OPT | NONE |
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. |
cKey7_PayStatusCode | PST | char | OPT | NONE |
A user defined code (00/PS) that indicates the current payment status for a voucher or an invoice. Examples of codes include:
A
Approved
for payment but not yet paid
H
Held pending approval
P
Paid
Note: Some of the payment status codes are hard coded; the system assigns
the code.
|
szKey8_CostCenter | MCU | char | OPT | 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.
|
mnKey9_AddressNumber | AN8 | MATH_NUMERIC | OPT | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
mnCentury | CTRY | MATH_NUMERIC | OPT | NONE |
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.
|
szDocumentPayItem | SFX | char | OPT | NONE |
A number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has
multiple pay items, the numbers are sequential. |
mnNumberOfSplitPayments | NSP | MATH_NUMERIC | OPT | NONE |
The number of equal, consecutive payments into which you want the system to divide the voucher or invoice. For example, if the number of
split payments is 3, the system divides the invoice or voucher into three equal payments.
You can use split payments only if the number of
days between payments is a constant number, such as 30.
Note: For amounts that are not equally divisible, the system uses soft rounding.
|
mnJobnumberA | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
szComputerID | CTID | char | OPT | NONE |
|
mnAmountGross | AG | MATH_NUMERIC | OPT | NONE |
A value that specifies the total amount of the invoice or voucher pay item. The gross amount might include the tax amount, depending on
the tax explanation code. The system does not decrease the gross amount when payments are applied. When you void a transaction, the
system clears the gross amount field.
|
mnAmountTaxable | ATXA | MATH_NUMERIC | OPT | NONE |
The amount on which taxes are assessed. |
mnAmtTax2 | STAM | MATH_NUMERIC | OPT | NONE |
The amount assessed and payable to tax authorities. It is the total of the VAT, use, and sales taxes (PST). |
mnAmountOpen | AAP | MATH_NUMERIC | OPT | NONE |
The amount of an invoice or voucher pay item that is unpaid. |
szGUIVATNumber | URRF | char | OPT | BOTH |
A 15-position reference that is reserved for the user. J.D. Edwards does not currently use this field and does not plan to use it in the future.
|
szSOCompanyKeyOrderNo | KCOO | char | OPT | BOTH |
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. |
mnSODocumentOrderInvoiceE | DOCO | MATH_NUMERIC | OPT | BOTH |
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. |
szSOOrderType | DCTO | char | OPT | BOTH |
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
|
mnSOLineNumber | LNID | MATH_NUMERIC | OPT | BOTH |
A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns
this number,but in some cases you can override it. |