## Reviewing Control Reports

This chapter provides an overview of control reports and discusses how to:

- Run control reports.

- Set processing options for Invoice Summary to Workfile Control Report (R48S751).

### Understanding Control Reports

This section discusses:

- Control reports.

- The Workfile Control Report.

- The Workfile History Control Report.

- The G/L Link to Account Ledger Control Report.

- The Account Ledger to G/L Link Control Report.

- The Workfile to G/L Link Control Report.

- The G/L Link to Workfile Control Report.

- The Invoice Summary to Workfile Control Report.

- The Invoice Summary to Customer Ledger Control Report.

- The Customer Ledger to Invoice Summary Control Report

#### Control Reports

You use control reports to help ensure the reliability of the accounting data.

For the JD Edwards EnterpriseOne Contract Billing and Service Billing systems, it is important that the amounts billed in the Billing Workfile Detail table (F4812) and the Billing Workfile History table (F4812H) reconcile with corresponding amounts in the Account Ledger table (F0911).

Note. If you run the Workfile History Purge program (R48S999) before running any of the control reports, the results might be inaccurate. Specify a date range in the data selection of the control reports to exclude records that have been purged.

#### 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).

#### The Workfile History Control Report

You use the Workfile History Control Report (R48S711) to identify records in the Billing Workfile History table (F4812H) that are not correct based on other information within the F4812H table.

You use data selection 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 History Control Report examines records for these integrity issues:

Integrity Issue | Cause
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.

#### The G/L Link to Account Ledger Control Report

You use the G/L Link to Acct Ledger Control Report (R48S720) to verify that the information contained in the G/L Link table (F48S912) accurately represents the information that has been written to the Account Ledger table (F0911).

The report analyzes records in the F48S912 table that are grouped by billing control ID. The report compares all of the records in the group to the first record in the group and prints an error message when the accounting information for any record in the group does not match the accounting information for the first record in the group. The accounting information is stored in these fields:

- Account ID (AID)

- Business Unit (MCU)

- Object Account (OBJ)

- Subsidiary (SUB)

- Subledger - G/L (SBL)

- Subledger Type (SBLT)

- Batch Number (ICU)

As the report analyzes each F48S912 record, it adds the values in the Amount field (AA) and the Units field (U) and calculates the total amount and units for the group.

The report verifies that every record in the F48S912 table has a corresponding record in the F0911 table and verifies that the total amount and units for each F48S912 group equals the values stored in the Amount field (AA) and Units field (U) for the corresponding F0911 record. When the total amount and units are not equal, the report displays an error message and displays the difference between the totals amount and units from the F48S912 table and the amount and units from the F0911 table.

The report also displays an error when the accounting information for the F48S912 group does not match the accounting information for the F0911 record.

You use data selection to specify which records to evaluate. However, including some records from a certain batch number and excluding other records from the same batch might produce false error messages on the report. Oracle recommends that you limit the data selection to the batch number or batch date.

Note. The data sequencing for the G/L Link to Acct Ledger Control Report is hard-coded. Do not change it.

#### The Account Ledger to G/L Link Control Report

You use the Acct Ledger to G/L Link Control Report (R48S721) to verify that each record in the Account Ledger table (F0911) that was created by the revenue process in the JD Edwards EnterpriseOne Service Billing or JD Edwards EnterpriseOne Contract Billing system has at least one corresponding record in the G/L Link table (F48S912).

The report selects only the rows in the F0911 table that contain one of these document types:

- EU (Service Billing Revenue)

- AJ (Service Billing Adjustments)

- BA (Billing Adjustments)

The report lists any F0911 records that have one of these document types but does not have at least one corresponding record in the F48S912 table.

Note. The data selection for the Acct Ledger to G/L Link Control Report enables you to specify some columns from the F48S912 table. However, because the report selects only records from the F0911 table that do not have corresponding records in the F48S912 table, using columns from the F48S912 table in the data selection has no effect.

#### The Workfile to G/L Link Control Report

You use the Workfile to G/L Link Control Report (R48S730) to identify integrity issues between the Billing Detail Workfile and Billing Workfile History tables (F4812 and F4812H) and the G/L Link table (F48S912).

