CLS Data Import to Banner

Automated daily import of MIIS Custom Language Services (CLS) applicant data in Salesforce to Banner. 

  • Jennifer Peck in CLS will manually check the "Ready for Export" check box on a CLS application record in Salesforce after verifying the data in that record and the associated contact record.  It's important to make sure phone numbers and addresses are entered correctly in Salesforce to avoid errors when creating records in Banner.
  • A scheduled Informatica task flow will run at 2:45pm ET on weekdays to select CLS application and contact records in Salesforce and insert them into a table in the Banner database.  These records will be selected based on this criteria:
    • Ready for Export check box on CLS application record checked.
    • No value in the MovedToBannerDate field on the CLS application record.
  • A scheduled Banner database process will run on weekdays at 3pm ET to read the exported Salesforce data, call Common Matching procedures, and insert/update records in Banner.
  • A scheduled Informatica task will run at 3:30pm on weekdays and copy Banner IDs for people in Banner to Salesforce.  The records selected will have an SFRC record on the Alternate Identification tab in SPAIDEN.  The associated Banner ID will be inserted into the Banner ID field on the Salesforce contact record for that SFRC ID value.

Prepare Record in Salesforce for Export

Verify that the Desired start and end dates on the CLS application record have values.  Verify that the address and phone numbers on the associated contact record contain valid data.  Enter data into or correct data in these fields if necessary.  Check the Ready for Export check box.  The MovedToBannerDate field must be blank in order for the record to be exported from Salesforce.

After the data is exported, an Informatica task will update the MovedToBannerDate field on each exported CLS application record.  This prevents it from being selected in the future.

Common Matching

An automated process will run and execute the common matching procedures.  The MIIS_CLS common matching rule is used to check if the data coming into Banner is new, a match, or will be suspended. 

New Records

All records created in Banner will be seen in the Banner SPAIDEN form in Banner Admin.  

Salesforce Field Banner Field Tab in SPAIDEN Notes
First Name First Name Current Identification  

Middle Name

Middle Name

Current Identification

 

Last Name Last Name Current Identification  

Mailing Street

Street Line 1

Address

Address Type Code is ‘MA’

Mailing City

City

Address

 

Mailing State/Province

State or Province

Address

 

Mailing Zip/Postal Code

ZIP or Postal Code

Address

 

Mailing Country

Nation

Address

 

Home Phone Area Code & Phone Number Telephone Telephone Type is ‘HOME’, Address Type is 'MA'

International Phone Number

International Access

Telephone

Telephone Type is ‘HOME’, Address Type is 'MA'

Mobile Area Code & Phone Number Telephone Telephone Type is ‘CELL’, Address Type is 'MA'

International Cell Phone Number

International Access

Telephone

Telephone Type is ‘CELL’, Address Type is 'MA'

Gender

Legal Sex

Biographical

 

Birthdate Birth Date Biographical  

Email

E-mail Address

E-mail

Email Type is ‘REC1’

Language of Study Additional Identification Additional Identification Used for creating 8MFB record.  

If the application name is 'CLS Application - Intensive Language Training', the additional identification value will be the language of study value followed by the desired start and end dates.

If the application name is 'CLS Application - English for Diplomats', the additional identification value will be 'English for Diplomats ' followed by the desired start and end dates.

Desired Start Date

Additional Identification

Additional Identification

Used for creating 8MFB record.

Desired End Date

Additional Identification

Additional Identification

Used for creating 8MFB record.

AutoId

ID

Alternate Identification

Name Type is 'SFRC'.  Informatica task runs daily to select SFRC records in Banner and populate the Banner ID associated with each on the Salesforce contact record.

Matching Records

If a match is found, the process will determine if records need to be created for the following:

  • Phone numbers
  • Email Address
  • SFRC Alternative Identification record
  • 8MFB Additional Identification record

Suspended Records 

At least one record was found where some of the fields identified in the rule match the record being entered, but not all.  Nothing is created automatically in Banner when this happens.  An email will be sent to Jennifer Peck and Marci Fitzurka listing suspended records and potential matches.  They will need to look up the data in Banner and determine if the person in question already exists.  If the person exists, the Banner ID should be manually entered on the person's contact record in Salesforce.  If none of the potential matches are the person in Salesforce, the records must be manually created in the Banner SPAIDEN form.

Note: You can use the GOAMTCH form in Banner to determine why a record suspends.  Select Generated for ID, and MIIS_CLS for the matching rule. You may want to familiarize yourself with the rule first in the GORCMRL form and also name aliases in the GORNAME form.

Enter the person's name, address, and birth date.  Click the Duplicate Check button.  That will either display a message at the top stating there isn't a match and you can create the person as New or it will list the potential duplicates below.  The duplicates will list the elements of the matching rule criteria.  For example, the screen shot below has Jim Morrison entered in the top portion.  His City and Zip don't match a Jim Morrison record already in Banner (PPRD):

The 2 priorities of the rule display the criteria in the Matching Rule Sets drop down.  The Address has "No Match" after it and is the reason why the record entered suspended.

Details

Article ID: 356
Created
Tue 9/20/22 8:56 AM
Modified
Tue 9/26/23 10:39 AM

Related Services / Offerings (1)

Get help with automated systems integrations, data integrations, 3rd party connectors.