This section describes the general Plasma configuration. All its chapters are linked in the respective deployment pages for Transaction and Quotes where there are extended with an additional description specific for these.

Plasma_Config

You need to configure the Plasma_Config table to specify the general configuration, such as the primary source type, name and flag determining whether the Feeder is used or not. This has to be loaded manually.

Plasma_Config table description: Plasma Configuration Tables

The detailed configuration description is included in respective configuration pages for Transaction and Quotes.

Config Owner field in the Company Parameter table is the Extractor name.

• Since Plasma_Data_Extractor is used for both Transactions Extraction and Quotes Enrichment, we need to know which mapping/fields table to refer to. So we have to add the respective table name in Plasma_Config table with keys “MappingTableName”, “TargetFieldsTableName”, “TargetDLLabel”, “TargetDLName”, “TargetDLType”.

• “DataDelayInMonths” – Integer input: only data which is past the current date by the given number of months will be taken into consideration whenever the aggregation happens. By default, it is 0 (no delay).

• “EmailIdsForFailureAlert” – An email address for the failed jobs notifications can be provided (multiple values separated by comma).

• “DataPartitionedForLoad”

  • If there is not enough data in your primary source, you can set DataPartitionedForLoad with Config Value set to N.

  • Otherwise, configure Y. When the Feeder is used, it is important to know what the entityId of the Feeder is mapped to in the primary source. “FeederEntityFieldInPrimarySource” should be the name of the field in the primary source which has the value of entityId (sku/customerId) for the selected entity type (Product/Customer).

Bound Partition Creation

Create a bound partition with the name and label “local” with the same partition credentials. This allows the Extractor (PA logic) to write audit logs to the Plasma_Audit configuration table.

Feeder

Since the Extractor creates a temporary table for every source, there is a limit for this temporary table on how many rows it can handle. If the number of rows in all sources together reaches over or tends to reach over the Maximum In-Memory Count parameter whose value is 100,000 by default (unless changed in the partition to some other value), then the Feeder needs to be activated.

The Feeder’s main objective is to partition the data so that it never crosses the Maximum In-Memory Count when creating temporary tables. The Feeder will inject the entities (either Customer or Product) and the logic will run for each entityId.

If it is clear that the number of rows in all sources together would not reach over the Maximum In-Memory Count parameter in the particular partition, the Feeder can stay deactivated. The benefit of having the Feeder deactivated is much faster data processing.

The configuration is done via several steps in the particular Data Load and in the Plasma_Config configuration table, for both Transaction and Quotes the description is included in the respective configuration pages.

Currency Exchange Rates

Converts MONEY fields from the source currency to USD. This is calculated per row.

The currency exchange rates should be loaded into the “Plasma_Currencies” DS. The exchange rates will be fetched from the “ccy” DS. If any rates are missing here, they will be fetched from the “Plasma_Currencies” DS.

The additional configuration is included in the respective configuration pages for Transaction and Quotes.

Additional Configuration

Plasma-specific components can be hidden from regular users with the help of user roles. Users with the Plasma role can mark these components as Plasma objects. Once marked, these objects are displayed only to Plasma users and only Plasma users can edit and delete them.

Open

To mark components as Plasma objects:

1. Go to Administration > Configuration > PriceAnalyzer > Plasma.

2. Find the desired component and enable the ‘Use with Plasma’ checkbox.
   After your selection, the component is checked for any dependencies it might have (e.g. between a Data Load and a Data Feed). If there are any dependent components that are not marked as Plasma objects, a warning is displayed and the configuration is not saved.

3. Before saving the configuration, look for items with the 'Inconsistency on Server' flag and fix the issues.