Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnBatchNumber | ICU | MATH_NUMERIC | OPT | 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. |
mnBatchNumberActive | ICUA | MATH_NUMERIC | OPT | NONE |
This is the batch number assigned during the Service Billing generation. This batch number will be used as a linking mechanism to allow
the user to reset records in the Service Billing History file (F4812H) to their previous journal status. This field will contain a batch number only
while the batch is recognized by the system as being active and hasn't been posted. This field can be cleared at two possible times during
the Service Billing Generation cycle; either when the batch is identified for deletion or if the batch is posted. |
cGenerationTypeService | GTYP | char | OPT | NONE |
A code that determines the batch types and markup rules for invoice, revenue, and component amounts. The system assigns the batch
type when the batch is created. Depending on how you define the billing constants, different markup rules can apply to different amounts. Valid
values are:
1
Apply the markup rule to invoice, revenue, and component amounts. If the billing constants specify that invoice and revenue
amounts are always the same, the markup rule applies to revenue, invoice, and component amounts. If the billing constants specify that the
invoice and revenue amounts can be different, the markup rule still applies to revenue, invoice, and component amounts if no type 2 rule
exists.
2
Apply the markup rule to revenue and component amounts. If the billing constants specify that the invoice and revenue amounts can be
different, the markup rule applies to revenue and component amounts only.
3
Apply the markup rule to component amounts only. This rule is not
dependent on billing constants settings. |
szWorkStationId | JOBN | char | OPT | NONE |
The code that identifies the work station ID that executed a particular job.
|
mnDocumentOrderAlt | DOCZ | MATH_NUMERIC | OPT | NONE |
The original document number. This can be a voucher, an invoice, unapplied cash, a journal entry number, etc. Matching document
numbers are also used to identify related documents in the Accounts Receivable and Accounts Payable systems. See matching document
(DOCM). This document number (DOCO) is always the original document number, and the matching document number (DOCM) is the check,
adjustment, or credit to be applied against the original document.
For example:
A/P Automated/Manual Payment: Original (DOCO) - Voucher;
Matching Document (DOCM) - Payment
A/R Original Invoice: Original (DOCO) - Invoice
Receipt Application: Original (DOCO) - Invoice; Matching
Document (DOCM) - Receipt
Credit Memo/Adjustment: Original (DOCO) - Invoice; Matching Document (DOCM) -Credit Memo
Unapplied
Case: Original (DOCO) - Receipt |
szDocTypeInvoiceOnly | DCTI | char | OPT | NONE |
A user defined (00/DI) document type for invoice entry. Any document type set up for invoice-only entry should begin with the letter R
(receivables). The default is RI, RR, or RM. Reserved document types have been defined for vouchers, invoices, receipts, and time sheets.
The
reserved document types are:
P_
Accounts Payable Documents R_Accounts Receivable Documents
T_
Payroll Documents I_Inventory
Documents
O_
Order Processing Documents
Note: Verify that the default document type for invoices is set up in both UDC 00/DT and UDC 00/DI.
|
szDocumentCompanyInvoice | KCOI | char | OPT | NONE |
Invoice Document Company. |
cModeFlag | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|
cErrorId | EV01 | char | OPT | NONE |
An option that specifies the type of processing for an event.
|