| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| mnBillingControlId | BCI | MATH_NUMERIC | REQ | INPUT |
A unique number that the system assigns to each billing record. The system assigns the number from the Next Numbers - Automatic table
(F0002) for system 15, line 2 (Billing Control).
|
| jdGLDate | DGL | JDEDATE | REQ | INPUT |
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.
|
| mnParentSeqNo | PRSQ | MATH_NUMERIC | REQ | INPUT |
A number that provides an audit trail to the original transaction of a billing detail transaction. The system initially assigns 000 as the parent
sequence number. The number remains 000 unless you split the transaction. In this case,the sequence number (SBSQ) of the original
transaction becomes the parent sequence number (PRSQ) for the resulting transactions. |
| mnSeqNo | SBSQ | MATH_NUMERIC | REQ | INPUT |
A number that provides an audit trail for the billing detail transactions related to the same billing control ID. The system initially assigns 001
as the sequence number (SBSQ) of the original transaction. If you split a transaction, the system increments the number to the next available
sequence numbers (SBSQ) for the resulting transactions. |
| mnSecSeqNo | SCSQ | MATH_NUMERIC | REQ | INPUT |
A number you can use to track the changes applied to a billing detail transaction. The system initially assigns 001 as the secondary
sequence number (SCSQ). Each time you modify the billing detail transaction, the system increases the number by 1. |
| cGenerationType | GTYP | char | REQ | INPUT |
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. |
| cJrnlStsCode | JRST | char | OPT | INPUT |
A code that identifies whether the system has created the accounting Journals.
0 Not Journaled
1 Journaled
2 Posted
3 Billing
detail transaction has been changed
4 History record has completed the billing cycle and any adjustments for accounting journals have been
created |
| mnActiveJrnlBatchNumber | ICUA | MATH_NUMERIC | REQ | INPUT |
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. |
| szWorkStationId | JOBN | char | OPT | INPUT |
The code that identifies the work station ID that executed a particular job.
|
| szUserId | USER | char | OPT | INPUT |
The code that identifies a user profile.
|
| szProgramId | PID | char | OPT | INPUT |
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.
|
| jdDateUpdated | UPMJ | JDEDATE | OPT | INPUT |
The date that specifies the last update to the file record. |
| mnTimeLastUpdated | UPMT | MATH_NUMERIC | OPT | INPUT |
The time that specifies when the program executed the last update to this record. |