Require Job name in SM37 while executing call transaction in background

Hi all,
I am executing a report program, which contains Call transaction.
I have recorded properly. The recording contains background job screen also ( means a separate popup came and i gave the job name and i gave immediately )
When i execute in this program in foreground its creating job,its showing the job in sm37.
But when i execute this program in background, it does not showing the job name in sm37.
Anyone kindly help this out?
Anandhab

Hi,
The job will be created by the step level user.
Try searching again with jobname and * for username.
Regards,
Jovito

Similar Messages

Call transaction in Background job

Hi,
I am executing a program in background. In that program I am having a CALL TRANSACTION as below:
CALL TRANSACTION 'ME22'
    USING g_t_bdctab
    MODE 'N'
    UPDATE 'S'
    MESSAGES into g_t_bdcmsg.
But it is not working. The same is working when the program is executed in foreground.
Is this means, we cannot have CALL TRANSACTION in background?
If Yes, then what could be the solution for it?
Thanks,
Pankaj.

Hello Pankaj,
Call transaction works in background.
Provided you are not picking file from presentation server.
If you are picking file from presentation server, place the same file in application server and during background job pick the file from application server then your program works perfectly.
Regards,
Tarun

Error while executing the transaction QC22 (Quality Certificate for Batch)

Hello Friends,
While executing the transaction QC22(Quality Certificate for Batch), after giving the Batch Number and Customer Number, when i am executing it , system is throwing the error message as "Not all data was found for characteristic 90139982 in profile D80D8".
Message no. ZQ010
Diagnosis
Not all data was found for characteristic 90139982, referenced as number 0030 in certificate profile D80D8. The missing data could be the short text, specifications, or results.
System Response
The missing charactertistic will not be printed on the certificate,
Procedure
Review the settings for data orgin of the short text, specifications, and results, and adjust accordingly.
One more thing i would like to add here as against the same batch in april we had taken the print of COA (Quality Certificate) through the transaction QC22. But now we are trying to do that than system is thrown above mentioned error.
As i am new in QM, kindly explain we were to maintain the certificate profile.
Waiting for the experts inputs.
Thanks and Regards,
Jitendra Chauhan

Hi
Try with QA33 you may have display authorization, or check in MB51 on the base of material and batch you can find the lot number generated, then go to QA03 and check the result, if you want to validate the characters check with the inspection plan, the characters entered in the inspection plan and the characters in the concerned certificate profile.
Regards
Naveen.
Edited by: vaddapalli naveen on Jul 1, 2010 1:57 PM

Database Alert Macros issue while executing the macros in Background

Hi All,
I am facing some problems while executing the Database alert macros in Background/Process Chain.
There are two macros for which the problem exists.
1.Excess Projected Inventory above Max
The logic here is, the alert should work for Only Fixed Lot size Procedure.
If the Stock on hand (projected EA) > (Safety Stock (EA) + Full SOQ (EA)) then alert = "Projected inventory is XX% above MAX".
XX is the Percent above Max.
Note: SOQ => fixed lot size.
2.Excess Actual Days of Supply
The Logic here is, the alert should work for all Lot size Procedures except for "Fixed lot size".
Actual Days Supply >=180 days. (current -> future buckets)
- For every receipt cell check the Actual Days Supply - if >= 180 days.
The macros are working perfectly as expected.

Hi Abhi,
Hope you are doing good.
Yes exactly, the macros are working in foreground/Interactively but not in the Background via Process chain. Let me send the details again.
Issue :
I am facing some problems while executing the Database alert macros in Background/Process Chain.
There are two macros for which the problem exists.
1.Excess Projected Inventory above Max
The logic here is, the alert should work for Only Fixed Lot size Procedure. But in Background the alerts are getting created for Lot for Lot and other Planning procedures..
If the Stock on hand (projected EA) > (Safety Stock (EA) + Full SOQ (EA)) then alert = "Projected inventory is XX% above MAX".
XX is the Percent above Max.
Note: SOQ => fixed lot size.
2.Excess Actual Days of Supply
The Logic here is, the alert should work for all Lot size Procedures except for "Fixed lot size". But in Background the alerts are getting created for the Fixed Lot size procedures too..
Actual Days Supply >=180 days. (current -> future buckets)
- For every receipt cell check the Actual Days Supply - if >= 180 days.
The macros are working perfectly as expected in Foreground/Interactively but the samething is not happening while executing the macro in Background/Process Chain.
I have tried running these macros in different sequences(Default/Start/Macro) but couldn't able to resolve the issue.
Thanks in Advance,
Jay.

