3.30.126. Control Data Analysis

(1) Submission Processing’s Monitoring Section is responsible for the information in the IRM. The Monitoring Section makes the necessary changes on a yearly basis.

(2) The Director of Submission Processing is responsible for policy related to this IRM.

(3) The team manager is responsible for ensuring the IRM is timely submitted to Publishing each year.

(1) Program Reports: The program reports provided in the IRM are for identification and balancing purposes for the Submission Processing tax examiners and clerks.

(2) Program Effectiveness: The program effectiveness is determined by Submission Processing employees being able to successfully resolve any balancing of data issues they may encounter.

(1) The reports for the Control Data Analysis, Project PCD, are on the Control-D/Web Access server, which has a login program control.

(1) The table lists commonly used acronyms and their definitions:

(1) Service Center Directors, Headquarter Branch Chiefs, and Headquarter Analysts do not have the authority to approve deviations from IRM procedures. Any request for an exception or deviation to an IRM procedure must be elevated through appropriate channels for executive approval. Ensuring other functional areas are not adversely affected by the change and it does not result in disparate treatment of taxpayers.

(2) Request for an IRM deviation must be submitted in writing following instructions from IRM 1.11.2.2.4, Internal Management Documents System - Internal Revenue Manual (IRM) Process - When Procedures Deviate from the IRM. Any disclosure issues will be coordinated by the program owner. No deviations can begin until reviewed by the program owner and elevated through the appropriate channels for executive approval.

(3) All Submission Processing (SP) requests must be submitted to the following SP Headquarter Analyst:

Sue Allen
Submission Processing IRM Coordinator
Coordination & Quality Support Section
Program Management/Process Assurance Branch
sue.allen-cincinnati@irs.gov
(859) 320-3633

(1) This system primarily utilizes specific tape control records from the Campus Data Control System (SCF01), containing period data and a recirculating disc file, containing inventory and cumulative data for each campus pipeline program.

(2) The main purpose of this project is to feed computer counts to the Daily Production Report (by program) as pipeline documents are entered into the computer. This is necessary in order to compare the number of documents manually counted through pipeline with those entered and processed by the computer.

(3) The ultimate goal is to ensure that all pipeline documents are batched and processed to good tape under the correct program number.

(4) The objectives of PCD are accomplished through two computer programs. The main program (PCD03) loads the current Balance Forward File and adds period data for the current day. It then computes new percentages, new cumulative counts, and current inventory counts and generates updated records. The correction run (PCD01) is an update program for the Balance Forward File. It allows the campuses to insert, change and delete records on the existing file.

(1) A master table of all program codes, as specified in the 5995a database located via the Organization Function Program (OFP) Home Page web link on the Internal Revenue Service (IRS) Intranet at http://ofp.ds.irsnet.gov/index.asp has been established so that the program number will be printed on the Control Data Analysis reports and the program number and title will be printed on various other error and reject reports. The Program Number Master List contains all entries on the Program Number Master Table.

(2) Whenever changes are made to the Program Number Master Table, a Form 8000, Program Number Update Record will be forwarded from HQ to the Information Technology (IT) Division, Enterprise Computing Center (ECC) - Mainframe Operations Branch (MOB). Functional areas can view and/or print copies of the Program Number Update List (GMF-81-40) and the Program Number Master List (GMF-81-41) from Control-D.

(3) When updates have been completed the Campus GMF 81 Point of Contact (POC) or Production Monitor is responsible for analysis of the changes and notification to the Campus Accounting Operation Data Control to update the Balance Forward File. Data Control is also responsible for analyzing data on the Invalid Listing.

(4) Subsequent changes to the Program Number Master Table will be reflected on the Program Number Update List (GMF-81-40). The Program Number Master List (GMF-81-41) reflects all updated changes and should be utilized throughout the year by the Data Control Unit in the Accounting Operation for updating the Balance Forward File and to assist in analyzing data on the Invalid Listing (PCD-03-45).

(5) ECC MOB will download the Program Number Master List into the Batch/Block Tracking System (BBTS). Changes to blocking series on GMF-81-41 should be coordinatedby the Campus Production Monitor with the appropriate numbering units to ensure consistency of reporting.

(6) Changes to blocking series and the Saturday/Sunday key may cause items to post to the Invalid Listing, PCD-03-45. Should this happen, manual adjustments may be necessary until all work previously numbered, prior to receipt of the new Generalized Mainline Framework (GMF) Transmittal, is worked through the system.

