| Data element |
Definition |
ACCT_PER_INVOICE_DATED
Indexed - yes
Format - char (6)
May be null - no |
The accounting period in which the INVOICE_DATE falls. The value is stated
in MON-YY format. MON is the calendar month (stored in upper case), and
YY is the calendar year.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Note: the beginning and ending dates of an accounting period are not
the same as the first and last day of the calendar month.
Note: because the ACCT_PER_INVOICE_DATED is based on the INVOICE_DATE,
there are no records for the ADJ period.
Example: SEP-02 (September, 2002, which occurs in fiscal year 2003).
|
|
ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The summarized amount of the actual dollars for the line item (SB_OBJECT_PARENT)
for the invoice (INTERNAL_REF_NO). This is the total of the ACTUAL_AMT
of the BRIMFUND_OBJ_EXP records that were not included in other invoices
and whose GL_EXTRACT_DATE falls between the EXPENSE_START_DATE and the
EXPENSE_END_DATE.
See also BRIM_MASTER. EXPENSE_START_DATE and BRIM_MASTER. EXPENSE_END_DATE.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: AREXCF.actamt (current records) or AREXHF.actamt (history
records)
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIMFUND_SB_EXP record was loaded into the Data Warehouse.
This is usually the same date that the record was extracted from BRIM.
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. (To specify the date format in Windows 95, choose
the Regional Settings of the Control Panel, select the Date tab and specify
the Short date style. In Windows, use the International option of the
Control Panel. On the Macintosh, use the Date & Time Control Panel.)
Example: 9/19/2002
|
|
BRIM_HISTORY_STATUS
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code that indicates whether the record has ever been copied
to the BRIM history tables.
From time to time, the Office of Research Services uses the BRIM feature
to close a period. When this is done, records are flagged as being history
records, and are copied to the BRIM history table (AREXHF). Any records
for invoices that have been voided or paid in full are then deleted from
the BRIM current table (AREXCF). Any records for invoices that have NOT
been voided or paid in full remain in the current table.
The BRIMFUND_SB_EXP table contains data from the BRIM history table,
supplemented by the data from the BRIM current table.
Values:
C records for the invoice exist only in the BRIM
current table
H records for the invoice exist in the BRIM history
tables
BRIM source: AREXCF.current (current records) or AREXHF.current (history
records)
|
|
CALENDAR_YR_INVOICE_DATED
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character number that identifies the calendar year of the accounting
period in which the INVOICE_DATE falls. The calendar year begins January
1 and ends December 31.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Example: 1997 (the calendar year for INVOICE_DATE 09/01/1997, which falls
in SEP-97).
|
|
FISCAL_MON_SEQ_INV_DATED
Indexed - yes
Format - char (2)
May be null? no
|
The month (accounting period) of the fiscal year in which the INVOICE_DATE
falls. This field is used for sorting.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Note: because the FISCAL_MON_SEQ_INV_DATED is ultimately based on the
INVOICE_DATE, there are no records for month 13 (the ADJ period).
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
|
|
FISCAL_YR_INVOICE_DATED
Indexed - yes
Format - char (4)
May be null? no
|
The financial year in which the INVOICE_DATE falls. Penn's fiscal year
begins July 1 of one calendar year and ends June 30 of the next calendar
year.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Example: 1998 (fiscal year beginning July 1, 1997, and ending June 30,
1998, in which INVOICE_DATE 09/01/1997 falls)
|
|
FUND_CODE
Indexed - yes
Format - char (6)
May be null? no
|
The 6-character code that identifies the sponsored project fund to which
the invoice applies. The fund code is the unique identifier for a specific
set of financial resources that needs tracking or management.
Example: 539354
Values: Refer to the BRIM_FUNDS table for values.
BRIM source: AREXCF.coafund (current records) or AREXHF.coafund (history
records)
|
|
FUND_INVOICE_NUMBER
Indexed - yes
Format - char (20)
May be null? yes
|
A value in the format FFFFFF-####, where FFFFFF is the FUND_CODE for
the sponsored project fund for which the invoice was generated, and ####
is the sequence number (with leading zeroes) of the invoice for the FUND_CODE.
That is, 512345-0001 is the first invoice for fund 512345.
Example: 539354-0014
BRIM source: AREXCF.fundinv (current records) or AREXHF.fundinv (history
records)
|
|
FUND_RESP_ORG
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code for the organization responsible for managing the
fund (FUND_CODE). Many organizations may use the same fund, but only one
organization - the FUND_RESP_ORG-is accountable for managing the fund.
Only those who are authorized to access records for the FUND_RESP_ORG
may access the BRIMFUND_SB_EXP record.
Example: 0103 (Biology)
Values: Refer to the ORG_CODES table for values.
BRIM source: ARINVT.lead
|
|
FYTD_ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of the actual dollars for the line item (SB_OBJECT_PARENT)
for the fund (FUND_CODE) for the fiscal year
(FISCAL_YR_INVOICE_DATED), including the ACTUAL_AMT of this invoice.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The variance (difference) between the actual amount and the invoiced
amount for the line item (SB_OBJECT_PARENT) for the fund (FUND_CODE) for
the fiscal year
(FISCAL_YR_INVOICE_DATED). That is, FYTD_ACTUAL_AMT - FYTD_INVOICED_AMT.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_INVOICED_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount invoiced for the line item (SB_OBJECT_PARENT) for the
fund (FUND_CODE) for the fiscal year
(FISCAL_YR_INVOICE_DATED), including the INVOICED_AMT of this invoice.
The invoiced amount is the amount the sponsor was asked to pay for the
line item; it may or may not be the same as the actual amount.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
INTERNAL_REFERENCE_NO
Indexed - yes
Format - char (8)
May be null? no
|
A code of up to 8 characters that uniquely identifies the BRIM invoice.
Example: 15719
BRIM source: AREXCF.invno (current records) or AREXHF.invno (history
records)
|
|
INVOICE_DATE
Indexed - no
Format - date (7)
May be null? no
|
The date of the invoice, per the accountant in the Office of Research
Services who created the invoice in BRIM.
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. (To specify the date format in Windows 95, choose
the Regional Settings of the Control Panel, select the Date tab and specify
the Short date style. In Windows, use the International option of the
Control Panel. On the Macintosh, use the Date & Time Control Panel.)
Example: 9/13/2002
BRIM source: AREXCF.invdte (current records) or AREXHF.invdte (history
records)
|
|
INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The variance (difference) between the actual amount and the invoiced
amount for the line item (SB_OBJECT_PARENT) for the invoice (INTERNAL_REF_NO).
That is, ACTUAL_AMT - INVOICED_AMT.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: AREXCF.variance (current records) or AREXHF.variance (history
records)
|
|
INVOICED_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The invoiced amount for the line item (SB_OBJECT_PARENT) for the invoice
(INTERNAL_REF_NO). The invoiced amount is the amount the sponsor is asked
to pay for the line item on the invoice; it may or may not have the same
value as the ACTUAL_AMT.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: AREXCF.bilamt (current records) or AREXHF.bilamt (history
records)
|
|
MONTH_INVOICE_DATED
Indexed - yes
Format - char (2)
May be null? no
|
The 2-character number that identifies the calendar month (accounting
period) in which the INVOICE_DATE falls.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Note: because the MONTH_INVOICE_DATED is ultimately based on the INVOICE_DATE,
there are no records for month 13 (the ADJ period).
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
|
|
PJTD_ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of the actual dollars to date for the line item (SB_OBJECT_PARENT)
for the fund (FUND_CODE), including the ACTUAL_AMT of this invoice.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The variance (difference) between the actual amount to date and the invoiced
amount to date for the line item (SB_OBJECT_PARENT) for the fund (FUND_CODE).
That is, PJTD_ACTUAL_AMT - PJTD_INVOICED_AMT.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_INVOICED_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount invoiced to date for the line item (SB_OBJECT_PARENT)
for the fund (FUND_CODE), including the INVOICED_AMT of this invoice.
The invoiced amount is the amount the sponsor is asked to pay for the
line item on the invoice; it may or may not have the same value as the
actual amount.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: AREXCF.ptdamt (current records) or AREXHF.ptdamt (history
records)
|
|
QUARTER_SEQ_INVOICE_DATED
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year in which the INVOICE_DATE falls.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
SB_OBJECT_PARENT
Indexed - yes
Format - char (4)
May be null? no
|
The 4-character code for the Object in the General Ledger's chart of
accounts that serves as the parent (or rollup group) for other Objects,
allowing amounts to be summarized at the parent level.
An OBJECT_CODE identifies the asset, liability, revenue, or expense.
On BRIM invoices, an SB_OBJECT_PARENT corresponds to an invoice line.
In the General Ledger, a given parent Object may be associated with more
than one child Object, and a given child Object may have more than one
parent. However, BRIM includes only Objects that fall under Object parents
SB01 through SB41, and a given Object has only one SB_OBJECT_PARENT. All
values for SB_OBJECT_PARENT begin with 'SB'.
Example: SB01 (Administrative Salaries)
Values: Refer to the BRIM_EXP_CODES table for values.
BRIM source: AREXCF.objpar (current records) or AREXHF.objpar (history
records)
|
|
SB39_DESC
Indexed - no
Format - char (12)
May be null? yes
|
For most records, if the SB_OBJECT_PARENT is SB39, SB39_DESC contains
a short description (up to 12 characters long) of the invoice line item.
If the SB_OBJECT_PARENT is not SB39, SB39_DESC is null (which will appear
blank in reports).
For records converted from the legacy system to BRIM, SB39_DESC may be
'Conversion,' regardless of the value of the SB_OBJECT_PARENT.
Examples: 'Lab Tests', 'Conversion'
BRIM source: AREXCF.SB39exp (current records) or AREXHF.SB39exp (history
records)
|
|
SORT_PERIOD_INVOICE_DATED
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period in which the INVOICE_DATE falls. The value is stated
YYYYMM format. YYYY is the calendar year, and MM is the calendar month.
The INVOICE_DATE is the date of the invoice, per the accountant in the
Office of Research Services who created the invoice in BRIM.
Note: the beginning and ending dates of an accounting period are not
the same as the first and last day of the calendar month.
Note: because the SORT_PERIOD_INVOICE_DATED is ultimately based on the
INVOICE_DATE, there are no records for month 13.
Example: 199709 (the SORT_PERIOD_INVOICE_DATED for INVOICE_DATE 09/01/1997,
which falls in SEP-97)
|
|
SPONSOR_CODE
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code that identifies the external organization that sponsors
the fund.
Examples: 1010 Department of the Army); 1529 (Proctor & Gamble).
Values: Refer to the FUND_SPONSORS table for values.
BRIM source: AREXCF.custno (current records) or AREXHF.custno (history
records)
|
|
VOID_INVOICE_FLAG
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code used to identify voided invoice records.
Values:
N a normal invoice
Y a voided invoice
BRIM source: AREXCF.arstat (current records) or AREXHF.arstat (history
records)
|