Problem while executing the transaction code FMBV (Reconstruct)

We are facing a problem while executing the transaction code FMBV
(Reconstruct Availability Control in Funds Management) in it when we
execute this transaction system only updates the expenditure which is
made before technical upgrade from 4.6c to ECC6 EHP6, against the
Assigned Budget (KBFC budget type) in the Annual Budget Table (BPJA)
and
the expenditure which we made after the upgrade, the program just
ignore
it. We can also see the expenditure in the standard FBL3N report.
Please guide us.
Thanks and Best Regards,

Dear Abrar
In your description, you refer to missing update after an upgrade. First of all, see if table FMIT is consistent, as it is the basis for calculating the assigned values during AVC reconstruction.
Refer to this note:
977016 FMIT: Missing totals records in Funds Management And perform following steps:
1.- Run program RGZZGLUX
2.- Run program RFFMRC04 to match totals table with line items. A test run after a successful effective run should not find inconsistencies.
3.- If RFFMRC04 does not show more inconsistencies, run FMBV as final step.
Note that this reconstruction must be done without any other budgeting/posting activities at the same time, otherwise you may cause other inconsistencies.
Please let me know the results.
Best regards,
977016 - FMIT: Missing totals records in Funds Management
Symptom
After the upgrade to ERP 2004 or higher you realize that the FMIT totals table is no longer updated in Funds Management. You start the RFFMRC04 report to reconstruct the totals, but the report still displays the missing totals after an update run.
Other Terms
FMIT, EA-PS, ECC 5.00, ECC 6.00, ECC 7.00
Reason and Prerequisites
This problem occurs due to a generation error.
Solution
Start the RGZZGLUX report to generate missing source code in FI-SL. Then start the RFFMRC04 report to reconstruct the totals, now another run of the report should no longer display any errors.

How to execute ME22N transaction in background.

Hi experts,
How to execute ME22N and ME23N in background, when execute the transaction in background, , it should generate a spool, with out any printpreview. How can we do this....?
thanks

Hi,
Write a BDC program for updation of tables for u r user-exit.
After that Schedule u r program in back gound job scheduling.
Using SM36 - Define Background job.
Give the job name and Press job wizard button.
It's asking about job name and job class -prioritty.
press continue and give program name .
Select radiobutton based on u r requirement.
Then specify periodic job or only in holidays.
Then u select hours and all.
In SM37 give u r job name and and press execute.
Reward if useful.
Regards,
Narasimha

How to edit the job name in SM37

Hi All,
I have job in SM37 with the mane ZBI_PROCESSING and the Job in Release status. Now I want to change the Job Name to Z_PROCESSING_SS. Please let me know how to edit the Job Name.
Regards,
Ravi

Hi Ravi,
In SM37 when you have the list of all jobs, right-clic on the job you want to rename, copy, enter the new name.
Then you can delete the first job. The copied one will then be executed.
Regards,
Fred

Execute CALL TRANSACTION in the background....

Hi,
I want to use CALL TRANSACTION in a report program and execute this report in the background.
There is not GUI_UPLOAD / GUI_DOWNLOAD used anywhere.
Can someone suggest me what precaution I need to take in my code for CALL TRANSACTION?
Is there any additional code for background processing?
Thanks.

hi,
this is the sample code:
Precations need to take :
1. see that u r transfer tha data in correct field, on correct screen, and of correct format.
2. capture the error logs in bdcmsgcoll - error logs have to be handle.
3. ensure correct recording.
in selection screen you can mention in which mode u want :
A     Display all screens
E     Display errors
N     Background processing
P     Background processing; debugging possible
This is the sample code:
& Report ZKO01_BDC                                                       &
& Object Id       :                                                       &
& Object Name     : ZKO01_BDC                                             &
& Program Name    : ZKO01_BDC                                             &
& Transaction Code: ZKO01_BDC                                             &
& Module Name     : FI / CO                                               &
& Program Type    : BDC Program      Create Date     : 23.06.2008         &
& SAP Release     : 6.0              Transport No    :                    &
& Description     : BDC to upload internal order with indernal assignment &
& Version         : 1.0.                                                  &
& Changed on      :                                                       &
report zko01_bdc
       no standard page heading line-size 255.