Note. Table F48S912 stores key information from workfile transactions and the subsequent journal entry created in the Account Ledger table (F0911). This table is used for reporting and audit purposes.
You use data selection to specify which records to evaluate.
You should run this report after you have run the Create G/L Entries program (R48198). Any G/L batches that have been created in the JD Edwards EnterpriseOne Contract Billing or Service Billing system that have not been through the Create G/L process might cause discrepancies on the report.

The Workfile to G/L Link Control Report views table F4812 and table F4812H as if they were a single table.

Only revenue-related transactions are processed.

The report groups records in the F4812 and F4812H tables by billing control ID (BCI). The report selects all of the transactions in the F48S912 table that have the same billing control ID and accumulates the amounts from the F48S912 records.

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

First-Line Errors

In some situations, the accumulated amount from the F48S912 table should equal the amounts from the F4812 and F4812H tables. In other situations, the accumulated amount from the F48S912 table should be zero. In either of these situations, when the amount from the F48S912 table is incorrect, the report prints an error message on the first line of the error report.

When the selected F4812 or F4812H record has a value of 4 (Costing Only) or 1 (Invoicing Only) in the Eligibility Code field (ELGC), or is a prior split or prior component transaction, and when the accumulated amount from the F48S912 table does not equal zero, the report displays one of these error messages:

- Accumulated G/L Link Amount Should be 0 - Elg Code=1

- Accumulated G/L Link Amount Should be 0 - Elg Code=4

- Accumulated G/L Link Amount Should be 0 - Earlier Split

- Accumulated G/L Link Amount Should be 0 - Earlier Component

  Note. A billing control ID group is a group of records from the F4812 and F4812H tables that belong to the same transaction. Each record in the group has the same values in these fields:
  Date - For G/L (and Voucher) (WDDGL)
  Billing Control ID (WDBCI)
  Parent Sequence Number (WDPRSQ)
  Sequence Number (WDSBSQ)
  Component Code (WDCCOD)
  A prior split transaction is a billing control ID group that has been split into new transactions. The G/L Link revenue transactions that are associated with earlier split groups should net to zero.
  A prior component transaction is a billing control ID group that had a component code but had the component code removed through a transaction re-extension. The G/L link revenue transactions that are associated with earlier component groups should net to zero.

When the selected F4812 or F4812H record is not designated as Cost Only or Invoicing Only and is not a prior split or prior component transaction, the report lists one of these error messages when the value in the Amount - Revenue field (BTOL) from the selected F4812 or F4812H record does not equal the accumulated amount from the F48S912 table:

- Incorrect Accumulated G/L Link Amount, No G/L Link Transactions Found.

- Incorrect Accumulated G/L Link Amount, Wrong Number of G/L Link Transactions.

- Incorrect Accumulated G/L Link Amount, Correct Number of G/L Link Transactions.

Second-Line Errors

When the system encounters any of the first-line errors, the report checks the F4812 and F4812H records that belong to the BCI group. The report compares the amounts from the F48S912 records with the amounts in the Amount - Revenue field from the F4812 and F4812H records, along with the number of document type AJ (Service Billing Adjustments) and document type EU (Service Billing Revenue) entries, and displays one of these error messages on the second line:

- Missing EU transaction

- Missing AJ transaction

- Extra EU transaction

- Extra AJ transaction

- EU entry has wrong amount

- AJ entry has wrong amount

The report displays the primary key fields from the F4812 and F4812H tables, the revenue amount, the G/L link amount, the discrepancy between these values, and the two error messages describing the problem.

#### The G/L Link to Workfile Control Report

You use the G/L Link to Workfile Control Report (R48S731) to identify records that are missing from the Billing Detail Workfile table (F4812) and the Billing Workfile History table (F4812H), based on data contained within the G/L Link table (F48S912).

Note. Table F48S912 stores key information from workfile transactions and the subsequent journal entry created in the Account Ledger table (F0911). This table is used for reporting and audit purposes.
You use data selection to specify which records to evaluate.
You should run this report after you have run the Create G/L Entries program (R48198). Any general ledger batches that have been created in the JD Edwards EnterpriseOne Contract Billing or Service Billing system that have not been processed through the Create G/L Entries program might cause discrepancies on the report.

The G/L Link to Workfile Control Report views table F4812 and table F4812H as if they were a single table.

