| Data element |
Definition |
ACCT_PER_APPLIED
Indexed - yes
Format - char (6)
May be null - no |
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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: OCT-97(October, 1997, which occurs in fiscal year 1998).
|
|
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: SEP-97 (September, 19979, which occurs in fiscal year 1998).
|
|
APPLIED_TO_ORIG_TRANS_ID
Indexed - no
Format - char (9)
May be null? yes
|
A 9-character code that identifies the receivable (the invoice, or, rarely,
the cash receipt) to which a cash receipt or credit memo has been applied.
In the group of records involved in a cash/credit application, the record
for the cash receipt or credit memo will have a null value for APPLIED_TO_ORIG_TRANS_ID
in BRIM (which is stored as '.' in the Warehouse). For the record(s) for
the receivable(s) to which the cash or credit was applied, the value of
APPLIED_TO_ORIG_TRANS_ID matches the value of the BRIM_ORIGINAL_TRANS_ID
in the BRIM MASTER record for the receivable.
Note: all 9 characters are used; there are blanks between the initial
letter and the numerals in the APPLIED_TO_ORIG_TRANS_ID.
Examples: 'I 3154' (an invoice to which cash or credit has been applied);
'R 1123' (a cash receipt to which cash has been applied); '.' (a receipt
or credit memo that is the source of cash/credit being applied)
BRIM source: ARCASH.applto (current records) or ARYCSH.applto (history
records)
|
|
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: ARCASH.batch (current records) or ARYCSH. 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: 04 (Federal 1034); 07 (Automatic Payment)
Values:
Refer to the FUND_BILLING_FORMAT_CODES table for values.
BRIM source: ARCASH.salesmn (current records) or ARYCSH.salesmn (history
records) (for most unapplied receipts, based on data fed to BRIM from
BEN Financials via the SBTFUND.txt extract-fnd_flex_values_vl.attribute27)
|
|
BRIM_EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date when the BRIMCASH_RECEIPTS record was loaded into the Data Warehouse.
This is usually the same date that the record was extracted from BRIM.
This information is stored in the Warehouse in date format. In Business
Objects, it is displayed as specified in the desktop operating system
settings. It is recommended that users specify a date format that includes
4 digits for the year. (To specify the date format in Windows 95, choose
the Regional Settings of the Control Panel, select the Date tab and specify
the Short date style. In Windows, use the International option of the
Control Panel. On the Macintosh, use the Date & Time Control Panel.)
Example: 9/19/2002
|
|
CALENDAR_YR_APPLIED
Indexed - no
Format - char (4)
May be null? no
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
Example: 1997 (the calendar year for DATE_APPLIED 10/31/1997, which falls
in OCT-97).
|
|
CALENDAR_YR_INVOICE_DATED
Indexed - no
Format - char (4)
May be null? no
|
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: 1997 (the calendar year for INVOICE_DATE 09/01/1997, which falls
in SEP-97).
|
|
CASH_RCPT_ORIG_TRANS_ID
Indexed - no
Format - char (9)
May be null? yes
|
A 9-character code that indicates the open cash receipt, or the cash
receipt or credit memo that is the source of the cash or credit in a cash/credit
application transaction.
A record for an open (unapplied) cash receipt has a CASH_RCPT_ORIG_TRANS_ID
beginning with R (for example, 'R 678'). (This matches the BRIM_ORIGINAL_TRANS_ID
for the receipt in the BRIM_MASTER table.) When the receipt is applied,
the records involved in the cash application transaction have a CASH_RCPT_ORIG_TRANS_ID
like the one for the open receipt, but beginning with C (for example,
'C 678'). If a credit memo is applied, the records involved in the cash
application transaction have a CASH_RCPT_ORIG_TRANS_ID that matches the
BRIM_ORIGINAL_TRANS_ID for the credit memo record in the BRIM_MASTER table.
Note: all 9 characters are used; there are blanks between the initial
letter and the numerals in the CASH_RCPT_ORIG_TRANS_ID if the numeric
portion is less than 8 digits.
Examples: 'R 12052' (an unapplied receipt); 'C 1123' (the receipt or
credit memo that is the source of the cash or credit in a cash/credit
application transaction)
BRIM source: ARCASH.oti (current records) or ARYCSH.oti (history records)
|
|
CCATI
Indexed - no
Format - char (8)
May be null? no
|
An 8-character numeric code that identifies the cash/credit application
transaction. When a cash receipt is posted in BRIM as being unapplied,
it is assigned a unique CCATI. When a cash receipt or credit memo is applied
to one or more receivables, a unique CCATI is used to identify the group
of records involved in the cash/credit application. The group includes
one record for each applied portion of the cash receipt or credit memo,
and one record for each receivable to which the cash or credit was applied.
For example, if a receipt for $100 is applied to two invoices, with $75
going to one invoice and $25 going to the other, there will be four records-one
for the $75 being applied from the receipt, one for the $75 being applied
to the first invoice, one for the $25 being applied from the receipt,
and one for the $25 being applied to the second invoice.
Note that if a cash receipt is entered manually in BRIM, and is immediately
applied in full, the CCATI group includes only the record(s) to which
the cash receipt was applied.
Example: 10327
BRIM source: ARCASH.ccati (current records) or ARYCSH.ccati (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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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/31/1997
BRIM source: ARCASH.dtepaid (current records) or ARYCSH.dtepaid (history
records) (for most unapplied 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? no
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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? no
|
The month (accounting period) of the fiscal year in which the INVOICE_DATE
falls. This field is used for sorting.
The INVOICE_DATE is the date of the 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_YR_APPLIED
Indexed - yes
Format - char (4)
May be null? no
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
Example: 1998 (the fiscal year beginning July 1, 1997, and ending June
30, 1998, in which DATE_APPLIED 10/31/1997 falls.)
|
|
FISCAL_YR_INVOICE_DATED
Indexed - yes
Format - char (4)
May be null? no
|
The financial year in which the INVOICE_DATE falls. Penn's fiscal year
begins July 1 of one calendar year and ends June 30 of the next calendar
year.
The INVOICE_DATE is the date of the cash receipt, credit memo, or invoice.
Example: 1998 (fiscal year beginning July 1, 1997, and ending June 30,
1998, in which INVOICE_DATE 09/01/1997 falls)
|
|
FUND_CODE
Indexed - yes
Format - char (6)
May be null? no
|
The 6-character code that identifies the sponsored project fund to which
the 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 ARCASH.ponum (current records) or ARYCSH.ponum
(history records) (for most unapplied 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? no
|
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 unapplied 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: ARCASH.ponum (current records) or ARYCSH.ponum (history
records) (for most unapplied receipts, fed to BRIM from BEN Financials
via the SBTASSET.txt extract -gl.gl_je_headers.entered_dr and gl.gl_je_headers.entered_cr)
|
|
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 BRIMCASH_RECEIPTS record.
Example: 0103 (Biology)
Values:
Refer to the ORG_CODES table for values.
BIRM 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, CCATI, and APPLIED_TO_ORIG_TRANS_ID.
Examples:
_RECEIPT (for all receipts)
15719 (if APPLIED_TO_ORIG_TRANS_ID is
null, this identifies a credit memo; otherwise, it identifies an invoice)
BRIM source: ARCASH.invno (current records) or ARYCSH.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: 09/01/1997
BRIM source: ARCASH.invdte (current records) or ARYCSH.invdte (history
records)
|
|
MONTH_APPLIED
Indexed - yes
Format - char (2)
May be null? no
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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? no
|
The 2-character number that identifies the calendar month (accounting
period) in which the INVOICE_DATE falls.
The INVOICE_DATE is the date of the 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
|
|
PAID_AMOUNT
Indexed - no
Format - number (13,2)
May be null? yes
|
The amount applied to the cash receipt, credit memo, or invoice.
Usually, when an unapplied receipt or credit memo is created, the PAID_AMOUNT
has a positive value. As a portion of the cash receipt or credit memo
is applied to an invoice, that portion is recorded with a negative value
for the receipt or credit memo, and with a positive value for the invoice
to which it is applied.
Values:
-99,999,999,999.99 to 99,999,999,999.99
BRIM source: ARCASH.paidamt (current records) or ARYCSH.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.
Examples: 'ACH PAY', 'CK 547900183227'
BRIM source: ARCASH.refno (current records) or ARYCSH.refno (history
records) (for most unapplied receipts, fed to BRIM from BEN Financials
via the SBTASSET.txt extract -gl.gl_je_lines.description)
|
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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)
|
|
RECEIPT_LINK
Indexed - yes
Format - char (17)
May be null? no
|
Used to link a BRIMCASH_RECEIPTS record with its summary record in BRIM_MASTER.
If the BRIMCASH_RECEIPTS record is the source of the cash or credit being
applied (that is, for credit memos and for most _RECEIPT records), RECEIPT_LINK
is the INTERNAL_REFERENCE_NO concatenated with characters 2 - 9 of the
CASH_RCPT_ORIG_TRANS_ID. From the first character to the last non-blank
character, the value is 16 characters long (including internal blanks).
If the BRIMCASH_RECEIPTS record is for a _RECEIPT that is the target
of the cash or credit being applied, RECEIPT_LINK is the INTERNAL_REFERENCE_NO
concatenated with characters 2 - 9 of the APPLIED_TO_ORIG_TRANS_ID. From
the first character to the last non-blank character, the value is 16 characters
long (including internal blanks).
If the BRIMCASH_RECEIPTS record is for an invoice, RECEIPT_LINK is the
APPLIED_TO_ORIG_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 to which cash has been
applied);
'16828 16828' (a credit memo)
In the BRIM ARCASH & ARYCSH tables, 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_SEQ_NO
Indexed - yes
Format - number (20,0)
May be null? no
|
A sequence number, assigned by BRIM, that uniquely identifies a BRIMCASH_RECEIPTS
record.
In most cases, there is one BRIMCASH_RECEIPTS record per CCATI, FUND_INVOICE_NUMBER,
INTERNAL_REF_NO, and APPLIED_TO_ORIG_TRANS_ID. However, consider the case
where a receipt for $100 is applied to two other receipts for the same
fund, with $75 applied to 'R 1111111' and $25 applied to 'R 2222222'.
There will be four records for the CCATI: (1) the $75 being applied from
the receipt, (2) the $75 being applied to 'R 1111111', (3) the $25 being
applied from the receipt, and (4) the $25 being applied to 'R 2222222'.
The values for CCATI, FUND_INVOICE_NUMBER, INTERNAL_REF_NO, and APPLIED_TO_ORIG_TRANS_ID
will be the same for records (1) and (3). Therefore, RECORD_SEQ_NO is
used to uniquely identify a BRIMCASH_RECEIPTS record.
Examples: 93, 361
BRIM source: ARCASH.caseno (current records) or ARYCSH.caseno (history
records)
|
|
SORT_PERIOD_APPLIED
Indexed - yes
Format - char (6)
May be null? no
|
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 other records, DATE_APPLIED is the date specified by the
BRIM user as the date a cash receipt or credit memo was applied to one
or more invoices (or, in rare cases, to a cash receipt).
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: 199710 (the SORT_PERIOD_APPLIED for DATE_APPLIED 10/31/1997,
which falls in OCT-97)
|
|
SORT_PERIOD_INVOICE_DATED
Indexed - yes
Format - char (6)
May be null? no
|
The accounting period in which the INVOICE_DATE falls. The value is stated
YYYYMM format. YYYY is the calendar year, and MM is the calendar month.
The INVOICE_DATE is the date of the 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: 199709 (the SORT_PERIOD_INVOICE_DATED for INVOICE_DATE 09/01/1997,
which falls in SEP-97)
|
|
SPONSOR_CODE
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code that identifies the external organization that sponsors
the fund to which the cash receipt, credit memo, or invoice applies.
Examples: 1010 Department of the Army); 1529 (Proctor & Gamble).
Values:
Refer to the FUND_SPONSORS table for values.
BRIM source: ARCASH.custno (current records) or ARYCSH.custno (history
records) (for most unapplied receipts, based on data fed to BRIM from
BEN Financials via the SBTFUND.txt extract-fnd_flex_values_vl.attribute4)
|
