Penn Computing

University of Pennsylvania
Penn Computing << go backback
BRS_DETAIL Table   Tables and Data Elements   BRS Home   Data Warehouse Home

BRS_DETAIL Table - Data Element Index

Select a data element to view its definition and its indexed, format, and null values.


Note: while not stored in the BRS_Detail table, Student Name is in the view of BRS_Detail that is used by the Business Objects universes. If you wish to include the name in a Business Objects query, it is advisable to use Student Name from the BRS_Detail_v, instead of getting the name from the Person table.

Data element

Definition

ACCOUNT_1

Indexed - no
Format - char (9)
May be null? yes

The 9-digit legacy number tied to a deferred income for charges, or liability account for payments. Charges could be for items such as tuition, residence or dining; payments might be in the form of financial aid or cash.

ACCOUNT_1_BC

Indexed - no
Format - char (1)
May be null? yes

The budgetary control character that represents the level at which funds availability checking occurs, for the 26-digit General Ledger account that has been mapped to Account_1.

COA_BC is the third segment of the Accounting Flexfield. 

Examples: 1 (CNAC/ORG/FUND Year-To-Date); T (All Funds Checks). 

Values:
0 Project-to-Date for capital projects
1 CNAC/ORG/FUND Year-To-Date
2 CNAC/ORG/FUND/CREF Year-To-Date
4 CNAC/ORG/FUND/CREF Project-to-Date
A Funds Check parent of 1
B Funds Check parent of 2
D Funds Check parent of 4
T All Funds Checks

 

ACCOUNT_1_CNAC

Indexed - no
Format - char (3)
May be null? yes

The 3-character center Net Asset Class (NAC) code, for the 26-digit General Ledger account that has been mapped to Account_1. The first two positions of the COA_CNAC identify the school or center. The last position identifies the Net Asset Class: 0 (Unrestricted); 1 (Temporarily Restricted); 2 (Permanently Restricted). 

COA_CNAC is the first segment of the Accounting Flexfield.  See CNAC_CODES documentation for additional information about this accounting segment.

Example: 880 (Medical center, Unrestricted) 

Values:
Refer to the CNAC_Codes table for values.

ACCOUNT_1_CREF

Indexed - no
Format - char (4)
May be null? yes

The 4-character Center Reference code, for the 26-digit General Ledger account that has been mapped to Account_1. This is an identifier uniquely defined by each school or center. 

COA_CREF is used to record information that is important to a school or center but is inappropriate for any other segment of the Accounting Flexfield. The value of the center Reference code is unique within a school or center. 

COA_CREF is the seventh and last segment of the Accounting Flexfield.  See CENTER_REF_CODES documentation for additional information about this accounting segment.

See the definition for CENTER_REF_CODES / CENTER_REF_CODE. 

Examples: 4045 (Graduate Programs); 4091 (SAS Newsletter) 

Values:
Refer to the center_REF_CODES table for values. 

ACCOUNT_1_FUND

Indexed - no
Format - char (6)
May be null? yes

The 6-character fund number, for the 26-digit General Ledger account that has been mapped to Account_1. A fund is the unique identifier for a specific set of financial resources that needs tracking or management. 

COA_FUND is the fourth segment of the Accounting Flexfield.  See FUND_CODES documentation for additional information about this accounting segment.

Examples: 000000 (General Unrestricted Fund); 010201 (SAS: GEN FUND 1) 

Values:
Refer to the FUND_CODES table for values.

ACCOUNT_1_OBJ

Indexed - no
Format - char (4)
May be null? yes

The 4-character OBJECT code, for the 26-digit General Ledger account that has been mapped to Account_1. Identifies the asset, liability, revenue, or expense. 

COA_OBJECT is the fifth segment of the Accounting Flexfield. See OBJECT_CODES documentation for additional information about this accounting segment.

Examples: 5220 (EXTERNAL OFFICE SUPPLIES); 1149 (CASH SUSPENSE) 

Values:
Refer to the OBJECT_CODES table for values.

ACCOUNT_1_ORG

Indexed - no
Format - char (4)
May be null? yes

The 4-character ORGANIZATION code, for the 26-digit General Ledger account that has been mapped to Account_1. This is a subdivision of the University created for management purposes. 

An ORGANIZATION belongs to only one responsibility center, and its ORGANIZATION code is unique. That is, no two ORGANIZATIONs will have the same values for COA_ORG. 

COA_ORG is the second segment of the Accounting Flexfield. See ORG_CODES documentation for additional information about this accounting segment.

Examples: 0702 (Wharton Finance); 0705 (Wharton Legal Studies) 

Values:
Refer to the ORG_CODES table for values.

ACCOUNT_1_PROG

Indexed - no
Format - char (4)
May be null? yes

