Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

udm_supervisor t-code (DUMP)

Former Member
0 Likes
725

Hi gurus,

I am working with t-code udm_supervisor.

I am getting a DUMP with this description: Exception condition "CNTB_ERROR_FCODE" raised.

This happens when when I am in contacts tab.

I select a contact, and when I press RESUBMISSIONS button, I get this DUMP.

I've been debugging, and there is a table called it_button_properties that is having one more button with function code: "RSM_INV", that is not in m_table button.

This tables are used in the method: set_button_visible.

When this method is called with the button that doesn't appear in m_table, it raised the exception CNTB_ERROR_FCODE.

Has anyone any suggestion?

Thanks in advance,

Jay

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
629

Hi Guys,

Finally, the way I resolved this issue was like this.

This was a problem of the standard code, so I reported this issue to SAP, and they had to create an special SAP note for this.

The SAP note number to solve this is: 1704495.

Hope this helps,

Best wishes

Jay

3 REPLIES 3
Read only

former_member189779
Active Contributor
0 Likes
629

Try search OSS note for this.

Read only

Former Member
0 Likes
629

Hi Jay,

You Can also have a check with your customisation done for resubmission ,as resubmission is required to be displayed till the time they are settled by the customer irrespective of whether the
customer is reached so with that we have to activate few things ...May be you can check with your functional folk.

if i am not wrong resubmission is one of collection procedure so corresponding attributes are being configured .

Thanks,

Deb

Read only

Former Member
0 Likes
630

Hi Guys,

Finally, the way I resolved this issue was like this.

This was a problem of the standard code, so I reported this issue to SAP, and they had to create an special SAP note for this.

The SAP note number to solve this is: 1704495.

Hope this helps,

Best wishes

Jay