**October 29, 1990 M28-1, Part I**

**Change 1**

**CONTENTS**

**CHAPTER 8. CHAPTER 31 TARGET PROCESSING**

**PARAGRAPH PAGE**

**SUBCHAPTER 1. THE SYSTEM**

8.01 Target System Is Essential to Chapter 31 Recordkeeping 8-1

8.02 Specific Processing Instructions 8-1

a\. VR&C Target Processing 8-1

b\. Adjudication Target Processing 8-1

8.03 Chapter 31 Target System Overview 8-1

a\. Online Target Processing 8-1

b\. VR&C Payment System Processing 8-2

8.04 Target System Security 8-2

a\. Paper Document Security 8-2

b\. Target Access Card Security 8-2

c\. Sensitive Files 8-2

d\. Work-Study Students , Use of Target System 8-2

e\. Further Information on Target Security 8-2

8.05 Authorization of VR&C Division Target Commands 8-2

a\. Requesting Appropriate Commands 8-2

b\. Special Restrictions and Concerns 8-2

8.06 Target System Training 8-2

a\. Purpose of CAI Lessons 8-2

b\. Uses and Limitations of CAI Lessons 8-3

c\. Multiple Resources Available for Target Training 8-3

8.07 Target Liaison Representative 8-3

a\. Liaison With Station Target Resources 8-3

b\. Training Program 8-3

c\. Other Related Duties 8-3

8.08 VR&C Outbased Locations 8-4

a\. Locations With Target Equipment 8-4

b\. Locations Without Target Equipment 8-4

c\. Target Training for Personnel in Outbased Locations Without Target
Equipment 8-4

8.09 Schedule of Operations 8-4

a\. Target Processing Schedule 8-4

b\. Use of the Chapter 31 Payment Schedule of Operations 8-4

8.10 Chapter 31 Transaction Types 8-5

a\. Statistical Master Record Transaction Types 8-5

b\. Pay Transaction Types 8-6

8.11 Manila Regional Office 8-6

8.12 Common Target Commands, Functions and Processing Procedures Which
May Be

Used for Chapter 31 8-8

a\. Commands and Functions 8-8

b\. General Target Processing Procedures Apply to Chapter 31 8-8

**8-i**

**M28-1, Part I October 29, 1990**

**Change 1**

**CONTENTS-Continued**

**PARAGRAPH PAGE**

**SUBCHAPTER II. THE 320 SCREEN**

8.13 General 8-10

8.14 Processing Overview 8-10

a\. 320 Screen Access 8-10

b\. PIF (Pending Issue File) Search 8-10

c\. Master Record Search 8-10

8.15 The 320 Screen-Case Status/Control/Counseling 8-10

a\. Access to 320 Screen Data Entry Fields 8-10

b\. Case Status Data 8-10

c\. Priority Updating of Case Status Fields 8-11

d\. Target Case Status Categories and Reasons 8-11

e\. Open/Closed Case Status 8-11

f\. Future Control Data 8-11

\(1\) Case Status Future Controls 8-11

\(2\) Future Employee Controls 8-11

\(3\) Revision Capability Restricted by Division 8-11

\(4\) Selection of Control Dates 8-11

\(5\) One-Time Notice for Certain Cases Before

Deletion From the Chapter 31 Master Record 8-12

\(6\) Recurring Notices for Certain Cases 8-12

\(7\) VR&C Division Routes

Employee Future Control Notices 8-12

\(8\) M35 (CH31 Case Status/Future Control)

Inquiry Screen 8-12

\(9\) Modify or Delete Future
Controls\...\...\...\...\...\...\...\...\.... 8-12

g\. Counseling Information 8-12

\(1\) General 8-12

\(2\) CER Folder Location 8-12

\(3\) Individualized Written Rehabilitation Plan or "Goal" Code 8-12

4\) Employment Code 8-12

\(5\) Pre-Chapter 31 Salary 8-13

6\) Post-Chapter 31 Salary 8-13

\(7\) Serious Employment Handicap 8-13

h\. Control Code Issues and Next Screen Processing 8-13

\(1\) General 8-13

2\) Control Codes 8-13

\(3\) Control Code Selection from Pending

Issue File 8-14

\(4\) VR&C Disallowance Processing 8-14

i\. Employee Responsible Code 8-14

j\. Processing Capability 8-15

\(1\) Online Updating 8-15

\(2\) Automatic TR 80R Generated 8-15

k\. Target System Edits 8-15

1\. Summary 8-15

\(1\) VR&C Division 8-15

\(2\) Other Divisions 8-16

**8-ii**

**October 29, 1990 M28-1, Part I**

**Change 1**

**CONTENTS-Continued**

**PARAGRAPH PAGE**

**SUBCHAPTER III. DISALLOWANCE PROCESSING**

8.16 Scope 8-22

8.17 Substantive Disallowance Based on Determination of Nonentitlement
8-22

a.. Initial Claim 8-22

b\. Reopened Claim 8-22

8.18 Processing the Disallowance on the 408 Screen 8-24

a\. VR&C Division Reasons for Disallowance 8-24

b\. Authorization 8-24

c\. Reprocessing a Disallowance 8-24

8.19 Circumstances When 408 Screen Will Not Be Completed for a
Disallowance 8-24

a\. New Evidence Causes No Change 1n Previous
Disallowance\...\...\...\...\...\...\...\...\...\...\... 8-24

b\. Duplicate Claim
Submitted\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...
8-24

c\. Informal Claim
Disallowed\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
8-24

d\. Apportionment Claim Disallowed 8-24

8.20 Reasons for Disallowance 8-24

a\. 65-Entitlement Exhausted 8-24

b\. 66-Beyond Eligibility Termination Date 8-24

c\. AA-Declared Ineligible 8-24

d\. BB-Not Entitled 8-24

e\. CC-Failure to Pursue 8-25

f\. DD-Other 8-25

8.21 Disallowance Letter 8-25

**SUBCHAPTER IV. USE OF THE CORR (CORRECTION) COMMAND**

8.22 General 8-25

8.23 CORR Processing 8-25

a\. Screens Allowing CORR Processing 8-25

b\. Protected (Noncorrectable) Fields 8-25

c\. Impact on Other Systems 8-25

d\. Online Processing-Transaction 02S 8-25

8.24 Target Access and Response 8-25

a\. Access Procedure 8-25

b\. Target Response 8-25

c\. Master Record Corrections 8-26

8.25 Correctable Fields 8-26

a\. M32-CH31 Master Record Status 8-26

b\. M33-CH31 Entitlement/Diagnostic 8-27

c\. M34-CH31 Entitlement History 8-28

d\. M36-CH31 Award Data 8-29

**SUBCHAPTER V. USE OF CNBR (CHANGE OF FILE NUMBER) COMMAND**

8.26 General 8-30

8.27 Change of File Number and Consolidation Function 8-30

a\. Identification of File Number To Be Retained 8-30

b\. Master Record Adjustment Restrictions Based on Master Record Types
8-30

c\. When the CNBR Command Can Be Used 8-30

d\. CNBR Processing Requires "XXX" in PAY Field for Type E Master
Records 8-30

**8-iii**

**M28-1, Part I June 4, 1987**

**CONTENTS-Continued**

**PARAGRAPH PAGE**

e\. CNBR Processing Requires All Payees Under One File Number Have Type
E

Master Records 8-32

f\. Online Update by Transaction 26R

8.28 Deletion Function 8-32

a\. Restricted to Statistical Master Records 8-32

b\. For Veteran Records Only 8-32

c\. Multiple Payee Records Cannot Be Deleted 8-32

d\. VR&C Officer Approval Required 8-32

e\. Online Update by Transaction 26D 8-32

8.29 Access and Response 8-32

a\. Access Procedure 8-32

b\. Target Response 8-33

c\. Input Processing 8-33

\(1\) Change or Consolidation of Chapter 31 Master Record Required 8-33

\(2\) Intentional Deletion 8-33

\(3\) Special Processing Functions 8-33

8.30 CAI Lesson Available 8-33

8.31 File Number Adjustment and Cancellation-BIRLS and CP&E Systems 8-33

8.32 Records That Cannot Be Adjusted Using the CNBR Command Must Be
Reported

to VA Central Office 8-34

**SUBCHAPTER VI. MASTER RECORD INQUIRY PROCEDURES**

8.33 Obtaining Master Record Inquiries on the Target System 8-34

8.34 Ready Screen Entries 8-34