Only revenue-related transactions are processed.

The report reads through records in the F48S912 table and attempts to locate the corresponding F4812 or F4812H record. If no corresponding record is found, the report displays an error message.

#### The Invoice Summary to Workfile Control Report

You use the Invoice Summary to Workfile Control Report (R48S751) to verify that the amounts in the Billing Detail Workfile and Billing Workfile History tables (F4812 and F4812H) match the amounts in the Invoice Summary Work File table (F4822).

The system uses either table F4812 or table F4812H, depending on the current status of the invoice in the F4822 table. For invoices that have not been processed by the Create A/R Entries program (R48199), the system uses table F4812. The system uses table F4812H for invoices that have been processed by the Create A/R Entries program.

For each record in the F4822 table, the report selects the corresponding F4812 or F4812H records and totals the amounts. Any discrepancies between the totals of the F4812 or F4812H records and the F4822 record are listed on the error report.

The report compares amounts from these fields:

Fields from the F4812 table or the F4812H table | Comparison | Fields from the F4822 table
Amount - Invoice (ITOL) | should equal | This Period (THPD)
Amount - Foreign Invoiced (CITL) | should equal | This Period - Foreign (FHPD)
Amount - Invoice Tax (ITAM) | should equal | Amount - Tax (STAM)
Amount - Foreign Invoice Tax (CITX) | should equal | Amount - Foreign Tax (CTAM)

In addition, when the Tax Explanation code for the F4822 record is E (Value Added Tax Exempt) or blank, the report compares the amounts from these fields:

Fields from the F4812 table or the F4812H table | Comparison | Fields from the F4822 table
Amount - Invoice Taxable (ITXA) | should equal | Amount - Non-Taxable (ATXN) or Amount - Taxable (ATXA)
Amount - Foreign Invoice Taxable (CITA) | should equal | Amount - Foreign Non-Taxable (CTXN) or Amount - Foreign Taxable (CTXA)

You can print the report in summary or detail mode. The summary report includes invoice information from the F4822 table. The detail report includes both invoice information from the F4822 table and the corresponding information from the F4812 or F4812H tables. You use the processing options to specify whether to print the summary or detail report.

#### The Invoice Summary to Customer Ledger Control Report

You use the Invoice Summary to Customer Ledger Control Report (R48S761) to verify that the amounts in the Invoice Summary Work File table (F4822) match the amounts in the Customer Ledger table (F03B11).

This table describes how the system compares the amounts for each invoice in the F4822 table to the amounts for the same invoice in the F03B11 table:

F4822 Fields | F03B11 Fields
This Period (THPD) | Amount - Gross (AG)
This Period - Foreign (FHPD) | Amount - Currency (ACR)
Amount - Taxable (ATXA) | Amount - Taxable (ATXA)
Amount - Foreign Taxable (CTXA) | Amount - Foreign Taxable (CTXA)
Amount - Tax (STAM) | Amount - Tax (STAM)
Amount - Foreign Tax (CTAM) | Amount - Foreign Tax (CTAM)
Amount - Non-Taxable (ATXN) | Amount - Non-Taxable (ATXN)
Amount - Foreign Non-Taxable (CTXN) | Amount - Foreign Non-Taxable (CTXN)

The system prints an error on the report if any of the amounts are not equal.

Note. The system processes posted records only.

#### The Customer Ledger to Invoice Summary Control Report

You use the Customer Ledger to Invoice Summary Control Report (R48S771) to verify that each invoice transaction in the Customer Ledger table (F03B11) that originated in the JD Edwards EnterpriseOne Contract Billing or Service Billing system has at least one corresponding source transaction in the Invoice Summary Work File table (F4822).

The system prints an error on the report if table F4822 does not contain a corresponding source transaction.

### Running Control Reports

You can run all of the control reports from the Billing Control Reports menu (G48S33).

### Setting Processing Options for Invoice Summary to Workfile Control Report (R48S751)

Processing options enable you to specify the default processing for programs and reports.

Print

This processing option enables you to specify whether to print a summary or detail report.

1. Summary or Detail | Leave this processing option blank to print the error report in summary mode. Enter 1 to print the error report in detail format. In summary format, only invoice information appears on the error report. In detail format, the system prints workfile information as well as the summary information.