Building the Execution Id Work File

Overview

Use this job aid to build the execution Id work file. In order to produce any of the Execution Id Reports, a work file containing the transactions must be created. The work file contains only those transactions that existed at time of the creation of the work file. Any transactions that are entered or posted in the dataset after the creation of the work file will not be included in the Execution Id Reports. Purged and deleted transactions are not included in the work file. The process of building this work file may require a significant amount of time and disk space. The amount of time required to build the work file is affected by such factors as the size of the files, speed of the processor, the availability of contiguous disk space, and average access time of the disk drive. The disk space consumed by the work file depends primarily on the number of transactions included in the selection process. The work file may be built after normal business hours. In which case, it will be necessary to leave the workstation used in the extraction process and file server powered up. The process may be included in a month-end report stream. If a work file already exists, its date range is indicated in the upper section of the window. This option replaces any existing work file in the dataset. The work file can be deleted after printing all desired Execution ID Reports to free up disk space if necessary.

To build the execution Id work file:

1. From the Toolbar, click SJI for System Journal Interface.

2. Select Execution Id, and then select Build Execution Work File.

   Open

   

    

3. Choose an empty box and Select Create. (if you do not have Multiple Execution Files check marked this page will be skipped)

   Open

   

    

4. In the Beginning Ledger Date box, type the earliest date and in the Ending Ledger Date box, type the latest date that transactions should be included in the work file. Only transactions with a ledger date or void date within this date range are included in the work file.

5. In the Detail to Include boxes, determine which packages to include in the extraction process. A positive response selects transactions from the source package (module) for inclusion in the work file. A negative response excludes those transactions. (We recommend creating the work file will all packages so that both sides of each transaction will be included). A message is displayed at the bottom of the screen to indicate the progress of the extraction process.

6. Click OK.

    

7. A Description must be entered in the box, then Click OK.

    

8. If you chose to include Commodity Settlements, an override window displays. Click Yes to output the contents of the Vehicle ID box, Ticket Number box, or Delivery Sheet box instead of the contents of the Discount/Premium Description box from the system account (transaction) codes, or click No to output the normal contents of the box.

    

9. At the Is This Correct? prompt, click Yes.

    

10. At the Do You Want These To Be The New Default Parameters, click No.

     

Learn more about Execution Work File feature: