topic Re: SUBMIT Statement problem in Application Development and Automation Discussions

SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 05:01:00 GMT

Hi guyz,

I am trying to call program RPCAWSR0 using SYBMIT statement by sending variant as well as employee nos. But i am able to see only variant values not able to see the employee no which i am passing from calling program.

Can anybody give me solution to get it done .Code using is

<b>submit rpcawsr0

via selection-screen

using selection-set l_variant

with pernr in pnppernr.</b>

Thanks,

Venkat.O

Re: SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 05:20:42 GMT

SUBMIT

Basic forms:

1. SUBMIT rep.

2. SUBMIT (name).

Extras:

1. ... LINE-SIZE col

2. ... LINE-COUNT line

3. ... TO SAP-SPOOL List output to the SAP spool database

4. ... USING SELECTION-SCREEN scr

5. ... VIA SELECTION-SCREEN

6. ... AND RETURN

7. ... EXPORTING LIST TO MEMORY

8. ... USER user VIA JOB job NUMBER n

9. ...Various additions for passing parameters to rep

10. ... USING SELECTION-SETS OF PROGRAM prog

Effect

Calls report rep.

The system leaves the active program and starts the new report rep. In basic form 2, you can specify the name of the report in the field name. You must specify the name in uppercase, otherwise a runtime error occurs.

Note

You can only start programs with type '1' using SUBMIT. If the program has a different type, the system triggers a runtime error.

Please consult Data Area and Modularization Unit Organization documentation as well.

Addition 1

... LINE-SIZE col

Effect

The list generated by the report has the line width col.

Addition 2

... LINE-COUNT line

Effect

The list generated by the report has line lines per page.

Addition 4

... USING SELECTION-SCREEN scr

Effect

When you execute the report, the system uses the selection screen number that you specify in the scr field. This must be a selection screen defined using the SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statements.If you omit the addition, the system uses the standard selection screen 1000.

This addition allows you to start the same report in different situations, using a different selection screen each time.

Notes

The addition VIA SELECTION SCREEN determines whether the report is processed in the foreground or the background.

What happens if the required screen does not exist or is not a selection screen?

Screen 1000:

If you want to use the standard selection screen (... USING SELECTION-SCREEN 1000 or do not specify a ... USING SELECTION-SCREEN) addition, the system does not process a selection screen.

Other selection screens:

The system triggers a runtime error.

Addition 5

... VIA SELECTION-SCREEN

Effect

The selection screen is displayed. In this case, the selection screen is displayed again after the report list has been displayed. The values entered by the user remain displayed.

Addition 6

... AND RETURN

Effect

Returns to the calling transaction or program after the called program has been executed. SUBMIT ... AND RETURN creates a new internal session.

Addition 7

... EXPORTING LIST TO MEMORY

Effect

Does not display the output list of the called report, but saves it in ABAP memory and leaves the called report immediately. Since the calling program can read the list from memory and process it further, you need to use the addition ... AND RETURN . Also, since the called report cannot be requested for printing, the addition ... TO SAP-SPOOL is not allowed here. In addition, you must not assign a function code to the ENTER key in the current GUI status. The saved list is read from the SAP memory using the function module 'LIST_FROM_MEMORY' and can then be saved to the database using EXPORT, for example. You can process this list further with the function modules 'WRITE_LIST', 'DISPLAY_LIST' ... of the function group "SLST".

Addition 8

... USER user VIA JOB job NUMBER n

Effect

Schedules the specified report in the job specified by the job name job and the job number n. The job runs under the user name user and you can omit the addition USER user. The assignment of the job number occurs via the function module JOB_OPEN (see also the documentation for the function modules JOB_CLOSE and JOB_SUBMIT). This addition can only be used with the addition ...AND RETURN.

Note

When scheduling a report with the SUBMIT ... VIA JOB job NUMBER n statement, you should always use the addition ...TO SAP-SPOOL to pass print and/or archive parameters. Otherwise, default values are used to generate the list and this disturbs operations in a production environment.

SY-SUBRC = 0:

Job scheduled successfully

SY-SUBRC = 4:

Job scheduling terminated by user

SY-SUBRC = 8:

Error in job scheduling (JOB_SUBMIT)

SY-SUBRC = 12:

Error in internal number assignment

Addition 10

... USING SELECTION-SETS OF PROGRAM prog

Effect

Uses variants of the program prog when executing the program rep.

Note

Important

The programs prog and rep must have the same SELECT-OPTIONS and PARAMETERs. Otherwise, variants of the program prog may be destroyed.

Note

When using this addition, the specified variant vari of the program prog is taken in USING SELECTION-SET vari. On the other hand, all variant-related actions on the selection screen of rep (Get, Save as variant, Display, Delete) refer to the variants of prog.

Example

SUBMIT REPORT01

VIA SELECTION-SCREEN

USING SELECTION-SET 'VARIANT1'

USING SELECTION-SETS OF PROGRAM 'REPORT00'

AND RETURN.

Rewards if useful...............

Minal

Re: SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 05:27:29 GMT

Hi Venkat,

First of all try and debug the program and see whether the values for the Pernr are being populated in the variable and if it is being passed with the submit statement.

Because at times,the declaration of the variable that you are passing has some issues with type compatibility.

You have mentioned

pernr in pnppernr.

In this case,while populating the variable to be passed to the next report must have the option LOW and HIGH populated.

In case you have any further clarifications,do let me know.

Regards,

Puneet Jhari.

Re: SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 05:27:46 GMT

change pernr to pnppernr as highlighted in bold

submit rpcawsr0

via selection-screen

using selection-set l_variant

with <b>pnppernr</b> in pnppernr.

Re: SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 05:36:11 GMT

Hi,

Is the employee.no you are passing should appear in the selection-screen of program RPCAWSR0 or it should be used some where during execution of RPCAWSR0 .

Need the above information to provide you the correct solution.

Regards,

Dilli

Re: SUBMIT Statement problem

Former Member — Wed, 19 Sep 2007 06:19:38 GMT

Hi,

My suggestion is to call the program RPCAWSR0 without passing the employee no in the submit statement. If you want to access the employee.no in the program RPCAWSR0 you can use memory for transferring the values.

Steps:

i) Export the employee no to the Memory ID before the submit statement.

Export pernr to memory id 'M001'.

ii) Call the program RPCAWSR0 using the submit statement

Submit rpcawsr0

via selection-screen

using selection-set l_variant.

iii) In the program RPCAWSR0, use import statement to import the value from memory id 'M001'.

Import pernr from memory id 'M001'.

By this way the employee.no can be made available to program RPCAWSR0.

The reason why you are not able to get the employee.no in the selection screen of the program rpcawsr0 is due to the fact that at a time only one(either variant or values for the selection-screen parameters/select-options) of the addition i)Using selection-set or ii) With pernr in pnppernr needs to be specified.

Do F1 help on Import and Export to know more about these statements.

Hope this helps....

Regards,

Dilli