cancel
Showing results for 
Search instead for 
Did you mean: 

"BuilHeader not bound " values in std fields in IC Web UI

former_member206299
Contributor
0 Kudos

Hi,

In CRM 7.0 in the IC Web UI we are getting "BuilHeader Not bound" values for the first name , lastname fields.

This happens only if an account is having more than one contact person.

We debugged and we could see that is_dev_client is getting abap_true as a result.


* filter '... not bound' entries in non development system clients

  if is_dev_client = abap_false and value cp '*#n#o#t #b#o#u#n#d'."#EC NOTEXT
    clear value.
  endif.

the condition is failing and the value is not getting cleared.

Please note that the Components , Views corresponding to this scenario is standard only and not customized.

Any suggestions will be appreciated.

Regards,

Sijo.

Edited by: sijokjohn85 on Sep 11, 2009 1:20 PM

Edited by: sijokjohn85 on Sep 11, 2009 1:44 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member206299
Contributor
0 Kudos

Closed

Former Member
0 Kudos

Hi Sijo, Hi All

I do face the similar issue in CRM system but when trying to implement the note, I see the following message

Is that mean notes not relevant for the system? please clarify...

Regards,

Kamal

Former Member
0 Kudos

We just noticed the same error today, I found this note but haven't had a chance to apply yet.

Note 1310136 - UI fields contain text "... not bound"

Note 1242762 - BuilContactPersonRel for BuilHeader

former_member206299
Contributor
0 Kudos

Hi Glenn,

Thanks for your reply.

I checked the NOTES suggested and I checked the correction instructions, but i can see that all the changes are already existing in the present system.

Regards,

Sijo

nicolas_busson
Active Contributor
0 Kudos

Hi Sijo,

Obviously you don't know how to check notes...

Regards,

Nicolas Busson.

former_member206299
Contributor
0 Kudos

Hi Nicolas,

I compared the code changes explained in the correction

instructions with the existing code in methods of the classes they have mentioned in the SNOTE .

Is it not the right way.......if not please correct me...???????

Regards,

Sijo.

nicolas_busson
Active Contributor
0 Kudos

Unfortunately it is not...

Before comparing the code changes, you should have read the reason& prerequisite + the solution given in the note.

You would have understood that:

1) The "problem" you are experiencing is standard behavior as of CRM7.0

2) And you would also have noticed that more than 1 solution is given to avoid this behavior. A few of them are listed here:

- Not be provided debug authorization (meaning if your user is not granted auuthorization object S_DEVELOP you won't see those entries)

- Work in a non-test system

- Maintain some parameter with "N" in your SU01 user...

- Etc.

Regards,

Nicolas Busson.

Former Member
0 Kudos

The note did resolve the same issue in our system. But it was not clear that the SU3 setting for BSPWD_SHOW_NOT_BOUND had to be set to N, note made it sound like the setting was done in SE80.

Call transaction SE80. Load the package CRM_BSP_WD. Open the context menu by right-clicking on the folder "SET/GET parameter" and then choose "Create". Enter the parameter ID BSPWD_SHOW_NOT_BOUND and the text "Y=Display, N=Do Not Display, SPACE=System-dependent" and choose "Save".