**FPLS Release 03-01 Manifest Minor**

**Questions & Answers from May 6 & 8 Manifest Calls**

**and May 28 & June 3 Specification Calls**

**FCR #1561 -- Add an additional DoD code of "P" for Pension/Retired
Personnel**

1.  **Question:** When this change goes into effect, will states receive
    the "P" code for pensioners on previously reported participants
    (i.e., is this change retroactive)?

**Answer: No. States will begin seeing the new code of "P" for pension
and retired personnel the first quarter that DoD reports the information
to the NDNH.**

**FCR #1131 -- Delete the State-Submitted SSN field from the FCR
Reconciliation File**

2.  **Question:** When a state submits a name and SSN that is different
    from the name and SSN that is verified through SSA's process, will
    you notify the state via an error record?

> ***Answer: In the situation described above, a state receives an
> acknowledgement record (Record Type 'FS') with a SSN Validity Code
> explaining the process used to verify, identify or correct the SSN. In
> that record, the SSN Field contains the information submitted by the
> state as the person\'s SSN. The Provided/Corrected SSN Field contains
> the identified or corrected SSN for the person found during the SSN
> verification routines. The FCR Primary SSN Field contains the SSN
> stored on the FCR as the person\'s primary SSN. The FCR Primary First,
> Middle and Last Names contain the name of the person stored on the FCR
> that verified with the Primary SSN.***

##### FCR #1180 -- Create default values for specific NDNH data that are invalid

3.  **Question:** For those fields that are defined as "filler," will
    you notify the states of which fields are being defaulted?

> ***Answer: The defaulted values in a record are returned to states
> when and if that particular record is matched and returned in an
> NDNH-to-FCR Proactive Match, an FCR-to-NDNH Proactive Match, or an
> NDNH Locate. However, the response record does not include an
> indicator that one or more of the values therein were defaulted.***

#### 

**FCR #1653 -- Do not store invalid FIPS County Codes (This is a future
enhancement proposed for states' consideration).**

4.  **Question:** Does CSENet accept Central Registry FIPS?

> ***Answer: Yes, a County FIPS that equal '000' is valid for all
> states, territories and the District of Columbia.***

5.  **Question:** How is the FCR going to know the Central Registry
    address?

> **Answer: The FCR will not know the Central Registry address. We do
> not store addresses on the FCR and the FIPS County Code is an optional
> field.**

6.  **Question:** How is OCSE handling invalid FIPS codes on the FCR
    now? (State representatives suggest that OCSE provide a list to
    states so they can correct.)

> ***Answer: On person transactions or change case transactions, the
> FIPS County Code must be numeric or spaces. This edit does allow all
> zeroes in the FIPS County Code. Warning Code TW018 (invalid FIPS
> County Code) is returned when the field fails the edit.***
>
> ***On add case transactions, the FIPS County Code must be a valid FIPS
> County Code for the state. Warning Code TW018 (invalid FIPS County
> Code) is returned when the field fails the edit. The FCR has every
> state set up the internal FIPS County Code table with '000' as a valid
> value. Although the FCR edits the FIPS County Code on add case
> transactions against the FIPS County Codes for the state, zeroes are
> allowed.***

7.  **Question:** How do we get the correct tribal FIPS codes?

> ***Answer: OCSE will research the tribal FIPS codes and provide this
> information to each IRG State Administrator.***

8.  **Question:** Is the use of the FIPS code positions 6 and 7 being
    discontinued?

> **Answer: OCSE conducted a conference call with states on May 14, 2003
> to discuss removing positions 6 and 7 of the FIPS codes from the IRG.
> The results of the call were as follows:**
>
> ***In the last release of the IRG application, 20 additional local
> Child Support Offices address types were added to the county level.
> The purpose of adding the 20 address types was to enable counties that
> have more than one office providing the same service to enter
> addresses for each office, as well as to standardize all address types
> for the IRG. Currently there are 20 states using the state extension
> code to identify specific address types within a county. OCSE
> representatives had suggested that the Local CSE office address types
> be used for this purpose instead.***
>
> ***During this discussion, a number of Workgroup members indicated
> that the 6^th^ and 7^th^ digits of the state extension code are
> currently used to identify county offices. They further indicated that
> removing the state extension code would require major system
> programming and therefore have a large impact on states. Most members
> were opposed to this change. Further decisions will have to take place
> on this issue.***

**CSENet \# 98 - Case closure modification to update closing reason
codes**

### **Question:** When will the existing documentation, such as the CSENet 2000 IGD including the Valid Transactions Table and TFM, be revised to include the case closure modification and available to states?

> ***Answer: August 22, 2003.***

**General Questions**

9.  **Question:** How do you make changes to race code for USDA and will
    there be a change to race code on the FCR?

> **Answer: We do not store race code on the FCR.**

10. **Question:** When will the specifications for FPLS Release 03-01 be
    available to states?

> Answer: The specifications were posted to the OCSE web site May 22,
> 2003.

11. **Question:** Can states use the FCR test database to test external
    locate sources?

> Answer: No, currently the FCR test database is available to test the
> NDNH and SVES as locate sources.

12. **Question:** How do states get set up for the FCR test database?

> **Answer: States should contact their State Technical Support (TS)
> Liaison who can provide documentation on the set-up procedures. Please
> refer to the following website for your assigned State TS Liaison at:
> <http://www.acf.hhs.gov/programs/cse/newhire/contacts/fcrtscontacts.htm>.**

13. Question: When will the FPLS Manifest enhancements be implemented?

> **Answer: OCSE's implementation of FPLS Release 03-01 is scheduled for
> Friday, August 22, 2003.**

14. Question: During one of the manifest conference calls, you discussed
    the unverified SSN match project. Are you looking for volunteer
    states to participate in this match?

> **Answer: No**