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.
|
NOTE_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 note |
LAST_UPDATE_DATE
Format DATE
Indexed? No
May be Null? No |
The date the note was last modified. |
PARENT_NOTE_ID
Format NUMBER (15)
Indexed? No
May be Null? No |
Note ID of the parent of the current note. |
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 this note. |
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 transaction associated with this note.. The TRX_NUMBER coupled with the TRX_SOURCE uniqely identify the transaction. 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 this note. |
SOURCE_OBJECT_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 object associated with this note. |
SOURCE
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The source object type for this note.
Values: See the Oracle Electronic Techincal Reference Manual for the list of credit request reasons. |
SOURCE_OBJECT_CODE
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the source object type for this note.
Values: See the Oracle Electronic Techincal Reference Manual for the list of credit request reasons.
|
SOURCE_OBJECT_NUMBER
Format VARCHAR2 (40)
Indexed? No
May be Null? No |
The numeric identifier used internally by the BEN Billing and Receivable system to identify the object associated with this note. |
NOTE_TYPE
Format VARCHAR2 (80)
Indexed? No
May be Null? No |
The note type.
Values: See the Oracle Electronic Techincal Reference Manual for the list of credit request reasons. |
NOTE_TYPE_CODE
Format VARCHAR2 (30)
Indexed? No
May be Null? No |
An alphanumberic identifier used to specify the note type.
Values: See the Oracle Electronic Techincal Reference Manual for the list of credit request reasons.
|
NOTE_STATUS
Format VARCHAR2 (1)
Indexed? No
May be Null? No |
This flag determines whether the note is public, private or published outside the organization. |
ENTERED_BY
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
The person who entered the note. |
ENTERED_DATE
Format DATE
Indexed? No
May be Null? No |
The date the note was entered. |
CREATED_BY
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
The person who created the note. |
CREATION_DATE
Format DATE
Indexed? No
May be Null? No |
The date the note was created. |
LAST_UPDATED_BY
Format VARCHAR2 (240)
Indexed? No
May be Null? No |
The person who last modified the note. |
NOTES
Format VARCHAR2 (2000)
Indexed? No
May be Null? No |
The note text. |
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. |