ACES2 SQL Setup

LSAC Report/Conditions

Contact your LSAC representative to create a report with the following fields on your ACES2 database. Below are the required ACES2 fields for your ACES2 report and where the fields map to in CAMS Enterprise.

ACES2 Value Mapping

The ACES2ValueMapping SQL table allows you to map incoming ACES2 fields to the corresponding fields in CAMS. In most fields, if the incoming data text exactly matches what is set in the corresponding CAMS Glossary category or Reference table, it will not need to be mapped in the ACES2ValueMapping table. If your data text in CAMS does not match the incoming text, any value for each field can be mapped. This allows you to use any desired text in CAMS fields by simply mapping the incoming data to the CAMS data. Value mapping is done in this SQL table only and beyond the initial setup will rarely need to be changed.

There are occasions where multiple rows for the same value would need to be mapped. For example, multiple incoming values for the same ACES2FieldName such as ethnicities may require multiple entries of the same ACES2FieldName with differing entries in the CAMSMappedValue field. Or there may be situations where multiple values for an ACES2FieldName would need to be mapped to the same CAMS value in the CAMSMappedValue field. For example, it may be desirable to have multiple ACES2 values for Decisions_Status_Short map to the same Applicant Status in CAMS.

Columns in this table are:

Below is a list of all incoming ACES2 fields and the requirements for the ACES2ValueMapping SQL table. The fields are listed alphabetically. Note that some fields do not require any action in the ACES2ValueMapping table.

CAMS Fields Exported to ACES2

Two CAMS fields are exported to ACES2 after successfully importing ACES2 records into Student Admissions Information.

ACES2 Custom Defaults

Any time CAMS saves to a table in the ACES2 import, CAMS can override a field in that table with a value you define in the ACES2CustomDefaults SQL table. You can define when these defaults will be used, either on an insert or update. Defaults override any import values brought in from the ACES2 import. Populating this table is optional and should only be used to override data imported from ACES2. Custom Defaults, if populated, will override imported data for all records imported.

You may add custom defaults for any of the following tables:

Any method used by the institution to insert the data into this table must ensure that fields are mapped correctly and use the correct layout.

Below are the ACES2CustomDefaults fields and their descriptions.

ACES2 Default Student Activities

Each time a new student record is inserted into CAMS Enterprise via the ACES2 process, CAMS will check the ACES2DefaultStudentActivities table and attempt to create new Student Activities from the entries in this table. If there are no entries in this table or if the ActivityTypeID's do not exist, no Student Activities will be created.

ACES2DefaultStdentActivitiesID - This column is populated automatically by SQL and cannot be modified.

ActivityID - The ActivityID from the ActivityLookup table. This table is what populates the Activity drop-down in CAMS.

ActivityTypeID - The activity type you wish to use.

Notes - The text you would like placed in the Notes section of the activity. This text will be placed in all student records where this activity is created.

DocumentUID - Only applicable if the Activity Type is Export. This is the DocumentUID from the DocumentRef table. A DocumentUID of 0 (zero) must be entered for the activity if it is NOT an Export activity.

EmailRefID - Only applicable if the Activity Type is Email. This is the EmailRefID from the EmailRef table. This value must be NULL if the activity is NOT an Email activity.