The below listed chapters represent steps which need to be followed in the given order.

...

Make sure the following PP tables include data:

1. Plasma_Country_Region_Mapping

2. Plasma_OperatorMapping

3. Plasma_Transactions_Extractor_Fields

4. Plasma_Transactions_SequenceControlTable

5. Plasma_Config

2. Plasma_Transactions_Extractor_Mapping Configuration

Follow the instructions athttps://pricefx.atlassian.net/wiki/spaces/ACCDEV/pages/3769499743/Plasma+Configuation+Tables#Plasma_Transactions_Extractor_Mapping.
Example:

...

3. Plasma_Config Configuration

The PP table description: https://pricefx.atlassian.net/wiki/spaces/ACCDEVACC/pages/37694997435932942408/Plasma+ConfiguationConfiguration+Tables#Plasma_Config.

Plasma_Config general configuration description: https://pricefx.atlassian.net/wiki/spaces/ACCDEV/pages/3842736231/Plasma+General+Configuration#Plasma_Config.

...

To configure the Feeder (activation) for Transactions:

1. Open the Data Load “Plasma_Transactions” of the ‘Calculation’ type.

2. Go to the “4 Calculation” tab.

3. Select “Plasma_Data_Extractor_Feeder” as the calculation logic for the Feeder and select the entity (either Product or Customer). The Feeder will inject all the rows from the master table. It can be configured to inject only selected IDs by specifying in the SKUs/CustomerIds input field. In order to use the Feeder, the corresponding master table should be joined in the Plasma_Transactions_Extractor_Mapping table, otherwise it will not work.
   

   Image Modified

4. Configure thePlasma_Config PP table: set the DataPartitionedForLoad field to “Y” and specify the Feeder entity under the FeederEntityFieldInPrimarySource PP (typically CustomerId).
   

   Image Modified

Notes:

• To deactivate the Feeder do the opposite.

• It is recommended to keep the Feeder activated (or ask for increasing the Maximum In-Memory Count parameter to an appropriate value).

...

Distiller creates the output data (rolled up monthly) and does not need any configuration.
It rolls up the quotes data for each month, all sellingFrom/sellingTo combinations.

To run it:

1. Open the “Plasma_Output_Creation” Data Load and select “Run now”. To test this, open PA logic “Plasma_Transactions_Creation” and execute.

2. Open the “Plasma_Output_Enrichment” Data Load and select “Run now”. To test this, open PA logic “Plasma_Transactions_Enrichment” and execute.

8. Calculation Flows

Deploy the Calculation Flows “Plasma_Transactions_Sequencer” and “Plasma_Transactions_Sequencer_Reset“ to be active.

...

If Plasma_Transactions_Extractor_Mapping changes (the values set there are different to those which were present during the previous run of Plasma Data Loads) while the incremental mode is active, then:

1. The below listed DataSources/Datamarts need to be truncated:

   • Plasma_TX DS

   • Plasma_Transactions DM

   • Plasma_Output_Transactions DM
     

2. The last incremental load date in every respective Data Load needs to be reset (set to null):

   • Plasma_Transactions

   • Plasma_Transactions_PreviousPrice

   • Plasma_Transactions_Exchange

   • Plasma_Ouput_Creation

   • Plasma_Output_Enrichment
     

This way it is guaranteed that there is no data inconsistency in the Data Sources and all the included data meet the criteria specified in the PP tables.

...