Issue with Compliance Calibrator 5.2 SP9 Background Jobs

Hello,
I'm having an issue with Compliance Calibrator 5.2 SP9 where If I run a role analysis as a background job that has the same parameters as a previously run role analysis background job, the second job that is run will display a failure message. It does not appear to matter if the similar background jobs were run by the same individual or separate individuals. As long as the job that was previously run is still in the background job history, than any job with the same parameters run by a user will fail.
Is this normal operation for CC?
Is there a configuration change that could allow a job to be rerun in the background multiple times?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?
Thanks for the help it's much appreciated,

To better clarify what is occurring, the 1st job will run and complete successfully and return/display the appropriate results correctly. The 2nd job will than be subsequently kicked off and finish same as with the previous job except when you open the background results no data is displayed and the message at the bottom reads: Failed to display result. To make more sense of what Iu2019m doing, these are the logical steps Iu2019m following:
1. Select Role Level analysis
2. Enter parameters for analysis
3. Schedule background job to run immediately
4. View background job results (successful job and correct results)
5. Select Role Level analysis (with same or any other user)
6. Enter same parameters as step 2 for analysis
7. Schedule background job to run immediately
8. View background job results (successful job, but the error message: u2018Failed to display resultu2019, instead of seeing the CC reports)
I believe the error is somewhere in the running of a job with the same parameters (Same Role and same Report Type). If I delete the previous jobs from the background history that have the parameters Iu2019m using and try the analysis again, a third time, with the same parameters as before, it will run successfully and display the correct results.
Is this normal and acceptable operation for CC5.2 SP9?
Is there a configuration change that would allow a job to be run in the background multiple times with the correct CC results?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?

Similar Messages

Having issues with accurate calibration of distances for running?

Anyone having problems with accurate calibration of distances when running, with iPod touch?

The Nike+ app that comes with the iPod requires use of the shoe sensors that must be purchased separately.
This app uses the sensor built into the iPod. Note that not all the feature are available on the iPod since it does not have GPS
Nike+ Running for iPhone 3GS, iPhone 4, iPhone 4S, iPhone 5, iPod touch (3rd generation), iPod touch (4th generation), iPod touch (5th generation) and iPad on the iTunes App Store

Issues with black psd files on black backgrounds when exported to PDF.

Hello there,
I'm having an issue since I upgraded to leopard and moved all my stuff from my old macbook pro (running OSX 10.4) to my new macbook pro (running OSX 10.5). CS3 didn't seem to have any problems before but now when I export an Indesign file with a black background containing a photoshop layered tif with a black background to pdf, the appears to be a big difference between the blacks - the Indesign file's black appears to be a mid grey.
Any help would be appreciated!
Here's how it all looks in InDesign: http://aycu14.webshots.com/image/48613/2005862333507831436_rs.jpg
But this happens when exported and viewed in Acrobat (or preview etc.): http://aycu02.webshots.com/image/49801/2005871851784365159_rs.jpg

In ID prefs go to Appearance of Blacks
and set both instances to display Blacks Accurately.
You will need to measure the rich black in the Tiff and make a rich black swatch in ID and use that for your book cover. now the blacks will match.

Issue with 32 bit mapping while doing the job configuration.

Hello,
From my end, facing a strange issue while execution of job in 32-bit mode.
As part of the solution implementation, do have one excel file which has to be imported to my database. For this activity, have created a package in SQL 2012 and changed the project properties to 32-bit (by setting False from the Run64bitRuntime). With this
implementation, It has worked fine without having an issue.
As we are going with the project deployment model, have deployed this package to Integration Services Catalogs. From my end, have executed the package by choosing the option to execute in 32-bit Runtime and It is also worked fine.
From my end, have configured the same package through job by mapping the package from SSIS Integration Catalog. Now, the job is getting failed as the package is not running in 64-bit mode. Have tried to configure the package in 32-bit mode. But, I
could not be able to configure the same. I am getting the option of 32-bit run time when I am going with File System,SSIS package store not with the SSIS Catalog.
From your end,could you please help me in resolving this issue?
SSIS Package Store--> Execution Options
SSIS Catalog--> ????
Regards,
Pradeep.

