Importing background jobs

Is there a way to import SAP background jobs from one client to another? In SM37, there ia an option to export the job, but I don't see an option to import it.
Thanks

Hi,
The 'export' option you see is just a possibility to export to Excel the table of jobs in the selection.
Regards,
Eli

Similar Messages

Rule set import - Background job did not run

Hi,
I am setting up my CC 5.2 production system. I have downloaded from ruleset from the dev CC and imported it into production. However the background job generated did not run. I am implementing SAP note 999785 to fix this, but am wondering what should I do about the rule set? Do I need to delete the rule set and reimport it? As this background job did not run I notice that the permission rules did not generate.
Any advice is welcome.
Thanks

Hi,
as the backgorund job never ran and no rules were created, I can just reimport the ruleset and let the job run. I have tried this and the rules were created successfully

Scheduled TMS_ # TMS_TP_IMPORT background jobs fail with error code 0232

Is anyone else having the problem we've just encountered since upgrading to ECC 6.0 and CRM 2007, where once setting up the automatic import ALL background jobs, to have all of the Transport Change Requests imported into the Q-Prod testing systems automatically, fail after several successful runs?
After setting up the automatic import background job to run every 15 minutes, the first few run successfully (importing any transports as it should), then the transports stop being imported.
The background jobs continue to run, but have the following in the job log overviews CRM 2007 - "Could not start transport control program tp". R\3 ECC 6.0 - "Transport control program tp ended with error code 0232".
Only by deleting the background job and recreating it (or manually importing) from STMS, can the transports continue to be imported. Although I have noticed that there are multiple tp.exe processes started, which need to be deleted before the STMS and TMS Background jobs work again.
The:
   DB is SQL Server 2005
   disp+work is at version 7000.150.14.48855
   R3Trans is at version 7000.149.14.47907
   tp is at version 7000.144.14.39594
Any suggestions on how to cure this for good?

Thanks All
FYI
SAP first suggested the following notes: 19466, 1150361, and to add a Startup profile parameter rfc/use_gwstart = 1. Which was only partially successful.
I guess it had more to do with RFC processes hanging than it did with the tp, which was fixed in a later kernel patch level.
I've upgraded the kernel to the latest (70000.181.0.0) and my problem was fixed.
Ken

Is there any way to restart Cancled Background job

Dears,
Now we have a very important background job need to run everyday, but sometime it will be canceled due to memory is not enough.
Is there any way to restart Cancled Background job automatically ?
Thanks,
Michael

Hi Michael,
To start the cancelled job manually
At SM37 just mark the job then click Job -> Change and just reschedule.
For auto
Create another job with same program name and variant , then create background processing event which gets trigger only when your job gets failed.
For Event Creation kindly reach out to ABAPers and for Event based Scheduling you can contact basis team.
BR Vaibhav

EXPORT - IMPORT in BACKGROUND JOB

Hello ABAP Gurus,
There are two programs I am using.
In 1st Program I am Exporting the Data to the ABAP Memory and then after that scheduling the second program in background from 1st Program through
1 ) JOB_OPEN
2 ) SUBMIT
3 ) JOB_CLOSE
Now I am trying to Import the data that is Exported in the second program which is scheduled in background.
But I am not able to Import it.
My question is that - Does EXPORT - IMPORT Statements works in such scenario when background job is scheduled.
As it is working fine if, I only submits and does not put in the Background JOB.
Looking forward for the answer.
Helpful answers will definately be awarded.
Thanks in Advance
Sudhanshu Garg

Hi Sudhanshu,
Export/import to memory uses ABAP memory which will not be accessible by the background job.
No need of creating the structures in dictionary
You can use the Table INDX for storing your data in the database.
See the link below for an example.
http://help.sap.com/saphelp_45b/helpdata/en/34/8e73a36df74873e10000009b38f9b8/content.htm

QA Approval - importing queue with background jobs

Hi all,
I have activated the QA approval in my system and it all works fine. I have scheduled a background job via STMS to import the whole test system buffer each day and this works fine too. Now I want to schedule a background job to import the production buffer automatically too. This would allow us to have all approved transports automatically imported once a day (as QA approval is activated only approved transports would be imported).
Sounds simple, but with QA approval the production buffer displays approved and non-approved requests, so the background job fails as not all transports in the buffer are in the correct status.
Any suggestions on how I can get around this problem?
Thanks
Claire.

