Analytics Catalog/Data dictionary/EXM_EXPENSE_REPORTS
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

EXM_EXPENSE_REPORTS

SharedUsed in 1 subject areas16 reporting columns

Source object in the Oracle Fusion data model.

Primary key: EXPENSE_REPORT_ID
Joins (inferred from key columns): PAYMENT_METHOD_CODE → IBY_PAYMENT_METHODS_B

Columns

ColumnKeyIn reportsDescription (inferred)
AUDIT_CODE●Code identifying the audit.
AUDIT_RETURN_REASON_CODE●Code identifying the audit return reason.
CASH_EXPENSE_PAID_DATE●Cash expense paid date.
EXPENSE_REPORT_DATE●Expense report date.
EXPENSE_REPORT_IDPK○Identifier for the expense report.
EXPENSE_REPORT_NUM●Expense report number.
EXPENSE_REPORT_TOTAL●Expense report total.
EXPENSE_STATUS_CODE●Code identifying the expense status.
FINAL_APPROVAL_DATE●Final approval date.
IMAGED_RECEIPTS_STATUS_CODE●Code identifying the imaged receipts status.
PAYMENT_METHOD_CODE●Code identifying the payment method.
PURPOSE●Purpose.
RECEIPTS_RECEIVED_DATE●Receipts received date.
RECEIPTS_STATUS_CODE●Code identifying the receipts status.
REIMBURSEMENT_CURRENCY_CODE●Currency code for the reimbursement.
REPORT_SUBMIT_DATE●Report submit date.
SHORTPAY_TYPE_CODE●Code identifying the shortpay type.

2 reports read from this table

Change a column here and these are the reports that move with it, the blast radius for any change to EXM_EXPENSE_REPORTS.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for EXM_EXPENSE_REPORTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern