Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
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. |
mnShortItemNumber | 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. |
szBranchPlant | 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.
|
szLocation | LOCN | char | NONE | NONE |
The storage location from which goods will be moved. |
szLot | LOTN | char | NONE | NONE |
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics. |
szParentLot | PLOT | char | NONE | NONE |
An inventory separation device that allows tracking of the inventory by date received or similar convention to control lots or layers. |
mnStorageUnit | STUN | MATH_NUMERIC | NONE | NONE |
A number that uniquely identifies goods in specific location detail information. Location detail contains a storage unit number if you turn on
license plate tracking in the Item/UOM Profile (P46011) for the item's level 1 unit of measure.
The system assigns a storage unit number to a
storage unit when it creates a request or suggestion |
mnSequenceNumberLocation | LDSQ | MATH_NUMERIC | NONE | NONE |
The sequence number that identifies a record in the Location Detail table (F4602). The system uses this number to distinguish between the
diffferent pallets, cases, and so forth, for the same item in the same location. |
mnTransactionLineNumber | TRNO | MATH_NUMERIC | NONE | NONE |
The transaction line number keeps the different From and To lines for one transaction (for example, combining multiple lots into one or
splitting one lot into several new ones) together by giving them the same transaction line number. |
cFromTo | FRTO | char | NONE | NONE |
A code that indicates whether a line in a transaction is a From line or a To line. This field allows you to combine multiple existing products or
locations into a single product or location. For example, you can create three From lines and one To line. You can also split one existing
product or location into several new products or locations. For example, you can create one From line and two To lines. The information that is
contained in a From transaction line is always existing item location information. |
cMasterCardex | LMCX | char | NONE | NONE |
For Future Use. |
cLotStatus | LOTS | char | NONE | NONE |
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes
indicate that the lot is on hold.
You can assign a different status code to each location in which a lot resides on Item/Location Information or
Location Lot Status Change. |
mnPotency | 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). |
szGrade | 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). |
mnParentItemNumber | KIT | MATH_NUMERIC | NONE | NONE |
The system provides for three separate item numbers.
1. Item Number (short) - An eight-digit, computer assigned, completely
non-significant 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. |
szCostCenter | MMCU | char | NONE | NONE |
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:
o Branch/Plant (MMCU)
o Dept A (MCU)
o Dept B (MCU)
o Job 123
(MCU)
Business unit security is based on the higher-level business unit. |
szContractNumber | DMCT | char | NONE | NONE |
A unique number your company assigns to identify a particular agreement. You might want to assign some significance to the agreement
number (for example,an agreement type code, location, year, and so forth). An agreement might have multiple supplements to record
addendum or changes, for example. |
mnContractSupplement | DMCS | MATH_NUMERIC | NONE | NONE |
The supplement number records any changes or addendum to agreements that occur over time or by item. It can also indicate individual
agreements that are tied to a master agreement. The system allows up to 999 different supplements per base agreement number. |
cContractBalancesUpdated | BALU | char | NONE | NONE |
This field will be used to control whether a record in the inventory, sales order or purchasing detail files has been updated to the distribution
contract balances file. Valid values are:
blank or N - Not been updated
Y or 1 - Updated |
szCompanyNumber | 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. |
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
|
szPayItem | 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 | GLPT | char | NONE | NONE |
A user defined code (41/9) that identifies the G/L offset that system uses when it searches for the account to which it posts the transaction. If
you do not want to specify a class code, you can enter **** (four asterisks) in this field.
You can use automatic accounting instructions (AAIs) to
predefine classes of automatic offset accounts for the Inventory Management, Procurement, and Sales Order Management systems. You
might assign G/L class codes as follows:
IN20 Direct Ship Orders
IN60 Transfer Orders
IN80 Stock Sales
The system can generate
accounting entries based upon a single transaction. For example, a single sale of a stock item can trigger the generation of accounting entries
similar to the following:
Sales-Stock (Debit) xxxxx.xx
A/R Stock Sales (Credit) xxxxx.xx
Posting Category: IN80
Stock Inventory
(Debit) xxxxx.xx
Stock COGS (Credit) xxxxx.xx
The system uses the class code and the document type to find the AAI. |
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 | 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. |
szCompanyOrderNumber | 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. |
mnUnqueLineNumber | 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. |
cAsOfPostedCode | IPCD | char | NONE | NONE |
This code designates the status of the posting of each particular transaction in the Inventory Ledger file. Valid codes are:
Y Posted (This
transaction has been recorded in the 'As Of' generation file (F41112)).
S The value of your inventory has yet to be impacted by the
tranasaction.
X The transaction was a movement of inventory only that had no effect on its value.
Blank The transaction has not been posted to the
'As Of' file. |
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 | TRUM | char | NONE | NONE |
The unit of measure you used when you entered this transaction into the system. |
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. |
szTransactionReference | TREF | char | NONE | NONE |
A reference number that provides an audit trail for specific transactions. |
szReasonCode | RCD | char | NONE | NONE |
A user defined code (42/RC) that explains the purpose for a transaction. For example, you can indicate the reason that you are returning
items. |
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).
|
mnUnitCost | UNCS | MATH_NUMERIC | NONE | NONE |
The amount per unit, derived by dividing the total cost by the unit quantity. |
mnExtendedCost | PAID | MATH_NUMERIC | NONE | NONE |
The extended cost or price value of an inventory transaction for an inventory item.
|
szTerminalIdentification | TERM | char | NONE | NONE |
The workstation ID number. |
mnUniqueID | UKID | MATH_NUMERIC | NONE | NONE |
This field is a unique number used to identify a record in a file. |
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.
|
jdDateCreated | CRDJ | JDEDATE | NONE | NONE |
This is the date that the ledger file was updated. This field is updated at the same time as the Program ID, Terminal ID, and time in the Item
Ledger file (F4111). |
idHRequestF4111 | GENLNG | ID | NONE | NONE |
General purpose ID variable. |
szCountry | CTR | char | OPT | 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. |
szProgramId_2 | PID | char | OPT | 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.
|
szVersion | 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. |
szFormId | FID | char | OPT | NONE |
The Form ID refers to the report (R), form (V), or table number (F). |
szFormAction | FATN | char | OPT | NONE |
Form Action for Localization Exits UDC 00/FA
1 ADD Add
2 CHG Change
3 DEL Delete
4 XIT Hypercontrol Exit |