Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
cLastInCostFlag | EV01 | char | NONE | NONE |
An option that specifies the type of processing for an event.
|
cAverageCostFlag | EV02 | char | NONE | NONE |
An option that specifies the type of processing for an event.
|
cPurchasingCostFlag | EV03 | char | NONE | NONE |
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX,
and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
|
cLotCostFlag | EV04 | char | NONE | NONE |
PeopleSoft event point processing flag 04.
|
mnItemNumberShort | ITM | MATH_NUMERIC | NONE | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
szSecondItemNumber | LITM | char | NONE | NONE |
A number that identifies the item. The system provides three separate item numbers plus an extensive cross-reference capability to
alternative item numbers. The three types of item numbers are:
Item Number (short)
An 8-digit, computer-assigned item number.
2nd Item Number
A
25-digit, user defined, alphanumeric item number.
3rd Item Number
Another 25-digit, user defined, alphanumeric item number.
In addition to
these three basic item numbers, the system provides an extensive cross-reference search capability. You can define numerous
cross-references to alternative part numbers. For example, you can define substitute item numbers, replacements, bar codes, customer numbers, or
supplier numbers.
|
szThirdItemNumber | AITM | char | NONE | NONE |
The system provides three separate item numbers plus an extensive cross-reference capability to alternate item numbers. These item
numbers are as follows:
1. Item Number (short) - An 8-digit, computer-assigned item number.
2. 2nd Item Number - The 25-digit, free-form, user
defined alphanumeric item number.
3. 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number.
In addition to
these three basic item numbers, an extensive cross-reference search capability has been provided (see XRT). Numerous cross references to
alternate part numbers can be user defined, such as substitute item numbers, replacements, bar codes, customer numbers, or supplier
numbers. |
szInventoryLocation | LOCN | char | NONE | NONE |
The storage location from which goods will be moved. |
szInventoryLot | LOTN | char | NONE | NONE |
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics. |
cCostLevel | CLEV | char | NONE | NONE |
A code that indicates whether the system maintains one overall inventory cost for the item, a different cost for each branch/plant, or a
different cost for each location and lot within a branch/plant. The system maintains inventory costs in the Inventory Cost table (F4105).
Valid codes
are:
1 Item level
2 Item/Branch level
3 Item/Branch/Location level |
cSalesPriceLevel | PLEV | char | NONE | NONE |
A code that indicates whether the system maintains standard sales prices for an item, different sales prices for each branch/plant, or
different sales prices for each location and lot within a branch/plant. The system maintains sales prices in the Base Price file (F4106). Valid codes
are:
1 Item level
2 Item/Branch level
3 Item/Branch/Location level |
mnTransactionQuantity | TRQT | MATH_NUMERIC | NONE | NONE |
A value that represents the available quantity, which might consist of the on-hand balance minus commitments, reservations, and
backorders. You enter this value in the Branch/Plant Constants program (P41001).
|
cMarginMaintenanceYN | MGMN | char | NONE | NONE |
The Margin Maintenance Y/N code is a system set work field used by Average Cost Update to determine whether or not to recalculate the
unit price based on Margin Maintenance (%). |
szCurrencyCode | CRCD | char | NONE | NONE |
A code that identifies the currency of a transaction.
|
szUnitOfMeasurePrimary | UOM1 | char | NONE | NONE |
A user defined code (00/UM) that identifies the unit of measure that the system uses to express the quantity of an item, for example, EA
(each) or KG (kilogram). |
jdEffectiveDate | EFTJ | JDEDATE | NONE | NONE |
The date when a transaction, contract, obligation, preference, or policy rule becomes effective.
|
mnNumberOfLines | 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. |
mnTransactionLineNumber | 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. |
mnLotPotency | LOTP | MATH_NUMERIC | NONE | NONE |
A code that indicates the potency of the lot expressed as a percentage of active or useful material (for example, the percentage of alcohol
in a solution). The actual potency of a lot is defined in the Lot Master table (F4108). |
szLotGrade | LOTG | char | NONE | NONE |
A code that indicates the grade of a lot. The grade is used to indicate the quality of the lot. Examples include the following:
A1 Premium
grade
A2 Secondary grade
The grade for a lot is stored in the Lot Master table (F4108). |
szCostCenter | OMCU | char | NONE | NONE |
The business unit from an account number. The account number business unit is usually found in the data item MCU, however, Distribution
systems use the field MCU as the branch. |
szCompanyNumber | 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.
|
mnDocumentNumber | 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. |
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
|
szDocumentPayItem | 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. |
mnJournalEntryNumber | JELN | MATH_NUMERIC | NONE | 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. |
mnBatchNumber | ICU | MATH_NUMERIC | NONE | 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. |
jdGLDate | DGL | JDEDATE | NONE | 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.
|
szGlCategory | GLC | char | NONE | NONE |
A code that determines the trade account that the system uses as the offset when you post invoices or vouchers. The system concatenates
the value that you enter to the AAI item RC (for Accounts Receivable) or PC (for Accounts Payable) to locate the trade account. For
example, if you enter TRAD, the system searches for the AAI item RCTRAD (for receivables) or PCTRAD (for payables).
You can assign up to four
alphanumeric characters to represent the G/L offset or you can assign the three-character currency code (if you enter transactions in a
multicurrency environment). You must, however, set up the corresponding AAI item for the system to use; otherwise, the system ignores the G/L
offset and uses the account that is set up for PC or RC for the company specified.
If you set up a default value in the G/L Offset field of the
customer or supplier record, the system uses the value during transaction entry unless you override it.
Note: Do not use code 9999. It is reserved for
the post program and indicates that offsets should not be created.
|
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
|
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. |
szCompanyOrderNumber | 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. |
jdTransactionDate | TRDJ | JDEDATE | NONE | NONE |
The date that an order was entered into the system. This date determines which effective level the system uses for inventory pricing. |
szTransactionUnitOfMeasure | UOM | char | NONE | NONE |
A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).
|
mnAddressNumber | 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.
|
szTransactionExplanation | TREX | char | NONE | NONE |
Text that identifies the reason that a transaction occurred. |
mnTimeOfDay | TDAY | MATH_NUMERIC | NONE | NONE |
The computer clock in hours:minutes:seconds. |
szUserId | USER | char | NONE | NONE |
The code that identifies a user profile.
|
szProgramId | 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.
|
jdDateUpdated | UPMJ | JDEDATE | NONE | NONE |
The date that specifies the last update to the file record. |
cWriteCardexFlag | EV05 | char | NONE | NONE |
A flag that indicates whether automatic spell check is turned on. |
mnMarginMaintenanceAmount | MMPC | MATH_NUMERIC | NONE | NONE |
This field is used as a method to automatically maintain a desired margin. If a value is entered in this field, every purchase order receipt will
add the margin percentage to the item's cost, if the costing method is 1, 2, or 6, in order to generate a new list price.
For example: Item cost =
56.00, and Margin Maintenance % = 20, then the new list price will be as follows:
56 * ( 1 + .20 ) = 67.20 |
mnOrderLineNumber | 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. |
mnFreightUnitAmount | PRRC | MATH_NUMERIC | OPT | NONE |
The unit cost of one item, as purchased from the supplier, excluding freight,taxes, discounts, and other factors that might modify the actual
unit cost you record when you receive the item. |
mnFreightExtendedAmount | AEXP | MATH_NUMERIC | OPT | NONE |
The number of units multiplied by the unit price. |
szBranchPlant | 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.
|