Problem in Datatransfer to ODS

Hi friends,
I have a problem when i upload data from infosource to ODS object.It doent load some data.
Ex: I have Sales overview infocube.I planned to take Ods and load data to ods.When i load data from infosource 2LIS_13_VDITM,it doesnt load 0Deb_cred and 0doc_Class.But same infosource loads to Infocube,it loads 0deb_cred and 0doc_class also.
Waiting for you reply.
Rgds,
Suren

hi surendhar,
After scheduling the load check in the monitor what exactly u r getting
R u getting any error?
is the staus showing green?
r u able to see the no. of records transferred.
also u mentioned that for some of the fiels data is not populating.
check whether data is available for that particular fields from R/3 side or from flat file.
have u written any update rules for that info objects?
is that data is available for that info objects in psa?
Also while creating update rules of ods have u mentioned the correct data soruce..
let me know
Dont forget to reward points that is the way of saying thanks in sdn
cheers
ravi

Similar Messages

Problem in activation of ODS 0SD_O06 due to Archiving request.

Hi Experts,
I am having a problem in activating ODS 0SD_O06, it is giving below error message
1. 550 of 1.476.126 data records are in a locked area
2. 550 data records locked by archiving request 1.048.978
3. Error when checking data to be activated against archiving objects.
We have archived the ODS content based on Billing Date, Archiving Request 1.048.978 is for the Bill Date 01.01.2004 to 31.12.2004.
I checked in the new data table of ODS with the Bill Date 01.01.2004 to 31.12.2004, I got 550 Records.
It means the records which is already archived for Bill Date 01.01.2004 to 31.12.2004, got changed and again came into the request.
I am not able to find the solution for this, please help me in this, your help will be highly appreciated.
Thanks and Regards,
Ajay Kumar
9350006555

hi,
If the data has been archieved then there is no tool to get the archieve data back in BW. So I suggest to investigate further.
Thanks

Process Chain problem related to Update ODS Object Data (Further Update)

In the process chain, the data is loaded to an ODS first then feed to an InfoCube by kind of data mart load. But when checking the process chain, getting yellow warning msg:
A type "Update ODS Object Data (Further Update)" process has to follow process "Activate ODS Object Data" var.our_infopackage_name in the chain
Message no. RSMPC016
If we add the variant "Update ODS Object Data (Further Update) after the activation of the ODS and before the InfoPackage to feed data to the cube, then another yellow warning shows up for the InfoPackage of loading data to the InfoCube that says the Update variant can not be before the loading to this Cube and etc.
What should we do to have the problem resolved?
Thanks

hey Dinesh,
How to have a wait time for the load to the cube?
I've given you "Very helpful" rewarding points and after you give the answer to the above, I will give you the "Solve problem" rewarding points.
Thanks

Problem in activation of ODS

I am unable to activate the ODS and showing the error as SID is not properly assigned. Do I need change the request of ODS to red.

Hi,
You cannot reactivate the ODS data unless you edit the data inside the PSA. The data in the PSA is not compatible... may be some special character has arrived in PSA which loads to ODS but, it will create problem during ODS activation. You need to delete the request in ODS... go to PSA and find out the error record and edit it and again load it from PSA. Error record can be traced in errorlog of ODS activation.
Thanks
Kishore Kusupati

Update Problem in CUBE from ODS.

Hi Experts,
     I have problem in Updating data from ODS to CUBE and ODS to INFO-OBJECT.
In brief, ODS has the Up-to date data ( Means till today - 28/07/10 ) . But the cube has Data till 22/07/2010. If I am trying to activate the ODS , Its is showing NO REQUEST TO ACTIVATE. And the DATAMART status is also not available . But the thing is , I checked in ODS till 22/07/2010 also DATAMART status is not available. And Its a Delta .
Please help me out, How can I update the data In CUBE and to an Info object.
Thanks,
Sethi.