But it is a job property, not the catalog:
Arthur My Blog

Background Job not Printing TOs immediately

Hello experts,
I am having an issue with printing Transfer Orders created by background job, the output requests are sent to the output controller with status '-' . It works when I manually create the TOs or if I run the RLAUTA10 program with my userID in SE38 .
I have set the background job user default print parameters in SU3 to print immediately.
Also in the Job step, I have set up the print parameters to 'print immediately'
I have assigned printer for sorce storage type & set the indicator to use the source sto type in OMLV, The printer seems to be determined correctly, I've checked the Spool request name & printer in the spool controller, only issue seems to be the print not being triggered immediately.
Not sure, if there is some other setting that I have to make to be able to print the TOs created by the background job immediately.
Any help would be appreciated.
Thanks
Kris T

whether the printer which you assigned is configured in SAP (network printer)? or LOCL?
printing may not happen if LOCL(background job)
Thanks

Issue with Visibility Settings for Backgrounds and Layers

I am using Acrobat Pro XI 11.0.10 (Windows) and having an issue with visibility settings for layers and backgrounds. I am attempting to get backgrounds to appear while viewing in Adobe Reader and Acrobat Pro but not be printed and so far have had no success.
When using a background the Appearance Options dialogue has "Show when printing" unchecked, but "Show when displaying on screen" is checked. This results in the background not showing on the screen, and the background will only appear once the box for "Show when printing" is checked. It looks like the option for printing is dictating whether or not the background is able to appear.
Using layers has not worked either. The background layer is set to "Never Prints", but will still show up when printed.
I was wondering if anyone else has run into this and has a solution, or has any recommendations.
Thanks in advance.

Hi setrev2012,
How are you adding the backgroud?
The only way I can think to accomplish this is via a watermark.
The basics...
Open PDF in Acrobat. Choose Pages > Watermark > Add Watermark.
Select a jpg or PDF of your background and adjust scaling options as desired.
Then click the Appearance Options.. and uncheck the Show When Printing option.
In this image the PDF is a blank page with the word "Test" on it. The watermark is the stamp and impression (a stock photo jpg).
If you want a solid color background, just create a flat image of the background color for use as the watermark.
If you have already followed the steps and still facing the issue then please share the file with me at [email protected] so that i can have a look.
Regards,
Rave

Effdt issue with PT8.50.12

After upgrading from PT8.49.04 to PT8.50.12 found the fundamental issue with Effective Date. For example on JOB table the effdt date criteria get added automatically to query with additional join on EFFSEQ field which causes issue for all batch process and PS Query. Oracle accepted it as known bug in PT85012 which get fixed in PT85013 tool release.

It is the same for PeopleTools 8.51, and we just put the PeopleTools 8.51.13 in our test system,
Unless I'm wrong or that's a typo, the PTools patch 8.51.13 is not available for download yet (1st of Sept). The last one being 8.51.12 dated from 19th of August.
Nicolas.

Assigning Jobclass to Background Jobs

Dear BW Gurus,
Regards.We got an situation : We schedule an Infopackage as Background Job (JOB A),with default Jobclass-> C.Hence the background job runs with Jobclass>C in the Source system(SAP R/3) aswell.Now when the Endusers run programs in the Background(Source system(SAP R/3 ) (JOB B),they assign Jobclass-->A(High Priority),Hence the sytem allocates the Workprocess id (assigned to our JOB A) to the Background Job(JOB B) with High priority,and finally our Background job is still "ACTIVE",but without no WorkProcess id assigned to it !!!(For more than 30 hours!!!).This has happened earlier aswell and it would be really helpful if some one could throw light on this issue.Should we
1) Leave the Job undisturbed (would the system allocate anyother WP to the job??)
2) Kill the Background job ??
Thanks
Shiv

