Third Party Data Integration IEPPLUS

Size: px

Start display at page:

Download "Third Party Data Integration IEPPLUS"

Norman Stokes
6 years ago
Views:

Third Party Data Integration IEPPLUS 1990-2013 SunGard Public Sector Inc. All rights reserved.

1 Third Party Data Integration IEPPLUS SunGard Public Sector Inc. All rights reserved. No part of this publication may be reproduced without the prior written permission of SunGard Public Sector Inc., with the exception of copies made for your internal use. SunGard, the SunGard logo, PLUS 360, eschoolplus, IEPPLUS, PerformancePLUS, efinanceplus, and BusinessPLUS are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. All other trade names are trademarks or registered trademarks of their respective 2014 SunGard Public Sector Inc. All Rights Reserved Page 1 of 8

OVERVIEW The IEPPLUS application can integrate with any 3 rd party system. A file generated by the 3 rd party system will be automatically imported into an IEPPLUS table (e.g. JeffersonDailyImport).

3 OVERVIEW The IEPPLUS application can integrate with any 3 rd party system. A file generated by the 3 rd party system will be automatically imported into an IEPPLUS table (e.g. JeffersonDailyImport). The name of the IEPPLUS table is prefaced by the name of the school district. Once the data is imported into this single table, another process is run to take the data and add it to the application IEPPLUS tables (e.g. Placement, Identification, StudentStatus). INTEGRATING STUDENTS Typically, the import process is set up as a scheduled task and is automatically run on a set time. However, the student import can also be run manually. From the Data Integration module, select File, Import, Student Data. The system will locate all students in the IEPPLUS XXXXX table and attempt to import the data into the IEPPLUS system. Once the process has completed, a message appears indicating that the process was successful as well as the total number of students that were imported. The data has been processed into the IEPPLUS system. The Import reports can now be run. REPORTS There are two reports to run based on the Import Students process. From the Run A Report menu, search for Import Student Error and Import Student Summary. The Import Student Summary report will display the start / end date, start time and end time in which the import process ran along with student names, ID s, The Start and Completion time information is helpful to determine when the last time the import process ran and if it was successful (completed date/time). The Import Student Error report will display each student and the applicable error. INTEGRATION 2014 SunGard Public Sector Inc. All Rights Reserved Page 3 of 8

4 From the Maintenance menu, select Rule. A listing of each data integration rule will now be displayed. The direction of these rules will be set to Down meaning that the data is imported into the IEPPLUS system. Any custom integration rule will be prefaced by the name of the district. Rules: 1. Third Party Import - Federal Ethnicity: This custom rule will import the 'FEDETHNICITY' field into the IEPPLUS Student.ST_Ethnicity field. 'FEDETHNICITY' should be the description of an alternate code with a type of 'Import Code' linked to an entry in the Federal Ethnicity code table. This rule requires the 'FEDETHNICITY' field. 2. Third Party Import - State Assigned Student ID: This custom rule will import the 'STATE_STUDENTNUMBER' field into the IEPPLUS Identification.ID_Data field. The type of the identification is found from an Identification code table entry with an alternate code of type 'Import Code' and a description of 'SASID'. This rule requires the the 'STATE_STUDENTNUMBER' field. 3. Third Party Import - Home Phone: This custom rule will import the 'STUDENT_HOME_PHONE' field into the IEPPLUS Communication.CM_Data field. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'HP'. This rule requires the the 'STUDENT_HOME_PHONE' field. 4. Third Party Import - Home Address: This custom rule will import the 'STUDENT_STREET', 'STUDENT_CITY', 'STUDENT_STATE' and 'STUDENT_ZIP' fields into the IEPPLUS 'Address' table with 2014 SunGard Public Sector Inc. All Rights Reserved Page 4 of 8

