BYOBI Data Dictionary - Item Visibility

Abigail Briggs Updated by Abigail Briggs

Item Visibility Data

The Item Visibility data available through BYOBI provides the visibility status of individual items at both Company and Business Unit level.

The table DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY contains the status that has been applied to an item and allows reporting to understand whether an item is Selected, Deselected or Preferred.

The visibility status is determined by a hierarchy. Where a status has been set specifically at Business Unit level, this takes precedence over the Company-level status.

Visibility hierarchy

There are two types of status that can be applied to an item:

Status Type

Values

Description

Supplier / Category-level status

Selected, Deselected, Preferred

The default status applied to items through a supplier or category-level selection. For example, a buyer may deselect the Stationery category, which means items within that category inherit a Deselected status.

Item-level status

Item Selected, Item Deselected, Item Preferred

A status specifically applied by the buyer to an individual item. This overrides the supplier/category-level status for that item.

Company and Business Unit status

The table provides visibility at both Company and Business Unit level.

The Business Unit status takes precedence over the Company status where a Business Unit-specific status has been set.

Item-level overrides

An item can also have an individual buyer-level override.

For example, if a buyer has configured the Stationery category as Deselected, the items within that category will generally inherit the Deselected status.

However, if the buyer then individually selects a particular item, that item will have an Item Selected status. This item-level setting overrides the inherited Deselected status.

The same principle applies to Item Deselected and Item Preferred.

Therefore, when determining the effective status of an item, the hierarchy should be considered:

1. Business Unit item-level status ↓ 2. Company item-level status ↓ 3. Supplier/category-level status

Where a more specific status exists, it overrides the less specific status.

Data fields

Data Field

Description

_UPDATED_AT

Date/time the visibility record was last updated

BUYER_BUSINESS_UNIT_ITEM_VISIBILITY

The item's visibility status for the specific Business Unit. Where populated, this takes precedence over the Company-level visibility status.

BUYER_BUSINESS_UNIT_NAME

Name of the Business Unit to which the visibility status applies

BUYER_COMPANY_ITEM_VISIBILITY

The item's visibility status at Company level

BUYER_ID

Unique identifier for the buyer/customer organisation

COMPANY_ID

Unique identifier for the buyer company

CUSTOMER_REF

Customer-specific reference associated with the item

ITEM_ID

Unique identifier for the item. This is the joining key to the Product & Price data

ORGANISATION_REF

Reference identifying the organisation associated with the record

Linking to Product & Price data

To combine Item Visibility data with product information, link DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY to DIM_PURCHASING_PRODUCT_AND_PRICE using ITEM_ID.

DIM_PURCHASING_PRODUCT_AND_PRICE.ITEM_ID = DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY.ITEM_ID

This allows you to report on the product itself — such as supplier, product description, price and UNSPSC — alongside the item's visibility status for the buyer and/or Business Unit.

Important: When reporting on the effective visibility of an item, do not simply use the Company-level status. Check whether a Business Unit-specific status exists first, as this will override the Company-level status.

How did we do?

BYOBI Data Dictionary - Product & Price

Contact