CMvX Record 198 Reset Cache

“Account not in vExchange” Error

You will receive an error message if you attempt to upload a 200 series record without a corresponding 500 series record in vExchange.

• • What happened? The CMvX 200 series record updates existing claims. If you did not correctly onboard a claim with a 500 series record that matched your Forwarder, then vExchange will have no existing claim for you to update.

• • What’s the result? vExchange will create a CMvX Record 198 and a rejection so that you can fix the problem. This enforcement is in place for all Forwarders.

• • What’s the fix? Import and process CMvX Record 198 by following the instructions below.

Step 1: Find the Rejected Record

• • Folder: On the FTP server, go to the folder “CMvX\FromVertican\Rejections”.
  • File: The rejection file is a report of records that were rejected. The format looks something like this:
    • YGCID_YGCID20220812.txt_2022081275.UPD_BDR_2022081207051.
  • Record: Each record in the file will have a rejection message after the ##. In this case, the message is “Account not in vExchange”.
    • , | 201| : Account not in vExchange

Step 2: Find & Import the Record 198 Reset Cache File

• • Folder: On the FTP server, go to the folder called CMvX\FromVertican\
  • File: The ResetCache file is for you to import in CMvX. The format looks something like this:
    • R_198_[AGENT_ID]_[YEAR][MONTH][DAY]_Reset_Cache.txt
  • Import: In CMvX, process the R_198_[AGENT_ID]_[YEAR][MONTH][DAY]_Reset_Cache.txt file. The CMvX Record 198 Import will reset the cache to create 500 series records to onboard the claims that are missing from vExchange.
  • Note: Record 198 will attempt to onboard a claim that was missing from vExchange. However, if the keys don’t match your Forwarder, the onboarding will be rejected.

Closed Claims

• • If the claim is closed, you will receive a separate Rejection Report. Closed claims (history) can be updated/reset manually or re-opened and updated accordingly.

CMvX Record 198 Fields