Table of Contents

BYOBI Data Dictionary - Item Visibility

Abigail Briggs Updated by Abigail Briggs

Overview

The Item Visibility data available through BYOBI provides information about the visibility settings applied to individual items at both Company and Business Unit level.

The table DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY contains visibility information that can be used to report on whether items are selected, deselected or preferred by a buyer organisation.

Visibility settings can be applied at different levels, including supplier/category level and individual item level. Where a more specific setting applies, it takes precedence over a broader setting.

This guide explains the available data fields, how visibility settings interact, and how to join Item Visibility data to Product & Price data for reporting.

Understanding Item Visibility

Visibility Status Types

There are two types of visibility setting to consider:

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.

Example: If a buyer deselects the Stationery category, items within that category will generally inherit a Deselected status. If the buyer subsequently selects an individual item within that category, the item-level setting overrides the inherited category setting.

The same principle applies to individual item settings of Item Deselected and Item Preferred.

Company and Business Unit status

Visibility settings can be applied at Company or Business Unit level.

Where a Business Unit-specific setting has been applied to an item, it takes precedence over the Company-level setting for that Business Unit.

For example:

Company-level setting

Business Unit setting

Effective setting

Selected

No specific setting

Selected

Deselected

Selected

Selected

Selected

Deselected

Deselected

Preferred

No specific setting

Preferred

These examples illustrate the precedence rule, assuming the settings shown are applicable to the item and the absence of a Business Unit setting allows the Company-level setting to apply.

Item-level overrides
Individual item overrides

An individual item setting can override an inherited supplier/category-level setting.

For example:

Inherited supplier/category setting

Individual item setting

Result

Deselected

Item Selected

Selected

Selected

Item Deselected

Deselected

Selected

Item Preferred

Preferred

When determining the effective visibility of an item, consider both the organisational scope and the level at which the visibility setting was applied.

The general precedence rules are:

  1. Business Unit-specific setting: takes precedence over the Company-level setting where a Business Unit setting exists.
  2. Individual item setting: takes precedence over the inherited supplier/category-level setting for that item.
  3. Inherited supplier/category setting: applies where no more specific item setting overrides it.

These rules should be applied using the available data fields and the actual representation of settings in the source data. A missing or blank value should not automatically be interpreted as Selected or Deselected without confirming the expected default behaviour.

Data fields

The DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY table contains the following 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

The DIM_PURCHASING_PRODUCT_AND_PRICE table contains product and price information.

To report on item visibility alongside product information, join DIM_PURCHASING_PRODUCT_AND_PRICE to DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY.

The common joining field is ITEM_ID.

Join condition

DIM_PURCHASING_PRODUCT_AND_PRICE.ITEM_ID
    = DIM_PURCHASING_BUYER_BU_ITEM_LEVEL_VISIBILITY.ITEM_ID

This enables reporting on product attributes, such as:

  • Supplier
  • Product description
  • Price
  • UNSPSC classification
  • Company and Business Unit visibility settings

How did we do?

BYOBI Data Dictionary - Product & Price

Contact