types: begin of record,
        auart_001(004),
        ktext_002(040),
        bukrs_003(004),
        werks_004(004),      " ADDED NEW - RAHUL SHINDE
        scope_005(010),
        prctr_006(004),      " ADDED NEW - RAHUL SHINDE
        waers_007(005),
        astkz_008(001),
        plint_009(001),
      end of record.
types: begin of ty_stats,
       mess(72) type c,
       auart_001(004),
       text(18) type c,
       end of ty_stats.
data : it_record type table of record,
        wa_record like line of it_record.
data: bdcdata type table of bdcdata,
      mestab type table of bdcmsgcoll.
data : stats type table of ty_stats.
data: opt type ctu_params.
data: m(72) type c.
data : fl_name type string.
data : wa_bdcdata like line of bdcdata,
        wa_mestab like line of mestab.
data : wa_stats like line of stats.
data:   ctumode like ctu_params-dismode.
data:   cupdate like ctu_params-updmode.
data: file type rlgrap-filename.
data: xcel type table of alsmex_tabline with header line.
data: mod1(1) type c.
initialization.
opt-dismode = 'A'.
opt-updmode = 'S'.
opt-nobinpt = 'X'.   "No batch input mode
                    Selection Screen
selection-screen begin of block bk1 with frame.
selection-screen skip 1.
parameters p_file type localfile. " default 'D:\Common\PWC\Asset BDC\Book2.xls'.
parameters p_mode like ctu_params-dismode obligatory.
selection-screen skip 1.
selection-screen end of block bk1.
file = p_file.
mod1 = p_mode.
at selection-screen on value-request for p_file.
call function 'KD_GET_FILENAME_ON_F4'
       exporting
            static    = 'X'
       changing
            file_name = p_file.
                    Selection Screen
start-of-selection.
file = p_file.
ctumode = mod1.
cupdate = 'L'.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       exporting
            filename                = file
            i_begin_col             = '1'
            i_begin_row             = '1'
            i_end_col               = '100'
            i_end_row               = '5000'
       tables
            intern                  = xcel
       exceptions
            inconsistent_parameters = 1
            upload_ole              = 2
            others                  = 3.
loop at xcel.
case xcel-col.
    when '0001'.
        wa_record-auart_001 = xcel-value.      "ok
    when '0002'.
        wa_record-ktext_002 = xcel-value.      "ok
    when '0003'.
        wa_record-bukrs_003 = xcel-value.      "ok
    when '0004'.
        wa_record-werks_004 = xcel-value.      "ok
    when '0005'.
        wa_record-scope_005 = xcel-value.      "ok
   when '0005'.
       wa_record-KTEXT_005 = xcel-value.    "ok
    when '0006'.
        wa_record-prctr_006 = xcel-value.      "ok
    when '0007'.
        wa_record-waers_007 = xcel-value.      "ok
    when '0008'.
        wa_record-astkz_008 = xcel-value.      "ok
    when '0009'.
        wa_record-plint_009 = xcel-value.      "ok
endcase.
at end of row.
    append wa_record to it_record.
    clear wa_record.
endat.
endloop.
loop at it_record into wa_record.
perform bdc_dynpro      using 'SAPMKAUF' '0100'.
perform bdc_field       using 'BDC_CURSOR'
                              'COAS-AUART'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'COAS-AUART'
                              wa_record-auart_001.
perform bdc_dynpro      using 'SAPMKAUF' '0600'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BUT2'.
perform bdc_field       using 'COAS-KTEXT'
                              wa_record-ktext_002.
perform bdc_field       using 'BDC_CURSOR'
                              'COAS-SCOPE'.
perform bdc_field       using 'COAS-BUKRS'
                              wa_record-bukrs_003.
perform bdc_field       using 'COAS-WERKS'
                              wa_record-werks_004.
perform bdc_field       using 'COAS-SCOPE'
                              wa_record-scope_005.
perform bdc_field       using 'COAS-PRCTR'
                              wa_record-prctr_006.
perform bdc_dynpro      using 'SAPMKAUF' '0600'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SICH'.
*perform bdc_field       using 'COAS-KTEXT'
                             wa_record-KTEXT_005.
perform bdc_field       using 'BDC_CURSOR'
                              'COAS-PLINT'.
perform bdc_field       using 'COAS-WAERS'
                              wa_record-waers_007.
