5Tips for Updating Your Configuration

• Baseline Configuration is uploaded to your environment during the provisioning process.
• At a minimum, you must update the following .csv files for your school:
• SCHOOL.csv
  • Federal School Code
  • OPEIDs
  • COD Routing ID
• COA.csv: COA Breakdown
• The Configuration Administration page only accepts compressed files with a ".zip" file extension.
• You must strictly adhere to the .csv naming standard in the Configuration File workbook for the application to recognize and accept the request to load the Configuration. You can add data where the percent (%) symbol exists.
• All dependent .csv files and Groovy directories must be included in the compressed file being uploaded.
• Don't compress a parent folder. Select only the .csv files and Groovy directories you want to upload, and only compress those files. Compressing a parent folder will break the path to the Groovy script that is documented in the .csv file.
• Don't remove Groovy scripts from their directory, change the directory name, or directory structure. This breaks the path to the Groovy script that is documented in the .csv file.
• You can't upload just a .csv file that references Groovy files. You must also provide all the relevant Groovy directories with the .csv file in the compressed folder.
• You can't upload just an updated Groovy file. The compressed file must contain the associated .csv file that references the Groovy script in the full Groovy directory.
• When you open a .csv file, some columns are automatically reformatted by Microsoft Excel. The format must be updated before you attempt to upload the Configuration or an error will be returned, and the upload will fail. Known data impacted by auto formatting:
  • Number values with leading zeros (for example, C-Codes, Reject Codes, OPEIDs)
  • Dates
• All Date columns in the .csv files must be converted to YYYY-MM-DD. Example .csv files:
  • FAS_FUND_CONFIG
  • FUND_PRIORITY
  • NFR_ATTRIB
• The CODE_NUMBER in these .csv files must be converted to 3 digits in length, or the application returns an "Invalid code length for entry" error:
  • ISIR_C_CODES
  • ISIR_C_CODES_TO_FIELDS
  • ISIR_REJECT_TO_C_CODES
• These .csv files contain a CODE_NUMBER, but don't update the format to a 3-digit value:
  • ISIR_REJECT_CODES
  • ISIR_VERIFICATION_CODES
  • ISIR_REJECT_CODES_TO_FIELDS
• If you copy or type any data onto a new blank line in the .csv file and then clear the field/row contents, you must delete the entire row. Even if the .csv shows a blank record, Microsoft Excel stores hidden data within that row, which can result in an error.
• If you want the latest Baseline Configuration, download it from the latest Product Release Notes > Latest Release > Baseline Configuration Release Extract. See Document ID 2613016.1 on My Oracle Support.
• Don't upload the Baseline Configuration you download from the release notes in a Production environment, as it will overwrite important institutional data contained in your SCHOOL.csv. Extract the data or script from the baseline .csv or Groovy you want to implement and update your local Configuration files downloaded from the Configuration Administration screen.
• In SCHOOL.csv, provide your school's OPEID. If your school has multiple OPEIDs, it is important that your main OPEID is listed first as it sets the SCHOOL_CONFIGURATION.
  • In the csv provide all OPEIDs in the following format: opeid main~opeid2~opeid3 and so on.
  • Make sure the main OPEID is first and then enter all other OPEIDs; understanding that the first one on the list has additional significance, and the SCHOOL_CONFIGURATION.