Compliance Calibrator: Background jobs didn't bring in the correct data.

Hi Gurus;
In Compliance Calibrator; background jobs were last run on 5/27/09 but the management report shows that the summary is as of 5/20/09. That should have been updated uptill 5/27/09 and the new number of conflicts should have come up, which it didn't. What can be the problem?
Thanking you;
Raja

Hi Harleen;
This job was actually set by the client. So when I went to check the parameters of the jobs, I found that the field MGR_ANALYSIS consists of Field value "N". Does this mean that the Management Analysis box was not ticked when this job was scheduled?
Regards;
Raja

Similar Messages

HT1657 Can i get a refund for a rental i didn't view before the expiration date?

Can i get a refund for a rental i didn't view before the expiration date?
I wasn't able to tranfer the movie to the ipad, and couldn't view it on my pc.

All purchases are considered final, but you can try contacting iTunes support and see if they will give you a refund or credit : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page, then Purchases, Billing & Redemption

Background job - programs all running at the same time...

Hi experts,
i have an issue regarding background job.i have to run multple programs in background one after another in one program.so i am using function modules job_open,submit and job_close.
my problem all the jobs are statrting at same time .but i want to run after completion of first job second job should start.
please guide me
Thanks
sai
Edited by: Julius Bussche on Feb 19, 2009 9:36 AM
Please use meaningfull subject titles

Try something like
LOOP AT it_filenames INTO ts_filenames.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname = jobname
       IMPORTING
            jobcount = jobcount.
SUBMIT program
    WITH p_file1 = ts_filenames-zzfname
    VIA JOB jobname NUMBER jobcount
    AND RETURN.
IF sy-tabix EQ 1.
    CLEAR: pred_jobcount,
           pred_jobname.
    GET TIME.
    IF sy-uzeit LT '235950'.
      sdlsstrttm = sy-uzeit + 10.
      sdlstrtdt = sy-datum.
    ELSE.
      sdlsstrttm = '000010'.
      sdlstrtdt = sy-datum + 1.
    ENDIF.
ELSE.
    sdlsstrttm = '      '. " no_time from LBTCHTOP
    sdlstrtdt = '        '. " no_date from LBTCHTOP
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = jobcount
            jobname              = jobname
            predjob_checkstat    = ' '
            pred_jobcount        = pred_jobcount
            pred_jobname         = pred_jobname
            sdlstrtdt            = sdlstrtdt
            sdlstrttm            = sdlstrttm
       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.
pred_jobcount = jobcount.
pred_jobname = jobname.
ENDLOOP.
I removed the checkstat, cause if you want to check the status you only have to submit one job with multiple steps. (Put JOB_OPEN and JOB_CLOSE out of the loop)
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname = jobname
     IMPORTING
          jobcount = jobcount.
LOOP AT it_filenames INTO ts_filenames.
SUBMIT program
    WITH p_file1 = ts_filenames-zzfname
    VIA JOB jobname NUMBER jobcount
    AND RETURN.
ENDLOOP.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount = jobcount
          jobname   = jobname
          strtimmed = 'X'.
Regards

How to check why some of the Cron jobs didn't ran at the scheduled time?

This is my first question ever on the forum. Hope I'm following the format of posting the thread.
I could find a similar query on the forum but couldn't find the exact answer.
Versions:
Oracle: 11.2.02.0
Linux: Linux xxxxx 2.6.32.12-0.7-default #! SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/LINUX
In our crontab there are lot of scripts that ran at the scheduled time. Around 3 reports didn't ran at the scheduled time today?
There is no error or some error mail saying that those reports got failed. They just didn't ran at that time.
How to find out why those jobs didn't ran?
Is there anything like cron log or something like that to trace it?
Please guide me. Thanks in advance.

