Job cancelled in source BI

Hi there,
In BI 3.5 I created an InfoObject VCUSTOMER using 0CSUTOMER as template. Works and looks great.
Now I want to transfer this VCUSTOMER to another BI. I created an Export-DataSrc and replicated it in the destination BI. Works fine.
Next I created an InfoPackage to transfer the data from source to destination BI.
But the job seems to be cancelled already in the source system. That's what I get from checking in SM21. There are a few lines of alerts for the user ALEREMOTE, which refers to my attempts to transfer data from one BI to the other. The first alert number is F61 and it says "TemSe-In/Output on file that is not open" (in german).
Any hints? I tried 3 times, and it always cancels the job.
By the way, I succeeded doing the same thing before. Only with the Business Content object 0CUSTOMER. That worked fine.
Cheers,
Stefan

Stefan,
you cannot load data onto a reference IOBJ .. if you have transferred VCUSTOMER into the new BI , and if it is the same reference IOBJ , then you can see the data in 0CUSTOMER in VCUSTOMER , you cannot maintain specific master data for VCUSTOMER..
Arun
Assign points if useful

Similar Messages

Job was cancelled in source sytem.

Hi,
One job was in cancelled state in source system itself.How can i correct the error?how can i get the data from source sytem.could please anybody help me out on this issue please.In RSMO,in that statu tab its stating as JOB OVERVIEW,by clicking onto this its leads to,r/3.by executing this one it shows as job cancelle.update method is delta.
Thanks & Regards,
Praveena.

Hi anil,
one ODS is getting nearly 500000 of records,it is loading master data,here the problem is that in details tab processing process is well all the datapackets are getting fine data,but at transfer tab after processing of infoidocs,dataidocs should be filled,but there it self problem is getting.in status tab its is in yellow status i cant forcibly make it into green.how can i solve this issue.And please give me reply more detaily about RSODSACT tbale details,what are changes can be done by using this table.
Thanks & Regards,
Mano.

Jobs are cancelled in source system

hI all,
i scheduled process chain. load was chain was failed .failed request is showing jobs are cancelled in source system? why jobs are cancelled in source system & how to solve this error.
Thanks,
chandu

Try to repeat the process manually, as a temporary fix.
Check in SM58 and BD87 for pending tRFCs and IDOCS and puch them using F6
But you can analyze as advised by BR and Venugopal.
Hope it helps,
Naveen
Edited by: Naveen Vytla on Jul 21, 2008 2:46 PM

BWREMOTE background job canceled in sap r/3 system

