Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCS_Country | 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. |
szCS_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.
|
szCS_ProgramId | 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.
|
szCS_Version | 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. |
szCS_FormId | FID | char | NONE | NONE |
The Form ID refers to the report (R), form (V), or table number (F). |
szCS_FormAction | 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 |
mnNotaFiscalNumber | BNNF | MATH_NUMERIC | NONE | NONE |
A six-character number that identifies a nota fiscal. The number consists of the nota fiscal number and the nota fiscal series.
|
szNotaFiscalSeries | BSER | char | NONE | NONE |
A two-character number that along with the nota fiscal number, identifies a nota fiscal. The Nota Fiscal Series field is the second key that the
system uses to access a specific nota fiscal. |
mnNextNumber001 | N001 | MATH_NUMERIC | NONE | NONE |
The number that the system will assign next. The system can use next numbers for voucher numbers, invoice numbers, journal entry
numbers, employee numbers, address numbers, contract numbers, and sequential W-2s. You must use the next number types already
established unless you provide custom programming. |
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
|
cMatchType | MATC | char | NONE | 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).
|
mnOrderNumber | 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. |
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
|
szDocumentCompany | 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. |
szCostCenter | MCU | char | NONE | 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.
|
mnLineNumber | 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. |
mnNoOfLinesOnOrder | NLIN | MATH_NUMERIC | NONE | 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. |
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. |
szPO_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
|
szPO_LineType | LNTY | char | NONE | NONE |
A code that controls how the system processes lines on a transaction. It controls the systems with which the transaction interfaces, such as
General Ledger, Job Cost, Accounts Payable, Accounts Receivable, and Inventory Management. It also specifies the conditions under
which a line prints on reports, and it is included in calculations. Codes include the following:
S
Stock item
J
Job cost
N
Nonstock item
F
Freight
T
Text information
M
Miscellaneous charges and credits
W
Work order |
szPO_StatusCodeLast | LTTR | char | NONE | NONE |
A code (system 40/type AT) specifying the last step in the processing cycle that this order line has successfully completed. |
szPO_OverrideStatus | LTTR | char | NONE | NONE |
A code (system 40/type AT) specifying the last step in the processing cycle that this order line has successfully completed. |
cPO_SelectReceiptDate | MODE | char | NONE | NONE |
The processing mode used in Purchase Order Consolidator to signify when specific orders are being processed. |
cPO_OneNFbyReceipt | MODE | char | NONE | NONE |
The processing mode used in Purchase Order Consolidator to signify when specific orders are being processed. |
jdIssueDate | ISSU | JDEDATE | OPT | NONE |
The date that the log entry was issued. For example, the effective date for an insurance policy is entered in the Issue Date field. |
szOrderSuffix | SFXO | char | OPT | 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. |