Segmentation Basis count is not updated

[former_member239386]

Hi Expert,

In CRM 7.0, EHP3, we defined Segmentation Basis using Target Group report. This is scheduled in 2-step batch job. However, job completed successfully without updating the segmentation Basis count.

1. Perform Filtering at Segment (i.e filter for non-archived BP, and Category = Organization, and Role)

2. Use this Target Group, and build Segmentation Basis.

3. Run 2-Step Job to use TG in Step 1 to update Step 2. However, Step 2 (the Segmentation Basis) is not getting updated.

i) CRM_MKTTG_GENERATE_SEG_MODEL -> Target Group count in Step 1 is always updated after job finished

ii) CRM_MKTTG_MGR_GEN_TG -> Segmentation Basis is not updated based on the couunt from TG in Step 1

This would be highly appreciated if anyone can share how the job is scheduled with the variant. I came across this http://scn.sap.com/thread/618281 and would like to know how is the standard variant is generated. Thanks!

Note: Step 2 count was huge because initially the filtering in Step one did not add in "Role" as one of the criteria. After adding the role it, new count drop to 1mil. Hence, Step 2 need to be updated to 1mil BP instead of 2mil. Thanks!

[former_member331042 · Accepted solution]

Hello Subashish,

The way introduced from the thread you mentioned is possible before CRM7ehp1. However, currently

since the coding of report CRM_MKTTG_MGR_GEN_TG changed. A parameter p_mgr_id become invisible, I guess from your job log you will find the error below:

So your MGR will not be updated because the job was not noticed which MGR should be updated.

To verify this you can open your own saved variant. You will also find that only the TG selected was filled while the MGR GUID is blank:

So if you want to update the MGR from the TG, you can choose to schedule two periodic jobs separately. One for report CRM_MKTTG_GENERATE_SEG_MODEL and the one to update the

MGR from TG you have to schedule it from the path below:

SPRO - CRM - Marketing -  Segmentation - Classic Segmentation - Define Segmentation Basis

because only in this way the importing parameter p_mgr_id will be pass to the report CRM_MKTTG_MGR_GEN_TG automatically.

Another way to carry out the two steps job-chain. You have to copy the report CRM_MKTTG_MGR_GEN_TG and the includes in it to your own report name.

find the include CRM_MKTTG_MGR_GEN_TG_TOP and copy it to your own z*CRM_MKTTG_MGR_GEN_TG and change the selection screen to make p_mgr_id visible.

Then you need to find your own MGR GUID from table CRMD_MKTTG_TG_H and save your

variant. This variant will contain the MGR information.

As go to the reason why after CRM7ehp1, the report CRM_MKTTG_MGR_GEN_TG is not needed.

From ehp1 onwards segmentation basis is a combination of filters inherited from the profile/target group from which it was initially built. Every time you create a model/build a target group which consumes this segmentation model, system evaluates the BPs for this combination of filters at runtime. which means segmentation basis is a 'DYNAMIC' list of BPs evaluated at runtime

unlike in lower releases where segmentation basis is a 'STATIC' list. You can even count the segmentation basis from WEB UI in the model anytime.

Wish it clears!

Jack Yu

[former_member239386 · Accepted solution]

Hi Jack,

This is a very helpful answer yet a strange new design to hide the P_MGR field. We are currently using the 2nd option which is the "two steps job-chain" via standard reports.

In that case, it does mean that if variant is generated correctly, P_MGR should be captured and will be able to update the count in segmentation basis.

Back to the rationale with "Dynamic" design, it is a good start but does this address the authorization consideration?

What we understand is "All Customers" contains of BP (basically the BUT000) for Person, Organization.

-> Person = Employee, Individual Customer, Contact Persons

-> Organization = Corporate account, CRM Org Model

Before building Segmentation Basis

1. Pre-defined filtering criteria to segregate the BP from "All Customers" is set for Employee segment, Individual segment, Corporate Account segment and 3 TG are generated. The is under usage "Campaign".

No User will be able to see usage = Campaign, except for Super User.

Building Segmentation Basis

2. Super User will right click each of the 3 TG -> Follow Up -> Build Segmentation Basis, and we park this under Usage "ZSAP". Normal User is granted authorization to use "ZSAP". This is to ensure normal user can only use this 3 segmentation basis.

If "Dynamic" option is for normal user to access Step 1 and perform Step 2 (like super user), it will lead to accidentally modification of pre-defined filtering criteria / removal of entire TG.

Appreciate if EHP 7.3 is having different way of authorization concept. Thank you!

[former_member331042 · Accepted solution]

Hi Subashish,

I write to you two weeks later since I was in middle of some critical works. Hope you are still interesting in this topic.

Since it is dynamic list, so the normal user will not need to generate the TG to keep segmentation basis up date. They will only use this segmentation basis created by the super user.  Do you mean step 1 and step 2 will not meet the business requirement for the normal user?

Thanks and regards,

Jack Yu

[former_member239386 · Accepted solution]

Hi Jack,

Yes. Step 1 and Step 2 is not suitable for normal user.

1. Normal user does not know the "All Customer" contains of "Employee, B2B (Org & Contact) and B2C (Individual)" BP details, including archive and non-archive data.

2. Exposing the "All Customer" will lead to invalid data being retrieved, for example pulling based on "Country" will lead to mixture of B2B and B2C data.

In order to facilitate the operation of Normal user, Super user has first segregate into different segmentation basis to meet their needs, for example:

A) Employee

B) B2B (Corporate), but this is a relationship data which pull Contacts details

C) B2C (individual customer)

With the segmentation basis provided and controlled based on authorization, Normal user only see the A, B, C basis and use the campaign (internal or external) accordingly.

Hope this clarifies. I appreciate if there is better approach to address the requirement above which can be explored further.