| Data element |
Definition |
BBR_AWARD_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
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_ORG_CODE
Format CHAR(4)
Indexed? No
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.
|
PROMISE_DETAIL_ID
Format NUMBER (15)
Indexed? No
May be Null? No |
The numeric identifier used internally by the BEN Billing and Receivable system to uniquely identify the promise. |
LAST_UPDATE_DATE
Format DATE
Indexed? No
May be Null? No |
The date the promise was last updated. |
DELINQUENCY_ID
Format NUMBER (15)
Indexed? No
May be Null? No |
A numeric identifier used internally by the BEN Billing and Receivable system to identify the deliquency associated with the promise. |
TRX_ID
Format NUMBER (15)
Indexed? No
May be Null? No |
The numeric identifier used internally by the BEN Billing and Receivable system to uniquely identify the transaction associated with the promise. |
TRX_NUMBER
Format VARCHAR2 (20)
Indexed? No
May be Null? No |
A numeric identifier used internally by the BEN Billing and Receivable system to identify the disputed transaction. The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction associated with the promise. Transactions from different sources may have the same TRX_NUMBER. |
TRX_SOURCE
Format VARCHAR2 (50)
Indexed? No
May be Null? No |
The name of the batch source in BEN Billing and Receivables that created the transaction associated with the promise. |
BBR_CUSTOMER_ACCOUNT_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
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.
|
BBR_CUSTOMER_ACCT_SITE_NUMBER
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
The numeric identifier used internally by the BEN Billing and Receivable system to identify the the bill to site for the customer associated with this transaction.
This value corresponds to the BBR_CUSTOMER_ACCT_SITE_NUMBER field on the AR_CUSTOMER_ACCOUNT_SITE table in the BEN Billing and Receivables collection in the data warehouse.
|
BBR_BILL_TO_LOCATION_ID
Format NUMBER (15)
Indexed? No
May be Null? No |
The numeric identifier used internally by the BEN Billing and Receivable system to identify the bill to location for the 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.
|
AMOUNT_DUE_REMAINING
Format NUMBER
Indexed? No
May be Null? No |
The amount remaing to pay for the promise. |
CREATION_DATE
Format DATE
Indexed? No
May be Null? No |
The date the promise was created. |
INSTALLMENT
Format NUMBER (15)
Indexed? No
May be Null? No |
The sequence number given to each installment for multiple payment terms associated with this promise. |
INSTALLMENT_DUE_DATE
Format DATE
Indexed? No
May be Null? No |
The due date of this installment |
PAYMENT_ACCOUNT
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
Free text field containing account information. |
PAYMENT_METHOD
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The payment method for this promise.
Values:
Credit Card
Electronic Funds Transfer |
PAYMENT_METHOD_CODE
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the payment method for this promise.
Values:
|
PROMISE_AMOUNT
Format NUMBER
Indexed? No
May be Null? No |
The amount promisesd to pay. |
PROMISE_BROKEN_ON_DATE
Format DATE
Indexed? No
May be Null? No |
The date the promise was broken |
PROMISE_DATE
Format DATE
Indexed? No
May be Null? No |
The promised payment date. |
PROMISE_ASSIGNED_TO
Format VARCHAR2 (360)
Indexed? No
May be Null? No |
|
PROMISE_ITEM_NUMBER
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
The line item number associated with this promise. |
PROMISE_STATE
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The promise state.
Values:
Broken Promise
Promise |
PROMISE_STATE_CODE
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the promise state.
Values:
BROKEN_PROMISE
PROMISE |
PROMISE_STATUS
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The promise status.
Values:
Broken
Cancelled
Closed
Collectible
Fulfilled
In Question
Open
Pending
Rejected |
PROMISE_STATUS_CODE
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the promise status.
Values:
BROKEN
CANCELLED
CLOSED
COLLECTABLE
FULFILLED
IN_QUESTION
OPEN
PENDING
REJECTED |
WORK_QUEUE_COMPLETE_DATE
Format DATE
Indexed? No
May be Null? No |
Date the delinquency associated with this promise moved into the COMPLETE bucket on UWQ. |
WORK_QUEUE_STATUS
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The status of the delinquency associated with this promise on UWQ. Active/Pending/Complete.
Values:
Active
Complete
Pending |
WORK_QUEUE_STATUS_CODE
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the status of the delinquency associated with this promise on UWQ.
Values:
ACTIVE
COMPLETE
PENDING |
EXTRACT_DATE
Format DATE
Indexed? No
May be Null? No |
The date the promise 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. |
