Set Up Your Company Organizational Structure
If your company is a conglomerate that has fully owned subsidiaries or largely independent business units, or has grown through mergers and acquisitions, you must account for emissions for the entire organization. This emissions data can be used to perform carbon accounting for your organization and your subsidiaries.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Permission Set Needed | |
|---|---|
| To enter and modify data: | Net Zero Cloud Manager OR Net Zero Cloud Admin |
To account for emissions for your company organizational structure, involves these steps.
-
As a Salesforce administrator, configure your permissions and settings:
- To use data processing engine, assign yourself the Data Pipelines Base User and Data Processing Engine Psl permission set licenses. See Assign a Permission Set License to Users.
- To aggregate emissions using data processing engine definitions, Enable Data Pipelines.
-
To account for emissions for your extended organizational boundaries, enable the
Organizational Boundaries setting. See Enable Net Zero Cloud Features.
For additional details, contact your account executive.
- To create accounts for your company and for all your subsidiaries and business units, Create Accounts for the Extended Organization.
- To create an internal organizational unit that identifies your parent account, Create an Internal Organizational Unit to Identify the Parent Company.
-
Define the company hierarchy or structure by setting up account relationships:
- To represent a relationship between the parent company and all accounts in the org, Create a Party-Role Relationship for the Parent Company.
-
To represent the relationship between the parent company and all accounts, Create an Account
Hierarchy.
Emissions are calculated for all companies that are in the parent company hierarchy. If there are accounts for which relationships are not defined, which means they are not part of the company hierarchy, they will not be considered for emissions consolidation.
- Make sure that the emissions sources are associated with an account. This account represents the company to which the emissions source belongs to. See Determine the Sources to Inventory.
- Make sure that you perform carbon accounting for the emissions sources. The energy use and carbon footprint records are associated with the emission sources. The account name associated with the emission sources will be implicitly associated with the energy use and carbon footprint records for the purposes of emissions calculation and consolidation.
- To represent what portion of emissions are allocated from child company to parent company, Allocate Emissions to a Parent Company.
-
To aggregate emissions inventory for the parent company or the related companies,
recalculate the emissions inventory.
In a two-level organizational heirarchy, when you recalculate the emissions inventory for the parent company, the energy use, procurement data, and the carbon footprints associated with the parent company inventory are aggregated and rolled up. The carbon footprints are automatically associated with the account that is specified on the emission source, that is present on the footprint.
In a multilevel organizational hierarchy, tailor your emissions inventory accounting rollups to your specific needs by writing custom code to recalculate emissions inventories for entities in the organizational hierarchy structure.
- In a single-level organizational hierarchy, when you recalculate the emissions inventory for a subsidiary account, the emissions from the subsidiary company's carbon footprints are aggregated and rolled up. If you have more than 500 thousand energy use and carbon footprint records, they aren't aggregated and rolled up to the parent company inventory. If you have more than 500 thousand energy use and carbon footprint records, we recommend that you dissociate this annual emissions inventory from a few carbon footprint records and try again.