Hi ,
I got the point , I am showing how the request are there in date wise.
In ODS   :
                                                           CRM Sales Contract Item:Delta     29.07.2010
                                                           CRM Sales Contract Item:Delta                     28.07.2010
                                                           CRM Sales Contract Item:Delta      27.07.2010
                                                           CRM Sales Contract Item:Delta     26.07.2010
                                                           CRM Sales Contract Item:Delta     25.07.2010
                                                           CRM Sales Contract Item:Delta     21.07.2010
                                                           CRM Sales Contract Item:Delta     20.07.2010
                                                           CRM Sales Contract Item:Delta     19.07.2010
It's Showins , there is missing REQ after 21.07.2010 .
In INFO-CUBE
                                                            Delta Package for Update                         22.07.2010
                                                            Delta Package for Update                             21.07.2010
                                                            Delta Package for Update                             20.07.2010
                                                            Delta Package for Update               19.07.2010
                                                            Delta Package for Update                             18.07.2010
It's showing , there is no data in INFO CUBE after 22.07.2010 and    in ODS the same Date Request is Missing. So my DELTA go Inactivated. After Updating the REQ on 22.07.2010 to CUBE , Unfortunately DELETED without maiking that RED.    My mistake was that.
Please guide me ... What should I do ? Should I delete the Data in both CUBE and ODS. And Reload .
Thanks,
Sethi.
Edited by: ukumar on Jul 29, 2010 4:19 PM

Problem when loading from ODS to the CUBE

Hi Experts,
I am facing an unusual problem when loading data from ODS to the cube.
I have a first level ODS where the delta postings are updated. I have checked the active table of the ODS and the data is accurate.
I have deleted the entire data from the Cube and trying to do a full load from ODS to the CUBE.
I am sure when I run a full load the data goes from Active table of the ODS.
After the full load the the keyfigure values are 0. I have tried doing the testing by loading couple of sales documents and still the keyfigure values are 0.
I wonder when I load the full. The data should be picked exactly the way it is in active table of the ODS.
I also dont have any fancy routines in the update rules.
Please help me in this regard.
Regards
Raghu

Hi,
Check the procedure did u do that exactly or not. just follow the the laymen steps here:... and let me know ur issue
o     First prepare a flat file in Microsoft excel sheet for master data and transaction data and save it in .CSV format and close it.
o     First select info objects option and create info area then create info object catalog then char, & key figure. Then create id in Char, Name as attribute activate it then in key figures create no and activate it.
o     In info sources create application component then create info source with direct update for master data and flexible update for transaction data. The flat files would be created for master data create info package and execute it.
o     For transaction data go to info provider then select the file right click on it then select option create ODS object. Then a new screen opens give the name of the ODS and create other screen opens then drag character to key fields.
o     Activate it then update rules it will give error to it then go to communication structure and give 0Record mode then activate it then go to update rules it will activate it.
o     Then go to info source then create info package then external data then processing update, Data targets then the scheduling then click start then the monitor.
o     Then other screen opens there we can see if we doesnt able to see the records then come back to the info provider right click on it then other screen opens then select the option activate data in ODS then a screen opens.
o     so select the option QM where it would be in a yellow co lour then by double click then another screen opens then select green color option then click continue it and it comes to the previous screen then select the option and click save it would be underneath of it just click it up and close it.
o     Then come back to the main screen to the info source to the info package go to the package and right click on it then a screen opens then click schedule without distributing any of the tab directly click the monitor tab. Then refresh it until the records come to the green.
o     Once it is green the click the data target and see the file executed.
o     Now go to the info provider then a right click on the file name then create info cube. Then a new screen opens and gives the name and activates it. The drag the key figures to the other side, time characteristics to the other side, and chacetristics to the other side.
o     Then create the dimension table then assign it and activate it .Then go to file name right click on it then select the option create update rules select ODS option and give the file name and activate it .
o     Then come back to the main screen and refresh it. Whenever you see 8 file names you will know that it is undergoing the data mart concept.
o     In the main screen click ODS file right click then a pop up screen opens select the option update ODS data target. Then another screen opens in that we are able to see 2 options full update, initial update then select initial update.
o     Then another screen opens info Package there the external data , data targets , scheduler select the option later in background option then a another screen opens just click immediate then click save automatically it closes then click start option.
o     Then select monitor option then the contents then the field to be elected then the file to be executed.
regards
ashwin

