PMI Monitoring job is canceled.

Hi,
My XI system is running on XI 3.0 SP13. End-to-End Monitoring is based on PMI. When I activated the
end-to-end monitoring in advance setting I have given every 10 Minutes the pmi has to collect. When I am running background job "44949495949330.." with abap program "SPI_PS_ASSEMBLE_DSP" is scheduled to run every 10 min. But this job is getting status of red saying job is concealed with job log as follows.
Job started
Step 001 started (program SPI_PS_ASSEMBLE_DSP, variant &0000000000088, user ID AKRT00)
12/14/2005 06:02:39: Assembling started for <XI Domain domain.65.netweaver50 11/23/2005 04:17:18>
No new data since last run - processing stopped
The input data is invalid
Job concealed after system exception ERROR_MESSAGE.
Can any body help me how to rectify this error.
Thanks in advance..
Thanks & Regards,
Mallikarjun.M

Hi Arjun,
Try checking your input data.It might not be in the right format.
regards,
Prash

Similar Messages

Job getting cancelled for 'Chain not processed for date-2007031920070318' ?

Hi All,
We have 2 process chains running only on weekdays - one for sales and the other for billing. A cancelled job is created for one of the process chains with the job log message as 'Chain not processed for date-2007031920070318' for the not run days whereas the other does not have any issues though the same monitor job program runs for both. The difference is only in the variant but nothing much other than that its maintained for 2 different chains.
   We also debugged the monitor job program. It basically does nothing other than displaying messages depending on the status of the chain log.
Please let me know your suggestions as to why it happens.
Thanks,
krishna

it is also giving following error message:
Caution: Program has changed
Caution: At time of termination, Active source code no longer available and after above two statements its giving sign "?" before every statement in below manner:
024300 ?     lit_ekpo_dummy1[] = it_ekpo[].
024310 ?     DELETE lit_ekpo_dummy1 WHERE ebeln NE tab1-ebeln.
024320 ?     DESCRIBE TABLE lit_ekpo_dummy1 LINES count01.
024330 ?
024340 ?     REFRESH lit_ematn_dummy[].
024350 ?     lit_ematn_dummy[] = lit_ematn[].

Delta uploading job get cancelled in SAP R/3

question, during delta loading from SAP R/3 to BW, if the delta uploading job get cancelled twice for some reason, will I lost some delta data??
Pls advise!
Many Thanks!
rajatina.

Hi,
If your delta jobs are getting error out in BW then you don't need to worry about, because till that time your delta pointer in source system is not yet updated. But if you make any request green by chance in BW monitor then your delta pointer will get updated and you might loose some delta.
You can request repeat delta multiple times without any issue.
Regards,
Durgesh.

In LO Cockpit, Job contol job is cancelled in SM37

Dear All
   I am facing one problem. Pl help me to resolve that issue.
When ever I am scheduling the delta job for 03 (Application Component), that is cancelled in SM37. Hence, I couldn't retrive those data from queued delta MCEX03 (smq1 or lbwq) to RSA7 because of job is cancelled. When I have seen that job log I got below Runtime Errors. Please hep me to resolve this issue
Runtime Errors         MESSAGE_TYPE_X
Date and Time          04.10.2007 23:46:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Structures have changed (sy-subrc=2)
Long text of error message:
Technical information about the message:
Message class....... "MCEX"
Number.............. 194
Variable 1.......... 2
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU02"
"MCEX_UPDATE_03"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks in advance
Raja

