Supplier Site Inactivation Report

Payables

Supplier sites that are candidates for inactivation — no transactions in a defined period, or already inactive but still referenced — so procurement can clean up the supplier master and cut duplicate-payment risk.

Sample build of the Supplier Site Inactivation Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Sample

Months

Sample

2,810

Sites reviewed

240

Dormant 12 mo

Inactive w/ open AP

Supplier	Site	Last Activity	Open Balance	Status	Recommendation
Acme Industrial	Sample	Sample	$1,240,500.00	Open	Sample
Northwind Trading	—	—	$842,150.75	Posted	—
Globex Holdings	Sample	Sample	$96,400.00	Validated	Sample
Initech LLC	—	—	$1,005,233.10	Open	—
Umbrella Corp	Sample	Sample	$58,720.40	Paid	Sample
Acme Industrial	Sample	Sample	$1,240,500.00	Open	Sample

AI Analyst · active

reading

The report reads supplier sites with their last AP activity and open balance.

flag

Six sites are inactive but still carry an open AP balance — they can't be paid through a normal run while inactive, so those payments stall.

root cause & next step

Reactivate to pay then re-inactivate, or move the balance to an active site; an inactive site with open AP is a payment dead-end.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.

SQL data set · genericized · parameterized · no hardcoded segments

Show / hide SQL

SELECT 
SUPPLIER_NAME,
SUPPLIER_NUMBER,
SUPPLIER_SITE_ID,
SUPPLIER_SITE_NAME,
SOURCE_SYSTEM,
SUPPLIER_TYPE,
PROCUREMENT_BU,
LE_VALUE,
LE_NAME,
SUPPLIER_CREATION_DATE,
LAST_TRX_DATE,
MONTHS_BETWEEN(SYSDATE, LAST_TRX_DATE) Months_since_last_trx,
Days_Since_Active,
START_DATE_ACTIVE

,STATUS

FROM(
SELECT 
PSV.VENDOR_NAME SUPPLIER_NAME,
PSV.SEGMENT1 SUPPLIER_NUMBER,
PSSM.VENDOR_SITE_ID SUPPLIER_SITE_ID,
PSSM.VENDOR_SITE_CODE SUPPLIER_SITE_NAME,
PSSM.ATTRIBUTE5 SOURCE_SYSTEM,
FLV2.MEANING SUPPLIER_TYPE,
HOU.NAME PROCUREMENT_BU,
GCC.SEGMENT1 LE_VALUE,
FVL.DESCRIPTION LE_NAME,
PSV.CREATION_DATE SUPPLIER_CREATION_DATE,
MAX(AIA.INVOICE_DATE) LAST_TRX_DATE,
NVL(PSV.START_DATE_ACTIVE,PSV.CREATION_DATE) START_DATE_ACTIVE,
(SYSDATE - NVL(PSV.START_DATE_ACTIVE,PSV.CREATION_DATE)) Days_Since_Active

,FLV.MEANING STATUS

 FROM 
POZ_SITE_ASSIGNMENTS_ALL_M PSSA,
POZ_SUPPLIER_SITES_ALL_M PSSM,
POZ_SUPPLIERS_V PSV,
GL_CODE_COMBINATIONS GCC,
HR_OPERATING_UNITS HOU,
FND_FLEX_VALUES_VL FVL,
AP_INVOICES_ALL AIA

,HZ_PARTY_SITES HPS
,FND_LOOKUP_VALUES FLV
,FND_LOOKUP_VALUES FLV2
WHERE 1=1
AND PSSM.VENDOR_SITE_ID = PSSA.VENDOR_SITE_ID
AND PSSM.PRC_BU_ID = PSSA.BU_ID
AND PSSM.VENDOR_ID = PSV.VENDOR_ID
AND GCC.CODE_COMBINATION_ID = PSSA.ACCTS_PAY_CODE_COMBINATION_ID
AND FVL.FLEX_VALUE = GCC.SEGMENT1
AND HOU.ORGANIZATION_ID = PSSM.PRC_BU_ID
AND UPPER(FVl.VALUE_CATEGORY) = 'ENTITY VALUE SET' --'CUSTOM_ENTITY_VALUE_SET'
AND AIA.VENDOR_ID(+) = PSV.VENDOR_ID

AND HPS.PARTY_SITE_ID=PSSM.PARTY_SITE_ID
AND FLV.LOOKUP_CODE=HPS.STATUS
AND FLV.LOOKUP_TYPE='HZ_STATUS'
AND FLV.LANGUAGE=USERENV('LANG')
AND FLV2.LOOKUP_CODE=PSV.VENDOR_TYPE_LOOKUP_CODE
AND FLV2.LOOKUP_TYPE='POZ_VENDOR_TYPE'
AND FLV2.LANGUAGE=USERENV('LANG')

--Parameters
--AND ((COALESCE(null,:P_BU) IS NULL) OR (HOU.NAME IN (:P_BU)))
AND (HOU.ORGANIZATION_ID IN (:P_BU) OR 'All' IN ('All'||:P_BU))

GROUP BY
PSV.VENDOR_NAME,
PSV.SEGMENT1,
PSSM.VENDOR_SITE_ID,
--HPS.PARTY_SITE_NAME,
PSSM.VENDOR_SITE_CODE,
PSSM.ATTRIBUTE5 ,
FLV2.MEANING,
HOU.NAME,
GCC.SEGMENT1,
FVL.DESCRIPTION,
PSV.CREATION_DATE,
NVL(PSV.START_DATE_ACTIVE,PSV.CREATION_DATE)
, FLV.MEANING)
WHERE 1=1
--Parameters
AND MONTHS_BETWEEN(SYSDATE, LAST_TRX_DATE) > :P_MONTHS
AND Days_Since_Active > 90
ORDER BY LAST_TRX_DATE DESC

:P_BU :P_MONTHS

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

●— fact → dimension join

Element	Type	Definition
POZ_SUPPLIER_SITES_ALL_M	dimension	dimension
POZ_SUPPLIERS_V	dimension	dimension
AP_INVOICES_ALL	dimension	dimension
HR_OPERATING_UNITS	dimension	dimension
Open Balance	measure	measure

Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.

How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →

See the complete model

How this report's fact and dimensions fit the full picture, via conformed keys.

Payables data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

Table	Reporting columns	Subject areas
POZ_SITE_ASSIGNMENTS_ALL_M	7	2
POZ_SUPPLIER_SITES_ALL_M	179	56
POZ_SUPPLIERS_V	2	24
AP_INVOICES_ALL	63	15
HR_OPERATING_UNITS	Setup / configuration table — joined for reference, not exposed for analytics

Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.