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

Columns

Column	Key	In reports	Description (inferred)
AMOUNT_REMAINING		●	Amount remaining.
DISCOUNT_AMOUNT_AVAILABLE		●	Discount amount available.
DISCOUNT_DATE		●	Discount date.
DUE_DATE		●	Due date.
GROSS_AMOUNT		●	Gross amount.
HOLD_DATE		●	Hold date.
HOLD_FLAG		●	Indicator (Y/N) for the hold.
IBY_HOLD_REASON		●	Iby hold reason.
INVOICE_ID	PK	○	Identifier for the invoice.
PAYMENT_METHOD_CODE		●	Code identifying the payment method.
PAYMENT_NUM	PK	●	Payment number.
PAYMENT_PRIORITY		●	Payment priority.
PAYMENT_STATUS_FLAG		●	Indicator (Y/N) for the payment status.
REMITTANCE_MESSAGE1		●	Remittance message1.
REMITTANCE_MESSAGE2		●	Remittance message2.
REMITTANCE_MESSAGE3		●	Remittance message3.
REMIT_TO_ADDRESS_NAME		●	Name of the remit to address.
REMIT_TO_SUPPLIER_NAME		●	Name of the remit to supplier.
SECOND_DISCOUNT_DATE		●	Second discount date.
SECOND_DISC_AMT_AVAILABLE		●	Second disc amount available.
THIRD_DISCOUNT_DATE		●	Third discount date.
THIRD_DISC_AMT_AVAILABLE		●	Third disc amount available.

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

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.