Export datasource extraction failure

Hi,
I'm loading from cube to another using std export datasource. When querying the cube and using manage /content, the data is there, but when loading the 2nd cube, it says no data found. The selection criteria on the infopackage is only on calmonth. (This same criteria is used in query and manage/contents succesfully).
RSRV shows no errors with the data.
Can export datasources get corrupt?

Hi Sue
Maybe the value of calmonth you provided in seletion is not correct. You can check this in RSA3 on BW side.Enter datasource name as 8<cubename> and check it out.
Also try this- replicate the export datasource in RSA1-> Infosources.In tcode SE38 execute program RS_TRANSTRU_ACTIVATE_ALL with infosource name as 8<cubename> and source system as your BW sytem. Then try loading the data again.
Regards
Pradip

Similar Messages

Are Export DataSources always 3.x format? Can they be migrated to 7.0 DTP?

Hi,
I am extracting for a BW Export DataSource into a cube. It seems that when you generate an Export DataSource, the DataSource in 3.x format.
I first created the ETL using the 3.x scenario.
i.e Export DataSource->Transfer Rules->InfoSource->Update Rules->Cube
I then wanted to move the DTP for improved efficiency and so created a new 7.0 InfoSource and built the 7.0 scenario
i.e Export DataSource->Transformation->7.0 InfoSource->Transformation->Cube and all works well.
I'm now trying to remove the 3.x scenario, but it causing problems because the Export DataSource remains 3.x.
If I try to delete the 3.x DataSource, it wants to remove dependent objects (which are both 3.x & 7.0 scenarios).
If try and migrate the 3.x DataSource to 7.0 (Rightclick: Migrate), it gives me an Error Message no. RSDS163 - Export DataSource 8AUEQUIPMTM(CBW230ALE) in myself system: Object type RSDS not possible
I can't find anything on OSS, but I suspect Export DataSources are not supported in the 7.0 format as yet.
As such, I am required to leave 3.x scenario intact to process the 7.0 scenario.
This isn't a great problem, but it is a little messy and confusing for the person administering the loads.
Can anyone tell me if it possible to make an Export DataSource into 7.0 DataSource?
Many thanks
Adrian

Hi,
when needed, you can indeed convert datasources from v3.5 to V7, and back, using transaction RSDS. Choose "with export". This "saves" the "other" version, and so it can be "restored" afterwards via RSDS again.
This is also true after DS replication from a sourcesystem, when the system asks whether you want the new replicated DS to be 3.X or V7. Either you choose, you can convert afterwards if needed.
Regards
hugo vandenabeele
senior BW consultant

Generation of export datasource - datasource does not appear

Hello Guys,
I hope you can help me. I searched half the day in the SAP system and also google but couldn't get any help for my issue.
Situation:
I have already generated, activated export datasources and loaded with them from a BW in USA to EUROPE some transactional Data and master data. No problem (sales data, materials, 0ustomer).
But!: When i try to generate a export datasource for 0SOLD_TO and 0Ship_To infoobjects i receive the usual message "Datasource succesfully generated", but i never receive the expected 80Sold_TOT/80Sold_TOM resp. 80ship_TOT/80Ship_TOM datasources entry in the datasources tree! They simply dont get created at all.
Of course i did the replication (first in the source BW and also in the Target BW) but they both never appear.
Interestingly i have only an entry for 0SOLD_TOH (for the Hierarchies). But as explained not for the texts or the attributes.
My thought was that it might has to do with the fact that 0Sold_to and 0Ship_to are referenced characterisicts to 0customers?! but this would be strange in my eyes because in that way i would not be able to extract the attributes which are only connected to Sold-to and Ship-to!
I hope my question is clear for you and someone can help me!
Thanks a lot!
Regards
Andreas

Ok, I did the test now and it confirms our theory: No, export datasource are generated for IO's which are based on referenc. chars.!
This brings me really to the question: What should i do now to extract the Z-Attributes which belong to the objects 0Sold_to and 0Ship_to? I am not allowed to change the reference char which is 0Customer.
I need the export data sources because we extract the data from a USA BW on 7.x to a EUROPEAN BW 7.x
For me there is no other way known than this to transfer master data and transactional data from the DSOs and Cubes. Right?

Zero elimination into the export datasource

Hi gurus!
I have the following problem:
1) In the Infocube 1 I have a export datasource and this provider receives data from a FLAT FILE;
2) In this FLAT FILE I have 19 records. One of them has all key figures as zero value;
3) When I load this FLAT FILE into the Infocube 1 receives all records (total of 19);
4) I have the Infocube 2 that receives data from Infocube 1 (via export datasource);
5) When I load data from Infocube 1 to Infocube 2, I miss the record with all KF as zero value. I receive only 18 records.
Does anybody know what is happening?
Note: This behavios is like the zero-elimination on compress data.
Thanks in advance,
Silvio Messias