8.35 Chapter 31 Master Record Status (M32 8-35

8.36 Chapter 31 Entitlement/Diagnostic (M33 8-39

8.37 Chapter 31 Entitlement History (M34 8-42

8.38 Chapter 31 Case Status/Counseling (M35 8-44

8.39 Chapter 31 Award Data (M36 8-45

8.40 Chapter 31 Dependency Data (M37 8-47

8.41 Chapter 31 Future Controls/Receivables (M38 8-47

**FIGURE**

8.01 Commands Authorized VR&C Staff Members 8-7

8.02 320 Screen - Chapter 31 Case Status/Control/Counseling 8-11

8.03 Completed 320 Screen 8-13

8.04 Case Status Future Control Requirements Summary 8-17

8.05 Control Codes 8-18

8.06 408 Screen-Chapter 31 Nonentry Into Training 8-23

8.07 Uses of the CNBR Command 8-31

**8-iv**

**June 4, 1987 M28-1, Part I**

**SUBCHAPTER 1. THE SYSTEM**

**8-01 TARGET SYSTEM IS ESSENTIAL TO CHAPTER 31 RECORD KEEPING**

Counseling psychologists, vocational rehabilitation specialists and VR&C
Division technicians and clerical personnel must have a working
knowledge of how VR&C program data are recorded and the VA automated
data processing schedules.

**8.02 SPECIFIC PROCESSING INSTRUCTIONS**

a\. VR&C Target Processing. The instructions for specific VR&C commands
and VR&C Target processing are contained in various subchapters of this
chapter:

**Target Process Subchapter**

\(1\) Case Status (CAST) Processing and Controls II

\(2\) VR&C Disallowance/Nonentry Into Training (CADJ/CAUT) III

Processing

\(3\) Counseling Data Updates II

\(4\) Master Record Corrections and Updates (CORR) IV

\(5\) Change/Delete Chapter 31 File Number (CNBR) V

\(6\) Inquiry Functions (MINQ/PINQ/SINQ/BINQ) VI

**b. Adjudication Target Processing**. The instructions for Adjudication
Target processing are found in DVB Manual M28-2, Adjudication Division
Procedures Under 38 U.S.C. chapter 31:

**Target Process Part, Chapter**

\(1\) Adjudication Chapter 31 Disallowance (CADJ/CAUT) II, 3

Processing

\(2\) Master Record Corrections and Updates (CORR) IV, 2

\(3\) Chapter 31 Eligibility and Entitlement Determinations II, l

\(4\) Change/Delete Chapter 31 File Number (CNBR) IV, 1

\(5\) Update Processing IV, 3

**8.03 CHAPTER 31 TARGET SYSTEM OVERVIEW**

The chapter 31 master record available on the Target System will combine
payment data from the VR&C payment system and statistical data from
entries made on the chapter 31 Target System.

**a. Online Target Processing**. Chapter 31 Target processing of entries
other than payment data is done on line using field station Target
terminals. Chapter 31 master record statistical data entries, updates to
existing chapter 31 master records, and new chapter 31 master records
will be processed using chapter 31 Target processing.

**8-1**

**M28-1, Part I June 4, 1987**

**b. VR&C Payment System Processing**. The VR&C payment system at the
Hines DPC processes subsistence allowance payments for VR&C program
participants. Procedures for the payment of subsistence awards will be
included in DVB Manual M28-2. Changes made to the chapter 31 payment
system will automatically update the corresponding chapter 31 master
records after each VR&C payment cycle.

**8.04 TARGET SYSTEM SECURITY**

Each person working with the Target System is responsible for Target
System security to protect both the data and the equipment.

**a.** **Paper Document Security**. It is important that each printed
document generated from the Target System be filed in the appropriate
folder or be disposed of in accordance with RCS VB-1, Part I.

**b. Target Access Card Security**. Each person authorized use of the
Target System is issued a TAC (Target access card) by the station Target
Security Officer. Under no circumstances will any person disclose his or
her password or allow any individual to use his or her TAC. VR&C staff
members will be issued TAC's in the 75XX series. The 75XX series card is
required to process certain Target actions which are restricted to VR&C
Division staff members. Therefore, any 75XX series cards issued to
people outside the VR&C Division should be collected to preserve the
integrity of the system.

**c. Sensitive Flies**. To protect the data in certain records, a Target
sensitive file will be created. For example, a VA employee would have a
sensitive file. Each record identified as a sensitive record is assigned
a level of access. The VR&C Officer will have access to sensitive files
at level "7" or below depending on local needs. In general, other VR&C
Division employees should not require sensitive file authority above
level "O" unless station management determines otherwise.

**d. Work-Study Students' Use of Target System**. Work-study personnel
may be authorized inquiry access to the Target System, but they may not
access sensitive files. They will not be granted non inquiry access nor
will they be given training in non inquiry Target functions.

**e. Further Information on Target Security**. More specific information
regarding Target security can be found in DVB Manual M23-1, part V,
chapter 6, and VA Manual MP-6, part XXV, supplement No. 3.1.

**8.05 AUTHORIZATION OF VR&C DIVISION TARGET COMMANDS**

**a. Requesting Appropriate Commands**. To obtain a TAC and to request
initial or amended command authorization, a VA Form 20-8824, Terminal
Access Request, must be completed. Detailed procedures for completion of
VA Form 20-8824 are contained in DVB Manual M23-1, part V, paragraph
6.05. Each individual authorized use of the Target System will be issued
a TAC. The authorized commands to be used by the VR&C Division are shown
in figure 8.01 at the end of this chapter. The commands authorized in
figure 8.01 are not mandatory, but are presented as a guide in the
assignment of commands to employees performing certain types of duties
in the VR&C Division. The commands authorized for each individual will
be only those required for the performance of official duties.

**b. Special Restrictions and Concerns**. No individual will be
authorized the use of both CEST and any of the CAUT commands. PEST and
CAUT may be authorized to the same individual, however, but only if the
CAUT command is restricted to authorization of chapter 31 nonpay
information. Care must be taken to insure that command authorizations
permit backup coverage of all VR&C work activities in the event the
primary person responsible for the Target function is not available.

**8.06 TARGET SYSTEM TRAINING**

**a. Purpose of CAI Lessons**. Before specific commands or functions can
be used efficiently, the individual operator must complete Target
training. Training for Target functions and Target commands will be
accomplished independently using the LERN command to access the CAI
(computer assisted instruction)

**8-2**

**June 4, 1987 M28-1, Part I**

lessons. These CAI lessons are designed to provide an individual,
step-by-step, and thorough training program. The CAI lessons are
intended to provide an introduction to Target System operations for
employees already trained in the substantive aspects of their positions.
An individual will train using only those lessons which relate to his or
her currently assigned duties.

**b. Uses and Limitations of CAI Lessons**. A detailed list of all CAI
lessons and an explanation of the procedures for taking CAI lessons are
given in the CAI system. The CAI lessons are not designed to be a
comprehensive manual dealing with every complex or unusual situation,
but they do provide basic knowledge to use Target commands and to
perform various Target functions. The CAI lessons are self-instructional
in nature and are designed so that each individual can proceed at his or
her own pace without other assistance. Should lesson difficulties arise,
the VR&C Target Liaison Representative or the Station Target Training
Coordinator will provide individual instruction. As CAI lessons are
completed, the individual should notify the VR&C Target Liaison
Representative or the Station Target Training Coordinator to begin
action to obtain or update command authority.

**c. Multiple Resources Available for Target Training**. All available
resources should be used when needed for Target training. This includes
the CAI lessons; TP 20-1, Target Training Program; locally developed
training packages; and other resources available through the station
Target Training Coordinator or Target Liaison Representative.

**8.07 TARGET LIAISON REPRESENTATIVE**

Each VR&C Division shall designate a person as the VR&C Target Liaison
Representative. The VR&C Target Liaison Representative will be assigned
specific duties:

**a. Liaison With Station Target Resources**. He or she will develop an
effective working relationship with the station Target Training
Coordinator and other station Target resource personnel. In many
regional offices, the station Target Training Coordinator has previously
organized a training program which may be useful in designing a training
program for the VR&C Division. Other Target resource personnel include
the Target Security Officer and the Supervisory Terminal Operator.

**b. Training Program**. He or she will organize and conduct a Target
training program for the VR&C Division. This will include:

**(1)** Reviewing the lesson sequencing for each trainee based on job
function;

**(2)** Developing a local record keeping system to monitor progress and
maintaining training records for

each trainee;

**(3)** Keeping the VR&C Officer apprised of each staff member's
progress;

**(4)** Providing individualized instruction where necessary; and

**(5)** Utilizing existing resources and developing local resources if
necessary to aid in the training program.

**c. Other Related Duties**. Other related duties will include:

**(1)** Arranging with the Target Security Officer for the assignment of
TAC's and assuring the Security Officer is informed when a VR&C staff
member has completed training for system command authorization or
updating;

**(2)** Participating in problem resolution involving VR&C Target issues
at the local level; and

**(3)** Maintaining close communication with appropriate Central Office
staff members regarding Target

implementation and problem resolution.

**8-3**

**M28-1, Part I June 4, 1987**

**8.08 VR&C OUTBASED LOCATIONS**

**a. Location With Target Equipment**. VR&C outbased locations which
have onsite Target capability will follow the Target processing
procedures specified in this manual. Training will be coordinated by the
field station VR&C Target Liaison Representative.

**b. Locations Without Target Equipment**. VR&C outbased locations which
do not have Target capability will use existing VA forms, with
appropriate headings added locally, to transmit data items to the
regional office for entry into the Target System. New forms will not be
developed locally for this activity. The outbased locations should
transmit this data as soon as possible. In no case should more than 10
workdays elapse from the date of case action to date of input into
Target. Data sheets and control code sheets should be disposed of by the
regional office after Target input action is completed. Local procedures
should also be developed for retrieval of Target information from the
regional office for use by the outbased location.

**c. Target Training for Personnel In Outbased Locations Without Target
Equipment**. Personnel in outbased locations which do not have Target
equipment must receive, at the minimum, orientation on Target input and
output functions during visits to the regional office. This Target
training will be coordinated by the VR&C Target Liaison Representative
at the field station.

**8.09 SCHEDULE OF OPERATIONS**

**a. Target Process Schedule**. VR&C Target input transactions are
processed on line. Changes to the master record are processed
immediately. In contrast, payment input transactions are processed on
paper documents and are sent to the Finance Section of the Hines DPC. At
the DPC, following review by Finance Section staff members, the
transactions are processed by the computer on a cycle basis. There are
normally six to nine cycles each month. The exact dates of cycle payment
processing and the resultant update to the chapter 31 master records are
shown on the Vocational Rehabilitation Chapter 31 Payment Schedule of
Operations, which is distributed to field stations monthly.

**b. Use of the Chapter 31 Payment Schedule of Operations**. Every
individual using Target in the VR&C Division and anyone using VR&C
reports or performing activities which result in a chapter 31
subsistence award should have ready access to the schedule of
operations. The following subparagraphs explain each column and footnote
on the Vocational Rehabilitation Chapter 31 Payment Schedule of
Operations. All time references are in central time.

**(1)** **Column 1** indicates the processing cycle number at the Hines
Data Processing Center. Cycles for a given month are numbered
sequentially beginning with 0 (zero). After the last cycle of the month,
the Hines DPC processes a number of EOM (end of month) computer runs to
change the payment system, such as to update master records to show
accounts receivable and reports of death.

**(2) Column 2** indicates the cutoff time and date for documents
processed in the payment system. Documents transmitted by the regional
offices and received in the Hines center by 10 a.m. central time on the
date shown in column 2 will be entered into the payment system during
the indicated cycle.

**(3) Column 3** provides the date and time the documents must go to the
Analysis and Control Division by 10 a.m. for review. The documents then
go to a contract vendor (by 12 noon) to have the data keypunched into a
computer tape. The vendor will have all the data on computer tape within
24 hours.

**(4) Column 4** shows the date and time the computer tape is returned
to the Hines center for transmission to the Philadelphia Data Processing
Center for processing by 9 a.m.

**(5) Column 5** indicates the date the Hines center transmits the
signed voucher to the Austin (TDC)

Treasury Disbursing Center. This is the same date the Philadelphia DPC
transmits the cycle paytapes to the Austin DPC. The Austin DPC delivers
the paytapes and vouchers to the Austin TDC.

**8-4**

**June 4, 1987 M28-1, Part 1**

**(6) Column 6** indicates the date and time that payment information
which has been updated for the cycle indicated is entered into the
chapter 31 Target master record.

**(7) Column 7** shows the anticipated date of the retroactive payment
checks which are prepared by the Austin TDC from the cycle payment tape.

**(8) End of Mouth Statistical Processing**. The next section of the
schedule of operations identifies the date the chapter 31 statistical
reports and future controls are processed for distribution to field
stations. Also shown are the end-of-day processing dates for the online
and payment updates used in generating the reports and the date the
reports and controls are scheduled to be mailed to the field stations.

**(9) Notes**. The notes section of the schedule of operations contains
specific data pertinent to the cycle information:

**(a) Stop, Suspend, and Hold Action Cutoff Date**. Stop and suspend
payment actions and hold check teletype notices are processed during EOM
processing. The first note indicates the date and time regional office
teletype Stop, Suspend, and Hold actions must reach the Hines DPC
Finance Section (35).

**(b) Recurring Payment Information**. The last cycle of the month
generates a recurring payment tape as well as a retroactive payment
tape. The second note indicates the check date for VR&C recurring
payments and the date the Austin TDC will release the recurring checks
to the post office.

**(c) Vendor Data Transcription**. The third note indicates the period
of time allowed for vendor data transcription.

**(d) Philadelphia DPC Master Record Update Transmissions**. The next
note indicates the time the Philadelphia DPC must transmit the payment
update to the Hines DPC for subsequent updating of the chapter 31 master
records.

**(10) Schedule of Operations Distribution**. The final portion of the
schedule indicates the distribution of the schedule of operations.

**8.10 CHAPTER 31 TRANSACTION TYPES**

The transaction types listed below will appear on the M32 screen in the
STAT or PAY field under LAST ACTIVITY.

**a. Statistical Master Record Transaction Types**

**Transaction Type Transaction Description**

02S Correction to record

03R Eligibility determination

26D Delete file number from the chapter 31 master record system

26R Change of fide number in the chapter 31 master record system

27Z Disallowance

80R Case status update

**8-5**

**M28-1, Part I June 4, 1987**

**Transaction Type Transaction Description**

81R Counseling data update

85R Case status or employee future control, change

or deletion

88R Update of eligibility and entitlement data

90 Computer system-generated update

**b. Pay Transactions Types**

**Transaction Type Transaction Description**

04 Establish or increase accounts receivable

05 Lump-sum payment

07 Reduce or liquidate accounts receivable

10 Suspend payment

11 Original or reopened award

13 Amend award

18 Establish or Change 1n amount of recurring deduction

21 Returned check

22 Change of address or name

23 Change of award station

25 Change of stub name

70 End-of-month payment purge of terminated pay

records

98 Future date rate change

XXX Payment record no longer held in the chapter 31

payment system

**8.11 MANILA REGIONAL OFFICE**

The Target processing procedures described in this and other chapters of
this manual do not apply to the Manila regional office.

**8-6**

June 4, 1987 M28-1, Part I

+------------+------+-------+--------+------+-------+------+--------+
|            | **VR | **CO  | *      | *    | **PSY | **   | **CL   |
|            | &C** | UN-** | *VOC** | *PSY | CH-** | SECR | ERI-** |
|            |      |       |        | CH** |       | E-** |        |
|            | **O  | **SEL | **R    |      | **O   |      | *      |
|            | FF** | ING** | EHAB** | *    | ME-** | **TA | *CAL** |
|            |      |       |        | *TEC |       | RY** |        |
|            | **CE | *     | **     | H/** | **TRI |      | **P    |
|            | RS** | *PSYC | SPE-** |      | STS** |      | OSI-** |
|            |      | HO-** |        | **AI |       |      |        |
|            |      |       | **CIA  | DS** |       |      | **T    |
|            |      | *     | LIST** |      |       |      | IONS** |
|            |      | *LOGI |        |      |       |      |        |
|            |      | STS** |        |      |       |      |        |
+------------+------+-------+--------+------+-------+------+--------+

**COMMANDS**

BINQ x x x x x y x

BUPD

CADD x x x x y y x

CADJ (C&P)

CADJ (EDU\*) x x x

CAST(CH31) x x x x

CAUT(C&P)

CAUT(EDU\*) x x x

CDAT x x x x y

CDEV x x x x x

CERT

CEST x

CFID

CNAM

CNBR (CH31) x y y y

CORR x x x x

DISP x x x y y y x

DUPC

FNOD

HELP

MINQ x x x x x y x

NOES

PCAN x x x y y y x

PCHG x x x y y y x

PCLR x x x y y y x

PEST x x x y y y x

PINQ x x x x x y y

QCRE x y y y y

RESU(C&P)

RESU(EDU)

SINQ x x x x x y x

STOP(C&P)

STOP(EDU)

SUSP(C&P)

SUSP(EDU)

WIPP x x x y y y y

PENF x x x y y y y

VARM x x x y y

*Command authorization for VR&C staff positions not covered by one of
the listed titles will be determined locally with approval by the
regional office Director.*

*\*Education CADJ and CAUT Commands for VR&C personnel are limited to
chapter 31 functions.*

*X**Command is authorized for personnel fully trained in job
functions.*

*Y**Command is limited to the minimum number of personnel required to
process the workload.*

**Figure 8.01. Commands Authorized VR&C Staff Members**

**8-7**

**M28-1, Part I June 4, 1987**

**8.12 COMMON TARGET COMMANDS, FUNCTIONS, AND PROCESSING PROCEDURES
WHICH MAY BE USED FOR CHAPTER 31**

**a. Commands and Functions**. VR&C Staff members are authorized use of
many Target commands and functions (see fig. 8.01). The following Target
commands and functions which are currently used by other systems will be
used in chapter 31 application processing:

**(1) CEST (Claims Establishment)**. An original pending issue will be
established in the PIF (Pending Issue File) when either no chapter 3 1
master record exists or when the master record type is S or J. A pending
issue under end product 295 must be established before an application
allowance or disallowance may be processed.

**(2) PEST (Pending Issue Establishment)**. This command is used to
establish a pending issue on the PIF when a type A, E or I chapter 31
master record exists. It will generally reflect only those fields
entered by the operator and held on the PIF. Therefore, in contrast to
PINQ (Pending Issue Inquiry) displays for C&P and other education
benefits, fields not changed by the operator will not be displayed, with
two exceptions. Service data will always be displayed. The VA training
history will also be displayed if any field in this training history is
changed.

**(3) CDEV (Claims Development)**. This command accesses screens to
generate letters requesting specific types of evidence to support a
claim. Currently, the 201, 202, 204, and 205 development screens are
available for chapter 31 cases.

**(4) CDAT (Claims Data Entry)**. This command allows the operator to
enter all the data required to determine eligibility and entitlement to
chapter 31 benefits. The CDAT command may be used to access 300-level
screens as well as all those screens from a lower level. For example, an
adjudicator using the CDAT command may access appropriate 200 or 300
series screens, but cannot access the screen 408 (Chapter 31 Nonentry
Into Training). The CDAT command may also be used to update existing
master record entries found in any enterable field on the 331, 332, and
333 screens. An update would be generated whenever the APPLICATION field
on these screens is left blank.

**(5) CADJ (Claims Adjudication)**. This command allows the operator to
enter all 200, 300 and 400 level screens appropriate for chapter 31
benefits. It allows for chapter 31 data entry for either basic
eligibility determinations or disallowances. The CADJ command may be
used to update master record fields in the same manner as the CDAT
command.

**(6) GAP (Generate and Print)**. This command is used when benefits are
disallowed. GAP directs the Target System to generate and print
disallowance data based upon entries made on the supporting screens. For
example, GAP is entered in the NEXT SCREEN field of the 408 screen to
generate a disallowance of a chapter 31 claim. A favorable chapter 31
eligibility determination, which will be used to refer claimants to the
VR&C Division, is generated via the new GED (Generate Eligibility
Determination) function.

**(7) CAUT (Claims Authorization)**. Basic eligibility determinations
and disallowances prepared under CDAT or CADJ that have been GED'D or
GAP'D are authorized or canceled using this command. This is the last
action performed by the operator before the basic eligibility
determination or disallowance transaction is sent for processing into
the Target chapter 31 master record.

**(8) CORR (Corrections)**. Chapter 31 master record corrections may be
made using Target processing under the CORR command. The number of
fields which can be corrected on the Target System using this command,
however, is limited.

**b. General Target Processing Procedures Apply to Chapter 31**. Many
claims processing steps, commands, and screens used for other benefit
programs are also used for chapter 31:

**8-8**

**October 29, 1990 M28-1, Part I**

**Change 1**

**Commands**

**Claims Processing Steps Used Screens Used**

\(1\) Claim Establishment CEST/PEST Ready Screen

BIRLS Data Record CDAT 101 BIRLS Data

Pending EPC Set Up CADJ 102 Claim Establish or

Claimant's Address Entered\* 103 Pending Issue

Date of Claim Recorded Control

Routed to Next Step Establish

S99 Disposition

Also accessed are:

P0l

S02

\(2\) Claims Development and Request for CDEV Ready Screen

Necessary Evidence 200 Development

Screen Selection

201 3101 Data Selection

202 Request for Military/

Medical Data

204 Dependency Data

205 Education

\(3\) Data Entry/Adjudicative Action CDAT/CADJ Ready Screen

Enter Basic Eligibility and Rating Data 200-series Screens

Enter Disallowance Data 300-series Screens

GED/GAP 400-series Screens

Also accessed:

S02

S99

\(4\) Authorization CAUT Ready Screen

501 Authorization

S99

Also accessed:

S02

103 if establishing new issue

*\***NOTE**- The claimant's address may only be entered on the 102
screen during original claim processing, Following completion of
processing the original claim, only pay transactions may be used to
update and change addresses.*

**8-9**

**M28-1, Part I October 29, 1990**

**Change 1**

**SUBCHAPTER 11. THE 320 SCREEN**

**8.13 GENERAL**

From the time VA receives an application for chapter 31 benefits to the
time the veteran leaves the program, the veteran advances through a
series of case statuses. These statuses indicate the veteran's current
level of participation in the chapter 3 1 program. VR&C staff members
use the Target 320 or CAST screen, CH31 CASE STATUS/CONTROL/COUNSELING,
to track each veteran's movement through the chapter 31 case status
system. In addition to recording case status information, VR&C personnel
may establish future controls to review a veteran's progress and input
counseling data. From the 320 screen, the case manager can also access
the 408 screen for disallowance processing by entering 408 in the NEXT
SCREEN field. Although VR&C staff members will most frequently use the
320 screen, employees from other divisions-such as Adjudication and
Finance-may use the Future Employee Controls section of the 320 screen.
These groups may use the screen to diary future employee control dates
which are not related to changes in the veteran's case status. Figure
8.02 provides a sample of the Target 320 screen.

**8.14 PROCESSING OVERVIEW**

**a. 320 Screen Access**. Use the CAST (Case Status) command to access
the 320 screen from the Ready Screen. Minimal Ready Screen entries are
the command CAST, the operator's password, and the veteran's file
number. If required data is missing or entered incorrectly, the Ready
screen will display an error message.

**b. PIF (Pending Issue File) Search**. When VR&C staff members use the
CAST command, Target will search the PIF for a matching file number. If
a matching pending issue exists, the Payee Selection Screen (S02) will
appear. The S02 screen will display all the pending issues associated
with that particular file number. The VR&C operator may then decide
which, if any, of the control codes to designate for adjustment via the
320 screen. If the operator selects a control code from the S02 screen
by marking an "X" beside the desired control code, the top of the 320
screen will display that same control code. If the operator does not
select a control code from the S02 screen, then the CONTROL CODE field
on the 320 screen will be blank. NOTE: Only VR&C staff members can
access PIF using the CAST command.

**c. Master Record Search**. When either a non-VR&C employee uses the
CAST command or if there is not a pending issue, the system will check
for a chapter 31 MR (master record) with a matching file number. If a
matching MR is found, the 320 screen will appear, with the Date, File
Number, Payee Number, Stub Name, and any case status data, future
controls, counseling data, and employee controls already part of the
chapter 31 MR. If this search reveals no matching MR, CAST processing
cannot continue and the Ready screen will display the following message:

CH31 RECORD NOT FOUND-START NEW COMMAND WITH PA2 KEY.

**8.15 THE 320 SCREEN-CASE STATUS/CONTROL/COUNSELING**

**a. Access to 320 Screen Data Entry Fields**. There are 5 types of data
on the 320 screen: case status data, case status future controls,
counseling data, future employee controls, and control code issues/next
screen request. VR&C staff members may access all these data fields on
the 320 screen. Employees from other divisions may only access the
Future Employee Controls of the 320 screen.

**b. Case Status Data**. There are 9 chapter 31 case status categories:
Applicant, Evaluation and Planning, Extended Evaluation, Independent
Living, Rehabilitation to the Point of Employability, Employment
Services, Rehabilitated, Interrupted, and Discontinued. Each of these
statuses appears on a specific line on the 320 screen. Data recorded for
each case status applicable to the veteran's program include:

**(1)** The date the veteran's case was assigned to the status (Begin
Date);

2.  The date the veteran's case exited the status (End Date);

**(3)** The reason for exiting the status (Reason);

**8-10**

**October 29, 1990 M28-1, Part I**

**Change 1**

**(4)** The time spent in the status (Elapsed Days, which are
automatically generated by the system); and

**(5)** The desired case review date and the employee number of the
operator entering a future control for a case status which is open, that
is, one which has a begin date, but no end date. Under certain
conditions, the system may also generate a future control date.

**c. Priority Updating of Case Status Fields**. To reflect the veteran's
actual progress or status in the program, the VR&C Division must update
the Target case status categories (using the date of change) no later
than 2 workdays after the program status change. Outbased locations not
having Target equipment must mail or call in requests for Target update
within 2 workdays after the program status changes. No more than 2
workdays may elapse between receipt of outbased change data in the VR&C
Division and entry of the data into the Target System. Employees on
travel must enter their Target work activity within 10 workdays of their
return to the regional office.

**d. Target Case Status Categories and Reasons**. The required use of
the Target case status categories, changes to the statuses, begin dates,
end dates, and reason codes are shown in Table 7.01.

**e. Open/Closed Case Status**. A veteran's case status may be either
open or closed. An open case status has only a begin date and reflects
the veteran's current status in the chapter 31 program. A closed case
status has a begin date, end date and ending reason code. When a case
status is closed, the Target System automatically calculates the number
of elapsed days in that status and displays this number on the 320
screen. In a single transaction on the 320 screen, an operator can
update-that is, open, close, or change-more than one case status. In any
event, time periods for case statuses may not overlap and only one open
case status is permitted. There must always be an open case status for
each chapter 31 case. Figure 8.03 shows a 320 screen following data
entry.

**f. Future Control Data**. Future controls consist of the dates and
employee identifications related to future reviews of the veteran's case
status. This data is designed to assist in case management. There are
two kinds of future controls: case status and employee.

**(1) Case Status Future Controls**. Case Status Future Controls on the
320 screen consist of a future review date on the open case status and
an employee number identifying the VR&C employee responsible for
reviewing the veteran's case. The future control date is system
generated at 180 days initially for the following statuses: 01, 02, 03,
and 08. (For the case status associated with each of these codes, as
well as a summary of future control entry requirements, see fig. 8.04.)
Thus an operator need enter only an employee number for these statuses.
An operator must determine and enter a future control date for the
following statuses: 04, 05, and 06. An operator entered date may range
from 45 days to 2 years in the future. There must be a future control
date and employee number for an open case status, except for statuses 07
and 09 for which future control data are optional. A future control on
status 07 or 09 must contain both a future date and an employee number.

**(2) Future Employee Controls**. The Future Employee Controls section
is located in the lower right quarter of the 320 screen. Both VR&C and
non-VR&C employees may use these controls. This is the only section of
the 320 screen accessible to non-VR&C employees. The control signifies
that the employee associated with the control needs to review the case
on the established date. However, these controls are not necessarily
associated with actions related to changes in the veteran's case status.
To establish a future employee control, the operator must enter a valid
date and employee code. To be valid, a date must be in the format
MM-DD-YY and must be at least 45 days, but no more than 2 years, from
the current date. A case may contain up to nine future employee
controls, provided the employee identification numbers are different.

**(3) Revision Capability Restricted by Division**. Each division's
employees can modify or delete future employee controls associated with
their own division, but cannot change or delete employee controls
associated with other divisions. Division controls may be deleted or
modified by any operator within the division, as needed, no matter who
initially established the control. An operator can modify a control by
changing the date or employee code. To eliminate a control, the operator
must delete both fields.

**8-11**

**M28-1, Part I October 29, 1990**

**Change 1**

**(4) Selection of Control Dates**. The Target System reviews future
control dates only during end-of-month processing. The actual processing
date is shown on the monthly Vocational Rehabilitation Chapter 31
Payment Schedule of Operations. At that time, the designated date of
each future control is examined and those which will come due during the
next month are selected for notice. For example, end-of-month April
selects control dates of May I through 31 of the current year. The
resultant field notices would then be issued for delivery about the
first day of the month after the report run. Therefore, in establishing
operator entered future controls, the operator must remember that the
expected computer notice will be received the first day in the month
fixed in the control date. First-of-the-month delivery will ensure
timely action on the matured control.

**(5) One-Time Notice for Certain Cases Before Deletion From the Chapter
31 Master Record**. The notice for a future employee control (COIN TAR
6014, Chapter 31 Matured Employee Controls By Division) or an operator
entered case status future control on statuses 07 and 09 (COIN TAR 6013,
Future Controls For Open Case Statuses) will be a one-time report
generated by the employee code associated with the control. After the
report is generated, the control will be automatically canceled and the
LAST ACTIVITY STAT fields will be updated to reflect transaction 90, the
date of processing, and the time as 1200.

**(6) Recurring Notices for Certain Cases**. Recurring notices are
system-generated at 60-day intervals for statuses 01, 02, and 06, and at
120-day intervals for statuses 03, 04, 05, and 08. These notices are
reported on COIN TAR 6013 in a listing format by employee number, case
status, claim number, stub name, case status begin date, number of days
in status, last activity type and date, award station, and CER folder
station. The report notifies the case manager of cases requiring review
and assures that cases in these statuses are periodically brought to the
attention of the case manager and VR&C Officer. This will continue until
the case status is closed and the future control data (both date and
employee code) are erased.

**(7) VR&C Division Routes Employee Future Control Notices**. Notices of
employee future controls maturing during the upcoming month are part of
the chapter 31 reports package delivered on the first of the month to
the VR&C Division. VR&C personnel must sort the employee future control
report (COIN TAR 6014) for routing within the VR&C Division and to other
divisions. VR&C officers are responsible for assuring that these reports
are distributed timely and that appropriate follow-up action is taken by
their staff.

**(8) M35 (CH31 Case Status/Future Control) Inquiry Screen**. This MR
inquiry screen displays in chronological order by employee code all
future controls established in the chapter 31 MR. The MINQ (Master
Record Inquiry) command will access the M35 when benefit type CH31 or
the specific screen number M35 is entered on the Ready screen.

**(9) Modify or Delete Future Controls**. Operator input cannot change
system-generated control dates directly. The case status must be closed
or the begin date must be modified to change the future control already
established. Operator entered controls, however, may be adjusted by
entries to the date or employee code fields.

**g. Counseling Information**

**(1) General**. The counseling data portion of the 320 screen records
information related to the rehabilitation program goal. The counseling
data fields include:

**(2) CER Folder**. As soon as the VR&C Division has established a CER
(Counseling/Evaluation/

Rehabilitation) folder, enter in the CER FOLDER field the 3-digit
designation of the station having jurisdiction of the CER folder. When a
CER folder is transferred, an operator at the sending station should
enter the number of the station receiving the CER folder.

**8-12**

**October 29, 1990 M28-1, Part I**

**Change 1**

**(3) IWRP (Individualized Written Rehabilitation Plan) Code**. The IWRP
CODE field has a 3-digit entry. In IWRP CODE, enter the first one, two
or three digits of the code shown on VA Form 28-8872, Rehabilitation
Plan, item 7, Program Goal. If only the first one or two digits of the
code for the program goal have been identified, enter these digits in
the first one or two positions, respectively, of the field. Amend the
entry to a 3-digit code as soon as this code is determined. An entry in
this field is required to move a veteran out of Evaluation and Planning
status with ending reason codes 05 or 07. If the program goal changes
during training, update this field. Similarly, update this field when
the veteran is in Employment Services status and it becomes apparent
that the veteran's employment goal will differ from the IWRP code in the
veteran's chapter 31 MR.

**(4) Employment Code**. In the EMPLOYMENT CODE field, enter the first 3
digits of the DOT (Dictionary of Occupational Titles) employment code of
the veteran's actual employment position when the veteran is declared
Rehabilitated. This field requires an entry any time Employment Services
status closes with ending reason code 22, 23, or 25 or the veteran
enters Discontinued status when Interrupted status closes under ending
reason 35.

**(5) Pre-Chapter 31 Salary**. The PRE CH31 SALARY field requires a
4-digit entry. Enter the monthly salary or equivalent (at the time the
entitlement decision is made) in this field upon completion of the
initial evaluation. Enter only whole dollar figures of the veteran's
monthly wage with no dollar sign (\$). Enter leading zeros to fill the
field.

**(6) Post-Chapter 31 Salary**. Once the veteran has completed a program
of CH31 services and has obtained employment, enter the veteran's
monthly salary in the POST CH31 SALARY field. Enter whole dollar figures
with no dollar sign (\$). Enter leading zeros to fill the field. A
positive entry other than zeros in this field is required to place a
veteran in Rehabilitated status from Employment Services status under
ending reasons 22, 23, or 25 or to move the veteran from Interrupted
status to Discontinued status with ending reason 35.

**(7) Serious Employment Handicap**. Entry in the SERIOUS EMPLOYMENT
HANDICAP field is required to indicate whether or not a serious
employment handicap exists. If the counseling psychologist has
determined that the veteran has a serious employment handicap, enter "Y"
in this field. Conversely, if the veteran does not have a serious
employment handicap, enter "N." Should the veteran's employment handicap
status change during the course of his/her program, update this field
accordingly.

**h. Control Code Issues and Next Screen Processing**.

**(1) General**. The last section of the 320 screen provides for
establishing, clearing, and canceling control codes and for next screen
processing.

**(2) Control Codes**. Control codes in the chapter 31 program identify
work processes and control workflow. Control codes may be established,
cleared, or canceled on the CAST 320 screen. The VR&C Division uses the
following six control codes, which are also summarized in figure 8.05:

**(a) Control Code 707: Motivation and Outreach --Rescinded per M28,
Part I, Chapters 1-4, dated 3/14/06**

~~**[1]{.underline}. Establishment**. The Adjudication Division
establishes a control code 707 as a future diary control for the VR&C
Division to motivate the veteran when there is potential eligibility for
vocational rehabilitation and a Target control can be used.~~

~~**[2]{.underline}. Final Disposition**. Clear this control code using
the PCLR (clear pending issue) field following completion of all
procedures described in M28-1, Part I, chapter 12 regarding motivation
and outreach activities.~~

**(b) Control Code 717: Vocational/Educational Counseling**

**8-13**

**M28-1, Part I October 29, 1990**

**Change 1**

**[1]{.underline}. Establishment**. The VR&C Division establishes
control code 717 at the time it receives a counseling referral. This
control code creates a pending issue control for counseling activity
with individuals under all VA education benefit programs other than
chapters 1 5 and 3 1. As an exception, dependents under chapter 35 who
are determined to be in need of SRT (Special Restorative Training) or
SVT (Specialized Vocational Training) will be placed under control codes
appropriate to chapter 3 1.

**[2]{.underline}. Final Disposition**. Cancel this control code using
the PCAN (Cancel Pending Issue) field when an eligible person fails to
keep scheduled appointments. Clear this control code using PCLR when the
VR&C Division completes all scheduled vocational/educational counseling
activity. Do not PCLR a 717 for each counseling session.

**(c) Control Code 718: Rehabilitation Assistance Visits**

**[1]{.underline}. Establishment**. Control code 718 establishes a
future diary control for planned interactions with a veteran or eligible
beneficiary under chapters 15, 31, and 35 (SRT or SVT only). Stations
may elect to use alternative methods for controlling for future
supervisory assistance visits. For example, stations may use the 320
CAST screen or a local diary system.

**[2]{.underline}. Final Disposition**. Clear the 718 using PCLR when
planned activity is completed and documented. If the planned activity is
no longer necessary, cancel the 718 using PCAN.

\(d\) Control Code 719: Evaluation and Planning Process

**[1]{.underline} Establishment**. The Adjudication Division
automatically establishes control code 719 as a pending issue when it
completes eligibility processing for a chapter 31 applicant. This
control code will remain pending until all necessary initial
rehabilitation evaluation or reevaluation counseling planning activity
is completed.

**[2]{.underline}. Final Disposition**. Clear control code 719 using
PCLR when required counseling evaluation and planning activities are
completed and documented. Cancel control code 719 using PCAN if the
veteran fails to pursue the claim and all efforts to encourage
participation in the evaluation and planning process fail.

**(e) Control Code: 768 Appellate Activity**

**[1]{.underline}. Establishment**. When the VR&C Division accepts the
claimant's written communication as a notice of disagreement or when the
claimant files a substantive appeal, the VR&C Division will establish a
pending issue under control code 768.

**[2.]{.underline} Final Disposition**. Clear the 768 control code using
PCLR when the VR&C Division releases the statement of the case or the
issue in contention is resolved either by the claimant withdrawing the
notice of disagreement or by the VR&C Division granting the benefit
sought.

**(f) Control Code 769: Contract Services**

**[1]{.underline} Establishment**. Establish a control Code 769 as a
pending issue for cases referred for contract services to ensure a
future review of the services for quality and compliance with the
contract.

**[2]{.underline}. Final Disposition**. Clear the control code 769 using
PCLR following the review of the completed contract service activity.

**(3) Control Code Selection from the Pending Issue File**. When
accessing the 320 screen, the Target System will display the S02 screen
(Payee Selection Screen) if one or more PIF issues exist. The S02 screen
will give the case manager the ability to associate entries on the 320
screen with the appropriate control code. The case manager may either
cancel under PCAN or clear under PCLR the control code selected from the
S02 screen and displayed in the CONTROL CODE field. Control codes
specified in the PCAN or PCLR fields will

**8-14**

**October 29, 1990 M28-1, Part I**

**Change 1**

be canceled or cleared respectively from the PIF when WIP (Work in
Process) program runs each night. If the operator did not select a
control code, but wants to establish one as a pending issue, he or she
may enter a control code in the PEST field. This entry will cause a
default to PEST (pending issue establishment) processing. The 320 screen
can process only one control code. Therefore, the operator cannot enter
a control code in the PEST field if the top of the 320 screen already
displays another control code.

**(4) VR&C Disallowance Processing**. Following selection of a control
code from the S02 screen and its display in the CONTROL CODE field on
the 320 screen, the operator can request the 408 screen for VR&C
disallowance processing. To request disallowance processing, enter 408
in the NEXT SCREEN field. To access disallowance processing, the PEST,
PCLR, and PCAN fields on the 320 screen must be blank. To proceed with
disallowance processing, however, the VR&C operator must have CADJ
(Claims Adjudication) command authority. Otherwise, Target will display
the message

DISALLOWANCE PROCESSING NOT AUTHORIZED.

Once the 408 screen is displayed, the operator will follow application
processing procedures to check for an E or I type chapter 31 MR. Other
existing 408 screen edits and messages will be used. After entry of data
on the 408 screen, a VR&C operator with CAUT authority can access the
501 screen via the NEXT SCREEN field.

**i. Employee Responsible Code**. The EMPLOYEE RESPONSIBLE field at the
top of the 320 screen is a 4-position number code which identifies the
VR&C case manager. The MR will retain this code. A VR&C operator can
update this field, however, in conjunction with or independent of any
other changes on the 320 screen. When the VR&C division receives a case,
the division must assign the case an employee responsible code.
Consequently, unless the Target System displays a code from the MR, the
VR&C operator must make an entry in the EMPLOYEE RESPONSIBLE field on
the 320 screen for processing to occur. If a non-VR&C employee accesses
the screen, the screen will show the VR&C employee responsible for that
veteran's case. When the Target System automatically establishes
Applicant case status following Adjudication application processing,
this field will not contain an entry. The VR&C operator who initially
accesses this screen will have to enter the employee responsible code
with any input on this screen. Following designation of the employee
responsible, the MR will retain the code for the field employee
responsible regardless of other screen activity, unless a VR&C employee
changes the EMPLOYEE RESPONSIBLE field. The regional office will assign
the actual employee responsible codes using the following format:

First Digit: 8 (VR&C Division designation)

Second Digit: 1 (Regional Office Location)

2 (First Outbased Location)

3 (Second Outbased Location), etc.;

Third and Fourth Digits: 00-19 (Individual Counseling

Psychologist)

20-39 (Individual Vocational

Rehabilitation Specialists)

40-59 (Individual Clerks and

Psychological Technicians)

**j. Processing Capability**

**(1) Online Updating**. Once 320 screen processing is complete, an 80R
case status transaction will immediately update the associated chapter
31 MR, based on the entries on the 320 screen. This transaction overlays
the existing MR data with the newly input data and also updates the MR
fields LAST ACTIVITY DATE and LAST ACTIVITY TIME with the date and time
of the overlay. The LAST ACTIVITY TRANS TYPE field will show 80R.

**8-15**

**M28-1, Part I October 29, 1990**

**Change 1**

**(2) Automatic TR 80R Generated**. Applicant eligibility processing by
the Adjudication Division on the 431 screen can also indirectly generate
updates to the data displayed on the 320 screen. If a veteran is found
eligible for chapter 31 benefits and a GED (Generate Eligibility
Determination) action is completed, the Target System will automatically
open Applicant case status. Similarly, a determination to disallow will
automatically set up a closed Applicant case status with ending reason
code 01. This processing will close any open case status for movement to
the Applicant case status.

**k. Target System Edits**. All data entered on the 320 screen undergoes
a series of edits for accuracy and consistency. If Target discovers
errors, the operator must correct the error conditions before processing
can continue. The fields that contain the errors will flash on the
screen. Once the screen is error-free, Target formats a transaction,
updating the chapter 31 MR by overlaying the case status, counseling,
and/or future control fields with the newly entered data.

**1. Summary**

**(1)** VR&C Division. The 320 screen allows VR&C Division employees to:

**(a)** Enter the VR&C employee responsible code;

**(b)** Enter case status dates and ending reasons;

**(c)** Enter a case status future control date;

**(d)** Enter an associated employee code for both operator-entered and
system-generated case status future control dates for each open case
status;

**(e)** Enter counseling data;

**(f)** Enter future employee controls by employee code;

**(g)** Establish, clear, or cancel control codes in conjunction with
CAST processing; and

**(h)** Access the 408 screen for VR&C disallowance processing.

**(2)** Other Divisions. The 320 screen allows employees in other
divisions to enter future employee controls by employee code.

**8-16**

**October 29, 1990 M28-1, Part I**

**Change 1**

320 CH31 CASE STATUS/CONTROL/COUNSELING 06-02-90

FILE NUMBER 99-555-666 CONTROL CODE 718 NAME J R HILL

EMPLOYEE RESPONSIBLE 8100

BEGIN DATE END DATE RSN ELAPSED DAYS FUTURE CONTROL

APPLICANT 04-01-90 04-02-90 02 0002

EVAL/PLAN 04-02-90 06-01-90 05 0061

EXTEND EVAL

INDEPEND LIVE

REHAB TO EMP 06-01-90 12-15-90 8100

EMP SERVICES

REHABILITATED

INTERRUPTED

DISCONTINUED

CER FOLDER 452 FUTURE EMPLOYEE CONTROLS

IWRP CODE 117 04-01-91 8001 06-20-90 8100

EMP CODE

PRE CH31 SALARY 0800

POST CH31 SALARY

SER EMP HDCP Y

PEST PCLR PCAN NEXT SCREEN

DSL,320

**Figure 8.02. 320 Screen Chapter 31 Case**

**Status/Control/Counseling**

320 CH31 CASE STATUS/CONTROL/COUNSELING 06-02-90

FILE NUMBER CONTROL CODE NAME

EMPLOYEE RESPONSIBLE

BEGIN DATE END DATE RSN ELAPSED DAYS FUTURE CONTROL

APPLICANT

EVAL/PLAN

EXTEND EVAL

INDEPEND LIVE

REHAB TO EMP

EMP SERVICES

REHABILITATED

INTERRUPTED

DISCONTINUED

CER FOLDER FUTURE EMPLOYEE CONTROLS

IWRP CODE

EMP CODE

PRE CH31 SALARY

POST CH31 SALARY

SER EMP HDCP

PEST PCLR PCAN NEXT SCREEN

DSL,320

**Figure 8.03. Completed 320 Screen**

**8-17**

**M28-1, Part I October 29, 1990**

**Change 1**

**CASE STATUS CASE STATUS FUTURE CONTROL**

**CATEGORY CODE REQUIREMENTS**

APPLICANT 01 Future Date Is System

Generated; Operator

Must Enter Employee

Number

EVALUATION 02 Future Date Is System

AND PLANNING Generated; Operator

Must Enter Employee

Number

EXTENDED EVALUATION 03 Future Date Is System

Generated; Operator

Must Enter Employee

Number

INDEPENDENT LIVING 04 Operator Must Enter

Future Date and

Employee Number

REHABILITATION TO THE 05 Operator Must Enter

POINT OF EMPLOYABILITY Future Date and

Employee Number

EMPLOYMENT SERVICES 06 Operator Must Enter

Future Date and

Employee Number

REHABILITATED 07 (Optional) Operator

May Enter Future Date

and Employee Number

INTERRUPTED 08 Future Date Is System

Generated; Operator

Must Enter Employee

Number

DISCONTINUED 09 (Optional) Operator

May Enter Future Date

and Employee Number

**Figure 8.04. Case Status Future Control Requirements Summary**

**8-18**

**October 29, 1990 M28-1, Part I**

**Change 1**

**CONTROL CODE DESCRIPTION**

707 Motivation and Outreach Activities

717 Vocational and Educational Counseling with

Individuals Other Than Claimants Under Chapter 15,

31, or 35 (SVT or SRT only)

718 Rehabilitation Assistance Visits

**Future Diary Controls for Control Code 718:**

**Desired Control Action Reason Code**

Motivation Contact 30

Pending Induction 31

Assistance Visit 32

IWRP Review 33

Post-employment Followup 34

719 Evaluation and Planning Process

768 Appellate Activity

769 Contract Services

**Figure 8.05. Control Code Summary**

**SUBCHAPTER Ill. DISALLOWANCE PROCESSING**

**8.16 SCOPE**

This subchapter provides instructions for the processing of chapter 31
disallowances. The Target screen 408, Chapter 31 Nonentry into Training,
is used to record those disallowances. Figure 8.06 provides a sample of
the Target screen 408.

**8.17 SUBSTANTIVE DISALLOWANCE BASED ON DETERMINATION OF
NONENTITLEMENT**

Screen 408 will be completed when it is determined from the evidence of
record that a veteran does not meet requirements for entitlement. A
formal disallowance will be required in these cases upon denial of a
current claim.

**a. Initial Claim**. Screen 408 will be completed to record in the
claimant's master record the formal disallowance of an initial claim in
the following instances.

**(1)** Disallowance of a claim under all applicable laws; or

**(2)** Upon withdrawal of an original claim.

**b. Reopened Claim**. Screen 408 will also be used to record
disallowances for reopened claims for the same reasons an initial claim
may be denied.

\[***NOTE: Pages 8-20 through 8-22 are blank.\]* 8-19**

**June 4, 1987 M28-1, Part I**

320 CH31 CASE STATUS/CONTROL/COUNSELING 06-02-90

FILE NUMBER CONTROL CODE NAME

EMPLOYEE RESPONSIBLE

BEGIN DATE END DATE RSN ELAPSED DAYS FUTURE CONTROL

APPLICATION

EVAL/PLAN

EXTEND EVAL

INDEPEND LIVE

REHAB TO EMP

EMP SERVICES

REHABILITATED

INTERRUPTED

DISCONTINUED

INACTIVE

CER FOLDER LOC FUTURE EMPLOYEE CONTROLS

DOT CODE IWRP/EMP

SAL PRE-TRG/POST-TRG

ENTITLE EXT

SER EMP HDCP

PEST PCLR PCAN NEXT SCREEN

**Figure 8.06. 408 ScreenChapter 31**

**Nonentry Into Training**

**8-23**

**M28-1, Part I June 4, 1987**

**8.18 PROCESSING THE DISALLOWANCE ON THE 408 SCREEN**

**a. VR&C Reasons for Disallowance**. Enter an "X" in only one of the
fields in the right column

on the 408 screen to show the specific reason for disallowance. If there
are two or more reasons for disallowance, enter only the one which takes
precedence. When code 29, Other, is selected, an explanation must be
written in the REMARKS field. This explanation may be up to 70
characters in length. Do not make any entries in the left column, which
is reserved for Adjudication Division disallowances. (For a more
complete explanation of the reasons for disallowance, see ch. 3, par.
3.05.)

**b. Authorization**. The disallowance printout which is generated
following GAP processing will be signed by the preparing CP or VRS and
an authorizer. The authorizer will also complete the 501 screen.

**c. Reprocessing a Disallowance**. If, on review or reconsideration,
the basis for the allowance has changed, the disallowance will be
reprocessed.

**8.19 CIRCUMSTANCES WHEN 408 SCREEN WILL NOT BE COMPLETED FOR A
DISALLOWANCE**

The 408 screen will not be completed for the situations listed below:

**a. New Evidence Causes No Change In Previous Disallowance**. Evidence
is submitted after award or disallowance of the claim and no change 1n
the previous determination is warranted;

**b. Duplicate Claim Submitted**. There has been a prior disallowance of
a pending claim and a subsequent claim by the same claimant is
disallowed for the same reason, without reconsideration of new evidence.
The claimant will be informed of the dismissal of the claim as a
duplicate of the claim previously completed. The actions will be taken
by the division which prepared the prior disallowance. The reapplication
will be marked "Duplicate Claim" and initiated by the adjudicator or by
the CP or VRS, as appropriate.

**c. Informal Claim Disallowed**. An informal claim, including an
unsigned application, will be administratively disallowed without a
decision as to entitlement. The claimant will not be given notice of any
right to appeal, but will be informed that determination as to
entitlement may not be made in the absence of a formal application; and

**d. Apportionment Claim Disallowed**. A claim for apportionment is
disallowed. This does not, however, abrogate the claimant's right to
notice of the action taken or the right to appeal. A notice of
disagreement from a denial of apportionment between a veteran and spouse
should be treated in the nature of a contested claim and the procedures
in DVB Manual M21-1, chapter 36 will be followed.

**8.20 REASONS FOR DISALLOWANCE**

The VR&C Division may access the 408 screen for one of six reasons to
disallow a case. The CP or VRS may not access the remaining 12 reasons
for disallowance shown in the left column on the screen. The CP or VRS
may select only one reason at one time from the six available.

**a. 65Entitlement Exhausted**. The award is disallowed because the
veteran has used all education and rehabilitation benefits for which he
or she is eligible.

**b. 66Beyond Eligibility Termination Date**. A claimant is not
entitled to chapter 31 benefits which extend past the eligibility
termination date.

**c. AADeclared Ineligible**. The veteran's service connection is
severed or reduced to a noncompensable level prior to the making of an
eligibility/entitlement determination by the VR&C Division.

**d. BBNot Entitled**. The veteran does not have an employment
handicap.

**8-24**

**June 4, 1987 M28-1, Part I**

**e. CCFailure To Pursue**. The veteran has not followed up a VA
request for additional information.

**f. DDOther**. This field is used when a claim is disallowed for a
reason other than one listed on the

screen.

**8.21 DISALLOWANCE LETTER**

The Target System is not capable of generating letters at this time, so
dictated letters are required. Whenever action is taken to disallow a
claim based upon a determination of non entitlement, the claimant or
fiduciary and any designated representative will be furnished a written
explanation sufficient to enable the recipient to understand the reason
for the action taken. The claimant will also be provided notice of the
right to appeal the decision.

**SUBCHAPTER IV. USE OF THE CORR (CORRECTION) COMMAND**

**8.22 GENERAL**

Chapter 31 master record (02S) corrections may be made directly on the
Target VDT. The CORR (Correction) command is available for both VR&C and
Adjudication personnel. CORR will be used to access a chapter 31 master
record, either to correct existing information or to add information
that previously did not exist in the record.

**8.23 CORR PROCESSING**

**a. Screens Allowing CORR Processing**. Changes to the chapter 31
master record may be made on the following screens:

**(1)** M32CH31 Master Record Status

**(2)** M33CH31 Entitlement/Diagnostic

**(3)** M34CH31 Entitlement History

**(4)** M36CH31 Award Data

**b. Protected (Non correctable) Fields**. The number of fields which
can be corrected by Target is limited. The cursor will not move to
fields to which no change can be made.

**c. Impact on Other Systems**. A correction to a chapter 31 master
record does not affect the BIRLS or CP&E system. If corrections to other
records are necessary concurrent with corrections to the chapter 31
master record, current procedures for BIRLS update (DVB Manual M23-1,
pt. 1, ch. 6) and Education master record correction (DVB Manual M28-2,
pt. IV, ch. 2) should be followed.

**d. Online Processing-Transaction 02S**. Chapter 31 CORR processing is
done on line, as is the updating of the chapter 31 master record.
Entries made to Target correctable fields will appear if a MINQ or CORR
is subsequently entered. The CORR action will be identified as an 02S
transaction in the STAT field under LAST ACTIVITY on the M32 screen.

**8.24 TARGET ACCESS AND RESPONSE**

**a. Access Procedure**. Access will be from the Ready screen using the
CORR command, the operator's password, either the screen number or the
benefit type, and the file number.

**b. Target Response**. After making the proper Ready screen entries and
pressing the Enter key, the screen requested in the screen number field
of the Ready screen will normally be displayed. If the screen number
field was not completed on the Ready screen, the M32 screen will be
displayed. However, if there is more than one payee for the record
requested, an S02 selection screen will be displayed listing all payees.
The

**8-25**

**M28-1, Part I June 4, 1987**

veteran's record (payee 00) is the only record in which data may be
changed using the CORR command. Selection may be made by placing an "X"
in front of the desired record and pressing the Enter key. If a record
is not available, the Ready screen will be redisplayed with an
explanatory message.

**c. Master Record Corrections**. When a correction screen is displayed,
the operator may enter data in the correctable fields, request another
screen or both. Additionally, the operator may restore the original
displayed data on the screen by using the RES function. If the field to
be corrected contains data, this data should be erased and the correct
data entered. If the field to be corrected is blank, the correct data
should be entered. If the operator enters new data or changes old data
and presses the Enter key, the entries are edited for validity and a
correction transaction (TR 02S) is generated. If no data elements are
changed or entered and no additional screen is requested, the operator
may terminate processing by hitting the Entry key. If END is entered in
the NEXT SCREEN field, processing is terminated, all screen input is
lost and no transaction is sent. If another screen is requested,
however, it will be displayed after the generation of any correction
transactions from the current screen.

**8.25 CORRECTABLE FIELDS**

The fields listed by screen below are correctable using the CORR
command.

**a. M32-CH31 Master Record Status**. The M32 screen correctable fields
and their allowable entries are:

**FIELD NAME ALLOWABLE ENTRIES**

SOCIAL SECURITY NUMBER Any nine-digit number, with or without dashes or
spaces. It

cannot begin with 8 or 9.

SEX M or F.

BIRTH DATE A valid date (MM/DD/YY) with or without dashes. It must be at

least 15 years in the past.

HOME PHONE (AREA CODE) Any valid area code.

HOME PHONE (PHONE NUMBER) Any valid phone number.

WORK PHONE (AREA CODE) Any valid area code.

WORK PHONE (PHONE NUMBER) Any valid phone number.

FIDUCIARY FOLDER LOCATION Any valid station number except 376 or 358.

RETIRED FOLDER "NO" is the only valid entry.

SPECIAL CODE Blank, 00, or 34 if participant is a chapter 34 crossover
trainee.

POWER OF ATTORNEY The following powers of attorney can be entered as

alphabetic or numeric characters: PVA (71) AL (74) ARC (75)

AVC (76) AMV (77) DAV (83) JWV (86) MPH (89). All other

entries in the power of attorney field must be the equivalents in

MP-6, part IV, supplement No. 1.1, paragraph 501.02. Blanks

may be entered to delete a power of attorney.

**8-26**

**June 4, 1987 M28-1, Part I**

**FIELD NAME ALLOWABLE ENTRIES**

HOMEBOUND Y or blank. Y if determined by the VR&C Division to be

homebound.

COMPETENCY 2 or blank. 2 if determined by a VA rating board to be

incompetent.

EOD (ENTERED ON DUTY) Any valid date, with or without dashes, or blank.
Blanks are not a

valid entry for the first EOD date line. The EOD date cannot be

later than the RAD date for the same line.

RAD (RELEASED FROM ACTIVE DUTY) Any valid date, with or without dashes,
or blank. The RAD

date must be blank if the EOD date for the same line is blank.

The RAD date may be blank if the EOD date and the inservice

indicator (see SERVICE PERSON field below) are entered. The

RAD date cannot be earlier than EOD date for the same line.

MILITARY RETIRED PAY Y or blank. If the veteran receives retired pay in
lieu of

compensation, enter Y.

SERVICE PERSON Y or blank. If Y entered, an EOD date must exist without
an

RAD date.

**b. M33-CH31 Entitlement/Diagnostic**. The M33 screen correctable
fields and their allowable entries are:

**FIELD NAME ALLOWABLE ENTRIES**

TEMPORARY ENTITLEMENT Y or blank. If the veteran is entitled to receive
chapter 31 services

while development takes place to determine exact remaining

entitlement, enter Y.

CURRENT COMBINED DEGREE Any valid percentage 00 to 100 in increments of
10

(SERVICE CONNECTED AND or blank. If an entry exists in SC (service
connected)

NONSERVICE CONNECTED) condition, then an entry in SC combined degree
must exist. If an

entry exists in NSC (nonservice connected) condition, then an

entry in NSC combined degree must exist.

CURRENT CONDITIONS (SC AND Any valid diagnostic code entered as NNNN,
NNNN-NNNN,

NSC) NNNN/NNNN or NNNNNNNN. If condition is ES (extra-

schedular), US (under-schedular) or a PP (permanent partial)

evaluation, enter as NNNN-AA or NNNN/AA, using ES, US or

PP as appropriate. Allows up to three SC and three NSC

conditions.

CURRENT PERCENT (SC AND NSC) The valid percentage assigned the
associated condition. Enter as

00 to 100. If a current percentage exists, an associated current

condition must exist. Allows up to three SC and three NSC

percentages.

**8-27**

**M28-1, Part I June 4, 1987**

**FIELD NAME ALLOWABLE ENTRIES**

ADDITIONAL CONDITIONS (SC) Valid entries are I through 9 if more than
three SC

conditions exist or blank if no more than three SC conditions

exist.

ADDITIONAL CONDITIONS (NSC) Valid entries are I through 9 if more than
three

NSC conditions exist or blank if no more than three NSC

conditions exist.

INDIVIDUAL UNEMPLOYABILITY Valid entries are Y, N, or blank. Enter Y if
the

veteran is rated unemployable by a VA rating board. If Y is

entered, the SC current combined degree entered must be less

than 100.

MEMORANDUM RATING The only valid action under the CORR command is

to delete an existing Y entry. If the veteran receives a formal

rating after a memorandum rating, the memorandum rating

indicator must be blanked out and the proper conditions and

rating percentages entered.

PARAGRAPH Valid entries are 28, 29, 30, or blank. If the veteran is
rated under

paragraph 28, 29, or 30, the appropriate entry will be made. If the

entry is 28, the current SC combined degree must be 50 or 100. If

the entry is 29 or 30, the current SC combined degree must be

100\. If the veteran was rated under paragraph 28, 29, or 30, but is

now no longer so rated, blanks must be entered in place of the

paragraph number.

**c. M34-CH31 Entitlement History**. The M34 screen correctable fields
and their allowable entries are:

**FIELD NAME ALLOWABLE ENTRIES**

FACILITY NAME Enter up to 20 characters of the facility's name for any
period of

current or prior VA training. An erroneous entry may also be

deleted by setting it to blanks. Entry of up to five facilities may be

made.

TRAINING TYPE The type of training at the facility. The types of
training are listed

in DVB Manual M28-2, part V, paragraph 2.20.

COURSE NAME The course name for the training facility listed.

ENTITLEMENT USED The entitlement used for the course listed, entered as
months and

fractions of a month (MM.FF). Fractions may be entered as 00,

25, 50, or 75 only.

BENEFIT TYPE The type of VA benefit the veteran received for the course.
This

may be entered as CH31, CH32, CH34, CH35, 901, 903, WWII,

CH33, or OTH.

**8-28**

**June 4, 1987 M28-1, Part I**

**FIELD NAME ALLOWABLE ENTRIES**

TRAINING STATUS For each course, enter S for satisfactory progress or
conduct

and cooperation, U for unsatisfactory progress or conduct and

cooperation, or I for in training. In training may only be indicated

on the first line.

ADDITIONAL TRAINING OVER 5 Valid entries are 0 through 9 or blank. Entry
of I would

indicate six periods of training, the five listed and I over 5. Blank

or 0 will be entered if 5 or less periods of training exist.

**d. M36CH31 Award Data**. The M36 screen correctable fields and their
allowable entries are:

**FIELD NAME ALLOWABLE ENTRIES**

EFFECTIVE REASON See DVB Manual M28-2, part V, paragraph 2.09.

TERMINATION REASON See DVB Manual M28-2, part V, paragraph 2.16.

ENTITLEMENT CODE Entry will be based upon period of service at last
discharge as follows:

01 Other 02 WWII

03 Pre-KC (PTE)

04 KC (Korean conflict)

05 Post-KC (PTE)

06 VE (Vietnam era)

07 Post-VE (PTE)

TRAINING TIME/HOURS The first position of this field must be a number,
the second

position can be a / (slash), - (dash) or space and the third position

must be an alphabetic entry.

TRAINING TIME CODE I less than 1/2 time

(THE FIRST POSITION) 2 1/2 time

3 3/4 time

4 full time

0 Other

TRAINING HOURS DDeficiency hours-IHL or NCD

(THE THIRD POSITION) UHigh school units

QQuarter hours-IHL

SSemester hours-IHL

CClock hours-OJT; or NCD in which classroom training

predominates

PVocational/technical in which shop practice

predominatesNCD

RResidence or internship-IHL

TRAINING TYPE See DVB Manual M28-2, part V, paragraph 2.20.

**8-29**

**M28-1, Part I June 4, 1987**

**FIELD NAME ALLOWABLE ENTRIES**

ATTENDANCE HOURS/DAYS Number of hours a week and days a week attending

entered as NNN, NN/N, NN-N or N.

ATTENDANCE HOURS Number of hours a week attending from 01-60.

If entry is less than 10, it must have a preceding

zero.

ATTENDANCE DAYS Number of days a week attending, from 1 to 7

FACILITY CODE Any valid eight-digit facility code

**SUBCHAPTER V. USE OF CNBR (CHANGE OF FILE NUMBER) COMMAND**

**8.26 GENERAL**

The CNBR (Change of File Number) command may be used by both VR&C
(Vocational Rehabilitation and Counseling) and Adjudication personnel.
Generally this command will change a file number, consolidate duplicate
master records, and delete unwanted records with incorrect file numbers.
This command is restricted to chapter 31 Target master records which
indicate the veteran is not in receipt of subsistence payments. It was
designed chiefly to adjust or delete the limited chapter 31 master
records created October 24, 1983, as a result of the Target conversion
from the St. Paul statistical system.

**8.27 CHANGE OF FILE NUMBER AND CONSOLIDATION FUNCTION**

**a. Identification of File Number To Be Retained**. If an operator
discovers that two or more chapter 31 master records exist for the same
veteran, the operator must decide which file number should be retained.
Similarly, if a chapter 31 master record was established under an
incorrect file number, the operator must identify the actual file number
and correct the record.

**b. Master Record Adjustment Restrictions Based on Master Record
Types**. The CNBR command will process differently or not at all
depending on the contents of the master record(s) requiring adjustment.
The contents are determined by the type of each master record. If the
master record type 1, j or S, the master record is considered to contain
only statistical data. If the master record type is A, E, or C, the
master record contains pay data, but may also contain statistical data.
If the field STAT DATE contains a value of MM-DD-YYYY or 00-00-0000 and
the master record type is A, E or C, the record contains both pay and
statistical data.

**c. When the CNBR Command Can Be Used**. If the master record to be
eliminated contains only statistical data, the CNBR command may be used
to create a new master record under the correct file number. The CNBR
command may similarly be used to combine the statistical data in the
incorrect record with the correct master record provided the correct
master record contains only pay data. If the incorrect master record
contains pay data, however, CNBR processing is restricted to those cases
where the master record is type E and the pay data has been purged from
the payment system. Purged pay data is identified on the M32 screen by
"XXX" in the PAY field under LAST ACTIVITY (see subpar. d below). In
addition, the associated correct master record must also contain pay
data. If both records contain statistical data, however, CNBR processing
is not possible because Target cannot determine which statistical field
data entries are correct. Figure 8.07 summarizes the capability of the
CNBR command by master record type when a change of file number or
consolidation of chapter 31 master records is required.

**d. CNBR Processing Requires "XXX" In PAY Field for Type E Master
Records**. The PAY field found under LAST ACTIVITY on the M32 screen in
the incorrect master record must contain the entry "XXX" or the CNBR
command will not process against the record. That value signifies that
the payment data

**8-30**

**June 4, 1987 M28-1, Part I**

**INCORRECT FILE NUMBER WITH MR CONTAINING:**

STATISTICAL DATA PAY DATA ONLY PAY AND

I, J, OR S TYPE MR A, C, OR E STATISTICAL

TYPE MR DATA A, C, OR

STAT DATE=blank E TYPE MR

STAT DATE=value

CORRECT FILE

NUMBER WITH

MR CONTAINING:

NO MR YES NO NO

(New MR is created under

correct file number and

old MR under incorrect

file number is deleted.)

PAY DATA YES NO\* NO\*\*

ONLY (Statistical Data from

A, C, OR E incorrect file number is

TYPE MR added to the new MR,

then the incorrect

STAT DATE = statistical MR is

BLANK automatically deleted.)

STATISTICAL DATA NO NO NO

I, J, OR S

TYPE MR

PAY AND NO NO\* NO

STATISTICAL

DATA

A, C, OR E

TYPE MR

*\*If the incorrect MR is E type (pay data only) and the new MR is A or
E type, CNBR will delete incorrect MR. NOTE: All E type master records
which are linked to incorrect file number will be deleted.*

*\*\*If the incorrect E type contains both pay and statistical data, but
the new A or E type MR (payee 00) contains pay data only, CNBR will add
incorrect master record's statistical data to the new MR and purge the
incorrect MR.. NOTE: All E type master records which are linked to file
number will be deleted.*

**Figure 8.07. Uses of the CNBR Command**

**8-31**

**M28-1, Part I June 4, 1987**

have been automatically purged from the VR&C Payment System at the Hines
DPC. If the "XXX" is not present, the error message "RECORD EXISTS ON
PAY SYSTEM" will be generated.

**e. CNBR Processing Requires All Payees Under One File Number Have Type
E Master Records**. Multiple payees may exist on a case requiring CNBR
processing, so the Target System checks for additional payee records for
each veteran (payee number = 00) record before CNBR processing against
an incorrect type E master record takes place. In addition, all payee
master records associated with a given file number must be type E. If
not, the error message "ALL PAYEE RECORDS NOT E-TYPE. START NEW COMMAND
WITH PA2 KEY" will be generated.

**f. Online Update by Transaction 26R**. A transaction 26R will be
generated online and identified in the chapter 31 master record STAT
field found under LAST ACTIVITY on the M32 screen.

**8.28 DELETION FUNCTION**

**a. Restricted to Statistical Master Records**. For chapter 31
processing, a designated operator may use CNBR processing to delete
chapter 31 master records as indicated:

**DELETION CAPABILITY BY MASTER RECORD TYPE:**

> A C E I J S

NO NO NO YES YES YES

**b. For Veteran Records Only**. If deletion is requested, but the
master record requiring deletion is other than payee "00," then an error
situation has been identified and the Target message "CANNOT PROCESS,
OTHER THAN 00 RECORD FOUND" will be issued.

**c. Multiple Payee Records Cannot Be Deleted**. If deletion is
requested, but the master record requiring deletion has a payee "00"
record and one or more records under payee numbers other than "00," then
the deletion function cannot be used and the message "CANNOT PROCESS,
MULTIPLE PAYEES" will be issued.

**d. VR&C Officer Approval Required**. The intentional deletion of a
chapter 31 master record must be approved by the VR&C Officer. The
approval will consist of an annotation on OF 41, Routing and Transmittal
Slip, of the claim number to be deleted, the VR&C Officer's signature
and the date. Following the deletion action, the request will be filed
down on the left flap of the R&E folder or on the left flap of the
claims folder if an R&E folder does not exist. Whenever a chapter 31
master record is deleted by CNBR processing, a security transaction type
24 will be issued for the station Security Officer. The station Security
Officer will then contact the VR&C Officer to ensure the deletion of a
given record was properly approved. The VR&C Officer will confirm the
deletion action in writing for the Security Officer's records.

**c. Online Update by Transaction 26D**. A transaction 26D will be
generated and identified in the chapter 31 master record STAT field
found under LAST ACTIVITY on the M32 screen.

**8.29 ACCESS AND RESPONSE**

The CNBR command will be used to access a chapter 31 master record for
file number adjustment or cancellation.

**a. Access Procedure**. The following entries will be made on the Ready
screen:

**(1)** Command: Enter CNBR.

**(2)** Password: Enter the operator's password.

**(3)** File Number: Enter the file number for the record which is to be
changed or deleted.

**8-32**

**June 4, 1987 M28-1, Part I**

**b. Target Response**. If the information entered by the operator is
not valid, an error message is displayed. If the information is properly
entered, the operator's command authority is checked. If the operator is
not authorized use of the command, a record of the violation is made on
the security log, a security violation message is displayed on the
operator's VDT, and processing is terminated. If the operator is
authorized use of the command, a search for the chapter 31 master record
is made based on the information entered. If no master record is found
under that file number, the Ready Screen (S00) will be redisplayed with
a message. If the master record is found, the initial inquiry screen of
the master record to be changed is displayed.

**c. Input Processing**. The operator can only change one display field,
FILE NUMBER. Depending on the contents of the chapter 31 master records
involved, different processing steps will take place.

**(1) Change or Consolidation of Chapter 31 Master Record Required**.
When the inquiry screen is displayed for a change of file number, the
operator will enter the correct file number in the FILE NUMBER field.
Upon entry in Target, this correct file number is checked against BIRLS.
A BIRLS record must exist under the correct file for the transaction to
process. A check will be made for a BIRLS record in all cases despite
the existence of a chapter 31 master record. In addition, the number of
the station in the BIRLS record must match that of the operator. If no
matching BIRLS record is located, a message is displayed and processing
ends. At the time BIRLS is checked, the incorrect file number is checked
for outstanding PIF issues. If there are no outstanding PIF issues, a
transaction is generated. If PIF issues exist under the incorrect
record, the transaction cannot be accepted until the PIF is cleared.

**(2) Intentional Deletion**. If an intentional deletion of a master
record is desired, the operator must enter eight zeros (00000000) in the
FILE NUMBER field. Upon entry in Target, the chapter 31 master record
associated with the file number initially entered on the Ready Screen is
deleted. Certain jurisdictional edits are performed before this
processing can take place. Specifically, the station number of the
operator must match that of either the chapter 31 master record being
deleted or the associated BIRLS record. If there is no match of station
number with either record, a message is displayed and processing ends.
As an exception, if there is no match of station number with the chapter
31 master record and no BIRLS record exists for that file number,
processing will continue.

**(3)** Special Processing Functions

**(a)** If RES (restore) is entered in the NEXT SCREEN field, the system
will ignore the data entered on the

screen and restore the original displayed data.

**(b)** If END is entered in the NEXT SCREEN field, processing is
terminated, all screen input is lost, and no transaction is sent.

**8.30 CAI LESSON AVAILABLE**

Lessons which will facilitate chapter 31 Target implementation are
available on the Target System using the LERN command. The CAI lesson
C31-CNBR has been developed for training on the chapter 31 change,
combine or delete file number function.

**8.31 FILE NUMBER ADJUSTMENT, AND CANCELLATION-BIRLS AND CP&E SYSTEMS**

The processing of CNBR in Target will adjust a chapter 31 master record,
but no information from this action is exchanged between the chapter 31
master record and the BIRLS or the CP&E systems. Therefore, for these
other records systems, the records adjustment procedures using the DUPC
(Duplicate Record Consolidation) command must continue to be used in
accordance with the procedures outlined in DVB Manual M23-1, Part I,
chapter 6.

**8-33**

**M28-1, Part I June 4, 1987**

**8.32 RECORDS THAT CANNOT BE ADJUSTED USING THE CNBR COMMAND MUST BE
REPORTED TO VA CENTRAL OFFICE**

Those cases which cannot be adjusted by using CNBR processing must be
reported to Central Office for correction. A print of the M32 screen of
the incorrect master record(s), annotated "Incorrect Record," along with
a print of the M32 screen of the correct master record, annotated
"Correct Record," will be submitted to the Director, Vocational
Rehabilitation and Education Service (226).

**SUBCHAPTER VII. MASTER RECORD INQUIRY PROCEDURES**

**8.33 OBTAINING MASTER RECORD INQUIRIES ON THE TARGET SYSTEM**

a\. Complete chapter 31 MR (master record) data can be obtained via the
MINQ (master record inquiry) command. The seven chapter 31 master record
inquiry screens follow:

\(1\) M32 (chapter 31 Master Record Status) Screen

\(2\) M33 (chapter 31 Entitlement/Diagnostic) Screen

\(3\) M34 (chapter 31 Entitlement History) Screen

\(4\) M35 (chapter 31 Case Status/Counseling) Screen

\(5\) M36 (chapter 31 Award Data) Screen

\(6\) M37 (chapter 31 Dependency Data) Screen

\(7\) M38 (chapter 31 Future Controls/Receivables) Screen

b\. In addition to these seven basic screens, there is one additional
screen which may be used. This screen reflects receivables which have
been placed in the C&P account.

M01 (Deductible/Receivable/Balance Data) Screen

**8.34 READY SCREEN ENTRIES**

**a.** To obtain a chapter 31 MINQ screen, make the following entries on
the Ready screen:

**(1)** Command (MINQ);

**(2)** Operator's password;

**(3)** Screen number (enter the number M32, M33, etc.). If this field
is left blank, the Benefit field must have an entry;

**(4)** File number; and

**(5)** BENEFIT Field. The correct entry for this field is CH31. Either
this field or the SCREEN NUMBER

field must have an entry for chapter 31 MINQ'S.

\(6\) Press the Enter key.

**b.** If no chapter 31 MR is found with the entered information, then
the following message will be displayed at the bottom of the Ready
screen: "NO CH31 MASTER EXISTS AT HINES."

**c.** If all appropriate Ready screen fields are entered, but no screen
number is requested and a chapter 31 MR is found, a M32 screen will be
displayed.

**d.** If more than one record is found, the Payee Selection S02 screen
will be displayed. Selection of the appropriate record, veteran or
apportionee, can be made from the S02 screen.

**8-34**

**June 4, 1987 M28-1, Part I**

**e.** MINQ screen printouts will be requested only if:

**(1)** A complex claim is being processed and master record data must
be thoroughly analyzed, or

**(2)** A copy of the MINQ screen data is needed in the claims folder
for historical or record purposes.

***NOTE***: MINQ screen printouts need not be signed by the employee.
All MINQ screen printouts when no longer required, will be disposed of
under Records Control Schedule VB-1, part I, items 13‑052.400 and
08‑041.000.

**f.** The Target System searches only the CH31 data base; it does not
search the C&P/CH34/CH35 or the CH32/903/901 data bases unless the Ready
screen has an entry specific to those data bases in the SCREEN NUMBER or
BENEFIT field.

**g.** It is important to note that if a MINQ is requested for a chapter
31 MR, no search will be done for chapter 34, chapter 35, C&P, or other
records under the given file number. If no chapter 31 MR is found on
such an inquiry, the message shown in subparagraph b above will be
displayed even if another record exists. Conversely, if both the SCREEN
NUMBER field and the BENEFIT field are left blank on the Ready screen, a
search will be done for CH34/35 or C&P records only, but no search will
be done to locate a chapter 31 MR even if one exists.

**8.35 CHAPTER 31 MASTER RECORD STATUS (M32)**

**a. M32 Screen Display Fields**. This screen provides basic data about
the veteran, including address, telephone number, dates of claim and
award, check amount, location of the CER
(counseling/evaluation/rehabilitation) folder and service dates.

**b.** A brief description of displayed fields follows:

**FIELD NAME DESCRIPTION**

DATE Current processing date (MM-DD-YY).

MASTER RECORD TYPE Shows the current status of the claim using the

following legends:

A---Active

C---Dependent

E---Terminated

I---Basic

J---Disallowed

S---Statistical

FILE NUMBER The veteran's file and payee numbers. The payee number is

separated from the file number by a hyphen.

STUB NAME First initial, middle initial (if any) and up to five letters
of the

payee's last name.

SOCIAL SECURITY NUMBER Shows the veteran's Social Security number. If
the veteran has no

Social Security number, zeros will be entered.

NAME AND ADDRESS Shows the payee's current name and address of record.

**8-35**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

SEX Shows whether the veteran is made (M) or female (F).

BIRTH DATE Shows the veteran's date of birth. Displayed in MM-DD-YYYY
format.

LAST ACTIVITY Shows the transaction code in the first three spaces
followed by the month-day-year that the last online statistical (STAT)
transactions. For the payment system (PAY) transactions, shows the
transaction code in the first two spaces followed by the month- year
cycle number that the last payment (PAY) transaction processed.

TIME Shows the hour and minute (central time) that the last statistical
(STAT) transaction processed.

HOME PHONE Shows the veteran's home phone number including the area
code.

WORK PHONE Shows the veteran's work phone number including the area
code.

AWARD STATION Displays the three-digit number of the field station with
jurisdiction of the veteran's subsistence payments.

ORIG CLAIM DATE Shows the date the original application for chapter 31
was received in the VA. Displayed as MM-DD- YYYY or zeroes.

CER FOLDER LOC Shows the three-digit number of the field station with
jurisdiction over the veteran's CER folder.

ORIG AWARD DATE Shows the effective date of the original chapter 31
award.

FIDUCIARY FOLDER LOC If a fiduciary folder exists for the veteran, this
field will show the station at which the folder is located.

APP EDUCATION LEVEL Shows highest level of education attained by the
veteran at the time of application for chapter 31. The system displays
the education level at time of application, 00- 17 or 20 if unknown.

RETIRED FOLDER

APP SC COMB DEGREE

FOLDER PULL CODE Not used at this time.

CHECK AMOUNT XXXX.XX, suppress zeroes left or decimal point, or blank.

APP DEPENDENCY XX or blank.

EMP RESPONSIBLE XXXX or blank.

SPECIAL CODE XX or blank.

**8-36**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

POWER OF ATTORNEY See DVB Manual M28-2, part V.

HOMEBOUND "Y" or blank.

EOD (4 OCCURRENCES) Shows the EOD (entry on duty) dates.

RAD (4 OCCURRENCES) Shows the release from active duty date associated
with the EOD on the same line.

CONVERSION IND A "I" indicates the master record existed before Target
and has not been updated.

APP SC COMB DEGREE Service-connected combined degree of disability at
time of application.

FOLDER PULL CODE Not used at this time. This field will be used to
indicate that a claim must be processed with the folder or to remove
that restriction.

CHECK AMOUNT This shows net pay, the regular recurring (monthly) payment
less any recurring deductions established in the record. The field
contains zeros if the master record is terminated (type E).

APP DEPENDENCY XX or blank.

EMP RESPONSIBLE Unique code associated with the employee responsible for
the chapter 31 case.

SPECIAL CODE Special code to identify special circumstances.

POWER OF ATTORNEY See DVB Manual M28-2, part V.

HOMEBOUND "Y" is entered if the VR&C Division determines the veteran to
be homebound.

EOD (4 OCCURRENCES) Date of entry on active duty.

RAD (4 OCCURRENCES) Date of release from active duty. Each RAD
corresponds to the EOD next to it.

***NOTE**: During initial creation of a master record, all service dates
from the 101 BIRLS screen are displayed for the operator under EOD and
RAD on the 331 screen. (Maximum 2 periods of service presented.) During
subsequent processing where an MR already exists or for redisplay from
PIF, the lines will be displayed in reverse chronological order (most
recent first). All fields will be available for input.*

**8-37**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

CONVERSION IND The "1 " indicates the master record existed before
Target and has

not been updated.

The "0" indicates that a pre-target case has been updated. If the field
is blank, the master record was created initially on Target.

COMPETENCY **Display As**

Blanks

Blanks

"2 INCOMPETENT"

ACCOUNTING CODE Displays "04," "08," or blank.

DISALLOWANCE RSN **Display As**

"O1 NO MILITARY SERVICE"

"03 CHARACTER OF DISCHARGE"

"04 ENTITLEMENT FORFEITED"

"05 NO S/C DISAB---POSS OTH ENT"

"5A NO S/C DISAB---NO OTH ENT"

"06 DISABILITY NOT DUE TO SVC"

"16 FAILURE TO PROSECUTE"

"20 CLAIM WITHDRAWN"

"21 WHEREABOUTS UNKNOWN"

"22 DEATH OF CLAIMANT"

"29 OTHER---ADJ"

"30 ELECTED OTHER BENEFIT"

"65 ENTITLEMENT EXHAUSTED"

"66 BEYOND ELIG TERM DATE"

"AA DECLARED INELIGIBLE"

"BB NOT ENTITLED"

"CC FAILURE TO PURSUE"

"DD OTHER---VR&C"

PAY SUSPENSE Shows whether the record is in pay suspense. If so, action
needed to release suspense is indicated:

"02 AWARD"need award action

"04 ADDR OR AWD"need change of address or

award action

"06 ADDR & AWD"need change of address and

award action

MILITARY RET PAY For veterans in receipt of retired pay, the entry will
be "Y".

SERVICE PERSON Field indicates whether the applicant is currently in
service. If so, a "Y" is displayed and an EOD is present with no
corresponding RAD.

**8-38**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

REASON Reason for returned checks.

**Display As**

"0l ADDRESS" means unclaimed, undetermined, or moved

"02 REMARRIED"

"03 DEATH"

"04 NOT ENTITLED"

"05 NOT ENTITLED"

"06 NOT ENTITLED"

"OTHER" (***NOTE**: Any number other than the numbers given will result
in this display*.)

NUMBER The number of the returned check.

AMOUNT Returned check amount or zeros.

DATE Returned check date displayed as MM-DD-YYYY or blank.

NEXT SCREEN A three-position entry field. Acceptable entries include
M00, M32, M33, M34, M35, M36, M37, and M38 and END. No entry is also
acceptable, and the display will end if the Enter key is pressed with no
entry in the field.

xxx\..... System-generated information and error message. For example,

\..... xxx the "ADDITIONAL PAYEE(S)" message is generated if an
appointee record exists.

**8.36 CHAPTER 31 ENTITLEMENT/DIAGNOSTIC (M33)**

**FIELD NAME DESCRIPTION**

CURRENT DATE Current processing date (MM-DD-YY).

FILE NUMBER The veteran's file and payee numbers. The payee number is
separated from the file number by a hyphen.

STUB NAME First initial, middle initial (if any) and up to five letters
of the payee's last name.

PRIOR VA TRAINING Fields to specify length of time of previous VA
training by

(MONTHS AND DAYS) benefit type. Time expressed in months and days.

CH31

CH32

CH33

CH34 Sum total of all previous VA training pursued. Time expressed

CH35 in months and days. If DD exceeds 29, excess days are

OTHER converted to months and added to MM. DD=30 converts to TOTAL
MM=01.

**8-39**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

CREDITABLE 31 ENT Entitlement available for the receipt of chapter 31
benefits. Computed by subtracting TOTAL (all prior VA training) from
maximum entitlement of 48 months, converting remaining days to
fractional months entitlement as follows:

**Days Entitlement**

1-7 .25

8-15 .50

16-23 .75

24-31 1.00

TEMPORARY ENTITLEMENT Entitlement used under other benefit programs is
unknown or needs clarification to validate so "Y" is entered. When the
information becomes available, this "Y" indicator is removed by the
operator.

REMAINING CH31 ENT Is not used at this time. Will show the amount of
entitlement remaining to the veteran as of the last award date in the
master record for chapter 31.

ENTITLEMENT EXTENSION VR&C Officer's approved extension of entitlement
in whole month increments.

RESTORED ENTITLEMENT Is not used at this time.

TERMINATION DATE The date after which a veteran is no longer eligible
for chapter 31 benefits.

> Displayed as a date. The objective is for each veteran to have 12
> years in which to use his or her eligibility. The system will generate
> this date based on INIT RATING NOTIFICATION DATE, MED INFEAS PERIOD
> and/or DEFERRAL PERIOD fields. Straight subtraction plus I day will be
> used to determine length of periods and actual days will be counted.
> If In-Svc, the applicant has NO ELIG TERMINATION DATE.
>
> Termination Date is INIT RATING NOTIFICATION Date plus 12 years or
> Init Rating Notification Date plus 12 years plus Med Infeas Period,
> Init Rating Notification Date plus 12 years plus Deferral Period or
> Init Rating Notification Date plus 12 years plus Med Infeas Period
> plus Deferral Period.

**8-40**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

TERMINATION REASON The reason value identifies the components of the
calculated termination date.

**Value Termination Date Computed**

1 Init Rating Notification Date plus 12 years.

2 Init Rating Notification Date plus 12 years plus Med Infeas Period.

3 Init Rating Notification Date plus 12 years plus Deferral Period.

4 Init Rating Notification Date plus 12 years plus Med Infeas Period
plus Deferral Period.

SERIOUS EMP HANDICAP If the veteran is identified as having a serious
employment handicap, ("Y" entry), an extended termination date and/or
extended entitlement beyond 48 months is allowable. This includes
extensions granted under 38 CFR 21.78(b)(3).

INIT RATING NOTICE Date the veteran was notified of the disability
granting initial compensable service connection or RAD if applicant
established basic eligibility while in service.

DIAGNOSTIC

CURRENT COMBINED DEGREE The percentage of service-connected disability

SERVICE CONNECTED assigned, combining disability percentage for all
service- connected conditions.

CURRENT CONDITIONS SERVICE- The disabling conditions for which the
veteran was rated

CONNECTED service connected represented by a specific diagnostic code
assigned based on the nature of the disability. A maximum of three
conditions can be entered.

CURRENT PERCENT SERVICE The percent disabling of the associated Current
Condition

CONNECTED identified. A maximum of three percents can be entered.

ADDITIONAL CONDITIONS SERVICE Represents the number of existing
service-connected

CONNECTED conditions beyond those displayed on the screen.

Values are from "1 " to "9 ".

CURRENT COMBINED DEGREE The percentage of nonservice-connected
disability

NONSERVICE CONNECTED assigned, combining disability percentages for all
nonservice- connected conditions.

**8-41**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

CURRENT CONDITIONS The disabling conditions for which the veteran was
rated

NONSERVICE CONNECTED nonservice-connected represented by a specific
diagnostic code assigned based on the nature of the disability. A
maximum of three conditions can be entered.

CURRENT PERCENT NONSERVICE The percent disabling of the associated
current

CONNECTED condition (non-service connected) identified. A maximum of
three percent can be entered.

ADDITIONAL CONDITIONS Represents the number of existing nonservice-
connected

NONSERVICE CONNECTED conditions beyond those displayed on the screen.
Values are from "1" to "9".

INDIVIDUAL UNEMPLOYABILITY If the veteran has entitlement to individual
unemployability (IU), Y would be entered. If the veteran's entitlement
to IU was denied or reversed, then N would be entered. No entry is
necessary if IU is not an issue.

MEMORANDUM RATING A Y is entered to indicate that a disability rating
does not exist and a memorandum rating to establish service connection
has been made. In this circumstance, no service-connected degree is
assigned to the service-connected conditions).

PARAGRAPH Entries of 28, 29, or 30 indicate that the veteran is
receiving temporary 100 percent or 50 percent service-connected
compensation due to paragraphs 28, 29, or 30. This would involve
hospitalization/ surgery for his or her service-connected condition or a
prestabilization rating.

NEXT SCREEN Valid entries include M00, M32, M33, M34, M35, M36, M37,
M38, END, or no entry.

**8.37 CHAPTER 31 ENTITLEMENT HISTORY (M34)**

**FIELD NAME DESCRIPTION**

DATE Current processing date (MM-DD-YY).

FILE NUMBER The veteran's file and payee number. The payee number is
separated from the file number by a hyphen.

STUB NAME First initial, middle initial (if any) and up to five letters
of the payee's last name.

**8-42**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

ELIGIBLE AT APPLICATION CH32/34 Indicates whether there was eligibility
for chapter 32 or chapter 34 benefits at the time of application for
chapter 31 benefits. Eligibility means that the individual had not
reached his or her delimiting date and had remaining entitlement.

ELIGIBLE AT APPLICATION CH 35 Indicates whether there was eligibility
for chapter 35 benefits at the time of application for chapter 31
benefits. If eligible, "5 CH35" is displayed. Otherwise, "N None" or "U
UNK" is displayed.

DELIMITING DATE AT Date in which the claimant's eligibility for chapter
35 benefits

APPLICATION CH 35 expires. Entry expressed in the standard data format
with the year given as for digits.

CH 32/34 Months of chapter 32 or chapter 34 benefits remaining at the
time of application for chapter 31. Entry expressed as months and
decimal quarter months.

REMAINING ENTITLEMENT AT Months of chapter 35 benefits remaining at the
time APPLICATION CH 35 of application for chapter 31. Entry expressed as
months and decimal quarter months.

The following fields provide detailed information on prior training
under VA education programs:

**FIELD NAME DESCRIPTION**

FACILITY NAME The name of the training establishment attended while
pursuing the course shown on the same line.

TRAINING TYPE Type training for the corresponding course pursued as
shown on the same line.

COURSE NAME Contains a general description of the course pursued in
facility shown on the same line.

ENTITLEMENT USED Number of months of entitlement used while pursuing
corresponding course at designated facility. Expressed as months and
decimal quarter months.

BENEFIT TYPE Education program under which the training was pursued.
Display can be:

"CH31"

"CH34"

"CH35"

"CH32"

"901"

"903"

"WWII"

"CH33"

**8-43**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

TRAINING STATUS Shows whether veteran's progress in training is rated

satisfactory (S) or unsatisfactory (U), or whether he

is still in training (1).

ADDITIONAL TRAINING OVER 5 If veteran has attended more than 5
facilities or has

been enrolled in more than 5 types of programs, this

field is set to indicate the number of additional

schools, programs, etc. EXAMPLE: If value in field

= 1, veteran had 6 periods of training at the time

he applied for CH31 benefits. Used as an alert

that additional folder review may be necessary.

Values are from 0 to 9.

NEXT SCREEN Valid entries include M00, M32, M33, M34, M35, M36, M37,
M38, END, or no entry.

**8.38 CHAPTER 31 CASE STATUS/COUNSELING (M35)**

**FIELD NAME DESCRIPTION**

DATE Current processing date (MM-DD-YY).

FILE NUMBER The veteran's file and payee numbers. The payee number is
separated from the file number by a hyphen.

(STUB NAME) First initial, middle initial (if any) and up to five

letters of the payee's last name.

The following case status and future control fields provide information
on the 10 case status categories listed on the left side of the screen.

**FIELD NAME DESCRIPTION**

CASE STATUS The beginning date for the corresponding case status as
shown

BEGIN DATE on the same line.

CASE STATUS The ending date for the corresponding case status as shown

END DATE on the same line.

CASE STATUS The reason for leaving or entering that corresponding case
status

RSN as shown on the same line.

CASE STATUS The actual days spent in a case status. The value is system

DAYS generated.

FUTURE CONTROL DATE Operator entered or system generated maturing date
of a master record control indicating review is needed because of the
time spent in the corresponding case status as shown on the same line.

**8-44**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

EMP A unique code associated with an individual VR&C employee
responsible for the case status future control as shown on the same
line.

COUNSELING PLAN RECEIVED Date obtained from St. Paul statistical system
con- version. For information only.

EMPLOYMENT OBJECTIVE Date obtained from St. Paul statistical system con-
version. For information only.

DISPOSITION Date obtained from St. Paul statistical system con- version.
For information only.

DOT CODE IWRP/EMP Objective code of final plan and employment code after
rehabilitation.

LAST DISPOSITION Date obtained from St. Paul statistical system con-
version. Form information only.

SALARY/PRE-TRG/POST TRG PRE-TRG: monthly whole dollar rate of pay at the
time of the

> veteran\'s chapter 31 entitlement determination.
>
> POST TRG: monthly whole dollar rate of pay at the time the veteran is
> employed. This amount will be verified and/or corrected at the time of
> the rehabilitation declaration."

NEXT SCREEN Valid entries include M00, M32, M33, M34, M35, M36, M37,
M38, END, or no entry.

**8.39 CHAPTER 31 AWARD DATA (M36)**

**FIELD NAME DESCRIPTION**

DATE Current processing date (MM-DD-YY).

FILE NUMBER The veteran's file and payee numbers. The payee number is
separated from the file number by a hyphen.

STUB NAME First initial, middle initial (if any) and up to five letters
of the payee's last name.

The following fields contain award data and occur up to four times. Data
in one field within a column will force data or default values to be
displayed for all appropriate fields within that column. If a column
contains no data, blanks will be displayed for all fields.

**FIELD NAME DESCRIPTION**

EFFECTIVE DATE MM-DD-YY or zeros

EFFECTIVE RSN Must enter a reason if any effective date is entered.

TERMINATION DATE The "zone" date of the enrollment period,

TERMINATION RSN Must enter a reason if a termination date is entered.

**8-45**

**M28-1, Part I June 4, 1987**

**FIELD NAME DESCRIPTION**

ENTITLEMENT CODE Entry will be based upon period of service at last
discharge as follows:

01 Other

02 WWII

03 Pre-KC (PTE)

04 KC

05 Post-KC (PTE)

06 Vietnam Era

07 Post-VE (PTE)

GROSS AMOUNT NNNN.NN, suppress leading zero left of decimal point, or
zeros

NET AMOUNT NNNN.NN, suppress leading zero left of decimal point, or
zeros

DEPEND TOT/THIS "00", "l0" - "79", "81" - "89" or blank "/" "00, "10" -
"79", "81" - "89", or blank

TRNG TIME/HOURS The first position of this field must be a number, the
second position can be a / (slash), a-(dash) or a space and the third
position must be an alphabetic entry. The format for entry is N/A, N-A,
or N space A.

TRAINING TIME CODE 1 less than 1/2 time

(THE FIRST POSITION) 2 1/2 time

3 3/4 time

4 Full time

0 Other

TRAINING HOURS D---Deficiency Hours---IHL or NCD

(THE THIRD POSITION) U---High School Units

Q---Quarter Hours---IHL

S---Semester Hours---IHL

C---Clock Hours OJT or NCD

P---Vocational/Technical---Shop Practice PredominatesNCD

R---Residence or Internship---IHL

TRAINING TYPE X or blank

ATTEND HOURS/DAYS Number of hours a week and days a week attending
school. Number of hours a week attending from 01-60. Number of days a
week attending 1-7.

FACILITY CODE Any valid facility code or blank. If eight digits
XXbXXXXbXXb. If nine digits XXbXXXXbXXX.

TRAINING WAGES XXXX.XX, suppress leading zero left of decimal point, or
blank.

**8-46**

**June 4, 1987 M28-1, Part I**

**FIELD NAME DESCRIPTION**

JOURNEYMAN WAGES XXXX.XX, suppress leading zero left of decimal point,
or blank.

APPORTIONED TYPE Variable or blank.

APPORTIONED AMT XXXX.XX, suppress leading zero left of decimal point, or
blank.

ADVANCE PAY IND Enter Y or zero.

NEXT SCREEN Valid entries include M00, M32, M33, M34, M35,

M36, M37, M38, END, or no entry.

**8.40 CHAPTER 31 DEPENDENCY DATA (M37)**

(Future Development)

8.41 CHAPTER 31 FUTURE CONTROLS/RECEIVABLES (M38)

**FIELD NAME REMARKS**

CURRENT DATE MM-DD-YY

FILE NUMBER bNNbNNNbNNN-NN, or NNNbNNbNNNN-NN

STUB NAME XbXbXXXXX or XbbbXXXXX

a\. The following fields contain future control data and occur up to 10
times. Data in one field within a row will force data or default values
to be displayed for all fields within that row. If a row contains no
data, blanks will be displayed for all fields.

**FIELD NAME DESCRIPTION**

FUTURE CONTROL DATE MM-DD-YYYY or blank

(displayed in chronological order)

FUTURE CONTROL RSN Variable or blank

FUTURE CONTROL EMP Variable or blank

b\. The following fields contain deduction/balance data and occur up to
four times. Data in one field within a row will force data or default
values to be displayed for all fields within that row. If a row contains
no data, blanks will be displayed for all fields.

**FIELD NAME REMARKS**

DEDUCTION CODE Variable.

DEDUCTION CLASS Variable.

DEDUCTION XXXX.XX, suppress leading zero left of decimal point (unless
entire field zeros). When there is a deduction code and class but no
deduction, display zeros.

**8-47**

**M28-1, Part I June 4, 1987**

**FIELD NAME REMARKS**

AR BALANCE XXXXX.XX, suppress leading zero left of decimal point (unless
entire field zeros). When deduction code and class but no balance,
display zeros.

AR DATE MM-DD-YYYY or blank.

FIELD NAME DESCRIPTION

NEXT SCREEN Valid entries include M00, M32, M33, M34, M35, M36, M37,
M38, END, or no entry.

**8-48**