EXM_EXP_REP_PROCESSING
This table is used to store processing status for an expense report.
Details
-
Schema: FUSION
-
Object owner: EXM
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
EXM_EXP_REP_PROCESSING_PK |
EXP_REP_PROCESSING_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
EXP_REP_PROCESSING_ID | NUMBER | 18 | Yes | Unique identifier of the processing detail of a specific expense report. | |
EXPENSE_REPORT_ID | NUMBER | 18 | Yes | Identifier of the expense report for which status changes are tracked. | |
EVENT | VARCHAR2 | 240 | Yes | Event that triggered an expense report status change, such as approval and audit. | |
EVENT_PERFORMER_ID | VARCHAR2 | 64 | User who initiated the expense report status change event. | ||
EVENT_DATE | DATE | Date when the expense report status change occurred. | |||
APPROVAL_LEVEL | VARCHAR2 | 30 | Order in which the approval notification was sent. | ||
EXPENSE_STATUS_CODE | VARCHAR2 | 30 | Expense report approval status, such as Approved, Pending Manager Approval, or Paid. | ||
AUDIT_CODE | VARCHAR2 | 30 | Audit type for the expense report based on receipt requirements, such as original receipt-based audit and imaged receipt-based audit. | ||
AUDIT_RETURN_REASON_CODE | VARCHAR2 | 30 | Reason why the expense report was returned to the individual during audit. | ||
EXPORT_REJECT_CODE | VARCHAR2 | 30 | Reason for the rejection of the expense report by the payment request creation process. | ||
EXPORT_REQUEST_ID | NUMBER | 18 | Identifier of a specific instance of the expense reimbursement process that processed this report. | ||
RECEIPTS_STATUS_CODE | VARCHAR2 | 30 | Receipt status of an expense report, such as Missing, Required, and Received. | ||
IMAGED_RECEIPTS_STATUS_CODE | VARCHAR2 | 30 | Status of the imaged receipts for an expense report, such as Required, Missing, and Received. | ||
HOLDING_EXPENSE_REPORT_ID | NUMBER | 18 | Identifier of the expense report that is on payment hold, thereby preventing the reimbursement of this expense report. | ||
NOTE_ID | NUMBER | 18 | Identifier of the note that resulted from the status change. | ||
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
EXM_EXP_REP_PROCESSING | exm_expense_reports | EXPENSE_REPORT_ID |
EXM_EXP_REP_PROCESSING | exm_expense_reports | HOLDING_EXPENSE_REPORT_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
EXM_EXP_REP_PROCESSING_N1 | Non Unique | Default | EXPENSE_REPORT_ID |
EXM_EXP_REP_PROCESSING_U1 | Unique | Default | EXP_REP_PROCESSING_ID |