| Data element |
Definition |
ACCOUNTANT_NAME
Indexed - yes
Format - char (20)
May be null - no |
The name of the accountant in the Office of Research Services who is
responsible for monitoring the FUND_CODE, as of the BRIM_EXTRACT_DATE.
Note: the value is stored in upper case.
Example: 'ALIYU MOHAMMED'
BRIM source: ARINVT.vpartno (fed to BRIM from BEN Financials via the
SBTFUND.txt extract - fnd_flex_values_vl.description)
|
|
ACCT_DESK_NUMBER
Indexed - yes
Format - char (4)
May be null? yes
|
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: ARINVT.seq (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_vl.flex_value)
|
|
ACCT_END_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The last date when the FUND_CODE may be used to track financial activity
for the sponsored project.
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/30/2002
BRIM source: ARINVT.lastordr (fed to BRIM from BEN Financials via the
SBTFUND.txt
extract-fnd_flex_values_vl.attribute7)
|
|
ACCT_PERIOD_LAST_INVOICE_DATED
Indexed - no
Format - char (6)
May be null? yes
|
The accounting period in which the FUND_LAST_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 FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
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_PERIOD_LAST_INVOICE_DATED is based on the FUND_LAST_INVOICE_DATE,
there are no records for the ADJ period.
Example: AUG-02 (August, 2002, which occurs in fiscal year 2003).
|
|
ACCT_PER_SNAPSHOT
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period when the BRIM_FUNDS 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, as of the BRIM_EXTRACT_DATE.
Example: 215/573-6716
BRIM source: ARINVT.acctphone
|
|
ACCT_START_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The first date when the FUND_CODE may be used to track financial activity
for the sponsored project.
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: 10/1/2001
BRIM source: ARINVT.projstart (fed to BRIM from BEN Financials via the
SBTFUND.txt extract-fnd_flex_values_vl.attribute5)
|
|
BILL_TO_CODE
Indexed - yes
Format - char (6)
May be null? yes
|
A 6-character code that identifies the default mailing address for invoices
for the FUND_CODE.
Note: the reference table for the fund billing addresses are not yet
available in the Data Warehouse
BRIM source: ARINVT.cshipno
|
|
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, as of the BRIM_EXTRACT_DATE.
Examples: 01 (Standard Invoice); 07 (Automatic Payments)
Values: Refer to the FUND_BILLING_FORMAT_CODES table
for values.
BRIM source: ARINVT.taxcode (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? yes
|
A 2-character code that indicates how often, or on what schedule, the
fund is billed, as of the BRIM_EXTRACT_DATE.
Note: the value may be null for receipts, and for records converted from
the legacy billing & receivables system to BRIM (INTERNAL_REFERENCE_NO
is 1117 or lower).
Examples: 20 (Automatic [no invoice required]; Q1); 25 (Automatic [no
invoice required]; by schedule)
BRIM source: ARINVT.stkcode (fed to BRIM from BEN Financials via the
SBTFUND.txt extract -fnd_flex_values_vl.attribute26)
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIM_FUNDS 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_FYTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of the invoice variances stored in BRIM
for all the expense-based invoices for the fund. That is, the sum of all
the invoice variances stored in BRIM for all the expense-based invoices
for the FUND_CODE that are dated from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT.
See also CALC_FYTD_INVOICE_VARIANCE.
The invoice variance is the difference between the actual amount and
the invoiced amount for a line item of an invoice.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the INVOICE_VARIANCE in the BRIMFUND_SB_EXP table,
where:
- the VOID_INVOICE_FLAG is 'N'
- the FISCAL_YR_ INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate BRIM_FYTD_INVOICE_VARIANCE for a closed
accounting period may find that the re-calculated value does not match
what is in BRIM_FUNDS. The likely reason for the discrepancy is that an
invoice has been voided since the end of the closed accounting period.
Note: BRIM_FYTD_INVOICE_VARIANCE is calculated based on BRIMFUND_SB_EXP
rather than BRIM_MASTER because, when an invoice is voided, the total
variance amount is not backed out in BRIM_MASTER.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
BRIM_PERIOD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The sum of the invoice variances stored in BRIM for all the expense-based
invoices for the FUND_CODE that were dated during the ACCT_PERIOD_SNAPSHOT.
See also CALC_PERIOD_INVOICE_VARIANCE.
The invoice variance is the difference between the actual amount and
the invoiced amount for a line item of an invoice.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the INVOICE_VARIANCE in the BRIMFUND_SB_EXP table,
where:
- the VOID_INVOICE_FLAG is 'N'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate BRIM_PERIOD_INVOICE_VARIANCE for a closed
accounting period may find that the re-calculated value does not match
what is in BRIM_FUNDS. The likely reason for the discrepancy is that an
invoice has been voided since the end of the closed accounting period.
Note: BRIM_PERIOD_INVOICE_VARIANCE is calculated based on BRIMFUND_SB_EXP
rather than BRIM_MASTER because, when an invoice is voided, the total
variance amount is not backed out in BRIM_MASTER.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
BRIM_PJTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the invoice variances stored in BRIM for
all the expense-based invoices for the fund. That is, the sum of all the
invoice variances stored in BRIM for all the expense-based invoices for
the FUND_CODE that are dated during or before the ACCT_PERIOD_SNAPSHOT.
See also CALC_PJTD_INVOICE_VARIANCE.
The invoice variance is the difference between the actual amount and
the invoiced amount for a line item of an invoice.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the INVOICE_VARIANCE in the BRIMFUND_SB_EXP table,
where:
- the VOID_INVOICE_FLAG is 'N'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate BRIM_PJTD_INVOICE_VARIANCE for a closed
accounting period may find that the re-calculated value does not match
what is in BRIM_FUNDS. The likely reason for the discrepancy is that an
invoice has been voided since the end of the closed accounting period.
Note: BRIM_ PJTD_INVOICE_VARIANCE is calculated based on BRIMFUND_SB_EXP
rather than BRIM_MASTER because, when an invoice is voided, the total
variance amount is not backed out in BRIM_MASTER.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
CALC_FYTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The difference between the total actual amount and the total invoiced
for all invoices for the FUND_CODE that were dated from the beginning
of the FISCAL_YR_SNAPSHOT through the ACCT_PERIOD_SNAPSHOT. That is,
CALC_FYTD_INVOICE_VARIANCE = FYTD_ACTUAL_AMT - FYTD_TOTAL_INVOICED.
See also BRIM_FYTD_INVOICE_VARIANCE.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
CALC_PERIOD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The difference between the total actual amount and the total invoiced
for all invoices for the FUND_CODE that were dated during the ACCT_PERIOD_SNAPSHOT.
That is,
CALC_PERIOD_INVOICE_VARIANCE = PERIOD_ACTUAL_AMT -PERIOD_TOTAL_INVOICED.
See also BRIM_PERIOD_INVOICE_VARIANCE.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
CALC_PJTD_INVOICE_VARIANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
The difference between the total actual amount and the total invoiced
for all invoices for the FUND_CODE that were dated during or before the
ACCT_PERIOD_SNAPSHOT. That is,
CALC_PJTD_INVOICE_VARIANCE = PJTD_ACTUAL_AMT -PJTD_TOTAL_INVOICED.
See also BRIM_PJTD_INVOICE_VARIANCE.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Note: The value of CALC_PJTD_INVOICE_VARIANCE may differ from the value
of BRIM_PJTD_INVOICE_VARIANCE. Legacy (pre-BRIM) invoices have an invoice
amount, but have 0 for both the actual amount and of the variance. Legacy
invoices have an internal reference number of 1117 or lower.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
CALENDAR_YR_LAST_INVOICE_DATED
Indexed - no
Format - char (4)
May be null? yes
|
The 4-character number that identifies the calendar year of the accounting
period in which the FUND_LAST_INVOICE_DATE falls. The calendar year begins
January 1 and ends December 31.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
Example: 2002 (the calendar year for FUND_LAST_INVOICE_DATE 8/2/2002,
which falls in AUG-02).
|
|
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 BRIM_FUNDS 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 fund.
Note: a reference table for these comment codes is not yet available
in the Data Warehouse
Example: PAST1
BRIM source: ARINVT.commid
|
|
FISCAL_MON_SEQ_LAST_INV_DATED
Indexed - no
Format - char (2)
May be null? yes
|
The month (accounting period) of the fiscal year in which the FUND_LAST_INVOICE_DATE
falls. This field is used for sorting.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
Note: because the FISCAL_MON_SEQ_LAST_INV_DATED is ultimately based on
the FUND_LAST_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_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 BRIM_FUNDS 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_YR_LAST_INVOICE_DATED
Indexed - no
Format - char (4)
May be null? yes
|
The financial year in which the FUND_LAST_INVOICE_DATE falls. Penn's
fiscal year begins July 1 of one calendar year and ends June 30 of the
next calendar year.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
Example: 2003 (fiscal year beginning July 1, 2002, and ending June 30,
2003, in which FUND_LAST_INVOICE_DATE 8/2/2002 falls)
|
|
FISCAL_YEAR_SNAPSHOT
Indexed - yes
Format - char (4)
May be null? no
|
The financial year of the accounting period when the BRIM_FUNDS 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 tracked
in BRIM. (BRIM tracks funds that have automatic payment schedules, and
those that receive cash only after the sponsor is billed for project-related
expenses. BRIM does not track funds paid via a letter of credit.) 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: ARINVT. Item (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_vl.flex_value)
|
|
FUND_LAST_INVOICE_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date of the last invoice (expense-based or automatic payment) that
was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE. (This is the
date on the invoice, which is not necessarily the date the invoice was
created.)
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: 8/2/2002
BRIM source: ARRECR.lastbill
|
|
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 BRIM_FUNDS record.
Example: 0103 (Biology)
Values: Refer to the ORG_CODES table for values.
BRIM source: ARINVT.lead (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_vl.attribute1)
|
|
FYTD_ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of the actual dollars for expense-based
invoices for the fund. That is, the total of the actual amounts for all
expense-based invoices for the FUND_CODE that are dated from the beginning
of the FISCAL_YR_SNAPSHOT through the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMT in the BRIMFUND_SB_EXP table, where:
- the VOID_INVOICE_FLAG is 'N'
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate FYTD_ACTUAL_AMT for a closed accounting
period may find that the re-calculated value does not match what is in
BRIM_FUNDS. The likely reason for the discrepancy is that an invoice has
been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_APPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of the cash receipts that were applied
to invoices for the FUND_CODE. That is, the total of the cash receipts
applied to invoices for the FUND_CODE from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the FISCAL_YR_APPLIED is the same as the FISCAL_YR_SNAPSHOT in BRIM_FUNDS
- the SORT_PERIOD_APPLIED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_AUTOPAY_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of the automatic payment invoices for the
fund. That is, the sum of the invoice totals for all automatic payment
invoices for the FUND_CODE that are dated from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is '07' or '08'
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
FYTD_EXPENSE_BASED_INVOICED
Indexed - no
Format - number (13,2)
May be null - yes |
The fiscal year-to-date total of the expense-based invoices for the fund.
That is, the sum of the invoice totals for all expense-based invoices
for the FUND_CODE that are dated from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is less than or equal to '06'
- the FISCAL_YR_ INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_RECEIVABLES
Indexed - no
Format - number (13,2)
May be null? yes
|
For invoices for the fund dated from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT, the outstanding receivables as of the
end of the ACCT_PERIOD_SNAPSHOT.
The value of FYTD_RECEIVABLES should equal FYTD_TOTAL_INVOICED + FYTD_TOTAL_RECEIPTS.
Calculated based on the BALANCE in the BRIM_MASTER table, where:
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_TOTAL_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of all invoices for the fund. That is,
the sum of the invoice totals for all invoices for the FUND_CODE that
are dated from the beginning of the FISCAL_YR_SNAPSHOT through the ACCT_PERIOD_SNAPSHOT.
The value of FYTD_TOTAL_INVOICED should equal FYTD_AUTOPAY_INVOICED +
FYTD_EXPENSE_BASED_INVOICED.
Calculated based on the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
FYTD_TOTAL_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE from the beginning
of the FISCAL_YR_SNAPSHOT through the ACCT_PERIOD_SNAPSHOT. This includes
amounts that were applied to invoices during the FISCAL_YR_SNAPSHOT by
the end of the ACCT_PERIOD_SNAPSHOT, and amounts that were not.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999
|
|
FYTD_UNAPPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE during the FISCAL_YR_SNAPSHOT
by the end of the ACCT_PERIOD_SNAPSHOT, that was not applied to invoices
during the FISCAL_YR_SNAPSHOT by the end of the ACCT_PERIOD_SNAPSHOT.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is '_RECEIPT'
- the FISCAL_YR_INVOICE_DATED is the same as the FISCAL_YR_SNAPSHOT
in BRIM_FUNDS
- the FISCAL_YR_APPLIED is the same as the FISCAL_YR_SNAPSHOT in BRIM_FUNDS
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_APPLIED less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: completely applied receipts will net to 0.
Values:
-99,999,999,999.99 to 99,999,999,999
|
|
FYTD_UNBILLED_ACTUAL_EXP
Indexed - no
Format - number (13,2)
May be null? yes
|
The fiscal year-to-date total of the actual amounts for the fund that
have yet to be included in an invoice. That is, the total of all actual
amounts for the FUND_CODE that are dated from the beginning of the FISCAL_YR_SNAPSHOT
through the ACCT_PERIOD_SNAPSHOT,
and that have invoice dates (if any) that fall after the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMOUNT in the BRIMFUND_OBJ_EXP table,
where:
- the SORT_PERIOD_INVOICE DATED is greater than the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS, OR the SORT_PERIOD_INVOICE DATED is null
- the FISCAL_YR_POSTED is the same as the FISCAL_YR_SNAPSHOT in BRIM_FUNDS
- the SORT_PERIOD_POSTED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
BRIMFUND_OBJ_EXP includes actual amounts for expense, revenue, and asset
Object codes that are relevant to invoices.
Note: Users who re-calculate FYTD_UNBILLED_ACTUAL_EXP for a closed accounting
period may find that the re-calculated value does not match what is in
BRIM_FUNDS. The likely reason for the discrepancy is that an invoice has
been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
LAST_PONUM
Indexed - no
Format - number (4)
May be null? yes
|
The sequence number of the invoice (expense-based or automatic payment)
last created for the FUND_CODE, as of the BRIM_EXTRACT_DATE. The value
will be 0 if the fund has not yet been invoiced.
Note: though leading zeros are used in the sequence number portion of
the FUND_INVOICE_NUMBER in the BRIMAUTOPAY_PROFILES, BRIM_MASTER, BRIMFUND_SB_EXP,
and BRIMCASH_RECEIPTS tables, LAST_PONUM does not include leading zeros.
Values:
1 - 9999
BRIM source: ARINVT.lastponum
|
|
MON_LAST_INVOICE_DATED
Indexed - no
Format - char (2)
May be null? yes
|
The 2-character number that identifies the calendar month (accounting
period) in which the FUND_LAST_INVOICE_DATE falls.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
Note: because the MON_LAST_INVOICE_DATED is ultimately based on the FUND_LAST_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
|
|
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 BRIM_FUNDS 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
|
|
PBIL
Indexed - no
Format - number (13,2)
May be null? yes
|
The total authorized billing amount for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARINVT.price (total of 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)
|
|
PERIOD_ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The total of the actual amounts for expense-based invoices for the FUND_CODE
that were dated during the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMT in the BRIMFUND_SB_EXP table, where:
- the VOID_INVOICE_FLAG is 'N'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate PERIOD_ACTUAL_AMT for a closed accounting
period may find that the re-calculated value does not match what is in
BRIM_FUNDS. The likely reason for the discrepancy is that an invoice has
been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_APPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total of the cash receipts that were applied during the ACCT_PERIOD_SNAPSHOT
to invoices for the FUND_CODE.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the SORT_PERIOD_APPLIED is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_AUTOPAY_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The sum of the invoice totals for automatic payment invoices for the
FUND_CODE that were dated during the ACCT_PERIOD_SNAPSHOT.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is '07' or '08'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_EXPENSE_BASED_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The sum of the invoice totals for expense-based invoices for the FUND_CODE
that were dated during the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is less than or equal to '06'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_TOTAL_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The sum of the invoice totals for all invoices for the FUND_CODE that
were dated during the ACCT_PERIOD_SNAPSHOT.
The value of PERIOD_TOTAL_INVOICED should equal PERIOD_AUTOPAY_INVOICED
+ PERIOD_EXPENSE_BASED_INVOICED.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_TOTAL_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE during the ACCT_PERIOD_SNAPSHOT.
This includes amounts that were applied to invoices during the ACCT_PERIOD_SNAPSHOT,
and amounts that were not.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_UNAPPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE during the ACCT_PERIOD_SNAPSHOT,
that was not applied to invoices during the ACCT_PERIOD_SNAPSHOT.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is '_RECEIPT'
- the SORT_PERIOD_INVOICE_DATED is the same as the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_APPLIED is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: completely applied receipts will net to 0.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PERIOD_UNBILLED_ACTUAL_EXP
Indexed - no
Format - number (13,2)
May be null? yes
|
The total of all the actual amounts for the FUND_CODE that are dated
during the ACCT_PERIOD_SNAPSHOT and that have yet to be included in an
invoice. That is, their invoice dates (if any) fall after the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMOUNT in the BRIMFUND_OBJ_EXP table,
where:
- the SORT_PERIOD_INVOICE DATED is greater than the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS, OR the SORT_PERIOD_INVOICE DATED is null
- the SORT_PERIOD_POSTED is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
BRIMFUND_OBJ_EXP includes actual amounts for expense, revenue, and asset
Object codes that are relevant to invoices.
Note: Users who re-calculate PERIOD_UNBILLED_ACTUAL_EXP for a closed
accounting period may find that the re-calculated value does not match
what is in BRIM_FUNDS. The likely reason for the discrepancy is that an
invoice has been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the actual amounts for expense-based invoices
for the FUND_CODE that were dated during or before the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMT in the BRIMFUND_SB_EXP table, where:
- the VOID_INVOICE_FLAG is 'N'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: Users who re-calculate PJTD_ACTUAL_AMT for a closed accounting
period may find that the re-calculated value does not match what is in
BRIM_FUNDS. The likely reason for the discrepancy is that an invoice has
been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_APPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the cash receipts that were applied to invoices
for the FUND_CODE. That is, the total of the cash receipts applied to
invoices for the FUND_CODE during or before the ACCT_PERIOD_SNAPSHOT.
Calculated based on the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the SORT_PERIOD_APPLIED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_AUTOPAY_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the automatic payment invoices for the fund.
That is, the sum of the invoice totals for automatic payment invoices
for the FUND_CODE that are dated during or before the ACCT_PERIOD_SNAPSHOT.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is '07' or '08'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_EXPENSE_BASED_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the expense-based invoices for the fund.
That is, the sum of the invoice totals for all expense-based invoices
for the FUND_CODE that are dated during or before the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the BILLING_FORMAT_CODE is less than or equal to'06'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_RECEIVABLES
Indexed - no
Format - number (13,2)
May be null? yes
|
Outstanding receivables for the fund as of the end of the ACCT_PERIOD_SNAPSHOT.
The value of PJTD_RECEIVABLES should equal PJTD_TOTAL_INVOICED + PJTD_TOTAL_RECEIPTS.
Calculated based on the BALANCE in the BRIM_MASTER table, where:
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_TOTAL_INVOICED
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of all invoices for the fund. That is, the
sum of the invoice totals for all invoices for the FUND_CODE that are
dated during or before the ACCT_PERIOD_SNAPSHOT.
The value of PJTD_TOTAL_INVOICED should equal PJTD_AUTOPAY_INVOICED +
PJTD_EXPENSE_BASED_INVOICED.
Calculated based on the INVOICE_TOTAL in the BRIM_MASTER table, where:
- the INTERNAL_REF_NUMBER is not '_RECEIPT'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_SNAPSHOT is the same as the SORT_PERIOD_SNAPSHOT in
BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PJTD_TOTAL_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE during or before
the ACCT_PERIOD_SNAPSHOT. This includes amounts that were applied to invoices
by the end of the ACCT_PERIOD_SNAPSHOT, and amounts that were not.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Values:
-99,999,999,999.99 to 99,999,999,999
|
|
PJTD_UNAPPLIED_RECEIPTS
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of cash received for the FUND_CODE during or before
the ACCT_PERIOD_SNAPSHOT, that was not applied to invoices by the end
of the ACCT_PERIOD_SNAPSHOT.
Calculated based on the PAID_AMT in the BRIMCASH_RECEIPTS table, where:
- the INTERNAL_REF_NUMBER is '_RECEIPT'
- the SORT_PERIOD_INVOICE_DATED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the SORT_PERIOD_APPLIED less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
Note: completely applied receipts will net to 0.
Values:
-99,999,999,999.99 to 99,999,999,999
|
|
PJTD_UNBILLED_ACTUAL_EXP
Indexed - no
Format - number (13,2)
May be null? yes
|
The project-to-date total of the actual amounts for the fund that have
yet to be included in an invoice. That is, the total of all actual amounts
for the FUND_CODE that are dated during or before the ACCT_PERIOD_SNAPSHOT
and that have invoice dates (if any) that fall after the ACCT_PERIOD_SNAPSHOT.
Note: though the value should be 0 for automatic payment funds, in some
cases, it may not be 0.
Calculated based on the ACTUAL_AMOUNT in the BRIMFUND_OBJ_EXP table,
where:
- the SORT_PERIOD_INVOICE DATED is greater than the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS, OR the SORT_PERIOD_INVOICE DATED is null
- the SORT_PERIOD_POSTED is less than or equal to the SORT_PERIOD_SNAPSHOT
in BRIM_FUNDS
- the FUND_CODE is the same as the FUND_CODE in BRIM_FUNDS
BRIMFUND_OBJ_EXP includes actual amounts for expense, revenue, and asset
Object codes that are relevant to invoices.
Note: Users who re-calculate PJTD_UNBILLED_ACTUAL_EXP for a closed accounting
period may find that the re-calculated value does not match what is in
BRIM_FUNDS. The likely reason for the discrepancy is that an invoice has
been voided since the end of the closed accounting period.
Values:
-99,999,999,999.99 to 99,999,999,999.99
|
|
PRINCIPAL_INVESTIGATOR_NAME
Indexed - no
Format - char (40)
May be null? yes
|
The name of the investigator who is responsible for the FUND_CODE. Note:
A period may or may not be included after a middle initial.
Example: LEE,WILLIAM F
BRIM source: ARINVT.unitms (fed to BRIM from BEN Financials via the SBTFUND.txt
extract-fnd_flex_values_vl.attribute3)
|
|
PROJECT_TITLE
Indexed - no
Format - char (200)
May be null? yes
|
The title of the sponsored project funded via the FUND_CODE.
Note: The value is the title as typed into BRIM by ORS staff. Most values are in mixed case, but some values are in upper case. A double quote mark (‘”’) may or may not be the first character, and it may or may not be the last character.
Note: PROJECT_TITLE is populated if the value for ACCT_PER_SNAPSHOT is ‘APR-06’ or later. Records for earlier snapshots have a null value for PROJECT_TITLE.
Examples: ’”SBDC”’, ‘”4Sight: Blindness Prevention Program’, ‘ADAP Isoforms in T Lymphocytes”’, ‘AAV Gene Therapy for the CNS in MUCO’
BRIM source: ARINVT.descrip1
|
|
QUARTER_SEQ_LAST_INVOICE_DATED
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year in which the FUND_LAST_INVOICE_DATE falls.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
QUARTER_SEQ_SNAPSHOT
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year when the BRIM_FUNDS 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)
|
|
SCHOOL
Indexed - yes
Format - char (2)
May be null? yes
|
A 2-character code used to identify the school responsible for the FUND_CODE.
The code set is from the University's General Ledger, and has been in
use since July 1, 1996.
Example: 40 (School of Medicine)
Values: Refer to the CNAC_CODES Table for values.
The code for a school or center is the same as the
first 2 characters of the CNAC.
BRIM source: ARINVT.class (fed to BRIM from BEN Financials via the SBTFUND.txt
extract-bpadmin.organiztion.ledger_alias_code)
|
|
SORT_PERIOD_LAST_INVOICE_DATED
Indexed - no
Format - char (6)
May be null? yes
|
The accounting period in which the FUND_LAST_INVOICE_DATE falls. The
value is stated YYYYMM format. YYYY is the calendar year, and MM is the
calendar month.
The FUND_LAST_INVOICE_DATE is the date of the last invoice (expense-based
or automatic payment) that was created for the FUND_CODE, as of the BRIM_EXTRACT_DATE.
(This is the date on the invoice, which is not necessarily the date the
invoice was created.)
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_LAST_INVOICE_DATED is ultimately based
on the FUND_LAST_INVOICE_DATE, there are no records for month 13.
Example: 200208 (the SORT_PERIOD_LAST_INVOICE_DATED for FUND_LAST_INVOICE_DATE
8/2/2002, which falls in AUG-02)
|
|
SORT_PERIOD_SNAPSHOT
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period when the BRIM_FUNDS 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? yes
|
The 4-character code that identifies the external organization that sponsors
the fund, as of the BRIM_EXTRACT_DATE. (In rare cases, the sponsor of
a fund changes during the life of the fund.)
Examples: 1010 Department of the Army); 1430 (National Science Foundation).
Values: Refer to the FUND_SPONSORS table for values.
BRIM source: ARINVT.supplier (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)
BRIM source: ARINVT.code (fed to BRIM from BEN Financials via the SBTFUND.txt
extract - fnd_flex_values_vl.description)
|
