Dialog & Report Programming!

Hi Experts,
Can you please explain what is the different between
Dialog & Report Programming
Thanks in Advance,
Guru.

hi
Here is that difference
Report Programs:
1. Reports are stand alone programs.
2. We use reports to read data base tables & represent results in Lists
3. Reports are collection of processing blocks, controlled by System calls depending on events.
4. Reports can use LDBs or SELECT STATEMENTS
defined by DEVELOPER.
5.Reports can call Dialogue programs and vice versa.
Dialog Programming
1.Dialogue programs are not stand alone programs. (we
have to link the dialogue programs to at least one or
more SCREENS & TRANSACTION CODES)
2. We use Dialogue Programs to read & change
Database tables.
3.Dialogue programs are controlled by Screen flow logic.
4.Dialogue program is also called as Module pool program
or TRANSACTION.
5.These module pools are separated in to PBO and PAI
events.
Re: Difference between Dialog programming and reports.
regards
vijay
plz dont forget to reward points if helpful
Regards,
Santosh

Similar Messages

What is difference between report programming and dialog programming?

hi,
what is difference between report programming and dialog programming? plz provide some example code
bye

ABAP programming
Basically reports are used to read database and represent the results in lists.
Reports are collections of processing blocks that the system calls depending on events.
We can use reports to evaluate data from database tables.
Reports are stand alone programs and controlled by events.
A report itself never creates events
steps in report:
Processing the selection screen
Reading the database
Evaluating the data and creating lists
Outputting a list.
1st u write simple logics, after that u can enhance the code as step by step.
http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
http://www.sapdev.co.uk/reporting/reportinghome.htm
Dialog Programming
Structure of a Dialog Program
A dialog program consists of the following basic components:
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Check this link for basics.
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Check this link for Dialog Programming/Table Control
http://www.planetsap.com/Tips_and_Tricks.htm#dialog
Check this SAP Help for Dialog Program doc.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
Check this SAP Help link for Subscreens.
http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
Check this link for subscreen demo program.
http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
Also check this link too.
http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
http://abapprogramming.blogspot.com/

How to use a parameter of a report program from selection screen in a dialog program

how to use a parameter value(entered ) of a report program from a selection screen in a dialog program.
I have to fetch the value entered in the parameter of report program and display it in a dialog program

Hi Aasim,
Just mention like below in your ABAP report.
PARAMETERS: p_aufnr TYPE aufnr MEMORY ID ord.
and mention the same memory ID name in the module pool screen property it automatically populates the value to and fro

How to use a parameter of a report program in a dialog program

how to use a parameter of a report program in a dialog program.
I have to fetch the value entered in the parameter of report program and display it in a dialog program

Hi Aasim,
Just mention like below in your ABAP report.
PARAMETERS: p_aufnr TYPE aufnr MEMORY ID ord.
and mention the same memory ID name in the module pool screen property it automatically populates the value to and fro

How to use a parameter in a report program in a dialog program

how to use a parameter in a report program in a dialog program

Hi Shaikh,
Post it in http://scn.sap.com/community/abap
"ABAP Development".
sree

HOw to find Report program associated module pool program?

HOw to find Report program associated module pool program?
I.e
Me21n is the tcode.I want to find screens related to this tcode.
Associated report program is RM_MEPO_GUI.(It has no screens hence it is a report program).
(if module program is attached to tcode,i can easily find entries in d020s)
Here report program is calling a module pool program SAPLMEGUI(Has screens).
If i give the Tcode Me21n,i want to list out all the screens of it..
Can u give any suggestion....

Hi Sampath.
Manually i can see it (by seeing in system-status)..
programmatically i want to know..
for ex:if u take Tcode:Va01
we can get program (dialog) and tcode in Tstc table .
If we know the program name(dialog), we can find program and screens in d020s table.
Va01 is atatched to a module pool program..No problem to find screens..
In case of me21n,
It is atatched to report program(calling module pool program)..
Here i could not be able to get the screens ..
I think u undrstood my problem..

How to do the Validations in Report Programming?

How to do the Validations in Report Programming?
how to do screen Validations and Field Validations if posssible can any one send the code regarding the Validation ....
Tks
Durusoju

