Oracle Fusion · Data dictionary
POZ_SITE_ASSIGNMENTS_ALL_M
ProcurementUsed in 2 subject areas7 reporting columns
Procurement Suppliers (POZ).
Primary key: VENDOR_SITE_ID, BU_ID
Joins (inferred from key columns): BU_ID → FUN_ALL_BUSINESS_UNITS_V · VENDOR_SITE_ID → POZ_SUPPLIER_SITES_ALL_M
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ALLOW_AWT_FLAG | ● | Indicator (Y/N) for the allow awt. | |
| ASSIGNMENT_ID | ● | Identifier for the assignment. | |
| BU_ID | PK | ○ | Identifier for the business unit. |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| INACTIVE_DATE | ● | Inactive date. | |
| LAST_UPDATED_BY | ● | User who last updated the row. | |
| LAST_UPDATE_DATE | ● | Date and time the row was last updated (the incremental-extract key). | |
| VENDOR_SITE_ID | PK | ○ | Identifier for the vendor site. |
1 report read from this table
Change a column here and these are the reports that move with it, the blast radius for any change to POZ_SITE_ASSIGNMENTS_ALL_M.
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 POZ_SITE_ASSIGNMENTS_ALL_M?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table