DSO Activation error in SAP BI 7.0

Hi all,
I am trying to activate a DSO which is created by me in SAP BI7.0.When I save the DSO it didn't placed any error even when I clicked Check it dispalyed as consistent.But When I clicked activate it placed an error saying the DSO cannot be actvated.
1.The creation of the export DataSource failed
Message no. RSBM035
Diagnosis
The creation of the DataSource &v1& was unsuccessful.
System Response
Whilst generating the export InfoSource, the metadata for a DataSource must be generated. An error arose when doing this.
Procedure
Consult the appropriate developer (function module: RSB1_OLTPSOURCE_GENERATE).
2. Error when opening an RFC connection
Message no. RSAR051
3.Error when creating the export DataSource and dependent Objects
Message no. RSDODSO169
4. Error when activating DataStore Object
Message no. RSO404
I have tried to check the RFC connection in SM59 but I didn't find anything.If we need to create an RFC connection then please let me know the steps.This activation of DSO is very important as it is stopping all the work.Please suggest me what Steps need to be taken now as this is very important.
Regards
D

in SM59 double click your XYZ destination,might have to correct the IP address in SM59
perform a "test connection"
if not fine then check the target host, system number and name/ip and modify them accordingly; don't forget that this is MyBW system you have to maintain actually your XYZ host details.
if the test went through, the next is to test authorizations: menu test, authorizations. Check tab logon/security settings; you should use ALE as user... you need to know this pwd if you change it!. Check if this user is not locked.
Hope it Helps
Chetan
@CP..

Similar Messages

DSO Activation Error - While Installing BI Content

HI Friend,
    First, I deleted one sap source systems for BW1 ( My bw1 server BI is : BW1CLNT100 ), later ,I create the same sap source system, But active 0FIAP_O03 ods,
had error:
DataSource 80FIAP_O03 does not exist in source system BW1CLNT100 of version A
Error when creating the export DataSource and dependent Objects
Error when activating DataStore Object 0FIAP_O03
I go to BW1CLNT100 datasoucres ,I not finded 80FIAP_O03 datasoucre, But I goto bw prd BI datasoucre, I found   80FIAP_O03 datasoucre.
I think loss 80FIAP_O03 datasoucre for BW1CLNT100 source system, because I am't delete Roules on the 0FIAP_O03 infosoucre for delete sap soucre systems.
DSO Activation Error - While Installing BI Content
this problem no issue, So I create new thread.
Now, How could me create or load 80FIAP_O03 datasoucre for BW1CLNT100 source system?
Now, I Replicate Datascoure for BW1CLNT100 source system, Delete old datasocure....... I go home, I will try tomorrow .

Hello,
You should generate the export data source for 0FIAP_O03 again, if there is still a problem please goto
RSA1 > SOURCE SYSTEMS > and right click on the relevant source system, find the datamart application component and
right click on this to replicate the datasource.
Best Regards,
Des

DDIC Activation error for SAP HR SP 23

Hello,
We have installed ECC 6.0 SR3 with DB2 as database and HP UX OS.
When I am updating HR Software component to SP23, it gives an DDIC Activation error. After checking the logs, "Table Type HRPP_T_PPDIT_HASH could not be activated" was displayed.
Did a consistency check on table PPDIT, which said it was consistent.
Kernel level is latest 185. R3 trans and Tp is also latest.
Kindly help.
Regards,
Sagar

Hi
Please check the following SAP Notes
Note 672651 - OCS: Known problems with Support Packages in Basis Rel.6.40
Note 573044 - Unicode conversion for HR application
Regards
Chen

DSO Activation Error - Error Assigning SID

Hi Experts,
While activating data in DSO i am getting the following error,
Value '01032010' of Characteristis 0DATE is not plausible
Error when assigning SID : Action VAL_SID_CONVERT
I have checked in PSA, dates in other reords are same as this date format, I am unable to identify any difference in date format between this data package and those which are processed successfuly.
If anybody faced this problem , please help.
Regards,
ASingh

HI AKSINGH,
It seems to be there is a problem with date format, it should be YYYYMMDD. To check the entries in PSA, goto SE11/SE16 then give table name = RSTSODS and display and give
PSA= <InfoSourceName>* the execute and find your PSA name and then see the technical name of PSA and then give that name in SE11/SE16 and see the all values.And note down the error records and correct it.
OR
Goto the Manage screen of the DSO --> Contents tab and click on on "New Data" button at the bottom.
This will take you to the New table. Check the number of entries.
Next enter the value "01032010" in the 0DATE field and execute.
If the record is displayed, goto debug mode (/h) and edit the record as per the format (YYYMMDD or whatever).
If the record is not displayed, then display all the records in the NEW table. Sort the data based on the 0DATE field. find out that particular record and again edit it in debug mode (/h).
Once you have edited the record, go and activate the request again. Your issue must be resolved.
Regards
KP

DSO Activation Error

Experts,
My request got successfully loaded into the DSO. Then I activated it and executed the request. Unfortunately no data showed up except for the field names. So I went back to the manage screen of the DSO and saw that the request had turned red. Why is the request turning red after activation. Why isnt it showing any data after activation. Before loading, when I previewed it, all the data was shown correctly.