AT SELECTION-SCREEN - selscreen_event
Syntax
| { ON {para|selcrit} }
| { ON END OF selcrit }
| { ON BLOCK block }
| { ON RADIOBUTTON GROUP radi }
| { }
| { ON {HELP-REQUEST|VALUE-REQUEST}
| FOR {para|selcrit-low|selcrit-high} }
| { ON EXIT-COMMAND }.
Alternatives:
1. ... OUTPUT
2. ... ON {para|selcrit}
3. ... ON END OF selcrit
4. ... ON BLOCK block
5. ... ON RADIOBUTTON GROUP radi
6. ... { }
7. ... ON {HELP-REQUEST|VALUE-REQUEST} FOR
 {para|selcrit-low|selcrit-high} }
8. ... ON EXIT-COMMAND
Effect
These additions allow individual evaluation of specific elements of the selection screens of the program. The information as to which selection has triggered the event is contained in the system field sy-dynnr.
Alternative 1
... OUTPUT
Effect
This event is triggered at the screen event PBO of a selection screen. In the event block, the selection screen can be prepared through assignments to the data objects of parameters and selection criteria and through dynamic screen modifications.
Note
The assignments to input fields in the event block AT SELECTION-SCREEN OUTPUT always affect the selection screen and overwrite the user inputs from previous displays of the same selection screen. Assignments in the event blocks LOAD-OF-PROGRAM oder INITIALIZATION, on the other hand, only have an effect at first program start.
Alternative 2
... ON {para|selcrit}
Effect
This event is triggered at the screen event PAI of a selection screen if the content of the input field of a parameter para or a line of a selection criterion selcrit was passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or an error message in the event block makes the fields para and selcrit ready for input again.
No parameter that is defined as a radio button can be specified. For this purpose, the addition ON RADIOBUTTON GROUP is provided.
Note
If a user action takes place in the dialog box for the multiple selection of a selection criterion selcrit, the entries of the selection table are passed to the program, line by line. For each line, the event AT SELECTION-SCREEN ON selcrit is triggered.
Alternative 3
... ON END OF selcrit
Effect
This event is triggered after the selection table selcrit has been fully passed to the program after a user action in the dialog box for the multiple selection has taken place. In the event block, the entire selection table can be checked.
Alternative 4
... ON BLOCK block
Effect
This event is triggered at the screen event PAI of a selection screen if all the input fields of a block block of the selection screen were passed to the ABAP program. In the event block, the user inputs can be checked. Sending a warning or an error message in the event block makes all the fields of the block block ready for input again.
Alternative 5
... ON RADIOBUTTON GROUP radi
Effect
This event is triggered at the screen event PAI of a selection screen if all the fields of a radio button group radi of the selection screen were passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or error message in the event block makes all the radion buttons of the block radi ready for input again.
Note
The individual fields of a radio button group are not passed individually and do not trigger the event AT SELECTION-SCREEN ON par.
Alternative 6
Effect
The event AT SELECTION-SCREEN itself is triggered as the last event of selection screen processing if all the input values were passed to the program. In this event block, all the user inputs can be checked. Sending a warning or an error message in the event block makes all the screen fields ready for input once again.
Alternative 7
... ON { HELP-REQUEST | VALUE-REQUEST } FOR
 {para|selcrit-low|selcrit-high} }
Effect
The two events ON HELP-REQUEST and ON VALUE-REQUEST are triggered at the screen events POH and POV of a selection screen if - for the input field of a parameter para or one of the input fields of a selection criterion selcrit - the field help F1 or the input help F4 was called. Other selection events are not triggered.
In the event blocks, a self-defined field or input field can be programmed, which overrides any helps possibly defined in the ABAP Dictionary.
Notes
These event blocks can only be implemented for fields of the selection screen that are defined in the same ABAP program and not in a possibly linked logical database.
With the events for the field and input help, no data is transported between the selection screen and the ABAP program. As with general screens, suitable function modules must be used for these. The parameters and selection criteria changed for the input help are transported to the selection screen.
Alternative 8
... ON EXIT-COMMAND
Effect
This event is triggered if the user has called one of the functions Back, Exit or Cancel. In the event block, possible clean-up actions can be executed.
Example
In these executable programs, a standard selection screen and a further selection screen are defined. In the event blocks AT SELECTION-SCREEN, the inputs in the selection screens can be specially handled using the name p_carrid and the screen number in sy-dynnr.
REPORT demo_at_selection_screen.
Global data
DATA: sflight_tab TYPE TABLE OF sflight,
 sflight_wa LIKE LINE OF sflight_tab.