Hello Claire,
This issue has been described in SAP Note 313991. please check.
Regards,
Debasis

Importing SAP background Jobs to CPS

Hi,
We have installed free version of SAP CPS for testing. We are able to create new job through SAP CPS on Backend system.
But how to import existing jobs from backend SAP (AS ABAP) system to SAP CPS
Thanks and Regards,
Yash

Hi,
The import creates definitions in CPS that match the definitions of the jobs in SAP, you can find these under "Job Definitions" or under "Job Chains" (depending if it was a single step or multi-step job).
If you want to start running the job from CPS, you need to submit the corresponding job definition in CPS with the desired scheduling parameters and put the one directly in SAP on hold or remove it all together.
Based on your questions, monitoring of SAP jobs by CPS could also be of interest to you.
You can find more information on both topics in the administration guide that comes with the product (under the "i" icon in the user interface).
Regards,
Anton.

Problems creating background job for program (job open, submit and close)

Hi gurus,
im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
Below goes my code,
any ideas will be rewarded
CLEAR: stdt_modify_type, stdt_output.
CALL FUNCTION 'BP_START_DATE_EDITOR'
       EXPORTING
            stdt_dialog                    = 'Y'
            stdt_input                     = stdt_input
            stdt_opcode                    = 14
       IMPORTING
            stdt_modify_type               = stdt_modify_type
            stdt_output                    = stdt_output
       EXCEPTIONS
            fcal_id_not_defined            = 1
            incomplete_last_startdate      = 2
            incomplete_startdate           = 3
            invalid_dialog_type            = 4
            invalid_eventid                = 5
            invalid_opcode                 = 6
            invalid_opmode_name            = 7
            invalid_periodbehaviour        = 8
            invalid_predecessor_jobname    = 9
            last_startdate_in_the_past     = 10
            no_period_data_given           = 11
            no_startdate_given             = 12
            period_and_predjob_no_way      = 13
            period_too_small_for_limit     = 14
            predecessor_jobname_not_unique = 15
            startdate_interval_too_large   = 16
            startdate_in_the_past          = 17
            startdate_is_a_holiday         = 18
            startdate_out_of_fcal_range    = 19
            stdt_before_holiday_in_past    = 20
            unknown_fcal_error_occured     = 21
            no_workday_nr_given            = 22
            invalid_workday_countdir       = 23
            invalid_workday_nr             = 24
            notbefore_stdt_missing         = 25
            workday_starttime_missing      = 26
            no_eventid_given               = 27
            OTHERS                         = 28.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MOVE 'X' TO gv_flag.
ENDIF.
DATA jobname LIKE tbtcjob-jobname.
DATA jobcount LIKE tbtcjob-jobcount.
DATA job_release LIKE btch0000-char1.
DATA job_imediate TYPE c.
CLEAR: jobname, jobcount, job_release.
CONCATENATE 'MAPAEXEC' sy-uname sy-datum
               INTO jobname SEPARATED BY space.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = jobname
       IMPORTING
            jobcount         = jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ENDIF.
SUBMIT z_mapa_execucao_orcamental
         VIA JOB jobname NUMBER jobcount
         WITH ano EQ ano
         WITH so_perio IN so_perio
         WITH so_date IN so_date
         WITH so_org EQ so_org
         WITH so_num IN so_num
         AND RETURN.