Probleme beim Datenladen von ODS in einen Infocube

Problem:
BW 3.5
Ein ODS wurde mit Daten befüllt und soll nun als Delta in einen Infocube geschrieben werden. Jedesmal wenn ich jetzt versuche einen Init-Request zu starten gibt es einen Kurzdump in der RSA1 mit folgender Meldung:
Fehleranalyse
     Kurztext der Fehlermeldung:
Datenanforderung an dem OLTP ***
     Langtext der Fehlermeldung:
     Technische Informationen zur Nachricht:
     Nachrichtenklasse... "RSM"
     Nummer.............. 000
     Variable 1.......... " "
     Variable 2.......... " "
     Variable 3.......... " "
     Variable 4.......... " "
Auslösestelle des Laufzeitfehlers
     Programm                                SAPLRSSM
     Include                                 LRSSMU36
     Zeile                                   420
     Modultyp                                (FUNCTION)
     Modulname                               RSSM_OLTPSOURCE_SELECTIONS
Gibt es dazu irgendwelche Erfahrungen, was kann man da tun?
MFG
Michael Ruschmann

hi,
check oss note 852443-Dump in LRSSMU36/RSSM_OLTPSOURCE_SELECTIONS include.
hope this helps.
852443-Beratung:Dump in Include LRSSMU36/RSSM_OLTPSOURCE_SELECTIONS
Symptom
Wenn ein MESSAGE_TYPE_X Laufzeitfehler im Include-Programm LRSSMU36 im ABAP-Programm SAPLRSSM im Funktionsbaustein RSSM_OLTPSOURCE_SELECTIONS auftritt, gehen Sie vor, wie unten in der Lösung beschrieben.
Dieser Dump tritt auf, wenn Sie ein InfoPackage zu einer DataSource/ Quellsystem-Kombination öffnen wollen, bei dem eine Initialisierung fehlerhaft abbrach und danach ohne Bereinigung der Delta-Verwaltung ein neuer Init mit überlappenden Selektionen ausgeführt wurde.
Der Dump kann auch auftreten, wenn Sie eine Systemkopie/Backup in nur eines der 2 Systeme BW/OLTP einspielen, ohne vorher alle Delta-Queues zu dieser BW/OLTP-Kombination zu löschen, da dann die Deltaverwaltung immer inkonsistent ist. In einem solchen Fall wenden Sie sich bitte an die Beratungsabteilung der SAP.
Weitere Begriffe
Dump, Include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X
Init, Delta-Queue, Systemkopie, Backup, Initialisierung, InfoPackage
Ursache und Voraussetzungen
Programmfehler
Lösung
Dieser Lösungansatz kann nur bei Ladeläufen aus einem OLTP System angewandt werden und NICHT für Datamartfortschreibungen, da die Deltaverwaltung nicht über die Transaktion RSA7 erfolgt.
1. Zu der DataSource/Quellsystemkombination finden Sie die Einträge zur Initialisierung im BW-System in der Tabelle RSSDLINIT. Vergleichen Sie diese mit den Einträgen im OLTP-System in der Tabelle ROOSPRMSC.
2. Wenn im BW KEINE Einträge in der RSSDLINIT vorhanden sind, dann löschen Sie im Quellsystem (OLTP) in der RSA7 die Delta-Queue zu dieser Datasource/BW-Kombination.
3. Wenn im BW in der Tabelle RSSDLINIT schon Einträge vorhanden sind, dann untersuchen Sie die dort aufgeführten Requests, die in der Spalte RNR stehen, im Monitor (Transaktion RSRQ). Alle diese Requests müssen alte, rote Init-Requests sein, die Sie durch neue Inits ersetzen wollen. Wenn dies der Fall ist, löschen Sie wieder im Quellsystem (OLTP) in der Transaktion RSA7 die Delta-Queue zu dieser Datasource/BW-Kombination.
Danach können Sie das InfoPackage wieder öffnen.
Prüfen Sie dort, dass im Menü
'Scheduler'/'Initialisierungsoptionen für Quellsystem'
keine Einträge mehr vorhanden sind.
Wenn doch welche vorhanden sind, löschen Sie diese.
Danach können Sie eine neue Initialisierung starten.
Wenn Sie meinen, trotz fehlerhaftem ersten Inits einen 2.ten Init mit überlappenden Selektionen erzeugen zu können, so dass danach dieser Dump auftritt, geben Sie der Entwicklung eine detailierte Beschreibung Ihres Vorgehens in einer Kundenmeldung. Dieses Verhalten konnte von Seiten der SAP noch nie nachvollzogen werden und bedürfte deshalb eines ausgiebigen Tests und der Möglichkeit zum Debuggen in Ihrem System.
Symptom
If a MESSAGE_TYPE_X runtime error occurs in the LRSSMU36 include program in the SAPLRSSM ABAP program of the RSSM_OLTPSOURCE_SELECTIONS function module, proceed as described in the solution below.
This dump occurs if you try to open an InfoPackage for a DataSource/source system combination for which an initialization terminated incorrectly and a new INIT with overlapping selections was executed without the delta-administration being cleaned up.
The dump can also occur if you import a system copy/backup into only one of the 2 BW/OLTP systems without first deleting all delta queues for this BW/OLTP combination because the delta administration is always inconsistent. In such cases, contact the SAP consulting department.
Other terms
Dump, include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X, INIT , delta queue, system copy, backup, initialization, InfoPackage
Reason and Prerequisites
This is caused by a program error.
Solution
You can implement this correction only for load times from an OLTP system and NOT for data mart updates because the delta administration does not occur via Transaction RSA7.
1. The entries for the initialization in the BW system are contained in the RSSDLINIT table for the DataSource/source system combination. Compare these with the entries in the ROOSPRMSC table in the OLTP system.
2. If there are NO entries in the RSSDLINIT table in BW, delete the delta queue for this DataSource/BW application combination in the source system (OLTP) using transaction RSA7.
3. If the RSSDLINIT table in BW already contains entries, check the requests listed there in the RNR column in the monitor (transaction RSRQ). All of these requests must be old init requests that appear in red and that you want to replace with new inits. If this is the case, delete the delta queue for this DataSource/BW application combination again in the source system (OLTP) using transaction RSA7.
You can then open the InfoPackage again.
Check there that there are no more entries in the
'Scheduler'/'Initialization options for source system' menu.
If you do find some entries, delete them.
You can then start a new initialization.
If, despite the first incorrect init, you want to be able to create a second init with overlapping selections, which means that this dump will then occur, enter a detailed description of your procedure in a customer message and send it to Development. SAP has never been able to reproduce this behavior, therefore, you will need to carry out a great amount of testing and have the option to debug in your system.

