| Data element |
Definition |
ACCOUNTANT_NAME
Indexed - no
Format - char (20)
May be null - yes |
The name of the accountant in the Office of Research Services who is
responsible for monitoring the FUND_CODE.
Note: the value is stored in upper case.
Example: 'ALIYU MOHAMMED'
BRIM source: ARRECR.code (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_description)
|
|
ACCT_DESK_NUMBER
Indexed - yes
Format - char (4)
May be null? no
|
The code that identifies the desk of the accountant in the Office of
Research Services who is responsible for monitoring the FUND_CODE.
Example: 7
BRIM source: ARRECR.taxdist (fed to BRIM from BEN Financials via the
SBTFUND.txt extract - fnd_flex_values_vl.flex_value)
|
|
ACCT_PER_SNAPSHOT
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period when the BRIMAUTOPAY_PROFILES record was snapshot
This is based on the BRIM_EXTRACT_DATE, and is stated in MON-YY format.
MON is the calendar month (stored in upper case), and YY is the calendar
year.
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_SNAPSHOT is based on the BRIM_EXTRACT_DATE,
there is no snapshot for the ADJ period.
Example: SEP-02 (September, 2002, which occurs in fiscal year 2003).
|
|
ACCT_PHONE_NUMBER
Indexed - no
Format - char (12)
May be null? yes
|
The telephone number of the accountant in the Office of Research Services
who is responsible for monitoring the FUND_CODE.
Example: 215/573-6716
BRIM source: ARRECR.fob
|
|
AUTO_PAY_FREQUENCY
Indexed - no
Format - number (4)
May be null? yes
|
A number used with AUTO_PAY_PERIOD to indicate how often an automatic
payment installment is due for the FUND_CODE.
Example: If AUTO_PAY_PERIOD is M, and AUTO_PAY_FREQUENCY is 3, an automatic
payment installment is due every 3 months (that is, quarterly).
BRIM source: ARRECR.period
|
|
AUTO_PAY_PERIOD
Indexed - no
Format - char (1)
May be null? yes
|
A one-character code used with AUTO_PAY_FREQUENCY to indicate how often
an automatic payment installment is due for the FUND_CODE.
Example: If AUTO_PAY_PERIOD is M, and AUTO_PAY_FREQUENCY is 3, an automatic
payment installment is due every 3 months (that is, quarterly).
Values:
M (months); D (days)
BRIM source: ARRECR.period
|
|
AUTOPAY_REFERENCE_NO
Indexed - yes
Format - char (8)
May be null? no
|
A code of up to 8 characters that identifies an automatic payment profile
for the sponsor. The value is usually the same as the value of FUND_CODE,
but BRIM does not require the values to be the same.
Example: 539354
BRIM source: ARRECR.autono (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_vl.flex_value)
|
|
BILLING_FORMAT_CODE
Indexed - yes
Format - char (2)
May be null? yes
|
A 2-character code that indicates the format in which the bill for the
fund is rendered.
Examples: 07 (Automatic Payments); 08 (Invoiced by Department)
Values:
Refer to the FUND_BILLING_FORMAT_CODES table for
values.
BRIM source: ARRECR.salesmn (fed to BRIM from BEN Financials via the
SBTFUND.txt extract - fnd_flex_values_vl.attribute27)
|
|
BILLING_FREQUENCY_CODE
Indexed - yes
Format - char (2)
May be null? no
|
A 2-character code that indicates how often, or on what schedule, the
fund is billed.
Examples: 20 (Automatic [no invoice required]; Q1); 25 (Automatic [no
invoice required]; by schedule)
BRIM source: ARRECR.stkcode (fed to BRIM from BEN Financials via the
SBTFUND.txt extract - fnd_flex_values_vl.attribute26)
|
|
BILLING_RATE
Indexed - no
Format - number (13,2)
May be null? yes
|
The amount of an automatic payment installment
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARRECR.extprice
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIMAUTOPAY_PROFILES 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
|
|
CALENDAR_YEAR_SNAPSHOT
Indexed - yes
Format - char (4)
May be null? no
|
The 4-character number that identifies the calendar year of the accounting
period when the BRIMAUTOPAY_PROFILES record was snapshot This is based
on the ACCT_PER_SNAPSHOT.
The calendar year begins January 1 and ends December 31.
Example: 2002 (the CALENDAR_YEAR for ACCT_PER_SNAPSHOT SEP-02).
|
|
COMMENT_ID
Indexed - yes
Format - char (6)
May be null? yes
|
A 6-character code that identifies a comment associated with the automatic
payment profile for the FUND_CODE.
Note: a reference table for these comment codes is not yet available
in the Data Warehouse
BRIM source: ARRECR.commid
|
|
CREATION_DATE
Indexed - no
Format - date(7)
May be null? yes
|
The date when the automatic payment profile record was created 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: 1/13/2002
BRIM source: ARRECR.entered
|
|
FISCAL_MON_SEQ_SNAPSHOT
Indexed - yes
Format - char (2)
May be null? no
|
The month (accounting period) of the fiscal year of the accounting period
when the BRIMAUTOPAY_PROFILES record was snapshot This field is used for
sorting.
Note: because the FISCAL_MON_SEQ_SNAPSHOT is ultimately based on the
BRIM_EXTRACT_DATE, there is no snapshot 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_YEAR_SNAPSHOT
Indexed - yes
Format - char (4)
May be null? no
|
The financial year of the accounting period when the BRIMAUTOPAY_PROFILES
record was snapshot. Penn's fiscal year begins July 1 of one calendar
year and ends June 30 of the next calendar year.
Example: 2003 (the fiscal year beginning July 1, 2002, and ending June
30, 2003, in which BRIM_EXTRACT_DATE 9/19/2002 falls.)
|
|
FUND_CODE
Indexed - yes
Format - char (6)
May be null? no
|
The 6-character code that identifies the sponsored project fund that
is on an automatic payment schedule. 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: ARRECR.item (fed to BRIM from BEN Financials via the SBTFUND.txt
extract-fnd_flex_values_vl.flex_value)
|
|
FUND_INVOICE_NUMBER
Indexed - yes
Format - char (20)
May be null? yes
|
A value in the format FFFFFF-0001, where FFFFFF is the FUND_CODE, and
0001 is the sequence number (including leading zeroes) to be used for
the first invoice created for the fund.
BRIM source: ARRECR.ponum (based on data fed to BRIM from BEN Financials
via the SBTFUND.txt extract-fnd_flex_values_vl.flex_value)
|
|
FUND_RESP_ORG
Indexed - yes
Format - char (4)
May be null? no
|
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 BRIMAUTOPAY_PROFILES record.
Example: 0103 (Biology)
Values:
Refer to the ORG_CODES table for values.
BRIM source: ARINVT.lead
|
|
LAST_BILL_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when a receivable record (invoice) was last created for an automatic
payment installment for the FUND_CODE.
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: 1/15/2002
BRIM source: ARRECR.lastbill
|
|
MAX_PAYMENT_COUNT
Indexed - no
Format - number (3)
May be null? yes
|
The total number of automatic payment installments expected for the life
of the FUND_CODE.
BRIM source: ARRECR.max
|
|
MONTH_SNAPSHOT
Indexed - yes
Format - char (2)
May be null? no
|
The 2-character number that identifies the calendar month (or accounting
period) when the BRIMAUTOPAY_PROFILES record was snapshot This is based
on the ACCT_PER_SNAPSHOT.
Note: because the MONTH_SNAPSHOT is ultimately based on the BRIM_EXTRACT_DATE,
there is no snapshot for the 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
|
|
NEXT_BILL_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The next date when a receivable record (invoice) ought to be created
for an automatic payment installment for the FUND_CODE. (BRIM determines
this date based on the auto pay frequency, the auto pay period, the last
bill date, the maximum payment count, and the used payment count.)
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: 2/15/2002
BRIM source: ARRECR.nextbill
|
|
PBIL
Indexed - no
Format - number (13,2)
May be null? yes
|
The total authorized billing amount for the FUND_CODE.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARRECR.price (based on data fed to BRIM from BEN Financials
via the SBTASSET.txt extract -gl.gl_je_headers.entered_dr and gl.gl_je_headers.entered_cr)
|
|
PROJECT_TITLE
Indexed - no
Format - char (200)
May be null? yes
|
The title of the sponsored project funded via the FUND_CODE. See also
PROJECT_TITLE in the BRIM_FUNDS table.
Note: The value is the title as typed into BRIM by ORS staff. For example,
some values are in upper case, while others are in mixed case.
Note: due to a system error, records created prior to June 15, 2002 may
have a PROJECT_TITLE whose value is actually the SPONSOR_REF_ID.
Example: 'Analysis of Ligand Binding ErbB Receptor Tyrosine Kinases'
BRIM source: ARRECR.descrip (taken in BRIM from ARINVT.descrip1)
|
|
QUARTER_SEQ_SNAPSHOT
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year when the BRIMAUTOPAY_PROFILES record was
snapshot This is based on the ACCT_PER_SNAPSHOT.
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
SORT_PERIOD_SNAPSHOT
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period when the BRIMAUTOPAY_PROFILES record was snapshot
This is based on the BRIM_EXTRACT_DATE, and is stated YYYYMM format. YYYY
is the calendar year, and MM is the calendar month.
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_SNAPSHOT is based on the BRIM_EXTRACT_DATE,
there are no records for month 13.
Example: 200209 (the SORT_PERIOD_SNAPSHOT for BRIM_EXTRACT_DATE 9/19/2002,
which falls in SEP-02)
|
|
SPONSOR_CODE
Indexed - yes
Format - char (4)
May be null? no
|
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: ARRECR.custno (fed to BRIM from BEN Financials via the SBTFUND.txt
extract-fnd_flex_values_vl.attribute4)
|
|
SPONSOR_REF_ID
Indexed - yes
Format - varchar2 (35)
May be null? yes
|
The identification number that is assigned to the award by the sponsoring
agency. (The award for the sponsored project may be distributed among
one or more FUND_CODEs.)
Example: DAMD-17-94-J-1433 (an award identification number assigned by
the Department of the Army)
Note: due to a system error, records created prior to June 15, 2002 may
have a null value for SPONSOR_REF_ID.
BRIM source: ARRECR.shipvia (fed to BRIM from BEN Financials via the
SBTFUND.txt
extract-fnd_flex_values_vl.description)
|
| USED_PAYMENT_COUNT
Indexed - no
Format - number (3)
May be null? yes
|
The total number of automatic payment installments for the FUND_CODE,
for which a receivable record (invoice) has been created. (One invoice
is created for each installment.)
BRIM source: ARRECR.used
|