IF stdt_output-startdttyp EQ 'I'.
    CLEAR job_imediate.
    job_imediate = 'X'.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            calendar_id                 = stdt_output-calendarid
            event_id                    = stdt_output-eventid
            event_param                 = stdt_output-eventparm
            event_periodic              = stdt_output-periodic "?
            jobcount                    = jobcount
            jobname                     = jobname
            laststrtdt                  = stdt_output-laststrtdt
            laststrttm                  = stdt_output-laststrttm
            prddays                     = stdt_output-prddays "??
            prdhours                    = stdt_output-prdhours "?
            prdmins                     = stdt_output-prdmins "??
            prdmonths                   = stdt_output-prdmonths
            prdweeks                    = stdt_output-prdweeks "?
            predjob_checkstat           = stdt_output-checkstat
            pred_jobcount               = stdt_output-predjobcnt
            pred_jobname                = stdt_output-predjob
            sdlstrtdt                   = stdt_output-sdlstrtdt
            sdlstrttm                   = stdt_output-sdlstrttm
            strtimmed                   = job_imediate
            targetsystem                = stdt_output-instname
            start_on_workday_not_before = stdt_output-notbefore
            start_on_workday_nr         = stdt_output-wdayno
            workday_count_direction     = stdt_output-wdaycdir
       IMPORTING
            job_was_released            = job_release
       EXCEPTIONS
            cant_start_immediate        = 1
            invalid_startdate           = 2
            jobname_missing             = 3
            job_close_failed            = 4
            job_nosteps                 = 5
            job_notex                   = 6
            lock_failed                 = 7
            OTHERS                      = 8.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ELSE.
    MESSAGE i004(zmapas) WITH jobname.
ENDIF.
Thanks in advance,
Best Regards
João Martins

Hello João.
In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
Check this code:
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
           jobname          = w_jobname
      IMPORTING
           jobcount         = w_jobcount
      EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
CHECK sy-subrc = 0.
CLEAR seltab_wa.
MOVE: t_jobs-param TO seltab_wa-selname,
t_processar-line+34 TO seltab_wa-low.
APPEND seltab_wa TO seltab.
seltab_wa-selname = 'P_LOJA'.
seltab_wa-low = t_processar-ficheiro+7(4).
APPEND seltab_wa TO seltab.
*** Submete o programa para o JOB
SUBMIT (t_jobs-repid)
WITH SELECTION-TABLE seltab
USER sy-uname
   VIA JOB w_jobname NUMBER w_jobcount
   AND RETURN.
*** Encerra o JOB
l_hora = sy-uzeit.
ADD 60 TO l_hora.
CALL FUNCTION 'JOB_CLOSE'
   EXPORTING
      jobcount           = w_jobcount
      jobname           = w_jobname
      sdlstrtdt            = sy-datum
      sdlstrttm           = l_hora
      targetserver       = w_servidor
   IMPORTING
      job_was_released     = l_liberado
   EXCEPTIONS
      cant_start_immediate = 1
      invalid_startdate    = 2
      jobname_missing      = 3
      job_close_failed     = 4
      job_nosteps          = 5
      job_notex            = 6
      lock_failed          = 7
      OTHERS               = 8.
Regards.
Valter Oliveira.

Submit RSEOUT00 as background job

Hi all,
Here is my requirement.There is a Z program from which RSEOUT00 program has to be called , so that it will change the Idoc status to '03'. I tried using Submit RSEOUT00..and return and also tried JOB_open and then SUBMIT rseout00 WITH docnum EQ p_idocno user sy-uname via job jobname number jobcount and return and then JOB_CLOSE .I checked SM37 also where i can see this job as finished..
I tried COMMIT WORK statement and also WAIT statement .
But still the idoc status wont change to '03' .
Can anyone plase advise on how to correct this .
Regards,
Sudheer

Hi,
I have created background job for RSEOUT00 and written the below code. It worked.
DATA: w_number           TYPE tbtcjob-jobcount,
           w_name              TYPE tbtcjob-jobname VALUE 'ZTEST_JOB'.
   CALL FUNCTION 'JOB_OPEN'
     EXPORTING
       jobname          = w_name
     IMPORTING
       jobcount         = w_number
     EXCEPTIONS
       cant_create_job = 1
       invalid_job_data = 2
       jobname_missing = 3
       OTHERS           = 4.
   IF sy-subrc = 0.
     SUBMIT rseout00 VIA JOB w_name NUMBER w_number AND RETURN.
     IF sy-subrc = 0.
       CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
           jobcount             = w_number
           jobname              = w_name
           strtimmed            = 'X'
         EXCEPTIONS
           cant_start_immediate = 1
           invalid_startdate    = 2
           jobname_missing      = 3
           job_close_failed     = 4
           job_nosteps          = 5
           job_notex            = 6
           lock_failed          = 7
           OTHERS               = 8.
       IF sy-subrc <> 0.
       ENDIF.
     ENDIF.
   ENDIF.
Thanks,
Appanaboina

