06 predecessor successor actual file es2psa
015D ====== Predecessor / Successor Actual File (ES2PSA) ====== ES2PSA - Length 51 - Revised 9/8/2006
Columns | Len | Key | Type | COBOL Field Name | Description & Notes | |
| 1 | 15 | 15 | Key | Char | PSA-SESA-ID | Predecessor or successor SESA ID; if P-S type is "P", this is a successor pointing to its predecessor; if P-S type is "S", this is a predecessor pointing to its successor |
| 1 | 10 | 10R | Key | Char | PSA-ACCT | U-I account number portion of the SESA ID shown above |
| 11 | 15 | 5R | Key | Char | PSA-RUN | Reporting unit number portion of the SESA ID shown above |
| 16 | 21 | 6 | Key | Num | PSA-POSTED-DATE-COMPL | "Complement" to the posted date, set to 999999 minus posted date (for instance, a posted date of 2/17/2007 (converted to yymmdd format as 070217) would appear as (999999 – 070217) = 929782. The date complement is needed to ensure that the newest date will appear first in the sorted file, while successively older postings are relegated farther to the back |
| 22 | 22 | 1 | Key | Char | PSA-P-S-TYPE | Identifier for whether the following SESA ID is a predecessor ("P") or a successor ("S") to the SESA-ID listed above |
| 23 | 37 | 15 | Key | Char | PSA-P-S-SESA-ID | Predecessor's or successor's SESA ID; if the P-S type is "P", this is a predecessor to the SESA ID shown above; if P-S type is "S", this is a successor instead |
| 23 | 32 | 10R | Key | Char | PSA-P-S-ACCT | U-I account number portion of the predecessor/successor SESA ID |
| 33 | 37 | 5R | Key | Char | PSA-P-S-RUN | Reporting unit number portion of the predecessor/successor SESA ID |
| 38 | 43 | 6 | Num | PSA-POSTED-DATE | Date when this actual predecessor or successor relationship was first shown on this file (yymmdd format) | |
| 44 | 49 | 6 | Char | PSA-TRANSFER-DATE | Date when the change-of-ownership took place, from predecessor to successor; this has the standard yymmdd format; however, if this date is not yet known, it can be left blank | |
| 50 | 51 | 2 | Char | PSA-SOURCE | Origination of this predecessor/successor information; valid values for the code are- 'AR' = ARS (Annual Refiling Survey) 'BL' = BLS Weighted Match 'ED' = EDI Center 'ER' = Employer 'EX' = Extract 'FS' = Other Federal/State Program 'HS' = Historical 'MD' = Media 'MW' = Multiple Worksite Report (MWR) 'OT' = Other data source 'RL' = Record linking 'SD' = SUTA Dumping 'UI' = Unemployment Insurance (U-I) department 'WR' = Wage record data | |
Predecessor / Successor Actual File Data Set Name: WS.ES202.PREDSUCC.ACTUAL Service Center DSN: YBUssX.A145.PREDSUCC.ACTUAL, ('ss' = State FIPS code) Type of File: VSAM indexed File Layout: ES2PSA CICS ID: ES2PSA (standard); EssPSA (Service Center; ss=State) The Predecessor/Successor Actual File provides a list of all predecessors and successors that have been associated with a given account. One relationship is listed in each record, so there can be multiple predecessor and multiple successor listings for any given establishment. These are sorted according to their "posting date", when they first appear on the file. The newest relationships show up first, so they can be given greater credence than those associations that date back several quarters or even years. This file is paired with the Potential Predecessor/Successor File to list all suspected and validated predecessors and successors on the ES2G screen. The Predecessor / Successor Notes File is also connected, allowing up to 145-byte narratives to be listed with a P/S pairing. Before Version 9, the predecessor and successor listings were placed on the Micro File. Now the PSA File shows these pairings, but in a more complete manner, since the many-to-one, etc., relationships can be shown, along with transfer dates, source codes, etc. The PSA File is used wherever the P/S information from the Micro File had been utilized in the past. There are several places in batch processing where PSA data are used, such as the micro edits (to flag large new employers without a predecessor), the predecessor / successor edits (Jobs 015D and 015S), and in building older-version Micro Files for export in the 076N and 076P jobs. In CICS, the most prevalent use of PSA data is in the ES2G transaction, which has separate screens for actual and potential predecessor and successor relationships. ES2E uses the pred/successor information for the same micro edit check already mentioned for the batch side. | ||||||
Related Links