Hi Pooja,
Loading a request is one part and activating the request is other in DSO. when you load the request entire data will come to new table and when it is activated the data is shifted to active table, at this point of time it will check each and every record and also some of the routines. Normally at the activation time you will get invalid characters and lower case/ upper case these type of errors.
You can check the erroneous records in PSA and also in the red datapacket's messages in Monitor screen. You can edit the error at PSA level and manually you can process the data to DSO.
Hope this will helps.
Rgs,
I.R.K

Mass Activity - Error in SAP CPS

Hi guys,
I am trying to run a mass activity from SAP CPS in the ISU system. I imported the mass activity - 0004, the posting and the document date had to be changed dynamically, so I created a parameter set as shown here.
Created a job to copy parameters(these two parameters only). Ran the job, the parameters are created and copied to target id FPMA5
Created a copy of the job SAP_MassActivityTemplateRun -> Used the Target ID as shown and date as today.
So, I am consuming the Identification FPMA5 from the previous job run here. Tried to run it, getting the below error in the SAP CPS system.
com.redwood.scheduler.connector.sap.rfc.connection.exception.SapBapiException: BAPI exception while calling /SCJS/ISU_START_MASS_ACTIVITY: E XM 300 RAISE_EXCEPTION {00,341} Runtime error & has occurred [0004,K2,26.05.2014,FPMA5]
BAPI exception while calling /SCJS/ISU_START_MASS_ACTIVITY: E XM 300 RAISE_EXCEPTION {00,341} Runtime error & has occurred [0004,K2,26.05.2014,FPMA5] [RAISE_EXCEPTION, {00,341}, Runtime error & has occurred, [0004,K2,26.05.2014,FPMA5]]
Parameters:
0004
2014-05-26
FPMA5
X
        at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:727)
        at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:533)
        at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:310)
        at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:147)
        at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:481)
        at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:303)
        at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:200)
        at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:109)
        at com.redwood.scheduler.connector.sap.rfc.command.impl.AbstractMassActivityRunCommand.startMassActivity(AbstractMassActivityRunCommand.java:264)
        at com.redwood.scheduler.connector.sap.rfc.command.impl.MassActivityTemplateRunCommand.doExecute(MassActivityTemplateRunCommand.java:50)
        at com.redwood.scheduler.connector.sap.rfc.command.impl.AbstractMassActivityCommand.execute(AbstractMassActivityCommand.java:67)
        at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:84)
        at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:57)
        at com.redwood.scheduler.connector.sap.rfc.service.operation.RunJobOperation.doWork(RunJobOperation.java:136)
        at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)
        at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)
        at java.lang.Thread.run(Thread.java:722)
I now added other parameters into the parameter set, maintained them in the COPY_Parameter job. Even then I get the same error!
I believe my problem is this - I am able to copy the parameters, but passing them to the Mass activity is somehow failing(I am using the MASS_ACTIVITY_TARGET_ID field output from Copy parameters to MASS_ACTIVITY_ID, which I believe is wrong. But I want to use the copy parameter job's output in the mass activity template run). Please let me know.
I followed this guide: Importing and Running Mass Activities - SAP Central Process Scheduling by Redwood - SAP Library
Thanks and regards,
Pavan

Hi Pavan,
To create a job chain-level parameter, proceed as follows:
Go to Definitions > Job Chains and choose Edit on your job chain
In the job chain editor, click on the Parameters tab
Click Add, fill in Name, for example MASS_ACTIVITY_DATE, fill 0 into Display Order.
In default expression field, fill =Time.expressionNow('truncate day add 3 days')
Make sure Display is checked, click Save
Submit the job chain, you will notice that the date is as expected, cancel the submit.
In the job chain, go to the job for which you want to set the parameter and choose Reference, select the job chain parameter.
The above will use the date at submit time + 3 days, if you want to use the runtime date, when the job chain starts, you disable Display and enable Runtime, remove 'add 3 days'.
Hope that helps.
Regards,
HP

Write optimized dso activation error

The dictionary activation module could not activate all objects.
System Response
A statement is produced from the activation module log with warnings and error messages.
Enhancement category for include or subtype missing.....help me solve this issue....

Hi,
We had similar error during cube activation but we didn't change Enhancement catagory rather we have deleted additional indexes created on different dimension tables in SE11.
Go to se11 and check the number of indexes created, use Index button on tool bar. Delete unwanted indexes and then try to activate again.
Reards,
Durgesh.

ODS data activation error system SAP BI 7.0

Hi Gurus,
I am carrying out full load in a standard ODS.
When I try activating the request,system is giving me the error message as given below.
No SID found for value '%' of characteristic 0COND_CURR.
I have also tried the option of transfer global settings in RSA1->source systems.
Please help in this regard.

Hello Gurus,
Issue resolved
For my requirement i changed info object 0currency -> General Tab page -> Transfer routine -> Created and written a code as follows
If result = '%' .
result = 'USD'.
endif.
This resolved my ODS data activation issue.
Thanks a lot for all your help.

While activating a request in DSO getting error code 10

While activating a request in DSO getting error code 10
Hi All,
I am trying to load data into Billing: Condition Data (0SD_O06) using 2LIS_13_VDKON. First while loading data I am getting error
Record 8778 :InfoObject SOLD_TO does not contain alpa-conforming value 100000 which I changed manually in PSA maintenence and tried to load data again and now I am getting an error (Error 10 in the update) ID:RSAR No119.
I have checked the formula in Transformation and it works fine. Still I am not able to load data.
Please help.
Thanks and regards
Vishal Pardeshi

Check the log for the request from the manage screen of the DSO, it will be there next to the monitor button.
Otherwise you can check the error from the monitor screen of the request in Details tab.
Veerendra.

Errors found by DSO activation

Hi gurus,
i got the following errors after checking the logs of the DSO activation. Any suggestions??
Thanks. points will be given,
SD
Value " " from characteristic ZM_RMTEXT contains an error at position 1
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 1 is one of these characters. The value is therefore not permitted.
Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
Procedure
Check the origin of the characteristic value. If possible, change the characteristic value in the source.
Incorrect source text in update routines and transfer routines can also cause this problem.
============================================================================
Value 'B2 1234567 Kabelsatz' (hex. '4232203132333435363720204B6162656C7361747A') of characteristic ZM_MATTAU contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 4232203132333435363720204B6162656C7361747A).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.