Alv show in report but when see in spool (after run background job) there i

my program have some error when i run result alv show in report but when see in spool (after run background job) there is no data, (other program can see result in spool)
Please help
here is some example of my program
********************************declare internal table*****************************
internal table output for BDC
data : begin of t_output occurs 0,
bukrs type anla-bukrs,
anln1 type anla-anln1,
anln2 type anla-anln2,
zugdt type anla-zugdt,
result(70) type c,
end of t_output.
*****get data from loop********************************
loop at t_anla.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln1
         IMPORTING
              OUTPUT = t_anla-anln1.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln2
         IMPORTING
              OUTPUT = t_anla-anln2.
check record is correct or not
    select single bukrs anln1 anln2 zugdt
    into w_output
    from anla
    where bukrs = t_anla-bukrs and
    anln1 = t_anla-anln1 and
    anln2 = t_anla-anln2
   zugdt = '00000000'
if record is correct
    if sy-subrc = 0 and w_output-zugdt = '00000000'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Yes : this asset can delete'.
      append w_output to t_output.
if record is not correct
    elseif sy-subrc = 0 and w_output-zugdt <> '00000000'.
there is error record this asset have value already
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset have value already'.
      append w_output to t_output.
    else.
there is error record this asset donot exist in table anla
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset doest not exist'.
      append w_output to t_output.
    endif.
*end of check record is correct or not
    clear w_output.
endloop.
******************************show data in ALV***************************************************
show data from file in ALV
perform display_report_ALV.
*&      Form display_report_ALV
form display_report_ALV.
DATA: LT_FIELD_CAT TYPE SLIS_T_FIELDCAT_ALV,
      LT_EVENTS TYPE SLIS_T_EVENT,
      LV_REPID LIKE SY-REPID.
PERFORM ALV_DEFINE_FIELD_CAT USING LT_FIELD_CAT.
PERFORM ALV_HEADER_BUILD USING T_LIST_TOP_OF_PAGE[].
PERFORM ALV_EVENTTAB_BUILD USING LT_EVENTS[].
LV_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM = LV_REPID
            IT_FIELDCAT        = LT_FIELD_CAT
            I_SAVE             = 'A'
            IT_EVENTS          = LT_EVENTS[]
       TABLES
            T_OUTTAB           = t_output
       EXCEPTIONS
            PROGRAM_ERROR      = 1
            OTHERS             = 2.
IF SY-SUBRC NE 0.
    WRITE: / 'Return Code : ', SY-SUBRC,
      'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
endform.
*&      Form alv_define_field_cat
      text
     -->P_LT_FIELD_CAT text
FORM ALV_DEFINE_FIELD_CAT USING TB_FCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: WA_FIELDCAT LIKE LINE OF TB_FCAT,
    LV_COL_POS TYPE I.
DEFINE FIELD_CAT.
    CLEAR WA_FIELDCAT.
    ADD 1 TO LV_COL_POS.
    WA_FIELDCAT-FIELDNAME = &1.
    WA_FIELDCAT-REF_TABNAME = &2.
    WA_FIELDCAT-COL_POS = LV_COL_POS.
    WA_FIELDCAT-KEY = &3.
    WA_FIELDCAT-NO_OUT = &4.
    WA_FIELDCAT-REF_FIELDNAME = &5.
    WA_FIELDCAT-DDICTXT = 'M'.
    IF NOT &6 IS INITIAL.
      WA_FIELDCAT-SELTEXT_L = &6.
      WA_FIELDCAT-SELTEXT_M = &6.
      WA_FIELDCAT-SELTEXT_S = &6.
    ENDIF.
    WA_FIELDCAT-DO_SUM = &7.
    WA_FIELDCAT-OUTPUTLEN = &8.
    APPEND WA_FIELDCAT TO TB_FCAT.
END-OF-DEFINITION.
FIELD_CAT 'BUKRS' 'ANLA'     'X' '' 'BUKRS' 'Company Code' '' ''.
FIELD_CAT 'ANLN1' 'ANLA'     'X' '' 'ANLN1' 'Asset Number' '' ''.
FIELD_CAT 'ANLN2' 'ANLA'     'X' '' 'ANLN2' 'Asset Sub Number' '' ''.
FIELD_CAT 'ATEXT'   'T5EAE'     'X' '' 'ATEXT' 'Result' '' ''.
FIELD_CAT 'RESULT' ''     'X' '' 'RESULT' 'RESULT' '' ''.
ENDFORM.                    " alv_define_field_cat

