IMPORT/EXPORT statement in Background Mode

[Former Member]

Hey dudes,

I am facing a problem in my coding. I am dealing with coding in several events in IS-U, transaction FPY1.

However, it's not so important ya. Now I am written some code on IMPORT and EXPORT some parameters between 2 program code. It's work very fine only in 'DEBUG MODE', but when it's running not debug mode (Is BACKGROUND MODE), coz it's massive run program.

I suspect it's because of the background job. Does background job using ABAP Memory? IMPORT/EXPORT is only for dialog work process, not background work process?? I have a lot of question mark on my head now..

Hope anyone facing dis issue before can help.

Cheers,

Isaac.

[Former Member]

Are you trying to pass data via EXPORT/IMPORT between two programs that are both running in background, or from an online session to a background process?... i.e. what are the two lots of program code that you are wanting to pass parameters between?

It would be fine for a background program to "export" data to a memory ID, then for the same batch program to submit another program that does the "import" from the same memory ID... but this method won't work for an online user doing an "export" and a batch job doing an "import" -> for this to work, you would need to persist the parameters so that the batch job can retrieve them.

If you can explain the scenario a bit more, will try to offer more help...

Jonathan

[Former Member]

Hi Jon,

Thanks a lot for your help.

I found the problem already. It's because I was checking on sy-tcode, whereas sy-tcode is blank on background processing.

Really appreciate your help man.

Cheers,

Isaac.

[Former Member]

An error cause by myself.

In conclusion:

I realize that SY-TCODE is blank for background job.

Thanks.

[Former Member]

This message was moderated.