Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCountry | CTR | char | NONE | 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 | NONE | 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 | NONE | 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 | NONE | 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 | NONE | NONE |
The Form ID refers to the report (R), form (V), or table number (F). |
szFormAction | FATN | char | NONE | NONE |
Form Action for Localization Exits UDC 00/FA
1 ADD Add
2 CHG Change
3 DEL Delete
4 XIT Hypercontrol Exit |
szKey1_CompanyKey | KCO | char | NONE | 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. |
szKey2_DocumentType | DCT | char | NONE | 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
|
mnKey3_DocVoucherInvoiceE | DOC | MATH_NUMERIC | NONE | 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. |
szKey4_DocumentPayItem | SFX | char | NONE | 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. |
mnKey5_PayItemExtensionNumber | SFXE | MATH_NUMERIC | NONE | NONE |
A code to designate an adjusting entry to a pay item on a voucher or invoice. This field is required so that each record is unique. |
jdKey6_DateInvoiceJ | DIVJ | JDEDATE | NONE | NONE |
The date that either you or the system assigns to an invoice or voucher. This can be either the date of the supplier's invoice to you or the
date of your invoice to the customer. |
szKey7_Company | CO | char | NONE | 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.
|
mnKey8_AmountGross | AG | MATH_NUMERIC | NONE | 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.
|
mnKey9_AmountTax | STAM | MATH_NUMERIC | NONE | NONE |
The amount assessed and payable to tax authorities. It is the total of the VAT, use, and sales taxes (PST). |
cKey10_CurrencyMode | CRRM | char | NONE | NONE |
An option that specifies whether the system displays amounts in the domestic or foreign currency.
On
The system displays amounts in the
foreign currency of the transaction.
Off
The system displays amounts in the domestic currency of the transaction.
|
szKey11_CurrencyCodeFrom | CRCD | char | NONE | NONE |
A code that identifies the currency of a transaction.
|
mnKey12_CurrencyConverRate | CRR | MATH_NUMERIC | NONE | NONE |
A number (exchange rate) that a foreign currency amount is multiplied by to calculate a domestic currency amount.
The number in this field
can have a maximum of seven decimal positions. If more are entered, the system adjusts to the nearest seven decimal positions.
|
mnKey13_AddressNumber | AN8 | MATH_NUMERIC | NONE | NONE |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
szKey14_VendorInvoiceNumber | VINV | char | NONE | NONE |
The supplier's invoice number that is used for voucher entry. Voucher entry allows only one invoice per voucher number. If multiple invoice
numbers exist on a voucher, you must set them up as multiple vouchers or combine the invoices and enter them as one voucher. Depending
on how you have your accounts payable constants set, the system can do one of the following:
o Accept a duplicate invoice number
without warning or error
o Generate a warning message in which the duplicate invoice number can still be accepted
o Generate an error
message
Blank values are treated in the same manner as any other invoice number. Two blank invoice numbers are treated as duplicates.
To test
for duplicate invoice numbers that might have been entered in error, run the Suspected Duplicate Payments report (R04601).
Note: The
duplicate invoice number validation is not run for vouchers with document type NO. These vouchers are created by the Generate Reimbursements
program (R03B610).
|
jdKey15_DateForGLandVoucher | DGJ | JDEDATE | NONE | 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. |
mnKey16_DocumentOrderInvoiceE | DOCO | MATH_NUMERIC | NONE | NONE |
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. |
szKey17_OrderType | DCTO | char | NONE | NONE |
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
|
szKey18_CompanyKeyOrderNo | KCOO | char | NONE | NONE |
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. |
szKey19_OrderSuffix | SFXO | char | NONE | NONE |
In the A/R and A/P systems, a code that corresponds to the pay item. In the Sales Order and Procurement systems, this code identifies
multiple transactions for an original order.
For purchase orders, the code is always 000.
For sales orders with multiple partial receipts against an
order, the first receiver used to record receipt has a suffix of 000, the next has a suffix of 001, the next 002, and so on. |
mnKey20_LineNumber | LNID | MATH_NUMERIC | NONE | NONE |
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. |
szKey21_TaxArea1 | TXA1 | char | OPT | NONE |
A code that identifies a tax or geographic area that has common tax rates and tax authorities. The system validates the code you enter
against the Tax Areas table (F4008). The system uses the tax rate area in conjunction with the tax explanation code and tax rules to calculate tax
and G/L distribution amounts when you create an invoice or voucher. |
cKey22_MatchType | MATC | char | OPT | NONE |
A code, attached to each purchase-order detail record or receipt record, that indicates whether a voucher exists and whether the voucher
or receipt record has been reversed. Valid values are:
1
No voucher exists.
2
A voucher exists.
3
The voucher has been reversed.
4
The receipt
record has been reversed.
Note: Record types 3 and 4 are audit records only; you cannot access these record types for the Voucher Match
program (P4314) or the PO Receipts program (P4312).
|
mnKey23_NoOfLinesOnOrder | NLIN | MATH_NUMERIC | OPT | NONE |
A number representing the number of lines on either a purchase or sales order.
or The number of receivers recorded during the receipts
process. This field will be used in Voucher Matching. |
cKey24_LocalizationError | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
cPayStatusCodeDefault | 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.
|
cPayStatusCode | 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.
|
cPayStatusCode_Orig | 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.
|
mnJobnumberA | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
szComputerID | CTID | char | OPT | NONE |
|
nNumberOfWarning | INT01 | integer | OPT | NONE |
Number of Days in Future to Query for Responses Due.
|