DSO Activation Job cancelled.

Hi ,
I loaded data to DSO and activated.
It took lot of time for activation so i cancelled the job of activation (Partially activated )and also started the deletion of the request.
Now deletion request also takes lot of time?
What is the best way to delete the request and what to do with existing deletion request?
Thanks and Regards,
MuraliManohar

Hello ,
if u want to delete previus request.........
create a process chain...... to load data from source system to PSA and then TO ODS...........in this process chain you can include process type "Delete previous request from PSA.............so that you dont store much data in PSA.........if you are doing full load on ODS ...u can delete the contents of ODS with process type Delete Contents of InfoProvider(for small data) ......
Another Method :
Dirctly from DSO you can delete particular request or at the table level also you can delete the request from the any data target.
Goto SE16 -> RSICCONT - > Provide the DSO Name and execute -> List of reuests in the DSO will be displayed->select u r request and delete it.
Hope it helps.
Regards
Vikas Sharma
Robert Bosch

Similar Messages

ABAP/4 processor: UNCAUGHT_EXCEPTION - Activation job cancelled short dump

Hi All,
I loaded data to the new table of ODS successfully. But the data is not available for reporting.
When i try to activate the request,it shows no error bt neither does data *** to active table .I checkd in sm37 for logs, it shows ABAP/4 processor: UNCAUGHT_EXCEPTION error. It shows that CX_SDB_ORA_PROGRAM_ERROR exception was raised.
I also checked in table RSODSACTREQ in SE16 and found that status was 0 (means activation successful) n operation was U (means updating) .........
The same problem persists for activation job for any ODS.......The support package has been upgraded from 11 to 14 recently.......
Please help me resolve this issue.
Regards,

Prithi,
Check out for invalid char's in the PSA.....
Check monitoring for invalid char's .. some time it will reach up to New data table and while activation it may get struc...
hope there is some prob with invalid char's aor length of char.... Special char..like @__ in PSA .
Cheer's
HVR.

BC Activation Jobs Cancelled

I had a couple of BC activation jobs fail overnight because the server was shut down.
In the Admin Workbench all of the objects are active (green lights).
Any advice on what I should do? I'm tempted to start the activation again but if all of the objects are active do I need to?

Hi,
My advice is restarting. Because the job was failed , few objects would have not been activated properly. So it is better to do it again.
With rgds,
Anil Kumar Sharma .P

Deadlock when deleting from rsstatmanpsa during DSO activation

We are experiencing intermittent Oracle deadlocks during DSO activation in our BI system. The deadlocks occur when the following SQL statement is executed:
      delete from rsstatmanpsa where
             partnr >= l_s_status-rnr_sid and
             psa     = l_s_status-dta.