977789 wrote:
This is my first question ever on the forum. Hope I'm following the format of posting the thread.
I could find a similar query on the forum but couldn't find the exact answer.
Versions:
Oracle: 11.2.02.0
Linux: Linux xxxxx 2.6.32.12-0.7-default #! SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/LINUX
In our crontab there are lot of scripts that ran at the scheduled time. Around 3 reports didn't ran at the scheduled time today?
There is no error or some error mail saying that those reports got failed. They just didn't ran at that time.
How to find out why those jobs didn't ran?
Is there anything like cron log or something like that to trace it?
Please guide me. Thanks in advance.Since this question has nothing to do with Oracle Databases and everything to do with Linux functions and usage, it would be better asked in the [url https://forums.oracle.com/forums/forum.jspa?forumID=135]Linux Forum
When posting there, you can save yourself a bit of time by going ahead and showing the line from crontab for a report that "didn't run", and perchance the script itself. Best enclosed in the / tags to preserve formatting.

Background Job get Cancelled when executing the report. Reason?

Hi All,
I have scheduled a Back ground Job and executed Immediately.
when checking transacion SM37 the job get canceled.
How to find out the problem for the Job Cancellation.
Regards,
Viji

hi
After scheduling back ground job ( give a time laps of 2 min )
then go to sm37 ( at this moment , the job is not yet started) .
select ur job in sm 37 and when job starts processing , type JDBG as the command and press enter.
Now it will go to the debugging screen, where u will find system program . Now set a break point at the stements used in ur program from the debugging screen itself.( menu - breakpoint- breakpoint at - statement ) and press F8 .
Now you can start debug ur code.
Revrt back if any issues.
Regards,
Naveen

Selecting one of VI windows from the bottom of WinXP didn't bring up the VI

I opened several VI windowss and other application softwares. After switching to another windows (not Labview) and back, I found that I couldn't open the VIs. They were listed in the bottom bar of WinXP. However, when I chose one of them, the VI window didn't show up. If I right-clcik a VI and chose "Maximu", the VI showed up but cannot be resized. That's really strange. How to solve this problem? Thanks.

LabView opens windows for a VI's front panel and diagram in the locations at which they were last saved. It sounds like the VI you're having trouble with was saved to a location off the screen, maybe on another computer with a different screen resolution.
When you maximize a window, it's displayed to fill the visible screen, regardless of the original window position. For any Windows window, you can't resize the window when it's maximized. You have to Restore it before you can resize it. But for you, the restore puts it back off the screen where you can't see it.
Normally, in Windows, you move a window by grabbing its title bar with the move and dragging it around. If you can't see the window, you can't use the mouse to move it. But you can use the cursor arrow
keys to move it.
1. Left-click on the task bar button for the VI so it's depressed. Left-click on the task bar is a toggle button: click once and the window is displayed; click again and it's minimized. The task bar button will be depressed when the window is displayed and raised when it's minimized.
2. Right-click on the task bar button for the VI and select Move.
3. Press and hold each of the cursor arrow keys, one at a time, and watch for an empty rectangle to move across the screen. If you don't see a rectangle after holding one cursor key for about 5 seconds, try another key.
4. When you see a rectangle on the screen, press Enter and the window will be displayed.
5. Save the VI with the windows in the desired position.

Information Broadcasting job didn't start at the precalculationserver

Problem: we start workbook-precalculation-jobs in broadcasting but you see only the bi-job in the sm66/sm50 and it never goes to the precalculation server.
At the moment is he only workaround to cancel the job and start the precalculationservice again.
Who had the same problem and know amentments

Have your Basis person check to make sure the RFC connection between BW and Precalc is functioning.
Sounds like you only have one precalc. Even though you do, you might want to specifiy that precalc server in your broadcast setting for the report, rather than accepting the system default. This has been a bug for some SP levels. Check for OSS Notes regarding precalc server and your particular BW version and SP level. The precalc functionality has had a variety of bugs over time, some that may only exist for a particular SP.

Provide brings back the actual date , different to the table content

Hi,
I´m not a developer, but must do that part now in my company.
We have a 46C with actual packages.
In a customer report I have to add 2 fields to an output.
It selects from PNP and provides data like follows:
GET PERNR.
PROVIDE * FROM P0000
FROM P0001
FROM P0002
FROM P0006
FROM P0007
FROM P0013
FROM P0016
FROM P0053
    BETWEEN PN-BEGDA
        AND PN-ENDDA.
That worked fine.
Now I liked to set 2 fields with contents of IT 0000 (table PA0000):
    IF P0000-MASSG = '01'.            " MA aktuell im Vorruhestand ?
     TRANS-BEGVORRST = P0000-BEGDA.
     TRANS-ENDVORRST = P0000-ENDDA.
    ENDIF.
At debugging I can see, that the requested fields from P0000 are set to the actual date, not to the value I can select from table or shown in the SAP transaction.
All other fields from PA0000 are matching the row I expect, but not the date fields
Any idea?

Hi,
That is the behavior of PROVIDE statement. If you combine (JOIN) several tables (P0001, P0002, etc) together, it will give you all the intersected dates.
For example, in two tables itab1 and itab2, the respective columns col1 and col2 are interval limits of type i. The filling of the internal tables results in the following intervals (rows two and three):
|   Itab1 Int1    |     |Itab1 Int2 |     |
|        |      Itab2 Int1       |        |
| |          ... BETWEEN ...             |
| | i1 |   i2   | i3 |   i4   |i5|     | <<<< This is the result
Regards,
Lim...
Edited by: Ruslim Chang on Apr 17, 2009 11:26 AM

Adding Printer from Print and Fax does not bring up the correct Window.

Hi,
When I first had my Macbook, OSX Leopard, I tried adding a printer and saw that the Window that popped up allowed me to add printers from IP, Windows, Local, Etc.
However, when I came back to add a printer now, all I get is this window:
http://img502.imageshack.us/img502/2748/picture1vc9.png
That window pops up when I press the + on this window:
http://img264.imageshack.us/img264/8923/picture2sc1.png
I remembered when I press the + button, it would come up with a different window than the one I get now, which allowed me to add a printer from Windows, among other options.
Please let me know if the window I get right now is supposed to happen. I can't add any printers from the window I get now.
Thanks alot.

Just to add a bit of clarity to the previous response, you need to click on the clear, oval widget at the upper right-hand corner of the the window. That will reveal the Toolbar with the options for IP, Windows, etc.

Background job SWFSLSDLEX cannot be scheduled (error )"

Hi All ,
i got the following error ,
when i try to customize the SWU3 " Schedule background job for dead line monitoring ".
The error is :
"Work item -: Background job SWFSLSDLEX cannot be scheduled (error )"
And the Error log says :
Refer to your workflow system administrator.
The specified error number should indicate possible reasons for the error. It is possible that the system is in an inconsistent state. The scheduled start of the specified background job must be compared with the minimum date/time of all work items in table SWWDHMIN. It may be necessary to delete the scheduled background job by hand and reschedule it by calling report RSWWDHEX.
Apparently i dont see any table SWWDHMIN.
Thanks!
Richard A

The issue is solved by adding start profile and instance profile to operation modes.
Many thanks to my BASIS Guys for solving it !
Richard A

Compliance Calibrator Job Run

Hi;
I have submitted a job to run in Compliance Calibrator as job type = immidiate, but the job does not appear to start and sits in ready status in State column. Can anyone guess, what the problem can be?
Regards;
Sumanta

Hello,
This is known issue with GRC AC, please stop and start application "sap.com/grc~ccxsysbgear " from Visual Administrator - then you need to wait for some time and it should be started.
Visual Administrator --> Server -->Services --> Deploy --> Choose Application --> sap.com/grc~ccxsysbgear -
> Stop and then Start.
Hope this helps.
Thanks
Davinder

Re: Virsa Compliance Calibrator & Pre-defined SOD Rule Set

Hi All,
We have installed the Virsa Compliance calibrator 5.1 in our sandbox environment. When we goto the "Rule Architect" tab under Compliance calibrator using tcode /virsa/zvrat it brings up the page with Rules information.
Per the Virsa documents that i read they have mentioned that there are pre-defined SOD Rules (Transaction codes and Tcode objects) that we can use in the Rule Architect.
My question is how do i enable and use those pre-set SOD Rules that Virsa provides by default. I do not see them under the Rule architect tab though. Can someone give some pointers to use these pre-set SOD rules.
Thanks & Regards
-Murali

Hi Laziz,
Thanks for your patience in replying to my CC 5.1 queries. I did follow your steps for the Generate Rule & Background Job-> Schedule Analysis and scheduled the job immediate.
However, when i looked up the status of the scheduled analysis Background Job-> Search pulls up the job i scheduled at the top it reads "Job scheduler Status: unknown error" . I clicked on "View Log" button and it shows some messages as shown below (Note: I am just posting some parts of the error msgs below. but it still goes for 1 page...)
May 16, 2007 1:09:07 PM com.virsa.cc.xsys.bg.BgJobDaemon init
INFO: *** BgJobDaemon loaded
May 16, 2007 1:11:09 PM com.virsa.cc.common.util.ConfigUtil setDefaultJ2EEParam
WARNING: Cannot get Application URL: null. PLEASE SET 'Background Daemon URL' IN CONFIGURATION TAB
java.lang.NullPointerException
     at com.virsa.cc.common.util.ConfigUtil.setDefaultJ2EEParam(ConfigUtil.java:203)
     at com.virsa.cc.common.util.ConfigUtil.getBgJobStartURL(ConfigUtil.java:192)
     at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:45)
     at java.lang.Thread.run(Thread.java:534)
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.ReportPack50SP1_01 class: com/virsa/cc/extreport/ReportPack50SP1_01/ReportPack50SP1_01.class
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: Jar Entry length=1568 compressed size=1568 actual read=1568
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtActbyRsk_Act_RskLvl class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtActbyRsk_Act_RskLvl.class
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: Jar Entry length=13210 compressed size=13210 actual read=13210
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtRolbyRsk class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtRolbyRsk.class
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: Jar Entry length=19287 compressed size=19287 actual read=19287
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.CrtProfbyRsk class: com/virsa/cc/extreport/ReportPack50SP1_01/CrtProfbyRsk.class
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: Jar Entry length=12807 compressed size=12807 actual read=12807
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: class name: com.virsa.cc.extreport.ReportPack50SP1_01.UsersbyOrgLevels class: com/virsa/cc/extreport/ReportPack50SP1_01/UsersbyOrgLevels.class
May 16, 2007 1:24:37 PM com.virsa.cc.extreport.JarClassLoader loadClassData
FINEST: Jar Entry length=18557 compressed size=18557 actual read=18557
May 16, 2007 1:24:59 PM com.virsa.cc.common.util.ConfigUtil setDefaultJ2EEParam
WARNING: Cannot get Application URL: null. PLEASE SET 'Background Daemon URL' IN CONFIGURATION TAB
java.lang.NullPointerException
I am not sure whats causing this and it's been 2hrs since i scheduled the user analysis but i don't see any data still appearing in the fron-end..Any pointers again???
Thanks
-Murali

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

