Penn Computing

University of Pennsylvania
Penn Computing << go backback

TELECOM_INVOICE_SUMMARY Table
   Tables and Data Elements   General Ledger Home   Data Warehouse Home

TELECOM_INVOICE_SUMMARY Table - Data Element Index

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



Data element Definition

ACCOUNTING_PERIOD

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

The Accounting Period stated in MON-YY format. MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an ACCOUNTING_PERIOD are not the same as the first and last day of the calendar month. 

Example: JUL-99 (July 1999, which occurs in fiscal year 2000). 

Values:
List of values not available.
BUILDING_ID

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

The 3-letter building code used by ISC Networking. This value is not from the same codeset as Facilities Space@Penn data.

Values:
List of values not available.
CALENDAR_MONTH

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

The number that identifies the calendar month (or accounting period). 

Example: 01 (January); 11 (November). 

Values:
01        January
02        February
03        March
04        April
05        May
06        June
07        July
08        August
09        September
10        October
11        November
12        December
13        Adjustment period
CALENDAR_YEAR

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

The calendar year for the ACCOUNTING_PERIOD. The calendar year begins January 1 and ends December 31. Example: 1999 (the CALENDAR_YEAR for ACCOUNTING_PERIOD JUL-99). 
Values:
List of values not available.
COA_ACCOUNT

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

The seven segment values that comprise the 26-position Accounting Flexfield. The segments are COA_CNAC, COA_ORG, COA_BC, COA_FUND, COA_OBJECT, COA_PROGRAM, and COA_CREF. 

Example: 40042274525799519120021438.

See also COA_CNAC, COA_ORG, COA_BC, COA_FUND, COA_OBJECT, COA_PROGRAM, and COA_CREF.

Values:
List of values not available.
COA_BC

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

The budgetary control character that represents the level at which funds availability checking occurs. 

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
COA_CNAC

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

The 3-character center Net Asset Class (NAC) code. 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. 

Example: 880 (Medical center, Unrestricted) 

Values:
Refer to the CNAC_Codes table for values.
COA_CREF

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

The 4-character Center Reference code. 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 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.
COA_FUND

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

The 6-character fund number. 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. 

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

Values:
Refer to the FUND_CODES table for values.
COA_OBJECT

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

The 4-character OBJECT code. Identifies the asset, liability, revenue, or expense. 

COA_OBJECT is the fifth segment of the Accounting Flexfield.

Examples: 5261 (INT PHONE ALLOC); 5262 (INT PHONE EQP); 5263 (INT TOLL CHGS) 

Values:
Refer to the OBJECT_CODES table for values.
COA_ORG

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

The 4-character ORGANIZATION code. 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.

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

Values:
Refer to the ORG_CODES table for values.
COA_PROGRAM

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

The 4-character PROGRAM code. 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. 

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

Values:
Refer to the PROGRAM_CODES table for values.
COA_RESPONSIBLE_ORG

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

The 4-character code for the organization responsible for managing the fund. 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.
CYCLE_END_DATE

Indexed - yes
Format - date
May be null? yes

The beginning date of the billing cycle for which the item was invoiced.

Values:
List of values not available.
CYCLE_START_DATE

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

The end date of the billing cycle for which the item was invoiced.

Values:
List of values not available.
DESC1

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

The description of the type of charge (e.g., line fee, handset/equipment cost, voicemail, outlet fee, installation, long distance calls, Philadelphia calls, etc.).

Values:
List of values not available.
DETAIL_EXISTS

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

Indicates whether there are supporting TELECOM_CALL_DETAIL records for the transaction.
Values:
List of values not available.
FISCAL_MONTH_SEQ

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

The month (or accounting period) of the fiscal year. This field is used for sorting.

Examples: 01 (July); 11 (May). See also FISCAL_YEAR 

Values:
01        July
02        August
03        September
04        October
05        November
06        December
07        January
08        February
09        March
10        April
11        May
12        June
13        Adjustment period
FISCAL_YEAR

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

The financial year in which the ACCOUNTING_PERIOD falls. Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year. 

Example: 2000 (fiscal year that began July 1, 1999, and ended June 30, 2000) 

Values:
List of values not available. 
INVOICE_DATE

Indexed - yes
Format - date
May be null? yes

The date on which the invoice was created.

Values:
List of values not available.
ISC_INVOICE_NUMBER

Indexed - no
Format - number(7)
May be null? yes

Invoice Number from the ISC Telecommunications Billing System.

Values:
List of values not available.
ITEM

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

Identifies the phone number, MAC Address of a PennNet HandSet, Outlet ID for a PennNet Phone Port or department user ID billed for the charge.

Values:
List of values not available.
LAWSONID

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

Lawson ID is a 6 digit cost center number used by UPHS. It only appears on charges against the Interfund number, 210-2100-1-000000-xxxx-0000-0000.

Values:
List of values not available.
LOCATION

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

The location of the line, handset or outlet id. Values of this field are usually the room number or something similar. This information is made available to Public Safety via a 511 feed. If the charge is for a “PENNNET PHONE NBR APPEARANCE”, then this field will contain the phone number(s) that appears on that set.

Values:
List of values not available.
START_BILL_DATE

Indexed - no
Format - date
May be null? yes

The date the service was first activated and billed.

Values:
List of values not available.
STOP_BILL_DATE

Indexed - no
Format - date
May be null? yes

Stop Bill Date may be null, or, if not null, represents the date after which service was no longer billed, due to a cancellation or deactivation.

Values:
List of values not available.
TRAN_CODE

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

A 3-digit number that identifies the type of charge.

Values:
List of values not available.
TRAN_CODE_BRIEF

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

The brief description of the 3-digit number that identifies the type of charge.

Values:
List of values not available.
TRAN_CODE_DESC

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

The long description of the 3-digit number that identifies the type of charge.

Values:
List of values not available.
TRANSACTION_AMOUNT

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

The amount billed.

Values:
List of values not available.
TRANSACTION_SEQ

Indexed - yes
Format - number(22)
May be null? no

The unique sequence number for the transaction.

Values:
List of values not available.

TELECOM_INVOICE_SUMMARY Table
   Tables and Data Elements   General Ledger 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