- 22.214.171.124 Delete PICF Linkage Records (Command Code TSDEL)
- Exhibit 2.2.5-1 Command Code TSDEL
- Exhibit 2.2.5-2 Command Code TSDEL — Input and Output Screen Displays
December 16, 2014
(1) This transmits revised IRM 2.2.5, Partnership Control System, PCS Command Code TSDEL.
(1) This document was updated to correct minor typographical errors.
Terence V. Milholland
Chief Technology Officer
This process accesses Partnership/Partner records and deletes the linkage on the database. A TSDEL-REC is written to GENDATA for subsequent batch processing.
When errors are detected on lines 1 or on lines 2-12 (as indicated by "**" in screen positions 39-40) one of the following messages will be displayed on line 13 of the input screen. Where appropriate, the operator should correct the input screen element and re-enter. If all the screens have been successfully processed, the message "REQUEST COMPLETED" will be displayed on line 13.
Message Condition ** CNTRL PRTNRSHP ON LINES 2–12 An entry on lines 2–12 matched the Control entry on input line 1. ** INVALID MFT Not numeric, or not valid for PICF. ** INVALID TAX PERIOD Not YYYYMM format or valid. ** INVALID TIN TIN does not have a valid configuration. ** INVALID TIN, F/S TIN does not have a valid configuration. ** MFT/TAX PERIOD INCONSISTENT Self explanatory. PARTNER NOT LINKED TO PARTNERSHIP Self explanatory. ** PARTNER RECORD NOT LINKED ON PICF Indicates the input Partner record TIN/FS/MFT/Tax Period is not linked to the input Partnership on line 1. ** PARTNER RECORD NOT ON PICF Indicates the input Partner TIN/FS/MFT/Tax Period is not on PICF. ** TIN/MFT INCONSISTENT Self explanatory. CC TSDEL AVAILABLE FOR CAMPUS TERMINAL INPUT ONLY Self explanatory. CC-DEFINER NOT VALID WITH TSDEL CC-definer is not blank or T. CONTROL FS/MFT INCONSISTENT Self explanatory. CONTROL MFT/TAX PERIOD INCONSISTENT MFT and Tax Period are not consistent. I/O ERROR (PICF, FIND, XXXX) Computer error, try again. I/O ERROR (PICF, REPLACE, XXXX) Computer error, try again. INVALID CONTROL MFT Not numeric, or not valid for PICF. INVALID CONTROL TAX PERIOD Not YYYYMM format. INVALID CONTROL TIN, F/S TIN does not have a valid configuration and File Source Indicator. LINES 2–12 BYPASSED Character in positions 37–40, lines 2–12 are "BYOK" or "BYDR" . MFT 47 INVALID WITH TSDEL MFT 47 is not valid for PICF. PARTNERSHIP RECORD NOT ON PICF Indicates the input Key Case TIN/FS/MFT/Tax-Period (line 1) is not on the PICF. PN TIN CHANGED TO nnnnnnnnnnnn PICF account is Changed-TIN case. Displays new edited TIN. Re-input using new TIN. PS TIN CHANGED TO nnnnnnnnnnnn PICF account is Changed-TIN case. Displays new edited TIN. Re-input using new TIN. REQUEST NOT PROCESSED INPUT ON LINES 1–12 ONLY There is data on line 13. Line 13 is reserved for messages.
TSDEL Input Screen Format
Record Element Description
|1||1||6||TSDEL Command Code Definer|
|2||1||7–18||Edited Key Case TIN (Item 2)|
|3||1||20–21||Key Case MFT (NN) (Item 3)|
|4||1||23–28||Key Case Tax Period (YYYYMM) (Item 4)|
|5||2–12||1–12||Edited Investor TIN (Item 5)|
|6||2–12||14–15||Investor MFT (NN) (Item 6)|
|7||2–12||17–22||Investor Tax Period (YYYYMM) (Item 7)|
Note: Item numbers in parenthesis refer to those on Form 8335.
TSDEL Input Screen Example
Record Element Description
|1||1||6||TSDEL Command Code Definer — Space|
|2||1||7–18||Key Case TIN "16–1234567"|
|3||1||20–21||Key Case MFT "06"|
|4||1||23–28||Key Case Tax Period "199512"|
|5||2||1–12||Investor TIN "02–1234567"|
|6||2||14–15||Investor MFT "02"|
|7||2||17–22||Investor Tax Period "199512"|
|3,4||These have the same format as line 2|
TSDEL Input Screen — Example of re-input of corrected screen
The processing stopped when an error was encountered on line 5. The original output screen displayed "**" in positions 39–40, which the operator has overlaid with "DR" sine line 5 is to be dropped and not processed.
The lines following line 5 were not processed as shown by blanks in positions 39–40. This screen will be transmitted again by depressing the "ENTER" key after entering the entry codes (line 8, positions 24–25) after the last entry on the screen.
TSDEL Output Screen — Example 1
The Partnership record shown on line 1 is not on the PICF. The processing stopped when this error was encountered and lines 2–4 were not processed as shown by blanks in positions 39–40 of those lines.
TSDEL Output Screen — Example 2
This screen was re-input since an error had been encountered previously on line 5. Another error was encountered on line 7 and the processing stopped. Line 8 was not processed.