This is at line 83 of the SET STATUS method of class CL_RSSM_STATMAN. (See below for runtime error details.)
When these errors occur the background job for the DSO activation is cancelled with the message ABAP/4 processor: DBIF_RSQL_SQL_ERROR. Strangely, when this occurs as part of a process chain, the status of the process variant does not get updated until/unless someone displays the process chain log, at which point the status changes and follow-on events are triggered. In other words, the process chain does not seem to be receiving word that the DSO activation process has abended, so we do not receive alerts that a problem has occurred.
Has anyone else experienced this issue?
Thanks,
Bob
P.S. We are running BI 7.0, Patch Level 15 on Oracle 10.2.0.4.0
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "SET_STATUS" "(METHOD)", nor was it propagated by a RAISING clause.
How to correct the error
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/DELE/RSSTATMANPSA ]"
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"CL_RSSM_STATMAN===============CP" or "CL_RSSM_STATMAN===============CM008"
"SET_STATUS"
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.
The exception must either be prevented, caught within proedure
"SET_STATUS" "(METHOD)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
Termination occurred in the ABAP program "CL_RSSM_STATMAN===============CP" -
in "SET_STATUS".
The main program was "RSPROCESS ".
In the source code you have the termination point in line 83
of the (Include) program "CL_RSSM_STATMAN===============CM008".
The program "CL_RSSM_STATMAN===============CP" was started as a background job.
Job Name....... "BI_PROCESS_ODSACTIVAT"
Job Initiator.. "ALEREMOTE"
Job Number..... 05302800
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SET_STATUS" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_RSSM_STATMAN===============CP "; its source
code begins in line
1 of the (Include program "CL_RSSM_STATMAN===============CM008 ".
Source Code Extract
Line
SourceCde
53
if i_with_internal_check is initial.
54
l_s_status = i_s_status.
55
call function 'RSSM_GET_TIME'
56
importing
57
e_timestamps = l_s_status-ts_last_changed.
58
if l_s_status-ts_proc_started <= '10000101000000'.
59
l_s_status-ts_proc_started = l_s_status-ts_last_changed.
60
endif.
61
if l_s_status_exist is initial.
62
insert rsstatmanstatus from l_s_status.
63
if sy-subrc <> 0.
64
message x000.
65
endif.
66
else.
67
modify rsstatmanstatus from l_s_status.
68
if sy-subrc <> 0.
69
message x000.
70
endif.
71
endif.
72
delete from rsstatmanpart where
73
rnr      = l_s_status-rnr and
74
dta      = l_s_status-dta and
75
dta_type = l_s_status-dta_type.
76
select single * from rsstatmanpsa into l_s_psa where
77
rnr      = l_s_status-rnr and
78
psa      = l_s_status-dta.
79
if sy-subrc = 0.
80
delete from rsmdatastate_psa where
81
psa = l_s_status-dta and
82
type = l_s_status-dta_type.
>>>>>
delete from rsstatmanpsa where
84
partnr >= l_s_status-rnr_sid and
85
psa     = l_s_status-dta.
86
else.
87
select single * from rsmdatastate_psa into l_ds_psa where
88
psa = l_s_status-dta and
89
type = l_s_status-dta_type.
90
if sy-subrc = 0 and l_ds_psa-sid_checked > l_s_status-rnr_sid.
91
delete from rsmdatastate_psa where
92
psa = l_s_status-dta and
93
type = l_s_status-dta_type.
94
delete from rsstatmanpsa where
95
partnr >= l_s_status-rnr_sid and
96
psa     = l_s_status-dta.
97
endif.
98
endif.
99
if i_with_commit = 'X'.
100
call function 'DB_COMMIT'.
101
endif.
102
endif.

Walter,
Thanks for the suggestion. This is the same recommendation I just received from SAP.
We are currently in the midst of regression testing for a major release, so cannot implement these corrections immediately. I'll post again after we implement the corrections and let you know if they solve our problem.
Thanks again.
Bob

DSO activation issue

hi gurus,
we have started facing problem in bw system suddenly for dso activation.
earlier it was running fine for 2 million records it used to take ard 3600 sec to complete but now its running for 10-11000 sec and getting failed.even for dso whwre its 20000 records its failing wit message "bi_bctl failed due to missing confirmation"
and it is happening very frequently.we have maintained settings as 3600 sec -max wait time in RSODSO_SETTINGS.
But nthng is wrkng and now problems seems to be more complex as even dtp loads are running for long time to load data to cube
can anyone guide us as when we check in SM50 BGD process are also free so not able to find root cause as several dumps are also cmng in ST22.what can we ask basis team to check ?any parametrs.setitng.etc
Any quick help appreciated
thanks
nilesh

Hi
Check how many parallel processes(child jobs) you have for this DSO activation step. this will happen due to non availability of background processes.
Check you have enough background processes and try to decrease the number of child jobs.
if you are running DSO activation PC, make sure you have not selected option "automatic activate the data upon loading" in DSO.
check below blog
DSO activation job log and settings explained
Regards,
Venkatesh

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.

How to CANCEL ACTIVE JOB in SM37??

Hi Experts,
Pls. let me clarify one simple doubt that, am trying to CANCEL a ACTIVE jon in SM37, bcoz its taking too much time, like 60 hrs, so am suspecting that, some thing is wrong in report prog./SELECT!!!
So, I tried, SM37>MENU>JOB-->CANCEL ACTIVE JOB,
but, its not getting canceeled or DELETED??
So, How Cal I CANCEL/DELETE a ACTIVE job in SM37??
thanq

thanq,
its worked out.
but, i dont know that Wht happened to my browser/SDN/system, I am unable to see the Rewarding points option!!!!!!!!!!
So, as soon as i see this option, will post the reward points.

To cancel an Active job

IF a job is active, can we able to cancel the job before it is completed? I tried Cancel job which is in job menu,It is not showing any error or displaying information, but the job is still in Active status. Please help me how to cancel an active job?

Hello,
See note 666290. Use report RSBTCDEL to force deletion.
Arthur Silva

DSO activation in Process Chains - takes long time

Dear All,
We have included DSO activation in Process Chains. This process takes a long time to execute. We manually cancel the corresponding process in Process Overview and repeat it from chain. The chain runs daily and this issue also occurs on a daily basis.
Does anyone one of you have an idea of how to deal with this performance issue?
Regards.

Figure out in which class does your process fall in:
Class A- High Priority
Class B- Medium Priority
Class C- Least Priority
Background processes
Class A jobs
The number of work processes reserved for job class A is a subset of the number of background processes.
You should only reserve work processes for job class A if it makes sense within your system organization. Work processes reserved for class A jobs are no longer available for job classes B or C.
Set parallel processing for a specific BW process in the (variant) maintenance of the process
Call the function for setting the parallel processes.
You can call the function in the process variant maintenance of a process chain or in the process maintenance. The function call varies for the different BW processes.
For example, in the data transfer process you call the function with Goto--> Background Manager Settings.
The Settings for Parallel Processing dialog box appears
Under Number of Processes, define the maximum number of work processes that should be used to process the BW process.
If you enter 1, the BW process is processed serially.
If you enter a number greater than 1, the BW process is processed in parallel
In the Parallel Processing group frame, make the relevant settings for parallel processing in the background:
Enter a job class for defining the job priority.
The job priority defines how the jobs are distributed among the available background work processes
In the group frame Parallel Processing, you can define whether parallel processing should take place in dialog work processes or in background work processes for the processes ODSACTIVAT, ODSSID and ODSREQUDEL for the DataStore object
Transport:
The entries in tables RSBATCHPARALLEL and RSBATCHSERVER are written on a transport request of the Change and Transport System.
Edited by: ram.pch on Oct 7, 2011 9:55 PM

Error during activation of DSO - Activation of M records from DataStore obj

Hi All,
Below is the error i am getting while activating the DSO, Even though similar post on this topic, solution not mentioned, any solution greatly appreciable.
When -
During Activation of DSO
State of DSO -
Request become "RED", It is available for reporting, some records in Active table, some in new table and some in new table.
Job Log -
Error when inserting the data record for data package
Process 000105 returned with errors
Error when inserting the data record for data package
Process 000106 returned with errors
Process 000107 returned with errors
Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
Log for activation request ODSR_4GXKRYHMY97R9U62M6U52XXXY data package 000001...000001
Errors occured when carrying out activation
Analyze errors and activate again, if necessary
Activation of M records from DataStore object Z_DSPO terminated
Report RSODSACT1 ended with errors
Job cancelled after system exception ERROR_MESSAGE
Detail log -
Error when inserting the data record for data package 106
Message no. RSODSO_PROCESSING002
Diagnosis
Failed to store data records persistently. Possible causes are:
You tried to save a record that is already stored in the database.
This error only occurs with DataStore objects with option "Unique Data Records".
A unique index was created for the table of active data.
You can check this in the Data Warehousing Workbench by choosing "Display" for the DataStore object and opening the "Indexes" folder.
There is a technical problem on the database.
Thanks,

HI PT,
I am also getting the same error like i have loaded the data into DSO and tried to activate the init request but it has become red and checked in log found that there are some SID Generation errors so please give me the step by step solution.
SID Generation
Data Package 000056
Data Package 000064.
Thanks in advance,
Jay

DSO Activation failed

HI,
Process step dso activation is failed due to Runtime error...I Checked in JOB Log it says ABAP/4 Processor : MESSAGE_TYPE_X and job is cancelled. So i went to ST@@ Tcode and released the dump. and again repeated the failed step.then it again failed due to same.Please tell me how to fix this issue.
Regards,
Swathi

Hi,
Please check the following threads, an SAP note has to be applied:
Loaded for 4 times same dump in BI system
DSO Activation Dump
Thanks,
Arminder

Process Chain - Follow on dependencies to DSO Activation

Hi, I have a Data Load Process where the start routine is dependent on DSO data that was just previously activated. For some reason it looks like the the time before the load and the time after the DSO activation are close by just seconds.
The Data Load Routine will drop records if the activated DSO data is not available and this seems like what I am witnessing. I thought there was a way to configure the chain or job to wait until the previous is completely done. or did that go away with 7.0...
Is there a way to make sure the loading process doesn't start until the previous DSO activation is completed and the data is available?
Thanks!

Hi,
Interuppt concept :
If a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
The interrupt process schedules an additional background job that starts based on the relevant condition. Therefore the interrupt process is not really active during the interrupt phase; it does not use any resources during this time.
If the interrupt processes are filled before the start process condition, the chain starts as soon as the start condition is filled; the interrupt process no longer interupts the chain because its condition has already been filled. If the interrupt process condition is is filled again before the start condition of the chain is filled, this does not influence the chain. It is not stopped by the interrupt process..
so basically your interrupt will wait for an event like ex:..YABAP_YGTRFCEVENTRAISE_0035 ... so you can raise that event eother by some job or some program..bUt for you i think adding the waiting timw will be better option ..
hope i cleared you ..
Regards,
Shikha

Infoset based Query creating locks on DSO Activations

Hello Experts,
We are current on SAP NetWeaver 7.3 on ORACLE data base version 11.2.0.3.0.
We have a query thats built on top of an infoset ( Based on left outer join on 0material and 0mat_plant) when user executes the query its causing locks on DSO activations.
DSO activations are on hold due to locks on following table RSRNEWSIDS. when BASIS investigated this issue they came up with following reason
executing this infoset based query is causing the locks and if we kill this job the DSO Activations run fine.
The design is as follows
Infoset(0material --Lefter outer Join -- 0mat_plant) ---> MP ---> BEx Query.
Question 1) Is it possible for a query to create locks and cause holds on DSO Activations? if so what would be the reason?
Question 2) Any solution or any of you faced similar issue?
any solution is highly appreciated and rewarded.
Regards,
Vamsi.

