| Data element |
Definition |
ACCOUNT_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: 8/31/2002
BRIM source: ARTRAN.seqdte (current records) or ARYTRN.seqdte (history
records)
|
|
ACCOUNT_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: 9/01/2001
BRIM source: ARTRAN.seqno (current records) or ARYTRN.seqno (history
records)
|
|
ACCOUNTANT_NAME
Indexed - yes
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: ARTRAN.refer (current records) or ARYTRN.refer (history
records)
|
|
ACCT_DESK_NUMBER
Indexed - yes
Format - char (20)
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: ARMAST.caseno (current records) or ARYMST.caseno (history
records)
|
|
ACCT_PER_APPLIED
Indexed - yes
Format - char (6)
May be null? yes
|
The accounting period in which the DATE_APPLIED falls. The value is stated
in MON-YY format. MON is the calendar month (stored in upper case), and
YY is the calendar year.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
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_APPLIED is based on the DATE_ APPLIED, there
are no records for the ADJ period.
Example: SEP-02 (September, 2002, which occurs in fiscal year 2003).
|
|
ACCT_PER_INVOICE_DATED
Indexed - yes
Format - char (6)
May be null? yes
|
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 cash receipt, credit memo, or invoice.
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: 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_MASTER 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: ARMAST.fob (current records) or ARYMST.fob (history records)
|
|
AGE
Indexed - yes
Format - number (4)
May be null? yes
|
The age of the invoice, cash receipt, or credit memo, in days. AGE is
used in the aged receivables report.
For voided invoices, for invoices paid in full, and for cash receipts
and credit memos applied in full, AGE is 0.
For open invoices, cash receipts, and credit memos (that is, those that
are not void and that have a non-0 BALANCE), AGE is determined by subtracting
the INVOICE_DATE from the BRIM_EXTRACT_DATE.
Values:
0 to 9,999
|
|
AGE_RANGE
Indexed - yes
Format - char (13)
May be null? yes
|
A description of the range within which the AGE falls.
For open invoices, cash receipts, and credit memos, AGE is determined
by subtracting the INVOICE_DATE from the BRIM_EXTRACT_DATE. For other
records, AGE is 0.
Note: The value for each of the lowest three ranges begins with one leading
blank, so the value will appear in the correct order when sorted.
Values:
0-60 days
61-90 days
91-120 days
121-180 days
181-360 days
over 360 days
|
|
BALANCE
Indexed - no
Format - number (13,2)
May be null? yes
|
For an invoice or credit memo, the BALANCE is the amount of the outstanding
receivable (the INVOICE_TOTAL minus the PAID_AMOUNT).
For cash receipts, the BALANCE is the amount available to be applied
to one or more invoices (or, rarely, to a cash receipt).
Usually, for cash receipts and credit memos, the BALANCE has a zero or
negative value; for invoices, the INVOICE_TOTAL has a zero or positive
value.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARMAST.balance (current records) or ARYMST.balance (history
records) (for most unapplied receipts, fed to BRIM from BEN Financials
via the SBTASSET.txt extract -gl.gl_je_lines.entered_dr and gl.gl_je_lines.entered_cr)
|
|
BATCH
Indexed - no
Format - char (3)
May be null? yes
|
A 3-character code that indicates the method used to enter the record
in BRIM.
Values:
001 entered online
099 converted from the legacy billing & receivables
system to BRIM
100 entered in batch (from an extract of General
Ledger data)
BRIM source: ARMAST.batch (current records) or ARYMST. batch (history
records)
|
|
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: 01 (Standard Invoice); 07 (Automatic Payments)
Values: Refer to the FUND_BILLING_FORMAT_CODES table
for values.
BRIM source: ARMAST.salesmn (current records) or ARYMST.salesmn (history
records) (for most receipts, based on data 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.
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: for receipts, ARMAST.terr (current records) or ARYMST.terr
(history records). For invoices & credit memos, ARTRAN.stkcode (current
records) or ARYTRN.stkcode (history records).
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIM_MASTER 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 tables (ARYMST, as well as
ARYTRN for invoices & credit memos). Any invoices, credit memos, and
cash receipts that have been voided, paid in full, or fully applied, are
then deleted from the BRIM current tables (ARMAST, as well as ARTRAN for
invoices & credit memos). Any invoices, credit memos, and cash receipts
that have NOT been voided, paid in full, or fully applied remain in the
current tables, where they are available for further updating.
The BRIM_MASTER table contains data from the BRIM history tables, updated
and supplemented by the data from the BRIM current tables.
Values:
C the invoice, credit memo, or cash receipt record
exists only in the BRIM current tables
H a record for the invoice, credit memo, or cash
receipt exists in the BRIM history tables; a more
recent version of the record may also exist in the
BRIM current tables
BRIM source: ARMAST.current (current records) or ARYMST.current (history
records)
|
|
BRIM_ORIGINAL_TRANS_ID
Indexed - yes
Format - char (9)
May be null? no
|
A 9-character code that identifies the invoice, cash receipt, or credit
memo. There is usually, but not always, one record per BRIM_ORIGINAL_TRANS_ID
and ACCT_PER_SNAPSHOT. There are two such records for a voided invoice.
A record for an invoice has a BRIM_ORIGINAL_TRANS_ID that is 'I' concatenated
with the INTERNAL_REFERENCE_NO. A record for a cash receipt has a BRIM_ORIGINAL_TRANS_ID
that begins with 'R' followed by a numeric code. A record for a credit
memo has a BRIM_ORIGINAL_TRANS_ID that is 'C' concatenated with the INTERNAL_REFERENCE_NO.
Note: all 9 characters are used; there are blanks between the initial
letter and the numerals in the BRIM_ORIGINAL_TRANS_ID.
Note: both records pertaining to a voided invoice (the original invoice
and the record negating its INVOICE TOTAL) have the same value for
BRIM_ORIGINAL_TRANS_ID.
See also FUND_INVOICE_NUMBER and INTERNAL_REF_NUMBER.
Examples:
I 13521 (an invoice)
R 1034 (a cash receipt)
C 5529 (a credit memo)
BRIM source: ARMAST.oti (current records) or ARYMST.oti (history records)
|
|
CALENDAR_YR_APPLIED
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 DATE_APPLIED falls. The calendar year begins January
1 and ends December 31.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
Example: 2002 (the calendar year for DATE_APPLIED 9/4/2002, which falls
in SEP-02).
|
|
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 cash receipt, credit memo, or invoice.
Example: 2002 (the calendar year for 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_MASTER 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 invoice.
The value will be null for receipt records.
Note: a reference table for these comment codes is not yet available
in the Data Warehouse
Example: CERT
BRIM source: ARMAST.commid (current records) or ARYMST.commid (history
records)
|
|
CUSTOM_INVOICE_ADDR_FLAG
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code that identifies whether a customized mailing address
was used for the invoice. The value will be null for receipt records.
Note: reference tables for the invoice addresses and fund billing addresses
are not yet available in the Data Warehouse
Values:
Y a customized billing address was used for the
Invoice
N the billing address for the FUND_CODE was used
for the invoice
null (not applicable)
BRIM source: ARMAST.tosw (current records) or ARYMST.tosw (history records)
|
|
DATE_APPLIED
Indexed - no
Format - date (7)
May be null? yes
|
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
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/4/2002 (September 4, 2002)
BRIM source: ARMAST.dtepaid (current records) or ARYMST.dtepaid (history
records) (for most unapplied receipts, fed to BRIM from BEN Financials
via the SBTASSET.txt extract -gl.gl_je_headers.posted_date)
|
DISPLAY_EXP_END_DTE
Indexed - no
Format - date (7)
May be null? yes |
For the final expense-based invoice, the date displayed on the invoice
as the date of the end of the expense period covered by the invoice.
The value is null for automatic payment invoices, for receipts,
and for expense-based
invoices other than the final one for the fund.
In most cases, the expense period for the final expense-based invoice
extends past the ACCOUNT_END_DATE for the FUND_CODE. For example, the ACCOUNT_END_DATE
is December 31, 2003, but the final closing expense charges
are not posted until January 30, 2004. In order to capture the January
expense on the final invoice, the EXPENSE_END_DATE is set to January 31,
2004. However, if that is the expense period end date displayed on the
invoice, the sponsor would reject it, because it is later than the
ACCOUNT_END_DATE. Therefore, the DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE
are the dates that appear on the final invoice as the
dates for the expense period.
DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE are populated for final expense-based
invoices posted during or after MAY-04. They are not available for
final invoices posted before that accounting period. Note:
the data for DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE is reliable only if the snapshot is for
February, 2006 or for a later accounting period. (For example, ACCT_PER_SNAPSHOT=
'FEB-06'.)
See also EXPENSE_START_DATE
and EXPENSE_END_DATE.
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: 4/30/2004 (April 30, 2004)
BRIM source: ARMAST.assign (current records) or ARYMST.assign (history
records)
|
DISPLAY_EXP_START_DTE
Indexed - no
Format - date (7)
May be null? yes |
For the final expense-based invoice, the date displayed on the invoice
as the date of the beginning of the expense period covered by the invoice.
The value is null for automatic payment invoices, for receipts, and for
expense-based invoices other than the final one for the fund.
In most cases, the expense period for the final expense-based invoice
extends past the ACCOUNT_END_DATE for the FUND_CODE. For example, the ACCOUNT_END_DATE
is December 31, 2003, but the final closing expense charges are not posted
until January 30, 2004. In order to capture the January expense on the
final invoice, the EXPENSE_END_DATE is set to January 31, 2004. However,
if that is the expense period end date displayed on the invoice, the
sponsor would reject it, because it is later than the ACCOUNT_END_DATE.
Therefore, the DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE are the
dates that appear on the final invoice as the dates for the expense period.
DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE are populated for final
expense-based invoices posted during or after MAY-04. They are not available
for final invoices posted before that accounting period. Note:
the data for DISPLAY_EXP_START_DTE and DISPLAY_EXP_END_DTE is reliable only
if the snapshot is for February, 2006 or for a later accounting period.
(For example, ACCT_PER_SNAPSHOT=
'FEB-06'.)
See also EXPENSE_START_DATE
and EXPENSE_END_DATE.
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: 4/1/2004 (April 1, 2004)
BRIM source: ARMAST.respon (current records) or ARYMST.respon (history
records)
|
|
EXPENSE_END_DATE
Indexed - no
Format - date (7)
May be null? yes
|
For expense-based invoices, the date of the end of the expense period
covered by the invoice. The value will be null for other records.
See also
DISPLAY_EXP_END_DTE.
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: 6/30/2002
BRIM source: ARMAST.ornum (current records) or ARYMST.ornum (history
records)
|
|
EXPENSE_START_DATE
Indexed - no
Format - date (7)
May be null? yes
|
For expense-based invoices, the date of the beginning of the expense
period covered by the invoice. For automatic payment invoices, this is
the date the invoice was created. For most receipts, this is the date
the receipt was posted in the General Ledger.
See also
DISPLAY_EXP_START_DTE.
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: 4/1/2002
BRIM source: ARMAST.ordate (current records) or ARYMST.ordate (history
records) (for most receipts, fed to BRIM from BEN Financials via the SBTASSET.txt
extract-gl.gl_je_headers.posted_date)
|
|
FISCAL_MON_SEQ_APPLIED
Indexed - yes
Format - char (2)
May be null? yes
|
The month (accounting period) of the fiscal year in which the DATE_APPLIED
falls. This field is used for sorting.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
Note: because the FISCAL_MON_SEQ_APPLIED is ultimately based on the DATE_
APPLIED, 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_INV_DATED
Indexed - yes
Format - char (2)
May be null? yes
|
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 cash receipt, credit memo, or invoice.
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_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_MASTER 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_APPLIED
Indexed - yes
Format - char (4)
May be null? yes
|
The financial year in which the DATE_APPLIED falls. Penn's fiscal year
begins July 1 of one calendar year and ends June 30 of the next calendar
year.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
Example: 2003 (the fiscal year beginning July 1, 2002, and ending June
30, 2003, in which DATE_APPLIED 9/4/2002 falls.)
|
|
FISCAL_YR_INVOICE_DATED
Indexed - yes
Format - char (4)
May be null? yes
|
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 cash receipt, credit memo, or invoice.
Example: 2003 (fiscal year beginning July 1, 2002, and ending June 30,
2003, in which 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_MASTER 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 to which
the cash receipt, credit memo, or 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: 1st 6 characters of ARMAST.ponum (current records) or ARYMST.ponum
(history records) (for most receipts, fed to BRIM from BEN Financials
via the SBTASSET.txt extract - gl.gl_code_combinations.segment4)
|
|
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 expense-based invoice or auto
pay invoice was generated, and #### is the sequence number (with leading
zeroes) of the invoice to which cash or credit has been applied.
For cash receipt records, the value will have the format FFFFFF, indicating
the FUND_CODE for the sponsored project fund to which the cash receipt
applies.
Example: 539354-0001, 539354
BRIM source: ARMAST.ponum (current records) or ARYMST.ponum (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 BRIM_MASTER record.
Example: 0103 (Biology)
Values: Refer to the ORG_CODES table for values.
BRIM source: ARINVT.lead
|
|
INTERNAL_REFERENCE_NO
Indexed - yes
Format - char (8)
May be null? no
|
A code of up to 8 characters that identifies a cash receipt, credit memo,
or invoice. See also FUND_INVOICE_NUMBER and BRIM_ORIGINAL_TRANS_ID.
Note: both records pertaining to a voided invoice (the original invoice
and the record negating its INVOICE TOTAL) have the same value for
INTERNAL_REFERENCE_NO.
Examples:
_RECEIPT (for all receipts)
15719 (if RECORD_TYPE is 'C',
this uniquely identifies a credit memo; otherwise, it uniquely identifies
an invoice)
BRIM source: ARMAST.invno (current records) or ARYMST.invno (history
records)
|
|
INVOICE_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date of the cash receipt, credit memo, or invoice.
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 (August 2, 2002)
BRIM source: ARMAST.invdte (current records) or ARYMST.invdte (history
records)
|
|
INVOICE_TOTAL
Indexed - no
Format - number (13,2)
May be null? yes
|
The total amount of the cash receipt, credit memo, or invoice.
Usually, for cash receipts and credit memos, the INVOICE_TOTAL has a
negative value; for invoices, the INVOICE_TOTAL has a positive value.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARMAST.invamt (current records) or ARYMST.invamt (history
records) (for most receipts, fed to BRIM from BEN Financials via the SBTASSET.txt
extract -gl.gl_je_lines.entered_dr and gl.gl_je_lines.entered_cr)
|
|
MAINT
Indexed - no
Format - char (1)
May be null? no
|
A 1-character code used to distinguish the original invoice record from
the record posted to negate the invoice when it is voided.
In most cases, MAINT has the value '.' . (Because MAINT is part of the
unique identifier for BRIM_MASTER records, its value in the Warehouse
cannot be blank. Blanks in BRIM are converted to dots in the Warehouse.)
However, when an invoice is voided in BRIM, the original invoice has
its MAINT changed to A, and an invoice record is created (with the same
INTERNAL_REFERENCE_NO but a blank MAINT) to negate the original invoice's
INVOICE_TOTAL. (See also VOID_INVOICE_FLAG.)
Values:
. a receipt, credit memo, or (non-voided) invoice,
or the negating record in the pair of records for
a voided invoice
A the original record in the pair of records for a
voided invoice
BRIM source: ARMAST.maint (current records) or ARYMST.maint (history
records)
|
|
MONTH_APPLIED
Indexed - yes
Format - char (2)
May be null? yes
|
The 2-character number that identifies the calendar month (accounting
period) in which the DATE_APPLIED falls.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
Note: because the MONTH_APPLIED is ultimately based on the DATE_APPLIED,
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_INVOICE_DATED
Indexed - yes
Format - char (2)
May be null? yes
|
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 cash receipt, credit memo, or invoice.
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
|
|
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_MASTER 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
|
|
PAID_AMOUNT
Indexed - no
Format - number (13,2)
May be null? yes
|
For an invoice, the PAID_AMOUNT is the total amount of the payment(s)
applied to the invoice. The value is usually 0 or greater.
For cash receipts and credit memos, the PAID_AMOUNT is the amount available
to be applied to one or more invoices (or, rarely, to a cash receipt).
The value is usually 0 or greater for cash receipts, and 0 or less for
credit memos.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARMAST.paidamt (current records) or ARYMST.paidamt (history
records) (for most unapplied receipts, based on data fed to BRIM from
BEN Financials via the SBTASSET.txt extract -gl.gl_je_lines.entered_dr
and gl.gl_je_lines.entered_cr)
|
|
PAYMENT_ID
Indexed - no
Format - char (15)
May be null? yes
|
The sponsor-assigned code (up to 15 characters long) used to identify
the cash receipt.
Example: SUS 8730.IAH.09
BRIM source: ARMAST.refno (current records) or ARYMST.refno (history
records) (for most receipts, fed to BRIM from BEN Financials via the SBTASSET.txt
extract -gl.gl_je_lines.description)
|
|
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: ARTRAN.price (current records) or ARYTRN.price (history
records)
|
|
PRINCIPAL_INVESTIGATOR_NAME
Indexed - no
Format - char (35)
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: ARTRAN.descrip (current records) or ARYTRN.descrip (history
records)
|
|
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.
Example: 'Analysis of Ligand Binding ErbB Receptor Tyrosine Kinases'
BRIM source: ARTRAN.descr (current records) or ARYTRN.descr (history
records); taken in BRIM from ARINVT.descrip1)
|
|
QUARTER_SEQ_APPLIED
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year in which the DATE_APPLIED falls.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
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 cash receipt, credit memo, or invoice.
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 (11)
May be null? yes
|
The quarter of the fiscal year when the BRIM_MASTER 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)
|
|
RECEIPT_LINK
Indexed - yes
Format - char (17)
May be null? yes
|
Used to link a BRIM_MASTER record with its detail record(s), if any,
in BRIMCASH_RECEIPTS.
If the BRIM_MASTER record is for a cash receipt or credit memo, RECEIPT_LINK
is the INTERNAL_REFERENCE_NO concatenated with characters 2 - 9 of the
CASH_RCPT_ORIG_TRANS_ID. (A credit memo has an RECORD_TYPE of 'C'.) From
the first character to the last non-blank character, the value of RECEIPT_LINK
is 16 characters long (including internal blanks).
If the BRIM_MASTER record is for an invoice, RECEIPT_LINK is the BRIM_ORIGINAL_TRANS_ID.
From the first character to the last non-blank character, the value is
9 characters long (including internal blanks).
Examples: '_RECEIPT 17763'; 'I 14569' (an invoice); '16828 16828' (a
credit memo)
In the BRIM ARCASH & ARYCSH tables (the sources for BRIMCASH_RECEIPTS),
credit memo records look like invoice records, but, unlike invoice records,
have no value for applto (APPLIED_TO_ORIG_TRANS_ID). Records for most
cash receipts also have no value for applto. (Records for cash receipts
to which cash has been applied have an applto value that matches their
ARMAST oti (BRIM_MASTER.BRIM_ORIGINAL_TRANS_ID).) RECEIPT_LINK involves
concatenation for cash receipts and credit memos so those records in BRIM_MASTER
are not linked to invoice records in BRIMCASH_RECEIPTS that have the same
last 8 characters of CASH_RCPT_ORIG_TRANS_ID. RECEIPT_LINK for cash receipts
involves only the last 8 characters of CASH_RCPT_ORIG_TRANS_ID so the
cash receipt record in BRIM_MASTER can be linked to all the associated
records in BRIMCASH_RECEIPTS, where the CASH_RCPT_ORIG_TRANS_ID value
starts with an R for the unapplied receipt, and with a C for the application(s)
of the receipt. RECEIPT_LINK for credit memos also includes the last 8
characters of CASH_RCPT_ORIG_TRANS_ID, to ensure that the credit memo
record in BRIM_MASTER is not linked to invoice records in BRIMCASH_RECEIPTS.
|
|
RECORD_TYPE
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code used to identify the type of the BRIM_MASTER record.
This is used in the aged receivables report.
Values:
blank invoice
C credit memo
R receipt
B history balance forward record (not used at Penn)
BRIM source: ARMAST.artype (current records) or ARYMST.artype (history records)
|
|
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: ARTRAN.school (current records) or ARYTRN.school (history
records)
|
|
SORT_PERIOD_APPLIED
Indexed - yes
Format - char (6)
May be null? yes
|
The accounting period in which the DATE_APPLIED falls. The value is stated
YYYYMM format. YYYY is the calendar year, and MM is the calendar month.
For unapplied cash receipt records, DATE_APPLIED is the date of the cash
receipt. For applied cash receipts and for all credit memos, DATE_APPLIED
is the latest date specified by the BRIM user as the date the cash receipt
or credit memo was applied to one or more invoices (or, in rare cases,
to a cash receipt). For invoices, DATE_APPLIED is the latest date specified
by the BRIM user as the date a cash receipt or credit memo was applied
to the invoice.
The value will be null for unapplied credit memos, and for invoices to
which neither cash nor credit has been applied.
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_APPLIED is ultimately based on the DATE_APPLIED,
there are no records for month 13.
Example: 200209 (the SORT_PERIOD_APPLIED for DATE_APPLIED 9/4/2002, which
falls in
SEP-02)
|
|
SORT_PERIOD_INVOICE_DATED
Indexed - yes
Format - char (6)
May be null? yes
|
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 cash receipt, credit memo, or invoice.
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: 200208 (the SORT_PERIOD_INVOICE_DATED for 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_MASTER 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 to which the cash receipt, credit memo, or invoice applies.
Examples: 1010 Department of the Army); 1430 (National Science Foundation).
Values: Refer to the FUND_SPONSORS table for values.
BRIM source: ARMAST.custno (current records) or ARYMST.custno (history
records) (for most receipts, based on data fed to BRIM from BEN Financials
via the SBTFUND.txt
extract-fnd_flex_values_vl.attribute4)
|
|
SPONSOR_INVOICE_NUMBER
Indexed - no
Format - char (12)
May be null? yes
|
For expense-based invoices, SPONSOR_INVOICE_NUMBER is a code up to 12
characters long that that is assigned by the sponsor to identify the invoice.
For automatic payment invoices, BRIM sets SPONSOR_INVOICE_NUMBER to 'Auto
Pay'.
Examples: 0015B; Auto Pay
BRIM source: ARMAST.shipvia (current records) or ARYMST.shipvia (history
records)
|
|
SPONSOR_REFERENCE_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: ARMAST.refer (current records) or ARYMST.refer (history
records)
|
|
TOTAL_INVOICE_VARIANCE_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
For an expense-based invoice, TOTAL_INVOICE_VARIANCE_AMT is the difference
between the INVOICE_TOTAL and the total actual expenses for the invoiced
period. See also EXPENSE_START_DATE and EXPENSE_END_DATE..
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARMAST.pmarkup (current records) or ARYMST.pmarkup (history
records)
|
|
VOID_INVOICE_FLAG
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code used to identify voided invoice records. Note:
for BRIM_MASTER records with BRIM_HISTORY_STATUS = ‘C’, the
data for VOID_INVOICE_FLAG is reliable only if the snapshot is for October,
2005 or for a later accounting period. (For example, ACCT_PER_SNAPSHOT=
'OCT-05'.) For BRIM_MASTER records with BRIM_HISTORY_STATUS = ‘H’,
the data for VOID_INVOICE_FLAG is reliable for all snapshots.
For most records, VOID_INVOICE_FLAG is N.
When an invoice is voided in BRIM, an invoice record is created (with
the same INTERNAL_REFERENCE_NO as the original invoice) to negate the
original invoice's INVOICE_TOTAL. Both the original invoice record and
the negating record have a VOID_INVOICE_FLAG of Y. (See also MAINT.)
Values:
N a receipt, credit memo, or (non-voided) invoice,
or the negating record in the pair of records for
a voided invoice
Y a voided invoice
BRIM source: ARMAST.arstat (current records) or ARYMST.arstat (history
records)
|