How to cancel the background job processing in ABAP programming?

Hi,
I have a requirement where i need to cancel the job depending on some constraint. My code is something like this:
Select some data from the table.
if sy-subrc = 0.
Do nothing.
Else
Cancel the job
call function 'BP_JOB_ABORT'
exporting
   jobcount                         = number
    jobname                          = name
EXCEPTIONS
   CHECKING_OF_JOB_HAS_FAILED       = 1
   JOB_ABORT_HAS_FAILED             = 2
   JOB_DOES_NOT_EXIST               = 3
   JOB_IS_NOT_ACTIVE                = 4
   NO_ABORT_PRIVILEGE_GIVEN         = 5
   OTHERS                           = 6
The above code is cancelling the job but it is throwing an exception called CX_SY_DYN_CALL_PARAM_MISSING because i dint pass job count. How can we find the job count of next job that is going to run? Or How to handle the exception which it is throwing. Even if i try to handle that exception something like this:
TRY
call function 'BP_JOB_ABORT'
exporting
   jobcount                         = number
    jobname                          = name
EXCEPTIONS
   CHECKING_OF_JOB_HAS_FAILED       = 1
   JOB_ABORT_HAS_FAILED             = 2
   JOB_DOES_NOT_EXIST               = 3
   JOB_IS_NOT_ACTIVE                = 4
   NO_ABORT_PRIVILEGE_GIVEN         = 5
   OTHERS                           = 6
