The Workfile History Control Report

Journal Status is Generated, Not Posted

When you generate preliminary journal entries, the system changes the value in the Journal Status Code field (JRST) in the Billing Detail Workfile table (F4812) to 1 (Journaled). When you generate final journal entries, the system moves the record to the Billing Workfile History table (F4812H) and updates the Journal Status Code field in the F4812H table to a value other than 1. Therefore, table F4812H should not contain any records with a value of 1 in the Journal Status Code field. The report displays an error when table F4812H contains any records with a value of 1 in the Journal Status Code field.

Journal Status Code Inconsistent

The report displays an error message when the value in the Journal Status Code field (JRST) is 0, indicating that journals have not been generated, and any of these conditions, which occur when journals are generated or even later in the process, also exist:

• The Journal Status Code - Previous field (JRSP) has a value other than null or 0.

• The Revenue Completed field (LSPM) has a value of 1.

• The Batch Number - Revenue field (ICUJ) has a value other than 0.

• The Batch Number - Active field (ICUA) has a value other than 0.

Records Recognized for Revenue without a Revenue Batch Number

When you run the Create G/L Entries program (R48198) to create journal entries for revenue recognition, the system enters 1 in the Revenue Completed field (LSPM) and enters a batch number in the Batch Number - Revenue field (ICUJ). The report displays an error message when the value in the Revenue Completed field (LSPM) is 1, but the Batch Number - Revenue field (ICUJ) is equal to 0.

Revenue Not Processed, but Revenue Batch Exists

When the Revenue Completed field (LSPM) contains a value of 0, indicating that the revenue recognition process is not complete, and the Journal Status Code field (JRST) contains a value of 3, indicating that the billing detail transaction has changed, the report displays an error when either of these conditions exists:

• The Journal Status Code - Previous field contains a value other than 0, indicating that journals have been created for the batch.

• The Batch Number - Revenue field (ICUJ) contains a value other than 0, indicating that a revenue batch exists.

Revenue is Processed, Revenue Batch is Zero

When the value in the Process Complete field (LSSQ) is 1, indicating that the record is the last in a series, and the Journal Status Code field (JRST) contains a value of 4, indicating that the billing cycle is complete, the report displays an error message when the Batch Number - Revenue field (ICUJ) is equal to zero.

Active Batch is Zero

The report displays an error when the Batch Number - Active field (ICUA) is zero and these conditions are met:

• The Eligibility Code field (ELGC) is not equal to 1 (the record is not set up for invoicing only).

• The Process Complete field (LSSQ) contains a value of 0.

• The Secondary Sequence Number field (SCSQ) contains a value of 1, indicating that this is the first sequence for the record.

• The Journal Status Code field (JRST) contains a value of 4, indicating that the billing cycle is complete.

Revenue Batch is Zero

The report displays an error message when the Batch Number - Revenue field (ICUJ) is zero and these conditions are met:

• The Eligibility Code field (ELGC) is not equal to 1 (the record is not set up for invoicing only).

• The Process Complete field (LSSQ) contains a value of 1.

• The Secondary Sequence Number field (SCSQ) contains a value greater than 1, indicating that the record has been modified.

• The Journal Status Code field (JRST) contains a value of 4, indicating that the billing cycle is complete.

Currency Errors

When the Currency Mode field (CRRM) contains a value of D (domestic) or F (foreign), the report displays an error when either of these fields is blank:

• Currency Code - From (CRCD)

• Currency Code - Origin (CRCF)

When the Currency Mode field (CRRM) is blank, the report displays an error message when either of these fields is not blank.

Historical Amounts Equal to Zero

When you generate invoices, the system updates the Currency Conversion Rate - Divisor field (CRRD) with the exchange rate that is used for invoice generation only if it is different from the exchange rate that was used during workfile generation. In this situation, the system saves the values in these fields because the different exchange rate would cause the amounts to be different:

• Amount - Revenue - Historical (HBTL)

