Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnF43121Jobnumber | JOBS | MATH_NUMERIC | REQ | INPUT |
The job number (work station ID) which executed the particular job. |
szComputerID | CTID | char | REQ | INPUT |
|
cActionCode1 | ACTION | char | OPT | NONE |
A code that indicates the activity you want to perform. Valid codes are:
A Add new record
C Change existing record
D Delete existing
record
I Inquire on existing record
. End of program or function
space Clear the form
If you enter a code that is not active, the system
highlights the code and no action occurs.
NOTE: Depending on how your company has set up action code security, you might not be authorized
to use all action codes. |
cProcessEdits | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
szProgramId | 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.
|
szUserId | USER | char | REQ | INPUT |
The code that identifies a user profile.
|
szVersion | VERS | char | REQ | INPUT |
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. |
mnLandedCostJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
mnOrderNumber | DOCO | MATH_NUMERIC | OPT | 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 | OPT | 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
|
szCompanyKeyOrderNo | KCOO | char | OPT | 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. |
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. |
jdGLDate | DGL | JDEDATE | OPT | NONE |
A date that identifies the financial period to which the transaction is to be posted.
The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
|
mnBatchNumber | ICU | MATH_NUMERIC | OPT | NONE |
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either
assign a batch number or let the system assign it using the Next Numbers program. |
szBatchType | ICUT | char | OPT | NONE |
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction.
Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded. |
mnLCReceiptDoc | 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. |
mnLCJournalEntryLineNo | JELN | MATH_NUMERIC | OPT | NONE |
A number that designates a line within a journal entry. The system uses this field to sequence the journal entry lines for inquiry purposes. |
cCurrencyMode | CRRM | char | OPT | 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.
|
szCurrencyCode | CRCD | char | OPT | NONE |
A code that identifies the currency of a transaction.
|
mnLCF0911JobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
cReversalOption | OPT | char | OPT | NONE |
Selection option. Place the cursor on the option field and press F1 for a list of valid selection options. |
szP43250Version | 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. |
mnLineNumber | LNID | MATH_NUMERIC | OPT | 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. |
cModeProcessing | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|