**CHAPTER 3. TARGET PROCESSING OVERVIEW**

**CONTENTS**

PARAGRAPH PAGE

3.01 General 3-1

3.02 Target Commands 3-2

3.03 Pending-Issue Establishment 3-3

3.04 Claims Development Processing. 3-4

3.05 Claims Data Entry Processing 3-5

3.06 Claims Adjudication. 3-5

3.07 Claims Authorization . 3-5

**CHAPTER 3. TARGET PROCESSING OVERVIEW**

**3.01 GENERAL**

The following is a summary of the Target System actions during award
processing.

a\. **Pending Issue/Master Record Search.** The operator accesses the
C&P award screens by entering the CADJ command on the Ready Screen. Once
the Ready Screen entry edits have been successfully passed, the system
checks the Pending Issue File (PIF) to determine if claims control has
already been established.

\(1\) If no matching issue is found in the PIF, the claim must be
established in the system before award action can be initiated. The
system checks for the presence of a matching master record. If none is
found, a message is displayed to indicate CEST processing is required by
an individual with CEST authority. If a matching master record is found
and the full file key (file number, payee number, end product code,
benefit type and stub name) was entered on the Ready Screen, the system
defaults to CEST processing. If the full file key was not entered, the
operator is advised of the items required for claims establishment.

\(2\) If more than one pending issue is located, the operator may select
an existing issue on the S02 Screen or continue processing to create a
new issue, as appropriate.

b\. **Award Screen Processing**

\(1\) If processing an original claim, the award screens will have
minimal data displayed. For supplemental cases with an existing master
record, applicable data will be displayed from the master record.

\(2\) If all the necessary data have been entered on an award screen and
the ENTER key has been depressed, the system performs screen edits. When
all data have been successfully entered, the data are stored in the PIF.

c\. **Award Generation.** When all required data have been entered, the
operator may enter GAD (Generate and Display), GAP (Generate and Print)
or GAB (Generate and Bypass) in the NEXT SCREEN field. At this time, all
data in the PIF are edited for consistency and validity.

d\. **Authorization.** After the award has been generated and printed,
it must pass an authorization review. Following this review, the
authorizer may either authorize the award or disallow it and return it
for correction. If the award is authorized, the system formats the
transaction for processing by the RDPC and sends the appropriate data to
the letter-writing system.

e\. **System Updates.** Once a processing cycle has been run, the master
record file is updated. Any actions not accepted at this time are posted
to the NOES (Notices of Exception). The system clears the PIF of all
accepted actions and updates the rejected actions to show reprocessing
is required.

f\. **Requesting Screens**

\(1\) Access to the various screens is controlled so that any screen
requested may not exceed the command level authorized to the user.
Screens from a lower command level may be accessed. For example, an
adjudicator using the command CADJ may access 200-, 300- and 400-series
screens but cannot access the Authorization Screen 501.

\(2\) The system also restricts access to screens within a series if the
screen requested is inappropriate for the issue being processed. For
example, if, under the CDAT command, an operator requests a record which
has been established as a live compensation or pension benefit claim
(CPL), the system will not permit display of the burial screen (307)
since that would be an inappropriate screen for entry of data for the
established issue.

g\. **Data Entry Content and Format**

\(1\) Entry of data for Target processing must meet acceptable formats
required by the system edits. Statistical data entries other than those
normally used are identified in subsequent paragraphs providing
instruction for data entry on individual screens.

\(2\) Prefixing zeroes are not required if entering disability
percentages, dollar amounts or rating codes. They must be entered for
special monthly compensation codes, if applicable.

\(3\) Dates may be entered in several different formats as follows:

MM-DD-YY MM-D-YY MMDDYY

M-D-YY M-DD-YY

**NOTE:** If a date is entered without using hyphens, single-digit
months or days must be entered with a prefixed zero. Thus, February 3,
1990 would be entered as 020390.

\(4\) If the required entry is for month and year, e.g., establishment
of a diary control, the acceptable formats are as follows:

MYY M-YY MMYY MM-YY

**NOTE:** Leading zeroes need not be entered for single-digit months.

h\. **Special Processing Functions**

\(1\) Entry of DEL (Delete Data) in the NEXT SCREEN field will result in
deletion of that screen\'s data from the PIF and display of the menu
screen applicable to the command.

\(2\) Entry of RES (Restore Data) in the NEXT SCREEN field will result
in the system ignoring any data entered on the screen and retaining any
existing data previously entered. The prior data entered, if any, will
be displayed.

\(3\) Entry of BSP (Back-Space) in the NEXT SCREEN field of a 306 or 336
Screen will result in the redisplay of the 306 Income Screen for the
immediately preceding date.

\(4\) Entry of SUP (Suppress) in the NEXT SCREEN field of any screen
accessed under the CADJ command will result in the suppression of the
computer-generated letter. The 400 menu screen will be displayed with
the message LETTER SUPPRESSED BY ADJUD.