LO EXTRACTION:
First Activate the Data Source from the Business Content using LBWE
For Customizing the Extract Structure LBWE
Maintaining the Extract Structure
Generating the Data Source
Once the Data Source is generated do necessary setting for
Selection
Hide
Inversion
Field Only Know in Exit
And the save the Data Source
Activate the Data Source
Using RSA6 transport the Data Source
Replicate the Data Source in SAP BW and Assign it to Info source and Activate
Running the Statistical setup to fill
the data into Set Up Tables
Go to SBIW and follow the path
We can cross check using RSA3
Go Back to SAP BW and Create the Info package and run the Initial Load
Once the Initial delta is successful before running delta load we need to set up V3 Job in SAP R/3 using LBWE.
Once the Delta is activated in SAP R/3 we can start running Delta loads in SAP BW.
Direct Delta:- In case of Direct delta LUWs are directly posted to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUWs are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
Queued Delta: - In case of Queued Delta LUWs are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUWs, which are missed.
V3 -> Asynchronous Background Update Method Here by seeing name itself we can understand this. I.e. it is Asynchronous Update Method with background job.
Update Methods,
a.1: (Serialized) V3 Update
b. Direct Delta
c. Queued Delta
d. Un-serialized V3 Update
Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.
a. Update methods: (serialized) V3
Transaction data is collected in the R/3 update tables
Data in the update tables is transferred through a periodic update process to BW Delta queue
Delta loads from BW retrieve the data from this BW Delta queue
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Issues:
Even though it says serialized , Correct sequence of extraction data cannot be guaranteed
V2 Update errors can lead to V3 updates never to be processed
Update methods: direct delta
Each document posting is directly transferred into the BW delta queue
Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
Update methods: queued delta
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
Update methods: Un-serialized V3
Extraction data for written as before into the update tables with a V3 update module
V3 collective run transfers the data to BW Delta queue
In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3.This BW Delta queue is read when a delta load is executed.
Issues:
Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
V2 update has to be successful
Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.
Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.
Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
V1 - Synchronous update
V2 - Asynchronous update
V3 - Batch asynchronous update
These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.
Taking an example -
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed...), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.
V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (e.g. in LBWE definitions) to process these. This is again to optimize performance.
V2 and V3 are separated from V1 as these are not as real time critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.
Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.
hope it will helps you.....

How to send a mail to the user when a job gets canceled?

Hi experts,
                  I need to send a mail when a job gets canceled to the user.I know the FM for sending mail and i can find if a job is canceled from tbtco,but i want to know how to send the mail from the same program ,once it got canceled ?
thanks in advance,
helpful answers will be awarded with points
regards,
ashwin

Hi Ashwin
Use the below peace of code:
REPORT ZBCJOBMONITOR .
TABLES: SOMLREC90,
        TBTCO.
DATA: MAILDATA   LIKE SODOCCHGI1.
DATA: MAILTXT    LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
DATA: MAILREC    LIKE SOMLREC90 OCCURS 0 WITH HEADER LINE.
DATA: I_TBTCO    LIKE TBTCO OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001 .
SELECT-OPTIONS: S_JOB FOR TBTCO-JOBNAME.
SELECT-OPTIONS: S_JOBC FOR TBTCO-JOBClass.
SELECT-OPTIONS: S_REC FOR SOMLREC90-RECEIVER.
SELECTION-SCREEN END OF BLOCK B1.
START-OF-SELECTION.
CLEAR:    MAILDATA, MAILTXT, MAILREC, I_TBTCO.
REFRESH: MAILTXT, MAILREC, I_TBTCO.
PERFORM GET_ABENDED_JOBS.
PERFORM BUILD_RECEIVERS.
LOOP AT I_TBTCO.
    PERFORM BUILD_TEXT_MESSAGE.
    PERFORM SEND_MAIL_NODIALOG..
ENDLOOP.
     Form BUILD_TEXT_MESSAGE
FORM GET_ABENDED_JOBS.
SELECT * FROM TBTCO
          INTO CORRESPONDING FIELDS OF TABLE I_TBTCO
                     WHERE JOBNAME IN S_JOB
                       AND STATUS = 'A'
                       AND JOBCLASS IN S_JOBC
                       AND SDLSTRTDT = SY-DATUM.
ENDFORM.
     Form BUILD_TEXT_MESSAGE
FORM BUILD_TEXT_MESSAGE.
DATA: DATE(10) TYPE C.
DATA: TIME(10) TYPE C.
MAILDATA-OBJ_NAME = 'MONITOR'.
MAILDATA-OBJ_DESCR = 'Batch Job Monitor'.
MAILDATA-OBJ_LANGU = SY-LANGU.
CONCATENATE 'Job Name:' I_TBTCO-JOBNAME
              INTO MAILTXT-LINE SEPARATED BY SPACE.