Hi,
check if your record exist in your Source ICube.
If yes (and you don't filter your extraction) then the extractor is not considering the records having all key figs = 0.
If not then then check whether you have routines having RETURNCODE <> 0 in TRules or URules...
strange...
Olivier.

I want to Authorize on export datasources

Hi all,
I have a security issue on our BW system. Our BW system is also a source system to several global BW systems. We have restricted this access by using transaction SBIW - Limit Authorizations in the past. The downside of this approach is that you have to maintain this transaction for all datasources. Most systems that extract data from our system only need two or three dataflows.
We have upgraded to BI 7.0 and would like to use a normal authorization profile to get the same thing done. For transaction data, we can use autorization objects S_RS_ODSO and S_RS_ICUBE to restrict on export datasource. I am however unable to find a authorization object that gives the same autorhization for infoobjects.
I have two questions:
1 does anyone know an authorization object for 'export datasource' authorization on infoobjects?
2 Does anyone know an authorization object on export datasources in general? Ideally I would need one authorization object, to authorize on export datasources that can be used by a Remote user on our system.
Any help would be appreciated.
Regards,
Jaap

Try Here > http://support.apple.com/kb/TS1583
And See this Discussion...
https://discussions.apple.com/thread/4204776?start=0&tstart=0

Export datasource

thanq u for giving reply,
i couldnt get any sap application component in infosource. i am using flatfile extraction , i think that this could be the reason why i am not getting sap application component
Message was edited by: shanthi bhaskar
Message was edited by: shanthi bhaskar

Hi Bhaskar and welcome to the SDN,
not quite sure about your problem, but I guess you need to replicate the datasources of source system myself after generating export datasources. Additionally you need to switch on 'display generated objects'. You can do that in rsa1->infosources by selecting Settings->display generated objects from the top menu. Don't forget to refresh the display after doing that.
regards
Siggi

Export DataSource - Which Table

Hi
Using a Export DataSource on a InfoCube with both compressed and uncompressed data. Which tabel does it use? Is it able to find data in both F and E tables?
Thanks
Chris

Hi Chris,
usually the FM 'RSDRI_INFOPROV_READ' is used to read data from a provider...normally, every linked tables is read to extract all the necessary data...however I suggest you to do a 'little tour' in the OSS Notes 'cause in this situation some problems can occur (e.g. refer to 783831 'No data when reading using RSDRI_INFOPROV_READ' or 566762 'BW 30B: DataMarts for stock cubes').
Hope it helps (and, if yes, don't forget to assign some points...)
Bye,
Roberto

Export datasource on a cube

I have a export datasource for a custom cube. It is returning with zero records whenever we do extraction. I have regenerated it but it has not helped.
It gives no records even in RSA3. Although data is present in Cube.
Thanks in advance for your help.

Hi,
When you extract data from the cube, the view of the fact table is important because if you have compressed the data in the source, then data needs to come from the F and the E table, hence the view is needed. If this is corrupt for some reason, the extraction does not happen. Running this program will recreate the fact table views for all the cubes. Should not take too long...
Hope this helps...

Creating export datasource

Hi UmaMaheswar Plz
Let me know about the creating export datasource, infosource,infocube,update rules and info package. The APO version is 4.1
Thanx a lot for ur help

http://help.sap.com/saphelp_scm40/helpdata/EN/8f/9d6937089c2556e10000009b38f889/frameset.htm
Extracting Data from a Planning Area
Use
There are two purposes for which you might follow this procedure:
·        Ad hoc reporting on a planning area
·        To save planning data persistently to the database
Procedure
       1.      Generate an export DataSource for the planning area.
                            a.      From the SAP Easy Access menu, choose Demand Planning ® Environment ® Current Settings ®Administration of Demand Planning and Supply Network Planning.
                            b.      Select the planning area and in the context menu choose Change/Display.
                            c.      In Planning Book maintenance, choose Extras ® Generate Data Source
                            d.      A dialog box appears in which you enter a name for the data source. Choose Execute. A screen appears with details of the data source.
                            e.      Specify which fields you wish to be selectable later for reporting purposes. This step enables you to limit a query to specific objects or ranges of objects. What you select here does not affect which fields are included in the export structure. Select the Suppress field indicator for the fields (InfoObjects) that you do not want to transfer
The number of fields you transfer directly affects performance. Therefore you should only transfer those fields that you require for reporting purposes in the InfoCube.
The field for the planning version is selected per default; you cannot deselect it. This means that you must enter a planning version in the infoPackage later.
                              f.      Make a note of the DataSource name.
                            g.      Choose Save.
       2.      Replicate the data source. To do so, right mouse click the source system and choose Replicate DataSources in the Administrator Workbench. The source system is in this case the system in which you are doing Demand Planning. For example, if you are planning in system APO client 002, the technical name of the source system is APOCLNT002.
When the system messages at the bottom of your screen cease, a background job is triggered. Check in the job overview that this job has finished before proceeding to the next step.
       3.      Still in the source systems view of the Administrator Workbench in the context menu for the source system choose DataSource Overview.
       4.      Assign an InfoSource to the DataSource:
                            a.      In the DataSource overview under Data Marts, select the DataSource and choose Assign InfoSource from the context menu.
                            b.      In the dialog box click the Create icon.
                            c.      In the next dialog box, enter a name and a short description for the InfoSource.
                            d.      When the InfoSource has been created, choose Enter.
                            e.      Answer the prompt with Yes.
This saves the InfoSource/DataSource assignment.
If the above procedure is unsuccessful, use the following alternative:
·         Switch to the InfoSource view.
·         Create an InfoSource (right mouse click a suitable InfoArea and choose Create InfoSource).
·         Select the InfoSource and choose Assign DataSource from the context menu.
A dialog box appears with an overview of all DataSources in the Data Mart, including the export data sources you have generated yourself.
·         Select the DataSource you created in step 1.
       5.      In the Administrator Workbench switch to the InfoSource view.
       6.      Right mouse click the InfoSource you have just created and choose Change.
The definition screen for the assignment of the communication structure to the transfer structure appears. You see the communication structure in the upper half of the screen and the transfer structure in the lower half. Some of the assignment information is proposed by the system. You must fill in the missing information.
This is another opportunity to remove superfluous InfoObjects from the communication structure. See also step 1.
       7.      Define the assignment of the communication structure to the transfer structure.
                            a.      In the lower half of the screen, enter the source system and the DataSource for the transfer structure.
                            b.      On the Transfer structure tab page, copy the objects from the DataSource to the transfer structure (from right to left).
                            c.      Click on the Transfer rule tab page.
                            d.      Check where the assignment of transfer structure fields to communication structure InfoObjects is not proposed by the system.
                            e.      Where the assignment has not been proposed:
                                                  i.       Include new InfoObjects in the communication structure in the upper half of the screen.
                                                ii.       In the lower half of the screen, select the new InfoObjects in the communication structure on the left and copy them to the appropriate fields in the transfer structure on the right.
                              f.      Choose Activate.
       8.      If you need an InfoCube to carry out reporting with a BW front end, create an SAP Remote InfoCube, specifying as the InfoSource the one you created in step 4.
Otherwise, see the note below.
       9.      Activate the SAP Remote InfoCube.
Result
In the SAP Business Explorer Browser, you can now build queries based on this Remote InfoCube. See also Reporting on Data in a Planning Area.
If you want to copy planning area data to an InfoCube for backup purposes or to save old planning data, create a basic InfoCube at step 8 (for example, by running program /SAPAPO/TS_PAREA_TO_ICUBE) and proceed as you would to upload data from R/3 or a flat file.

Corrputed loaded text from an Export Datasource with Unicode

Hi Experts
I am new with BW and this forum helped me a lot in the past year.
I am loading texts to an InfoObject using a Master Data (texts) Export DataSource from another InfoObject. The system is NetWeaver 2004s (BW 3.5) with Unicode.
The InfoObject's Text MD is Language Dependent but users enter the system only with EN language.
For some reason the loaded texts are corrupted.
For example: The original InfoObject has Hebrew texts (that were loaded perfectly from the source system which is also Unicode), but the text in the PSA table and in the text table of the target InfoObject will be: ###########
Can anyone help?

Hi Niraj
Thanks for your answers
Let me explain:
Currently, we load texts with Hebrew chars from the SAP ECC6 system and everything is good (we see Hebrew chars in SAPGUI/BEx/WAD etc.)
The problem occurs when we load these texts from one InfoObject to another, via Export DataSource.
To do that, We generated an Export DataSource for the original InfoObject and assigned it to the target InfoSource of the other InfoObject. After running an InfoPackage for this DataSource, the texts that were loaded to the PSA (and hence, to the target InfoObject texts table) were corrupted - which means that they appeared: ##########
Thanks,
Yaniv

Error while generating export datasource in Test and Prod system

Hi experts,
I tried to generate export datasorce on a cube in teh testing system so that i can use this as a datasource for another cube. I did this so that i can transport all teh relevnt objects from D to T. But Iam gettin teh following erro msg
System setting does not allow changes to be made to object ISTD 80CRM_PRI.
while Prod system produces teh follwoing error msg
Changes to Repository or cross-client Customizing are not permitted
Choose 'Display object' or 'Cancel'.
After i have done this and when i go to the context menu of teh infocube i can see maintain export datasource option.
Also I couldn't see the infosource generated in Infosources ( FYI I have already done display generated objects under settings)
Can anyone tell me how to proceed further.
Thanks,
DV

Hi DV,
Generally export datasource are not included in the request from the test server. It gets generated automatically when (ODS,Cube) based on which the datasource s transported to production / quality .
I think solution should be try not to include export datasource, infosource ,transfer rules to request from dev server.
Hope that helps.
Regards
Mr Kapadia

Generate Export Datasource

Hi All,
While activating an ODS object, I got the error The creation of the export datasource failed. I tried activating the entire source system and replicated it. But still I am facing this issue. I checked the ODS in RSRV also. There it gave me the error Number of rows for active program and temporary program are different". I am facing this issue for newly created ODS objects also.
Can someone throw some light on this?
Thanks in advance,
Febina

Hi Febina Mohanan
Welcome to the board..
There are few considerations with your issue
1)Occured Because of Space issue Just check the space statistics in DB02 with the help of BASIS
2) Connectivity..
3) Just try in rsa1 Settings--->display Generated Objects >selct show generated objects->Continue..
4) Activate u r ds with the programe "RS_TRANSTRU_ACTIVATE_ALL"
Hope this will help...
Regards
R M K
Assining points is the only way of saying thanx in SDN ***