The 4-character PROGRAM code, for the 26-digit General Ledger account that has been mapped to Account_1. This is an activity or work process commonly defined across the University for tracking a PROGRAM's activity across schools and centers (or across organizations within a school or center).

COA_PROGRAM is the sixth segment of the Accounting Flexfield.  See PROGRAM_CODES documentation for additional information about this accounting segment.

Examples: 7311 (Alumni Relations); 0001 (Discretionary) 

Values:
Refer to the PROGRAM_CODES table for values.

ACCOUNT_1_RESP_ORG

Indexed - no
Format - char (4)
May be null? yes

The 4-character code for the organization responsible for managing the fund, for the 26-digit General Ledger account that has been mapped to Account_1. Many organizations may use the same fund, but only one organization -- the COA_RESPONSIBLE_ORG -- is accountable for managing the fund. Those who are authorized to access records for the COA_RESPONSIBLE_ORG for the fund may access all records for the fund, regardless of the value of the COA_ORG in the COA_ACCOUNT for the record. 

Examples: 0011 (NYC Penn Club); 0215 (French Institute). 

Values:
Refer to the ORG_CODES table for values. 

ACCOUNT_2

Indexed - no
Format - char (9)
May be null? yes

The 9-digit legacy number tied to a revenue or expense account.

ACCOUNT_2_BC

Indexed - no
Format - char (1)
May be null? yes

The budgetary control character that represents the level at which funds availability checking occurs, for the 26-digit General Ledger account that has been mapped to Account_2.

COA_BC is the third segment of the Accounting Flexfield. 

Examples: 1 (CNAC/ORG/FUND Year-To-Date); T (All Funds Checks). 

Values:
0 Project-to-Date for capital projects
1 CNAC/ORG/FUND Year-To-Date
2 CNAC/ORG/FUND/CREF Year-To-Date
4 CNAC/ORG/FUND/CREF Project-to-Date
A Funds Check parent of 1
B Funds Check parent of 2
D Funds Check parent of 4
T All Funds Checks

ACCOUNT_2_CNAC

Indexed - yes
Format - char (3)
May be null? yes

The 3-character center Net Asset Class (NAC) code, for the 26-digit General Ledger account that has been mapped to Account_2. The first two positions of the COA_CNAC identify the school or center. The last position identifies the Net Asset Class: 0 (Unrestricted); 1 (Temporarily Restricted); 2 (Permanently Restricted).  See CNAC_CODES documentation for additional information

COA_CNAC is the first segment of the Accounting Flexfield. 

Example: 880 (Medical center, Unrestricted) 

Values:
Refer to the CNAC_Codes table for values.

ACCOUNT_2_CREF

Indexed - yes
Format - char (4)
May be null? yes

The 4-character Center Reference code, for the 26-digit General Ledger account that has been mapped to Account_2. This is an identifier uniquely defined by each school or center. 

COA_CREF is used to record information that is important to a school or center but is inappropriate for any other segment of the Accounting Flexfield. The value of the center Reference code is unique within a school or center. 

COA_CREF is the seventh and last segment of the Accounting Flexfield.  See CENTER_REF_CODES documentation for additional information about this accounting segment.

See the definition for CENTER_REF_CODES / CENTER_REF_CODE. 

Examples: 4045 (Graduate Programs); 4091 (SAS Newsletter) 

Values:
Refer to the center_REF_CODES table for values. 

ACCOUNT_2_FUND

Indexed - yes
Format - char (6)
May be null? yes

The 6-character fund number, for the 26-digit General Ledger account that has been mapped to Account_2. A fund is the unique identifier for a specific set of financial resources that needs tracking or management. 

COA_FUND is the fourth segment of the Accounting Flexfield.  See FUND_CODES documentation for additional information about this accounting segment.

Examples: 000000 (General Unrestricted Fund); 010201 (SAS: GEN FUND 1) 

Values:
Refer to the FUND_CODES table for values.

ACCOUNT_2_OBJ

Indexed - yes
Format - char (4)
May be null? yes

The 4-character OBJECT code, for the 26-digit General Ledger account that has been mapped to Account_1. Identifies the asset, liability, revenue, or expense. 

COA_OBJECT is the fifth segment of the Accounting Flexfield. See OBJECT_CODES documentation for additional information about this accounting segment.

Examples: 5220 (EXTERNAL OFFICE SUPPLIES); 1149 (CASH SUSPENSE) 

Values:
Refer to the OBJECT_CODES table for values.

ACCOUNT_2_ORG

Indexed - yes
Format - char (4)
May be null? yes

The 4-character ORGANIZATION code, for the 26-digit General Ledger account that has been mapped to Account_2. This is a subdivision of the University created for management purposes. 

An ORGANIZATION belongs to only one responsibility center, and its ORGANIZATION code is unique. That is, no two ORGANIZATIONs will have the same values for COA_ORG. 

