Application Development 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: 

unable to findout the error message in debug

Former Member
0 Kudos
271

Hi Gurus,

When i am trying to execute the T.code FMCI_COPY_NEXT_YEAR i am getting the

ERROR MESSAGE: SET SCREEN NOT ALLOWED IN SUB SCREEN (SCREEN NO SAPLSBAL_DISPLAY0101) in new implementation.

i am unable to find out where the exact error is comming ... i requested you to please guide me for the same...

Thanks in Advance !!!

regards,

Sanjay

10 REPLIES 10

Former Member
0 Kudos
187

HI,

double click on message and notice the number and type.

Debug the program/function and set a breakpoint as statement "message".

The system will hold on each message and with the information of number and type, you will find the right costing.

Regards

Nicole

Former Member
0 Kudos
187

HI,

double click on message and notice the number and type.

Debug the program/function and set a breakpoint as statement "message".

The system will hold on each message and with the information of number and type, you will find the right costing.

Regards

Nicole

0 Kudos
187

Hi ,

Thanks for your early reply...when I try to double click on the message its not showing any thing...

0 Kudos
187

Hi,

okay, maybe you have an different editor then me. Go to the long-text of the message, however it works in your system, to see the message number and type.

Regards

Nicole

0 Kudos
187

Hi,

I am using ECC 6.0 version but long text is not working....could you suggest work around the way... its urgent..

Regards,

Sanjay.

0 Kudos
187

Hi,

that can`t be.

Each message pop-up has an longtext.

Is there an help-button, then press on it.

Regards

Nicole

0 Kudos
187

no help button is there

0 Kudos
187

Then debug without knowing the type and number and take a look to each message, the system hold after you set statement.

How? Take a look to my first comment. :O)

0 Kudos
187

Thanks a lot

Former Member
0 Kudos
187

Hi,

In the debugging mode, go to menu Breakpoints,

Select breakpoint at statement

and then type MESSAGE

and then execute (F8) you will get to know the exact place where the message is triggered.