| Data element |
Definition |
ADJUSTMENTS_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes |
The total adjustment amount applied to this transaction. |
|
AGREEMENT_NUMBER
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The agreement number for this invoice.
The agreement number is assigned when an invoice is created for an award in the BEN Billing and Receivables GMS module.
The AGREEMENT_NUMBER is stored in the Invoice Transaction Flexfield when a transaction related to the GMS draft invoice is created in the BEN Blling and Receivables AR module. |
ASSIGNMENTS_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The total assignment amount applied to this transaction. |
|
AWARD_NUMBER
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The BBR_AWARD_NUMBER associated with this transaction.
The BBR_AWARD_NUMBER is stored in the Invoice Transaction Flexfield when a transaction related to the GMS draft invoice is created in the BEN Blling and Receivables AR module.
Although this is named "PROJECT NUMBER" on the DFF it is actually the award number. If more than one award is related to this transaction, such as may be the case with a deposit transaction, then this field will be null. |
|
AWARD_ORGANIZATION
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The organization responsible for the proposal associated with this transaction.
The AWARD_ORGANIZATION is stored in the Invoice Transaction Flexfield when a transaction related to the GMS draft invoice is created in the BEN Blling and Receivables AR module.
Although this is named "PROJECT ORGANIZATION" on the DFF it is actually the award org. Contains award org as of the time of the transaction. If more than one award is related to this transaction, such as may be the case with a deposit transaction, then this field will be null. |
|
BALANCE_DUE_CHARGES
Format NUMBER
Indexed? No
May be Null? Yes
|
The total receivables charges due for this transaction. |
|
BALANCE_DUE_FREIGHT
Format NUMBER
Indexed? No
May be Null? Yes
|
The total freight due for this transaction. |
|
BALANCE_DUE_LINE
Format NUMBER
Indexed? No
May be Null? Yes
|
The total balance due for all lines associated with this transaction.
The line balance due does not include amounts due for tax, freight or receivables charges. |
|
BALANCE_DUE_TAX
Format NUMBER
Indexed? No
May be Null? Yes
|
The total tax due for this transaction. |
|
BALANCE_DUE_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The total balance due for this transaction including line, tax, freight and recievables charges.
|
|
BBR_AWARD_NUMBER
Format VARCHAR2 (30)
Indexed? Yes
May be Null? Yes
|
The alphanumeric identifier used internally by the BEN Billing and Receivable system to uniquely identify the proposal.
An Award Number is associated with only one INSTITUTION_NO. INSTITUTION_NO is the eight-digit sequence number used by the University to uniquely identify the proposal.
For a given record, BBR_AWARD_NUMBER will not have the same value as the proposal's INSTITUTION_NO. |
|
BBR_AWARD_ORGANIZATION
Format VARCHAR2(4)
Indexed? Yes
May be Null? No
|
The 4-character code that identifies the organization responsible for the proposal associated with this transaction.
To facilitate Organization-based security, BBR_AWARD_ORG is set to '.' if it would otherwise be null.
Values: Refer to the ORG_CODES table for values. |
|
BBR_CUSTOMER_REGISTRY_ID
Format VARCHAR2 (30)
Indexed? Yes
May be Null? Yes
|
Registry ID for the Customer funding the proposal associated with this tranasaction.
This value corresponds to the BBR_CUSTOMER_REGISTRY_ID field on the AR_CUSTOMER table in the BEN Billing and Receivables collection in the data warehouse. |
|
BBR_EVENT_NUMBER
Format NUMBER (15)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the project event associated with this transaction. |
|
BBR_INSTALLMENT_NUMBER
Format VARCHAR2 (15)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the award installment associated with this transaction. |
|
BBR_PROJECT_NUMBER
Format VARCHAR2 (25)
Indexed? No
May be Null? Yes
|
The 6-character fund code associated with this transaction.
A fund is the unique identifier for a specific set of financial resources that needs tracking or management. FUND_CODE is the fourth segment of the Accounting Flexfield.
Values: Refer to the FUND_CODES table for values. |
|
BBR_RECEIPT_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The alphanumeric identifier used internally by the BEN Billing and Receivable system to identify the receipt associated with this transaction. |
|
BBR_TASK_NUMBER
Format VARCHAR2 (25)
Indexed? No
May be Null? Yes
|
The alphanumeric identifier used internally by the BEN Billing and Receivable system to identify the project task associated with this transaction. |
|
BILL_TO_ADDRESS_BLOCK
Format VARCHAR2 (1260)
Indexed? No
May be Null? Yes |
The address of the bill to customer associated with this transaction.
|
|
BILL_TO_CONTACT
Format VARCHAR2 (360)
Indexed? No
May be Null? Yes
|
The first and last name of the bill to customer associated with this transaction.
This value corresponds to the BBR_CUST_ACCT_SITE_CONTACT field on the AR_CUSTOMER_ACCOUNT_SITE table in the BEN Billing and Receivables collection in the data warehouse. |
|
BILL_TO_LOCATION
Format VARCHAR2 (40)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the location of the bill to customer associated with this transaction.
This value corresponds to the BBR_bill_TO_LOCATION_ID field on the AR_CUSTOMER_ACCOUNT_SITE table in the BEN Billing and Receivables collection in the data warehouse.
|
|
BILL_TO_NAME
Format VARCHAR2 (360)
Indexed? No
May be Null? Yes
|
The name of the bill to customer associated with this transaction.
|
|
BILL_TO_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the account of the bill to customer associated with this transaction.
This value corresponds to the BBR_CUSTOMER_ACCOUNT_NUMBER field on the AR_CUSTOMER_ACCOUNT table in the BEN Billing and Receivables collection in the data warehouse. |
|
COMMITMENT
Format VARCHAR2 (20)
Indexed? No
May be Null? Yes
|
The TRX_NUMBER of a commitment transaction related to this transaction. |
|
COMPLETE
Format VARCHAR2 (1)
Indexed? No
May be Null? Yes
|
Indicates if the invoice is complete.
Values: Y (Yes) N (not Yes) |
|
CONTEXT_VALUE
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
For Feeder transactions, CONTEXT_VALUE contains additional information about the feeder source. |
|
CREDITED_TRX_ID
Format NUMBER (15)
Indexed? Yes
May be Null? Yes
|
For credit memos, the TRX_ID of the credited transaction. |
|
CREDITED_TRX_NUMBER
Format VARCHAR2 (20)
Indexed? No
May be Null? Yes
|
For credit memos,The TRX_NUMBER of the credited transaction.
The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. Transactions from different sources may have the same TRX_NUMBER. |
|
CREDITED_TRX_SOURCE
Format VARCHAR2 (50)
Indexed? No
May be Null? Yes
|
For credit memos, the TRX_SOURCE of the credited transaction.
The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. Transactions from different sources may have the same TRX_NUMBER. |
|
CREDITS_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The total credit amount applied to this transaction.
|
|
DISCOUNTS_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The total discount amount applied to this transaction. |
DOCUMENT_NUMBER
Format NUMBER (15)
Indexed? No
May be Null? Yes |
|
|
DRAFT_INVOICE_NUMBER
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The draft invoice number for this invoice.
The draft invoice number is assigned when an invoice is created for an award in the BEN Billing and Receivables GMS module. Draft invoices are numbered sequentially starting from one for each award.
The draft invoice number is stored in the Invoice Transaction Flexfield when a transaction related to the GMS draft invoice is created in the BEN Blling and Receivables AR module. |
|
DUE_DATE
Format DATE
Indexed? No
May be Null? Yes
|
The date payment is due for this transaction based on the transaction payment terms.
If the transaction payment terms are "IMMEDIATE" then the DUE_DATE with be the same as the TRX_DATE. |
|
EXTRACT_DATE
Format DATE
Indexed? Yes
May be Null? Yes
|
The date the transaction header record was extracted from BEN Billing and Receivables and loaded into the Data Warehouse.
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. |
|
EXTRACT_DATE_PAY_SCHED
Format DATE
Indexed? Yes
May be Null? Yes
|
The date payment schedule data associated with this transaction was extracted from BEN Billing and Receivables and loaded into the Data Warehouse.
The payment schedule in BEN Billing and Receivables contains summarized balances for each transaction and these balances may change independently of the changes to the transaction itself due to activity such as credits, adjustments and receipts. Fields on this table that can be modifed by the payment schedule changes are: BALANCE_DUE_LINE BALANCE_DUE_TAX BALANCE_DUE_FREIGHT BALANCE_DUE_CHARGES BALANCE_DUE_TOTAL ORIGINAL_TOTAL RECEIPTS_TOTAL CREDITS_TOTAL ADJUSTMENTS_TOTAL ASSIGNMENTS_TOTAL DISCOUNTS_TOTAL
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. |
|
INITIAL_CUSTOMER_TRX_ID
Format NUMBER (15)
Indexed? Yes
May be Null? Yes
|
The TRX_ID of a commitment transaction related to this transaction. |
|
INV_GL_DATE
Format DATE
Indexed? Yes
May be Null? Yes
|
The date the transaction is accounted for in the General Ledger.
It is possible for lines associated with a single transaction to have different INV_GL_DATE dates. In that case this field contains the most recent INV_GL_DATE date. |
|
INV_GL_DATE_ACCT_PERIOD
Format VARCHAR2 (15)
Indexed? Yes
May be Null? Yes
|
The Accounting Period stated in MON-YY format.
MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an ACCOUNTING_PERIOD are not the same as the first and last day of the calendar month. Example: JUL-96 (July 1996, which occurs in fiscal year 1997). |
|
INV_GL_DATE_FISCAL_MONTH_SEQ
Format VARCHAR2 (2)
Indexed? Yes
May be Null? Yes
|
The month (or accounting period) of the fiscal year.
This field is used for sorting. Examples: 01 (July); 11 (May). See also FISCAL_YEAR |
|
INV_GL_DATE_FISCAL_YEAR
Format VARCHAR2 (4)
Indexed? Yes
May be Null? Yes
|
The financial year.
Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year. Example: 1997 (fiscal year that began July 1, 1996, and ended June 30, 1997) |
|
INVOICING_RULE
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The name of the invoicing rule used for the transaction.
Values: Advance Invoice Arrears Invoice Immediate |
|
LEGAL_ENTITY
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The legal entity that owns or issues this transaction. |
|
ORIGINAL_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The original balance due for this transaction including line, tax, freight and recievables charges. |
|
PAYMENT_TERM
Format VARCHAR2 (15)
Indexed? No
May be Null? Yes
|
The payment terms for the transaction.
Values: 30 NET IMMEDIATE
|
|
PENNERA_SPONSOR_CODE
Format VARCHAR2 (5)
Indexed? Yes
May be Null? Yes
|
The 5-character numeric code that uniquely identifies the agency that was asked to fund the proposal.
Codes less than or equal to 599999 were assigned to the sponsor by InfoEd (the vendor of the PennERA software). Codes greater than or equal to 60000 were assigned to the sponsor by the Office of Research Services.
Values: Refer to the PENNERA_SPONSOR Table for values. PennERA source (assuming the proposal record has been opened in the Proposal Tracking module): any screen for the proposal; the Proposal Header (unlabelled, stationary section at the top of the screen); the sponsor code for the sponsor named on the second line of the Proposal Header text (SPONSOR_CODE is not shown) |
|
PROJECT_MANAGER
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The name of the primary investigator responsible for the proposal associated with this transaction.
The PROJECT_MANAGER is stored in the Invoice Transaction Flexfield when a transaction related to the GMS draft invoice is created in the BEN Blling and Receivables AR module. |
|
RECEIPTS_TOTAL
Format NUMBER
Indexed? No
May be Null? Yes
|
The total receipt amount applied to this transaction. |
|
RELATED_TRX_ID
Format NUMBER (15)
Indexed? Yes
May be Null? Yes |
The TRX_ID of the transaction related to this transaction. |
|
RELATED_TRX_NUMBER
Format VARCHAR2 (20)
Indexed? No
May be Null? Yes
|
The TRX_NUMBER of the transaction related to this transaction.
The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. Transactions from different sources may have the same TRX_NUMBER. |
|
RELATED_TRX_SOURCE
Format VARCHAR2 (50)
Indexed? No
May be Null? Yes
|
The TRX_SOURCE of the transaction related to this transaction.
The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. Transactions from different sources may have the same TRX_NUMBER. |
|
SHIP_TO_ADDRESS_BLOCK
Format VARCHAR2 (360)
Indexed? No
May be Null? Yes
|
The address of the ship to customer associated with this transaction. |
|
SHIP_TO_CONTACT
Indexed - no
Format - number (13,2)
May be null? yes
|
The first and last name of the ship to customer associated with this transaction.
This value corresponds to the BBR_CUST_ACCT_SITE_CONTACT field on the AR_CUSTOMER_ACCOUNT_SITE table in the BEN Billing and Receivables collection in the data warehouse. |
|
SHIP_TO_LOCATION
Format VARCHAR2 (40)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the location of the ship to customer associated with this transaction.
This value corresponds to the BBR_SHIP_TO_LOCATION_ID field on the AR_CUSTOMER_ACCOUNT_SITE table in the BEN Billing and Receivables collection in the data warehouse. |
|
SHIP_TO_NAME
Format VARCHAR2 (360)
Indexed? No
May be Null? Yes
|
The name of the ship to customer associated with this transaction. |
|
SHIP_TO_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the account of the ship to customer associated with this transaction.
This value corresponds to the BBR_CUSTOMER_ACCOUNT_NUMBER field on the AR_CUSTOMER_ACCOUNT table in the BEN Billing and Receivables collection in the data warehouse. |
|
SOLD_TO_NAME
Format VARCHAR2 (360)
Indexed? No
May be Null? Yes
|
The sold to customer name. |
|
SOLD_TO_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? Yes
|
The numeric identifier used internally by the BEN Billing and Receivable system to identify the account of the sold to customer associated with this transaction.
This value corresponds to the BBR_CUSTOMER_ACCOUNT_NUMBER field on the AR_CUSTOMER_ACCOUNT table in the BEN Billing and Receivables collection in the data warehouse. |
|
SPECIAL_INSTRUCTIONS
Format VARCHAR2 (240)
Indexed? No
May be Null? Yes
|
User entered special instructions that apply to this transaction. |
|
SPONSOR_INV_NUMBER
Format VARCHAR2 (150)
Indexed? No
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. |
|
TRX_CLASS
Format VARCHAR2 (20)
Indexed? No
May be Null? Yes
|
The transaction class code for the transaction.
Values: INV (Invoice) CM (Credit Memo) |
|
TRX_COMMENTS
Format VARCHAR2 (240)
Indexed? No
May be Null? Yes
|
User entered comments associated with this transaction. |
|
TRX_DATE
Format DATE
Indexed? Yes
May be Null? No
|
The date of the tranaction.
For invoices, the "Invoice Date". |
|
TRX_DATE_ACCT_PERIOD
Format VARCHAR2 (15)
Indexed? Yes
May be Null? No
|
The Accounting Period stated in MON-YY format.
MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an ACCOUNTING_PERIOD are not the same as the first and last day of the calendar month. Example: JUL-96 (July 1996, which occurs in fiscal year 1997). |
|
TRX_DATE_FISCAL_MONTH_SEQ
Format VARCHAR2 (2)
Indexed? Yes
May be Null? No
|
The month (or accounting period) of the fiscal year.
This field is used for sorting. Examples: 01 (July); 11 (May). See also FISCAL_YEAR |
|
TRX_DATE_FISCAL_YEAR
Format VARCHAR2 (4)
Indexed? Yes
May be Null? No
|
The financial year.
Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year. Example: 1997 (fiscal year that began July 1, 1996, and ended June 30, 1997) |
|
TRX_ID
Format NUMBER (15)
Indexed? Yes
May be Null? No
|
The numeric identifier used internally by the BEN Billing and Receivable system to uniquely identify the transaction. |
|
TRX_NUMBER
Format VARCHAR2 (20)
Indexed? Yes
May be Null? No
|
A numeric identifier used internally by the BEN Billing and Receivable system to identify the transaction.
The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. Transactions from different sources may have the same TRX_NUMBER. |
|
TRX_REFERENCE
Format VARCHAR2 (150)
Indexed? No
May be Null? Yes
|
The BBR_AWARD_NUMBER stored in the Interface Header Attribute 1 for this transaction. |
|
TRX_SOURCE
Format VARCHAR2 (50)
Indexed? No
May be Null? Yes
|
The name of the batch source in BEN Billing and Receivables that created the transaction. |
|
TRX_TYPE
Format VARCHAR2 (20)
Indexed? No
May be Null? Yes
|
The name of the transaction type for the transaction. |