Problem in activating the ODS

Hi experts,
while activating the data in the ODS , I am getting the following errors.
"System error ocurred(RFC Call)"
Activation of data records from ODS object XXX terminated
"Task 0031 for parallel SID assigment terminated with errors"
"Task 0021 for parallel SID assigment terminated with errors"
"Task 0009 for parallel SID assigment terminated with errors"
"System error ocurred(RFC Call)"
Task 004 2for parallel SID assignment terminated with errors.
When I saw the dump I found the following message
How to correct the error
"MESSAGE_TYPE_X" C
"SAPLRSATREE " or "LRSATREEF28 "
"RSATREE_START_ACTIVATION"
I
                                                                                Information on where termination occurred
The termination occurred in the ABAP program "SAPLRSATREE " in
"RSATREE_START_ACTIVATION".
The main program was "SAPMSSY1 ".
The termination occurred in line 536 of the source code of the (Include)
program "LRSATREEF28 "
of the source code of program "LRSATREEF28 " (when calling the editor 5360).

Hi Kris,
Do u have any red requests in ur ODS Manage. This error is caused when u have red requests and still u r trying to activate the data in the ODS.
Or Probably u have check the check box for bex reporting in setings of ods, Uncheck it and ur error will go.
Try these and let us know
Regards
Majeed