APPEND MAILTXT.
PERFORM FORMAT_DATE USING I_TBTCO-SDLSTRTDT
                            DATE.
CONCATENATE I_TBTCO-SDLSTRTTM+0(2) ':'
              I_TBTCO-SDLSTRTTM+2(2) ':'
              I_TBTCO-SDLSTRTTM+4(2)
                 INTO TIME.
CONCATENATE 'Start Date/Time:' DATE TIME
            INTO MAILTXT-LINE SEPARATED BY SPACE.
APPEND MAILTXT.
CONCATENATE 'Job Class:' I_TBTCO-JOBCLASS
            INTO MAILTXT-LINE SEPARATED BY SPACE.
APPEND MAILTXT.
MAILTXT-LINE = 'Job has terminated abnormally'.
APPEND MAILTXT.
ENDFORM.
     Form BUILD_RECEIVERS
FORM BUILD_RECEIVERS.
LOOP AT S_REC.
    CLEAR MAILREC.
    MAILREC-RECEIVER = S_REC-LOW.
    MAILREC-REC_TYPE = 'U'.
    APPEND MAILREC.
ENDLOOP.
ENDFORM.
     Form SEND_MAIL_NODIALOG
FORM SEND_MAIL_NODIALOG.
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
       EXPORTING
            DOCUMENT_DATA              = MAILDATA
            DOCUMENT_TYPE              = 'RAW'
            PUT_IN_OUTBOX              = 'X'
       TABLES
            OBJECT_HEADER              = MAILTXT
            OBJECT_CONTENT             = MAILTXT
            RECEIVERS                  = MAILREC
       EXCEPTIONS
            TOO_MANY_RECEIVERS         = 1
            DOCUMENT_NOT_SENT          = 2
            DOCUMENT_TYPE_NOT_EXIST    = 3
            OPERATION_NO_AUTHORIZATION = 4
            PARAMETER_ERROR            = 5
            X_ERROR                    = 6
            ENQUEUE_ERROR              = 7
            OTHERS                     = 8.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.
     Form FORMAT_DATE
FORM FORMAT_DATE USING IN
                       OUT.
CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
            DATE_INTERNAL            = IN
       IMPORTING
            DATE_EXTERNAL            = OUT
       EXCEPTIONS
            DATE_INTERNAL_IS_INVALID = 1
            OTHERS                   = 2.
ENDFORM.
Regards,
Sree

Hai i am facing problem in solving the job which cancelled.

In monitoring the porocess chain the non loading process failed (AND PROCESS) when i went diplay messages the job was cancelled.how to correct the cancelled and where i have to correct.

Ashok,
Looks like you have raised a duplicate post for finding cancelled jobs in BI:
How to find the cancelled job
am locking the post mentioned since it appears to be a duplicate...

Report Job was cancelled upon user request???

Hi,
My reports take more than 10 minutes to complete, most times I get
"Report Job was cancelled upon user request".
error, how to fix this problem? Is there any time limit inside the report I can set.
Thanks

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

IMPORT MONITOR JOBS ERROR IN ECC 6 INSTALLATION

WARNING 2014-12-18 23:54:18
Execution of the command "C:\Program Files\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "E:\ECC EXPORT 1\EXPORT_51031897-1\EXP1;E:\EXPORT 2\51031897-2\EXP2;E:\EXPORT 3\51031897-3\EXP3;E:\EXPORT 4\51031897-4\EXP4;F:\EXPORT 5\51031897-5\EXP5;F:\EXPORT 5\51031897-5\EXP6;F:\EXPORT 5\51031897-5\EXP7;F:\EXPORT 5\51031897-5\EXP8;F:\EXPORT 5\51031897-5\EXP9;F:\EXPORT 5\51031897-5\EXP10;F:\EXPORT 5\51031897-5\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\AMC\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_13"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)Import Monitor jobs: running 1, waiting 3, completed 68, failed 0, total 72.Import Monitor jobs: running 2, waiting 2, completed 68, failed 0, total 72.Import Monitor jobs: running 3, waiting 1, completed 68, failed 0, total 72.Loading of 'SAPAPPL1_14' import package: ERRORLoading of 'SAPAPPL2_2' import package: ERRORImport Monitor jobs: running 1, waiting 1, completed 68, failed 2, total 72.Import Monitor jobs: running 1, waiting 1, completed 68, failed 2, total 72.Loading of 'D010TAB' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 68, failed 3, total 72.
this is the error i'm getting
i started oracle instance through command prompt but in vain. only four jobs r not completing.
i checked virtual memory.
please help me out.
thanks
krish

