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

Similar Messages

  • 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

  • Generate Export Datasource in Production

    Hi All,
    We have transported our cubes to PRoduction system. When I try to generate export data source I get an error
    Changes to Repository or cross-client Customizing are not permitted.
    I have set the system change options in SE06 and SE03 as modifable for Customer Name space and SAP name space.
    I dont want to open the client for this purpose. because this may be a repitive process and we need to open the production client every time.
    Can anybody give their thoughts on this.
    Thanks in Advance,
    Best Regards,
    PV

    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

  • Creation of export datasource failed

    Hi All.
    i copied a bussiness content data source object (DSO) and tried to activate it. it is giving error that
    "The creation of the export DataSource failed"
    Why ??? where m i going wrong.
    Thanks & Regards,
    Mo

    Hello,
         This is the problem becos the system is unable to create DATAMART for DSO object.  The following reasons might be hindering the creation of DSO.  Please check whether
    1)  You have proper authorization to create Datasource/Datamarts.
    2)  If so then, check whether DATAMART for the BW Self Source System is properly Installed from Business Content.  (I hope you are working on the version 3.5 or later.. here we need to manually install Aplication Component related to Datamart from Business Content so that Datamart creation never fails after that)
    3)  Also check BW Self Source System is properly functioning.
    Thanks
    Kishore Kusupati
    Edited by: Kishore Kumar K on Jul 28, 2008 5:35 AM

  • 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

  • Can you include navigational attribute in export datasource

    Can you include a navigational attribute in an export datasource?  If so, how.
    Thanks.
    Sandy

    hi sandy,
    i don't think so. navigational attributes are not available. you need to understand that in case of an ODS object the export data source is generated out of the change log table, so if any field missing in the change log table it will not be part of the export data source.
    In case of cubes the characteristics and key figures reflects in the export data source.
    but why do you need navigational attributes in export data source ? it conflicts the nature of nav attributes as you will be storing the history statically with reference to the data when it was loaded. if you really want the same nav attributes in your subsequent data targets then include the characteristic which has the desired nav attributes in your target cube and map it from the export data source of the source info-provider. Switch on the nav attributes in the target info-providers.
    hope it helps
    thanks
    soumya

  • Function module names to delete the Export Datasource

    Hi Experts,
    Can anyone please let me know what function modules are while deleting the export datasource. So far in my research i have found only
    RSB1_DELETE_EXPORT_DATASOURCE. -- This fm does not deletes the export datasource, I want to know which fm is used exactly to delete the datasources.
    To delete the virtual infocubes, the fm used is RSDG_CUBE_DELETE. Similarly there must be a fm to delete the export datasource.
    Please help.
    Thanks,
    Prashant.

    Hi Reddy,
             I hope there is no specific function module to delete the entries ( as of version 4.0). So you need to code a delete statement to perform the task.
    Thanks,
    Siva.

  • Generating Export DataSource

    Greetings Y'all!
    Can anyone tell me what the purpose for generating Export DataSources are for and what the specific sequence of steps are to generate Export DataSources?
    Thank you!
    Philips Manalaysay

    Hi
    If you want to upload a cube from another cube or from ODS the source ODS of cube should have generated export datasource. This enables the CUbe or ODS to act as source for someother Cube to feed the data
    To Generate export data source Right click on the cube and in the menu Generate export datasource.
    Regards
    N Ganesh

  • The creation of export datasource failed.

    Hi everyone! This is Chong Tao from Central Michigan University and I got one problem recently when I was doing my set-up of the BW course. I actually wanna copy the infocube but when I click the "Generate export datasource", it automatically comes up one error message "The creation of export Datasource failed". What should I do to overcome this problem? Thanks for paying attention to this problem and I need your valuable advice as soon as possible since it is for the student in this SAP BW course.

    Hi,
    I guess your objective is to copy an existing infocube. Right ?
    In that case, Right Click Infocube and use 'copy'. This will create another Infocube with the same structure, but with no data. You can then fill this copy Infocube by cerating transformation between the two infocubes and scheduling through DTP.
    'Generate export datasource'  can normally be done when there are two separate BW systems and you want an Infocube to be a source of data to another Infocube in a different BW system( though it can be used in the same BW system as well).
    Best Regards

  • What is GENERATE EXPORT DATASOURCE

    Hello gurus,
    When we right click on Master data infosource we have a option like <u>GENERATE EXPORT DATASOURCE</u>, so what is the significance of that and what actually happens when we press that.
    I ll surely award points.
    Thanks

    Dear Khanna,
    When u click on export data source option, system generates a infosource.
    Actually this is required when u want to send data from one infoprovider to another infoprovider in same system or in external BIW system.
    In practice some times need comes for sending data from one target to another target. In this situation this is required. Many times u first load data in to ODS and then u send it to cube, this is the typical case you need export data source.
    Once you click this, system created infosource from the same. useing this infosource and creating update rule u can load data in to another target.
    Hope this answers your question.
    regards,
    Mahendra Sane

  • Export DataSource Performance Issues

    Hi,
    System: BI 7 with DataStage and R3
    Problem We just finished a technical upgrade to the BI 7 system from BW 30 and what has happened is post upgrade the export datasource setting for default data transfer has been changed.
    Where can I change the settings for default data transfer (I know it can be changed in SBIW and SPRO for global settings). It is currently using dialog processes to transfer data but I want use background processes to transfer the data. I was not able to find anything about changing the type of process used for data transfer.
    Thanks,
    Rahul

    Perhaps export-clixml has a performance issue based on the size of the XML object being processed. If so, anything you can do to limit the size should help. You way you have arrays of custom PSobjects, and seem to already writing each array out to a separate
    XML file. Is there someway that you could chop it up a little finer? Say if an array has 50,000 elements, what if you would write it in 2500 element chunks to a series of xml files? You'd then have to read it back in in a way that re-establishes the original
    array.
    Or, if your PSobjects generally contain all of the properties of the corresponding AD object, you could consider that perhaps you do not need them all; or you could filter one small set of properties to one xml file and so on...
    Al Dunbar -- remember to 'mark or propose as answer' or 'vote as helpful' as appropriate.

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

  • HT1420 Where is the store menu in iTunes.  I just got a new computer.  I disconnected the old computer and want to authorize the new one.  There is no file menu or store menu anywhere I can see.

    Where is the store menu in iTunes?  I updated my computer and want to authorize it.  I deauthorized the old computer (and probably my desktop at a different location, and want to authorize the new one.  The help says that I need to clickon the store menu in iTunes.  I do not see any store menu.  I can access songs that I purchased a while back, but cannot download any new purchases.  If I cannot get this worked out, how do I recoup my money for the new songs?  Also, can I transfer the songs I purchased to another service?  Brad

    It's in the same spot on a Windows machine as well

  • 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
    <b>System setting does not allow changes to be made to object ISTD 80CRM_PRI.</b>
    while Prod system produces teh follwoing error msg
    <b>Changes to Repository or cross-client Customizing are not permitted</b>
    <b>Choose 'Display object' or 'Cancel'.</b>
    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

Maybe you are looking for