TABLE OF CONTENTS PART 1.0 CREATE NEW TRANSACTION TO SUPPORT INTERSTATE BUSINESS (CSENet 201) 1.1 Summary of Changes 1.2 Background 1.3 Description of Changes 1.4 Impact on States 1.5 Pilot Testing 1.6 Resource Materials PART 2.0 MODIFY CASE-ID AND OTHER-CASE-ID VALIDATION CRITERIA TO MATCH FCR CASE-ID VALIDATION CRITERIA (CSENet 205) 2.1 Summary of Changes 2.2 Background 2.3 Description of Changes 2.4 Impact on States 2.5 Pilot Testing 2.6 Resource Materials APPENDICES CSENet 2000 DATA BLOCK RECORD LAYOUT - EXCERPT CHARTS Chart A-1. CSENet 2000 Data Block Transaction Header Record for Transactions Sent to the OCSE Server Chart A-2. CSENet 2000 Information Data Block Record

PART 1.0 CREATE NEW TRANSACTION TO SUPPORT INTERSTATE BUSINESS (CSENet 201)

The Child Support Enforcement Network (CSENet) 2000 Application is being modified to include a notification process of a case ID not being found. This new notification transaction will enable a state to send information back to the originating state, indicating that the case ID it received does not match any cases on its system.

1.1 Summary of Changes

A new transaction is being added to the CSENet Application to provide states the ability to advise a sending state that the case ID received in a transaction is not recognized by the receiving state's system.

1.2 Background

States use a variety of transactions to convey this information. As a result, states have recommended a new transaction to provide a standard method for advising a sending state that the case ID it provided is not recognized. A similar transaction, CSI P FUINF, already exists for CSI transactions, which indicates that no case information is available for the requested case ID.

This new transaction provides standardized usage in CSENet communications and increases synchronization of states' interstate cases to support the National Interstate Case Reconciliation (ICR) Project. This change was shared and discussed with state representatives during CSENet Interstate Communications Teleconferences on February 25, 2004, April 8, 2004, and April 14, 2004.

1.3 Description of Changes

This enhancement adds a new transaction, MSC P REJCT, to indicate that a case ID match was not found with the case ID provided by the sending state in an LO1, MSC, ENF, EST, PAT, or COL transaction.  Because this new transaction clearly indicates to the sending state that the other case ID it sent does not match the receiving state's case ID, corrective actions can then be taken to identify the proper case ID.

This new MSC P transaction requires a Header record and an Information data block.  The Header record should be formatted according to current requirements and must contain REJCT in the Action-Reason field. Data from the rejected transaction must be entered in the following order in the Information-Text-Line-1 field of the Information data block:

• Transaction-Serial-Number,
• Action-Code,
• Functional-Type-Code,
• Transaction-Date, and
• Action-Reason (if applicable).

The first 24 positions of the Information-Text-Line-1 field must not be all spaces. If these positions contain spaces, states receive a new, non-fatal, warning message (W938), advising that the Information-Text-Line-1 field does not meet the validation criteria for this field.

The edits for this new transaction bypass the requirement for a Case data block. Further, the edits also bypass the requirement for a value in the Status-Change-Code field in the Information data block.

For more detailed information on the Header record and Information data block, see Appendix A, "CSENet 2000 Data Block Record Layout - Excerpt".

1.4 Impact on States

To send this new transaction, states need to add REJCT as a Reason code for the MSC P to their CSE systems.  States should also be prepared to receive transactions with this code.  To exchange this transaction, states must have open exchange agreements for the MSC Function code with their partners. To enable or expand exchange agreements, state representatives should contact their CSENet 2000 Technical Representative or the CSENet Service Desk.

States using the MSC P REJCT transaction will benefit from this additional automated tool for supporting ongoing case ID synchronization.

The software is being implemented on August 20, 2004, at 12 noon (Eastern).

1.5 Pilot Testing

States may elect to participate in pilot testing from July 26 - August 11, 2004, 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 loopback testing.

States may also elect to test receiving transactions from the CSENet Testdeck Application.

CSENet Technical Representatives will be available to provide analysis and feedback concerning test transactions during the July 26 - August 11 period. 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

TheCSENet 2000 Interface Guidance Document (IGD)can be viewed on the OCSE Website at: http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm. The Data Dictionary (Version 5.0) is contained in Appendix A, Valid Transactions Table in Appendix B, the Data Block Record Layout in Appendix C, and the Transaction Functional Matrix in Appendix D of the IGD.

These appendices are to be updated in the future.

Table of Contents

PART 2.0 MODIFY CASE-ID AND OTHER-CASE-ID VALIDATION CRITERIA TO MATCH FCR CASE-ID VALIDATION CRITERIA (CSENet 205)