Dear BW Gurus,
Regards.We got an situation : We schedule an Infopackage as Background Job (JOB A),with default Jobclass-> C.Hence the background job runs with Jobclass>C in the Source system(SAP R/3) aswell.Now when the Endusers run programs in the Background(Source system(SAP R/3 ) (JOB B),they assign Jobclass-->A(High Priority),Hence the sytem allocates the Workprocess id (assigned to our JOB A) to the Background Job(JOB B) with High priority,and finally our Background job is still "ACTIVE",but without no WorkProcess id assigned to it !!!(For more than 30 hours!!!).This has happened earlier aswell and it would be really helpful if some one could throw light on this issue.Should we
1) Leave the Job undisturbed (would the system allocate anyother WP to the job??)
2) Kill the Background job ??
Thanks
Shiv

Initiating Background Job in R3 through XI

Hi,
I have an important issue here. How to initiate a background job in R3 (ABAP object) through XI.
Thanks in advance,
Bhanu P R Gattu

Hi Bhanu P R Gattu !
You can have XI to execute a custom R3 RFC (rfc adapter receiver). That custom RFC could trigger the background job.
You will need to define what event triggers the whole scenario..e.g. File-XI-RFC?
Regards,
Matias.
ps:please award points if helpful

Multiple background jobs to fill set-up tables in LO

Hi,
Can we schedule multiple background jobs for filling the same set-up table concurrently - obviously with non-overlapping selections.
ex: one background job for filling order# 1000 to 100,000
one background job for filling order#100,001 to 200,000
Both jobs running at same time.
Thanks,
Anita S.

Hi Anitha,
Yes we can Schedule Multiple Setup Jobs for the same Application wiht the Diff Ranges of selections.
It is possible and i have tried in our project.
Egg:-
We did a Reload of some doc that were missing in BI.
Did selective deletion of those corrupted data in some Data targetsand filled the Setup tables wiht those selection conditions (in our case 10 diff selection).
We ran this jobs in Background simultaniously when all the jobes finished we have ran the Full Repair Requests of those 10 selections to those respective data targets.
Hope this gives you enough clarity.........!!!
Best Regards,
VNK.

4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
Any ideas?
-Scott

Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
Notes 1006083 and 985617 are needed for this procedure.
Thanks for all the suggestions.
-Scott

Virsa CC 5.1: Issue with Background Job

Dear All,
I almost finished configuration of our new Compliance Calibrator dashboard (Java stack of NW'04). But, unfortunately, have an issue with SoD analysis now.
Using SAP Best Practice recommendations, we have uploaded all functions, business processes and risks into CC database, and then successfully generated new rules (there are about 190 active ones in our Analysis Engine).
I also configured JCo to R/3 backend and was able to extract the full list of our users, roles and profiles. But somehow background analysis job fails.
In job history table I see the following message: "Error while executing the Job:null", and in job log there is an entry, saying that "Daemon idle time longer than RFC time out, terminating daemon 0". But it's quite strange, as we use default values: RFC Time Out = 30 min, and daemons are invoked every 60 seconds.
Please, advise whether you had similar issues in your SAP environment and, if yes, how you resolved them.
Thanks,
Laziz

Hi Laziz
I am now just doing the first part of CC. May I know your details in how to configured Jco To R/3 Backend? Do you need to create any SM59 for connection T in R/3? If yes, I am lacking of the details to do that if you could help? Thank you.
Regards
Florence

I have been having a issue with getting the colors on my monitor to match the colors fro my print lab. I now have the monitor calibrated to match the prints but when I open elements it doesn't use the same colors. If i have it use the calibrated profile b

I have been having a issue with getting the colors on my monitor to match the colors fro my print lab. I now have the monitor calibrated to match the prints but when I open elements it doesn't use the same colors. If i have it use the calibrated profile by changing the color management settings, the color picker no longer shows true white or black. How do I get elements 12 to honor the new calibrated settings?

Ok so I've done what you said and this is what it's come back ....
I don't know that these are the errors , but they're the things which don't look right ...
Throughout the shut down there is a recurring line ;
It says ;
Com.apple.launchd 1 0x100600e70.anonymous.unmount 301 PID still valid
Then there are 2 more which I think are related ;
Com.apple.securityd 29 PID job has I overstayed its welcome , forcing removal.
Then the same with fseventd 48 and diskarbitrationd 13
Oh and on Launchd1 : System : stray anonymous job at shut down : PID 301 PPID13 PGID 13 unmount...
Then the last process says "about to call: reboot (RB_AUTOBOOT).
Continuing...
And stops ...
Hope this means something to you ... Thanks again for your help so far :-)

