The Workfile Control Report

You use the Workfile Control Report (R48S710) to identify records in the Billing Detail Workfile table (F4812) that are not correct based on other information in the F4812 table.

You use data selection on this report to specify which records to evaluate.

Records that the system identifies as having integrity issues are listed with the appropriate error message on the report.

The Workfile Control Report examines records for these integrity issues:

Integrity Issue

Cause

Records with Process Complete flag

When the last record for a transaction is moved to the Billing Workfile History table (F4812H), the Process Complete field (LSSQ) is set to 1. The report displays an error when table F4812 contains any records with a value of 1 in the Process Complete field.

Records with Void flag

When you void an invoice, the workfile transactions that were included on the invoice return to table F4812 with a status of not billed. Table F4812 should not contain workfile transactions with a V in the Void field (VOID). The report displays an error when table F4812 contains any records with a value of V in the Void field.

Records recognized for revenue without a revenue batch number

When you run the Journal Generation program (R48132) 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 if the value in the Revenue Completed field (LSPM) is 1, but the Batch Number - Revenue field (ICUJ) is equal to 0.

Records for which journals have been generated without an active batch number

When you run the Journal Generation program to create journal entries for revenue recognition, the system enters 1 in the Journal Status Code field (JRST) and a batch number in the Batch Number - Active field (ICUA). The Batch Number - Active field contains a batch number only when journals have been generated but not yet posted.

The report displays an error when the value in the Journal Status Code field (JRST) is 1, but the Batch Number - Active field (ICUA) is equal to 0.

Currency errors

When the Multi-Currency Conversion option on the General Accounting Constants form is set to Y (Use multi-currency acct.) or Z (Use multi-currency acct-divis.), the report displays an error when any of these fields is blank:

  • Currency Code From (CRCD)

  • Currency Code Origin (CRCF)

  • Currency Mode (CRRM)

When the Multi-Currency Conversion option on the General Accounting Constants form is set to N (Do not use multi-currency acct), the report displays an error when any 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)

When the two exchange rates are the same, the system resets the values in these historical amount fields to 0.

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

Components do not exist for the 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 when a base record exists but no corresponding component records exist, or if one or more component records exist but no corresponding base record exists.

Component values not consistent with base record

These fields should contain identical values on 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 on a base record and its component records.

Inconsistent invoice information on component records

The report displays an error message when:

  • 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.

Inconsistent invoice information on burden records

The report displays an error message when:

  • The base record and burden 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 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.

Tax code errors

The report displays an error when any of these situations occur:

  • 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.

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 appear in the Invoice Summary Work File table (F4822).