The CSENet 2000 Application is being modified so validation criteria for case IDs match the criteria used by the Federal Case Registry (FCR).

2.1 Summary of Changes

The CSENet validation criteria for the Case-ID and Other-Case-ID fields are being changed to match the criteria used by the FCR, including the new edits being implemented by the FCR in the Minor Release 04-01.

2.2 Background

Several states have requested this enhancement as a means of ensuring the ongoing synchronization of interstate case IDs.

In preparation for the ICR, states have made changes to their systems to ensure that they are using the same case ID, formatted in the same manner, for all external data exchanges.  Since these changes are expected to be implemented prior to Minor Release 04-01, this CSENet enhancement should have no effect on interstate case processing.

2.3 Description of Changes

The validation criteria in the CSENet Application for both the Case-ID and Other-Case-ID fields are being changed to the following:

• First position must not be a space.
• Must not contain all zeros.
• Must not contain an asterisk (*) or backslash (\) in any position.

The following existing requirements continue to be enforced on the Case-ID and Other-Case-ID fields:

• Must be left-justified.
• Maximum length of 15 characters, alphanumeric(A/N).
• Edits are applied when the field is filled (non-blank).
• Must not contain all spaces, except in transactions where the field is not required, e.g., LO1 Responses and Acknowledgements.

Two new error codes and messages are being created:

• E936 - Invalid Case-ID value, and
• E937 - Invalid Other-Case-ID value.

The error code and message for the invalid Case-ID value are being implemented immediately with the software release.  The one for an invalid Other-Case-ID value will not be applied until February 18,2005, at 12 noon (Eastern), in accordance with states' requests for a transition period on this new edit.  During the transition period, states will receive a new, non-fatal, warning message (W937), advising that the Other-Case-ID field does not meet the validation criteria for this field.

2.4 Impact on States

If states have made all the changes necessary to comply with the modified format for the Case-ID field for the ICR, there should be no impact.  States may experience an increase in invalid CSENet transactions related to the Other-Case-ID field, if they do not make the necessary changes during the 6-month transition period.  During national teleconferences, state representatives agreed that any changes to their CSENet systems would be minor, and that they would like OCSE to move forward.

The software is being implemented on August 20, 2004, at 12noon (Eastern).

2.5 Pilot Testing

States may elect to participate in pilot testing from July 26 - August 11, 2004, 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 loopback testing.

States may also elect to test receiving transactions from the CSENet Testdeck Application.

CSENet Technical Representatives will be available to provide analysis and feedback concerning test transactions during the July 26 - August 11 period.  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

TheCSENet2000 Interface Guidance Document (IGD) can be viewed on the OCSE Website at: http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm. The Data Block Record Layout (Version 5.0) is contained in Appendix C, and Transaction Error Codes and Messages (Version 5.0) in Appendix E of the IGD.

These appendices are to be updated in the future.

Table of Contents

---

APPENDICES

A. CSENet 2000 DATA BLOCK RECORD LAYOUT - EXCERPT

This appendix contains excerpted sections of the CSENet 2000 Data Block Record Layout that are affected by the addition of the MSC P REJCT transaction.

Chart A-1 is provided for your information. Chart A-2 contains changes to the Status-Change-Code and Information-Text-Line-1 fields. Changes are highlighted in turquoise.

For the complete Data Block Record Layout, see Appendix C of theCSENet 2000 Interface Guidance Document.

Chart A-1:  CSENet 2000 Data Block Transaction Header Record for Transactions Sent to the OCSE Server