Hi,
Check this code..
FORM display_report_alv.
DATA: lt_field_cat TYPE slis_t_fieldcat_alv,
lt_events TYPE slis_t_event,
lv_repid LIKE sy-repid.
PERFORM alv_define_field_cat USING lt_field_cat.
PERFORM alv_header_build USING t_list_top_of_page[].
PERFORM alv_eventtab_build USING lt_events[].
lv_repid = sy-repid.
IF sy-batch EQ 'X'. ----> " System Field for Backgroud..if Background use list display
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ELSE.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ENDIF.
IF sy-subrc NE 0.
    WRITE: / 'Return Code : ', sy-subrc,
    'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
ENDFORM.                    "display_report_ALV

Background job- getting printed automatically

In my BDC Program i have submitted Session for Background Processing using
Submit RSBDCSUB..........
my code is also given below..The problem is after the user executes the program, background job is automatically going to his Local printer and getting printed. HOw to avoid this?
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = gf_jobname
       IMPORTING
            jobcount         = gf_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
*-Submit the selected sales orders for changes.
SUBMIT rsbdcsub AND RETURN
         WITH mappe = v_sess
         WITH von = sy-datum
         WITH bis = sy-datum
         WITH z_verarb = 'X'
         WITH fehler = space
         WITH batchsys = space
         WITH logall = space
         USER sy-uname VIA JOB gf_jobname NUMBER gf_jobcount.
IF sy-subrc NE 0.
    MESSAGE i999 WITH text-013.
    EXIT.
ENDIF.
*-Close job and start immediately.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = gf_jobcount
            jobname              = gf_jobname
            strtimmed            = 'X'
       IMPORTING
            job_was_released     = gf_release
       EXCEPTIONS
            cant_start_immediate = 1
            invalid_startdate    = 2
            jobname_missing      = 3
            job_close_failed     = 4
            job_nosteps          = 5
            job_notex            = 6
            lock_failed          = 7
            OTHERS               = 8.

On SUBMIT use
SUBMIT zxxxxxx TO SAP-SPOOL
                    WITHOUT SPOOL DYNPRO
                    IMMEDIATELY ' '
                    KEEP IN SPOOL 'X'
                    DESTINATION printer
                     NUMBER number
                    AND RETURN

It has an error when run a program in background job

Dear Expert,
we have a program
when run it in background,it has a error "Error during import of clipboard contents" but when run it normally(run in front workbench se38 or run the t-code),everything is ok.i've used typingJDBG in the command box to debuge the background job,there has no error.
whould you like to tell me what had happen? thanks a lot!
addition: the program used a function ALSM_EXCEL_TO_INTERNAL_TABLE
Thanks & Regards,
Kerry
Edited by: Kerry Wang on Aug 24, 2009 2:12 PM
Edited by: Kerry Wang on Aug 24, 2009 2:14 PM
Edited by: Kerry Wang on Aug 24, 2009 2:14 PM

Hi,
You cannot use FMs to get data directly from the presentation server when program is executed in the backgroud.
Check the thread : GUI_DOWNLOAD
Regards,
Himanshu

Failed to Run OLE Excel program in background JOB (SM36)

Please help.
I have write a program to use OLE to create a Excel file.
The program can run successful in front end workstation. However, when I run the program in background job by SM36.
The statement "CREATE OBJECT EXCEL 'EXCEL.APPLICATION'" return with error "SY-SUBRC = 2".
How can I solve it ?
Can OLE Excel be run on background job ?
Thanks so much,
Mark