(7) Run GMF-81 always produces a Program Number Update List and a Program Number Master List. The Program Number Update List shows each update record that was input. If the update record was found to be invalid, an error reason message is printed on the Program Number Update List under the heading "Error Reason". See Exhibit 3.30.126-2, Program Number Update List (GMF- 81-40). The Program Number Master List shows each entry in the Program Number Master Table (by Master File System) after the valid updates have been posted. See Exhibit 3.30.126-3, Program Number Master List (GMF-81-41).

(8) Form 8000, Program Number Update Record, must be completed by the responsible HQ analysts to add, delete or bypass a program number on the Program Number Master List. See Exhibit 3.30.126-4, Program Number Update Record (Form 8000).

(9) The Program Number Update Record cannot be used for generating subprograms on the Control Data Analysis Reports. PROJECT PCD (565) DOES NOT RECOGNIZE FIFTH DIGIT PROGRAM NUMBERS OTHER THAN A ZERO.

(1) Form 8000, Program Number Update Record, is utilized by Headquarters to update the GMF Program Number File, and by campus analysts to use subprograms on the error, reject and BOB registers and Error Resolution System (ERS) reports. See Exhibit 3.30.126-4, Program Number Update Record (Form 8000).

(2) When an update to the GMF-81-41 Program Number File is needed, campus personnel are to coordinate the request through their specific campus’ GMF-81-41 Point of Contact (POC). The campus GMF-81-41 POC must also coordinate with Submission Processing (SP) Headquarters program owners in addition to appropriate SP Headquarters IRM handbook analysts. The campus GMF-81-41 POC is to coordinate the requested change through the appropriate Headquarter handbook analysts for IRM 3.8.44, Campus Deposit Activity, or IRM 3.10.73, Batching and Numbering. The appropriate Headquarters handbook analyst will contact the Headquarters GMF 81-41 analyst who will work the requested change through the IT GMF-81-41 programmer.

(3) In order to complete this form, knowledge of the following IRMs is necessary:

• IRM 3.30.20, Organization, Function, and Program (OFP) Codes;

• IRM 3.30.126, Control Data Analysis;

• IRM 3.10.73, Batching and Numbering; and

• IRM 3.8.44, Campus Deposit Activity.

(4) GENERALLY, THE FIRST FOUR DIGITS OF A PROGRAM CODE ARE SPECIFIED IN IRM 3.30.20 AND CANNOT BE CHANGED. However, it is possible to use subprograms (fifth digit program codes) on the error, reject, and BOB registers and the ERS reports, by using the Program Number Bypass Key to bypass the HQ program number. Any key on the Form 8000 can be used to specify a fifth digit as long as the parameters for the campus subprogram entry specifies a set of documents identified by the parameters in the related HQ program number table entry. The following rules must be followed when subprograms are used.

1. Every possible combination of tax class, document code, and blocking series that is covered by the bypassed program must be covered by a subprogram.

2. DO NOT USE A ZERO IN THE FIFTH DIGIT OF A SUBPROGRAM. Program codes ending in 1 through 9 are used for subprograms and the code ending in zero is used for the HQ program code.

3. DO NOT SUBPROGRAM ONE PART OF A HQ PROGRAM AND USE THE HQ CODE FOR THE REST. When a code is subprogrammed, the entire HQ code is bypassed and all documents for the HQ program must use the subprograms.

(1) The Balance Forward File is maintained and updated daily through a recirculating process. This file is updated as follows:

1. Selected input from Service Center Control File (SCCF) for each Master File (and the reports column titles where those items appear) are:

If...	Then...
Good Block Proof Records	Good Transaction Items
Error Block Proof Records	Raw Errors Today
Reject Block Proof Records	Raw Rejects Today and Unpostable Rejects, Period
Renumber Block Proof Records	Rejects Cleared Today, Today’s Reject Deletions, Program Deletes
BOB Release Records	BOBs Cleared Today
BOB Control Records	Today’s New BOBs
Reinput Block Proof Records	Today’s Block Deletion Releases, Reinput
Delete Block Proof Records	Today’s Block Deletion Releases, Program Releases
Transaction Deletion Control Records	Today’s new Block Deletions
Manual and Generated Adjustment Transactions	Today's Transactions