Error while generate export datasource.

Hi Experts,
APO - 3.0A(BW-2.0A)
In APO while creating generate export datasource for a cube, I am getting the following error.
Creation of InfoSource 8XXX for target system BW 1.2 failed - Message no. RSBM 026
Diagnosis - Failed to create InfoSource &v1& for target system BW 1.2.
System Response -
The InfoCube cannot be used as a data mart for a BW 1.2 target system.
Any help is highly appreciated.
Thanks&Regards,
VJ

Thanks Rebort,
Just now I completed it after searching for OSS note. Anyhow thanks for you help too.
Now I am facing a different problem. The generated DM infosource is not available under InfoSource - DM.
I have changed the ODS setting from Hide to Show
also InfoSources - RC - insert lost nodes..
no luck.. any suggestion
Regards,
VJ
Message was edited by: Vijay Kumar

The Creation of Export DataSource Failed Error while transporting ODS Cube

Hi All,
I am facing this issue from last 1 week.. i had developed an ODS cube in APO-DP BW which will fetch data from SAP R/3 and its working fine in APO Dev Server. But when i transport this cube into APO PAC(Prodn Server) the below error i am getting..
   Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Activation Mode)
   The creation of the export DataSource failed
   Password logon no longer possible - too many failed attempts
   Password logon no longer possible - too many failed attempts
   Error when creating the export DataSource and dependent Objects
   Error when activating DataStore Object ZANAUTSL