\(5\) Entry of UNS (Unsuppress) in the NEXT SCREEN field of any screen
accessed under the CADJ command will result in the removal of the letter
suppressor. The 400 menu screen will be displayed with the message
LETTER SUPPRESSION REVOKED.

**3.02 TARGET COMMANDS**

The following is a description of the various commands used in the
processing of C&P claims. Included is a brief description of what the
command does and how it is used.

a\. **CEST ([C]{.underline}laims [EST]{.underline}ablishment).** For
establishing an original or reopened claim.

b\. **CDEV ([C]{.underline}laims [DEV]{.underline}elopment).** For
generating requests for information to claimants and other entities.
Access is limited to the 200-series screens.

c\. **CDAT ([C]{.underline}laims [DAT]{.underline}a Entry).** Most often
used for processing of burial awards/disallowances but may also be used
to enter data on other screens. Access is limited to the 200- and
300-series screens. If this command is entered and a PIF record is not
found, processing defaults to CEST processing for establishment of the
claim prior to data entry.

d\. **CADJ ([C]{.underline}laims [ADJ]{.underline}udication).** For
processing awards and disallowances using all screens through the 400
series. If this command is entered and a PIF record is not found,
processing defaults to CEST processing for establishment of the claim
prior to award entry.

e\. **GAD/GAP/GAB ([G]{.underline}enerate [A]{.underline}nd
[D]{.underline}isplay/[G]{.underline}enerate [A]{.underline}nd
[P]{.underline}rint/[G]{.underline}enerate [A]{.underline}nd
[B]{.underline}ypass).** Generates and displays the award for review or
generates and prints the award or disallowance action. This entry can be
made in the NEXT SCREEN field of any award screen or in the SCREEN
NUMBER field on the Ready Screen.

f\. **CORR ([CORR]{.underline}ection).** Allows entry of changes to
specific fields of the master record.

g\. **STOP/SUSP/RESU (Stop/Suspend/Resume).** Allows the operator to
process terminations, suspensions or resumptions of C&P benefits.

h\. **PCLR ([P]{.underline}ending Issue
[CL]{.underline}ea[R]{.underline}).** For clearing an existing PIF and
associated controls with end-product credit if award action is not
required. Also used to take credit for nonaward actions if the issue has
not been previously established.

i\. **PCAN ([P]{.underline}ending Issue [CAN]{.underline}celled).** For
canceling an existing PIF with no end-product credit.

j\. **PCHG ([P]{.underline}ending Issue
[CH]{.underline}an[G]{.underline}e).** For changing specific control
data in the PIF.

**3.03 PENDING-ISSUE ESTABLISHMENT**

a\. Establishing a pending issue enables the operator to set up a
working file to hold the data entered for the issue and establish
appropriate controls. A pending issue must be established prior to entry
of award data. CEST, CDAT and CADJ may be used to establish issues.
Original claims are established using the CEST command (par. 16.02) with
accession of BIRLS records. CEST processing may also be used to
establish an issue if a matching master record exists. CEST processing
can be accomplished under the CEST, CDAT or CADJ commands. The PIF is
maintained at the RDPC and contains data required for award and
disallowance actions and other data relating to development, location of
the claim and the end product assigned. Data stored in the PIF may be
displayed on the VDT by use of the PINQ command.

b\. If the CEST command is entered and no master record is found, the
operator completes the Ready Screen, the necessary BIRLS screens and the
101 Screen in that order. When a master record is found, only the Ready
Screen and 101 Screen are required. The operator may also access the 601
Screen to process a change of address, if required, by entering 601 in
the NEXT SCREEN field of the 101 Screen.

c\. If the command CDAT or CADJ is entered with a full file key on the
Ready Screen and no existing PIF record is found, but a master record is
found, the system will display the 101 Screen. After acceptable
completion of the 101 Screen, the 300 or 400 Selection Screen will be
displayed if a selection was not entered in the NEXT SCREEN field of the
101 Screen. In addition, the operator may access the 200-series screens
or the 601 Screen, if desired, by entering the appropriate screen number
in the NEXT SCREEN field.

d\. If the Ready Screen entries have been successfully edited and
verified, the system searches the PIF for claims previously placed under
control.

\(1\) If no matching issue is found in the PIF, the system looks for a
master record. If found, establishment continues as described below. If
no master record is found, the pending issue must be established using
the CEST command.

\(2\) If only one matching issue is found, the system searches the
master record file as in (1) above.

\(3\) If multiple pending issues are located, the S02 Selection Screen
is displayed listing all issues found. The operator reviews the list for
possible duplicate issues. If it is obvious that the issue is not a
duplicate, the operator may press enter to continue. Existing issues may
be reviewed by entering an X in front of the issue to be reviewed. The
P01 Screen will be displayed. To discontinue establishment after
accessing a P01 Screen, enter END in the NEXT SCREEN field. If it is
determined after reviewing the S02 Screen that the new issue is a
duplicate of an existing issue, press the PA2 key to cancel
establishment.

\(4\) If an issue with the same file number, payee number and end
product already exists, the operator will be advised to establish a new
issue under an incremented end product, if applicable.

