CLEARING DATA Table
XXX
Field Name |
Description |
Data Type |
Length |
|---|---|---|---|
CLEARING_DATE |
Date this transaction cleared. |
DATE |
|
CLEARING_DOCUMENT_NUMBER |
The document number associated with this transaction and its clearing date. |
VARCHAR2 |
10 |
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 |
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 |
DOCUMENT_LINE_ITEM |
Document Line Item Number. |
NUMBER |
|
DOCUMENT_NUMBER |
The number in SAP that uniquely identifies a detailed transaction document. |
VARCHAR2 |
10 |
DUNNING_AREA_KEY |
The key identifying a unique entry in the DUNNING_AREA table; should be used to join this table to others. |
VARCHAR2 |
7 |
LAST_DUNNED_DATE |
This field does not currenly contain up-to-date information and should not be used in reports until further notice |
DATE |
|
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 |