2005 - Transaction County-ID Does Not Match MEDS - Critical

This alert is generated for client information update transactions (e.g., EW12s) when the County ID (county, serial number, and FBU if reported) in the transaction does not match any current, pending or future County ID on MEDS in the Primary (INQM), Special 1 (INQ1), Special 2 (INQ2), Special 3 (INQ3), Food Stamp (INQF) or Pending Application (INQ4) segments.

This alert is generated for MEDS-ID change transactions (e.g., EW10s) when:

There is a current or ongoing active federal or county controlled case in the MEDS Primary, Special 1, Special 2, Special 3, IE/RR, Food Stamp or Pending Application segments; and
The County ID (county and serial number) in the transaction does not match either the current, pending, or future County ID in the MEDS Primary, Special 1, Special 2, Special 3, Food Stamp or Pending Application segments.

This alert is generated on Food Stamp modify transactions (e.g., FX40s) when the client is not active in another county and the transaction County ID (county and serial number) does not match MEDS for the update segment and time period indicated on the transaction.

This alert is generated for all other modify transactions (e.g., EW40s) when:

The client is not active in another county; and
The full transaction County ID does not match MEDS for the update segment and time period indicated on the transaction.

When the transaction Aid Code does not match MEDS and MEDS has Aid Code 38 eligibility, the transaction Aid Code will be compared to the original Aid Code (i.e., the eligible Aid Code reported by the county before MEDS rolled the eligibility into Aid Code 38) before the alert is issued.

Before issuing alert 2005 for modify transactions, MEDS will adjust the effective date forward, if possible, to match an eligibility update that may have been adjusted forward due to a current month eligibility conflict. If the effective date was adjusted and the update still could not be applied, alert message 2184 is issued along with this alert.

For modify transactions, when the client is active in another county, alert message 2078 will be issued instead of alert 2005.

The COUNTY-ID is a unique identifying number which may not be reused for another person. It is the Secondary Identifier in MEDS/CDB and is used by that system to help in locating the correct record.

Refer to MEDS Researching and Resolving File Clearance Alerts. Determine which scenario(s) best describes the circumstances for this alert. Follow the steps outlined in that document for the selected scenario.

Sample Alert

Click herehere to view the sample alert.

Possible Screens To Resolve This Alert

MEDS County ID Cross-Reference InquiryCross-Reference Inquiry on the transaction MEDS ID.
The County ID Cross Reference Report displaysdisplays all county IDs known to MEDS for the displayed MEDS ID; this screen does not indicate which county ID is the latest known to MEDS. The county ID with the 85 Aid Code is associated with MFBU of A. The county ID with the 84 Aid Code is associated with the MFBU of Z.
A Client Inquiry Request on the county IDcounty ID with the MFBU of A (the transaction county ID).
The Client Inquiry Summary INQS screen resultsresults.
This screen displaysdisplays the latest county ID, which is the county ID with the 84 Aid Code and the MFBU of Z.

Example: The worker sends an eligibility update transaction (EW30) to MEDS. It is rejected due to a County ID conflict and an alert 2005 is issued but the problem is not fixed. If another eligibility update to MEDS is sent with the same County ID, MEDS will also reject this transaction. In this case, resolve the problem stemming from the first alert and then, if necessary, submit a MEDS online transaction to report the information that was rejected in the previous updates.

Example: The worker sends a termination transaction (EW40) on a client whose program eligibility has changed (e.g., from CalWORKS to Foster Care). The transaction is rejected because the new program has already sent a transaction to update eligibility on MEDS before the transaction to discontinue eligibility is processed. In this case, no further update to MEDS is necessary.

Example: The worker requests an online transaction to MEDS with an erroneous County ID and an alert is issued. Re-enter the MEDS online transaction with the appropriate County ID.

Example: The worker enters an inappropriate CalSAWS update for an individual who is no longer a member of a case. In this situation, do not send an update to MEDS. Instead, after going through the proper channels, a GadWIN ticket must be generated for each record with the relevant MEDS and CalSAWS screen shots attached so that inappropriate updates and corresponding alerts can be researched and eliminated.

Action Required

Compare the 14-digit County-ID between MEDS and CalSAWS and determine why the County ID on the transaction does not match the County ID on MEDS. If matched, no action is required. If not matched, check the MEDS record, the prior MEDS worker alerts (INWA and/or CalSAWS), the county record. Correct the source problem and resubmit the information on the original transaction update(s) to MEDS.

Obtain a [County-ID Cross Reference Report] screen (INXC) to determine what is the correct 14-digit County-ID. Pulling up a [Whole Case Report] screen (INQW) is useful.

2005 - Transaction County-ID Does Not Match MEDS - Critical

Sample Alert

Possible Screens To Resolve This Alert

Action Required

Related Topics