Skip to end of metadata
Go to start of metadata

 

General Information

 

Marketing objects are set up with certain master data and are valid during a specified time frame. Changes in master data are not reflected automatically in these objects. If one wants to have these master data changes reflected in his objects, it would be necessary to identify and change manually all active and planned marketing objects which can be a very time consuming and inefficient task, therefore the PMDC report is provided.

 

The scope of PMDC is to evaluate certain master data changes and to apply these changes to affected trade promotions.

 

Report Parameters

 

The PMDC offers the following design to select trade promotions:

 

 

  1. Search for Marketing objects base on select options system fetches selected trade promotions from DB, that fall into the plan start and plan to date range. In case the plan start and plan end dates are not filled the range is defaulted with 01.02.1900 to 31.9999.
  2. Filter by statuses enter in selection screen
    1. filter by stystem status
    2. filter by user status
  3. Validate Selection: No Mkt found, post message

 

 

Report Design

 

For the selected trade promotions the PMDC report works the following way:

 

  1. Load Trade Promotion
  2. Enqueue Trade Promotion - if the trade promotion cannot be locked, the PMDC aborts. The reasons may be different (any other process locks the same trade promotion, TP status does not allow to execute CGCH 'Change attributes' business transaction)
  3. Read Product Assignment from Trade Promotion
  4. Read Product History according to PMDC parameters
  5. Performs CCA checks to determine any products to add, delete or change
  6. Performs product changes (add, delete or change)
  7. Regenerate KPI plan data
  8. Regenerate Conditions

 

Design for Product Assignment

 

Product Category change

 

The PMDC report checks if products and product categories used in a trade promotion are consistent with the product master data. Usually a product is assigned to a product category. Product categories may hold several products.

When products are used in trade promotions there are the following different scenarios.

  • Product is single assigned The product is entered in the product assignment block directly. The product holds the product category information.

  • Product is mass assigned The product category is entered in the product assignment block. The product category is exploded to insert the products assigned to the product category.

The product assignment for the trade promotion is hold in table CRMD_MKTPL_PROD. For mass assigned products the information about the selected product category is hold in the field SEL_CATEGORY_G.

 

The product master data gets changed the following way:

Product HT-1000 is moved to a different product category. Product HT-1000 is no therefore longer assigned to product category LAPTOPS but assigned to product category NOTEBOOKS. Furthermore the product HT-1020 gets newly assigned to product category LAPTOPS.

 

The PMDC report run for the sample trade promotions should detect the master data changes and perform changes to the trade promotions as per the following design. There is different design for single and mass assigned products:

 

  • Product is single assigned The trade promotion is created for the product itself. When running the PMDC report the product category for the product gets updated since this got changed in the product master data.

     
  • Product is mass assigned The trade promotion is created for the products for a certain product category. The planning account is therefore supposed to retrieve discounts for products of the product category.



    When running the PMDC report the following happens:
    • all products that were newly added to the selected product category are included in the trade promotion
    • all products that are no longer included in the selected product category are deleted from the trade promotion


 

There is the following design for active trade promotions - a trade promotion is considered as active if it is in 'released' status and has the start date is already reached:

 

Updating product categories in the single assignment scenario and adding new products to a trade promotion in the mass assignment scenario don't cause any issues. However deleting any product from an active trade promotion is not working. The following error is raised in the PMDC log:

 

Unable to delete product HT-1000 because promotion already started

 

Therefore whenever the PMDC is supposed to delete a product from an active trade promotion the whole PMDC process is failing. The trade promotion needs to be corrected manually in that case.

 

Unit of Measure change

 

The unit of measure may gets changed in the master data for a certain product.

For products getting the UoM changed in the master date there is the following design. The trade promotion has a product assigned with the UoM taken from master data before the product master changed.

 

If the changed product UoM is still valid for the trade promotions sales data, the PMDC updates the product accordingly.

If the updated product master data is not valid for the trade promotion sales data the product cannot be updated but gets deleted.

This design is also valid for locked products. Since the sales data API won't return any data for locked products the product is supposed to be deleted rather than updated.

 

Design for Product Category Assignment

 

Product Category Change

 

For product category assignment the design is almost the same but depends on the minimul Level of Product hiearchy defined for the product category assignment. This difference is if the parent category is used in the TP or if the category is exploded to the min level and the child categories are added to the TP. There is the following product category hierarchy:

 

The parent product category is added to the TP - this is either assigned directly or exploded.

  • Assigned product category equal than the min hierarchy level - the product category is then assigned to the TP



  • Assigned product category higher than the min hierarchy level - the product category then gets exploded into the child categories

      

 

The product category now gets another child category added.

 

Depending on the min hierarchy level there is the following design.

  • Assigned product category equal than the min hierarchy level - there is no change done to the TP since the assigned hierarchy level did not change



  • Assigned product category higher than the min hierarchy level - the newly added product child category gets added to the TP

 

For trade promotions that already started (technically with having the start date in the past) there is the following design. The product category is not valid for the full TP validity period but is valid from the current date only. The product category effective start date is set to today's date.

While the existing product categories are valid for the full TP period, the added product category is valid for certain dates only.

Known Issues

 

Report Selection

 

2396367 - PMDC report is not working properly with user status

2175710 - PMDC program is not working for User Status

1932503 - PMDC requires values for the status selection option

1928400 - PMDC program ignores the status range option

 

Product Design

 

2598385 - PMDC deletes product that is moved to a different category below a mass assigned parent category

2573283 - PMDC updates effective_to date multiple times on product Hierarchy changes  

2056057 - PMDC: No message is sent to the log when a product is updated.

2021814 - PMDC does not update product when product category changes under the parent mass assigned category

1871966 - PMDC program deletes products instead of update them

1817606 - PMDC: Design change for products with modified product categories

1780957 - PMDC report deletes products with invalid Unit of Measures

 

PMDC Message Log

 

 

2056057 - PMDC: No message is sent to the log when a product is updated.

1920673 - PMDC log different when multiple TPMs in non-simulation mode.

1912544 - PMDC different log when report is run in simulation mode.

1895439 - PMDC : Inconsistent log in TEST mode for same TPM

1882547 - Save PMDC execution log for the transaction SLG1

1838417 - PMDC report does not save failure messages in SLG1

 

 

  • No labels