Field Name	Location	Length	A/N	Comments
Local-FIPS-State	1-2	2	N	Required The Local-FIPS-State must contain valid FIPS codes based on the jurisdiction table downloaded from the IRG. This always refers to the first two digits of your FIPS code. The CSENet 2000 application will convert the Local-FIPS-State and Other-FIPS-State on incoming transactions to keep the appropriate point of reference. You must have communications enabled for the specific Functional-Type-Code with the state with which you are communicating. The exchange of information agreement must be established in the FIPS Communication Matrix in the CSENet 2000 application.
Local-FIPS-County	3-5	3	N	Required The Local-FIPS-County must contain valid FIPS codes based on the jurisdiction table downloaded from the IRG. This always refers to the 3rd, 4th, and 5thdigits of your FIPS code. The CSENet 2000 application will convert the Local-FIPS-County and Other-FIPS-County on incoming transactions to keep the appropriate point of reference. You must have communications enabled for the specific Functional-Type-Code with the state with which you are communicating. The exchange of information agreement must be established in the FIPS Communication Matrix in the CSENet 2000 application.
Local-FIPS-Sub	6-7	2	A/N	The value of the Local-FIPS-Sub portion of the FIPS code will not be edited.
Other-FIPS-State	8-9	2	N	Required The Other-FIPS-State must contain valid FIPS codes based on the jurisdiction table downloaded from the IRG. This always refers to the first two digits of the state with which you are communicating. The CSENet 2000 application will convert the Local-FIPS-State and Other-FIPS-State on incoming transactions to keep the appropriate point of reference. You must have communications enabled for the specific Functional-Type-Code with the state with which you are communicating. The exchange of information agreement must be established in the FIPS Communication Matrix in the CSENet 2000 application.
Other-FIPS-County	10-12	3	N	Required The Other-FIPS-County must contain valid FIPS codes based on the jurisdiction table downloaded from the IRG. This always refers to the 3rd, 4th, and 5thdigits of the state with which you are communicating. The CSENet 2000 application will convert the Local-FIPS-County and Other-FIPS-County on incoming transactions to keep the appropriate point of reference. You must have communications enabled for the specific Functional-Type-Code with the state with which you are communicating. The exchange of information agreement must be established in the FIPS Communication Matrix in the CSENet 2000 application.
Other-FIPS-Sub	13-14	2	A/N	The value of the Other-FIPS-Sub portion of the FIPS code will not be edited.
CSENet 2000-Version-Number	15-17	3	N	Required Valid values for this field are: 003 States must fill with the CSENet 2000 version number 003.
Transaction-Serial-Number	18-29	12	N	Required Valid values for this field are: 1 or greater The value must be right justified and zero filled to the left. This is a unique sequential number assigned to each transaction and it must be generated by the state CSE system. Can be used to prevent the sending and/or processing of duplicate transactions.
Error-Reason-Code	30-31	2	A/N	This field is reserved for a future version. For the current version, this field must be blank-filled.
Transaction-Type	32-33	2	A/N	This field is reserved for a future version. For the current version, this field must be blank-filled.
Action-Code	34	1	A/N	Required Must contain a valid Action code.Describes the action of the transaction. Valid values for this field are: R - Request (an initiating transaction) A - Acknowledgment (Acknowledgment of receipt of request) P - Provision (Provision of information) M - Reminder (Used when a response is overdue) U - Update (Update of previously transmitted request) C - Cancel (Cancellation of previous request)
Functional-Type-Code	35-37	3	A/N	Required Must contain a valid Functional Type code. Indicates the child support business function. Valid values for this field are: LO1 - Quick Locate CSI - Case Status Information ENF - Enforcement MSC - Managing State Cases (formerly Miscellaneous) PAT - Paternity Establishment EST - Order Establishment COL - Collection
Transaction-Date	38-45	8	N	Required The date the transaction was generated. Date must not be greater than the current date.
Case-ID	46-60	15	A/N	Required The case ID used by your jurisdiction. Required for all transactions except LO1 Responses and Acknowledgments.
Other-Case-ID	61-75	15	A/N	Required The case ID used by the jurisdiction with which you are communicating. Required for Responses, Acknowledgments, and CSI transactions except for CSI P RINIT and CSI P RRESP.
Action-Reason	76-80	5	A/N	Required Required for CSI transactions. If used, must be in conjunction with Action and Functional Type codes pursuant to the Valid Transactions document.
Action-Resolution-Date	81-88	8	N	This field should be used in conjunction with certain Action-Reason codes to indicate the date on which an event occurs.
Attachments-Ind.	89	1	A/N	Required Indicates whether attachments should accompany this transaction. Valid values for this field are: Y - Yes N - No If this indicator is set to Y, then an Information data block must be included. The Information data block should list the attachments being sent.
Case-Data-Ind.	90	1	N	Required Indicates whether a Case data block is included in this transaction. Valid values for this field are: 0 - Case data block is not included in this transaction 1 - Case data block is included in this transaction This indicator can be 0 or 1 for all transactions with an Action code equal to A, C, or M. For COL, MSC, CSI Requests and Updates, this indicator can be 0 or 1. For CSI Responses, this indicator must be 1 if the 2ndcharacter of the Action-Reason code is S. This indicator must be set to 1 for all other transactions.
NCP-Identification-Ind.	91	1	N	Required Indicates whether an NCP Identification data block is included in this transaction. Valid values for this field are: 0 - NCP Identification data block is not included in this transaction 1 - NCP Identification data block is included in this transaction This indicator can be 0 or 1 for all transactions with an Action code equal to A, C, or M and COL, MSC and CSI transactions. This indicator must be 1 for all other transactions.
NCP-Locate-Data-Ind.	92	1	N	Required Indicates whether an NCP Locate data block is included in this transaction. Valid values for this field are: 0 - NCP Locate data block is not included in this transaction 1 - NCP Locate data block is included in this transaction This indicator must be set to 1 for PAT, EST, ENF Requests and Updates. This indicator must be set to 1 for LO1 Responses if the 2ndcharacter of the Action-Reason code is S. This indicator can be 0 or 1 for COL, MSC, CSI transactions. This indicator can be 0 or 1 for PAT, EST and ENF Responses.
Participant-Data-Ind.	93	1	N	Required Indicates the number of Participant data blocks included in this transaction. Valid values for this field are: 0 - Participant data block is not included in this transaction 1 - One Participant data block is included in this transaction 2 - Two Participant data blocks are included in this transaction 3 - Three Participant data blocks are included in this transaction 4 - Four Participant data blocks are included in this transaction 5 - Five Participant data blocks are included in this transaction 6 - Six Participant data blocks are included in this transaction 7 - Seven Participant data blocks are included in this transaction 8 - Eight Participant data blocks are included in this transaction 9 - Nine Participant data blocks are included in this transaction This indicator must be set to 2 or greater for PAT, EST, ENF Requests and Updates. These transactions require a minimum of two Participant data blocks: one containing the custodial party's information, and at least one additional Participant data block containing dependent information. This indicator must be at least 1, and may be 2-9 for CSI Responses if the 2ndcharacter of the Action-Reason code is S.
Order-Data-Ind.	94	1	N	Required Indicates the number of Order data blocks included in this transaction. Valid values for this field are: 0 - Order data block is not included in this transaction 1 - One Order data block is included in this transaction 2 - Two Order data blocks are included in this transaction 3 - Three Order data blocks are included in this transaction 4 - Four Order data blocks are included in this transaction 5 - Five Order data blocks are included in this transaction 6 - Six Order data blocks are included in this transaction 7 - Seven Order data blocks are included in this transaction 8 - Eight Order data blocks are included in this transaction 9 - Nine Order data blocks are included in this transaction This indicator must be 1 or greater for ENF Requests or Updates.
Collection-Data-Ind.	95	1	N	Required Indicates the number of Collection data blocks included in this transaction. Valid values for this field are: 0 - Collection data block is not included in this transaction 1 - One Collection data block is included in this transaction 2 - Two Collection data blocks are included in this transaction 3 - Three Collection data blocks are included in this transaction 4 - Four Collection data blocks are included in this transaction 5 - Five Collection data blocks are included in this transaction 6 - Six Collection data blocks are included in this transaction 7 - Seven Collection data blocks are included in this transaction 8 - Eight Collection data blocks are included in this transaction 9 - Nine Collection data blocks are included in this transaction This indicator must be 1 or greater for COL Responses.
Information-Ind.	96	1	N	Required Indicates whether an Information data block is included in this transaction. Valid values for this transaction are: 0 - Information data block is not included in this transaction 1 - One Information data block is included in this transaction If the Attachments-Ind. is Y, this field must be set to 1.
Sent-Date	97-104	8	N	This field may be filled by the state CSE system with the date the transaction was generated or sent.
Sent-Time	105-110	6	N	This field may be filled by the state CSE system, with the time the transaction was generated or sent. If used, the time must be in the military format of HHMMSS.
Due-Date	111-118	8	N	This field is reserved for a future version. For the current version, this field must be blank-filled.
Response-Date	119-126	8	N	This field is reserved for a future version. For the current version, this field must be blank-filled.
Overdue-Ind.	127	1	N	Required This field is used to indicate that a response is overdue. This field must be filled with 0.

Chart A-2: CSENet 2000 Information Data Block Record

Field Name	Location	Length	A/N	Comments
Status-Change-Code	1	1	A/N	Required* This field is used to indicate whether the case status has changed. Valid values for this field are: O - Open C - Closed *Not required for MSC P REJCT transactions.
New-Case-ID	2-16	15	A/N	This field will be used to transmit a new IV-D case ID to another State when the case ID has been changed.
Information-Text-Line-1 For MSC P REJCT, data must be entered in the following order: Transaction-Serial-Number Action-Code Functional-Type-Code Transaction-Date Action-Reason	17-96 17-28 29 30-32 33-40 41-45	80 12 1 3 8 5	A/N N A/N A/N N A/N	Required Contains free-form text except for MSC P REJCT transaction. Required if the Attachment Indicator = Y. Required for the MSC P REJCT transaction. The first 24 positions of this line must not be all spaces.
-Line-2 -Line-3 -Line-4 -Line-5	97-176 177-256 257-336 337-416	80 80 80 80	A/N A/N A/N A/N	Required All 4 lines contain free form text. Required if the Attachment Indicator = Y.