Data Import Transactions

The Data Import Transactions portlet displays the sequences of data movement from an ERP database to the JICS database.  The portlet shows the data file and log information for recent import transactions.  

Administrators can place the Data Import Transactions portlet on any page for easiest access.  For example, it can be configured on an Admin Tab:

Click on Data Import Transactions portlet title to expand the portlet to fill the screen with the 5 most recent transactions:

Click on the Go to Main Screen hyperlink to display the 30 most recent transactions, including the transaction data and transaction log file:

The Data Import Transactions portlet displays the current file being processed and the recent import transactions that took place between your ERP system and the JICS system.  

For each recent import transaction, the portlet displays:

• Sequence Number

  The order in which this transaction was processed.  Transaction records must be processed in sequence in order for data imports to succeed.

• End Time

  The date and time that the transaction occurred.

• Total Records

  The number of records imported in this transaction.

• Errors

  The total number of errors that occurred during this transaction.

• Status

  The status of the transaction at the time of completion:  Success or Failed.

• Data

  Each data file contains the following lines:

  • header

    The file header line contains the following data:

    • college code

    • datetimestamp of data transfer

    • the format name ("JENZA1")

    • mode ("TEST" or "LIVE")

    • sequence: number

  • one or more transactions

    Each transaction line contains comma-separated, URL-encoded data. All transaction lines begin with the following:

    • transaction code

      • TRM - term data

      • DPT - department data

      • PRS - person data

      • CST - college/status data

      • CCD - course code (course catalog) data

      • CRS - course (offering) data

      • SCH - course schedule data

      • CRP - course/person registration data

      • STU - student data

       

    • action

      A - Add a new record to Jenzabar's database

      U - Update an existing record in Jenzabar's database

      D - Delete an existing record in Jenzabar's database

      W - Issue a withdraw command for CRP transactions

    • last update datetimestamp (optional)

    The format of the rest of the transaction line is different for each transaction type:

    • TRM - term data

      This transaction type imports data into Jenzabar's Term table.

      The data format for the TRM transaction:

      • term code

      • description

      • start date

      • end date

    • DPT - department data

      This transaction type imports data into Jenzabar's Department table.

      The data format for the DPT transaction:

      • department code

      • description

    • PRS - person data

      The data format for the PRS transaction:

      • host id

      • host username

      • host password

      • first name

      • middle initial

      • last name

      • suffix

      • email

    • CST - college/status data

      The data format for the CST transaction:

      • host id

      • department code (optional)

      • status code (role)

      • degree type (optional)

      • graduation date (optional)

    • CCD - course code (course catalog) data

      The data format for the CCD transaction:

      • course code

      • title

      • description

      • department code

    • CRS - course (offering) data

      The data format for the CRS transaction:

      • term code

      • course code

      • section (optional)

      • title (optional)

       

    • SCH - course schedule data

      The data format for the SCH transaction:

      • term code

      • course code

      • section (optional)

      • start date (optional)

      • end date (optional)

      • days

      • start time

      • end time

      • location (optional)

    • CRP - course/person registration data

      The data format for the CRP transaction:

      • term code

      • course code

      • section

      • host id

      • status code (role in the course:  1PR or STU)

    • STU - student data

      The data format for the STU transaction:

      • host id

      • leave of absence start (optional)

      • leave of absence end (optional)

      • probation (optional)

      • standing (optional)

      • major (optional)

      • major description (optional)

      • division code (optional)

      • division description (optional)

  • footer

    The file footer line contains the following data:

    • EOF tag ("END")

    • the number of records contained in the data file

   

  

   

   

• Log

  Each data file import is logged in a separate file.  Click the Log hyperlink in the Data Import Transaction portlet to view the contents of the log file:

  

   

  Administrators use log files to review the success rate of data being sent to ICS.

  The log file that is created by the Data Import Service contains the following types of information:

  transaction

  Any or all of the following information is included in each transaction line of the log file, depending on the transaction type:

  • transaction type:  TRM, DPT, PRS, CST, CCD, CRS, SCH, CRP, STU

  • transaction action:  add (A), update (U), or delete (D), withdraw (W)

  • data import status:  success (1) or failure (0)

  • a text error message, if import failed

  • datetimestamp

  • the term code

  • the course code

  • the section code

  • host id

  • start date

  • end date

  • number of days that the class meets

  • start time

  • end time

  • encrypted classroom location

  • encrypted description

  • encrypted username

  • encrypted password

  summary

   

   

   

NOTE:  See the JICS Installation Guide for details about the Data Import Service and the format of transaction data and log records.

Preferences, Settings, and Permissions

Currently when you click on the   wrench icon, no preferences, settings, or permission operations are available for the Data Import Transactions portlet.