Hi Mark:
Your need is a very common one. I also was asked to generate an Excel in Background.
It is not possible to work with OLE in background mode.
The reason is: In background mode there is no presentation server. OLE is executed in presentation server.
Below I paste the code I wrote to solve my problem.
This class sends a mail with an excel attached. The Excel content will be the internal table you pass to the class. But the Excel is not binary, it is a plain text file, separated by tabulators. Anyway, when you open it with Excel, the columns are properly shown.
Sorry. Comments are in spanish, I don't have time to translate it.
I kindly ask to everybody which want to use it to keep my name in the code.
* Autor: Jordi Escoda, 30/10/2008.
* Descripción: Esta clase genera un correo electrónico destinado a
* una persona, adjuntando el contenido de una tabla interna como
* Excel (campos separados por tabuladores).
* La virtud de esta clase es su sencillez de utilización. Para lanzar
* el mail con el excel adjunto basta con declarar la tabla interna,
* llenarla, colocar el asunto del mensaje, el destinatario, el nombre
* del excel adjunto, y pasar la tabla interna.
* Ejemplo de utilización:
* DATA: lc_mail TYPE REF TO cl_mail_builder_xls_attach.
* DATA: lt_anla TYPE STANDARD TABLE OF anla.
*    SELECT * INTO TABLE lt_anla FROM anla.
*    CREATE OBJECT lc_mail.
*    CALL METHOD lc_mail->set_subject( 'Excel adjunto' ).
*    CALL METHOD lc_mail->set_recipient( 'XXX@XXXDOTCOM' ).
*    CALL METHOD lc_mail->set_attach_filename( 'ANLA' ).
*    APPEND 'Cuerpo del mensaje' TO lt_body.
*    APPEND 'Saludos cordiales' TO lt_body.
*    CALL METHOD lc_mail->set_bodytext( lt_body ).
*    CALL METHOD lc_mail->set_attach_table( lt_anla ).
*    CALL METHOD lc_mail->send( ).
*       CLASS cl_mail_builder_xls_attach DEFINITION
CLASS cl_mail_builder_xls_attach DEFINITION.
PUBLIC SECTION.
    METHODS: set_subject
                           IMPORTING im_subject TYPE so_obj_des,
             set_bodytext
                           IMPORTING im_body TYPE bcsy_text,
             set_recipient
                           IMPORTING im_recipient TYPE ad_smtpadr,
             set_attach_table
                           IMPORTING im_table TYPE ANY TABLE,
             set_attach_filename
                           IMPORTING im_attach_name TYPE sood-objdes,
             send.
PRIVATE SECTION.
    CONSTANTS:
      c_tab TYPE c VALUE cl_bcs_convert=>gc_tab,
      c_crlf TYPE c VALUE cl_bcs_convert=>gc_crlf,
      c_singlequote TYPE c VALUE '.
    DATA: l_recipient_addr TYPE ad_smtpadr.
    DATA: send_request   TYPE REF TO cl_bcs,
          document       TYPE REF TO cl_document_bcs,
          recipient      TYPE REF TO if_recipient_bcs,
          bcs_exception TYPE REF TO cx_bcs.
    DATA: binary_content TYPE solix_tab,
          size           TYPE so_obj_len.
    DATA: l_string TYPE string,
          l_body_text TYPE bcsy_text,
          l_subject TYPE so_obj_des,
          l_attach_name TYPE sood-objdes.
    METHODS: create_binary_content,
             get_dataelement_medium_text
                    IMPORTING im_table_name TYPE tabname
                              im_field_name TYPE fieldname
                    EXPORTING ex_medium_text TYPE scrtext_m.
ENDCLASS.                    "cl_mail_builder_xls_attach DEFINITION
*       CLASS cl_mail_builder_xls_attach IMPLEMENTATION
CLASS cl_mail_builder_xls_attach IMPLEMENTATION.
METHOD set_bodytext.
    l_body_text[] = im_body[].
ENDMETHOD.                    "add_bodytext
METHOD set_subject.
    l_subject = im_subject.
ENDMETHOD.                    "add_subject
METHOD set_attach_filename.
    l_attach_name = im_attach_name.
ENDMETHOD.                    "add_subject
METHOD set_recipient.
    l_recipient_addr = im_recipient.
ENDMETHOD.                    "add_subject
METHOD set_attach_table.
*   Rellena en un string el contenido de la tabla interna recibida
    DATA: ref_to_struct TYPE REF TO cl_abap_structdescr.
    DATA: my_like TYPE fieldname,
          nombretabla TYPE tabname,
          nombrecampo TYPE fieldname,
          texto_mediano TYPE scrtext_m.
    DATA: l_idx TYPE i,
          l_valorcampo(16) TYPE c,
          l_long TYPE i.
    FIELD-SYMBOLS: <fs_linea> TYPE ANY,
                   <fs_campo> TYPE ANY.
    FIELD-SYMBOLS: <comp_descr> TYPE abap_compdescr.
    CHECK NOT im_table[] IS INITIAL.
