Configuring for category 1 and 2

An organization administrator can configure Envizi™ Supply Chain Intelligence to capture and report on Scope 3 Category 1 and 2 data within the same instance. The GHG protocol calculation logic is fundamentally the same for both categories and Envizi Supply Chain Intelligence can be configured to calculate both simultaneously.

Depending on the requirements, there are two main approaches to capturing Category 1 (Purchased Goods and Services (PG&S)) and Category 2 (Capital Goods (CG)) data separately:
  1. A purchasing organization-based approach.
  2. A product category-based approach.
Note: It is recommended to use only one method.

Both approaches allow you to filter between PG&S and CG data by using the corresponding filters in the Emissions overview dashboards and enable an administrator to customize the summary report for synchronization to ESG reporting. Regardless of the approach chosen, perform the following two main tasks:

  1. Configure Envizi Supply Chain Intelligence for emissions calculation and analysis.
    1. Set up master data files to account for Category 1 and 2. For more information, see Setting up master data files to account for Category 1 and 2.
    2. Configure and upload data per standard implementation. For more information, see Configuring.
    3. Analyze data on the Emissions management dashboard by using filters for Category 1 and 2.
  2. Configure Envizi Supply Chain Intelligence for reporting synchronization.
    1. Create a support case to configure Envizi ESG Suite account styles to accept both Category 1 and 2. For more information, see Opening a support case.
    2. Configure additional summary report tabs for reporting additional categories. For more information, see Configuring additional summary report tabs for reporting additional categories.

Setting up master data files to account for Category 1 and 2

Note: You can use any character strings to identify Capital goods and Purchased goods and services, as long as the same identifiers are consistently used for filtering on the Capital goods and Purchased goods and services summary pages. In the following examples, PG&S and CG strings are used.
Option 1 - Using purchasing organizations

When orders or transactions are flagged by the originating ERP systems as either PG&S or CG, it is best to use a purchasing organization-based approach to clearly delineate Category 1 and 2. You can do this by using either a Purchasing organization or a Purchasing organization L1 to designate orders as PG&S or CG.

If the purchasing organization is not being used for any other purpose, you can directly define purchasing organizations as, for example, Purchased Goods and Services and Capital Goods in the Purchasing organization template. Then label each order line with the corresponding Organization ID. For example,
Figure 1. Purchasing organization template
Purchasing organization template
Alternatively, if the purchasing organization is being used, and if the distinct purchasing organizations can each be designated as either a PG&S or CG organization, then the Organization L1 ID can be used:
Figure 2. Purchasing organization template
Purchasing organization template
Option 2 - Using product category

When the products and/or services that are purchased can be categorized as PG&S versus CG, a product category-based classification is preferred. You can do this by defining a Category L1 ID to be used to designate each product ID as PG&S or CG in the Product-mapping template, then reference this Product category for each product in the Product template. For example,

Figure 3. Product template
Product template
Figure 4. Product-mapping template
Product mapping template
Tip: These methods can also be used to calculate and capture additional Scope 3 categories in customized implementations if inbound data can be modeled as transactions (order lines) using appropriate custom factor data. For example, Category 11 (downstream use of sold products), can be uploaded into the system as monthly or other frequency energy consumption transactions (order lines) with a measurement unit representing energy (for example, kWh or MJ). Custom average-data factors representing energy use matched to the product category could be uploaded and would then apply to all transactions. Energy-based orders and physical purchase orders can both be resident in the system together as long as order line identifiers are unique.

Configuring additional summary report tabs for reporting additional categories

Create an additional summary report page and configure page context variables to distinguish between category 1 and category 2 data on the emission dashboard. This allows data to be synced with the Envizi ESG Suite.

In order to distinguish between category 1 and 2 data, use one of the three methods - filtering the data on Purchasing organization (Order.buyer.organizationIdentifier), Purchasing organization L1 (Order.buyer.category1.code), or Product category L1 (Product.family.code). Any of these can be figured with the variables that are configured at the page level.

  1. Duplicate the existing summary tab.
    1. From the side navigation menu, click Page builder.The Page library is displayed.
    2. Select the Summary page and click Copy.
    3. In the Name field, type a page name and click Create.

      For example, Summary - Purchasing organization.

      The page has been duplicated and added as a tab on the Emission Management dashboard, and it is also available in the page library.

  2. Configure a filter to view the data on the new Summary page.
    1. In the Context section, click Configure.
    2. Click edit icon for any of the following variables.
      purchasingOrganizationFilter
      Filters data based on the purchasing organization identifier. Use this filter if you have selected option 1.
      purchasingLevelOneFilter
      Filters data based on the purchasing organization category 1 code. Use this filter if you have selected option 1.
      categoryLevelOneFilter
      Filters data based on the product family code. Use this filter if you have selected option 2.
    3. Add value and click Edit.
    4. Review the variable update and click Done.
    5. Click Save.
    6. Click Close.
  3. Optional: Configure an account number prefix to export data to Envizi ESG Suite.

    When configured the accountNumberPrefix variable, clicking Export sends data to Envizi ESG Suite for an account named: accountNumberPrefixSpend-based_Purchasing location ID in Order Line.

    If this account does not exist, an account is created. Therefore, verify that the accountNumberPrefix is set according to your desired account naming convention.

    accountNumberPrefix
    Specifies the account number prefix for the page.
    Note: The account number prefix is prefixed on all exports for the page.
    1. In the Context section, click Configure.
    2. For accountNumberPrefix variable, click edit icon.
    3. Add value and click Edit.
    4. Review the variable update and click Done.
    5. Click Save.
    6. Click Close.
  4. Contact support to remove the existing summary page. For more information, see Opening a support case.