Selection screens
PARAMETERS p_carrid TYPE spfli-carrid.
SELECTION-SCREEN BEGIN OF SCREEN 500.
SELECT-OPTIONS s_conn FOR sflight_wa-connid.
DATA s_conn_wa LIKE LINE OF s_conn.
SELECTION-SCREEN END OF SCREEN 500.
Handling selection screen events
AT SELECTION-SCREEN ON p_carrid.
IF p_carrid IS INITIAL.
 MESSAGE 'Please enter a value' TYPE 'E'.
ENDIF.
AUTHORITY-CHECK OBJECT 'S_CARRID'
 ID 'CARRID' FIELD p_carrid
 ID 'ACTVT' FIELD '03'.
IF sy-subrc = 4.
 MESSAGE 'No authorization for carrier' TYPE 'E'.
ELSEIF sy-subrc <> 0.
 MESSAGE 'Error in authority check' TYPE 'A'.
ELSE.
 IF sy-ucomm = 'ONLI'.
 CALL SELECTION-SCREEN '0500'.
 ENDIF.
ENDIF.
AT SELECTION-SCREEN.
IF sy-dynnr = '0500'.
 IF s_conn IS INITIAL.
 MESSAGE 'Please enter values' TYPE 'W'.
 ELSE.
 SELECT *
 FROM sflight
 INTO TABLE sflight_tab
 WHERE carrid = p_carrid AND
 connid IN s_conn.
 IF sy-subrc <> 0.
 MESSAGE 'No flights found' TYPE 'E'.
 ENDIF.
 ENDIF.
ENDIF.
Main program
START-OF-SELECTION.

Creating Cpmplecated screen in report program

hi,
We have requirement of creating report program with complecated screen design.This screen can be created easily in Dialog programming .I want to create similar screen in report program .
Please suggest how can I achieve this.
Thanks
Saurabh

Hi,
In the report program,
parameters: a type i.
now go to se51 enter the name of your program and screen no as 1000 and do the required changes as per the requirement.
if you execute the report, whatever you modified by using se51 will come.

Change Type of Screen Element in Report Program

Okay guys, I have been struggling with this the whole day.. someone please help me.
I have a selection screen defined in the selecton-screen of a report program
select-options : so_matnr for mara-matnr,
 so_ebeln for ekpo-ebeln,
 so_ebelp for ekpo-ebelp.
Now if I go to SE51 and give the program name and the screen number as 1000 (Default screen for report)
Now go to tab "Element List" --> "General Attributes"
in the column "Type of screen element" everything is considered as "I/O".
*Name* *Type of Screen Element*
%_SO_MATNR_%_APP_%-TEXT I/O
%_SO_MATNR_%_APP_%-OPTI_PUSH I/O
SO_MATNR-LOW I/O
%_SO_MATNR_%_APP_%-TO_TEXT I/O
SO_MATNR-HIGH I/O
%_SO_MATNR_%_APP_%-VALU_PUSH Push
%_SO_EBELN_%_APP_%-TEXT I/O
%_SO_EBELN_%_APP_%-OPTI_PUSH I/O
SO_EBELN-LOW I/O
%_SO_EBELN_%_APP_%-TO_TEXT I/O
SO_EBELN-HIGH I/O
%_SO_EBELN_%_APP_%-VALU_PUSH Push
%_SO_EBELP_%_APP_%-TEXT I/O
%_SO_EBELP_%_APP_%-OPTI_PUSH I/O
SO_EBELP-LOW I/O
%_SO_EBELP_%_APP_%-TO_TEXT I/O
SO_EBELP-HIGH I/O
Now, my requirement is that I need to do something at the loop at screen to change the 'I/O' to 'Text' for all the %TEXT% screen fields. Exactly behave like text labels in the dialog program
Now, I don't want to write a dialog program to achieve this. Is there any thing i can do in the report program to achieve it.

Hello,
Try something like this:
INITIALIZATION.
loop at screen.
if screen-name eq <your field>
 screen-input = 0.
 modify screen.
endif.
endloop.
The important thing is to do it on INITIALIZATION event
Gabriel P.-

Report programming

Hi all,
i am a beginner in ABAP,plz explain me clearly about the events in report programming.
thanks,
jetti.