perform bdc_field       using 'COAS-ASTKZ'
                              wa_record-astkz_008.
perform bdc_field       using 'COAS-PLINT'
                              wa_record-plint_009.
call transaction 'KO01' using bdcdata
                        options from opt
                        messages into mestab.
*PERFORM loggs.
clear wa_record.
refresh bdcdata.
endloop.
end-of-selection.
clear : wa_stats.
if stats is initial.
    write :/ text-001.
else.
loop at stats into wa_stats.                         "displays runtime messages
    write:/ 'MESSAGE :',wa_stats-auart_001.
    if wa_stats-auart_001 is not initial.
    write:/ wa_stats-auart_001, wa_stats-text.
    endif.
    skip 1.
endloop.
endif.
*& FORMS BDC_DYNPRO
form bdc_dynpro using program dynpro.
clear wa_bdcdata.
wa_bdcdata-program = program.
wa_bdcdata-dynpro   = dynpro.
wa_bdcdata-dynbegin = 'X'.
append wa_bdcdata to bdcdata..
endform.
FORM BDC_FIELD                                                 *
form bdc_field using fnam fval.
    clear wa_bdcdata.
    wa_bdcdata-fnam = fnam.
    wa_bdcdata-fval = fval.
    append wa_bdcdata to bdcdata..
endform.
*&      Form loggs
      text
--> p1        text
<-- p2        text
form loggs .
loop at mestab into wa_mestab.
    if wa_mestab-msgtyp = 'E'.
      call function 'FORMAT_MESSAGE'
        exporting
          id        = wa_mestab-msgid
          lang      = 'E'
          no        = wa_mestab-msgnr
          v1        = wa_mestab-msgv1
          v2        = wa_mestab-msgv2
          v3        = wa_mestab-msgv3
          v4        = wa_mestab-msgv4
        importing
          msg       = m
        exceptions
          not_found = 1
          others    = 2.
      wa_stats-mess = m.
      wa_stats-text = text-001.            "'Not Created'.
      wa_stats-auart_001 = wa_record-auart_001.
      "wa_stats-sernr = wa_flat-sernr.
      append wa_stats to stats.
    elseif wa_mestab-msgtyp = 'S'.
      call function 'FORMAT_MESSAGE'
        exporting
          id        = wa_mestab-msgid
          lang      = 'E'
          no        = wa_mestab-msgnr
          v1        = wa_mestab-msgv1
          v2        = wa_mestab-msgv2
          v3        = wa_mestab-msgv3
          v4        = wa_mestab-msgv4
        importing
          msg       = m
        exceptions
          not_found = 1
          others    = 2.
      if wa_mestab-dyname = 'SAPMIEQ0'
                                and wa_mestab-dynumb = '0101'
                                and wa_mestab-msgspra = 'E'
                                and wa_mestab-msgid = 'IS'
                                and wa_mestab-msgnr = '144'.
        loop at stats into wa_stats where auart_001 = wa_record-auart_001.
                                      "and sernr = wa_flat-sernr.
             delete stats.
        endloop.
            clear : wa_stats.
            wa_stats-mess = m.
            append wa_stats to stats.
      endif.
    endif.
    clear : wa_stats.
endloop.
endform.                    " loggs
Edited by: Naseeruddin on Nov 26, 2008 8:57 AM

MIGO-Error when MIGO is execute by call transaction on background

When we execute MIGO_TR or MIGO_GI in call transaction, this error is showed.
"RAISE_EXCEPTION" " "
"CL_GUI_CUSTOM_CONTAINER=======CP" or "CL_GUI_CUSTOM_CONTAINER=======CM001"
"CONSTRUCTOR"
Is there any alternate function available for the MIGO and avoiding the same error.
Thanks in advance.
Walter

Hi Walter,
MIGO is a SAP Enjoy transaction so BDC is not supported on the same.
Regards,
Atish

Call Transaction in background mode

Hi everyone,
What I am currently trying to do is to perform a 'call transaction' while forcing the 'background processing' mode even when the user is running the program in online mode; this allows me to retrieve a lot more messages that are useful to the user than the messages generated in online mode.
As long as I have seen there is no field for that in the options table that can be passed to the 'call transaction' sentence. The only way to see that behavior while in online mode is by 'playing back' a recording thru the SHDB transaction and checking the 'Simulate background' option.
My first attempt was to set the SY-BATCH flag before doing the call transaction but it doesn't work, the flag seems to reset itself with the correct value during the call.
Any comments on this would be greatly appreciated.
Regards,
Sergio

