AX1276
Ellucian data reference
This topic is a reference for the data fields available when importing data from Ellucian. The data fields vary depending on the type of source system (Banner or Colleague) and the data type.
Banner data types
The following data types can be imported from Banner systems. Also see Common data types (Banner and Colleague).
Chart of Accounts Components
The list of components used by the chart of accounts.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
ComponentType |
String(20) |
Account, Fund, Organization, Program, Activity, Location, etc. |
Value |
String(40) |
Account code, etc. |
Description |
String(250) |
|
ChartID |
String(50) |
The Ellucian ID of the owning Chart of Accounts |
ParentComponentID |
String(50) |
The Ellucian ID of the parent component, if part of a hierarchy |
Status |
String(20) |
Active or Inactive |
TransactionStatus |
String(20) |
Available or Unavailable |
AccountType |
String(40) |
|
FundType |
String(40) |
|
EffectiveStartDate |
DateTime |
|
EffectiveEndDate |
DateTime |
|
General Ledger Transaction Details
General ledger transactions are tied to account components using an accounting string identifier. To more easily consume the data, the six common identifiers in the accounting string are parsed out into separate columns such as Fund, Organization, and so on. The original accounting string is also included.
Field Name | Data Type | Comments |
---|---|---|
TransactionID |
String(50) |
|
Fund |
String(10) |
Parsed from the AccountingString |
Organization |
String(10) |
Parsed from the AccountingString |
Account |
String(10) |
Parsed from the AccountingString |
Program |
String(10) |
Parsed from the AccountingString |
Activity |
String(10) |
Parsed from the AccountingString |
Location |
String(10) |
Parsed from the AccountingString |
AccountingString |
String(150) |
The format of the accounting string is detailed in the Account Component Metadata |
TransactionNumber |
String(20) |
|
ReferenceNumber |
String(20) |
|
LedgerTransactionType |
String(40) |
ApprovedBudget, Donation, etc. |
LedgerDate |
DateTime |
|
Description |
String(250) |
|
DetailLineType |
String(6) |
Credit or Debit |
Amount |
Float |
|
Currency |
String(3) |
For example: USD |
Account Component Metadata
The list of components that make up the AccountingString value, and their order.
Field Name | Data Type | Comments |
---|---|---|
Name |
String(20) |
|
Description |
String(100) |
|
Code |
String(20) |
|
AccountingStringOrder |
Integer |
Position in the accounting string of this component’s value |
Colleague data types
The following data types can be imported from Colleague systems. Also see Common data types (Banner and Colleague).
Chart of Accounts Components
The list of components used by the chart of accounts.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
ComponentType |
String(20) |
Fund, Source, Location, Function, Unit, Object |
SubComponentType |
String(20) |
For example: Department, Account, GL Class, Fund Group |
Code |
String(10) |
|
Title |
String(50) |
|
ParentComponentID |
String(50) |
The Ellucian ID of the parent component, if part of a hierarchy |
Projects
The list of projects in the system.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
Name |
String(30) |
|
Description |
String(250) |
|
Status |
String(20) |
Active or Inactive |
TransactionStatus |
String(20) |
Available or Unavailable |
AccountType |
String(40) |
|
EffectiveStartDate |
DateTime |
|
EffectiveEndDate |
DateTime |
|
GrandID |
String(50) |
|
General Ledger Transaction Details
General ledger transactions are tied to account components using an accounting string identifier. To more easily consume the data, the six identifiers in the accounting string are parsed out into separate columns such as Fund, Source, and so on. The original accounting string is also included.
A transaction consists of multiple “detail lines,” and each line appears as a separate row in the import. To create a unique transaction ID for each item, an index is added to the transaction number. These detail lines are either credits or debits and can be to the same or different general ledger accounts.
Field Name | Data Type | Comments |
---|---|---|
TransactionID |
String(50) |
|
Fund |
String(10) |
Parsed from the AccountingString |
Unit |
String(10) |
Parsed from the AccountingString |
Object |
String(10) |
Parsed from the AccountingString |
Source |
String(10) |
Parsed from the AccountingString |
Function |
String(10) |
Parsed from the AccountingString |
Location |
String(10) |
Parsed from the AccountingString |
AccountingString |
String(150) |
Combination of all related component values, separated by hyphens, in the ComponentType order listed in the Chart of Accounts Components |
TransactionNumber |
String(20) |
|
ReferenceNumber |
String(20) |
|
LedgerTransactionType |
String(40) |
ApprovedBudget, Donation, etc. |
LedgerDate |
DateTime |
|
Description |
String(250) |
|
DetailLineType |
String(6) |
Credit or Debit |
Amount |
Float |
|
Currency |
String(3) |
For example: USD |
BudgetPeriodID |
String(50) |
Ellucian ID of the Fiscal Period |
BudgetOverride |
String(10) |
Override or Nooverride |
General Ledger Accounts
The list of general ledger accounts in the system.
Field Name | Data Type | Comments |
---|---|---|
AccountingString |
String(150) |
Combination of all related component values, separated by hyphens, in the ComponentType order listed in the Chart of Accounts Components |
Description |
String(250) |
|
Fund |
String(10) |
Parsed from the AccountingString |
Unit |
String(10) |
Parsed from the AccountingString |
Object |
String(10) |
Parsed from the AccountingString |
Source |
String(10) |
Parsed from the AccountingString |
Function |
String(10) |
Parsed from the AccountingString |
Location |
String(10) |
Parsed from the AccountingString |
Status |
String(20) |
Active or Inactive |
TransactionStatus |
String(20) |
Available or Unavailable |
AccountType |
String(40) |
|
EffectiveStartDate |
DateTime |
|
EffectiveEndDate |
DateTime |
|
GrandID |
String(50) |
|
Common data types (Banner and Colleague)
The following data types can be imported from Banner and Colleague systems.
Grants
The list of grants in the system.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
Title |
String(40) |
|
ReferenceCode |
String(20) |
|
ReportingSegment |
String(40) |
|
Status |
string(20) |
Active or Inactive |
Category |
String(40) |
|
AssistanceCategoryCode |
String(20) |
|
StartOn |
Date |
|
EndOn |
Date |
|
Amount |
Float |
|
Currency |
String(30) |
For example: USD |
PrincipalInvestigatorID |
String(50) |
Ellucian ID of a Person – not useful currently because importing Person data is not supported |
SponsorReferenceCode |
String(20) |
|
SponsorOrganizationID |
String(50) |
|
SponsorPersonID |
String(50) |
|
ProposalID |
String(50) |
|
Fiscal Period
The list of fiscal periods in the system.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
Title |
String(20) |
|
StartOn |
Date |
|
EndOn |
Date |
|
FiscalYearID |
String(50) |
|
Fiscal Year
The list of fiscal years in the system.
Field Name | Data Type | Comments |
---|---|---|
EllucianID |
String(50) |
|
Title |
String(20) |
|
ReportingSegment |
String(40) |
|
StartOn |
Date |
|
EndOn |
Date |
|
NumberOfPeriods |
Integer |
|
Status |
String(20) |
Defined, Open, or Closed |
YearEndAdjustment |
String(10) |
Active or Inactive |