List Events in an ABAP Program
After a user interaction on a list, the ABAP runtime environment checks whether it should process the function code itself (for example, %EX or %PC), or whether it should trigger the relevant event. Unlike normal screens, in which the PAI event is triggered, the runtime environment triggers three special events when list events occur. You can use the corresponding event blocks in your ABAP program to react to the user action. From within the program, you can use the SY-UCOMM system field to access the function code. There is no OK_CODE field that is filled.
Event Blocks for Function Codes PF<nn> (Obsolete)
When the user chooses a function code PF<nn> (<nn> can be between 01 and 24), the system always triggers the AT PF<nn> event. In the standard list status, the function keys F<nn> that are not reserved for predefined system functions all have the function code PF<nn> as long as a corresponding event block is defined in the program.
AT PF<nn>.
<statements>.
These event blocks are executed when the user chooses the corresponding function key. The position of the cursor in the list is irrelevant.
If you use these event blocks at all, it should only be for temporary test versions. In production programs, you should only use AT USER-COMMAND with a dialog status of your own to assign function codes to function keys. When you use your own interfaces, the system displays a function text explaining what the function does. This does not happen when you use AT PF<nn> event blocks.
Event Block for Function Code PICK
When the user triggers the function code PICK, AT LINE-SELECTION is always triggered if the cursor is positioned on a list line. The function code PICK is, by default, always linked with function key F2 and hence with the mouse double-click. Consequently, if you have a simple program that does not react to any further user actions, you only need to write this event block.
AT LINE-SELECTION.
<statements>.
As described in the section Dialog Status for Lists, the function code PICK is always added to the standard list status when you have an AT LINE-SELECTION event in your program.
If you assign PICK to other function keys or menu entries, AT LINE-SELECTION is also triggered when the user chooses then. You should avoid this for the sake of the semantics.
Conversely, if you have a more extensive program that does not react to line selection, you should not use the function code PICK. Instead you should assign a different function code to F2 , to ensure that as many events as possible trigger the AT USER-COMMAND event.
Event Block for User-Defined Function Codes
If the user chooses a function code during list processing that is neither processed by the system, or PICK or PF<nn>, the system triggers the event AT USER-COMMAND. For this event, you must define your own GUI status for a list. To react to your own function codes in a program, you must define the following event block:
AT USER-COMMAND.
<statements>.
In this event block, you can use an IF or CASE structure to tell the function codes apart. They are available in the system field SY-UCOMM. There are further system fields that are filled in list events, such as SY-LSIND and SY-PFKEY, that allow you to make further case distinctions.
Triggering a List Event from the Program
You can trigger a list event from the program as follows:
SET USER-COMMAND <fc>.
This statement takes effect after the current list is completed. Before the list is displayed, the event assigned to function code <fc> is triggered, regardless of the dialog status you are using.
The effect is the same as when the user chooses the function. In other words, predefined list function codes are trapped and processed by the runtime environment, the function codes PICK and PF<nn> trigger the AT LINE-SELECTION and AT PF<nn> events, and user-defined function codes trigger the AT USER-COMMAND event block.
Function code PICK triggers an event only if the cursor is located on a list line.
Using this statement in conjunction with the function codes reserved for system functions, you can call the system functions from the program. For example, you can use SET USER-COMMAND '%SC' to call the Find dialog box directly, or to position the list correctly before it is displayed.
If you use several SET USER-COMMAND statements while creating a list, the system executes only the last one.
Examples
Example for AT LINE-SELECTION.
REPORT demo_list_at_line_selection.
START-OF-SELECTION.
WRITE 'Basic List'.
AT LINE-SELECTION.
WRITE: 'Secondary List by Line-Selection',
 / 'SY-UCOMM =', sy-ucomm.
When you run the program, the basic list appears with the standard list status. The detail list shows that SY-UCOMM has the value PICK.
Example for AT PF<nn>.
REPORT demo_list_at_pf.
START-OF-SELECTION.
WRITE 'Basic List, Press PF5, PF6, PF7, or PF8'.
AT pf5.
PERFORM out.
AT pf6.
PERFORM out.
AT pf7.
PERFORM out.
AT pf8.
PERFORM out.
FORM out.
WRITE: 'Secondary List by PF-Key Selection',
 / 'SY-LSIND =', sy-lsind,
 / 'SY-UCOMM =', sy-ucomm.
