Return to Navigation

Understanding EDI TS130 Transcript Transactions

Recruiting and Admissions enables you to load external academic transcripts through EDI (Electronic Data Interchange).

To perform EDI TS130 transcript transactions:

  1. Process the inbound EC agent.

    Specify the location of the file that you want to load into the suspense file on the Schedule Inbound EC Agent page.

  2. Load the EDI data for transcript transactions.

    Run the TS130 Load process to load the data into staging files.

  3. Review and edit the data that you loaded in suspense pages.

    Correct all load errors before moving on to the next step. In the search dialog page of the suspense component, enter Error in the Edit Processing Option field and click the Search button. Access each suspense record and correct the errors until every suspense record has a value of Complete (rather than Error) in the Edit field of the Process Options page.

  4. After you have corrected all of the load errors in the suspense files, run the organization search process.

    This process looks for a match of the organization based on the ATP, ACT, FICE, or IPEDS code loaded against the same codes stored on the Organization Table, School Data page. The system compares the EDI School Subject and EDI Course Number on the EDI TS130 Courses page with the school subject and school course number on the School Course Classification page.

  5. Resolve and edit any course errors resulting from the organization search process.

    In the search dialog page of the suspense component, enter Error in the Edit Processing Option field and click the Search button. Access each suspense record and correct the course or organization errors until every suspense record has a value of Complete (rather than Error) in the Edit field of the Process Options page. If more than one match is found for an organization, the EDI Org Process Options Search field will be set to Error and the Search/Match results will show the number of schools that matched on the code used as shown. You will need to resolve that error and run the Organization Search process again for the courses to be populated.

    This process looks for data in your database (based on search parameters that you define on the Search/match Parameters page, to include, for example, name, social security number, and birth date) that matches the data that you are posting. For a set of parameters that suggest only a possible match (such as name and gender, for example), the process does not post the record until you can manually determine which records are actually duplicates.

  6. After you have corrected all of the organization and course errors in the suspense files, run the search/match/post process.

    This process looks for data in your database (based on search parameters that you defined on the Search/match Parameters page, to include, for example, name, social security number, and birth date) that matches the data that you are posting. For a set of parameters that suggest only a possible match (such as name and gender, for example), the process does not post the record until you can manually determine which records are actually duplicates.

  7. Check each suspense record that did not get posted to see if it is actually a duplicate.

    In the search dialog page of the TS130 Staging component, enter Complete in the Edit Process Option field and Perform in the Search/Match Process Option field, and then click the Search button. The search process finds only those suspense records that went through the search/match/post process but were not posted. The reason the search/match/post process did not post the records is because it found a possible duplicate record in the database. After you access the component, find the parameters for which the process identified a match, and then use search/match to look up the bio/demo information that matches the suspense record and decide whether a person who matches the incoming data already exists in the system. Then, specify whether you want the search/match/post process to add the bio/demo and test record to your database, update an existing record, or ignore the suspense record.

  8. Run the search/match/post process again.

    The process posts the suspense records that you manually tagged to post. By this time, all of your suspense records should be posted to your database. When a record posts to your database, the search/match/post process assigns an ID to the person. To view a bio/demo record that the search/match/post process created, select Develop Enrollment, Process External Data, Use, Bio/Demo Data. To view a test score record that the search/match/post process created or updated, select select Develop Enrollment, then select Process External Data, then select Use, then select Test Scores.

    Purge TS130 staging table records on the TS130 Purge Parameters page. You can also purge messages in this process. If you want to perform an analysis on your TS130 processing, perhaps at the end of a year, do not purge your messages with this process. Instead, purge them at a later date when you know you no longer need to view them.