Question 1) Is it possible for a query to create locks and cause holds on DSO Activations? if so what would be the reason?
It all comes down to SID if a query needs an association between fact and dimensions it will use SID and if you doing an activation it readjusts the SIDS so needs to be locked for the most up to date data.
Question 2) Any solution or any of you faced similar issue?
Do your query execution before or after DSO activation.
Cheers!
Suyash

DSO activation - long runtime

Hello guys,
in our BW system, activation of a DSO request takes a long time (> 1 hr), although only a small number of records (some hundred) has been loaded. When examining the log in sm37, I found out that there are no entries for the time in question (mind the time gap between 08:21:18 and 09:25:55):
08:21:13 Job started
08:21:13 Step 001 started (program RSPROCESS, variant &0000001044887, user ID BWBATCH)
08:21:18 Activation is running: Data target CUSDSO06, from 132,353 to 132,353
09:25:55 Overlapping check with archived data areas for InfoProvider CUSDSO06
09:25:55 Check not necessary, as no data has been archived for CUSDSO06
09:25:55 Data to be activated successfully checked against archiving objects
09:25:57 Status transition 2 / 2 to 7 / 7 completed successfully
... (further lines concerning SID generation etc. omitted)
The actual activation is executed within several seconds. So I wondered what happens in the time between 08:21 and 09:25. I tried to find out more on that by tracing (transaction st05) the process. The trace shows that for each request that has ever been loaded into the DSO, some tables are read (see below). Since there are more than 4000 requests and reading for each request takes around 1 second, the runtime sums up to more than one hour.
Yet, only ONE request has to be activated (all other of these requests have been activated during the months before, so they should be quite irrelevant to the actual activation job).
226
RSBKREQUE
FETCH
1
0
7
RSSTATMAN
REOPEN
0
SELECT WHERE "RNR" = 'DTPR_4669H4NELXUK91DGMUIWCY6FY' AND "DTA_SOURCE" = '/BIC/B0000302' AND "DTA_SOURCE_TYPE" = 'TFSTRU' AND "DTA_DEST" = 'CUSDSO06' AND "DTA_DEST_TYPE" = 'ODSO'
263
RSSTATMAN
FETCH
0
1403
6
RSSTATMAN
REOPEN
0
SELECT WHERE "RNR" = 'DTPR_4669H4NELXUK91DGMUIWCY6FY' AND "DTA_SOURCE" = 'SALES_CUSTOMERS_DS            FILE_HU' AND "DTA_SOURCE_TYPE" = 'DTASRC' AND "DTA_DEST" = 'CUSDSO06' AND "DTA_DEST_TYPE" = 'ODSO'
232
RSSTATMAN
FETCH
1
1403
5
RSSTATMAN
REOPEN
0
SELECT WHERE "RNR" = 'DTPR_4669H4NELXUK91DGMUIWCY6FY' AND "DTA_SOURCE" = 'SALES_CUSTOMERS_DS            FILE_HU' AND "DTA_SOURCE_TYPE" = 'DTASRC' AND "DTA_DEST" = 'CUSDSO06' AND "DTA_DEST_TYPE" = 'ODSO'
227
RSSTATMAN
FETCH
1
1403
6
RSSELDONE
REOPEN
0
SELECT WHERE "RNR" = 'REQU_4669GG41VH6YPLG04AL85I5GE' AND ROWNUM <= 1
902
RSSELDONE
FETCH
1
0
6
/ /RREQUID
REOPEN
0
SELECT WHERE "SID" = 119751
220
/ /RREQUID
FETCH
1
0
5
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
230
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751 AND ROWNUM <= 1
684
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
201
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
194
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
195
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
195
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
309
RSBKREQUE
FETCH
1
0
6
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
264
RSBKREQUE
FETCH
1
1403
7
RSBMNODES
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751' AND "NODE" = 0
410
RSBMNODES
FETCH
1
0
5
RSBMNODES
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751' AND "NODE" = 0
242
RSBMNODES
FETCH
1
0
6
RSBMLOG
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751'
247
RSBMLOG
FETCH
1
0
12
RSBMNODES
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751'
761
RSBMNODES
FETCH
30
1403
6
RSBMONMESS
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751' ORDER BY "NODE" , "POSIT"
645
RSBMONMESS
FETCH
17
1403
6
RSBMLOGPAR
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751'
431
RSBMLOGPAR
FETCH
7
1403
5
RSBKDATAP
REOPEN
0
SELECT WHERE "REQUID" = 119751
353
RSBKDATAP
FETCH
2
1403
6
RSBKDATAP
REOPEN
0
SELECT WHERE "REQUID" = 119751
246
RSBKDATAP
FETCH
0
1403
6
RSBKDATA_V
REOPEN
0
SELECT WHERE "REQUID30" = 'DTPR_4668XBCECQQT3RHYI54CCMUQM'
314.804
RSBKDATA_V
FETCH
0
1403
13
RSBMNODES
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751'
1.114
RSBMNODES
FETCH
30
1403
6
RSBMONMESS
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751' ORDER BY "NODE" , "POSIT"
639
RSBMONMESS
FETCH
17
1403
7
RSBMLOGPAR
REOPEN
0
SELECT WHERE "LOGID" = 'DTPR_119751'
374
RSBMLOGPAR
FETCH
7
1403
6
RSBKDATAP
REOPEN
0
SELECT WHERE "REQUID" = 119751
329
RSBKDATAP
FETCH
2
1403
6
RSBKDATAP
REOPEN
0
SELECT WHERE "REQUID" = 119751
242
RSBKDATAP
FETCH
0
1403
6
RSBKDATA_V
REOPEN
0
SELECT WHERE "REQUID30" = 'DTPR_4668XBCECQQT3RHYI54CCMUQM'
312.963
RSBKDATA_V
FETCH
0
1403
8
RSBKREQUE
REOPEN
0
SELECT WHERE "REQUID" = 119751
589
RSBKREQUE
FETCH
1
0
6
RSBKSELECT
REOPEN
0
SELECT WHERE "REQUID" = '                       119751'
287
RSBKSELECT
FETCH
0
1403
|        6|RSBKREQUE |REOPEN |     |     0|SELECT WHERE "REQUID" = 119751
Any ideas?
Many thanks,
Regards,
Günter