You would have to create a job on the fly to do this. This example shows how to kick off a background job via an ABAP program.
report zrich_0004 .
data:   sdate type sy-datum,
        stime type sy-uzeit,
        l_valid,
        ls_params like pri_params,
        l_jobcount like tbtcjob-jobcount,
        l_jobname like tbtcjob-jobname.
start-of-selection.
* Get Print Parameters
call function 'GET_PRINT_PARAMETERS'
       exporting
            no_dialog      = 'X'
       importing
            valid          = l_valid
            out_parameters = ls_params.
* Open Job
l_jobname = 'ZRICH_0005'.
call function 'JOB_OPEN'
       exporting
            jobname = l_jobname
       importing
            jobcount = l_jobcount.
* Submit report to job
submit zrich_0005
       via job     l_jobname
           number l_jobcount
       to sap-spool without spool dynpro
           spool parameters ls_params
              and return.
* Schedule and close job.
call function 'JOB_CLOSE'
       exporting
            jobcount = l_jobcount
            jobname   = l_jobname
            strtimmed = 'X'

Call transaction in background in report

I have a report in which I call a transaction, but the requirement is that I have to call it in background.
Can you please suggest how I can achieve this.
<removed_by_moderator>
Edited by: Julius Bussche on Aug 26, 2008 3:20 PM

Hi charles,
Use the mode 'N'
Example:-
DATA:
fs_opt TYPE ctu_params.
fs_opt-dismode = 'N'.
CALL TRANSACTION 'PA30' USING t_bdcdata OPTIONS FROM fs_opt.
Luck,
Bhumika

Call Transaction in Background for IW52

Hi All..
When i execute my BDC (Call Transaction) in foreground, the code will update IW52 screens without any errors/warnings.
But if we schedule this in background, the IW52 screens are not getting updated.
Even there are no Errors observed.
We have used the syntax as follows..
CALL Transaction IW52 using it_bdcdata MODE 'N' messages into it_bdcmsg.
Can anyone help me how to rectify it and make it to execute successfully in background mode..??
Your Help will be highly appreciated..
Regards
Pavan

Hello Friends...
I am running a call Transaction code in Background mode.
I am facing Error message..
If i run the same in foreground, it is working fine...
Error Message is "No Batch Input data for screen <SAPNV screen No>"
Expecting your guidence in this case...
Regards
Pavan
Message was edited by:
Pavan Sanganal

Not able to execute custom transaction in Background mode

Dear All,
There is a custom modele pool program to update the data in info type 9003. We have written a Z program in that we are calling this custom modele pool through CALL TRANSACTION with mode 'N' and update 'S'.
Z Program is running successfully and updating data in 9003 info type when we run in foreground mode.
But it is not updating when runs in Background mode.
Am I need to take any other precautions when run in background mode for custom transaction?
We are using 4.6C version.
Thanks in advance.
Regards,
Abaper

For custom transactions you shouldn't have a problem - unless you're trying to do something that needs dialog with the presentation server.
Set an infinite loop in the custom transaction, launch your program in backround, then from Sm50, go to debug and find out what's going on.
DATA: debug.
WHILE debug IS INITIAL. " Debug from SM50 will get you here, change field DEBUG in the
ENDWHILE. " debugger to contain 'X', and the loop will end.
Also, if your custom tx calls any standard SAP programs/FM, there is a chance that those programs work differently in background than foreground.

CALL Transaction in background not working pls help URGENT

hi i have writtin a bdc program which uses CALL TRSANCTION everything is working in foreground.
if i schedule the program in background the call transaction does not work. any idea why?????????
pls help its urgent

hi
good
have you checked in the debug mode, if you have checked in the debug mode check wheather it is giving any error before data is displaying in the screen, if any error is displaying as a message than check that error why it is coming there.
If no error is coming than check your flow of the bdc screen in the debug mode , there must be some prob, so that it is not working in the background.
thanks
mrutyun^

Error while executing pgm RMMR1MRS in background

Hi Experts,
when executing pgm RMMR1MRS ( T-code MRRL) in background , when i check job log am getting errors and warnings , but when executed manually it is working fine ,
can you guide me what might be the problem.
Thank's in advance,
Aby.

closed

Require Job name in SM37 while executing call transaction in background

Similar Messages

Maybe you are looking for