5 home value of 1. This rule requires the 'STUDENT_STREET', 'STUDENT_CITY', 'STUDENT_STATE' and 'STUDENT_ZIP' fields. 5. Third Party Import - Mailing Address: This custom rule will import the 'STUDENT_MAILING_STREET', 'STUDENT_MAILING_CITY', 'STUDENT_MAILING_STATE' and 'STUDENT_MAILING_ZIP' fields into the IEPPLUS 'Address' table with a mail value of 1 if these fields are not the same as the 'STUDENT_STREET', 'STUDENT_CITY', 'STUDENT_STATE' and 'STUDENT_ZIP' fields. This rule requires the 'STUDENT_MAILING_STREET', 'STUDENT_MAILING_CITY', 'STUDENT_MAILING_STATE', 'STUDENT_MAILING_ZIP', 'STUDENT_STREET', 'STUDENT_CITY', 'STUDENT_STATE' and 'STUDENT_ZIP' fields. 6. Third Party Import - Contact #1: This custom rule will import the 'CNT1_FNAME', 'CNT1_LNAME', 'CNT1_REL', and 'CNT1_TYPE' fields into the IEPPLUS 'Contact' table. 'CNT1_REL' should be the description of an alternate code with type = 'Import Code' linked to an entry in the Relationship code table. 'CNT1_TYPE' should be '1', '2', '3', or '9', corresponding with 'Parent/Guardian', 'Emergency Contact', 'Surrogate Parent', 'Other'. If a contact with CN_First = 'CNT1_FNAME' and CN_Last = 'CNT1_LNAME' already exists, that contact is updated. Otherwise, a new contact is created. This rule requires the 'CNT1_FNAME', 'CNT1_LNAME', 'CNT1_REL', and 'CNT1_TYPE' fields. 7. Third Party Import - Contact #1 Home Phone: This custom rule will import the 'CNT1_HPHONE' field into the IEPPLUS 'Communication' table. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'HP'. 8. Third Party Import - Contact #1 Work Phone: This custom rule will import the 'CNT1_WPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT1_FNAME' and CN_Last = 'CNT1_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'WP'. This rule requires the 'CNT1_FNAME', 'CNT1_LNAME', and 'CNT1_WPHONE' fields. 9. Third Party Import - Contact #1 Cell Phone: This custom rule will import the 'CNT1_CPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT1_FNAME' and CN_Last = 'CNT1_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'CP'. This rule requires the 'CNT1_FNAME', 'CNT1_LNAME', and 'CNT1_CPHONE' fields. 10. Third Party Import - Contact #1 This custom rule will import the 'CNT1_ ' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT1_FNAME' and CN_Last = 'CNT1_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'EM'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', and 'CNT2_ ' fields. 11. Third Party Import - Contact #1 Address: This custom rule will import the 'CNT1_STREET', 'CNT1_CITY', 'CNT1_STATE', 'CNT1_ZIP', and 'CNT1_RECVMAIL' fields into the IEPPLUS 'Address' table linked to the contact with CN_First = 'CNT1_FNAME' and CN_Last = 'CNT1_LNAME'. 'CNT1_RECVMAIL' should have a value of '1' if this contact should receive mail or NULL if this contact should not receive mail'. This rule requires the 'CNT1_FNAME', 'CNT1_LNAME', 'CNT1_STREET', 'CNT1_CITY', 'CNT1_STATE', 'CNT1_ZIP', and 'CNT1_RECVMAIL' 2014 SunGard Public Sector Inc. All Rights Reserved Page 5 of 8

6 12. Third Party Import - Contact #2: This custom rule will import the 'CNT2_FNAME', 'CNT2_LNAME', 'CNT2_REL', and 'CNT2_TYPE' fields into the IEPPLUS 'Contact' table. 'CNT2_REL' should be the description of an alternate code with type = 'Import Code' linked to an entry in the Relationship code table. 'CNT2_TYPE' should be '1', '2', '3', or '9'; corresponding with 'Parent/Guardian', 'Emergency Contact', 'Surrogate Parent', 'Other'. If a contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME' already exists, that contact is updated. Otherwise, a new contact is created. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', 'CNT2_REL', and 'CNT2_TYPE' fields. 13. Third Party Import - Contact #2 Home Phone: This custom rule will import the 'CNT2_HPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'HP'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', and 'CNT2_HPHONE' fields. 14. Third Party Import - Contact #2 Work Phone: This custom rule will import the 'CNT2_WPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'WP'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', and 'CNT2_WPHONE' fields. 15. Third Party Import - Contact #2 Cell Phone: This custom rule will import the 'CNT2_CPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'CP'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', and 'CNT2_CPHONE' fields. 16. Third Party Import - Contact #2 This custom rule will import the 'CNT2_ ' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'EM'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', and 'CNT2_ ' fields. 17. Third Party Import - Contact #2 Address: This custom rule will import the 'CNT2_STREET', 'CNT2_CITY', 'CNT2_STATE', 'CNT2_ZIP', and 'CNT2_RECVMAIL' fields into the IEPPLUS 'Address' table linked to the contact with CN_First = 'CNT2_FNAME' and CN_Last = 'CNT2_LNAME'. 'CNT2_RECVMAIL' should have a value of '1' if this contact should receive mail or NULL if this contact should not receive mail'. This rule requires the 'CNT2_FNAME', 'CNT2_LNAME', 'CNT2_STREET', 'CNT2_CITY', 'CNT2_STATE', 'CNT2_ZIP', and 'CNT2_RECVMAIL' fields. 18. Third Party Import - Contact #3: This custom rule will import the 'CNT3_FNAME', 'CNT3_LNAME', 'CNT3_REL', and 'CNT3_TYPE' fields into the IEPPLUS 'Contact' table. 'CNT3_REL' should be the description of an alternate code with type = 'Import Code' linked to an entry in the Relationship code table. 'CNT3_TYPE' should be '1', '2', '3', or '9'; corresponding with 'Parent/Guardian', 'Emergency Contact', 'Surrogate Parent', 'Other'. If a contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME' already exists, that contact is updated. Otherwise, a new contact is created. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', 'CNT3_REL', and 'CNT3_TYPE' 2014 SunGard Public Sector Inc. All Rights Reserved Page 6 of 8