check the profile parameter settings in RZ10. You can try number range buffering for better performnce

BI Dev client inactive & DSO activation problem

Hi SAP Experts,
Am facing some problems in DSO activation. Firstly the Business content DSO was not activating .So I had to activate the Datasources on the R/3. There were no errors in the job log but the DSO was still inactive. On trying to manually activate it , its stated that the BI Dev client was inactive. So I went to the Source Sytems tab, activated the BI client but it failed showing the following error messages:
1.EDI:Partner profile not available-> A partner profile could not be found with the following key:/IBDCLNT010/LS/
This involves the key fields of the table EDPP1: PARNUM.PARTYP
2.Entry in outbound table not found-> A partner profile could not be found with the following key:/IBDCLNT010/LS/RSRQST///
This involves the key fields of the table EDP13:RCVPRN,RCVPRN,RCVPFC
3.Entry in inbound table not found........LS/RSINFO :
4.Similar to error 3 :...../LS/RSSEND
5.Destination IBDCLNT010 has incorrect Unicode settings,adjust it to destination:
The unicode settings do not match the source systems.Conversion errors might occur during data transfer.Adjust the destination accordingly.
Has anybody seen this error log before. If so please do let me know your valuable suggestions.
Thanks for taking the time to read this technical concern
Edited by: Prathibha Pillai on Jul 29, 2008 7:58 AM

Hi,
As of 1-4 error messages.
You must define in partner profiles (ts WE20) the message type RSRQST as outbound on BI side and inbound on R/3 side, the message types RSINFO, RSSEND as inbound on BI side and outbound on R/3 side.
Regards,
Alexander

DSO Activation Job cancelled.

Similar Messages

Maybe you are looking for