Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCompanyKey | 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. |
szDocumentType | 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
|
mnDocVoucherInvoiceE | 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. |
szDocTypeMatching | DCTM | char | NONE | NONE |
Within Auto Bank Statement process, a document type is needed for the following:
1) Document Type is needed for creating Variance
Journal Entries for payments, receipts, and journal entries when running the Auto Bank Statement Process (R09616). If Document Type on the
Payment Clear tab is left blank, it will default to PN. If Document Type on the Receipt Clear tab is left blank, it will default to RC. If Document
Type on the Journal Entry Reconcile tab is left blank, it will default to JE.
2) Document Type is needed for creating Journal Entries on the
Journal Entry Create tab, and the Draft Paid tab. For both of these, it will default to JE if left blank.
|
mnDocMatchingCheckOr | DOCM | MATH_NUMERIC | NONE | NONE |
The number of the matching document, such as a receipt, payment, adjustment,or credit. You apply a matching document (DOCM) against
an original document (DOC), such as an invoice or voucher. |
szVendorInvoiceNumber | 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).
|
jdDateServiceCurrency | DSVJ | JDEDATE | NONE | NONE |
A date that indicates when you purchased goods or services, or when you incurred a tax liability.
|
szReportCodeAddBook018 | AC18 | char | NONE | NONE |
One of thirty reporting codes that you can assign to an address in the Address Book system. Use these codes to identify addresses for
reports, mailings, and so on. Category codes are user-defined (system 01, types 01 through 30).
Examples:
Category code 01 Location
or Branch
Category code 02 Salesperson
Category code 03 New tenant
Category code 04 Credit officer |
szCompanyKeyOrderNo | 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. |
szOrderType | 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
|
mnDocumentOrderInvoiceE | 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. |
cRG100 | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
cInvoiceType | INTY | char | REQ | INPUT |
An alphanumeric UDC that identifies different versions of the same invoice format. For example, you might use the codes 'D' and 'F' to
differentiate draft formats from final invoice formats. |