ENDFORM.
After executing the program, the system displays the basic list. The user can press the function keys F5 , F6 , F7 , and F8 to create secondary lists. If, for example, the 14th key the user presses is F6 , the output on the displayed secondary list looks as follows:
Secondary List by PF-Key Selection
SY-LSIND = 14
SY-UCOMM = PF06
Example for AT USER-COMMAND.
REPORT demo_list_at_user_command NO STANDARD PAGE HEADING.
START-OF-SELECTION.
WRITE: 'Basic List',
 / 'SY-LSIND:', sy-lsind.
TOP-OF-PAGE.
WRITE 'Top-of-Page'.
ULINE.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE sy-pfkey.
 WHEN 'TEST'.
 WRITE 'Self-defined GUI for Function Codes'.
 ULINE.
ENDCASE.
AT LINE-SELECTION.
SET PF-STATUS 'TEST' EXCLUDING 'PICK'.
PERFORM out.
sy-lsind = sy-lsind - 1.
AT USER-COMMAND.
CASE sy-ucomm.
 WHEN 'FC1'.
 PERFORM out.
 WRITE / 'Button FUN 1 was pressed'.
 WHEN 'FC2'.
 PERFORM out.
 WRITE / 'Button FUN 2 was pressed'.
 WHEN 'FC3'.
 PERFORM out.
 WRITE / 'Button FUN 3 was pressed'.
 WHEN 'FC4'.
 PERFORM out.
 WRITE / 'Button FUN 4 was pressed'.
 WHEN 'FC5'.
 PERFORM out.
 WRITE / 'Button FUN 5 was pressed'.
ENDCASE.
sy-lsind = sy-lsind - 1.
FORM out.
WRITE: 'Secondary List',
 / 'SY-LSIND:', sy-lsind,
 / 'SY-PFKEY:', sy-pfkey.
ENDFORM.
When you run the program, the system displays the following basic list with a the page header defined in the program:
You can trigger the AT LINE-SELECTION event by double-clicking a line. The system sets the status TEST and deactivates the function code PICK. The status TEST contains function codes FC1 to FC5. These are assigned to pushbuttons in the application toolbar. The page header of the detail list depends on the status.
Here, double-clicking a line no longer triggers an event. However, there is now an application toolbar containing five user-defined pushbuttons. You can use these to trigger the AT USER-COMMAND event. The CASE statement contains a different reaction for each pushbutton.
For each interactive event, the system decreases the SY-LSIND system field by one, thus canceling out the automatic increase. All detail lists now have the same level as the basic list and thus overwrite it. While the detail list is being created, SY-LSIND still has the value 1.
Example for SET USER-COMMAND.
REPORT demo_list_set_user_command NO STANDARD PAGE HEADING.
START-OF-SELECTION.
SET USER-COMMAND 'MYCO'.
WRITE 'Basic List'.
AT USER-COMMAND.
CASE sy-ucomm.
 WHEN 'MYCO'.
 WRITE 'Secondary List from USER-COMMAND,'.
 WRITE: 'SY-LSIND', sy-lsind.
 SET USER-COMMAND 'PF05'.
ENDCASE.
AT pf05.
WRITE 'Secondary List from PF05,'.
WRITE: 'SY-LSIND', sy-lsind.
SET CURSOR LINE 1.
SET USER-COMMAND 'PICK'.
AT LINE-SELECTION.
WRITE 'Secondary List from LINE-SELECTION,'.
WRITE: 'SY-LSIND', sy-lsind.
SET USER-COMMAND '%SC'.
This program creates one basic list and three detail lists. When the program starts, the third detail list is displayed immediately, along with a dialog box for searching in the list. The dialog box is displayed by setting the predefined function code %SC. To view the other lists, the user chooses Back.
Note that in the event AT PF05, the SET CURSOR statement is used to position the cursor on a list line in order to support the function code PICK.

Help needed in report programming

Hi All
I am processing some data on first screen of a report transaction and an output is displayed on second screen. My requirement is that when I press back, I have to come to SAP initial screen.
I have tried all options with 'LEAVE'. Problem is that control doesnt come even once in report, it goes into some standard code so I am unable to make changes..
Kindly help.
Thanks
Dinesh
<LOCKED BY MODERATOR - USE APPROPRIATE TITLES>
<LOCKED BY MODERATOR - URGENT, PLEASE HELP OR SIMILAR ARE FORBIDDEN>
Edited by: Alvaro Tejada Galindo on Aug 18, 2008 5:17 PM