Problem with update from ODS to Cube

Hi All,
I had an issue, when i was loading from ODS to Cube everything was fine except one data package failed coz of some object locked( User : myself, though i wasn't running anything else except this), but i check in SM12 no locks exist for that particular time.
apparently the load failed coz of this single package, its a load from ODS to Cube, so no chance of Manual update from PSA.
any suggestion: do i have to repeat that load all over again( sucks !!! it is for 40 mil)
Regards,
Robyn.

Hi Hoggard
Check the Job log fro ur Job in the SM37 and check for that Datapackage is there any thing failed liek
"ARFCSTATE-SYSFAIL" if this is there .. it means its an Deadlock .. please check the ST22 dump...
U can use the PSA...
1) go to the 8ODS infosource and copy the Delta IP
2) check the option in the processsing as Update PSA and the subsequently into the data targets
3) Schedule the IP manually
hope it helps
regards
AK

Problem with load to ODS

Hello
I'm loading data to an ODS. The background job has status "Finished", but the QM status is yellow and not all steps are green in the Details tab in the monitor. What steps should I take now? Is the load really completed, or is the details tab showing me the correct status?
I checked the source system and there is actually no data for the IP selection. So it should just say 0 from 0. The background job finished in a few seconds, but the QM status is yellow for some time now..
Thanks you
Aline.

Hi......
What do you mean by background job............before starting of every IP a background job will be executed........after completion of this background job only your IP will start........If you right click on the IP >> Display messages.......there you can see the job........
Is your extraction job is completed..........Copy the request number from the IP header tab >> go to the source system.......in SM37 >> give the request number with BI as prefix.............if your extraction job is finished...........
Then check for TRFC in SM58 in BW side ..........if any TRFC is there then PUsh it pressing F6............if after that also.....load does'nt proceed then check for short dump in BI side in ST22...............
Otherwise check TRFC and Short dumps in source system side........
If short dump is there in BI side........then make the QM status red.........delete the request from the target.........and repeat the load..............
If short dump is in Soirce system side..............then cancel the extraction job.........delete the request from the target.........and repeat the load..............
Hope this helps.......
Regards,
Debjani.............

ODS Activation Problem (with SIDS) BIG PROBLEM !!!

