Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
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. |
mnDocumentOrderInvoiceE | 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
|
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. |
szRoutingApproval | ARTG | char | OPT | NONE |
A code that determines to whom an order is routed for approval. |
szHoldValue | HCOD | char | OPT | NONE |
A user defined code (42/HC) that identifies why an order was placed on hold (for example, credit, budget, or margin standards were
exceeded). |
cBudgetAppNeeded | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
szStatusApproval_ASTS | ASTS | char | OPT | NONE |
Text indicating where this order stands in the approval process. Following are valid status messages:
Approved - The approver has
approved the order. When an approver approves an order, the system sends an electronic mail message to the next approver stating that his
approval is required next. If there are no more required approvers, the system sends a final approved electronic mail message to the person
who entered the order.
Rejected - The approver has rejected the order. When an approver rejects an order, the system sends an electronic
mail rejection message to the person who entered the order indicating the order was rejected and changes are necessary before the order can
be approved. After the person who entered the order makes changes, the approval processing begins again with the first
approver.
Pending - The approver has not yet taken action on the order.
Bypassed - The approver was skipped in the approval process because someone
of greater authority has approved or rejected the order.
First position meaning:
1 Budget Approver
2 Dollar Level Approver
3 Originator
of the Request
Second position meaning:
R Rejected - Valid with first postions 1, 2, or 3 .
A Approved - Valid with first postions 1, 2, or 3 .
N
Pending Message - Message is waiting in the Approval Process.
B Approval Level Skipped - A level of Approval was skipped.
O Time
Stamp - The information is a record of when the originator entered the information. |