Child Support Enforcement Network
Release 06-01 – Minor: August 18, 2006
Release Specifications
May 18, 2006
1.0 ORDER ARREARS FREQUENCY AMOUNT CORRECTION (OCSE REF # 158)
The Child Support Enforcement Network (CSENet) 2000 Application is being modified to support the current requirements as stated in the CSENet 2000 Interface Guidance Document, Appendix C, "Data Block Record Layout".
1.1 Summary of Changes
The CSENet Application is being modified to validate transactions when the Order-Arrears-Freq field is filled and the Order-Arrears-Freq.-Amount field contains a zero value. The Order-Arrears-Freq and Order-Arrears-Freq.-Amount fields are required for Enforcement (ENF) Requests, Updates, and Responses, as well as Paternity (PAT) and Establishment (EST) Responses.
1.2 Background
This problem was identified by a state that received a validation error when it sent a transaction that contained a value in the Order-Arrears-Freq field and a zero value in the Order-Arrears-Freq.-Amount field.
The CSENet Data Block Record Layout specifies that the Order-Arrears-Freq.-Amount may be filled with a zero value. However, the CSENet Application currently invalidates transactions that contain a value in the Order-Arrears-Freq. field and a zero value in the Order-Arrears-Freq.-Amount field. Under these conditions, an error message (E436, "Mandatory Order Arrears Freq. Amount Missing") is returned to the originating state and the transaction is not delivered to its destination.
1.3 Description of Changes
Modify the validation criteria to allow transactions containing a valid value in the Order-Arrears-Freq. field and a zero value in the Order-Arrears-Freq.-Amount field.
1.4 Impact on States
States will no longer receive the error code and message E436, "Mandatory Order Arrears Freq. Amount Missing", if the Order-Arrears-Freq. field is filled with a valid value, and the Order-Arrears-Freq.-Amount field contains a zero value.
1.5 Pilot Testing
States may elect to participate in pilot testing to verify system programming. Pilot testing provides states with an opportunity to exchange transactions via test data sets with:
- the CSENet server using FIPS code 9100000,
- other states participating in pilot testing, or
- their own system through loop-back testing.
The pilot testing will be conducted between July 24, 2006 and August 11, 2006. State representatives should contact their CSENet technical representative or the CSENet Service Desk at 1.800.258.2736 or CSENet.2000@lmco.com to participate.
1.6 Resource Materials
The CSENet 2000 Interface Guidance Document (IGD) and its appendices can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm.
The IGD and its appendices are to be updated later this year.
Material related to Release 06-01 Minor can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm.
Table of Contents
2.0 RACE FIELD VALUE CORRECTION (OCSE REF # 187)
The CSENet 2000 Application is being modified to support the current requirements as stated in the CSENet 2000 Interface Guidance Document, Appendix C, "Data Block Record Layout", to convey correct values for race.
2.1 Summary of Changes
The CSENet Application is being modified to ensure that only transactions with valid values for the non-custodial parent’s (NCP’s) race are validated for routing to other states.
2.2 Background
The CSENet Data Block Record Layout currently specifies values of W, B, I, A, S, X, and space for the Race field.
The problem was identified by a state which received a transaction from another state that had a value of 'O' in the Race field. This transaction should have been invalidated by the CSENet Application and returned to the originating state.
2.3 Description of Changes
Modify the CSENet Application to ensure that only valid values for the NCP’s race are validated for routing to other states. The valid values are; W, B, I, A, S, X, and space.
2.4 Impact on States
- States that enter a value other than those listed above will receive the error code and message E830, "Invalid Race in NCP ID block".
- Only transactions with valid values for race will be forwarded to states.
2.5 Pilot Testing
States may elect to participate in pilot testing to verify system programming. Pilot testing provides states with an opportunity to exchange transactions via test data sets with:
- the CSENet server using FIPS code 9100000,
- other states participating in pilot testing, or
- their own system through loop back testing.
The pilot testing will be conducted between July 24, 2006 and August 11, 2006. State representatives should contact their CSENet technical representative or the CSENet Service Desk at 1.800.258.2736 or CSENet.2000@lmco.com to participate.
2.6 Resource Materials
The CSENet 2000 Interface Guidance Document (IGD) and its appendices can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm.
The IGD and its appendices are to be updated later this year.
Material related to Release 06-01 Minor can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm.
Table of Contents
3.0 VALIDATE NEW-CASE-ID FIELD FORMAT AND REQUIRE THE NEW-CASE-ID FIELD FOR THE MANAGING STATE CASES ? PROVISION/RESPONSE, CHANGE LOCAL CASE ID TRANSACTION (OCSE REF # 226)
The CSENet 2000 Application is being modified to apply the same validation criteria for the New-Case-ID field as those that are applied to the Case-ID and Other-Case-ID fields. Further modifications will require the presence of the Information data block and the New-Case-ID field in the Managing State Cases ? Provision/Response, Change Local Case ID Transaction (MSC P GSCAS).
The specifications for this change were previously posted to the OCSE Website as part of Release 05-02, with the notation that the change would be implemented in 2006.
Note: The code number for the new error message, "Mandatory New Case ID is Missing", will be E942 instead of E940.
The specification can be accessed at:
http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm
Table of Contents
4.0 DELETE OBSOLETE CASE CLOSURE TRANSACTIONS (OCSE REF # 230)
The CSENet 2000 Application is being modified to delete obsolete case-closure transactions that no longer match the criteria that are outlined in the Code of Federal Regulations (CFR) [45 CFR 303.11 (b)].
The specifications for this change were previously posted to the OCSE website as part of Release 05-02, with the notation that the change would be implemented in 2006. The specification can be accessed at:
http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm
Table of Contents
5.0 DATE FIELD CORRECTIONS (OCSE REF # 257)
The CSENet 2000 Application is being modified to support the current requirements as stated in the CSENet 2000 Interface Guidance Document, Appendix C, "Data Block Record Layout".
5.1 Summary of Changes
Modify the validation criteria to ensure that the date field dependencies are accurately documented and validated.
5.2 Background
A state received erroneously validated transactions that contained a Residential-Address-End-Date field with an earlier date than the date in the Residential-Address-Effective-Date field and an Order-End-Date field and Order-Effective-Date field with the same date values. A further analysis of the date range fields revealed that the validation software was not checking for an "equals" condition.
5.3 Description of Changes
Implement validation criteria for the residential address date fields to ensure that the Residential-Address-End-Date field cannot contain a value that is earlier than or equal to the Residential-Address-Effective-Date field. A new error code and message are being created, which will be generated when there is an improper date in the Residential-Address-End-Date field.
In addition, the validation program is being changed so that the same date may not be used in the following pairs of fields:
- Order-Cancel-Date and Order-Effective-Date;
- Arrears-TANF-Thru-Date and Arrears-TANF-From-Date;
- Arrears-Non-TANF-Thru-Date and Arrears-Non-TANF-From-Date;
- Foster-Care-Thru-Date and Foster-Care-From Date;
- Medical-Thru-Date and Medical-From-Date;
- Order-End-Date and Order-Effective-Date; and
- Residential-Address-End-Date and Residential-Address-Effective-Date.
5.4 Impact on States
States sending transactions with a residential address end date that is equal to or earlier than the effective date will receive the new error code and message: E940 – "Res Address End Date <= Res Address Eff Date".
5.5 Pilot Testing
States may elect to participate in pilot testing to verify system programming. Pilot testing provides states an opportunity to exchange transactions via test data sets with:
- the CSENet server using FIPS code 9100000,
- other states participating in pilot testing, or
- their own system through loop back testing.
The pilot testing will be conducted between July 24, 2006 and August 11, 2006. State representatives should contact their CSENet technical representative or the CSENet Service Desk at 1.800.258.2736 or CSENet.2000@lmco.com to participate.
5.6 Resource Materials
The CSENet 2000 Interface Guidance Document (IGD) and its appendices can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm.
The IGD and its appendices are to be updated later this year.
Material related to Release 06-01 Minor can be viewed on the OCSE Website at:
http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm.