• Amount - Invoice - Historical (HITL)

• Amount - Invoice Taxable - Historical (HITX)

The report displays an error messages when the exchange rate used during invoice generation is different from the exchange rate used during workfile generation and any of the historical amounts field has a value of 0.

Components Do Not Exist for Base Record

Under normal circumstances, the system attaches component records to the corresponding base record by updating the Component Link field (CLNK) for these records with the same number. The Component Code field (CCOD) is blank on the base record and is updated on the component records.

The report displays an error message when a base record exists, but no corresponding component records exist, or when one or more component records exist, but no corresponding base record exists.

Component Values Not Consistent with Base Record

These fields should have identical values in a base record and its corresponding component records:

• Eligibility Code (ELGC)

• Job Type (Craft) Code (JBCD)

• Job Step (JBST)

• Business Unit - Home (HMCU)

• Business Unit - Host (JMCU)

• Suspend Aging (AGS)

• Date - Age Override (DAGO)

• Hold Code - Service Billing Transaction (HLD)

• Date - Released (Julian) (RDJ)

The report displays an error message when any of these fields have different values in a base record and its component records.

Inconsistent Invoice Information on Component Records

The report displays an error message when one of these situations occurs:

• The base record and component records have different invoice numbers in the Document (Order #, Invoice, and so forth) field (DOCZ).

• The base record has a value of 0 in the DOCZ field, indicating that the base record has not been included in an invoice, but one or more associated component records have an invoice number in the DOCZ field.

• The base record has an invoice number in the DOCZ field, indicating that the base record has been included in an invoice, but one or more associated component records have a value of 0 in the DOCZ field.

Tax Code Errors

The report displays an error message when any of these situations exists:

• The Tax Expl Code 1 field (EXR1) is not blank, but the Tax Rate/Area field (TXA1) is blank.

• The Tax Rate/Area field (TXA1) is not blank, but the Tax Expl Code 1 field (EXR1) is blank.

• The Tax Expl Code 1 field (EXR1) is equal to S (Sales or VAT (output) Tax), C (Value Added + Sales Tax), V (Value Added (input) Tax), or V+ (Value Added Tax, Tax on Tax), and the Amount - Invoice Tax field (ITAM) is blank.

Records Out of Sequence

The report displays an error message when the records in the Billing Workfile History table (F4812H) are out of sequence, based on the information in these primary key fields:

• Billing Control ID (BCI)

• Date - For G/L (and Voucher) (DGL)

• Sequence Number (SBSQ)

• Parent Sequence Number (PRSQ)

• Secondary Sequence Number (SCSQ)

• Split Link (SLNK)

• Component Link (CLNK)

• Component Code (CCOD)

Split Record Out of Sequence

The program checks all records for which the Parent Sequence Number field (PRSQ) has a value greater than 0. The report displays an error message when a record does not exist with the same primary field values as the first record and a value in the Sequence Number field (SBSQ) is equal to the value in the Parent Sequence Number field from the first record.

Duplicate Records Exist

The report displays an error message when identical records exist in the Billing Detail Workfile table (F4812) and the Billing Workfile History table (F4812H).

Missing Invoice Summary (F4822) Record

The report displays an error message when the Document (Order #, Invoice, and so forth) field (DOCZ) contains an invoice number, indicating that the workfile record has been included in an invoice, but no corresponding invoice records exist in the Invoice Summary Work File table (F4822).

Inconsistent Invoice Information on Burden Records

The report displays an error message when one of these situations occurs:

• The base record and burden records have different invoice numbers in the Document (Order #, Invoice, and so forth) field (DOCZ).

• The base record contains a value of 0 in the DOCZ field, indicating that the base record has not been included in an invoice, but one or more associated burden records have an invoice number in the DOCZ field.

• The base record has an invoice number in the DOCZ field, indicating that the base record has been included in an invoice, but one or more associated burden records have a value of 0 in the DOCZ field.