*   Línea con los nombres de las columnas.
    CLEAR l_string.
    LOOP AT im_table ASSIGNING <fs_linea>.
*     Toma los atributos del componente
      ref_to_struct =
                 cl_abap_structdescr=>describe_by_data( <fs_linea> ).
      LOOP AT ref_to_struct->components ASSIGNING <comp_descr>.
        ASSIGN COMPONENT <comp_descr>-name
                            OF STRUCTURE <fs_linea> TO <fs_campo>.
*       Obtenemos el origen de donde proviene (like). Ej:BKPF-BUDAT
        DESCRIBE FIELD <fs_campo> HELP-ID my_like.
        SPLIT my_like AT '-' INTO nombretabla nombrecampo.
        CALL METHOD get_dataelement_medium_text
          EXPORTING
            im_table_name = nombretabla
            im_field_name = nombrecampo
          IMPORTING
            ex_medium_text = texto_mediano.
        IF texto_mediano IS INITIAL.
          CONCATENATE l_string <comp_descr>-name INTO l_string.
        ELSE.
          CONCATENATE l_string texto_mediano INTO l_string.
        ENDIF.
        AT LAST.
          CONCATENATE l_string c_crlf INTO l_string.
          EXIT.
        ENDAT.
        CONCATENATE l_string c_tab INTO l_string.
      ENDLOOP.
      EXIT.
    ENDLOOP.
*   Contenido de la tabla
    LOOP AT im_table ASSIGNING <fs_linea>.
*     Toma los atributos del componente
      ref_to_struct =
                 cl_abap_structdescr=>describe_by_data( <fs_linea> ).
      LOOP AT ref_to_struct->components ASSIGNING <comp_descr>.
*       Asignamos el componente ue tratamos, para obtener
*       el valor del mismo
        ASSIGN COMPONENT <comp_descr>-name OF STRUCTURE <fs_linea>
                                        TO <fs_campo>.
        CASE <comp_descr>-type_kind.
          WHEN 'P'. "Packed Number
*           Convierte a caracter
            WRITE <fs_campo> TO l_valorcampo.
            CONCATENATE l_string l_valorcampo INTO l_string.
          WHEN OTHERS.
            l_long = STRLEN( <fs_campo> ).
            IF l_long > 11 AND <fs_campo> CO ' 0123456789'.
*             El Excel muestra un número tal como 190000000006
*             en formato 1,9E+11.
*             Para eviarlo, los números de más de 11 dígitos los
*             concatenamos con comillas simples.
              CONCATENATE l_string c_singlequote
                          <fs_campo> c_singlequote INTO l_string.
            ELSE.
              CONCATENATE l_string <fs_campo> INTO l_string.
            ENDIF.
        ENDCASE.
        AT LAST.
*         Añade CRLF
          CONCATENATE l_string c_crlf INTO l_string.
          EXIT.
        ENDAT.
*       Añade tabulador
        CONCATENATE l_string c_tab INTO l_string.
      ENDLOOP.
    ENDLOOP.
    create_binary_content( ).
ENDMETHOD.                    "set_attach_table
METHOD create_binary_content.
    DATA: l_size TYPE so_obj_len.
*   convert the text string into UTF-16LE binary data including
*   byte-order-mark. Mircosoft Excel prefers these settings
*   all this is done by new class cl_bcs_convert (see note 1151257)
    TRY.
        cl_bcs_convert=>string_to_solix(
          EXPORTING
            iv_string   = l_string
            iv_codepage = '4103' "suitable for MS Excel, leave empty
            iv_add_bom = 'X'     "for other doc types
          IMPORTING
            et_solix = binary_content
            ev_size   = size ).
      CATCH cx_bcs.
        MESSAGE e445(so).
    ENDTRY.
ENDMETHOD.                    "create_binary_content
METHOD send.
    DATA: l_sent_to_all TYPE os_boolean.
    TRY.
