Data Warehouse

IS&T Home >   Data Warehouse

MIT Data Warehouse COMMITMENT HISTORY Table


Cointains commitment information to create views "as of" a certain date, available for dates from July 1999 to present. This table must be joined to the TIME_DAY table, joining the Record_Value_From_Date (use a simple join and select Greater than or Equal) *AND* the Record_Value_Thru_Date (use a simple join and select Less than or Equal) to the Calendar_Date field.


Field Name

Description

Data Type

Length

COMMITMENT_AMOUNT

The dollars committed (set aside) but not yet paid for the line item.

NUMBER

11

COMMITMENT_AMOUNT_LC

XXX

NUMBER

22

COMMITMENT_TYPE_KEY

Key used to join to the COMMITMENT_TYPE table which describes various aspects of the commitment.

VARCHAR2

5

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

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

EXPECTED_DEBIT_DATE

Date when a commitment is expected to be posted.

DATE

8

EXPECTED_DEBIT_FISCAL_PERIOD

Fiscal period when a commitment is expected to be posted.

VARCHAR2

6

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

LOCAL_CURRENCY

XXX

VARCHAR2

5

MATERIAL_GROUP_KEY

Key identifying which Material Group an ordered item belongs to. This field should only be used for linking tables together, not for reporting.

VARCHAR2

9

PLANNED_AMOUNT

Dollar amount planned for this commitment.

NUMBER

22

PLANNED_AMOUNT_LC

XXX

NUMBER

22

PLANNED_QUANTITY

Quantity planned for this commitment (ea, boxes, liters, etc.).

NUMBER

22

RECORD_VALID_FROM_DATE

The date a commitment record is started. Usually the date the commitment was opened. If, however, changes were made to an open commitment this date may reflect the beginning of the altered commitment.

DATE

8

RECORD_VALID_THRU_DATE

The date a commitment record is valid through. Once the commitment is closed, it no longer appears within valid start and through date range.

DATE

8

REFERENCE_ASSIGNMENT_NUMBER

For a requisition or purchase order, the number referring to the cost collector assignment from which the commitment is generated.

NUMBER

22

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_DOCUMENT_TYPE

For a requisition or purchase order, the document type from which the commitment is generated.

VARCHAR2

30

REFERENCE_ITEM_NUMBER

For a requisition or purchase order, the number referring to the line item from which the commitment is generated.

NUMBER

22

SEGMENT_TEXT

Short text description (up to 50 characters) of a financial commitment

VARCHAR2

50

TOTAL_QUANTITY

Outstanding commitment quantity on the COMMITMENT_HISTORY.

NUMBER

11

TRANSACTION_COUNTER

Used to count records within a group on a report. Always contains a value of 1.

NUMBER

1

TRANSACTION_CURRENCY

XXX

VARCHAR2

5

USER_ID

In the Commitment History and Current Commitments tables, the kerberos ID of the person who entered the commitment.

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

WAREHOUSE_LOAD_DATE

The date the record was loaded into the Data Warehouse from the source system.

DATE

8