COA_ORG is the second segment of the Accounting Flexfield. See ORG_CODES documentation for additional information about this accounting segment.

Examples: 0702 (Wharton Finance); 0705 (Wharton Legal Studies) 

Values:
Refer to the ORG_CODES table for values.

ACCOUNT_2_PROG

Indexed - yes
Format - char (4)
May be null? yes

The 4-character PROGRAM code, for the 26-digit General Ledger account that has been mapped to Account_2. This is an activity or work process commonly defined across the University for tracking a PROGRAM's activity across schools and centers (or across organizations within a school or center).

COA_PROGRAM is the sixth segment of the Accounting Flexfield.  See PROGRAM_CODES documentation for additional information about this accounting segment.

Examples: 7311 (Alumni Relations); 0001 (Discretionary) 

Values:
Refer to the PROGRAM_CODES table for values.

ACCOUNT_2_RESP_ORG

Indexed - no
Format - char (4)
May be null? yes

The 4-character code for the organization responsible for managing the fund, for the 26-digit General Ledger account that has been mapped to Account_2.. Many organizations may use the same fund, but only one organization -- the COA_RESPONSIBLE_ORG -- is accountable for managing the fund. Those who are authorized to access records for the COA_RESPONSIBLE_ORG for the fund may access all records for the fund, regardless of the value of the COA_ORG in the COA_ACCOUNT for the record. 

Examples: 0011 (NYC Penn Club); 0215 (French Institute). 

Values:
Refer to the ORG_CODES table for values. 

ACCT_FEED

Indexed - no
Format - char (1)
May be null? yes

Denotes whether any part of transaction fed to General Ledger.
Values:
Null   did not feed to the GL
2 	   fed to the GL

ACCT_AMOUNT

Indexed - no
Format - number(10,2)
May be null? yes

ACCOUNT_AMOUNT is used to keep track of money that either comes from or goes to the General Ledger. In the case of Charges (where C_P = 'C'), the ACCT_AMOUNT stores the amount that was reported to the GL. For Payments (where C_P = 'P'), the ACCOUNT_AMOUNT plus the PAID_APP_AMOUNT indicates the amount retrieved from the GL. For payments, an ACCOUNT_AMOUNT different from zero indicates an unapplied portion of that transaction.

AMOUNT

Indexed - no
Format - number (10,2)
May be null? yes

The amount of the transaction.

BATCH_DATE

Indexed - yes
Format - date
May be null? no

The date this transaction was submitted to the billing system.

This information is stored in the Warehouse in date format. In Business Objects, it is displayed as specified in the desktop operating system settings. It is recommended that users specify a date format that includes 4 digits for the year. For example: 3/10/2004.

BATCH_REF

Indexed - no
Format - varchar2 (6)
May be null? yes

The batch reference code for this transaction. The first three characters indicate the type of batch load.

BILL_DATE

Indexed - no
Format - date
May be null? yes

The date this transaction was billed for the first time. Null values indicate transactions which have not yet been billed.

This information is stored in the Warehouse in date format. In Business Objects, it is displayed as specified in the desktop operating system settings. It is recommended that users specify a date format that includes 4 digits for the year. For example: 3/10/2004.

BRS_DESC

Indexed - no
Format - varchar2 (30)
May be null? yes

The description related to the subcode. This may be an ad-hoc description, different from the default description for the subcode, as based on a weekly feeder or other override. This is the description used for the subcode at the time the detail record was created, and is not updated over time. For a list of current subcode descriptions, refer to the BRS_SUBCODE table.

BRS_TERM

Indexed - yes
Format - char (3)
May be null? no

The 3-digit Term Code in the format TYY, where T is 1=Fall, 2=Spring, 3=Summer1, 4=Summer2 and YY is the 2-digit calendar year.

Example: 103 (corresponds to 2003C, which means Fall 2003), 203 (corresponds to 2003A, which means Spring 2003), 303 and 403 (representing Summer 1 and 2 sessions, respectively; corresponds to 2003B, which means Summer 2003)

BRS_USER

Indexed - no
Format - char (1)
May be null? yes

This is the user code for the subcode at the time the detail record was created, and is not updated over time. For a list of current subcode user codes, refer to the BRS_SUBCODE table.
Values:
A = Student Financial Aid
B = Billable Agencies
C = Cash payments
D = Dining / Dining Refunds
E = Voided Refunds
F = Fee Codes
H = Student Health
I = Info Assoc Inc Package
L = Short Term / Long Term Loans
M = Blue Cross/ Blue Shield
O = Auxiliary Charges
R = Residence/Housing
T = Tuition
W = Deferments
X = Clearing Accounts
Y = Student Deposits
Z = Bad Checks

C_P

Indexed - no
Format - char (1)
May be null? yes

