How do I create and upload my SBA data exports to EDMIS?EDMIS is the Entrepreneurial Development Management Information System, which is administered by SBA. EDMIS came online in October 2005 and it is based exclusively upon fiscal years. Thus, a reporting period for EDMIS is October 1 through September 30, regardless of whether your SBDC or WBC has a contract with SBA on a calendar year basis. Quarterly, SBA-funded centers are required to export data to the EDMIS system for reporting purposes. At the end of each quarter, you have 30 calendar days, plus five business days, to successfully submit your data. Your quarterly EDMIS exports are always comprised of two XML files. One file contains client data with counseling session and/or investment data attached and one file contains training data. WebCATS exports only the data that EDMIS identifies as mandatory. Although WebCATS stores significantly more data than just what is exported (such as client name, phone number, email address, etc), this optional data is omitted from the export in order to keep your EDMIS export operations as simple (and private) as possible. Furthermore, in order for a session to be exported it must be marked as “reportable” in the session. Non-reportable sessions are never exported. This FAQ is divided into two main topics:
Note: This FAQ is written for system administrators because they are the only type of WebCATS users that are allowed to perform EDMIS exports in WinCATS. EDMIS ConfigurationsEDMIS ValidationsWebCATS has several built-in validations in place for SBA-funded counseling sessions and conferences. These validations help ensure that the data in your database meets all the requirements set forth by SBA and the EDMIS system. By default, these validations are in place for SBA-funded counseling sessions and conferences only, but you can apply these same validation checks to counseling sessions and conferences under all funding sources by enabling the “Apply EDMIS validation checks to all funding sources?” option located on the General tab of WinCATS' global configurations, as shown next.
Locking DataOn this same configurations tab, you also have the ability to lock data in the WebCATS database that is older than a designated date. Why is this important? This is important because, although SBA allows edits to records previously submitted within the current fiscal year, once the fiscal year has closed, no records from the prior year may be edited. To ensure that your WebCATS database is fully synchronized with the EDMIS database, OutreachSystems strongly recommends that you lock data each year right before uploading your fourth-quarter export files to EDMIS. This prevents users from adding or editing records that you are in the process of exporting. System administrators can override this lock so if you require the ability to change records based on WebCATS or EDMIS error log data, you'll still be able to do so. To lock the WebCATS database after every fiscal year, set the date prior to which users should not be able to edit records, as shown next.
PIMS CodeEvery center in your database that contributes records to the EDMIS export must have a PIMS code present in its center record. EDMIS will reject any exported records that reference a center whose center record does not contain a PIMS code. To obtain a PIMS code, please contact SBA directly for this information. OutreachSystems does not have access to the PIMS codes. Creating the EDMIS Export FilesThe process of creating files for export to EDMIS is a long one. For this reason, we have divided this section into several broad steps, with each broad step containing its own set of steps:
Step 1: Performing Duplicate Client Analysis on the WebCATS DatabaseDuplicate client records negatively affect the integrity of your database. For SBA-funded centers reporting to EDMIS, duplicate client records are particularly troublesome because not only will you be overstating your client count and understating your extended engagement client count, but remedying duplicates is extremely complicated once session activity has been submitted to EDMIS for a duplicate client record. For these reasons, the first step of the EDMIS export process is to run WebCATS' built-in duplicate analysis reports on the WebCATS database. If any duplicates are identified, they must be cleaned up before proceeding with step 2 and it's extremely important that you carefully follow the clean-up procedure documented in the FAQ titled How can I find and clean up duplicate client records in my WebCATS database, and prevent future occurrences? as there are many considerations to take into account when attempting to consolidate duplicate client records. Step 2: Creating the First Set of Export Files & Error Logs
If you intend to export records from multiple funding sources, it's important to note that EDMIS will reject multiple initial counseling sessions or out-of-sequence initial/follow-up counseling sessions for a single client. Therefore, be prepared to encounter problems if you export records from multiple funding sources and you have multiple initial counseling sessions for a single client under different funding sources. For example, a dual-funded center that has one DLA-funded and one SBA-funded initial counseling session for a single client will encounter EDMIS rejections if the center selects both "SBA" and "DLA" for the export's funding source. Keep in mind that you can only export records for the current fiscal year. You should not export records belonging to prior fiscal years. If you do broaden your export date range, don't be tempted to break the export into multiple batches. Because initial counseling sessions must precede follow-up sessions into the EDMIS system, it's simplest to submit data from the entire date range at once to avoid any rejections due to sequencing. Depending on the size of your database, the export file types selected, and the quality of your Internet connection, the create export process can take up to 90 minutes, so please be patient. Step 3: Reviewing & Remedying the Errors that WinCATS IdentifiesIf the EDMIS Export Log identifies errors in your export files, you'll want to delete the upload files you just created and, instead, focus on remedying the errors. There's no point in uploading records to EDMIS that will be rejected. It's better to remedy the errors in WebCATS and then recreate the export files. If no errors are identified by the EDMIS Export Log the first time you sit down to generate a quarterly export, give yourself a hearty congratulations on a job well done and skip to the Step 4 section. You may be wondering how errors are possible when WebCATS automatically validates every new record added to the database to make sure it meets the latest EDMIS requirements. Unfortunately, as vigilant as WebCATS is, errors can still sneak in. For example, as per the latest EDMIS definitions, you cannot create a prep-only counseling session for a client if there are no prior sessions in the database for that client that includes contact time. WebCATS respects this, but what if the session with the contact time is deleted from the system after the prep-only session is created? WebCATS cannot validate this action and an EDMIS error is silently introduced. How you decide to fix the identified errors may depend upon the number of errors and the procedures in place for your program. If there are only a couple, it may be easier for the lead center to go into the database and correct the errors. But if there are a significant number of errors of if your program expects individual centers to be responsible for their own errors, you can direct WebCATS users to the EDMISrx menu option in WebCATS and request that they identify and correct the errors displayed there for their center. Below, the steps for identifying and correcting errors in WebCATS using EDMISrx are outlined:
Step 4: Creating & Uploading an Error-Free Set of Export Files to EDMISOnce all the errors identified by WebCATS have been corrected, you should create brand new export files, following the same steps you did when you created the first set of files (as outlined in the Step 2 section). Hopefully, all issues will have been resolved and the EDMIS Export Log provided by WinCATS will show no errors, but, if errors are still present the second time around, no problem. Simply notify your centers again to correct the remaining errors (or correct them yourself) and perform the export process again—or as many more times as necessary. At last you will have error-free export files! These are the ones you should upload to EDMIS. Up to this point, EDMIS has no knowledge of anything you've done in WinCATS. You must upload your export files to EDMIS to bring the EDMIS system into the loop. To upload your XML or Zip file to EDMIS, perform the following steps:
After uploading your export files, it's a good idea to delete the prior EDMIS export records, EDMIS export files, and EDMIS Export Logs that were created during the troubleshooting process, if you haven't already. Since none of the files resulting from these prior exports will be uploaded to EDMIS, there's no reason to keep them around and it will be best to delete them to avoid confusion in the future. In fact, it's not until you upload data to EDMIS and begin updating your EDMIS export records with the acceptance or rejection statuses provided by EDMIS, as discussed in the next section, that any EDMIS-related export activity is bonded to the WebCATS database. Step 5: Downloading EDMIS' Error File & Remedying the Errors that EDMIS IdentifiesAfter uploading your export files to EDMIS, you'll need to wait up to one business day for EDMIS to process them. After processing is complete, you should receive an e-mail from EDMIS for each uploaded file that informs you of the status of that file. However, OutreachSystems recommends that you never rely solely on the e-mail responses as they are unreliable. If you do not have a reply e-mail waiting for you within the next day or two, you should go directly to the EDMIS Web site to find out the upload status. If the upload status summary notes any failed records (whether you're viewing it via e-mail or the EDMIS Web site), it's imperative that you download the EDMIS Error Report to WinCATS so that the WebCATS system can track those records that have been accepted and rejected by EDMIS. When WebCATS knows that a record has been accepted by EDMIS, it's able to handle subsequent edits or deletions of that record according to EDMIS' requirements. Another benefit to downloading the EDMIS Error Report into WinCATS is that you'll be able to use the EDMISrx module to correct the errors identified by EDMIS. Since the EDMIS Error Report is not reader-friendly, the ability to read about the errors in plain English is extremely helpful. The process of downloading the EDMIS Error Report into WinCATS is outlined next:
Accepted records are never submitted to EDMIS again, unless they are edited or deleted. Rejected records, of course, must be remedied. These records can be remedied using the EDMISrx module again, as outlined in the Step 3 section. You may be thinking that you already went through a troubleshooting process and how can you still have rejected records? Keep in mind that the only errors you have corrected thus far have been those that WebCATS was able to detect. Unfortunately, WebCATS is not able to detect all errors. For example, WebCATS will warn you if a record doesn't contain a ZIP Code, but it cannot validate the ZIP Codes that are present. EDMIS, however, does validate ZIP Codes and if you upload a record with an invalid ZIP Code, the record will be rejected by EDMIS whereas WebCATS let it slip by. Once you or your users correct the errors identified by the EDMIS system, you should create brand new export files and submit them to EDMIS, following the same steps you did when you created the first set of files. When gathering records for the export, WinCATS will only include those records that were previously rejected. Accepted records from the last go-around will not be re-exported (unless you edited them). Essentially, you'll keep cycling through this process until the EDMIS system indicates that all your records were successfully uploaded. Don’t be discouraged if you need to do a couple of uploads in order to get to the point where all records are accepted by EDMIS. With each upload, you'll be submitting a smaller and smaller set of records. Step 6: Accepting All RecordsOnce the EDMIS system indicates that all your records were successfully uploaded, it's almost time for celebration—but not quite yet. There is still one VERY important step you must take, which is to manually set the status of the last batch of submitted records to "Accepted." Why manually? Because if your final upload status is that all records were successfully uploaded, there's no EDMIS Error Report to import into WinCATS to automatically do it for you. This is probably the easiest step of the entire process, but it is also the most overlooked step, with unpleasant consequences. If records that have been accepted by EDMIS aren't marked as accepted in WinCATS, WinCATS will continue to try and upload these records over and over again. The steps for manually setting the status of the very last batch of uploaded records to accepted are outlined next:
Congratulations! You have completed your EDMIS export process! Note: Did you just complete a fourth-quarter export? If so, don't forget to lock data for the previous fiscal year, as described in Locking Data. Note: Please don't hesitate to call us with any questions regarding the EDMIS export process. Also, we invite you to review the EDMISrx information located on our Web site to learn more about how you can use this module to automate the troubleshooting process on a monthly basis. |
|
Want more? Browse our extensive list of WebCATS FAQs. |