topic Re: Sharing data between two background jobs in Application Development and Automation Discussions

Sharing data between two background jobs

itabhishek9 — Tue, 02 Nov 2010 15:40:00 GMT

Hi SDNites,

I am using export and import to transfer tables between programs. Now I wanted to schedule 2 instances of the same pgm in background.

Can you please tell me in this case will there be overlapping of the same ABAP memory used or not. My call on this is that yes this will happen. If this is the case then what would be the resolution for the same i.e. how can I share data between two programs and also can schedule the 2 instances without any problem.

Regards,

Abhi

Edited by: Thomas Zloch on Nov 2, 2010 5:22 PM - somewhat misleading subject corrected

Re: Sharing data between two background jobs

Former Member — Tue, 02 Nov 2010 15:52:50 GMT

Hi Abhishek,

Yes you are correct there will be overlap of the Memory may be it is ok in Development but not in all the system. In this kind of scenario please save the data in 2 different Memory ID'S (Locations).

Please create the memory id dynamically like 2 different instances then 2 diiferent memory ID's like (JOBNAME)

Make the Jobname to PROGRAM_1 (1ST instance) PROGRAM_2 (2ND instance).

Your statement should be

EXPORT ITAB TO MEMORY ID JOBNAME.

And the Program using the SY-BATCH value and FM "GET_JOB_RUNTIME_INFO" get the jobname and use the IMPORT Statement using the MEMORY ID as your jobname and make sure that you will free this MEMORY ID.


  IF NOT sy-batch IS INITIAL.

*--Function Module to get the Runtime Job details
    CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
      IMPORTING
        jobcount        = v_jobcount
        jobname         = v_jobname
      EXCEPTIONS
        no_runtime_info = 1
        OTHERS          = 2.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
IMPORT ITAB FROM MEMORY ID V_JOBNAME.
FREE MEMORY ID V_JOBNAME.
ENDIF.

Let me know if you need anything else on this.

Regards,

Srinivas

Re: Sharing data between two background jobs

roberto_vacca2 — Tue, 02 Nov 2010 15:59:24 GMT

Hi..

You can use instead a CALL FUNCTION 'ZFUNC_CUSTOM' WITH DESTINATION 'NONE' .. Pay attention to "Update Module" option in the attributes. This should be "Start Delayed" if you are calling in the background process.

Hope to be useful...

Re: Sharing data between two background jobs

Former Member — Tue, 02 Nov 2010 16:03:40 GMT

Abap memory works on session level, so if you schedule your program twice, those jobs will run in two different session, that means they can't see the same ABAP memory

Max

Re: Sharing data between two background jobs

Former Member — Tue, 02 Nov 2010 16:19:07 GMT

Hi Abishek,

There will be no overlapping as export and import memories scope is limited to the session lever only.

Hope this answer your query.

Regards

Bikas

Re: Sharing data between two background jobs

kesavadas_thekkillath — Tue, 02 Nov 2010 16:28:50 GMT

Use Shared Memory.

link:[EXPORT TO MEMORY/DATABASE/SHARED BUFFER|http://help.sap.com/saphelp_45b/helpdata/en/34/8e73a36df74873e10000009b38f9b8/frameset.htm]