2. Form 8350, Correction to Block Proof Summary Balance Forward Records (See Exhibit 3.30.126-5, Correction to Block Proof Summary Balance Forward Records, Form 8350). This form is prepared by the functional area responsible for balancing the Block Proof Summary reports. Integrated Submission and Remittance Processing (ISRP) can be used for inputting data from Form 8350. However, the option exists for using the Conversational Time Sharing (CTS) routine (on demand terminals) for inputting this data. This option requires coordination with the Enterprise Computing Center (ECC) if ISRP is unavailable.

3. Block Deletes Processed List (PCD-03-48). ISRP must be used for inputting data from this listing. (See Exhibit 3.30.126-17.)

(1) IMF, BMF, EPMF, IRP and NMF

1. Correction Run:

Report	Title	Location
PCD-01-40	Balance Forward Listing	Exhibit 3.30.126-6
PCD-01-41	Update Status Listing	Exhibit 3.30.126-7

2. Control Data Analysis:

Report	Title	Location
PCD-03-40	Block Proof Summary and Error Analysis	Exhibit 3.30.126-8
PCD-03-41	Reject Analysis Report	Exhibit 3.30.126-9
PCD-03-42	IMF Block Deletion Analysis	Exhibit 3.30.126-10
PCD-03-43	BOB Analysis	Exhibit 3.30.126-11
PCD-03-44	Balance Forward Listing	Exhibit 3.30.126-12
PCD-03-45	Invalid Listing Summary	Exhibit 3.30.126-13
	Invalid Listing Error Codes	Exhibit 3.30.126-14
PCD-03-46	Reject Reinput Batch Transmittal	Exhibit 3.30.126-15
PCD-03-47	Planning and Control Data Files Summary	Exhibit 3.30.126-16
PCD-03-48	Block Deletes Processed List	Exhibit 3.30.126-17

3. Files for input to Project PCC (563) Daily Production Report

(1) During the final cycles each year, campuses should make every effort to:

1. Reduce inventories in those functions reflected on the Control Data Analysis Reports.

2. Ensure final inventories are accurate for each program.

3. Review the next year’s program codes in Exhibit 3.30.126-1, WP&C Program Codes (Initialization), for any new, combined, or deleted codes.

4. Request well in advance all necessary computer listings from IT Enterprise Computing Center - Mainframe Operations Branch (ECC MOB).

(1) Information on this printout represents a summary by master file and program code of:

1. Period and cumulative items processed to good tape SCF 1151 prior to Tape Control Record List (TCRL) totals less block deletions and unpostable rejects.

2. Period and cumulative raw conversion error receipts.

3. Errors processed.

4. Error inventory (the net of the processing activity through mainframe) beginning inventory plus new errors minus errors cleared.

5. Period and cumulative percentage of the errors to the total items processed through raw conversion. (See Exhibit 3.30.126-8.)

Note: Errors processed, Error inventory, new errors, and errors cleared are from the perspective of SCCF and not from the perspective of ERS. For example, ERS considers items in Quality Review Selection (QRSEL) as worked while SCCF considers them as errors not yet cleared.

(2) Some of these computations are based on the Cumulative (Cum) Conversion Volume, which does not print on the analysis, but is present on the Balance Forward File and can be reviewed on the Balance Forward Listings (PCD-01-40 or PCD-03-44).

(1) This listing provides a summary by master file and program code of reject activities, including unpostable and raw rejects, raw reject rates, and combined inventories. (See Exhibit 3.30.126-9.)

(1) This printout furnishes totals by program code on the status of documents deleted at the campus during the Tape Edit Processor (TEP) run, or at the Enterprise Computing Center (ECC) - Martinsburg (MTB). (See Exhibit 3.30.126-10.)

(1) The BOB Analysis provides information as to the processing activity of documents in blocks which fail to meet GMF validity requirements. In addition, this printout provides period and cumulative counts of the number of blocks converted to good tape and the number of blocks out of balance, with a corresponding percentage factor. (See Exhibit 3.30.126-11.)

(1) The Balance Forward Listing provides a summary by program code of current inventories for errors, rejects, BOBs, and block deletions. It also provides cumulative data for good transactions, raw errors, conversion volumes, block deletes, BOBs, unpostable rejects, and raw rejects. (See Exhibit 3.30.126-12.)

(1) This provides a listing of records which completed mainline processing but could not be accounted for in PCD because they failed to meet a specific criteria in the GMF-81. (See Exhibit 3.30.126-13.)

