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

CE_STATEMENT_LINES

Cash ManagementUsed in 3 subject areas23 reporting columns

Cash Management (CE), imported bank statement lines (the raw transactions from the bank).

Primary key: STATEMENT_LINE_ID

Columns

ColumnKeyIn reportsDescription (inferred)
ACCNT_SERVICER_REFAccnt servicer reference.
ADDENDA_TXTAddenda txt.
AMOUNTAmount.
BOOKING_DATEBooking date.
CHECK_NUMBERCheck number.
CLEARING_SYSTEM_REFClearing system reference.
COMM_WAIVER_IND_FLAGIndicator (Y/N) for the comm waiver ind.
CONTRACT_IDENTIFICATIONContract identification.
CUSTOMER_REFERENCECustomer reference.
END_TO_END_IDIdentifier for the end to end.
EXCHANGE_RATEExchange rate.
EXCHANGE_RATE_DATEExchange rate date.
FLOW_INDICATORFlow indicator.
INSTRUCTION_IDENTIFICATIONInstruction identification.
LINE_NUMBERLine number.
ORIG_BANK_ACCOUNT_IDIdentifier for the orig bank account.
RECON_REFERENCERecon reference.
RECON_STATUSStatus of the recon.
REVERSAL_IND_FLAGIndicator (Y/N) for the reversal ind.
SERVICER_STATUSStatus of the servicer.
STATEMENT_LINE_IDPKIdentifier for the statement line.
TRX_AMOUNTTransaction amount.
TRX_TYPEType of transaction.
VALUE_DATEValue date.

4 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 CE_STATEMENT_LINES.

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 CE_STATEMENT_LINES?
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