How to migrate hierarchy datasources?

hi friends
im in the process of migrating the datasources from 3.5 to 7.0 .
i have migrated 0profit_ctr_attr and 0profit_ctr_text and i need to migrate 0profit_ctr_0106_hier.. i right clicked on it and i didnt find  migrate  option....
can any one plz give me a sol for migrating the hierarchy datasources..
Thanx in adv
ravi

As of now you cannot migrate hierarchy datasources. You still have to stick to the older way of loading hierachies. TR/Infopackage..
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/682cacb88f297ee10000000a422035/content.htm

Similar Messages

  • How to create hierarchy datasource in BI7.0

    I want to create hierarchy datasource in BI7.0(Patch level:15), and my source systems is Oracle DB. Who can tell me how to do?
    Thanks.
    Edited by: Ricken Fan on Mar 5, 2008 9:44 AM

    Hi,
    SAP is not Supporting to create Hierarchy Data Sources in BI7.0
    You have to create Hierarchy Data Sources in 3.x only.
    Reg
    Pra

  • How to migrate the datasource from Bea 8.1 to Bea 10

    Hi,
    I have to migrate an application from bea 8.1 to 10.
    the configuration in 8.1 is as follow : (config.xml)
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="10" KeepXAConnTillTxComplete="true"
    MaxCapacity="150" Name="adiosPool" Password="adios47"
    Properties="user=adios47"
    RemoveInfectedConnectionsEnabled="false"
    ShrinkFrequencySeconds="600" StatementCacheSize="100"
    SupportsLocalTransaction="false" Targets="server"
    TestConnectionsOnCreate="false" TestConnectionsOnReserve="true"
    TestFrequencySeconds="60" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0"/>
    <JDBCTxDataSource JNDIName="weblogic.jdbc.jts.adiosPool"
    Name="adiosPool" PoolName="adiosPool" Targets="server"/>
    and that is my new configuration : (config.xml)
    <jdbc-system-resource>
    <name>adiosPool</name>
    <descriptor-file-name>jdbc/adiosPool-0758-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    jdbc/adiosPool-0758-jdbc.xml :
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
    <name>adiosPool</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0</url>
    <driver-name>oracle.jdbc.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>adios47</value>
    </property>
    <property>
    <name>portNumber</name>
    <value>1521</value>
    </property>
    <property>
    <name>SID</name>
    <value>HVAEE0</value>
    </property>
    <property>
    <name>serverName</name>
    <value>AXHE0.application.hvb.de</value>
    </property>
    </properties>
    <password-encrypted>{3DES}PMWtUXqoHT8=</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>weblogic.jdbc.jts.adiosPool</jndi-name>
    <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    but when I start the server I get the following exception :
    START SERVER
    javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jdbc.jts.adiosPool' didn't find subcontext 'jdbc'. Resolved 'weblogic'; remaining name
    'jdbc/jts/adiosPool'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:246)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:213)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    what's wrong ?
    Thanks for your ideas

    Hi,
    This is realated to Upgrading your domain.You can upgrade your domain from bea weblogic8.1SP4 to Bea weblogic 10.You need to use the upgrade tool from bea weblogic platform10.You can start the Upgrade wizard tool from Windows Start->All Programs->BEA Products->Tools->DomianUpgradeWizard.The tool will take you to upgrade the domain automatically.Once you have upgraded the domian everything(database connection pools,users,groups,any other resources) in 8.1 domian will be changed to 10.
    Bea Support Complete upgradation of Application as well as application data from 8.1 to 9.2 or 10.0
    Thanks
    Bishnu
    Regards
    Bishnu

  • How to Migrate 3X datasource to 7X datasource

    Hi,
    Can any one please update on steps involved in Migration of 3X Data source to 7X data source
    Thanks

    Hi,
    Please have a look into below article, it provides the steps for migration of dataflow including datasoure.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00d94ca8-9538-2c10-9b99-859afde1fa4a?quicklink=index&overridelayout=true
    Thank-You.
    Regards,
    Vinod

  • How to create a hierarchy datasource in R/3

    Hello,
    We use the 0MATERIAL_LKLS_HIER hierarchy datasource to load material hierachy in BW.
    I had to modify the function module that creates the data for 0MATERIAL_LKLS_HIER.
    Now, i need to create a new datasource based on the new function module.
    To do so, i created a generic datasource (with SBIW), a master data attributes datasource.
    I tried to put the same parameters that in 0MATERIAL_LKLS_HIER, but i didn't find how to indicate that it's a hierarchy and some other parameters (as you can see in RSA2 for 0MATERIAL_LKLS_HIER in the "semantic attributes" area).
    Also, i couldn't run the new datasource in RSA3 because it didn't show me the right selection fields.
    Could you tell me if there is a specific transaction to create hierarchy datasources ?
    Thank you.
    MGH

    Hi,
    May help you:----
    Re: hierchy creation in ECC and replicate to BI
    http://help.sap.com/saphelp_nw04/helpdata/en/8e/dbe92341c84242be2c7d3917f1c197/content.htm
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7034028c-ad1d-2a10-2c94-868e7707dfe2
    Regards,
    Suman
    Edited by: Suman Chakravarthy on Aug 6, 2011 3:12 PM
    Edited by: Jason Lax on Dec 28, 2011 2:28 PM (Updated URL to correct format)

  • How to create a hierarchy datasource in BW

    Gurus-
    Here is my requirement.
    I am asked to create a DSO and equivalent datasource for profit center. How to create a datasource for profit center in BW?

    what does ur DSO has to do with the hierarchy? And subject line and the subject are misleading.
    these are some of the std PCA datasources:
    0PROFIT_CTR_0106_HIER       
    0PROFIT_CTR_ATTR                 
    0PROFIT_CTR_TEXT
    0EC_PCA_1                         Profit Center: Transaction Data on Accounts
    0EC_PCA_2                         Profit Center: Statistical key figures
    0EC_PCA_3                         Profit Center: Actual Line Items
    0EC_PCA_4                         Profit Center: Actual Line Items Periodic Transfer

  • Cant Migrate 3.x Hierarchy Datasource

    as the title says we can migrate all our datasources from 3.x to bi7 but we do not get the option with the hierarchy datasources, is there any reason for this and if so what are the steps to overcome this.
    Thanks

    Hi,
    There is no new method to create Hierarchy in BI7.0 So, we have to follow the same steps as in BW 3.5.
    So,There is no need to migrate.
    Thanks & Regards,
    Dinakar.

  • Migration of datasource

    Hi All,
    I am working on BI7 and SRM standard content. I observe that the hierarchy DataSource  are in 3.x version and the classic flow is not coming up after activation.
    I have tried to migrate this DataSource  to 7.x with the export option but am getting the below error.
    " DataSource  0BBP_BIGURE_HIER(SRDCLNT200): Data type H not supported by object type RSDS "
    If some one has had this problem below Please help in the resolution.
    Kind Regards
    Niren

    Hi,
    We are currently working on BI content 7.0. After transfering we got the 3.5 flow for most of it. Now we are looking for a migration of 3.x flow to 7.x flow. It would be really helpfull If any of you could  answer my following queries:
    1. How do we migrate queries/workbooks?
    2. How much of effort it would be to migrate transformations having routines in it as part of  stsandard content . And is it just a copy paste of the ABAP routines or do we need to change it to an Object oriented ABAP?
    3. We are having around 100 info providers and 300 master objects. Will it be ok if we come up with a stratergy of migrating the info providers alone and still having 3.x flow for the master info objects.
    Thanks and Regards
    Niren.

  • Creation of Hierarchial datasource in 7.0

    Hello,
    I want to create an extractor ( 7.0 ), for loading hierarchy into an infoobject. I came to know that its not possible to create  Hierarchial datasource
    in 7.0 flow ( possible only in 3.X).
    still is it possible to create one through RSA2 transaction?
    In RSA2, if i create a new datasource, there is a field DataSource Type--> and the F4 help gives an option of HIER ( Hierarchy nodes )
    is it the right way to create one??
    Thanks
    Karthik

    Hi,
    Thanks for your reply.
    The BW10 transaction does not seem to exist.
    And i followed the steps mentioned in the link. In step 3, after entering the source system, i am getting a pop-up where i am asked to select
    a datasource.
    Here there are only two datasources present for selection
    one is attribute datasource , other one is datasource for loading text. ( which were already there).
    Here i am supposed to get another datasource name ( Hirearchial datasource ). I know that i have to create one before following the steps mentioned in the link.
    ( So that i get my hirearchail datasource name for selection in that pop up )
    my question was how do i go about creating this datasource. In RSO2 transaction , i can create datasources for loading text, attributes and transactional data.
    There is no option for creating Hirearchail datasource.

  • Flat File Hierarchy Datasources

    We are creating several flat file hierarchy datasources. The datasources will be maintained in an external database.
    I am familiar with the creation of flat file datasources for master and transactional data, but don't have good documentation for how the external flat file hierarchy is to be formatted.
    We have reviewed the 2004 Netweaver Document "How to Download Hierarchies in BW" and have used the program referenced there, Z_SAP_HIERARCHY_DOWNLOAD, to download our hierarchies to then test the upload.
    However, this has not worked.
    Does anyone have the record layout that the flat file must be in to upload a simple 2-level hierarchy (for example groupings of 0vendor)?
    Thanks, Doug

    I think the URL you mention is http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm.
    This contains the record layout instructions as follows.
      5.      Maintaining the hierarchy:
    Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
    PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields.  This option allows you to load characteristic values having a length greater than 32 characters.
    Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
    The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
    The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
    Description
    Field Name
    Length
    Type
    Node ID
    NODEID
    8
    NUMC
    InfoObject name
    INFOOBJECT
    30
    CHAR
    Node name
    NODENAME
    32
    CHAR
    Catalog ID
    LINK
    1
    CHAR
    Parent node
    PARENTID
    8
    NUMC
    First subnode
    CHILDID
    8
    NUMC
    Next adjacent node
    NEXTID
    8
    NUMC
    Language key
    LANGU
    1
    CHAR
    Description - short
    TXTSH
    20
    CHAR
    Description - medium
    TXTMD
    40
    CHAR
    Description- long
    TXTLG
    60
    CHAR

  • How to create  a datasource for 0COSTCENTER to load data in csv file  in BI

    how to create  a datasource for 0COSTCENTER to load data in csv file  in BI 7.0 system
    can you emil me the picture of the step about how to  loaded individual values of the hierarchy using CSV file
    thank you very much
    my emil is <Removed>
    allen

    Step 1: Load Required Master Data for 0CostCenter in to BI system
    Step 2: Enable Characteristics to support Hierarchy for this 0Cost Center and specify the External Characteristic(In the Lowest Node or Last Node) while creation of this Characteristic InfoObject
    Step 3: On Last Node of Hierarchy Structure in the InfoObject, Right Click and then Create Hierarchy MANUALLY by Inserting the Master Data Value as BI dosent Support the Hierarchy load directly you need to do it manually....
    Step 4: Mapping
    Create Text Node thats the first node (Root Node)
    Insert Characteristic Nodes
    Insert the Last Node of the Hierarchy
    Then you need to create a Open hub Destination for extracting data into the .csv file...
    Step1 : Create the Open Hub Destination give the Master Data table name and enter all the fields required....and create the transformations for this Open Hub connecting to the External file or excel file source...then give the location on to your local disk or path of the server in the first tab and request for the data...It should work alright let me know if you need anything else...
    Thanks,
    Sandhya

  • How to migrate 'responsibility' level personalizations?

    Hi all,
    We have done a set of personalizations at responsibility level in our UAT instance.
    We have no problem migrating the 'site' level personalization. We use the 'Functional Administrator' -> Import/Export utility.
    But, We find that the responsibility level personalizations are stored under a folder hierarchy as below:
    Eg:
    Responsibility: XXRecruitment Manager
    Responsibilty Key: XXRECRUIT_MAN
    Responsibility ID: 50977
    Personalization is exported in this folder:
    /oracle/apps/per/irc/vacancy/webui/customizations/responsibility/50977/RectrDetsRN
    It is stored under a folder '50977' corresponding to the responsibility id of the responsibility that we personalized.
    Our problem is, the responsibility id's and responsibility key's are different in UAT and production instances:
    Responsibility: XXRecruitment Manager 01
    Responsibilty Key: XXRECRUIT_MAN_01
    Responsibility ID: 50900
    Now, how to migrate such personaliations? Our client have personalized atleast 25 pages at various responsibilty levels. Please suggest a suitable way to migrate these personalizations.
    thanks in advance,
    Hem

    Hem,
    We had the similar discussion in past once, but I guess the user didn't update the final results. As far as I think, 'Functional Administrator' -> Import/Export utility should be handling this scenario.
    Did you try it atleast on one such responsibility level personalization?
    --Shiv                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to migrate the Objects from 3.1c to BI7

    Hi,
    We are in Functional Upgradation.
    How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
    Please help me to doing this....
    regards,
    anil

    BW Upgrade tasks (BW 3.1C to BI 7.0)
    Prepare Phase:
    Task     How-To     Who
    Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
    Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
         Basis/BW
    Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
         BI 7.0 Upgrade notes
         SAP Web Application Server 6.40 upgrade notes
         OS and DB specific upgrade notes
         SAP BW Add-on upgrade notes
    (e.g. SAP SEM, ST-PI, etc)
         Plug-In upgrade SAP notes
         Other notes identified in above notes and/or upgrade guides.
         Basis/BW
    Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
         First check the most current information from the SAP BW homepage http://Service.sap.com/BW  -> <SAP BW release> -> Availability
         Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
         Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
         Basis
    Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
         SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
         WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
         Basis
    Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
         SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
         Source system Plug-In requirements     Basis
    Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
         ETL Tools (example:  Ascential, DataStage, etc)
         Scheduling tools (example. Control-M, Maestro, etc)
         Monitoring tools (example: HP OpenView, Patrol, etc)
         Other OS or DB related tools     Basis
    Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
    The IGS chart migration will also be required after the SAP BW web report conversion.
         If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
         If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0.  (ArcView 8.2?).
         If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
    Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides  -> SAP NetWeaver).
         Basis
    Test and distribute new SAP BW Frontend
              Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
         A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
         After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
         Basis
    Alpha Conversion:
    Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
    Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
    Transaction RSMDCNVEXIT
    Check the system status:
         u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
         u201CNo Check yet/Inconsistent Internal Vales existu201D:
    The Alpha converter check has not been executed.
         u201CCharacteristics have Inconsistent Internal Valuesu201D:
    The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
         BW
    Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
    Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
         Basis/BW
    Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
         Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
         Basis
    Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
    SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
         This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
    Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
         Basis/BW
    Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
         In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
    For SAP BW developments not already collected in the transport collector, a decision must be made:
    Deploy the developments or wait until the upgrade has completed to deploy.
    o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
    o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
         In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
         BW
    Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
         Basis/BW
    Pre-upgrade Process:
    Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
         There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
         It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
         BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
    For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
         You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
         Basis
    Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
    Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
         Transaction DB02:
    o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
    o     Check missing database objects (indices, tables, etc)
    o     Missing indices may identify erred data loads or process problems
    Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
    Note: check for running data loads before executing a repair!
    o     Check DDIC/DB consistency
         Verify database objects and consistency
    (e.g. SAPDBA check for offline data files)
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         BW
    Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
    Note: this test should be repeatable so you can re-validate after the upgrade!
         Ensure that any inconsistencies are identified and corrected
         RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
         Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
         BW
    Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
    Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
         Check DB statistics for missing Indexes for InfoCubes and Aggregates
    o     User transaction RSRV to check      BW
    Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
         Ensure the Support Package queue is empty
         Confirm all applied Support Packages     Basis
    Check all u2018Repairsu2019     Check for unreleased repair transports
         Release all unreleased transports
    In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
         Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
         BW
    Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
    All InfoObjects should be active or saved (not activate):
    o     Check all inactive InfoObjects:
    Transaction RSD1 (Edit InfoObjects),
    click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
    Modified InfoObjects are denoted by yellow triangles!
    o     Determine if revision should be activated or removed.
         'Reorgu2019 or u2018Repairu2019 all InfoObjects
    This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
         Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
         BW
    All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
    All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
    o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
         BW
    All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
    o     All update rules and transfer rules should be active or deleted.
    o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
    All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
    o     All InfoCubes should be activated or deleted.
    o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
         BW
    All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
    o     For Original release SAP BW 3.x:
    A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
    Please see SAP note 484519 for details.
         BW
    Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
         Database admin
    Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
    o     Repeat PREPARE until all checks are successful.     Basis
    Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
    o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
    o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
    o     Incorrect data classes could create activation errors during the upgrade.
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         Basis/BW
    Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
    Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
         Database Admin
    Before Execution:
    All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
    The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
         Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
    - timing depends on the type of upgrade selected
         Basis/Admin
    Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
    - timing depends on the type of upgrade selected
         BW
    Check system parameters     Check OS, DB, and Instance profile parameters.
         Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
         Check for any DB specific parameters for BI 7.0
         Check for any new OS parameters     Basis
    Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
         Database Admin
    After Execution:
    Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
         BW
    Check the system logs     Perform a technical systems check.
         Example: Check system and all dispatcher logs (inc. ICM logs)
         Basis
    Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
         Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
         Basis
    Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
    o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Apply latest patches          Apply the latest SPAM patch
         Apply any required support packages that were not bound into the upgrade.
         Basis
    Apply additional BI 7.0 Support Packages
    (if required)          SAP recommends that customer remain current on SAP Support Packages.
         Review SAP Notes for all SAP BW Support packages applied in previous task.
    o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
         Review and implement SAP note 569128 as required     Basis
    Configuring Information Broadcasting EP/KMC Connections
         If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
         Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
         Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
         For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
         Basis
    Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
         Repeat tests that we executed prior to the upgrade.
         Validate results      BW
    Check InfoCube views for consistency     Check consistency of InfoCube fact table views
         It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
         BW
    Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
         The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
         It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
    o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
         Check that all other Source Systems are active.
    o     Activate as required.     Basis/BW
    Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
    Validate that personalization has been activated in your SAP BW system.
    Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
         Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
    Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
         To activate highlighted Personalization, click Execute.     BW
    For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
         Re-create all indexes in the ODS Object definition screen in transaction RSA1.
         ODS indexes must conform to the new naming convention
         BW
    Converting IGS chart settings
         Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
         Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
    o      Test via transaction RSRT
         Execute the conversion process as directed the BI 7.0 upgrade guide.
         Note: This step is required for all BI 7.0 upgrades     Basis
    Backup your SAP BW system     Perform a full database backup (including the File system)
    Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
         Database Admin

  • Can a hierarchy datasource be copied in R/3 system?

    Hi All,
             I have a requirement wherein I have to copy an existing hierarchy datasource. Is it possible to copay a hierarchy datasource? If yes, how?
            Is it possible to create a hierarchy datasource in R/3? if yes, how?
    Please reply.
    Thanks and regards
    Rajib

    Hi
    You need to do some workaround
    The user exit EXIT_SAPLRSAP_004 in the R/3 source system allows you to enhance your hierarchy DataSources.
    Configure the Extractor in R/3
    create an empty hierarchy,
    generate the DataSource, and
    populate it with data from the table via EXIT_SAPLRSAP_004
    Edited by: Pavan on Feb 11, 2010 10:53 AM

  • How to Create Hierarchy

    Dear Experts!!!!!!!!!!
    Can some one explain me in detail, how to create hierarchy.
    both internal and external hierarchy,methodology,steps.................
    Thanks in advance......
    Regards,
    Suman.T

    Explain the steps to load master data hierarchies from R/3 system.
    A summary of the steps are as follows:
    1) Goto Hierachy tab in infobject on to which your loading Hierachy data.
    2) Select With Hierarchies.
    3) Select Hierarchy Properties ( Time Dependent or not time depen..etc..)
    4) Click on External Chars in Hierarchies, in that select the characterstics on which this Hierarchy is depending.
    5) Then Create Infosource, assign Datasource.
    6) Create Infopackage, to load Hierarchies.
    7) Hierarchy section tab in Infoapackage select load Hierarchy and refersh the Available Hierarchies from OLTP, If it is Time dependent select time interval in update  tab.
    8) Then start the load.
    If you want to load from Flat file, some what different way to do it.
    It is normally done by the following:
    Transferring the master datasources in RSA5 to RSA6 and then replicating the DS into BW and assignment of DS to Infosource and cretaion of Infopackage and load it into the master tables.
    Generally, the control parameters for data transfer from a source system are maintained in extractor customizing. In extractor customizing, you can access the corresponding source system in the source system tree of the SAP BW Administrator Workbench by using the context menu.
    To display or change the settings for data transfer at source system level, choose Business Information Warehouse --> General Settings --> Maintaining Control Parameters for Data Transfer.
    Note: The values for the data transfer are not hard limitations. It depends on the DataSource if these limits can be followed.
    In the SAP BW Scheduler, you can determine the control parameters for data transfer for individual DataSources. You can determine the size of the data packet, the number of parallel processes for data transfer and the frequency with which the status IDocs are sent, for every possible update method for a DataSource.
    To do so, choose Scheduler --> DataSource --> Default Settings for Data transfer.
    In this way you can, for example, update transaction data in larger data packets in the PSA. If you want to update master data in dialog mode, smaller packets ensure faster processing.
    Thanks,
    Praveen Yagnamurthy,
    SAP BI Consultant,
    Blue Marlin Systems-INDIA.
    http://bluemarlinsys.com/bi.

Maybe you are looking for