Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
szDataAliasInvSummAccss_R01PSA | R01PSA | char | REQ | INPUT |
Use this parameter to retrieve information from the Invoice Summary Access table (F48520). Each piece of information is associated with a
unique field name. A one to eight character "Data Alias" identifies the field name. Enter the Data Alias (in upper case characters) which is
associated with the information you want to retrieve from the table. Select Data Aliases from the group associated with the Smart Field you are
using. (Only use Alpha fields if using an Alpha Smart Field, Character fields if using a Character Smart Field,etc.) The following Data Aliases
are available in this table:
Numeric Fields ITOL (Invoice Amount)
ITXA (Invoice Taxable Amount)
ITAM (Invoice Tax Amount)
IDSC
(Invoice Discount Available Amount)
CITL (Foreign Invoice Amount)
CITA (Foreign Invoice Taxable Amount)
CITX (Foreign Invoice Tax
Amount)
CIDS (Foreign Invoice Discount Available Amount)
U (Units)
AA (Amount) |
cContractSummaryBasis_R12P | R12P | char | OPT | INPUT |
A code that specifies the printing of the total amount billed to date. The system stores these amounts in the Invoice Summary Access file
(F48520) by Contract, Change Order, Owner Pay Item, Job (Cost Center), Cost Code (Subsidiary) and Cost Type (Object). However, you can
print amounts at a more summarized level if you wish. You can use this code to indicate which contract values, if any, should be a part of the
summarization. Valid values are:
Blank Do not summarize by contract information
1 Summarize by Contract Number
2 Summarize by
Change Order
3 Summarize by Owner Pay Item |
cAccountSummaryBasis_R13P | R13P | char | OPT | INPUT |
A code that specifies the printing of the total amount billed to date. The system stores these amounts in the Invoice Summary Access file
(F48520) by Employee, G/L Date, Contract, Change Order, Owner Pay Item, Job (Business Unit), Cost Code (Subsidiary), Cost
Type (Object) and Component Code. However, you can print amounts at a more summarized level if you wish.
You can use this code to
indicate which account values, if any, should be a part of the summarization. Valid values are:
Blank Do not summarize by the account number
1
Summarize by Business Unit
2 Summarize by Business Unit and Object
3 Summarize by Business Unit and Subsidiary
4
Summarize by Business Unit, Object and Subsidiary |
cEmployeeSummaryBasis_R14P | R14P | char | OPT | INPUT |
A code that specifies the printing of the total amount billed to date. These amounts are stored in the Invoice Summary Access file (F48520)
by Contract,Change Order, Owner Pay Item, Job (Cost Center), Cost Code (Subsidiary), and Cost Type (Object). However, you can print
amounts at a more summarized level if you wish. You can use this code to indicate whether the Employee/Supplier Number should be a part of
the summarization. Valid values are:
Blank Do not summarize by Employee/Supplier
1 Summarize by Employee/Supplier |
szComponentCodeToRetrieve_R16P | R16P | char | OPT | INPUT |
A code that specifies whether to print amounts which are associated with specific Component Codes. Values valid are:
Blank Print
amounts associated with base billing transactions only.
Component Code Print amounts associated with the specified component code only.
*ALL Print the amounts associated with both the base billing transaction and it's components.
*CMP Print the amounts for ALL components,
excluding the base billing transaction. |
mnAccumRegisterNumb_R25P | R25P | MATH_NUMERIC | OPT | INPUT |
A value used to identify a register for storing retrieval code information.
You can set up to 99 user defined registers. You can define
additional retrieval references to print, or calculate and print, the contents of the register. For example, you could use this field to calculate grand
totals.
Valid values are:
1-99 |
mnDocumentOrderInvoiceE_DOCO | DOCO | MATH_NUMERIC | REQ | INPUT |
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 | DCTO | char | REQ | INPUT |
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 | KCOO | char | REQ | INPUT |
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. |
szContractChangeNum_COCH | COCH | char | REQ | INPUT |
The change number of the contract. The change order number of the base contract is always initialized to 000. Each time you enter a
change order for a contract, the system automatically increases the change order number by one.
For example, the base contract is the change
order number 000, the first change order is 001, the second is 002, and so on. |
mnLineNumber_LNID | LNID | MATH_NUMERIC | REQ | INPUT |
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. |
szCostCenter_MCU | MCU | char | REQ | INPUT |
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 | OBJ | char | REQ | INPUT |
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 | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
mnAddressNumber_AN8 | AN8 | MATH_NUMERIC | REQ | INPUT |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
szComponentCode_CCOD | CCOD | char | REQ | INPUT |
A component code identifies a provisional burden that is accounted for at the billing detail transaction level. |
mnPrevDocumentOrderInve_DOCO | DOCO | MATH_NUMERIC | REQ | INPUT |
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. |
szPrevOrderType_DCTO | DCTO | char | REQ | INPUT |
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
|
szPrevCompanyKeyOrderNo_KCOO | KCOO | char | REQ | INPUT |
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. |
szPrevContractChangeNum_COCH | COCH | char | REQ | INPUT |
The change number of the contract. The change order number of the base contract is always initialized to 000. Each time you enter a
change order for a contract, the system automatically increases the change order number by one.
For example, the base contract is the change
order number 000, the first change order is 001, the second is 002, and so on. |
mnPrevLineNumber_LNID | LNID | MATH_NUMERIC | REQ | INPUT |
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. |
szPrevCostCenter_MCU | MCU | char | REQ | INPUT |
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.
|
szPrevObjectAccount_OBJ | OBJ | char | REQ | INPUT |
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. |
szPrevSubsidiary_SUB | SUB | char | REQ | INPUT |
A subset of an object account. Subsidiary accounts include detailed records of the accounting activity for an object account.
|
mnPrevAddressNumber_AN8 | AN8 | MATH_NUMERIC | REQ | INPUT |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or
location.
|
szPrevComponentCode_CCOD | CCOD | char | REQ | INPUT |
A component code identifies a provisional burden that is accounted for at the billing detail transaction level. |
jdDateInvoiceJournalDate_IDGJ | IDGJ | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction is to be posted. The general accounting constants specify the date range
for each financial period. You can have up to 14 periods. Generally, period 14 is for audit adjustments.
The system edits this field for PBCO
(posted before cutoff), PYEB (prior year ending balance), and so on. |
szCurrencyCodeFrom_CRCD | CRCD | char | REQ | INPUT |
A code that identifies the currency of a transaction.
|
szCurrencyCodeOrigin_CRCF | CRCF | char | REQ | INPUT |
The currency code of the insured amount. |
jdPrevDateInvJournalDate_IDGJ | IDGJ | JDEDATE | REQ | INPUT |
A date that identifies the financial period to which the transaction is to be posted. The general accounting constants specify the date range
for each financial period. You can have up to 14 periods. Generally, period 14 is for audit adjustments.
The system edits this field for PBCO
(posted before cutoff), PYEB (prior year ending balance), and so on. |
szPrevCurrencyCodeFrom_CRCD | CRCD | char | REQ | INPUT |
A code that identifies the currency of a transaction.
|
szPrevCurrencyCodeOrigin_CRCF | CRCF | char | REQ | INPUT |
The currency code of the insured amount. |
cFooterSection_FTSC | FTSC | char | REQ | INPUT |
A hidden flag, embedded in the Invoice Print with Smart Fields program (R48507), that indicates whether a section is a footer or non-footer
section. These values are passed into the smart fields when you design a version of the Invoice Print with Smart Fields program to determine
whether the logic should use the Business View field or Previous Business View field. Valid values are:
Blank
Non-footer section.
1
Footer
section.
|
mnNumericField_MATH01 | MATH01 | MATH_NUMERIC | OPT | OUTPUT |
- - - Good Performance Low Value.
|
szErrorCode_ERNO | ERNO | char | OPT | OUTPUT |
The error number assigned by the JDE edit/update programs designating the exact error that occured. |