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

reports

Former Member
0 Likes
1,073

Can we call a report from another report ?? if we can call can you please tell me how to do that.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,036

Hi

use submit

SUBMIT <PROGRAMNAME> AND RETURN.

SUBMIT <PROGRAMNAME> WITH p_werks = p_werks "parameters

AND RETURN.

SUBMIT <PROGRAMNAME> WITH p_werks = p_werks

WITH SELECTION-TABLE <seltab> AND RETURN. "select options

SUBMIT (sy-repid) WITH p_werks = p_werks

WITH SELECTION-TABLE <seltab> AND RETURN. "in case same program

Regards

9 REPLIES 9
Read only

Former Member
0 Likes
1,037

Hi

use submit

SUBMIT <PROGRAMNAME> AND RETURN.

SUBMIT <PROGRAMNAME> WITH p_werks = p_werks "parameters

AND RETURN.

SUBMIT <PROGRAMNAME> WITH p_werks = p_werks

WITH SELECTION-TABLE <seltab> AND RETURN. "select options

SUBMIT (sy-repid) WITH p_werks = p_werks

WITH SELECTION-TABLE <seltab> AND RETURN. "in case same program

Regards

Read only

Former Member
0 Likes
1,036

Hi,

we can call one report(executable) from another report.

for that use the command SUBMIT 'zrep'.

for more info refer this link

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9dd035c111d1829f0000e829fbfe/content.htm

rgds,

bharat.

Read only

former_member188827
Active Contributor
0 Likes
1,036

if da report doesnt have a tcode u can use submit statement.

if it has a tcode , u can also use call transaction

Read only

Former Member
0 Likes
1,036

Yes u can, by the submit statement,here is an example

  • Transferring control to report /FIR/SAPURF2S0BGS_SPS for *

  • processing of process orders based on the various ranges *

  • that are created above.

SUBMIT /fir/sapurf2s0bgs_sps WITH s_vbeln IN s_vbeln

WITH s_posnr IN r_posnr

WITH s_ebeln IN r_ebeln

WITH s_vbeln IN r_vbeln

WITH s_werks IN r_werks

WITH s_auart IN r_auart

WITH s_bsart IN r_bsart

WITH s_matnr IN r_matnr

WITH s_mbdat IN r_due

WITH s_mtart-low EQ space

WITH p_lgnum EQ space

WITH s_lgtyp-low EQ space

AND RETURN.

Read only

former_member188827
Active Contributor
0 Likes
1,036

SUBMIT {rep|(name)} [selscreen_options]

[ list_options ]

[ job_options]

[AND RETURN].

Addition:

... AND RETURN

Effect

The SUBMIT statement accesses an executable program rep. The executable program is executed as described under Calling Executable Reports.

The program name rep can either be specified directly or as the content of a character-like data object name. The data object name must contain the name of the program to be accessed in block capitals. If the program specified in name is not found, an irretrievable exception is generated.

The selscreen_options additions can be used to determine the selection screen for the program accessed and to supply it with values.

The list_options additions allow you to influence the output medium and the page size in the basic list for the program accessed.

You can schedule the program for background processing by specifying job_options.

Addition

... AND RETURN

Effect

The AND RETURN addition determines the object accessed by the runtime environment after program access is completed:

Without the AND RETURN addition, the internal session of the program accessed replaces the internal session of the calling program in the same position in the call sequence. Once program access is completed, the system returns to before the position from which the calling program was started.

As of Release 6.10, the content of the system field sy-calld at SUBMIT is copied by the calling program without AND RETURN. Before 6.10, the system entered the value "X", which was incorrect when the program was accessed from the first program in a call sequence.

The addition AND RETURN starts the executable program in a new internal session. The session for the calling program is retained. Once program access is completed, program execution for the calling program continues after the SUBMIT statement.

Note

When the SUBMIT statement is executed, the system runs an authorization check for the authorization group specified in the program attributes.

Read only

Former Member
0 Likes
1,036

Use submit and program name in capital.

anya

Read only

former_member188827
Active Contributor
0 Likes
1,036

CALL TRANSACTION ta { [AND SKIP FIRST SCREEN]

| [USING bdc_tab [bdc_options]] }.

Extras:

1. ... AND SKIP FIRST SCREEN

2. ... USING bdc_tab [bdc_options]

Effect

The statement CALL TRANSACTION calls the transaction whose transaction code is contained in data object ta. The data object ta must be of character type and must contain the transaction code in uppercase letters. If the transaction specified in ta cannot be found, an untreatable exception is triggered. The additions suppress the display of the initial screen and allow you to execute the transaction using a batch input session.

Read only

Former Member
0 Likes
1,036

hi,

use the SUBMIT command to call another report.

another report name should be in capitals.

if ur report has s tcode u can use even CALL TRANSACTION too

Read only

Former Member
0 Likes
1,036

hi,

To start an executable (type 1) program, use the SUBMIT statement.

If you use the VIA SELECTION-SCREEN addition, the system displays the standard selection screen of

the program (if one has been defined).

If you use the AND RETURN addition, the system resumes processing with the first statement after the

SUBMIT statement once the called program has finished.

When you use the LEAVE TO TRANSACTION '<T_CODE>' statement, the system terminates the current

program and starts the transaction with transaction code <T_CODE>. The statement is the equivalent of

entering /n<T_CODE> in the command field.

CALL TRANSACTION '<T_CODE>' allows you to insert an ABAP program with a transaction code into the

call chain.

To terminate an ABAP program, use the LEAVE PROGRAM statement. If the statement occurs in a

program that you called using CALL TRANSACTION '<T_CODE>' or SUBMIT <prog_name> AND

RETURN, the system resumes processing at the next statement after the call in the calling program. In all

other cases, the user returns to the application menu from which he or she started the program.

If you use the …AND SKIP FIRST SCREEN addition, the system does not display the screen contents of

the first screen in the transaction. However, it does process the flow logic.

If you started a transaction using CALL TRANSACTION that uses update techniques, you can use the

UPDATE… addition to specify the update technique (asynchronous (default), synchronous, or local) that

the program should use.

Submit sapbc402_tabd_hashed

WITH pa_city = sdyn_conn-cityfrom

WITH pa_ctry = sdyn_conn-countryfr

AND RETURN.

The WITH addition in the SUBMIT statement allows you to assign values to the fields on a standard

selection screen. The abbreviations "EQ, NE, … , I, E" have the same meanings as with select-options.

If you want to pass several selections to a selection option, you can use the RANGES statement instead of

individual WITH additions. The RANGES statement creates a selection table, which you can fill as though it

were a selection option. You then pass the whole table to the executable program.

If you want to display the standard selection screen when you call the program, use the

VIA SELECTION-SCREEN addition.

When you use the SUBMIT statement, use the Pattern function in the ABAP Editor to insert an appropriate

statement pattern for the program you want to call. It automatically suppplies the names of the parameters

and selection options that are available on the standard selection screen.

Hope this helps, Do reward.