Indicates whether the transaction was a charge or payment. This is the indicator for the subcode at the time the detail record was created, and is not updated over time. For a list of current subcode C_P values, refer to the BRS_SUBCODE table.

Values:
C(harge)
P(ayment)

DETAIL

Indexed - no
Format - char (1)
May be null? yes

Indicates whether a record can be found in the current BURSAR.DETAIL file on the mainframe (Detail ='Y'). Records with a DETAIL value of 'N' indicate that the data has been purged from the mainframe BURSAR.DETAIL file during the annual BRS purge, and now resides in any of the Intermediate, History or Inert files. In order to be purged on the mainframe, all of the following must be true: 1) the PAID_APP_DATE is not null, 2) the record is fully paid and applied, i.e., AMOUNT = APP_AMOUNT, 3) the BATCH_DATE value must be up to and including the last bill date of the BRS fiscal year (the billing cycle as of date in BR00720J), 4) the record is not from the Summer2 or Fall terms of the current year, and 5) BILL_DATE is not null.

Values:
Y   Current detail record
N   Not a current detail record

LAST_ACTIVITY_DATE

Indexed - no
Format - date
May be null? yes

The date this record was last modified in the Data Warehouse.

This information is stored in the Warehouse in date format. In Business Objects, it is displayed as specified in the desktop operating system settings. It is recommended that users specify a date format that includes 4 digits for the year. For example: 3/10/2004.

PAID_APP_AMOUNT

Indexed - no
Format - number(10,2)
May be null? yes

The applied amount of this transaction. This may be less that the value in Amount. Transactions can be fully or partially paid

PAID_APP_DATE

Indexed - no
Format - date
May be null? yes

The date this transaction was fully applied (paid).

This information is stored in the Warehouse in date format. In Business Objects, it is displayed as specified in the desktop operating system settings. It is recommended that users specify a date format that includes 4 digits for the year. For example: 3/10/2004.

PENN_ID

Indexed - yes
Format - char(8)
May be null? yes

The 8-digit identification number assigned to the employee by the Penn Community system. For example: 77777777. No two persons have the same Penn_ID. Only persons affiliated with the University will be assigned a Penn_ID.

SSN

Indexed - yes
Format - char(9)
May be null? no

The 9-digit Social Security Number of the student, or the University-assigned Student ID.

SUBCODE

Indexed - yes
Format - char(5)
May be null? no

A five-digit code used to designate a particular charge or payment. The subcode description used for the transaction. Values are generally grouped as follows:

0xxxx = Tuition, Acceptance Fees, General Fees 
     Special Fees & Other
1xxxx = Housing/Fraternities
2xxxx = Dining
3xxxx = Fees (schools, off-campus)
4xxxx = Student deposits
5xxxx = Refunds, Telephone, Damages, Short Term Loans & Other
6xxxx = Loans, Scholarships, Fac/Staff, RA, TA, 
          RF & and dept awards
7xxxx = Temporary Credits, Outside agencies
8xxxx = Outside programs
9xxxx = Payments, Voided refunds

SUBCODE_SEQ

Indexed - yes
Format - char(3)
May be null? no

This sequence maintains uniqueness for the bursar subcode within a file. When a subcode is used more than once, the sequence increments. The sequence number is three digits, beginning with 001 and incrementing as needed.

Values:
001 - 999

TERM

Indexed - no
Format - char(5)
May be null? yes

The SRS term corresponding to the BRS_Term. Penn divides the academic year into 3 terms or semesters: Fall, Spring, and Summer. Terms are designated by the 4-digit calendar year, followed by a term code. The Spring term code is A, the Summer term code is B, and the Fall term code is C. Since the BRS_Term is in TYY format (where the first digit represents the term, and the second two digits the calendar year), the BRS_Term values of 1 through 4 (1=Fall, 2=Spring, 3=Summer1, 4=Summer2) are translated to the appropriate letter term, and the 2-digit year is converted to a 4-digit format.

Example: 2003C means Fall 2003 (corresponds to BRS_Term 103), 2003A means Spring 2003 (corresponds to BRS_Term 203), 2003B means Summer 2003 (correponds to BRS_Terms 303 and 403, representing Summer 1 and 2 sessions, respectively)

TERM_SESSION

Indexed - no
Format - char(1)
May be null? yes

For summer terms, represents the session in which the student was billed.

Values: 
1     the first summer session
2     the second summer session
S     special session
Null  12 week session

TUIT_AUD_CODE

Indexed - no
Format - char(1)
May be null? yes

Tuition Calculation flag.
Values: 
Y   	Calc
Null    Do Not Calc
BRS_DETAIL Table   Tables and Data Elements   BRS Home   Data Warehouse Home

Questions about this page? Email us at da-staff@isc.upenn.edu

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania