SPONSOR BILLING DETAIL Table
Contains information about Sponsor Billing.
Field Name |
Description |
Data Type |
Length |
|---|---|---|---|
ACTUAL_AMOUNT |
The paid dollar amount of the line item. |
NUMBER |
11 |
ACTUAL_AMOUNT_LC |
XXX |
NUMBER |
22 |
ALLOCATION_NUMBER |
Allocation number for special G/L accounts. Only customer and vendor line items for which a special G/L indicator has been entered are affected. |
VARCHAR2 |
18 |
ALTERNATIVE_ACCOUNT_NUMBER |
A ten digit number, the last three digits of which correspond to the MIT classic system's "object code", now replaced by SAP G/L accounts. |
VARCHAR2 |
10 |
BLOCKED_PAYMENT_TEXT |
Text associated with the Blocked Payment Indicator. Explains why a line item is blocked for payment or tells when it is free for payment. |
VARCHAR2 |
20 |
CLEARING_DATE |
Date this transaction cleared. |
DATE |
8 |
CLEARING_DOCUMENT_NUMBER |
The document number associated with this transaction and its clearing date. |
VARCHAR2 |
10 |
CLEARING_ENTRY_DATE |
The date the clearing transaction was entered into SAP. |
DATE |
8 |
COMMITMENT_ITEM |
In SAP's FM module, expenses are classified by "commitment item", not G/L account. Each G/L account in SAP's CO module maps to a "commitment item" in the FM module. There are many fewer commitment items that G/L accounts. FM's commitment items represent a more summarized view of expense types. |
VARCHAR2 |
14 |
COMPANY_CODE |
Shows to which "company" in SAP a cost collector is attached. MIT uses separate "companies" in SAP to differentiate financial transactions for different legal entities with differing business rules or reporting requirements. There are currently three company codes, "CUR" for main campus, "TECR" for MIT's alumni magazine, Technology Review, and "LCP1" for Lincoln Laboratory. |
VARCHAR2 |
4 |
COST_COLLECTOR_FY_KEY |
Key used to join historical Cost Collector tables and a fact table (Balances, Balances by Fiscal Period, Summary Statement Detail) when you want to bring in cost collector data as it was at the end of fiscal year of the fact data. For the current fiscal year, the most recent data will be brought in. |
VARCHAR2 |
12 |
COST_COLLECTOR_KEY |
Key used to join the Cost Collector to the financial transaction, and to get the master data that were current at the time of the transaction. This field should only be used for joining data, NOT for reporting. |
VARCHAR2 |
12 |
CUSTOMER_KEY |
This key is to be used to join the FINANCIAL_DETAIL and the PROJECT or PROJECT_OSP tables. This field should only be used for linking tables together, NOT for reporting. |
VARCHAR2 |
11 |
DEBIT_CREDIT_INDICATOR |
A one-character flag that identifies whether the line item is a debit or credit. Values are D or C. |
VARCHAR2 |
1 |
DELIVERY_COMPLETE_INDICATOR |
Flag identifying whether or not a purchase is complete (Value: null or X). |
VARCHAR2 |
1 |
DOCUMENT_CURRENCY |
Tells what currency is used to pay for the line item values: USD=US Dollars. |
VARCHAR2 |
5 |
DOCUMENT_DATE |
The date entered by the user when creating the document. Generally the date the financial transaction occurred, but see also the definition for document line date. |
DATE |
8 |
DOCUMENT_ENTRY_DATE |
The date the document was entered into SAP. |
DATE |
8 |
DOCUMENT_LAST_CHANGE_DATE |
he date the document was last modified in SAP. |
DATE |
8 |
DOCUMENT_LINE_DATE |
If not blank, the date the financial transaction occurred. If blank, the document date is the date the financial transaction occurred. |
date |
8 |
DOCUMENT_LINE_ITEM |
Document Line Item Number. |
NUMBER |
3 |
DOCUMENT_NUMBER |
The number in SAP that uniquely identifies a detailed transaction document. |
VARCHAR2 |
10 |
DOCUMENT_TYPE_KEY |
Key used to join the Document Type to the financial transaction, and to get the master data that were current at the time of the transaction. This field should only be used for joining data, NOT for reporting. |
VARCHAR2 |
3 |
DUNNING_AREA_KEY |
The key identifying a unique entry in the DUNNING_AREA table; should be used to join this table to others. |
VARCHAR2 |
3 |
FINANCIAL_DETAIL_KEY |
XXX |
VARCHAR2 |
17 |
FUND_CENTER_KEY |
Key used only for joining the FINANCIAL_DETAIL table with other tables, NOT for reporting. |
VARCHAR2 |
16 |
FUND_KEY |
Key is used only for joining the FUND table with the FINANCIAL_DETAIL table, NOT for reporting. |
VARCHAR2 |
10 |
GL_ACCOUNT_KEY |
Key used to join the GL_ACCOUNT to the financial transaction, and to get the master data that were current at the time of the transaction. This field should only be used for joining data, NOT for reporting. |
VARCHAR2 |
10 |
INTERCOMPANY_TRANSACTION_ID |
XXX |
VARCHAR2 |
16 |
LINE_ITEM_TEXT |
The short description of the line item. Also appears on the SAP DTR for the cost collector associated with this financial detail. |
VARCHAR2 |
50 |
LOCAL_CURRENCY |
XXX |
VARCHAR2 |
5 |
MANUAL_BLOCKING_INDICATOR |
Flag signaling when a purchasing document line item is blocked for payment (Values: Y or N). |
VARCHAR2 |
1 |
MATERIAL_GROUP_CODE |
XXX |
VARCHAR2 |
9 |
OFFSET_COST_COLLECTOR_KEY |
"Offset Cost Collector" is a field referring to a WBS element subject to Underrecovery of F&A costs. The Offset Cost Collector Key in the Financial Detail table can be joined to the Cost Collector Key in Cost Collector tables in queries related to tracking underrecovery of F&A costs. It is used only for joining tables, not on the Request line. |
VARCHAR2 |
12 |
ORIGINAL_PROCEDURE_CODE |
XXX |
VARCHAR2 |
5 |
PARKED_BY_USER_NAME |
Kerberos ID of the user who "parked" the document |
VARCHAR2 |
12 |
POSTING_DATE |
The date the financial document was posted in SAP. Effective date of posting, not actual date. For example, a costing sheet posting could be generated in early July, but posted to June 30, if so specified by an authorized users. |
DATE |
8 |
POSTING_KEY |
Key required by SAP for each document line item, indicating the type of posting represented in the line item. "Posting Key" is the description for "Posting Key Code". |
VARCHAR2 |
3 |
POSTING_KEY_CODE |
2 digit code identifing the type of posting. Example: 09 - Security Deposit, 08 - Payment Clearing, 09 - Pledge, 09 - Special G/L Debit, 09 - Interest Due, 11 - Credit Memo, 40 - Debit, 50 - Credit, etc. |
VARCHAR2 |
2 |
PO_LINE_ITEM_TEXT |
XXX |
VARCHAR2 |
50 |
PO_QUANTITY |
The ordered quantity on a PO line item. |
NUMBER |
22 |
PO_UNIT_OF_MEASURE |
Identifies the unit by which the ordered quantity of a Purchase Order Line Item is measured. Example: each, box, dozen, gallon, case. |
VARCHAR2 |
3 |
PURCHASE_ORDER_ACCT_ASSIGNMENT |
XXX |
NUMBER |
22 |
PURCHASE_ORDER_ITEM |
Number identifying a line item associated with a purchase order. |
NUMBER |
5 |
PURCHASE_ORDER_NUMBER |
Identifies the purchase order. In SAP this is the Document Number for a Purchasing Document. |
VARCHAR2 |
10 |
REFERENCE_DOCUMENT_NUMBER |
For FINANCIAL_DETAIL: The reference number of the associated financial document. A value of %N means that there is no backup for the journal voucher. For COMMITMENT tables, the document number from which the commitment was generated. |
VARCHAR2 |
16 |
REFERENCE_TEXT |
The document header text associated with a journal document. Not always completed by the JV document creator. |
VARCHAR2 |
25 |
REVERSE_DOCUMENT_NUMBER |
The document number associated withreversing this transaction. |
VARCHAR2 |
10 |
REVERSE_DOCUMENT_YEAR |
The year of the reversed transaction. |
VARCHAR2 |
4 |
SPECIAL_GL_INDICATOR |
XXX |
VARCHAR2 |
1 |
SPECIAL_GL_TRANS_TYPE |
The special G/L transaction type groups together similar special G/L transactions. |
VARCHAR2 |
1 |
TIME_MONTH_KEY |
Key used only for joining the TIME_MONTH table to other tables, NOT for reporting. |
VARCHAR2 |
6 |
TRANSACTION_CODE |
The code assigned to each transaction by SAP. It may be more meaningful to use the document type. |
VARCHAR2 |
4 |
TRANSACTION_COUNTER |
Used to count records within a group on a report. Always contains a value of 1. |
NUMBER |
1 |
USER_NAME |
Kerberos ID of the person who entered the purchasing financial detail record in SAP, usually the purchasing agent |
VARCHAR2 |
12 |
VENDOR_KEY |
Key identifying an entry in the VENDOR master table. This field should only be used for linking tables together, not for reporting. |
VARCHAR2 |
11 |
VENDOR_NAME |
In the Financial Detail Table, the Vendor to whom a Purchase Order was issued. |
VARCHAR2 |
144 |
WAREHOUSE_LOAD_DATE |
The date the record was loaded into the Data Warehouse from the source system. |
DATE |
8 |