*       create persistent send request
        send_request = cl_bcs=>create_persistent( ).
*       create and set document with attachment
*       create document object
        document = cl_document_bcs=>create_document(
          i_type    = 'RAW'
          i_text    = l_body_text
          i_subject = l_subject ).
*       add the spread sheet as attachment to document object
        document->add_attachment(
          i_attachment_type    = 'xls'
          i_attachment_subject = l_attach_name
          i_attachment_size    = size
          i_att_content_hex    = binary_content ).
*       add document object to send request
        send_request->set_document( document ).
*       add recipient (e-mail address)
        recipient =
           cl_cam_address_bcs=>create_internet_address(
                                      l_recipient_addr ).
*       add recipient object to send request
        send_request->add_recipient( recipient ).
*       send document
        l_sent_to_all = send_request->send(
                             i_with_error_screen = 'X' ).
        COMMIT WORK.
        IF l_sent_to_all IS INITIAL.
          MESSAGE i500(sbcoms) WITH l_recipient_addr.
        ELSE.
          MESSAGE s022(so).
        ENDIF.
      CATCH cx_bcs INTO bcs_exception.
        MESSAGE i865(so) WITH bcs_exception->error_type.
    ENDTRY.
ENDMETHOD.                    "lcl_mail_xls_attachment
METHOD get_dataelement_medium_text.
    DATA: lt_fld_info TYPE STANDARD TABLE OF dfies,
      wa_fld_info TYPE dfies.
*   Busca en el diccionario los datos del campo
    CALL FUNCTION 'DDIF_FIELDINFO_GET'
      EXPORTING
        tabname        = im_table_name
        fieldname      = im_field_name
        langu          = sy-langu
      TABLES
        dfies_tab      = lt_fld_info
      EXCEPTIONS
        not_found      = 1
        internal_error = 2
        OTHERS         = 3.
    CLEAR ex_medium_text.
    IF sy-subrc = 0.
      READ TABLE lt_fld_info INDEX 1 INTO wa_fld_info.
*     Si lo ha podido tomar del diccionario...
      IF NOT wa_fld_info-scrtext_m IS INITIAL.
*       Toma el nombre del nombre de campo del diccionario
        ex_medium_text = wa_fld_info-scrtext_m.
      ENDIF.
    ENDIF.
ENDMETHOD.                    "get_dataelement_medium_text
ENDCLASS.                    "cl_mail_builder_xls_attach IMPLEMENTATION

How to get data from the called program using SUBMIT in a background job?

Hi Experts,
I've a program which creates a background job using JOB_OPEN and JOB_CLOSE function modules.
Between the above function modules I need to call a program using SUBMIT VIA JOB statement.
My problem is, How do I fetch some data in an internal table in the called program to the calling program after the SUBMIT statement?
I tried to EXPORT and IMPORT the data, but they are giving a failed sy-subrc when using this background job.
Kindly let me know your inputs and valuable suggestions.

Kumar,
When we execute a program as a background job then the output will be sent to Spool which needs to be fetched again.I guess we need to use Submit via spool as mentioned by Rajat.
Check these threads to get some idea
submit report to spool & import spool id
Re: Generate Spool for a report
K.Kiran.

Problems with background job

Hi,
I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice.
- First it is executed synchronously when the job is created
- Then it is executed in the normal job step as I want it to do
I don't want it to be executed the first time because it creates data!!!
Code:
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname = w_jobid
     IMPORTING
          jobcount = w_jobnr
          sdlstrtdt = sy-datum
          sdlstrttm = sy-uzeit.
SUBMIT (p_prog)
WITH p_idocnr = p_idocno
           USER            p_user
           VIA   JOB       w_jobid
                 NUMBER w_jobnr
                 AND       RETURN.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount         = w_jobnr
          jobname          = w_jobid
          strtimmed        = 'X'
     IMPORTING
          job_was_released = w_jobrel.
Does anyone have a clue of what I should do to prevent this?
// Regards Hans

Hi again,
1. U are right.
2. It will happen if we use SUBMIT.
3. As per the help documentation,
    it will run the program in separate session,
   ( as soon as submit statement comes)
4. and run the INITIALIZATION event.
The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN statement.
regards,
amit m.

Importing background jobs

Similar Messages

Maybe you are looking for