Hi,
Since it is a report program. U have to set PF status in ur output page (either ALV or any other output format).
In GUI status, triger the function code for BACK.
Then, inside the event AT USER-COMMAND, code LEAVE PROGRAM for the BACK function.
If it is an ALV output, the PF-status and User-command event should be called in the ALV function module.
Regards,
Prem

In Dialog module programing how to navigate to previous screens?

I have a REPORT program which displays a ALV output with custom menu buttons along with the ALV buttons on the menu bar.
Once the custom button is clicked the REPORT program calls a custom SCREEN 1 the screen is displayed to the user and the screen has a custom menu which has some custom buttons.
if the user selects any button the user is taken to the next SCREEN 2 .
My Problm is when the processing is finished on the SCREEN 2 i would like the system to retrurn back to report out put screen and NOT on SCREEN 1.
If i use the bwlow code in SCREEN 2 - PAI event it just returns me back to SCREEN 1 and not to the report output screen.
SET SCREEN 0.
LEAVE SCREEN.
What coding needs to be done to return me back to the REPORT output screen from SCREEN 2.

Hi,
there is also possibility to specify LEAVE TO LIST-PROCESSING.
Please check following link
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
Regards,
Karol
Edited by: Karol Seman on Oct 29, 2008 9:39 PM

Problem WIth Variant in a report program

I have a z report program with couple of variants , the problem is the varaints display onlt name of the variant and description when the varaint button is pressed.
The changed by , date etc details are not getting displayed.
Thanks
Arun

Hi Arun,
You will not get those data directly from the program execution screen. If you want to get those details, please check table VARID for that variant or program.
Regards,
Sourav

Can we create purchase order through report programming?

hi experts.....
can we create purchase order through report programming?If yes plz give me the thread details?

Hi,
Use this code in a program by using a BAPI function module
Anothe rway is using classical/ALV report using call transaction from a report for changing the PO
loop at i_header.
    header-ref_1         = i_header-legacy.
    headerx-ref_1        = c_x.
    header-doc_type      = i_header-bsart.
    headerx-doc_type     = c_x.
    header-comp_code     = i_header-bukrs.
    headerx-comp_code    = c_x.
    header-purch_org     = i_header-ekorg.
    headerx-purch_org    = c_x.
    header-pur_group     = i_header-ekgrp.
    headerx-pur_group    = c_x.
    header-vendor        = i_header-lifnr.
    headerx-vendor       = c_x.
    concatenate i_header-bedat+4(4)
                i_header-bedat+0(2)
                i_header-bedat+2(2)
                into header-doc_date.
    headerx-doc_date     = c_x.
    header-created_by    = i_header-ernam.
    headerx-created_by   = c_x.
    header-currency      = i_header-waers.
    headerx-currency     = c_x.
    concatenate i_header-kdatb+4(4)
                i_header-kdatb+0(2)
                i_header-kdatb+2(2)
                into header-vper_start.
    headerx-vper_start   = c_x.
    loop at i_items where legacy = i_header-legacy.
      item-po_item            = i_items-ebelp.
      itemx-po_item           = i_items-ebelp.
      itemx-po_itemx          = c_x.
      if i_header-bsart = 'NB'.
        item-material            = i_items-ematn.
        itemx-material           = c_x.
        schedule-quantity        = i_items-menge * 1000.
        schedulex-quantity       = c_x.
      else.
        item-short_text          = i_items-ematn.
        itemx-short_text         = c_x.
        item-matl_group          = '1000'.
        itemx-matl_group         = c_x.
        schedule-quantity        = '1'.
        schedulex-quantity       = c_x.
      endif.
      item-plant               = i_items-werks.
      itemx-plant              = c_x.
      schedule-po_item         = i_items-ebelp.
      schedule-sched_line      = '1'.
      schedulex-po_item        = i_items-ebelp.
      schedulex-sched_line     = '1'.
      schedulex-po_itemx       = c_x.
      schedulex-sched_linex    = c_x.
      concatenate i_items-eildt+0(2)
                   i_items-eildt+2(2)
                   i_items-eildt+4(4)
                   into schedule-delivery_date.
      schedulex-delivery_date = c_x.
      item-price_unit          = i_items-peinh * 100.
      itemx-price_unit         = c_x.
      item-tax_code            = i_items-mwskz.
      itemx-tax_code           = c_x.
      item-shipping            = i_items-evers.
      itemx-shipping           = c_x.
      account-po_item          = i_items-ebelp.
      accountx-po_item         = i_items-ebelp.
      accountx-po_itemx        = c_x.
      if i_header-bsart = 'FO'.
        item-pckg_no = sy-tabix.
        itemx-pckg_no = 'X'.
        limits-pckg_no        = sy-tabix.
        limits-limit          = i_items-overalllimit.
        limits-exp_value      = i_items-expectedoverall.
        posrvaccessvalues-pckg_no    = sy-tabix.
        posrvaccessvalues-line_no    = '0'.
        posrvaccessvalues-serno_line = '00'.
        posrvaccessvalues-percentage = '100.0'.
        posrvaccessvalues-serial_no = '01'.
        account-serial_no     = '1'.
        accountx-serial_no    = '1'.
        accountx-serial_nox   = c_x.
        account-quantity = '1'.
        accountx-quantity = c_x.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
          exporting
            input = i_items-kostl
          importing
            output = account-costcenter.
        accountx-costcenter   = c_x.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
          exporting
            input = i_items-sakto
          importing
            output = account-gl_account.
        accountx-gl_account   = c_x.
        item-acctasscat       = i_items-knttp.
        itemx-acctasscat      = c_x.
        item-item_cat         = i_items-epstp.
        itemx-item_cat        = c_x.
      endif.
      append:item,itemx,schedule,schedulex,account,accountx,limits,posrvaccessvalues.
      clear :item,itemx,schedule,schedulex,account,accountx,limits,posrvaccessvalues.
    endloop.
    call function 'BAPI_PO_CREATE1'
      exporting
        poheader                     = header
        poheaderx                    = headerx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
        importing
        exppurchaseorder             = ponumber
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
        tables
        return                       = return
        poitem                       = item
        poitemx                      = itemx
