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

AP_PAYMENT_SCHEDULES_ALL

PayablesUsed in 2 subject areas21 reporting columns

Payables (AP), payment schedules. One row per scheduled payment for each invoice, the anchor for AP aging.

Primary key: INVOICE_ID, PAYMENT_NUM
Joins (inferred from key columns): INVOICE_IDAP_INVOICES_ALL · PAYMENT_METHOD_CODEIBY_PAYMENT_METHODS_B

Columns

ColumnKeyIn reportsDescription (inferred)
AMOUNT_REMAININGAmount remaining.
DISCOUNT_AMOUNT_AVAILABLEDiscount amount available.
DISCOUNT_DATEDiscount date.
DUE_DATEDue date.
GROSS_AMOUNTGross amount.
HOLD_DATEHold date.
HOLD_FLAGIndicator (Y/N) for the hold.
IBY_HOLD_REASONIby hold reason.
INVOICE_IDPKIdentifier for the invoice.
PAYMENT_METHOD_CODECode identifying the payment method.
PAYMENT_NUMPKPayment number.
PAYMENT_PRIORITYPayment priority.
PAYMENT_STATUS_FLAGIndicator (Y/N) for the payment status.
REMITTANCE_MESSAGE1Remittance message1.
REMITTANCE_MESSAGE2Remittance message2.
REMITTANCE_MESSAGE3Remittance message3.
REMIT_TO_ADDRESS_NAMEName of the remit to address.
REMIT_TO_SUPPLIER_NAMEName of the remit to supplier.
SECOND_DISCOUNT_DATESecond discount date.
SECOND_DISC_AMT_AVAILABLESecond disc amount available.
THIRD_DISCOUNT_DATEThird discount date.
THIRD_DISC_AMT_AVAILABLEThird disc amount available.

10 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 AP_PAYMENT_SCHEDULES_ALL.

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 AP_PAYMENT_SCHEDULES_ALL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
Payables does not tie · Three-way match does not tie · The export ceiling