RAISE EXCEPTION TYPE CX_SY_DYN_CALL_PARAM_MISSING.
CATCH
CX_SY_DYN_CALL_PARAM_MISSING.
ENDTRY.
It avoids the exception but it doesnt cancel the job. I even tried with function modules like JOB_OPEN
JOB_SUBMIT,BP_JOB_SELECT,BP_JOB_ABORT and tried to build some logic using status overview table (TBTCO) and TBTCP (Jobstep overview table).
Can someone suggest me the right way to write this program ?
Thanks in advance.
Rashmi

Hi,
Problem is solved.
Create an background job with 2 steps. The first step in the background job calls the program ZBACKJOB_STEP1. In the variant we have a wrong material number
If the material number is not found in Mara, the next step in the job should not get executed and the job should get cancelled..
In the above posts i had asked how do I get the job count of the job that is currently triggering the program at the runtimeu2026..If u see the below code uu2019ll get to know.. We have to use the standard structure TBTCM which captures the properties/characteristics of the job.
REPORT ZBACKJOB_STEP1.
TABLES: MARA,TBTCM.
PARAMETERS : MATNR TYPE MATNR.
START-OF-SELECTION.
SELECT SINGLE * FROM MARA WHERE MATNR = MATNR.
IF SY-SUBRC IS INITIAL.
    WRITE / : 'This is the material selected on the selection-screen' , MARA-MATNR.
