PARK TX PAYMENT Table
XXX
Field Name |
Description |
Data Type |
Length |
|---|---|---|---|
ACCOUNTING_DOCUMENT_NUMBER |
XXX |
VARCHAR2 |
10 |
ADJ_ITEM |
XXX |
VARCHAR2 |
4 |
AMOUNT_REQUESTED |
XXX |
NUMBER |
9,2 |
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_OBJECT |
a seven digit number used to categorize the costs and revenues associated with a particular project or activity at MIT; The terms cost object and cost collector are used interchangeably. |
VARCHAR2 |
12 |
CREATED_AT |
XXX |
VARCHAR2 |
6 |
CREATED_BY |
User account or user name of the person who created the record. |
VARCHAR2 |
12 |
CREATED_ON |
XXX |
DATE |
|
CURRENCY_KEY |
Key used to join to the LIBRARY_CURRENCY table. This field should only be used for joining data, NOT for reporting. |
VARCHAR2 |
5 |
CYBERSOURCE_AUTH_CODE |
XXX |
VARCHAR2 |
16 |
CYBERSOURCE_AUTH_DATE |
XXX |
DATE |
|
CYBERSOURCE_AUTH_REASON_CD |
XXX |
VARCHAR2 |
3 |
CYBERSOURCE_AUTH_RECON_CD |
XXX |
VARCHAR2 |
16 |
CYBERSOURCE_AUTH_TIME |
XXX |
VARCHAR2 |
6 |
CYBERSOURCE_AVS_CODE |
XXX |
VARCHAR2 |
1 |
CYBERSOURCE_CAPTURE_DATE |
XXX |
DATE |
|
CYBERSOURCE_CAPTURE_REASON_CD |
XXX |
VARCHAR2 |
3 |
CYBERSOURCE_CAPTURE_RECON_CD |
XXX |
VARCHAR2 |
16 |
CYBERSOURCE_CAPTURE_TIME |
XXX |
VARCHAR2 |
6 |
CYBERSOURCE_DECISION |
XXX |
VARCHAR2 |
1 |
CYBERSOURCE_MERCHANT_ID |
XXX |
VARCHAR2 |
16 |
CYBERSOURCE_MERCHANT_REF |
XXX |
VARCHAR2 |
60 |
DEPARTMENT_CODE |
Code identifying an academic department, eg. 18 for "Mathematics", 6 for "Electrical Eng & Computer Sci". In the Alumni's tables, the department codes used are different from those used in MITSIS. |
VARCHAR2 |
4 |
DETAIL_CODE |
XXX |
VARCHAR2 |
4 |
EFFECTIVE_DATE |
In the COST COLLECTOR table: this represents the effective date or starting date of the fund cost collector. In the ASA OFFICER DETAIL table this is the starting date of the tenure of the officer. |
DATE |
|
EXPORT_STATUS |
XXX |
VARCHAR2 |
1 |
FISCAL_YEAR |
The 4 digit year. The fiscal year at MIT runs from July 1st through June 30th. (e.g.: June 30, 1997 would be fiscal year 1997, July 1, 1997 would be fiscal year 1998) |
VARCHAR2 |
4 |
INFO_TYPE |
XXX |
VARCHAR2 |
4 |
IS_DEGREE_CANDIDATE |
A flag indicates whether the student is a degree candidate for the next degree award term. Y (Yes), N (No). |
VARCHAR2 |
1 |
IS_ELIGIBLE_REG |
XXX |
VARCHAR2 |
1 |
IS_ENROLL_OK |
XXX |
VARCHAR2 |
1 |
IS_FULLY_APPLIED |
XXX |
VARCHAR2 |
1 |
MIT_ID |
MIT ID number of the person. Use this field to join with other tables containing data about people at MIT. |
VARCHAR2 |
9 |
PARK_PAYMENT_METHOD_KEY |
XXX |
VARCHAR2 |
1 |
PARK_PAYMENT_STATUS_KEY |
XXX |
VARCHAR2 |
1 |
PAYMENT_AMOUNT |
XXX |
NUMBER |
9,2 |
PAYMENT_BATCH |
XXX |
VARCHAR2 |
32 |
PAYMENT_BEGIN_DATE |
XXX |
DATE |
|
PAYMENT_END_DATE |
XXX |
DATE |
|
PAYROLL_PERIOD |
XXX |
VARCHAR2 |
2 |
PAYROLL_YEAR |
XXX |
VARCHAR2 |
4 |
PAY_DATE |
XXX |
DATE |
|
PERSONNEL_NUMBER |
XXX |
VARCHAR2 |
8 |
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 |
|
PROCESSOR_RESPONSE_CD |
XXX |
VARCHAR2 |
3 |
REQUEST_ID |
ASA Request Identification Number |
VARCHAR2 |
22 |
SA_DESCRIPTION |
XXX |
VARCHAR2 |
128 |
SA_ERROR |
XXX |
VARCHAR2 |
1 |
SA_ERROR_MESSAGE |
XXX |
VARCHAR2 |
128 |
SA_FILENAME |
XXX |
VARCHAR2 |
128 |
SA_REVERSAL |
XXX |
VARCHAR2 |
1 |
STUDENT_NAME |
XXX |
VARCHAR2 |
128 |
TERM_CODE |
** For FINANCIAL DATA: the Term Code identifies the status of the cost collector. Blank - open for charges between start and end dates. Term Code = 1 - Closed. Pre-end date charges allowed. Term Code = 2 - No longer in use. Term Code = 3 - Terminated. Charges not allowed. ** For STUDENT DATA: the Term Code identifies one of the terms in an academic year; for example: 1999FA==>Fall Term of the 1998-99 academic year, and 1999SP==>Spring Term of the 1998-99 academic year. |
VARCHAR2 |
10 |
TRANSACTION_ID |
XXX |
VARCHAR2 |
16 |
TRANSACTION_NUMBER |
XXX |
VARCHAR2 |
8 |
UPDATED_AT |
XXX |
VARCHAR2 |
6 |
UPDATED_BY |
XXX |
VARCHAR2 |
12 |
UPDATED_ON |
XXX |
DATE |
|
WAGE_TYPE |
wage type text of the amount, e.g., work, vacation, sick leave, health plan deduction, etc. There are hundreds of wage types; only those most likely to be used for reporting are in the data warehouse. |
VARCHAR2 |
4 |
WAREHOUSE_LOAD_DATE |
The date the record was loaded into the Data Warehouse from the source system. |
DATE |