I also updated the transport conversion tables but still problem not resolved.
Immediate help is hightly appreciated.
Thanx
AJ

Hi AJ,
Looking at your error, it seems that the RFC user's password is locked and hence connectivity from R/3 towards APO BW is broken.
You know the name of your export datasource (from R/3 to APO BW). Find out the name of your R/3 source system e.g. PACCLT000, by scrolling to the right against teh export data source.
Take help of your Basis or EAI team to identify the RFC destination corresponding to the connectivity from the R/3 source system (PACCLT000) to your APO BW system. (If needed ask for help from your BW team, I am not very sure how connectivity would be set up from R/3 to APO BW, I guess this would be independent from CIF connectivity)
For this RFC connection from R/3 to APO BW, see which RFC user is maintained in SM59 in APO and ask your security team to reset (or unlock) the password of this RFC user in R/3, and then if required update the user password details in SM59 in APO also.
After this, your issue should get resolved.
Thanks - Pawan

Generate Export DataSource from InfoCube In Production System

Software component : BI release 7.0 SP 18
Dear Gurus,
we have a strange situation in our production system from a month till now.
We want to generate an export data source from an infocube to load data into another one but now when we try to generate in prod ( right click on infocube and select "Generate Export DataSource" ) we can't create anymore.
Following message appears :
no changes to repository and cross client customizing object allowed
and the generation is stopped.
We always did it in production system in the same way as in the other system and then transported the update rule or transformation, but now it seems that is no more possible.
No setting has been changhed in SCC4 and in object changeability. Maybe is an authorization problem or is due to any other setting?
Does anybody has a way to solve this problem?
<removed by moderator>!
Kind Regards
Stefano
Edited by: Siegfried Szameitat on Nov 24, 2008 4:18 PM

Hi Stefano,
If you want to generate an export datasource you ask your basis team to open the system so that you can do.
As per the Sap Best Practise you can do the export datasoorce in your development system and move it to the quality and after testing you transport to Production.
Generallly if you can look in to production authorizations you may have only some operation like to display only.SOme times basis may give authorizations like creation of DTP and Infopacks like that.
Regards

Export datasource extraction failure

Similar Messages

Maybe you are looking for