Issue with desktop Opt/Click (right click) & 'Change Desktop Background'

I have an issue with the opt/click in the desktop in ML 10.8.2. The 'Change Desktop Background' using opt/click (right click) works after reboot, but fails to open (work correctly) thereafter. The 'System Preferences' icon bounces in the dock but nothing else happens, I have either click on the SP icon or re-opt/click (R click) again to get it working. All else seems to be in order but not this. I have tried this with 2 complete full installs & still doesn't work correctly (same issue. I have reported it to Apple, but I was wondering if anyone else experiencing this problem?

So, here's what I've learned so far.
Fresh reboot. Works fine. Close and try again, doesn't work. This you already know.
Here's what I tried to see if it makes a difference:
I removed:
~/Library/Caches
~/Library/Preferences/com.apple.finder.*, com.apple.systempreferences.* and com.apple.desktop.*
That didn't help.
I tried it in safe mode. Same issue.
Here's something interesting I noticed. If you open terminal and killall Finder, that refreshes it and makes it work again... for 1 try.
This does, in fact, seem like a bug.
For reference, I'm currently on a mid 2012 macbook pro. Running fully updated on mt lion.

Issue with background job--taking more time

Hi,
We have a custom program which runs as the background job. It runs every 2 hours.
Itu2019s taking more time than expected on ECC6 SR2 & SR3 on Oracle 10.2.0.4. We found that it taking more time while executing native SQL on DBA_EXTENTS. When we tried to fetch less number of records from DBA_EXTENTS, it works fine.
But we need the program to fetch all the records.
But it works fine on ECC5 on 10.2.0.2 & 10.2.0.4.
Here is the SQL statement:
EXEC SQL PERFORMING SAP_GET_EXT_PERF.
SELECT OWNER, SEGMENT_NAME, PARTITION_NAME,
         SEGMENT_TYPE, TABLESPACE_NAME,
         EXTENT_ID, FILE_ID, BLOCK_ID, BYTES
   FROM SYS.DBA_EXTENTS
   WHERE OWNER LIKE 'SAP%'
   INTO
   : EXTENTS_TBL-OWNER, :EXTENTS_TBL-SEGMENT_NAME,
   :EXTENTS_TBL-PARTITION_NAME,
   :EXTENTS_TBL-SEGMENT_TYPE , :EXTENTS_TBL-TABLESPACE_NAME,
   :EXTENTS_TBL-EXTENT_ID, :EXTENTS_TBL-FILE_ID,
   :EXTENTS_TBL-BLOCK_ID, :EXTENTS_TBL-BYTES
ENDEXEC.
Can somebody suggest what has to be done?
Has something changed in SAP7 (wrt background job etc) or do we need to fine tune the SQL statement?
Regards,
Vivdha

Hi,
there was an issue with LMT's but that was fixed in 10.2.0.4
besides missing system statistics:
But WHY do you collect every 2 hours this information? The dba_extents view is based on really heavy used system tables.
Normally , you would start queries of this type against dba_extents ie. to identify corrupt blocks and such:
SELECT owner , segment_name , segment_type
        FROM dba_extents
       WHERE file_id = &AFN
         AND &BLOCKNO BETWEEN block_id AND block_id + blocks -1
Not sure what you want to achieve with it.
There are monitoring tools (OEM ?) around that may cover your needs.
Bye
yk

Issue with Compliance Calibrator 5.2 SP9 Background Jobs

Similar Messages

Maybe you are looking for