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_CODEIBY_PAYMENT_METHODS_B

Columns

ColumnKeyIn reportsDescription (inferred)
AUDIT_CODECode identifying the audit.
AUDIT_RETURN_REASON_CODECode identifying the audit return reason.
CASH_EXPENSE_PAID_DATECash expense paid date.
EXPENSE_REPORT_DATEExpense report date.
EXPENSE_REPORT_IDPKIdentifier for the expense report.
EXPENSE_REPORT_NUMExpense report number.
EXPENSE_REPORT_TOTALExpense report total.
EXPENSE_STATUS_CODECode identifying the expense status.
FINAL_APPROVAL_DATEFinal approval date.
IMAGED_RECEIPTS_STATUS_CODECode identifying the imaged receipts status.
PAYMENT_METHOD_CODECode identifying the payment method.
PURPOSEPurpose.
RECEIPTS_RECEIVED_DATEReceipts received date.
RECEIPTS_STATUS_CODECode identifying the receipts status.
REIMBURSEMENT_CURRENCY_CODECurrency code for the reimbursement.
REPORT_SUBMIT_DATEReport submit date.
SHORTPAY_TYPE_CODECode 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. You can't join across them in OTBI, the owned conformed model joins them on shared 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