(2) At the end of the Invalid Listing, a summary is provided for all Program Codes by Master File with the Total of Invalid Documents and Documents by Activity Code (From-To codes).

(1) This is a transmittal that lists records of prior and current years’ returns and documents by program number, block DLN and block volume. (See Exhibit 3.30.126-15.)

(1) This listing identifies by master file and DLN those items which have been deleted from the prior day’s TEP run. (See Exhibit 3.30.126-17.)

(1) Verification of Good Transaction Items – Each day, upon receipt of the Block Proof Summary Reports, a designated employee in the Balancing function should do the following:

1. Annotate the printout with the cycle and/or tape numbers. Since the mainline runs in each campus are not necessarily scheduled on the comparable shifts, each campus must determine the processing cycle and tape numbers to be annotated.

2. Ensure the Period Good Transaction Items are equal to today’s good transaction items from SCF-11-51. Good tape block proof records on the Invalid Listing must be taken into consideration for balancing purposes.

3. Cumulative Good Transaction Items should equal:

(2) Balancing of Error Analyses – The column totals to be verified are as follows:

1. Raw Errors Today should equal the error tape document count on the TCRL (SCF-11-51).

2. Cumulative Raw Errors total should equal:

The previous day’s cumulative total

Plus today’s raw errors

3. The Current Error Inventory should equal:

The previous day’s error inventory

Plus today’s raw errors

Minus errors cleared today

4. Error items on the Invalid Listing and SCF-11-51 listing must be taken into consideration for balancing purposes.

5. Compare inventory totals from PCD-03-40 with SCCF Summary (SCF-07-42).

(3) Balancing of Reject Analyses:

1. Unpostable Rejects Period should equal the total reject Generalized Unpostable Framework (GUF) items from the GUF-53-40 control run.

2. The Cumulative Unpostable Rejects should equal:

The previous day’s unpostables cumulative

Plus today’s period total

3. Raw Rejects Today should equal the reject tape document count on the TCRL (SCF-11-51).

4. Cumulative Raw Rejects total should equal:

The previous day’s cumulative total

Plus today’s raw rejects

5. The Current Reject Inventory should equal:

The previous day’s reject inventory

Plus unpostable rejects period

Plus today’s raw rejects

Minus rejects cleared today

6. Reject items on the Invalid Listing and error codes on SCF-11-51 must be taken into consideration for balancing purposes.

7. Compare reject inventory totals from PCD-03-41 with SCCF Summary (SCF-07-42).

(4) Resolving discrepancies – When discrepancies in balancing these reports occur, perform the following steps to locate the cause:

1. Ensure actual Control Record List (CRL) record count totals (not adjusted totals) are used in computations.

2. Check the CRL for error coded items.

3. Check the Invalid Control Record List (SCF-01-41) for invalid items not included in CRL totals.

4. Ensure all appropriate items on the invalid listing are considered.

(1) Today’s New Block Deletions – Campus Deletes. The total for this column should equal the Total TEP deletes from the previous day. This total is equal to the Block Document Count of Transaction (Trans) Deletion Control Records with From Code 5 (good) and To Code 0 (raw).

(2) Today’s New Block Deletions – MCC Deletes. The count of MCC Deletes should equal the adjustments input to the SCCF with Control Records Source Code "D."

(3) Today’s Block Deletion Releases should equal the number of items entered on the Block Delete Processed List (PCD-03-48) through ISRP the preceding day.

(4) The Current Block Deletion Inventory equals:

(1) The Block Deletes Processed List will generate whenever there is activity in Today’s New Block Deletions. This list will be used as the source document to input Block Delete Processed Records. A Block Delete Processed Record is completed as follows:

1. Processing Code – Enter one of the following:

Code	Description
Code "1"	to indicate that the block is being reinput under the original DLN or a corrected DLN with the original program code.
Code "2"	to indicate that the block will be reinput with the DLN which changes the original program code, or not reinput for reprocessing at all (in case of duplicate processing).
Code "3"	(EPMF only) to indicate that the original data will be input into the mainline run in lieu of reinputting the block.

2. System ID Code:

"1" if IMF

"2" if BMF

"3" if EPMF

"5" if IRP

"6" if NMF

3. MCC Deletes – The good tape portion of a block that was shipped to Master File but must be deleted before it posts to the taxpayer's account. The count of MCC Deletes should equal the adjustments input to the SCCF with Control Record source Code "D".

4. Block DLN – the 12 digit DLN.

5. Block Document Count – the total number of items in the block.

6. Program Code – the five digit program code that identifies the document(s).

(2) This data will be input through ISRP and used as input to subsequent running of PCD03.

(1) Today's New BOBs should equal the Total Computer Count on the BOB ID List (GMF-09-45). See Exhibit 3.30.126-26, BOB ID List (GMF-09-45).

(2) BOBs Cleared Today equals:

1. The current day's Old Computer Doc Count Deleted Block DLN on the BOB Correction Control List (GMF-09-46). See Exhibit 3.30.126-25, BOB Correction Control List (GMF-09-46).

2. Plus the current day's New Computer Document Count Matched Block DLN on the BOB Correction Control List.

(3) The Current BOBs Inventory equals:

(4) Cumulative BOBs equals:

(5) Blocks Converted Cum equals:

(6) BOB Blocks Period should equal Total Today's New BOBs on the BOB ID List (GMF-09-45).

(7) BOB Blocks Cum equals:

(8) BOBs Volume Percent equals:

(1) The Invalid Listing is generated whenever a record fails to meet specific criteria. When a DLN appears on this report, it does not mean that the returns or documents that carry the DLN did not process. Rather, it indicates that there is a consistency problem with report inventories or with determining the Program Number associated with the DLN.

(2) A record will appear on the Invalid Listing whenever the amount to be subtracted is more than the amount present in the PCD03 inventories. A record will also appear on the Invalid Listing when the mainframe cannot decode a DLN into a specific Program Number. The entire record will be considered as being invalid in PCD and no counts will be updated in PCD.

(3) The error records appear on the Invalid Listing as an image of an input tape record from the SCCF posting tape. The error codes will be printed on the right side of the Invalid Listing. See Exhibit 3.30.126-14 for detailed error code instructions.

(4) All error conditions indicated by the Invalid Listing, must be resolved by analysis. Review the GMF-81 and compare the DLN components. If you are not sure of the resolution, identify the physical location of the document and review the document type to determine the necessary action.

(5) Some "Error Code" conditions need not be corrected (e.g., Integrated Data Retrieval System (IDRS) transactions). Other document counts from the Invalid List need to be added or subtracted from the appropriate columns, when balancing the Block Proof Summary and Error Analysis and Reject Analysis Reports and a correction must then be input into the next PCD-01 run.

(6) PCD-03 program will accommodate only the current and five prior year dates. All invalid tape records printed on the Invalid Listing should be analyzed daily to determine the corrected printout totals. Ensure all necessary adjustments are promptly made to the Balance Forward File.

(1) The From Code identifies the function which determines the current status of a block of documents (or portion thereof). The To Code identifies how a block of documents (or portion thereof) is to be processed next.

(2) The Record Type ID Code indicates the type of control record either posted to SCCF or attempting to post to SCCF. This ID Code is used with the From and To Codes.

(3) Valid From and To Code combinations and Record Type ID Codes for Control Data Analysis reports are as follows:

(1) This section provides necessary information for the Block Out of Balance function in maintaining a computer generated analysis, by specific program code, of BOB blocks. The information to determine the item count and DLN of new blocks going to BOB status will be found on the SCCF Posting Tape. Information contained on the SCCF consists of an image of the BOB record. During the normal computer run, PCD-03 will analyze the SCCF for certain records to produce the Block Proof Summary and Error Analysis, Reject Analysis, and Block Deletion Analysis reports. The computer will also analyze the BOB record image, to produce the BOB Analysis Report.

(2) The BOB Analysis Report provides campus management with accurate information relative to the number and types of documents with out-of-balance conditions. In addition, the report provides a period and cumulative count of blocks converted to tape and the period and the cumulative counts of the number of BOB blocks to total blocks converted.

(1) Run PCD-03 analyzes certain BOB records on the SCCF Posting Tape to produce the specified output. The BOB Record (identified by a 2 in column 1 for all Master File ID Systems) is used to determine the number of new BOBs received for correction each day by the Block Out of Balance function. The DLN is analyzed to determine the appropriate program code. The Block Document Count is then read and recorded by program code on the BOB Analysis Report. These items are:

1. Today’s New BOBs

2. BOBs Cleared Today

3. Current BOBs Inventory

4. Cumulative BOBs

(2) BOB Release Record is computer generated by GMF during a BOB Correction Run and is input into the next PCD-03 run.

