TN 1 (05-95)
NL 00702.103 Documents Processed by M/TEXT
The typist will process incomplete notices from the MADCAP and MCS programs. These notices will be available as electronic images in M/TEXT and will automatically be placed in the I Queue for the module.
Notices are prepared from “ALERTS” generated from MADCAP, MCS, AJS-1 and AJS-3 and from “REVIEWS” generated by MADCAP, MCS, and SALT. Alert and Review notices will continue to be printed as they have been. In addition to the printed notices, electronic versions are also available on M/TEXT in the I Queue.
B. List of documents processed
M/TEXT will currently allow typists to process the following documents:
The typist will receive the folder/holder for the account number of the notice to be processed.
When adding UTIs to notices from object programs, the technician should attempt to add the UTIs used by the object program that generated the letter. If no appropriate UTI is available from the object program, the technician may use the paragraph that fits the situation best, regardless of the source. M/ TEXT trigger mark logic will generate the correct trigger marks based on enclosure remarks and the workload type being processed.
The typist will add or delete models or dictated text as requested on the SSA-573 to complete the notice. (See NL 00702.150 if an enclosure is called for in a paragraph that is being deleted.)
Once the document has been altered, the user cannot recall the document as it appeared in its original state.
NOTE: Unlike , SALT, MCS and MADCAP notices which will have all program input data established in M/TEXT and presented to the typist for manipulation, only a “shell” will be established in M/TEXT for AJS-1 and AJS-3 notices. The shell will consist of addressee name and address, account number, a standard referral paragraph and signature. Any UTIs/paragraphs and any missing shell information must be manually entered by the typist.
When the typist's action has been completed, the notice will be sent to the IR or IP Queue.
Follow local instructions for any notices that are received without the folder /holder.
D. Description of document identification
Each document in a queue is given a 15 character identifier:
|SSN|| ||9 digits|
|PIC|| ||3 digits (use * if PIC is less than 3 characters)|
|RIC|| ||2 characters (Record Identification Code)|
|DB||=||MCS Disapproved Claim|
|MB||=||MADCAP - Blind|
|XX||=||Not system generated (miscellaneous notice)|
|Sequence||1 character (alpha/numeric)|
Sometimes more than one document has the same SSN and PIC. In this case a tie breaker will be assigned by M/TEXT that will make each document name with the same SSN and PIC unique. This happens when there are multiple copies of the same letter that need completion, such as attorney or administrative law judge (ALJ) copies or when different letters are prepared for the same SSN and PIC. When this happens it may be necessary to look at each document with the same SSN and PIC to determine which is the correct document.
0-9 = tiebreaker that distinguishes documents in a queue that otherwise have the same name when the notices are loaded to M/TEXT. EXAMPLE: On system generated notices, 0 = ALJ copy, 1 = Attorney copy, 2 = original notice.
A-Z = tiebreaker that distinguishes documents in a queue or that is completely dictated, that have the same name once a notice is copied or saved manually. EXAMPLE: An original MADCAP notice in the I queue will have a sequence code = 0 or an original notice with a sequence code = 2. When it is copied, the subsequent tie breaker begins with A. Single documents not associated with copies will always have a sequence code = 0.