\(5\) If a single issue exists or is selected on the S02 Screen, the
system checks the Claim Location field for that issue.

\(a\) If the award has been GAP\'d, the Ready Screen will be displayed
with the message XXX PENDING AUTHORIZATION NO ACTION ALLOWED, where XXX
is the transaction/modifier.

\(b\) If the award has already been authorized, the Ready Screen is
displayed with the message PENDING ISSUE CLEARED. XXX PENDING
ACCEPTANCE. NO ACTION ALLOWED.

\(c\) If the award has neither been GAP\'d nor authorized, the claim
location will be updated to reflect the new location as indicated by the
command entered.

**3.04 CLAIMS DEVELOPMENT PROCESSING**

a\. **General.** The CDEV, CDAT or CADJ commands may be used to request
from a claimant or third party any additional evidence necessary for
processing the claim. Letters are generated nightly by the RDPC from
these entries. Entries are stored in the PIF and may be reviewed until
the letter is sent to print. At that time, the screen entries are
deleted from storage.

**NOTE:** If an award is GAP\'d on the same day that development screens
are completed, the development paragraphs are held for inclusion in the
award letter. If the award letter is suppressed by the system or through
entry on the 501 Screen by the operator, **NO** letter of any type will
be generated. Include the necessary development requests with the
locally generated award letter.

b\. **Development Screens.** The screens used for development purposes
are in the 200 series. The specific screens for development of C&P
claims are as follows:

201 - 3101 Data Selection

202 - Request for Military/Medical Data

203 - General Claimant Data

204 - Dependency Data

206 - Burial/Reimbursement Data

208 - Disability/Death Claim Letters

209 - Miscellaneous Letters

c\. **Development Procedures.** The operator enters the command (CDEV,
CDAT, CADJ) on the Ready Screen along with the password, screen number
and the file number. Upon successful completion of the Ready Screen, the
S02 Screen will be displayed if the payee number, end product code and
benefit type were not entered on the Ready Screen and more than one PIF
is located. The operator should then select the appropriate issue and
hit ENTER to continue. The screen layout display, field descriptions and
allowable entries are contained in chapter 17. The text of the
paragraphs produced from screen entries is contained in Chapter 20.

**3.05 CLAIMS DATA ENTRY PROCESSING**

a\. **General.** Certain awards and disallowances may be processed using
the CDAT command. Target continues to perform edits as to the
completeness and validity of entries as each screen is entered. When all
required screens have been entered, the operator enters a special
command instructing the system to generate and print the
award/disallowance action. At this time, additional edits are performed
prior to generation of the printed action. If all edits are not
successfully passed, a message is displayed advising the operator as to
the areas requiring further review.

b\. **Data Entry Screens.** The screens available under the CDAT command
are in the 300 series:

301 - Basic Rating Data

303 - Supplemental Letter Data - Rating

304 - Dependency

306 - Veteran\'s Income Report

336 - Children\'s Income Report

307 - Burial Award/Disallowance

This command also provides access to screens in the 200 series.

c\. **CDAT Procedure.** The nominal Ready Screen entries are command,
operator\'s password, file number and, if desired, the screen number. If
no screen number is requested, the 300 Selection Screen will be
displayed. If more than one issue exists, the operator may enter the
desired screen number, payee number, end-product code and benefit type
to obtain direct access to the desired issue. If the specific issue
desired is not indicated on the Ready Screen and more than one issue
exists, the S02 Selection Screen will be displayed.

**3.06 CLAIMS ADJUDICATION**

a\. The full range of C&P awards can be processed using the CADJ
command. This command provides access to all 200-, 300- and 400-level
screens.

**NOTE:** The 406 Screen is only available under the STOP, SUSP and RESU
commands.

b\. The minimal entries on the Ready Screen are the command, operator\'s
password and the file number. If the screen number is not entered, the
400 Selection Screen is displayed. If more than one issue exists and the
payee number, end-product code and benefit type were not entered on the
Ready Screen, the S02 Screen will be displayed. After selection of the
desired issue the requested screen or the 400 Selection Screen will be
displayed.

c\. If no pending issue is found and the full file key was not entered,
the Ready Screen is displayed with a message.

**3.07 CLAIMS AUTHORIZATION**

a\. The CAUT command is used to authorize an award or disallowance. CAUT
is the last action performed before the award or disallowance is sent to
TCS for processing. Access to this function is limited as required by
current directives, and operators may not authorize their own award
actions. Once an award or disallowance has been authorized, it may not
be accessed for changes nor may the action be CANcelled. The operator
must wait until the action has been updated before taking any necessary
corrective action.

b\. The required Ready Screen entries are the command, operator\'s
password and the file number. If a particular issue is not specified by
entry of payee number, end-product code and benefit type and more than
one issue is found, the S02 Selection Screen is displayed. The only
screen available under this command is the 501 Screen. The screen is
displayed with basic identifying data. For additional information on the
screen layout and allowable entries, see chapter 9.