Hi my friends,
Thanks for your help ahead.
Today I checked the background job in SAP R/3 created by BWREMOTE via SM37. It showed me some jobs had been canceled.
I displayed its log, the detail message is:
==========================================
Step 001 started (program SBIE0001, variant &0000000083494, user name BWREMOTE)
DATASOURCE = ZQM_NOT_SHFGRP
Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,593 records
Result of customer enhancement: 1,593 records
Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,593 records
ABAP/4 processor: SAPSQL_INVALID_FIELDNAME
Job cancelled
==========================================
Then I displayed the "Long Text" of the job log. It is
One of the field names in the SELECT clause was not recognized.
Error analysis
The SELECT clause was specified in an internal table at runtime.
It contains the field name "TPR00", but this does not occur in any of
the database tables listed in the FROM clause.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLXRSA " in
"EXIT_SAPLRSAP_001".
The main program was "SBIE0001 ".
Source code extract
008840 concatenate 'TPR'
008850 day_temp+6(2)
008860 ' = '
008870 ' ''' zshift '''' into
008880 cond .
008890 append cond to itab .
008900 select schkz into i_not_shfgrp-zzschkz from t552a
008910 where zeity = '2'
008920 and mofid = 'CN'
008930 and mosid = '28'
008940 and ( schkz = 'SFTA' or
008950 schkz = 'SFTB' or
008960 schkz = 'SFTC' or
008970 schkz = 'SFTD' )
008980 and kjahr = day_temp+0(4)
008990 and monat = day_temp+4(2)
> and (itab) .
009010 endselect.
I guess that there is not a field named TPR00 in table t552a.
Next, I opened the 'project management of sap enhancement' via CMOD, entering the project name and chosing 'Display'.
Then Double click the Components 'EXIT_SAPLRSAP_001', we can see the function module 'EXIT_SAPLRSAP_001'. In the source codes, there is an include program, it is 'INCLUDE ZXRSAU01.'.
Then, I double clicked the Include program and find the position program terminated. The source codes are:
ZQM_NOT_SHFGRP *
when 'ZQM_NOT_SHFGRP'.
loop at c_t_data into i_not_shfgrp .
l_tabix = sy-tabix .
clear :mbatch ,zshift,cond ,zfield, zcharg, day_temp .
refresh itab.
if i_not_shfgrp-ausvn is initial.
else.
aa = '080000'.
bb = '160000'.
cc = '235959'.
day_temp = i_not_shfgrp-ausvn.
if i_not_shfgrp-auztv ge aa and
i_not_shfgrp-auztv lt bb .
zshift = 'MSHF' .
elseif i_not_shfgrp-auztv ge bb and
i_not_shfgrp-auztv le cc .
zshift = 'LSHF'.
else .
zshift = 'NSHF'.
day_temp = i_not_shfgrp-ausvn - 1.
endif.
concatenate 'TPR'
day_temp+6(2)
' = '
' ''' zshift '''' into
cond .
append cond to itab .
select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) .
endselect.
endif.
I found that we got a TPR00 during concatenation. In other words, day_temp+6(2) = 00. But I think it is impossible. I can not explain this.
Any ideas, my friends. Many thanks.

select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) . => doesn't make sense?!
endselect.
endif.
it seems something got deleted between 'and' and '(itab)'... so, you'll have to recheck the requirements for your select to fill the 'and' statement further.
so, it should look like
and monat = day_temp+4(2)
and <some kind of condition that needs to be fulfilled>.
endselect.
<some logic to fill a line in your internal table>.
append cond to itab.
endif.
obviously <some kind of condition that needs to be fulfilled> needs to be replaced by a real condition
and <some logic to fill a line in your internal table> needs to be replaced by some kind of formula
I assume something like (otherwise it would be really weird to select that field):
cond = i_not_shfgrp-zzschkz.
or a formula using the i_not_shfgrp-zzschkz field.
It would also be a lot better to replace your select ... endselect by a select single as you'll be selecting 1 record only anyways.
Message was edited by:
RafB

Job terminated in source system - Request set to red during delta load

Hi All,
There is issue with the delta load where as full load works fine and it results in below job termination with below log.
Job started
Step 001 started (program SBIE0001, variant &0000000128086, user ID ALEREMOTE1)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDITM
RLOGSYS    = BWP_010
REQUNR     = REQU_DA9R6Y5VOREXMP21CICMLZUZU
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 17173577728                             *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000000                                 *
ztta/roll_extension........... 2000000000                              *
Object requested is currently locked by user ALEREMOTE1
Job cancelled after system exception ERROR_MESSAGE
Please help me to resolve this issue.
Thanks,
Madhu,

Hello,
As per the screen shot provided below, data soruce belongs to LO, so first check in RSA7, whether it has got mark in RSA7, for which you have entries in RSA7 against the data source. If you are not able to find the data source in RSA7, then you need to set-up the update methods, based on the requirement.
1) Direct Delta
2) Queued Delta
3) Unserialised V3 Update
Once it is done, Delete the Previous Initilisation, again perform the Re-Init With Out data and now schedule the Delta Data Loads
Hope this may Help you.
Thanks
PT

Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_

Hi All,
can any one help on this issue.
I run the BI statistics in production and found out the error while triggering the delta's
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Error msg : Job terminated in source system --> Request set to red
Message no. RSM078
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS = BCLNT300
REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE = D
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 2147483648 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000320 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
But delta laoding for same is working in DEV...but not in prod...
Please suggest
Regards
Shweta

Swetha
finally found out the notes.
Please look into them and ask you basis to implemnt,
1161940
1106569
1145041
1146851
Please have a look and ask for implemtation in your system which are suitable for you
We also faced the same issue job termination in source system for BI Statistics
Regards#
Srini

0CRM_SALES_ACT_1 Cancelled in Source System

Hi, I'm having problems with a BI7 dataload, from our CRM source system, based upon the 0CRM_SALES_ACT_1 datasource. I've cleared down the data in my related InfoProviders, deleted all PSA requests and previous Delta Inits, and I'm now trying to load a new Init with Data Transfer. The job progresses so far (229,398 records) and then gets cancelled in the source system with the error message: "User is not integrated into organizational structure"
I've done some searching on SDN and can't find anyone posts with the same issue - my apologies if I've mised the key one.
I've reactivated the transfer structures using the activate all program in se38, and carried out an RSRV on the InfoProviders.
It was working when I last reloaded the data a few weeks ago, so something has changed either on the source system or the BI7 system since then, but I can't figure out why it's suddenly getting cancelled at source. It's also taking over 16 hours to get to this stage, whereas the last successful Init ran in four hours.
I've included the last part of the job log from the source system, showing the last successful data package and then the final system error message.
Any advice or help on this would be greatly appreciated.
01.07.2010 10:02:20 Asynchronous send of data package 38 in task 0042 (1 parallel tasks)
01.07.2010 10:02:20 tRFC: Data Package = 37, TID = AC10026B18944C2C4F29EB3A, Duration = 00:00:02, ARFCSTATE =
01.07.2010 10:02:20 tRFC: Start = 01.07.2010 09:17:44, End = 01.07.2010 09:17:46
01.07.2010 10:51:54 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5,882 records
01.07.2010 10:51:54 Result of customer enhancement: 5,882 records
01.07.2010 10:51:54 Asynchronous send of data package 39 in task 0043 (1 parallel tasks)
01.07.2010 10:51:54 tRFC: Data Package = 38, TID = AC10026B1A7C4C2C599D01C0, Duration = 00:00:02, ARFCSTATE =
01.07.2010 10:51:54 tRFC: Start = 01.07.2010 10:02:20, End = 01.07.2010 10:02:22
01.07.2010 11:09:00 User is not integrated into organizational structure
01.07.2010 11:09:00 Job cancelled after system exception ERROR_MESSAGE
Kind regards,
Jeff.

Hi, there's no short dump.
Kind regards,
Jeff.

SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

Dear all ,
One of the scheduled background job has been cancelled .
Kindly check the below loga and Background job details .
Job name        SAP_COLLECTOR_FOR_PERFMONITOR
Job class       C
Status          Canceled
(ABAP Program
Name           RSCOLL00
Variant
Language       EN)
Job Log :
30.05.2010 06:20:32 Job started
30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV                       on server PRDCIXI
30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
30.05.2010 06:20:39 Clean_Plan:finished
30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
30.05.2010 06:20:43 Job cancelled
Kindly suggest

Dear all ,
Kindly check the ST22 error logs .
Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). 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: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" 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 System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
for detail log.
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 7 2010 21:00:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 246
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1217248
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 1050520
MM Free. 146024
and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4BFF227871E00187E10080000A369120"
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
Program............. "RSHOST3M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
rmation on where terminated
Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
The main program was "RSHOST3M ".

Job termination in source system /Asynchronous transmission of info IDoc 2

Hi All,
We have certain loads that we do every 2 hours, which will run for 20 to 30 minutes to load current year BCS data into a Basic Cube. So, In total we schedule 12 times in a day. This is needed as we have users around the globe.
We have totally 10 BGD processes and 10 Dialog processes.
These loads are scheduled through a process chain and we submit three parallel jobs at a time based on the version and in total we have 15 loads, 5 per each parallel job.
We went live with this process yesterday and the jobs ran all well until today afternoon, when they started giving the following message and when I checked the log of the process chain, one of the InfoPackage did fail with job termination in the source system.
The job log is as follows:
Date       Time     Message text                                                                 Message class Message no. Message type
06/20/2007 13:55:47 Job started                                                                       00           516          S
06/20/2007 13:55:47 Step 001 started (program SBIE0001, variant &0000000014146, user ID RFCUSER)      00           550          S
06/20/2007 13:55:47 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)          R3           413          S
06/20/2007 13:55:47 DATASOURCE = 80BCS_VC10                                                           R3           299          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 *          Current Values for Selected Profile Parameters               *         R8           049          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:55:47 * abap/heap_area_nondia......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heap_area_total.......... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 * abap/heaplimit................ 40894464                                *        R8           050          S
06/20/2007 13:55:47 * zcsa/installed_languages...... EFD                                     *        R8           050          S
06/20/2007 13:55:47 * zcsa/system_language.......... E                                       *        R8           050          S
06/20/2007 13:55:47 * ztta/max_memreq_MB............ 2047                                    *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_area................ 3000320                                 *        R8           050          S
06/20/2007 13:55:47 * ztta/roll_extension........... 2000683008                              *        R8           050          S
06/20/2007 13:55:47 *************************************************************************         R8           048          S
06/20/2007 13:58:04 NONE                                                                             UGBW          001          E
06/20/2007 13:58:04 Job cancelled after system exception ERROR_MESSAGE                                00           564          A
I do not have acceess in BWP to get you the Data Transfer Parameters within BW system.
Any suggestions would be greatly appreciated.
Thanks & Best Regards,
- Shashi

Hi Shashi,
Check in st22 for any dumps, do you have any pointer there?
Also check sm21 to identify possible cause of errors.
Regards.

Job terminated in source system SAPSQL_SQLS_INVALID_CURSOR

Hi all,
can any one help on this issue.
I run the BI statistics and found out the error while triggering the delta's
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS    = BCLNT300
REQUNR     = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE    = D
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 2147483648                              *
abap/heaplimit................ 40894464                                *
zcsa/installed_languages...... ED                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000320                                 *
ztta/roll_extension........... 2000683008                              *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
Edited by: BW User on Nov 10, 2008 11:41 AM

Hi Arun,
Source system is also BW itself..No idocs have been archived.
For other BI statistics its running fine only for this one,,,,it is getting error.
If i didi INIT W/O data tarnsfer and running the delta,,,delta is failing
If i did INIT With data then 20000 records are comming after trying to run the delta again the same error is ocmming
Regards

SAP_COLLECTOR_FOR_PERFMONITOR job cancellation

Hello SAP,
The SAP Standered job "SAP_COLLECTOR_FOR_PERFMONITOR job cancelled due to DUMP                    "CONNE_ILLEGAL_TRANSPORT_HEADER".
DUMP details:
The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Could you please let me know how to resolve this issue.
Thanks & Regards
Prabhu
Edited by: Prabhu on Jul 23, 2009 1:05 PM

HI,
Here is the log :
Runtime Errors         CONNE_ILLEGAL_TRANSPORT_HEADER
Date and Time          07-26-2009 05:49:42
Short text
IMPORT dataset cannot be interrupted.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
Error analysis
In this particular case, already the header of the dataset is invalid.
More precisely: The first byte of the dataset, which is
used for security purposes, is already invalid.
User and Transaction
Client.............. 000
User................ "BATCH-USER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4A65E5E38F2F6948E10000000AFC02C1"
Program............. "SAPLSEU_COMPONENT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSEU_COMPONENT" - in
"RS_COMPONENT_VIEW".
The main program was "SAPMS07A ".
In the source code you have the termination point in line 35
of the (Include) program "LSEU_COMPONENTU01".
The program "SAPLSEU_COMPONENT" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BATCH-USER"
Job Number..... 04494200
Source Code Extract
Line
SourceCde
5
*"     VALUE(LANGUAGE) LIKE SY-LANGU DEFAULT SY-LANGU
6
*"     VALUE(OBJECT_TYPE) LIKE TADIR-OBJECT OPTIONAL
7
*"     VALUE(REFRESH) LIKE SY-INPUT OPTIONAL
8
*"     VALUE(WITHOUT_TREE_SETTING) LIKE SY-INPUT OPTIONAL
9
*"     VALUE(IGNORE_SFW_SWITCHES) TYPE CHAR1 DEFAULT SPACE
10
*" TABLES
11
*"      NODETAB STRUCTURE SNODETEXT
12
13
14
DATA: subrc LIKE sy-subrc.
15
DATA: l_delete TYPE i.
16
DATA: date LIKE sy-datum.
17
18
CLEAR sy-subrc.
19
date = sy-datum.
20
REFRESH nodetab. CLEAR nodetab.
21
G_IGNORE_SFW_SWITCHES = IGNORE_SFW_SWITCHES.
22
23
IF object_type = 'FUNC'.
24
object_type = 'FUGR'.
25
ENDIF.
26
IF object_type = space.
27
object_type = 'APPL'.
28
ENDIF.
29
apid-langu = language.
30
apid-type = object_type.
31
32
IF refresh IS INITIAL.
33
get table "nodetab" of all object lists
34
of the desired type "object_type":
>>>>>
IMPORT date nodetab FROM DATABASE dwtree(ap) ID apid
36
ACCEPTING PADDING.
37
subrc = sy-subrc.
38
ENDIF.
39
40
IF subrc NE 0 OR refresh = 'X'.
41
IF object_type = 'APPL' OR
42
object_type = 'DEVC'.
43
CASE object_type.
44
WHEN 'APPL'.
45
PERFORM get_components TABLES nodetab.
46
WHEN 'DEVC'.
47
PERFORM get_devc_view TABLES nodetab.
48
ENDCASE.
49
IF without_tree_setting IS INITIAL.
50
CALL FUNCTION 'RS_TREE_CONSTRUCT'
51
TABLES
52
nodetab = nodetab
53
EXCEPTIONS
54
OTHERS = 4.
Edited by: Prabhu on Jul 26, 2009 12:17 PM

Reg: job termination in source system

hi experts
can anyone tell me solution for this problem after loading infopackage, status of the infopackage is showing is like this "job termination in source system", but i checked with ss it showing job gets cancelled. but i am not assigned any to the data source, so how can eliminate this problem.
regards
harikrishna.N

HI
This can happen when request IDOC is sent source system, but the source system for some reason is not available.
Ensure that source system is available. Change technical status of request to red and delete request from datatarget. Trigger Infopackage again to get data from source system.
Cheers,
Raj

Job cancelled While loading data from DSO to CUBE using DTP

Hi All,
while i am loading data frm DSO to CUBE the job load is getting cancelled.
in the job overview i got the following messages
SYST: Date 00/01/0000 not expected.
Job cancelled after system exception ERROR_MESSAGE
wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

hi,
Are u loading the flat file to DSO?
then check the data in the PSA in the date field and replace with the correct date.
i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
so clear the data in PSA and then load to DSO and then to CUBE.
If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

Job cancelled after system exception ERROR_MESSAGE

Hello all
I am facing the following issue.
A custom report is schedulled and run as backround job. The report should create a txt file on server.
The report works fine in foreground, but as backround job ends up cancelled all the time.
The job log:
Job log overview for job:    VI5 / 13072800
Date       Time     Message text                                                                     Message class Message no. Message type
27.03.2009 13:09:28 Job started                                                                           00           516          S
27.03.2009 13:09:28 Step 001 started (program ZESSRIN110R, variant PR1_0000381, user ID METAPARTNER)      00           550          S
27.03.2009 13:09:28 File creation ERROR:                                                                  00           001          E
27.03.2009 13:09:28 Job cancelled after system exception ERROR_MESSAGE                                    00           564          A
There is no info in SM21 regarding the error.
Can anybody help with this?
Thanx in advance.
imi
Edited by: Imrich Vegh on Mar 27, 2009 2:27 PM

btw the part of my code looks like this:
server path check
    IF p_srv IS NOT INITIAL.
      OPEN DATASET gv_server FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
      IF sy-subrc EQ 0.     --- I keep receiving 8 here in BACKGROUND JOB
        WRITE : / text-077, gv_server.
      ELSE.
        MESSAGE text-069 TYPE 'E'.
      ENDIF.

Job Cancelled Problem

Hi Masters,
In SM37 I seen that 3 jobs were cancelled.
Pls see below:
======
Job started
Step 001 started (program RSSTAT1, variant &0000000002410, user name ALEREMOTE)
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status ; Action Start
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status @08@; Action Callback
Report RSSTAT1 completed with errors
Job cancelled after system exception ERROR_MESSAGE
How to investigate cancelled jobs under ALEREMOTE? How can i know this cancelled Job's request is assigned for what task.?
How to rerun a cancelled job? Pls tell steps.
Please suggest me.
Thanks,
BW26.

Hi,
it looks like you have an authority problem with aleremote. But anyway, did you check the syslog (sm21) or the dump overview (st22)? Are there any problems logged for the run time of the job?
regards
Siggi
PS: Have look here it might be of some help for you! /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Message was edited by: Siegfried Szameitat

Job cancelled in source BI

Similar Messages

Maybe you are looking for