| Data element |
Definition |
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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The ACCT_PER_INVOICE_DATED will be null if the expense has not been invoiced
(INVOICED_IND is 'N').
Note: the beginning and ending dates of an accounting period are not
the same as the first and last day of the calendar month.
Note: because the ACCT_PER_INVOICE_DATED is based on the INVOICE_DATE,
there are no records for the ADJ period.
Example: SEP-02 (September, 2002, which occurs in fiscal year 2003).
|
|
ACCT_PER_POSTED
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period to which the expense, revenue, or asset was posted.
The value 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 BRIM does not use the ADJ period, any expenses posted to
the ADJ period in the General Ledger are recorded in BRIM as if they were
posted to the JUN period.
Example: OCT-97 (October, 1997, which occurs in fiscal year 1998).
BRIM source: AREXIM.acctper (current records) or ARYXIM.acctper (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt
extract-gl.gl_period_statuses.period_name)
|
|
ACTUAL_AMT
Indexed - no
Format - number (13,2)
May be null? yes
|
The summarized amount of the actual dollars for the BRMFUND_OBJEXP_SEQNO.
When aggregating this column by the FUND_CODE and OBJECT_CODE for the
ACCT_PER_POSTED, the sum should equal the aggregated ACTUAL_MONTH balance
for the same period for the COA_FUND and COA_OBJECT in the BALANCES table.
Note: There is usually, but not always, one record per FUND_CODE, ACCT_PER_POSTED,
OBJECT_CODE, and GL_EXTRACT_DATE. See also BRMFUND_OBJEXP_SEQNO.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: AREXIM.actamt (current records) or ARYXIM.actamt (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt extract -gl.gl_je_lines.entered_dr
and gl.gl_je_lines.entered_cr)
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIMFUND_OBJ_EXP record was loaded into the Data Warehouse.
This is usually the same date that the record was extracted from BRIM.
This information is stored in the Warehouse in date format. In Business
Objects, it is displayed as specified in the desktop operating system
settings. It is recommended that users specify a date format that includes
4 digits for the year. (To specify the date format in Windows 95, choose
the Regional Settings of the Control Panel, select the Date tab and specify
the Short date style. In Windows, use the International option of the
Control Panel. On the Macintosh, use the Date & Time Control Panel.)
Example: 9/19/2002
|
|
BRIMFUND_OBJEXP_SEQNO
Indexed - yes
Format - number (9)
May be null? no
|
A sequence number, up to 9 digits long, used to uniquely identify a BRIMFUND_OBJ_EXP
record. The value of the sequence number is determined by the program
that loads the data into the BRIMFUND_OBJ_EXP table.
The sequence number is needed because, although there is usually one
record per FUND_CODE, ACCT_PER_POSTED, OBJECT_CODE, and GL_EXTRACT_DATE,
this is not always the case.
|
|
CAL_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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The CAL_YR_INVOICE_DATED will be null if the expense has not been invoiced
(INVOICED_IND is 'N').
Example: 1997 (the calendar year for INVOICE_DATE 09/01/1997, which falls
in SEP-97).
|
|
CAL_YEAR_POSTED
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character number that identifies the calendar year of the accounting
period to which the expense, revenue, or asset was posted. This is based
on the ACCT_PER_POSTED. The calendar year begins January 1 and ends December
31.
Example: 2002 (the CAL_YEAR_POSTED for ACCT_PER_POSTED SEP-02).
BRIM source: AREXIM.acctyear (current records) or ARYXIM.invoiced (acctyear)
(based on data fed to BRIM from BEN Financials via the SBTEXP.txt extract
gl.gl_period_statuses.period_name)
|
|
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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The FISCAL_MON_SEQ_INV_DATED will be null if the expense has not been
invoiced (INVOICED_IND is 'N').
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_POSTED
Indexed - yes
Format - char (2)
May be null? no
|
The month (accounting period) of the fiscal year of the accounting period
to which the expense, revenue, or asset was posted. This field is used
for sorting.
Note: because BRIM does not use the ADJ period, any expenses posted in
the General Ledger to the ADJ period (fiscal month 13) are recorded in
BRIM as if they were posted to the JUN period (fiscal month 12).
Values:
01 July
02 August
03 September
04 October
05 November
06 December
07 January
08 February
09 March
10 April
11 May
12 June
|
|
FISCAL_YR_INVOICE_DATED
Indexed - yes
Format - char (4)
May be null? 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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The FISCAL_YR_INVOICE_DATED will be null if the expense has not been
invoiced (INVOICED_IND is 'N').
Example: 1998 (fiscal year beginning July 1, 1997, and ending June 30,
1998, in which INVOICE_DATE 09/01/1997 falls)
|
|
FISCAL_YEAR_POSTED
Indexed - yes
Format - char (4)
May be null? no
|
The financial year of the accounting period to which the expense, revenue,
or asset was posted.
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 expense was charged. 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: AREXIM.coafund (current records) or AREXYM.coafund (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt
extract-gl.gl_code_combinations.segment4)
|
|
FUND_RESP_ORG
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code for the organization responsible for managing the
fund (FUND_CODE). Many organizations may use the same fund, but only one
organization - the FUND_RESP_ORG-is accountable for managing the fund.
Only those who are authorized to access records for the FUND_RESP_ORG
may access the BRIMFUND_OBJ_EXP record.
Example: 0103 (Biology)
Values: Refer to the ORG_CODES table for values.
BRIM source: ARINVT.lead
|
|
GL_EXTRACT_DATE
Indexed - yes
Format - date (7)
May be null? yes
|
The date when the BRIMFUND_OBJ_EXP record was extracted from the General
Ledger for export to 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 source: AREXIM.exdate (current records) or ARYXIM.exdate (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt
extract-control.run_date, the system date the extract was created)
|
|
INTERNAL_REFERENCE_NO
Indexed - yes
Format - char (8)
May be null? yes
|
A code of up to 8 characters that uniquely identifies the BRIM invoice
that includes the ACTUAL_AMT of this BRIMFUND_OBJ_EXP record in the Actual
Amount of a line item.
See also INVOICED_IND and INVOICE_DATE.
The INTERNAL_REFERENCE_NO value will be null if the expense has not been
invoiced (INVOICED_IND is 'N').
Example: 15719
BRIM source: AREXIM.invno (current records) or ARYXIM.invno (history
records)
|
|
INVOICE_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date of the BRIM invoice that includes the ACTUAL_AMT of this BRIMFUND_OBJ_EXP
record in the Actual Amount of a line item.
See also INVOICED_IND and INTERNAL_REF_NO.
The INVOICE_DATE will be null if the expense has not been invoiced (INVOICED_IND
is 'N').
INVOICE_DATE is stored in the Warehouse in date format. In Business Objects,
it is displayed as specified in the desktop operating system settings.
It is recommended that users specify a date format that includes 4 digits
for the year. (To specify the date format in Windows 95, choose the Regional
Settings of the Control Panel, select the Date tab and specify the Short
date style. In Windows, use the International option of the Control Panel.
On the Macintosh, use the Date & Time Control Panel.)
Example: 9/13/2002
BRIM source: ARMAST.invdte (current records) or ARYMST.invdte (history
records)
|
|
INVOICED_IND
Indexed - no
Format - char (1)
May be null? yes
|
A 1-character code that indicates whether the expense has been invoiced
(billed).
That is, an INVOICED_IND of 'Y' means that the ACTUAL_AMT of this BRIMFUND_OBJ_EXP
record is included n the Actual Amount of a line item in an invoice in
BRIM.
See also INTERNAL_REF_NO and INVOICE_DATE.
Values:
Y the expense has been invoiced
N the expense has not been invoiced
BRIM source: AREXIM.invoiced (current records) or ARYXIM.invoiced (history
records)
|
|
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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The MONTH_INVOICE_DATED will be null if the expense has not been invoiced
(INVOICED_IND is 'N').
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_POSTED
Indexed - yes
Format - char (2)
May be null? no
|
The 2-character number that identifies the calendar month (or accounting
period) to which the expense, revenue, or asset was posted. This is based
on the ACCT_PER_POSTED.
Note: because BRIM does not use the ADJ period, any expenses posted in
the General Ledger to the ADJ period (month 13) are recorded in BRIM as
if they were posted to the JUN period (month 12).
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
BRIM source: AREXIM.acctmonth (current records) or ARYXIM.invoiced (acctmonth)
(based on data fed to BRIM from BEN Financials via the SBTEXP.txt extract-gl.gl_period_statuses.period_name)
|
|
OBJECT_CODE
Indexed - yes
Format - char (4)
May be null? no
|
The 4-character code that identifies the asset, liability, revenue, or
expense. Only OBJECT_CODES that fall under Object Parents SB01 through
SB41 are included in the BRIMFUND_OBJ_EXP table.
Examples: 1832 (OTHER EQUIP), 4182 (STUD AID G/P); 5044 (RES FELLOW)
Values:
Refer to the OBJECT_CODES table for values.
BRIM source: AREXIM.coaobj (current records) or ARYXIM.coaobj (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt
extract-gl.gl_code_combinations.segment5)
|
|
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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The QUARTER_SEQ_INVOICE_DATED will be null if the expense has not been
invoiced (INVOICED_IND is 'N').
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
QUARTER_SEQ_POSTED
Indexed - no
Format - char (1)
May be null? yes
|
The quarter of the fiscal year to which the expense, revenue, or asset
was posted. This is based on the ACCT_PER_POSTED.
Values:
1 First quarter (July-September)
2 Second quarter (October-December)
3 Third quarter (January-March)
4 Fourth quarter (April-Adjustment period)
|
|
SB_OBJ_PARENT
Indexed - yes
Format - char (4)
May be null? no
|
The 4-character code for the Object in the General Ledger's chart of
accounts that serves as the parent (or rollup group) for the OBJECT_CODE,
allowing amounts to be summarized at the parent level.
An OBJECT_CODE identifies the asset, liability, revenue, or expense.
On BRIM invoices, an SB_OBJ_PARENT corresponds to an invoice line.
In the General Ledger, a given parent Object may be associated with more
than one child Object, and a given child Object may have more than one
parent. However, BRIM includes only Objects that fall
under Object parents SB01 through SB41, and a given Object has only one
SB_OBJ_PARENT. All values for SB_OBJ_PARENT begin with 'SB'.
Example: SB01 (Administrative Salaries)
Values: Refer to the BRIM_EXP_CODES table for values.
BRIM source: AREXIM.objpar (current records) or ARYXIM.objpar (history
records) (fed to BRIM from BEN Financials via the SBTEXP.txt
extract-applsys.fnd_flex_value_hierarchies.parent_flex_
value)
|
|
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 BRIM invoice that includes the ACTUAL_AMT
of this BRIMFUND_OBJ_EXP record in the Actual Amount of a line item.
The SORT_PERIOD_INVOICE_DATED will be null if the expense has not been
invoiced (INVOICED_IND is 'N').
Note: the beginning and ending dates of an accounting period are not
the same as the first and last day of the calendar month.
Note: because the SORT_PERIOD_INVOICE_DATED is ultimately based on the
INVOICE_DATE, there are no records for month 13.
Example: 199709 (the SORT_PERIOD_INVOICE_DATED for INVOICE_DATE 09/01/1997,
which falls in SEP-97)
|
|
SORT_PERIOD_POSTED
Indexed - yes
Format - char (6)
May be null? no
|
SORT_PERIOD_POSTED
Indexed - yes
Format - char (6)
May be null? no The accounting period to which the expense, revenue, or
asset was posted. This is based on the ACCT_PER_POSTED, and is stated
in 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 BRIM does not use the ADJ period, any expenses posted in
the General Ledger to the ADJ period (month 13) are recorded in BRIM as
if they were posted to the JUN period (month 12).
Example: 200209 (the SORT_PERIOD_POSTED for ACCT_PER_POSTED SEP-02)
|
