POZ_SUPP_REQUESTS

ProcurementUsed in 1 subject areas18 reporting columns

Procurement Suppliers (POZ).

Likely primary key: SUPP_REQUEST_ID (inferred from Oracle naming conventions — verify against Tables & Views)

Columns

Column	Key	In reports	Description (inferred)
ACTION_BY_PERSON_ID		●	Identifier for the action by person.
ACTION_DATE		●	Action date.
CHANGED_ADDRESSES_FLAG		●	Indicator (Y/N) for the changed addresses.
CHANGED_BANK_ACCOUNTS_FLAG		●	Indicator (Y/N) for the changed bank accounts.
CHANGED_BUS_CLASS_DETAILS_FLAG		●	Indicator (Y/N) for the changed bus class details.
CHANGED_CONTACTS_FLAG		●	Indicator (Y/N) for the changed contacts.
CHANGED_ORG_DETAILS_FLAG		●	Indicator (Y/N) for the changed organization details.
CHANGED_PAYMENT_METHOD_FLAG		●	Indicator (Y/N) for the changed payment method.
CHANGED_PROD_SERV_FLAG		●	Indicator (Y/N) for the changed prod serv.
CHANGED_SITES_FLAG		●	Indicator (Y/N) for the changed sites.
CHANGED_TAX_DETAILS_FLAG		●	Indicator (Y/N) for the changed tax details.
CHANGED_USER_ACCOUNT_FLAG		●	Indicator (Y/N) for the changed user account.
CHANGE_DESCRIPTION		●	Description of the change.
CHANGE_REQ_NUMBER		●	Change req number.
CHANGE_REQ_SUBMISSION_DATE		●	Change req submission date.
REQUEST_SOURCE_CODE		●	Code identifying the request source.
REQUEST_STATUS_CODE		●	Code identifying the request status.
SUPP_REQUEST_ID	PK?	●	Identifier for the supplier request.

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

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

We ship parameterized SQL, BICC config, and dbt models you own.