Marketing Profile : Creation based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset via the WebUI Segment Builder

Objective: Creation of a Marketing Profile Set based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset thru the WebUI Segment Builder.

Problems: Standard CRM_MKTTG_BP_BIRTHDATE Infoset DOES NEVER RETURN ANY RESULTS on the segmentation builder of the WebUI client (no matter the filter you specify).

Other cases: However if we create a new Data source with data “Extraction from Query” (transaction RS02) based on this standard CRM_MKTTG_BP_BIRTHDATE Infoset and we test the functionality using transaction RSA3, IT DOES RETURN RESULTS (using the same filters as in the segmentation builder)! Of course the segmentation builder works with other attribute lists.

NEW: IF WE DON’T SPECIFY ANY SEGMENTATION BASE IN THE PROFILE GROUP, IT DOES RETURN RESULTS!!! (GO TO THE END OF THE DOCUMENT FOR DETAILS)

Steps followed:

Review Standard Infoset CRM_MKTTG_BP_BIRTHDATE (Transaction SQ02).
1. Review Data Reading Program code: do we have to change the standard code? We have only remove the “BREAK-POINT” statement.
Creation of a Data source based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset (Transaction CRMD_MKTDS).
Creation of an Attribute List based on that standard Data source and selection the Birth date as a filter in the Attribute list (Transaction CRMD_MKTDS).
On the segment builder of the WebUI set any filter (Example: “TODAY”).

Steps in detail:

Review Standard Infoset CRM_MKTTG_BP_BIRTHDATE
1. SQ02.
2. (Image deleted)
3. Review Data Reading Program code (Code attached)
4. (Image deleted)
Creation of a Data source based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset
1. Data source: Transaction: SPRO – Customer Relationship Management – Marketing – Segmentation – Maintain Data Sources and Attribute Lists: CRMD_MKTDS
  1. Create Data Source
  3. Creation of Profile Set
  5. Graphical modeler
  7. Create Filter: We have already tried many different filters (we already seen notes referring to this matter).
  9. Example1: “today”
  11. Count target group. Here I would like to stand out that once you click on the “Count” option, immediately it shows 0 results. In other words, it doesn’t process any information. With other attribute lists it takes some time to process, no matter the filter or the attribute list you use. However if we create a new Data source with data “Extraction from Query” (transaction RS02) based on this standard CRM_MKTTG_BP_BIRTHDATE Infoset and we test the functionality using transaction RSA3, IT DOES RETURN RESULTS (with “today” filter and other)! So it seems that the problem has to do with the segment builder, not the Infoset.
  13. Result: it never return any results no matter the filter you specify.
Other cases:
1. Creation of a new Data source with data “Extraction from Query” where you enter the name of your new query
  1. Creation of a Data source based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset
    1. Standard Infoset CRM_MKTTG_BP_BIRTHDATE:
    3. We fill the form and select “Extraction from Query”:
    5. Press SAVE and define which fields will be available for selection and which of them will be visible.
  2. RSA3: Extractor checker in order to test the Data source:
    1. We specify the Data source:
    3. IT DOES RETURN RESULTS:
    5. ALV Grid:
NEW: It seems that it has to do with the Segmentation Basis selected in the creation of a Profile Set, because if we do not select any, it does return results. But we need to create this Profile Set based on a particular Segmentation Basis called BS Usuarios Registrados.
- Segment builder – Profile Set of the WebUI
  - Segmentation Basis: we leave it in blanc.
- Define Segmentation Basis:
  - Transaction: SPRO – Customer Relationship Management – Marketing – Segmentation – Classic Segmentation – Define Segmentation Basis.
    - BS Usuarios Registrados:
- Define Reports for Creating Segmentation Bases
  - Transaction: SPRO – Customer Relationship Management – Marketing – Segmentation – Classic Segmentation – Define Reports for Creating Segmentation Bases
    - ZMK_UTL_MGR_SITES_UREG
- Define Usage for Segments:
  - Transacción: SPRO – Customer Relationship Management – Marketing – Segmentation – General Settings – Define Usage for Segments.
    - ZBS_UR à02 Segmentatión Basis
- Attribute List:
  - Category:
There is no Category 02 Segmentatión Basis!!! Why??
New: It seems that it has to do with the Segmentation Basis selected in the creation of a Profile Set, because if we do not select any, it does return results. But we need to create this Profile Set based on a particular Segmentation Basis called BS Usuarios Registrados. Why is not posible to select Category 02 Segmentation Basis in the creation of the Attribute List?

Solution:-
- It seems that the standard Infoset doesn’t work by itself with Segmentation Basis. Two SAP notes have been applied and a new Field Group has been added to the Infoset (in order to distint the Segmentation Base).
  - CRMT_MKTTG_IS_BIRTHDATE-MGRGUID
  - 1966298: MGR_GUID is not populated correctly to infoset read program
  - 2007687:Segmentation InfoSet queries saved with incorrect Master Group
- For that reason we had to create a new Infoset based on the standard CRMT_MKTTG_IS_BIRTHDATE, but adding this new Field MGRGUID to the Group Fields.
This document was generated from the following discussion: Creation of a Marketing Profile Set based on the standard CRM_MKTTG_BP_BIRTHDATE Infoset thru the WebUI Segment Builder