Hi Krish,
Welcome to SDN.
The installation log files would help figure out the exact error.
In the below case, the log file SAPAPPL2_2.LOG might give more information. Let us if the logs have any errors mentioned.
Logs should be in the <OS drive>\Program Files\sapinst_instdir\.... folfer.
Regards,
Srikishan

Transport of Transformation failed with RC= 12 and job: RDDEXECL cancelled in Target sytem

Gurus,
When i am importing the workbench request from dev to qty.
I am getting error : Program terminated (job: RDDEXECL, no.: 22321300).
Transformation contains only Endroutine.
Job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxxxxx were synchronized
The internal session was terminated with the runtime error UNCAUGHT_EXCEPTION (see ST2
Job cancelled.
When i see the dump it is througing errror at the method of following class.
CL_RSO_TLOGO_PERSISTENCY-CHECK_INITIALIZED
Could you please help. Thanks in advance.
Ashok

Hi Ashok,
In QA use program "RSTRAN_ROUT_RSFO_CHECK" to check and remove any inconsistencies for the transformations. After that again transport those transformations in new TR and import in QA.
Also you have to search "Transport of Transformation failed with RC= 12 and job: RDDEXECL canceled in Target system" by Dinesh Tiwari.
Check the reply of Fun Sébastien in http://scn.sap.com/message/13795238#13795238.

BW- CRM MSA: Job is cancelled when Generic variant is used

Hi Gurus,
We are trying to download BW Reports on Mobile Sales App. The implementation is working perfect when we create variants in BW and then fetch data in CRM.
But now we want to restrict data according to territory of the Mobile User. This is to be done with the help of "By Terr. ID" subscription, but when we use a generic variant and request data, the job is cancelled in BW system saying "Logon for BW user failed when starting a step."
Pls help as it very very very very very very urgent!!!

Sim, segue o dump.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          07.02.2011 09:20:01
Error analysis
    Short text of error message:
    Process PSAPROCESS, variant ZBRPCHAIN_LEVEL1_2LIS_11_VASTI is not schedu
    led waiting for event RSPROCESS D6OVUGNYV55HIR2Y3JEML7XT6
    Long text of error message:
     Diagnosis
         Process PSAPROCESS (variant ZBRPCHAIN_LEVEL1_2LIS_11_VASTI) needs
         to be started. According to the process chain maintenance, it needs
         to be scheduled while waiting for event
         ZBRPCHAIN_LEVEL1_2LIS_11_VASTI D6OVUGNYV55HIR2Y3JEML7XT6. However,
         this is not the case.
     System Response
         The chain is cancelled.
     Procedure
         In order to complete the chain run, follow these steps:
         1. Ensure that Start Using Metachain or API is selected in the
             variant maintenance for the start process. By doing so, you
             ensure that the chain is not restarted.
         2. Schedule the process chain.
         3. In the log view for the process chain maintenance, choose View
             -> Merge Active Version, and end the incorrect process using
             the respective context menu entry.
     Procedure for System Administration
    Technical information about the message:
    Message class....... "RSPC"
    Number.............. 006
    Variable 1.......... "PSAPROCESS"
    Variable 2.......... "ZBRPCHAIN_LEVEL1_2LIS_11_VASTI"
    Variable 3.......... "RSPROCESS"
    Variable 4.......... "D6OVUGNYV55HIR2Y3JEML7XT6"

LANDSCAPE FETCH job gets cancelled

Hello Guru's,
The LANDSCAPE FETCH job gets cancelled on solution manager system due to the below mentioned error and in order to fix it
we have already applied the SAP note 1335225 but, the issue still persists.
Right now, we have come across the SAP note 1108071 which says the job will get cancelled "if you made adaptive computing
settings in SMSY and the SLD is not accessible".
can any one help me with how to check the adaptive computing settings in the header data of the system.
Also, the SLD check from system via tcode:sldcheck is sucessfull and we could access the SLD via browser. Please find the
details below.
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SAPSLDAPI_MP0
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   ashb01wa06pr.global.aes.com
port number: 59000
user       : SLDAPIUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access d
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     3
=> Check whether the SLD is running!
Immediate reponse is highly appreciated
Best Regards,
S.Viswanathan

Hello,
Could you include the Landscape_fetch error you mentioned in your message?
I think the issue is still your SLD. At the bottom of SLDCHECK it tries to retreive business systems in SLD.
If it is successfull you will see something like:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
   yoursystem1
   yoursystem2
   yoursystem3
(more...)
Your SLD check shows that it cannot retrieve systems from the SLD:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Please make sure that you have configured your SLD according to the post-installSLD setup and configuration guide. If you still have problems, follow this toubleshooting process...
http://help.sap.com/saphelp_nw70/helpdata/EN/78/20244134a56532e10000000a1550b0/frameset.htm
Best Regards.
Edited by: Phil May on Sep 2, 2009 10:31 AM

Oracle Reports Server CGI - Report Job was cancelled upon user request.

I am running reports on the web through Forms using Run_Report_Object built in. I am using Oracle 9iAS Enterprise Edition Release 1(1.2.2.2.2), Forms 6i Patch 9 (6.0.8.18.3) and Reports 6i Patch 9 (6.0.8.18) using CGI implementation. Most reports are running fine, but I have one that produces 125 pages and we are getting the following messages in the browser:
Error: The requested URL was not found, or cannot be served at this time.
Oracle Reports Server CGI - Report Job was cancelled upon user request.
However if you look at the Reports Server Queue Status thru the browser it shows that the report did finish, but it took 16 minutes. But the user gets the above message in their browser window.
Is there a way to get the first page of the report to display, while the rest of the report finishes, so the browser window doesn't timeout and display the above error?
Any help would be greatly appreciated.

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

Background job is cancelled dut o variant not exist

Dear friends,
In my program I have created a variant using FM 'RS_VARIANT_CREATE', and after the creation of variant , i'm submitting the job immediately, but the job get canceled with error message, specified variant is not defined.
when i checked the VARID table the variant gets updated, the time differnce is approximately 8 sec for both varaint creation and job start timre. Can any one face this type of issue, could any one help on this.
Thanks for your time.
Best regards
Kumar.

Hi Kumar,
Right after you create your variant use the statement COMMIT WORK AND WAIT.
If it doesn't work you can do something like this
While f_found = space.
select * from varid
where report = 'XYZ'
and variant = 'MYVAR'.
if sy-subrc = 0.
f_found = 'X'.
else.
wait up to 1 seconds.
endif.
endwhile.
I still think try COMMIT WORK AND WAIT after calling RS_VARIANT_CREATE.
Kind regards,
Marius

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

Job getting cancelled in background scheduling

Hi,
I have written a report in the SAP HR system and it is to be scheduled in background. This program transfers the PERNRs from HR system to CRM system as partners in BUT000.The report works perfectly fine if it is run in foreground. When I run it in background the job gets cancelled and I get the job log having a message that it could not ascertain code page and the system exception ERROR_MESSAGE is raised. If anybody has any clues regarding this problem please help me.
Thanks & Regards,
Rahul.

Hi,
I Guess you are using container controllers in the Report, and all container contols requires help from Sap Gui for execution. I guess that is the reason it is failing in background . Please check on that aspect as well.
Hope this helps..

PMI Monitoring job is canceled.

Similar Messages

Maybe you are looking for