ELSE.
        CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
      IMPORTING
        EVENTID                                    = TBTCM-EVENTID
        EVENTPARM                             = TBTCM-EVENTPARM
        EXTERNAL_PROGRAM_ACTIVE = TBTCM-XPGACTIVE
        JOBCOUNT                                = TBTCM-JOBCOUNT
        JOBNAME                                  = TBTCM-JOBNAME
        STEPCOUNT                              = TBTCM-STEPCOUNT
      EXCEPTIONS
        NO_RUNTIME_INFO                    = 1
        OTHERS                                     = 2.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'BP_JOB_ABORT'
        EXPORTING
          JOBCOUNT                                     = TBTCM-JOBCOUNT
          JOBNAME                                       = TBTCM-JOBNAME
        EXCEPTIONS
          CHECKING_OF_JOB_HAS_FAILED = 1
          JOB_ABORT_HAS_FAILED              = 2
          JOB_DOES_NOT_EXIST                   = 3
          JOB_IS_NOT_ACTIVE                      = 4
          NO_ABORT_PRIVILEGE_GIVEN       = 5
          OTHERS                                         = 6.
      IF SY-SUBRC <> 0.
      ENDIF.
    ENDIF.
ENDIF.
Regards,
Rashmi

Background Job processing

After writing a report, I used this Function Module LIST_TO_ASCI to copy my report to an internal table (DOWNTAB) because Ill use that internal table to download a text file on the server using dataset.
Here is my code:
FORM DL_REP_SERVER.
   DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
        MV_FILE2 LIKE RLGRAP-FILENAME.
DATA: BEGIN OF DOWNTAB OCCURS 1,
          LINE(150),
        END   OF DOWNTAB.
CLEAR: MV_FILE2.
MV_FILE2 = J:/Downloads/Report.txt.
CALL FUNCTION 'LIST_TO_ASCI'
       EXPORTING
            LIST_INDEX         = SY-LSIND
       TABLES
            LISTASCI           = DOWNTAB
            LISTOBJECT         = ABAP_LIST
       EXCEPTIONS
            LIST_INDEX_INVALID = 1
            OTHERS             = 2.
OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
IF SY-SUBRC <> 0.
    IF SY-SUBRC = 8.
      MESSAGE E037 WITH 'File could not be opened'.
    ELSE.
      MESSAGE E037 WITH 'Error occurs in downloading the file'.
    ENDIF.
ENDIF.
LOOP AT DOWNTAB.
    TRANSFER DOWNTAB TO MV_FILE2.
ENDLOOP.
CLOSE DATASET MV_FILE2.
ENDFORM.                    " DL_REP_SERVER
My big problem is this, when Im running my program ordinarily (not as background job), Im getting all the pages downloaded correctly but when I run it as background job (using SM36), Im only getting the last page of my report being downloaded. Definitely, I cant debug it because its in background. I cant figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
command line ( no '/' ), put the cursor on the job and press enter - will
take you to the job in debug mode.
You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
Steps
1. Create variant called BACKGROUND for program to be debugged.
2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
3. Execute transaction SM50.
4. Select process that runs ZDEBUGBG.
5. Goto 'Program/Session' 'Program' 'Debugging'.
A se80 debug session will open.
6. Change variable W_EXIT to 'E'.
7. Step thru (F6) until ZWBTEST comes up.
1. Go to Transaction SM66 and find your work porocess.
Select the line work process is on and click on the Debugging button.
If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
goto SM37 and from Program menu(not sure.. try other menu's)
-->Catchjob . it will goto the active job in debugging mode.

Compliance Calibrator: Background jobs didn't bring in the correct data.

Similar Messages

Maybe you are looking for