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

Ans plz

Former Member
0 Likes
773

Hi All,

1. If in any report running in background then can we set debugging.?

2. In ALV'S we used grid_display then can we set this to background?

3. D/f b/w se09 and se10?

4. d/f b/w workbench and customizing request?

5. HOW U MAINTAIN BOTH ALV and report option in your selection screen?

6. among all the events which events are mandatory in reports?

Regards,

krithika

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
744

Hello,

1)<b>Background job:</b> You can debug very easily if your program that you want to debug is a custom program. You can put an endless loop in the code somewhere.

WHILE SY-SUBRC = 0.

CHECK SY-SUBRC = 0.

ENDWHILE.

Now go to SM50, select the work process that is running the program. Click Program/Session->Program->Debugging, it will then open the debugger and you will be looping at your endless loop. Change the value of SY-SUBRC to get out of the loop and debug as normal.

or

1) Fix the break points.

2) Create job.

3) Go SM37

4) Select the job and write "jdbg" in command line.

Check:

3)<b>Difference between se09 and se10:</b>

5)<b>ALV in selection screen:</b>You can have parameters and ALV in your selection screen.For ALV,you can use docking container.

Regards,

Beejal

**Reward if this helps

Message was edited by:

Beejal Rawal

Hi All,

1. If in any report running in background then can we set debugging.?

2. In ALV'S we used grid_display then can we set this to background?

3. D/f b/w se09 and se10?

4. d/f b/w workbench and customizing request?

5. HOW U MAINTAIN BOTH ALV and report option in your selection screen?

6. among all the events which events are mandatory in reports?

Regards,

krithika

5 REPLIES 5
Read only

Former Member
0 Likes
745

Hello,

1)<b>Background job:</b> You can debug very easily if your program that you want to debug is a custom program. You can put an endless loop in the code somewhere.

WHILE SY-SUBRC = 0.

CHECK SY-SUBRC = 0.

ENDWHILE.

Now go to SM50, select the work process that is running the program. Click Program/Session->Program->Debugging, it will then open the debugger and you will be looping at your endless loop. Change the value of SY-SUBRC to get out of the loop and debug as normal.

or

1) Fix the break points.

2) Create job.

3) Go SM37

4) Select the job and write "jdbg" in command line.

Check:

3)<b>Difference between se09 and se10:</b>

5)<b>ALV in selection screen:</b>You can have parameters and ALV in your selection screen.For ALV,you can use docking container.

Regards,

Beejal

**Reward if this helps

Message was edited by:

Beejal Rawal

Read only

Former Member
0 Likes
744

Hi Krithika,

(2) I think you can run report with grid_display in background.

(3) They both are same , i am not sure if there is any difference.

(4) Workbench request is one where record changes made to ABAP Workbench objects and Cust. request is one Changes to Customizing settings is made and transported to different system

(5) to maintain both ALV and normal report, you can create two icons for each of them in the application tool bar and handle it.

(6) start-of-selection is the mandatory event. this event is trigerred by default even though you do not call it.

Regards,

George

    • plz reward point for helpful tips

Read only

Former Member
0 Likes
744

Krithika,

No event is mandatory in the report.

Depends on the situation, we need to use the events.

even without any event u can select the data from DB tables and can disply it as list.

Regards,

Sujatha.

Read only

Former Member
0 Likes
744

hi krithika,

SE09 is the transaction code for workbench organiser.Workbench organiser is the set of utilities for development change management.All Development changes are tracked via Workbench organiser.

SE10 is for Customosing organiser.Customising organiser is the set of tools for customising change management.All customizing changes are tracked via customising organiser.

regards,

keerthi

Read only

Former Member
0 Likes
744

hi,

1. I think yes...U can set the debugging for the reports running in the background..as I've never came across such situation..so I could not provide u the accurate solution.

2. Using only REUSE_ALV_GRID_DISPLAY, you can set an ALV report for background execution where as using reuse_alv_list_display, its not possible.

3. SE09 is the Transport Organizer which every ABAPers should be aware of this tool since this is used to track the changes made to the developement objects whethere is a new or existing one. Where as SE10 is used for managing the Customized change request which is frequently used by the Functional people.

4. Using Flag, you can maintain both ALV List and general list display on the selection screen. If the flag is true, then display the ALV list else General list.

5. Yes it is not mandatory to any event in the report. By default..start-of-selection event execution will take place if it not used in the report..All the events such as Load-of-progra, Intialization, start-of-selection..end-of-selection will execute automatically. However, you cant do the inputs validation without using at selection-screen event.

regards,

shamim