(1) The BOB Correction Control List (GMF-09-46) is computer generated by GMF and is provided on a daily basis.

(2) This list may be used to validate data on the BOB Analysis Report.

1. Old Computer Document Count Deleted Block DLN plus New Computer Document Count Matched Block DLN on the BOB Correction Control List (GMF-09-46) should equal the Total BOBs Cleared Today on the BOB Analysis Report (PCD-03-43).

2. Old Computer Document Count Non-Matched DLN of the BOB Correction Control List should equal Total Current BOB Inventory minus Total Today’s New BOBs on the BOB Analysis Report.

(3) The "Julian Date" on the BOB Correction Control List indicates the original BOB date. BOBs appearing on the list after three days should be checked to determine the reason they have not been cleared.

(4) A copy of this report may be found in Exhibit 3.30.126-25, BOB Correction Control List (GMF-09-46).

(1) This is a control listing provided by GMF on a daily basis (GMF-09-45).

(2) The BOB ID List may be used to validate data on the BOB Analysis Report.

1. Total BOB Blocks period on the BOB Analysis Report should equal the Total Today’s New BOBs on the BOB ID List.

2. Total of Today’s New BOBs on the BOB Analysis Report should equal the Total Computer Count on the BOB ID List.

(3) A copy of this report may be found in Exhibit 3.30.126-26, BOB ID List (GMF-09-45).

(1) Report any out of balance condition to the appropriate computing center if it appears to be a result of programming or scheduling errors.

(2) Verify that Production Control Records and Production Adjustments, generated daily by run PCD-03 are input to Project PCC (563) the same day.

(3) Prepare Correction to Block Proof Summary Balance Forward Records, Form 8350, at the start of the MF processing year to include the data required for the initial Balance Forward File. The CTS routine (on demand terminals) may be used for inputting this data. However, the Demand Terminal input must be coordinated with the computing centers.

(4) Update the Balance Forward File, as necessary, based on data provided by the Balancing and Input Correction functions.

(1) Each record is formatted as follows:

(2) Computations for Receipts and Production Volumes on PCD-03 generated records:

1. Function 910 (Pos. 13-15), Errors - Counts from the Block Proof Summary and Error Analysis Report:

Receipts (Pos. 41-48)	Raw Errors Today
Production (Pos. 49-56)	Errors Cleared Today

2. Function 920 (Pos. 13-15), Rejects - Counts from Reject Analysis Report:

Receipts (Pos. 41-48)	Unpostable Rejects Period plus Raw Rejects Today
Production (Pos. 49-56)	Rejects Cleared Today

3. Function 930 (Pos. 13-15), BOBs - Counts from BOB Analysis Report:

Receipts (Pos. 41-48)	Today’s New BOBs
Production (Pos. 49-56)	BOBs Cleared Today

4. Function 940 (Pos. 13-15), Block Deletes - Counts from Block Deletion Analysis Report:

Receipts (Pos. 41-48)	The sum of Today’s New Block Deletions (SC and MCC Deletes)
Production (Pos. 49-56)	The sum of Today’s Block Deletion Releases (Reinput), plus Program Deletes and Record Rerun

5. Function 950 (Pos. 13-15), To Enterprise Computing Center - Martinsburg (ECC-MTB) - Computations based on counts from all PCD reports as follows:

Receipts (Pos. 41-48) Note: The result of this computation may be a minus volume but, when combined with the Function 610 roll-down, should appear as the same figure on the DPR as the Function 950 production.	Minus Raw Errors Today Plus Errors Cleared Yesterday Minus Raw Rejects Today Plus Rejects Cleared Today Minus Today’s Reject Deletions (Reinput and Program Deletes) Plus Today’s Block Deletion Releases, Record Rerun Minus Today’s New BOBs Plus BOBs Cleared Today
Production (Pos. 49-56)	Period Good Transaction Items from the Block Proof Summary and Error Analysis.

6. Function 960 (Pos. 13-15), Program Deletes – Counts are from the Reject Analysis and Block Deletion Analysis Reports:

   Note: Receipts (Pos. 41-48) and production (Pos. 49-56) are always the same and are the sum of the following.

Today’s Reject Deletions	Program Deletes
Plus Today’s Block Deletion Releases	Program Deletions

7. Function 970 (Pos. 13-15), Reinputs - Counts are from the Reject Analysis and Block Deletion Analysis Reports:

   Note: Receipts (Pos. 41-48) and production (Pos. 49-56) are always the same and are the sum of the following.