7 19. Third Party Import - Contact #3 Home Phone: This custom rule will import the 'CNT3_HPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'HP'. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', and 'CNT3_HPHONE' fields. 20. Third Party Import - Contact #3 Work Phone: This custom rule will import the 'CNT3_WPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'WP'. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', and 'CNT3_WPHONE' fields. 21. Third Party Import - Contact #3 Cell Phone: This custom rule will import the 'CNT3_CPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'CP'. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', and 'CNT3_CPHONE' fields. 22. Third Party Import - Contact #3 This custom rule will import the 'CNT3_CPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'CP'. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', and 'CNT3_CPHONE' fields. 23. Third Party Import - Contact #3 Address: This custom rule will import the 'CNT3_STREET', 'CNT3_CITY', 'CNT3_STATE', 'CNT3_ZIP', and 'CNT3_RECVMAIL' fields into the IEPPLUS 'Address' table linked to the contact with CN_First = 'CNT3_FNAME' and CN_Last = 'CNT3_LNAME'. 'CNT3_RECVMAIL' should have a value of '1' if this contact should receive mail or NULL if this contact should not receive mail'. This rule requires the 'CNT3_FNAME', 'CNT3_LNAME', 'CNT3_STREET', 'CNT3_CITY', 'CNT3_STATE', 'CNT3_ZIP', and 'CNT3_RECVMAIL' fields. 24. Third Party Import - Contact #4: This custom rule will import the 'CNT4_FNAME', 'CNT4_LNAME', 'CNT4_REL', and 'CNT4_TYPE' fields into the IEPPLUS 'Contact' table. 'CNT4_REL' should be the description of an alternate code with type = 'Import Code' linked to an entry in the Relationship code table. 'CNT4_TYPE' should be '1', '2', '3', or '9'; corresponding with 'Parent/Guardian', 'Emergency Contact', 'Surrogate Parent', 'Other'. If a contact with CN_First = 'CNT4_FNAME' and CN_Last = 'CNT4_LNAME' already exists, that contact is updated. Otherwise, a new contact is created. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', 'CNT4_REL', and 'CNT4_TYPE' fields. 25. Third Party Import - Contact #4 Home Phone: This custom rule will import the 'CNT4_HPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT4_FNAME' and CN_Last = 'CNT4_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'HP'. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', and 'CNT4_HPHONE' fields. 26. Third Party Import - Contact #4 Work Phone: This custom rule will import the 'CNT4_WPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT4_FNAME' and CN_Last 2014 SunGard Public Sector Inc. All Rights Reserved Page 7 of 8

8 'CNT4_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'WP'. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', and 'CNT4_WPHONE' fields. 27. Third Party Import - Contact #4 Cell Phone: This custom rule will import the 'CNT4_CPHONE' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT4_FNAME' and CN_Last = 'CNT4_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'CP'. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', and 'CNT4_CPHONE' fields. 28. Third Party Import - Contact #4 This custom rule will import the 'CNT4_ ' field into the IEPPLUS 'Communication' table linked to the contact with CN_First = 'CNT4_FNAME' and CN_Last = 'CNT4_LNAME'. The type of the communication is found from a Communication code table entry with an alternate code of type 'Import Code' and a description of 'EM'. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', and 'CNT4_ ' fields. 29. Third Party Import - Contact #4 Address: This custom rule will import the 'CNT4_STREET', 'CNT4_CITY', 'CNT4_STATE', 'CNT4_ZIP', and 'CNT4_RECVMAIL' fields into the IEPPLUS 'Address' table linked to the contact with CN_First = 'CNT4_FNAME' and CN_Last = 'CNT4_LNAME'. 'CNT4_RECVMAIL' should have a value of '1' if this contact should receive mail or NULL if this contact should not receive mail'. This rule requires the 'CNT4_FNAME', 'CNT4_LNAME', 'CNT4_STREET', 'CNT4_CITY', 'CNT4_STATE', 'CNT4_ZIP', and 'CNT4_RECVMAIL' fields. 30. Third Party Import - Placement (TBD): This custom rule will create a new IEPPLUS 'To Be Determined' Placement record if the student currently has no placement records. This rule does not require any fields. Third Party Import - Placement Grade: This custom rule will import the 'GRADE_LEVEL' field into the IEPPLUS Placement.PL_Grade field. 'GRADE_LEVEL' should be the description of an alternate code with a type of 'Import Code' linked to an entry in the Grade code table. This rule requires the 'GRADE_LEVEL' field. REVISION HISTORY 2/24/14 Created 2014 SunGard Public Sector Inc. All Rights Reserved Page 8 of 8

PLUS 360 Advanced Data Integration With eschoolplus 3.1

PLUS 360 Advanced Data Integration With eschoolplus 3.1 1990-2014 SunGard Public Sector Inc. All rights reserved. No part of this publication may be reproduced without the prior written permission of SunGard