Hi,
You have invalid characters for the field ZM_MATTAU. Due to these your DSO activation is failing.
The way to resolve this is to write a cleansing routine for that field to strip away the bad characters and only permit the good characters to go through.
If you search the forum you'll get sample codes for the same.
Cheers,
Kedar

DSO Activation

I have a standard DSO. In the settings, the only thing checked is "Set Quality Status to 'OK' Automatically", I have this loading using a process chain and in the chain, I have the Activate process included.
The DSO loads with no problem, but the Activate step fails with error message "No active PSA table".
Two things that seem weird:
1. Without doing anything, I go to the DSO > Manage and the DSO has been activated (so why does the process Activate in the process chain fail?)
2. If I Repeat the Activate step in the process chain, even though the process is active based on # 1 above, the Activate step turns green and completes the process chain.
I am having this problem for several DSOs in several different chains.
Thanks for any help. Keith J

PC- Display variant for DSO activation - click on Parallel processing - click DS Activ option -
   Background with "A"
   Num of Par proessing = 6
again Click on this time DS-SID GEN
Background with "C"
   Num of Par proessing = 3
Make sure you have the same settings for DSO activation which are failing?
Also refer Note: 1301094 - SP21:Error during activation of DSO in a Process Chain
Symptom
When you execute a DTP for loading a Datastore Object error happens in the activation of Datastore. This typically happens in a process chain. The error messages are as follows:
o RSDRO 103: "PSA update failed"
o RSAODS 003: "Error occurred while deciding partition number"
Solution
SAP NetWeaver BI 7.00
           Import Support Package 21 for SAP NetWeaver BI 7. 00(SAPKW70021) into your BI system. The Support Package will be available when note 1270629 with the short text "SAPBINews NW BI 7.0 ABAP SP21", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.01 (SAP NW BI7.0 EnhP 1)
           Import Support Package 04 for SAP NetWeaver BI 7. 01 (SAPKW70104) into your BI system. The Support Package will be available when note 1227876 with the short text "SAPBINews NW7.01 BI ABAP SP04", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.10
           Import Support Package 08 for SAP NetWeaver BI 7. 10 BI (SAPKW71008) into your BI system. The Support Package will be available when note 1260071 with the short text "SAPBINews NW 7.10 BI SP08", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.11
           Import Support Package 02 for SAP NetWeaver BI 7. 11 (SAPKW71102) into your BI system. The Support Package will be available when note 1260072 with the short text "SAPBINews NW7.11 BI SP02", describing this Support Package in more detail, is released for customers.
In cases the correction instructions can be used.
Beforehand please definitely check the note 875986 for transaction SNOTE.
This note may already be available before the Support Package is released. However, the short text will still contain the words "preliminary version" in this case.
Edited by: Srinivas on Jul 29, 2010 4:30 PM

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

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 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

Getting Shor Dump while DSO Activation

Hi Experts,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest me.
Category               Internal Kernel Error
Runtime Errors         SYSTEM_CORE_DUMPED
Date and Time          25.02.2014 18:38:47
Short Text
     Process terminated by signal 10.
What happened?
     Error in the SAP kernel
     The current ABAP program "CL_RSODSO_DATASTORE=====
      terminated because the ABAP
     processor detected a system error.
Thanks
Sunil

Hi,
Take basis team help. error itself saying as related to internal kernel error.
recently any changes were applied on server? if yes then those might be causing.
please refer note - 517824.
Inform to basis team and sort it out.
Thanks

DSO Activation error in SAP BI 7.0

Similar Messages

Maybe you are looking for