Hi
Ok we have a situation in our project but first a few facts: -
1: For ODS we do not use keys but have a infobject that creates a unique ID for each entry with a bit of ABAP in the update rule (yep not very good I know but too many to change now)
2: The SID table keeps growing so we have deleted it four or five times with SE14.
Now I am not sure if these are related to our problem as we have used SE14 before and it hasnt created prolems??
THE PROBLEM
Some of th ODS that use this unique Info Object (we will call this A1) that creates unique entries will not activate with SID creation. It doesn't give much information apart from whatever process A1 is it is returned with errors.
We get the following message
Process 000034 returned with errors (process 34 is the one that tries to get a SID for A1)
Message no. RSODSO_PROCESSING006
Activation of M records from DataStore object CA_TS1 terminated
We also geta short dump every time too and that is copied below the line where it fails
Does anyone know of how i can reset the SID gerenration or anythign that may help
52           ID 'KEY' FIELD 'BI0'
53           ID 'DATA' FIELD l_field.
54
55
56   IF i_abend EQ rs_c_false.
57 *... Nachricht an den Message-Handler schicken
58
59     DATA: l_type TYPE smesg-msgty.
60
61 *... S-Meldung wenn kein Handler initialisiert
62     IF g_active IS INITIAL.
63       l_type = 'S'.
64     ELSE.
65       l_type = 'W'.
66     ENDIF.
67
68     CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
69       EXPORTING
70         i_class = 'BRAIN'
71         i_type   = l_type
72         i_number = '299'
73         i_msgv1 = i_program
74         i_msgv2 = i_text.
75   ELSE.
76     DATA: l_text TYPE string,
77           l_repid TYPE syrepid.
78
79     l_repid = i_program.
80     l_text = i_text.
81
>>     RAISE EXCEPTION TYPE cx_rsr_x_message
83           EXPORTING text = l_text
84                  program = l_repid.
85   ENDIF.
86
87 ENDFUNCTION.

Yep right click and delete data then set up new initial etc with very small selection.
Reloaded and exact same error message.
when I check the /BI0/SBBP_OBGUID table it only has one entry whilst the other infoobjects are getting filled in their SID tables so is there any way to sort of kick this table up the butt and reset it or something??
Your right about the P table so we can cross that out of the picture )
I do think it is somethign to do with the fact that we have used SE14 too many times and it hascaused in consistencies but if you have any ideas how to resync it or somethign it would be great
thanks

Problem with porcess chain and request

Hi experts, I need help!!
Description of the problem:
There are three ODS that load daily information through process chain to a Infocubo. The information is loaded to BW from View generated for a data base of Oracle.
Process chain for the three ODS is equal, I explain the one procedure to them:
1- It initiates the chain .
2- Blocks the View.
3- Load of data through of infoPackage.
4- If the load finishes well, then the data is delete of the View, the data is activte in the ODS and it arises to InfoCube, and if it finishes bad so unblocks the View and finishes process chain.
5- Then, reconstruct the Index.
Happens that in the three ODS when we loaded the information erase request loaded previously, then the historical one of the loads in the ODS does not stay. The three infopakages used to load the information to the ODS does not have labeled the option to erase the destiny of data, and it does not have it marked. The ODS do not have marked that option.
When I do it manually east problem does not happen. I erased process chain and I returned to create the chain porcess but it did not solve the problem.
Thank you

