Loading
Salesforce now sends email only from verified domains. Read More
Set Up Trade Promotion Management
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Understanding How KPI Values are Stored when BOM Component is Interfaced from Processing Services

            You are here:

            1. Salesforce Help
            2. Docs
            3. Set up and Maintain Trade Promotion Management

            Understanding How KPI Values are Stored when BOM Component is Interfaced from Processing Services

            In Processing Services, a product can be both a standard product and BOM component. For example, you can add Product Chewy Chocolate (6) as a standard product to a promotion and also add it as a component of Product Chocolate 6/12*96, which is a BOM header, to the same promotion. Therefore, when product actual data is interfaced into a table, the system must identify whether the value corresponds to a standard product or a BOM component.

            Required Editions

            Available in: Lightning Experience

            Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled

            When a product is created in Salesforce, its external ID is stored in the Product table. A BOM component external ID is stored in the Product Part table when it’s added to a BOM header via the Product Parts related list. When data is synced to Processing Services, the system generates different internal IDs for standard products and BOM components using the respective tables. The internal ID, along with the external ID of the product or product part, is stored in the ProductId table.

            When you import BOM component conditions into the system, provide the external IDs to identify BOM components and determine the correct internal IDs against which the values must be stored. BOM component values are applicable to these tables:

            • Account Product Measure
            • Daily Measure Int
            • Daily Measure Real
            • Product Measure
            • Promotion Tactic Daily Measure Real
            • Promotion Tactic Weekly Measure Real
            • Weekly Measure Int
            • Weekly Measure Real
            Example
            Example In this example, Product Chewy Chocolate (6) has two entries in the table—one as a standard product and the other as a BOM component—but each entry has a unique external ID. To differentiate and identify the values of the standard products and BOM components, the system uses the external IDs provided in the import data to find the internal IDs in the Processing Services ProductId table. The internal IDs are then used to insert data to the Promotion Tactic Measure Real table.
            AccountProductExternal IDMeasure CodeWeek 25Week 26
            Account ABC Product Chewy Chocolate (6) 1001 SHIP 10 10
            Account ABC Product Chewy Chocolate (6) 101 SHIP 15 20
            Account ABC Product Crispy Chocolate (6) 102 SHIP 5 5
            Account ABC Crisply White Wafer 1010 SHIP 40 30

            This data is interfaced.

            • Product Chewy Chocolate (6) with the External ID 1001 is a standard product and is stored in Processing Services with an Internal ID 6.
            • Product Chewy Chocolate (6) with the External ID 101 is a BOM component and is stored in Processing Services with an Internal ID 2.
            • Product Crispy Chocolate (6) with the External ID 102 is a BOM component and is stored in Processing Services with an Internal ID 3.

            While interfacing the actual values of the BOM components into the Promotion Tactic Measure Real table, the system uses the BOM component internal IDs as the Product ID. The system inserts the values of Product Chewy Chocolate (6) and Product Crispy Chocolate (6) in to the Promotion Tactic Measure Real table with Product IDs 2 and 3, respectively.

            Promotion Tactic Measure Real
            Promotion IDTactic IDProduct ID (Internal ID)Product NameMeasure CodeWeek 25Week 26
            a2o090000005DPDAA2 a2o090000005DPDAA3 2 Product Chewy Chocolate (6) SHIP 10 10
            a2o090000005DPDAA2 a2o090000005DPDAA3 6 Product Chewy Chocolate (6) SHIP 15 20
            a2o090000005DPDAA2 a2o090000005DPDAA3 3 Product Crispy Chocolate (6) SHIP 5 5
            a2o090000005DPDAA2 a2o090000005DPDAA3 5 Crispy White Wafer SHIP 40 30

            The data formats, columns, and column names of the original tables or import data is different from the ones used in this example. These parameters are intentionally added or modified for simplification and better understanding of the example.

             
            Loading
            Salesforce Help | Article