*   POADDRDELIVERY               =
        poschedule                   = schedule
        poschedulex                  = schedulex
        poaccount                    = account
*   POACCOUNTPROFITSEGMENT       =
        poaccountx                   = accountx
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
        polimits                     = limits
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
   posrvaccessvalues            = posrvaccessvalues.
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
    if ponumber eq space.
      loop at return where type = 'E'.
        clear buffer.
        move-corresponding return to e_return.
        concatenate i_header-legacy e_return into buffer.
        transfer buffer to p2_file.
      endloop.
      move-corresponding i_header to i_eheader.
      transfer i_eheader to p3_file.
      loop at i_items where legacy = i_header-legacy.
        move-corresponding i_items to i_eitems.
        transfer i_eitems to p4_file.
      endloop.
    else.
      commit work and wait.
    endif.
    clear:ponumber,header,headerx,item,itemx,account,accountx,limits,return,schedule,schedulex,posrvaccessvalues.
    refresh:item,itemx,account,accountx,limits,return,schedule,schedulex,posrvaccessvalues.
endloop.
close dataset p2_file.
close dataset p3_file.
close dataset p4_file.
Regards
Krishna

Calling a ALV Report program via a Remote Function module.

H All,
The thing which I am looking out for is ,to know a technique to acheive this,
To start with,
For the transaction MB51-(Material Document List),which is a Report Program "RM07DOCS",I also observed that this uses a ALV to display the output.
Now what I actually require is another extra field (from MARA table ) along with the standard output that is displayed from this report.
Also this needs to be passed to a different UI system(build using VC ).
So I have a RFC eg DisplayList(),where in I need to exeucte this report program ,get the output what it gives ,add my additional information what I want to and pass it as a export parameter,
So this is the structure which I can visualise,
FUNCTION ZFUN_MB51TXN.
I would get all the import parameters here ,from who ever is calling my fun module,
*Call the report program,pass the input parameters required
*get the output from this report program
*send the output to the caller through export parameters
ENDFUNCTION.
So Here I need to know ,Can this be achieved something using Submit report or anything,Any guidelines to move further would be really of great help!

Hi All,
It would really be great if you can explain with the reference to the same report program,the same selection screen elemetns or something.
Thanks,
Archies!

Dialog & Report Programming!

Similar Messages

Maybe you are looking for