I just checked the documentation and found that your code is incorrect. IAlternativeName::StrValue contains value for an email address, a Domain Name System (DNS) name, a URL, a registered object identifier (OID), or a user principal name (UPN). It doesn't
contain string value for directory name (and other non-mentioned types). Instead, you need to instantiate an IX500DistinguishedName interface and initialize it from an alternative name value:
class Program {
static void Main(string[] args) {
String RequestString = "Base64-encoded request");
CX509CertificateRequestPkcs10 request = new CX509CertificateRequestPkcs10();
request.InitializeDecode(RequestString, EncodingType.XCN_CRYPT_STRING_BASE64_ANY);
Console.WriteLine("Subject: {0}", request.Subject.Name);
foreach (IX509Extension ext in request.X509Extensions) {
if (ext.ObjectId.Name == CERTENROLL_OBJECTID.XCN_OID_SUBJECT_ALT_NAME2) {
CX509ExtensionAlternativeNames extensionAlternativeNames = new CX509ExtensionAlternativeNames();
string rawData = ext.RawData[EncodingType.XCN_CRYPT_STRING_BASE64];
extensionAlternativeNames.InitializeDecode(EncodingType.XCN_CRYPT_STRING_BASE64, rawData);
foreach (CAlternativeName alternativeName in extensionAlternativeNames.AlternativeNames) {
switch (alternativeName.Type) {
case AlternativeNameType.XCN_CERT_ALT_NAME_DIRECTORY_NAME:
IX500DistinguishedName DN = new CX500DistinguishedName();
DN.Decode(alternativeName.RawData[EncodingType.XCN_CRYPT_STRING_BASE64]);
Console.WriteLine("SAN: {0}", DN.Name);
break;
default:
Console.WriteLine("SAN: {0}", alternativeName.strValue);
break;
My weblog: en-us.sysadmins.lv
PowerShell PKI Module: pspki.codeplex.com
PowerShell Cmdlet Help Editor pscmdlethelpeditor.codeplex.com
Check out new: SSL Certificate Verifier
Check out new:
PowerShell FCIV tool.

Data problem from DSO to cube

hi
i am facing data from problem from dso to cube
i am getting daat into dso
plant   material doc_num itemno qty
p1      m1           1              1         10
p1      m1           1               2         20
dso i am uisng key fields
doc_no
item_no
doc_year
data fields
material
plant
qty
while loading data into cube
its showing only
p1 m1 1 2 20
item 1 is missing
there is no iten num filed in my target field?
ple let me know ur idea.

Hi,
The problem is in your ODS/DSO.
In your ODS you have 'Doc_num' as key field.
For both Items 1 & 2, you have same key field ( Doc_Num) Value.
So, the first record will be over written by the second one. So from your ODS you will get only the latest record to the Cube.
If you want to send both doc_nums to cube, you need to bring doc_num to the data fields area of ODS.
Hope this helps.
Cheers
Praveen

ODS Installation from BC Error

Hi,
We are trying to install ODS 0PY_PP_C1 from Business content. It gives me following errors .
1. "Error while Creating Export DataSource and dependent Objects"
2. "Data source 80PY_PP_C1 not maintained in BWSYSTEMNAME version A."
And we have tried with generating custom ODS as well ,but was not successful.(Same Error Messages)
We feel that somewhere there is default system setting, and system is taking source system as bw system itself instead of R/3 . So its trying to create export data source. But Generation of export datasource is not needed in our scenario.
Please let us know how do we solve above said issues.
Thank you.
Regards
Nimesh

hi,
take a look oss note 597326-Activating ODS: Error when creating the export DataSource. it should solve your problem.
note 597326
Activating ODS: Error when creating the export DataSource
Symptom
When you activate or transport ODS objects, the following errors appear in the log:
"The creation of the export DataSource failed". Message number RSBM 035
"Error &1 in function module &2". Message number RSBM 006
"Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
"Error when activating the ODS object &1". Message number RSDODSO 168
Other terms
RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
Reason and Prerequisites
A characteristic involved is active but it is using new or inactive attributes.
Characteristics involved are all characteristics used in the ODS object.
Solution
Check all characteristics involved as described in the following:
Check the Compounding and Attributes tabs in the characteristics maintenance.
All characteristics here must be active. This is displayed by a green icon.
If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again.

Error while activating the ODS

Dear Experts,
Please help me out,
I am facing one problem while activating the ODS of 0FIGL. Data is uploaded successfully into the ODS but while activeting the ODS, it gives the following error message :
Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0DOC_HD_TXT
Value 'SWITCH 24 PORT MANAGED -I' (hex. '00530057004900540043004800200032003400200050004F00') of characteristic 0DOC_HD_TXT
SID determination finished for InfoObject 0DOC_HD_TXT
I have also read out all the related post & also applied them in this but still the position is same.
also in RSKC, all the characters are allowed.
please suggest.
Thanks in advance
Neha
Process 000090 returned with errors

Hi,
Pliz go thru below article for restricting Invalid chars.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0afbb81-f219-2c10-4181-b20f6b10e373?quicklink=index&overridelayout=true
It might give u an idea or solve your issue.
Thanks,
Jitender.

Problem in Datatransfer to ODS

Similar Messages

Maybe you are looking for