Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szCacheActionCode | CATN | char | OPT | NONE |
This is a grouping of suppliers and items for pricing purposes. |
mnJobNumber | JOBS | MATH_NUMERIC | OPT | NONE |
The job number (work station ID) which executed the particular job. |
szErrorId | DTAI | char | OPT | NONE |
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
|
mnAaiTableNumber | ANUM | MATH_NUMERIC | OPT | NONE |
A number used to specify sequence and retrieve accounting information.
|
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
|
szDocumentType | DCT | char | OPT | 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
|
szCostType | COST | char | OPT | NONE |
A code that designates each element of cost for an item. Examples of the cost object types are:
o A1 Purchased raw material
o B1
Direct labor routing rollup
o B2 Setup labor routing rollup
o C1 Variable burden routing rollup
o C2 Fixed burden routing rollup
o Dx Outside
operation routing rollup
o Xx Extra add-ons, such as electricity and water
The optional add-on computations usually operate with the type
Xx extra add-ons. This cost structure allows you to use an unlimited number of cost components to calculate alternative cost rollups. The
system then associates these cost components with one of six user defined summary cost buckets.
|
szCompany | CO | char | OPT | 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.
|
szGlCategory | GLPT | char | OPT | 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. |
szCostCenter | 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.
|
szObjectAccount | OBJ | char | OPT | NONE |
The portion of a general ledger account that refers to the division of the Cost Code (for example, labor, materials, and equipment) into
subcategories. For example, you can divide the Cost Code for labor into regular time, premium time, and burden.
Note: If you use a flexible chart of
accounts and the object account is set to 6 digits, J.D. Edwards recommends that you use all 6 digits. For example, entering 000456 is not
the same as entering 456 because if you enter 456 the system enters three blank spaces to fill a 6-digit object. |
szSubsidiary | SUB | char | OPT | NONE |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
idCacheCursor | GENLNG | ID | OPT | NONE |
General purpose ID variable. |
mnTransactionID | TCID | MATH_NUMERIC | OPT | NONE |
|
szComputerID | CTID | char | OPT | NONE |
|