Today’s Reject Deletions	Reinput
Plus Today’s Block Deletion Releases	Reinput

8. Function 180 (Pos. 13-15), Batching:

   Note: Receipts (Pos. 41-48) and no production is generated for each program that has a Function 970 record. This computation is the following.

(1) Each record is formatted as follows:

(2) Computations for Receipts and Production for Function 950:

1. Cum Receipts since January 1 (Pos. 34-41) is the sum of:

Minus Today’s New Block Deletions, SC Deletes

Minus Today’s New Block Deletions, MCC Deletes

Minus Unpostable Rejects Period

Plus BOB Block Document Counts in the records with a "7" BOB Inventory Adjustment Code

Minus BOB Block Document Counts in the records with an "8" BOB Inventory Adjustment Code

Note: The result of this computation may be a minus volume.

2. The result of this computation may be a minus volume.

3. Cum Production This Week (Pos. 42-48) is minus Today’s New Block Deletions, SC Deletes.

4. Cum Production to the End of Scheduling Period (Pos. 49-56) is the sum of:

Minus Today’s New Block Deletions, SC Deletes

Minus Today’s New Block Deletions, MCC Deletes

Minus Unpostable Rejects Period

5. Cum Production to the End of Year (Pos. 57-64). This volume is identical to Pos. 49-56 above.

(3) Computations for Receipts (Pos. 34-41) and Inventory (Pos. 65-72) for Function 930:

1. In order to adjust BOB receipts for those blocks where the Generated Block Document Count was in error, the following computation is made for each program code:

Minus all Generated Block Document Count for BOB Release Records with Inventory Adjustment Code "7"

Plus all Generated Block Document Count for BOB Release Records with Inventory Adjustment Code "8"

2. The net Generated Block Document Count may be a minus volume.

(1) The first step in computing the Raw Error and Raw Reject Rates on the Block Proof Summary and Error Analysis and Reject Analysis Reports is the computation of a Period Conversion Total. The Period Conversion Total equals the sum of Good Transaction Items Period plus Raw Errors Today minus Errors Cleared Today plus Raw Rejects Today minus Rejects Cleared Today plus Today’s Reject Deletions Reinputs/Program Deletes. (BOBs are not included in the conversion total because they fall out of the system before the GMF processing for ISRP occurs.)

(2) The Raw Error Rate – Period equals the Raw Errors Today (Receipts) divided by the Period Conversion Total.

(3) The Raw Reject Rate – Period equals the Raw Rejects Today (Receipts) divided by the Period Conversion Total.

(4) To calculate cumulative error and reject rates, a Cumulative Conversion Volume is accumulated. The Cumulative Conversion Volume is the Period Conversion Total plus the Cumulative Conversion volume from the previous day taken from the previous day’s Balance Forward Listing. This new Cumulative Conversion Volume is entered on the Correction To Block Proof Summary Balance Forward Records, Form 8350.

(5) The Raw Error Rate – Cumulative equals the Raw Errors Cumulative divided by the Cumulative Conversion Volume.

(6) The Raw Reject Rate – Cumulative equals the Raw Rejects Cumulative divided by the Cumulative Conversion Volume.

(1) The rate computations for the total lines are the same as the computation by program code. However, for the total lines the respective fields for all programs are added together and the applicable rates are computed.

(1) Enter a two digit serial number (00-99) to the left of every line that contains data. Each line is considered a separate document.

(2) No more than 100 serial numbers may be placed in a block.

(3) Place each block of listings under a Form 1332, Block and Selection Record.

(1) For each block of forms and listings specified in IRM 3.30.126.9 and IRM 3.30.126.9.1 above, prepare a Block and Selection Record, Form 1332. Entries are required only in the areas specified herein. For an exhibit of the form, see IRM 3.10.73.12, Block Selection Control Record - Form 1332, Block Selection Record or Form 1332-SC, Block and Selection Record - Service Center Recognition/Image Processing System (SCRIPS).

1. SC Block Control Number - Affix the appropriate label, Alpha-Numeric Campus Block Number.

2. Document Locator Number - Enter the appropriate Format Code:

Description	Format Code
Form 8350	221
Block Deletes Processed List	176

3. Date - Enter the year, month, and day in format YYYYMMDD. For example: May 11, 2018 - enter 20180511.

4. Release forms and listings for input to ISRP.