cancel
Showing results for 
Search instead for 
Did you mean: 

Loyalty Management - Error when saving Reward Rule

Former Member
0 Kudos

Hi Experts,

I have created a new dynamic attribute with ID: Z_DEMO_COUNTER (see attachment). This dynamic attribute is assigned to my loyalty program and this attribute is updated correctly.

Now I want to create a new reward rule that triggers the change of the tier level of the membership when a specific points amount is reached (see also attachment). When I try to save the reward I receive the error message that ID XXX is initial, unknown or it does not have the correct object type. It also says 'Error when saving rule version'.

The same error I receive, if I try to add the dynamic attribute to the formula of my reward rule that updates the dynamic attribute (see attachment 2). So I assume the dynamic attribute is wrong defined in customizing?

What does that supose to mean?

My thread seems to be related to this thread: http://scn.sap.com/thread/1510960. Error Handling in SAP CRM Loyalty Management seems to be not sufucient as it does not explain the error so a user can understand what to do here.

Any help is greatly appreciated.

BR/

Oliver

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Oliver

This issue related with generation of FDT objects for dynattr.

You should find your transport request in what you are change rule builder settings first time. If you save attribute in request that different from it attribute can't generate necessery changings in BRF. So you should delete your dynattr and save new in request with rule builder settings and error will dissapear.

Hope it helps

Regards, EL

Former Member
0 Kudos

Thank you very much. That was the problem.

Former Member
0 Kudos

Hi Oliver

Even I am getting the error "No Valid data object for the return value; boolean data object needed".  I  read the above comments. Unfortunately I am not sure of the old transports in our system. Do u reckon I save a set of configurations on one TR to get the issue resolved? If so, could you please suggest all the necessary configuration steps?

Regards

Raj

Former Member
0 Kudos

Hi Raj, if you dont remember the TR than it is difficult. You might have to reactivate the condition attributes somehow to transport everything again. What I did was:

1. Merge my TR with the TR where the change of conditions was included.

2. Retransport of all changes...

The result than was, that it worked.

Good Luck...

Former Member
0 Kudos

Hi Oliver,

I am facing the same error, when creating a rule.

"No Valid data object for the return value; boolean data object needed".

I have saved the Dyn.attr setting in the TR, However could you please clarify me,

which is the (first time) initial rule builder setting you are referring to in your earlier post.

are you referring to - Define Rule policy types ?. Could you please revert.

Please find the attach screen.

Former Member
0 Kudos

Hi Raj,

Have you over come this error, if so , could you please let me know the configuration steps you have carried.

I am also facing the same error, when creating a rule.

"No Valid data object for the return value; boolean data object needed".

I have saved the Dyn.attr setting in the TR, However could you please clarify me,

which is the (first time) initial rule builder setting you are referring to in your earlier post.

are you referring to - Define Rule policy types ?. Could you please revert.

Please find the attach screen.

Former Member
0 Kudos

Hi Bhaskar

In Set rule parameters, please try with this combination and see if it works.

Condition = "Type - Membership Activity" or "POS Accural" (If you want to award points for purchases), Actions = "Earn Points"; Then select new rule with Type = Product, Earn Points = Use, Actual Points = Formula ( Ex: Loyalty points*1); Point Type = Your configured type and Qualification type = Redeemable.

Hope this helps.


-Raj

Former Member
0 Kudos

hi Raj,

I also met the same issue and I could not find any note for this issue,

I had removed my dynamic attribute and wrap it up into the initial request, but the issue still be there , do you have any idea?

Br.

William.

Former Member
0 Kudos

Hi,

Please try sap note: 1773466

Hope this helps,

Cenk

Answers (0)