The attached stored procedure(s) are examples to help your school get up and running. Again, please remember the attached stored procedure will likely need to be modified and customized to fit your school's needs. 
You will need both scripts below and the table create script for this integration to function. 


If you are using this stored procedure without making any modifications, you will need to setup CL Connect with the following parameters:


Package Name = BANINST1.z_campuslogic.p_su_transaction (this comes straight from the Stored Procedure template attached to this article. This needs to match whatever that's updated to, if it's updated at all.)


Below are the parameters in the example Stored Procedure along with the Event Property name CL Connect will need. The lengths under the "Data Type" column are suggestions - they should match the actual data that's coming over. This might vary from value to value depending on the data you're feeding into the ScholarshipUniverse application. 


Stored Procedure Value SQL Table Data TypeCL Connect Event PropertyCL Connect Data Type/Field Size
p_eventStudentId
VARCHAR2 (Your Student ID length)EventStudentIdString (Student ID length)
p_eventId
VARCHAR2 (100)EventIdString (100)
p_eventNotificationId
IntegerEventNotificationIdString (3)
p_eventNotificationName
VARCHAR2 (100)EventNotificationName
String (100)
p_eventDateTime
VARCHAR2 (50)EventDateTimeUtcStandard
String (50)
p_suAwardYearName
VARCHAR2 (100)
SuAwardYearName
String (100)
p_suTermId
VARCHAR2 (6)
SuClientTermId
String (6)
p_suTermName
VARCHAR2 (50)
SuTermName
String (50)
p_suScholarshipAwardId
VARCHAR2 (30)
SuScholarshipAwardId
String (30)
p_suScholarshipName
VARCHAR2 (100)
SuScholarshipName
String (100)
p_suScholarshipCode
VARCHAR2 (100)
SuScholarshipCode
String (100)
p_suAmount
NUMERIC (11,2)SuAmountString (14)
p_suPostBatchUser
VARCHAR2 (100)
SuPostBatchUser
String (100)
p_suPostType
VARCHAR2 (30)
SuPostType
String (30)
p_suTermComments
VARCHAR2 (4000)SuTermCommentsString (4000)