topic Re: Passing internal table values from module pool to report in Application Development and Automation Discussions

Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 11:35:23 GMT

Hi friends,

I designed my selection screen in module pool program and i wrote all internal table logics in report program.

i passed that input values by using export / import using memory ID . i gave same name for internal table in both programs.

But values is not passing to that report.

Thanks,

Meenachi.R

Re: Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 11:42:30 GMT

can copy the code or debug and analyze it u can understand where and what the problem

Regards

Mahesh

Re: Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 11:44:10 GMT

Hi Meenachi,

I do not understand why you have to use Export/Import for transferring values. If you are working on a module pool you can just declare the internal tables in the TOP include. Then it will be available throughout the program.

Also the input values in the screen would be transferred to the program on PAI and Vice versa on PBO if you have declared same type variables of screen fields in the TOP include.

If you are trying to do something else, let us know clearly what you are doing.

Regards,

Karthik D

Re: Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 11:50:19 GMT

Thanks mahesh

Re: Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 11:54:15 GMT

Thanks karthik..

I am using module pool as selection screen. i want to pass the selection screen values to another existing report.how to pass the values?

Meenachi.R

Re: Passing internal table values from module pool to report

RaymondGiuseppi — Fri, 18 May 2012 12:01:35 GMT

Export to/Import from memory should work, can you paste the coding of those statements in both your programs. Also have you checked that both programs actually execute those statements.

Regards,

Raymond

NB: The ITAB name can differ, you could have used a EXPORT tab FROM itab1 and IMPORT tab TO itab2 syntax.

Re: Passing internal table values from module pool to report

ThomasZloch — Fri, 18 May 2012 12:07:01 GMT

Sounds like an awkward design, why so complicated?

Thomas

Re: Passing internal table values from module pool to report

Former Member — Fri, 18 May 2012 12:25:42 GMT

Thanks Thomas..

Requirement is like that..

Selection screen should be in module pool and report should display in classical.

in module pool write statement should not work right!!

Meenachi.R

Re: Passing internal table values from module pool to report

RaymondGiuseppi — Fri, 18 May 2012 12:33:24 GMT

WRITE statements works in module pool, of course you will be required to explicitaly leave to LIST-PROCESSING, but it works.

Ref: Using LEAVE TO LIST-PROCESSING

Regards,

Raymond

Re: Passing internal table values from module pool to report

former_member210621 — Fri, 18 May 2012 13:07:48 GMT

Hi Meenachi,

If you have to use the internal table created on selection screen and use in the report, you can also design the same selection screen in report also. Then there will be no need to pass internal table.

Just handle Events carefully during execution.

--Regards

- Ketan

Re: Passing internal table values from module pool to report

Former Member — Sat, 19 May 2012 02:30:06 GMT

Hi,

You told that your module pool selection screen will be connected to an EXISTING report? Is this report has PBO and PAI?

Jake.

Re: Passing internal table values from module pool to report

Former Member — Mon, 21 May 2012 09:16:07 GMT

Thanks Raymond