Upgrading convertion routene from BI3.5 to BI7.0

Hello experts,
                      I am an ABAP consultant, We are upgrading the code written in BI conversion routines of 3.5 version to BI 7.0.
Below is the code in a BI 3.5 routine.
PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line  *-*
DATA: l_pp_o0100 LIKE /bi0/app_o0100,
      l_pp_ds0300 LIKE /bi0/app_ds0300,
      g_prodorder_save LIKE /bi0/app_o0100-prodorder,
      g_wip_factor LIKE /bi0/app_o0100-maxwipfop,
      g_wip_factortotal LIKE /bi0/app_o0100-maxwipfop,
      g_amount_cumulated LIKE /bi0/app_ds0300-amount,
      l_/bi0/app_o0100_itab TYPE HASHED TABLE OF /bi0/app_o0100 WITH
      UNIQUE KEY prodorder,
      l_/bi0/app_ds0300_itab TYPE HASHED TABLE OF /bi0/app_ds0300 WITH
      UNIQUE KEY coorder calday.
*  FORM check_new_prodorder
*  -->  L_PRODORDER
*  -->  G_WIP_FACTOR
FORM check_new_prodorder USING l_prodorder
                         CHANGING g_wip_factor.
  IF l_prodorder NE g_prodorder_save.
    CLEAR l_pp_o0100.
    READ TABLE l_/bi0/app_o0100_itab WITH TABLE KEY prodorder =
    l_prodorder INTO l_pp_o0100.
    g_wip_factor = ( l_pp_o0100-maxwipfop + l_pp_o0100-maxwipfwi ) / 2.
    g_prodorder_save = l_prodorder.
  ENDIF.
ENDFORM.                    "check_new_prodorder
*$*$ end of global - insert your declaration only before this line   *-*
FORM compute_data_field
  TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
  USING    COMM_STRUCTURE LIKE /BI0/_2CS2LIS_04_P_MATNR
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
  CHANGING RESULT LIKE /BI0/V0PP_C02T-WIP
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
*$*$ begin of routine - insert your code only below this line        *-*
* fill the internal table "MONITOR", to make monitor entries
* result value of the routine
  PERFORM check_new_prodorder USING COMM_STRUCTURE-prodorder
                            CHANGING g_wip_factor.
  RESULT = g_wip_factor *  COMM_STRUCTURE-itemqty -
                           COMM_STRUCTURE-gr_qty.
  IF RESULT < 0 OR
     COMM_STRUCTURE-gr_qty = 0 OR
     COMM_STRUCTURE-gr_qty = COMM_STRUCTURE-itemqty.
    RESULT = 0.
  ENDIF.
* if the returncode is not equal zero, the result will not be updated
  RETURNCODE = 0.
* if abort is not equal zero, the update process will be canceled
  ABORT = 0.
*$*$ end of routine - insert your code only before this line         *-*
ENDFORM.
I have written the global form check_new_prodorder in an subroutine pool program and tried to make an external call in the conversion routine ( of BI 7.0 version ).
I see in the debug mode that there is no records in the internal table l_/bi0/app_o0100_itab in the global form called in the local form, but in the older version ( in 3.5 ) there is data in the internal table specified.
Please provide your valuable inputs on this issue of mine,
Regards,
Murthy.

Hello Murthy,
check these links for some pointers:
/message/6271894#6271894 [original link is broken]
BW 3.5 to BI 7.0 Upgrade - ABAP OO migration
Re: Risks of upgrade from BW 3.5 to 7.0
Regards,
Lakshmi

Similar Messages

  • Delta not working after upgrade from 3.5 to BI7.0

    Hello All,
    We have recently upgraded from BW3.5 to BI7.0 and the standard delta is not working now after the upgade. The name of the Extractor is 0CRM_SALES_ACT_1.
    Did anyone come across this problem before or  can anyone suggest the solution.
    Thanks
    Madhu

    Hi Madhu,
    I've experienced a similar problem with this extractor.  I attempted to Initialize Delta with Data Transfer to no avail.  The job ran for 12+ hours and stayed in "yellow" status (0 records extracted).  The following steps worked for me:
    1.  Initialize Delta without Data Transfer
    2.  Run Delta Update
    3.  Run Full Update and Indicate Request as Repair Request
    Worked like a champ, data load finished in less than 2 minutes.
    Hopefully this will help.
    Regards.
    Jason

  • BW Upgrade from 3.1 to BI7.1

    Hi,
    we are planning to upgrade one of our BW3.1 to BI7.1 ABAP+JAVA system.I need some details about the BW upgrade before palnning.
    Our BW current version is BW3.1(SAP BASIS 620)
    Is it possible to upgrade BW3.1 ABAP system to BI7.1 ABAP+JAVA system in same upgrade tool?
    Is it possible to upgrade BW3.1 to BI7.1 directly?
    or do i need to upgrade first BW3.1 to Bw3.5 and then BW3.5 to BI7.1?
    Thanks in advance.
    Vijay

    I dont think 3.1 had JAVA comnponents - you would have to necessarily go for a separate stack install..
    The path would be :
    Upgrade 3.1 kernel to 640
    Upgrade to 7.1
    Install and configure the JAVA Stack - you could have the JAVA WAS running on the same server if required - but your server has to be sized for the same.
    You will have to install the JAVA stack separately...
    else..
    Upgrade to 3.5 - install the JAVA components
    Upgrade to 7.1 as a dual stack - but this would mean that you will have to test and validate the 3.5 upgrade first.
    Edited by: Arun Varadarajan on Oct 14, 2010 8:27 PM

  • I just recently upgraded my itouch from 4.1 to ios5, and updated to itunes 10.5. when isynced my music files,ebooks and other apps, all is working except when im trying to sync my video files. it says, canot be synced as cannot be played on this ipod.help

    i just recently upgraded my itouch from 4.1 to ios 5, and updated to itunes 10.5. but when i synced my music files,ebooks and other apps, all is working except when im trying to sync my video files. it says, canot be synced as cannot be played on this ipod. but those are the same files that i have when i was using the old 4.1 version and its syncing just fine.. the itunes advanced tab "create iphone or ipod version" is not working either so i cant convert it to be xferred and synced. what can i do to have my video files synced?

    i had the same problem but i just got a new video converter and made it convert videos to ipod/iphone format and then put them into itunes. i would suggest GOM encoder as the encoder can convert them and then once they're finished converting, put them automatically into your itunes for you. from there you can just sync them to your ipod.

  • Data load from ECC6 Unicode to BI7 MDMP

    Hello Contributors,
    We are upgrading R3 system to ECC6 Unicode but BI7 is still MDMP system. I'm testing data load and there are some errors related with unicode conversion.
    ECC has multiple langusges like English, Korean, Chinese etc...
    BI7 MDMP has English and Korean.
    Error1 :  Korean characters are broken in 0CUSTOMER_TEXT.
       As you know customer name doesn't have language code in R3 and Korean text are being used for Korean customers. After loading the data, English characters are okay but Korean characters  are broken and displayed as #
    Error2 :  Values of fields are merged each other if there is Korean characters in 0CUST_SALES_ATTR.
       We have Korean characters in some of attributes of 0CUST_SALES. So if a record has Korean characters in one of the field then the following fields are merged each other. But if there is no Korean characters then it is loaded correctly.
    For an example;
    Values of R3 extractor
        Cust#      Name               Field1          Field2     Field3
        1234     Korean Text               ABCD          EFGH     JKLM
        3456     English Text               OPQR          STUV     WXYZ
    Values of PSA table after loading
        Cust#      Name               Field1          Field2     Field3
        1234     Korean Text AB     CDEF          GHJK     LM     
        3456     English Text              OPQR          STUV     WXYZ
    (*if there are Korean characters then the following fields are divided and a part is updated in to the previous field)
    Please help me if you have any ideas to resolve this issues.
    Best Regards
    HD Sung.

    Convert your BI system to Unicode.  MDMP is not supported in this scenario, as you have found.

  • Converting Catalogs From Photoshop Album (2.0) to Photoshop Elements 13

    My Photoshop Album currently holds some 23,000 photographs/jpgs from 2003 to date. Each is catalogued to provide a very high level of granularity to assist in identifying specific photographs and their subject content.
    I have purchased Photoshop Elements to update the management of the collection. The Adobe information identifies it to be a suitable successor but indicates that there is likely to be some effort required to update the catalog. Using Catalog Manager I have attempted to Convert the old catalog which didn’t work because it “couldn’t be seen” in Elements. Further research of the Forum and other Adobe resources pointed to the Catalog Conversion Utility. Again this also failed to work.
    I then reduced the number of photographs to about 4,500 (year 2014). I have noted by the way that this has had virtually no effect on the psa file size. As I gradually Deleted photos from the Catalog I have come across about 100 items which cannot be deleted and returns the following error message….
    The ODBC data source reported the following error:
    “[Microsoft][ODBC Microsoft Access Driver] Indicator variable required but not supplied on column number 10 (fDateTimeHigh)”
    I have tried a number of ways to delete the photos including removing them from their folder; “Reconnecting the Missing File” with/without the same name in a different Folder; and generally getting myself very frustrated with my lack of knowledge. Googling/search for help and pointers hasn’t found the solution.
    What or where can I find a way of deleting these errant files? (I have MS Access if this is a tool that might get me the solution.)
    Note that one very old and small Catalog did convert and successfully integrated into Elements so it all works in principle. It seems to point to these problem jpgs.
    Any help would be much appreciated.
    FROM PHOTOSHOP ALBUM
    System Details:
    #### NOTE the following is incorrect (copied from “System Info” on Album Help. This is the original build OS; currently Windows 7 with latest updates. See further down for Photoshop Elements for System Info. ####
    Adobe Photoshop Album 2.0.0.16271
    Current Catalog:
    Catalog Name: Main.psa
    Catalog Location: C:\ProgramData\Adobe\Photoshop Album\Catalogs\
    Catalog Size: 45MB
    Catalog Cache Size: 536MB
    System:
    Operating System Name: XP
    Operating System Version: 6.1 Service Pack 1
    System Architecture: Intel CPU Family:6 Model:10 Stepping:7 with MMX, SSE Integer, SSE FP
    Built-in Memory: 4GB
    Free Memory: 4GB
    Important Drivers / Plug-ins / Libraries:
    Microsoft DirectX Version: 9.0
    Apple QuickTime Version: 7.76
    Adobe Image Viewer Version: Not installed
    Adobe Acrobat Reader Version: 11.0
    Adobe Acrobat Version: 10.1
    Adobe Atmosphere Version: 3.0
    FROM PHOTOSHOP ELEMENTS
    Elements Organizer 13.0.0.0
    Core Version: 13.0 (20140831.m.62014)
    Language Version: 13.0 (20140831.m.62014)
    Current Catalog:
    Catalog Name: Mum & Dad Document Scans
    Catalog Location: C:\ProgramData\Adobe\Photoshop Album\Catalogs\New Catalogs\Mum & Dad Document Scans\
    Catalog Size: 132KB
    Catalog Cache Size: 31.8KB
    System:
    Operating System Name: Windows 7
    Operating System Version: 6.1 Service Pack 1
    System Architecture:
    Built-in Memory: 8GB
    Free Memory: 4.6GB
    Important Drivers / Plug-ins / Libraries:
    Microsoft DirectX Version: 9.0
    Apple QuickTime Version: Not installed
    Adobe Reader Version: Not installed
    Adobe Acrobat Version: 10.1
    CD and DVD drives:
    D: (ATAPI iHAS624 BUS: 1 ID: 1 Firmware: B)

    Yes. Thanks for your reply. Just shows my age doesn't it! I've really got to upgrade my system from Windows 3.1.
    Still it lasted me for quite a few years over its various issues and wasn't a bad investment for me considering I think it was a magazine cover freebie, though I can't remember whether it was issued on 5" or 3" disks!!!
    Interesting to note that conceptually the original design was quite good and together with the new face recognition technology which is as good if not better than Picasa the PSE13 Organiser does a good job. It's a pity Adobe doesn't promote more of this side of the product. I wasn't able to find the replacement to Album as it was starting to struggle as the photo count increased and I hadn't been able to find an obvious replacement. Still that's over now.
    All I have to do now is to raise a query as to how to order/sort certain tags and it's a near perfect product for me. Can't find the answer in the Manual(s) or FAQs - or I'm not using the correct query key words.

  • Extraction issue in BI after Migration of dataflow from 3.x to BI7

    Hi,
    We are doing a BI upgrade project from 3.x to 7. I have the following
    query on data extraction from PSA to DSO and then to infocube after
    migration of dataflow (Updaterules, transferules and datasource) from
    3.x to BI7.
    When I load data from PSA to DSO using DTP it is taking all the
    requests data to DSO (all old requests data) instead of only new delta
    request data. And also when i load from DSO to infocube same problem
    is there (instead of taking only new delta request data, extracting
    all dso active data).
    Please suggest.
    Best Regards,
    SG

    In BI 7, we dont have an option to run init without data transfer. So first time when you run a delta DTP it will work as full load and set init pointer. This is expected.
    Case 1: If you have already loaded duplicate data into the data targets
    a. If request is already compressed perform reverse posting. if not compressed then perform selective deletion based on the request.
    b. Next deltas will work fine.
    Case 2: Still not loaded
    Follow the steps suggested by Luther Blake.
    Thanks,
    Hemanth

  • 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

  • Upgrading to iTunes9 from iTunes 8.2.1

    I wanted to know if my music would be deleted from my Libary if I upgrade to iTunes 9. Also I am not getting the Upgrade to iTunes 9 message when I open iTunes, and also will upgrading to iTunes fix my importing and buring of CDs and DVDs which states they are missing.

    I would wait before upgrading to iTunes9, from past experiences I'll wait till the bugs are fixed and no one is having any issues. It's another reason why I havn't converted over to Snow Leopard just yet. There is no hurry to update anything that you might have any concerns.
    Message was edited by: wygold

  • Converting Webutil from 10g to 6i.

    hi,
    I'm trying to convert webutil from 10g to 6i. Coz i need to give some facility of FTP.
    i'm able to change all the packages. But few packages like JAVA*, are not able to compile. it is giving error, some JNI. How to resolve this?
    Regards,
    Subir

    I will assume your application is deployed in a browser and not client/server in order to form my comments.
    Rather than trying to get WebUtil working in 6i, it would probably be simpler to just do what WebUtil does and write your own java bean. You can use the WebUtil code as an example. The important thing to remember is that WebUtil was designed with JDK 1.3.1.x and Forms 6i is based on 1.2 and older therefore you cannot just simply copy the WebUtil code and expect it to compile.
    If you have access to Metalink, here are two notes which explain how it can be done.
    Metalink Article ID 117340.1 How to Display Images in Webforms from the Client PC (Uploading Files)
    Metalink Article ID 116129.1 How to Upload and Save Data From/To a Local Client File Using Web Deployed Forms
    Best suggestion..... upgrade! ;)

  • How do I convert DOWN from Keynote '09 to '08?

    I'm trying to take a Keynote presentation and convert it from Keynote 09 down to 08. Please tell me there's an easy solution!

    you cant convert a newer version of a Keynote file to an older version. The file types are completely different and not backwards compatible.
    Thishappens with many applications when they are upgraded like Final Cut Pro, DVDS Pro, Aperture, et al
    If you need an 08 file you will need Keynote 08 to create it.
    You can export a Powerpoint file from Kenote 09 and then import that into Keynote 08 but you must keep it simple so it can export across.
              (file > export > Powerpoint)

  • Font trouble when upgrading to 6i from 2.5 on the HP-UX server

    Hi,
    We've recently upgraded to 6i from version 2.5 (developer
    2000). Most everything went smoothly except when deploying our
    server reports. We use Times New Roman on the PC based reports
    and those that are run on the server are mapped/aliased to
    Times. Everything worked fine in the 2.5 version. I have
    checked the setup of fonts, ppd files, and the like and
    everything is correct. In fact looking at the generated output,
    postscript (.ps) file, with a text editor you can see that the
    proper font has been used. Although, we still get lines that
    aren't wrapped, misalignment, centering doesn't work, etc.
    If I run the report at the HP-UX console the output looks fine
    as, just like the PC windows NT version. It's when the report
    is run using the command RWRUN60 that the output is incorrect.
    I get the same results when generating postscript or PDF files.
    As I said earlier the same application works fine for 2.5
    versions. And the correct ppd file and fonts are used. But the
    output is skewed. Leading me to believe that there is bug in
    the engine that builds the report output in the new version of
    the tool. Any suggestions would be most appreciated.
    thanks
    terry

    Hi.
    I am going to start on a new project where
    we will convert Reports from 2.5 to 6i.
    What's the procedure for converting reports
    from 2.5 to 6i? Is it as easy as opening the
    2.5 reports in the 6i builder or is a conversion
    needed like running RWCON60?
    I hope you can help me on this. Who knows maybe
    along the way we will encounter your problem and
    we might be able to return the favor.
    Again thank you very much.

  • What is the impact of upgrading jdbc drivers from 9.2 version to 10g driver

    Hi,
    My application is built on Oracle 9.2 with 9.2 version jdbc drivers.
    To use Java objects mapping with Oracle object TYPES (for ex. STRUCT),
    I had to go for 10g jdbc drivers. Otherwise, I am getting an error:
    java.sql.SQLException: Non supported character set: oracle-character-set-178
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
    at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:829)
    at oracle.sql.CharacterSetUnknown.failCharsetUnknown(CharacterSetFactory
    Thin.java:150)
    at oracle.sql.CharacterSetUnknown.convert(CharacterSetFactoryThin.java:1
    14)
    at oracle.sql.CHAR.<init>(CHAR.java:109)
    at oracle.sql.CHAR.<init>(CHAR.java:133)
    at oracle.jdbc.oracore.OracleTypeCHAR.toDatum(OracleTypeCHAR.java:143)
    at oracle.sql.StructDescriptor.toOracleArray(StructDescriptor.java:385)
    at oracle.sql.StructDescriptor.toArray(StructDescriptor.java:560)
    at oracle.sql.STRUCT.<init>(STRUCT.java:95)
    at oracle.sql.OracleSQLOutput.getSTRUCT(OracleSQLOutput.java:95)
    at oracle.sql.STRUCT.toSTRUCT(STRUCT.java:328)
    at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedSt
    atement.java:2025)
    at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedSt
    atement.java:2148)
    I would like to hear from you that, what is the impact on the existing application if I upgrade
    jdbc drivers from 9.2 version to 10g version?
    Please do mention all the impact.
    Vyshu

    JDBC 10g works just fine against 9.2 database. See the interopeability matrix on the JDBC portal http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
    Kuassi - blog http://db360.blogspot.com/

  • Upgrade/convert 521 to LWAPP

    I have a 526 controller and 4 521 APs on my LAN that I want to upgrade to LWAPP. I am using CCA and all the help says this should be a point-and-click type of thing. However, when I try the upgrade the CCA asks for an image I don't have and can't find in the CCA folder. The download section for the 521 doesn't have it either. Where can I get this image? Is there another way to upgrade?
    Thanks in advance,
    Diego

    I have the right recovery code but the CCA topology map doesn't even see any of my 521 AP's. It can see the WLC526 and it can see the 3560 PoE switch it's attached to, but those are the only 2 items on the topology map. I'm using native VLAN as 100. I set the ports the 521's into a trunk ports w/ native vlan as 100 so I can http to the 521 AP's. I'm using 3 vlans, voice, guest, and internal users but I just can't get them to join the WLC as LWAPPS??? Frustrating!! Any ideas? All the documentation shows the AP's showing in the topology map and then you just point/click to LWAPP recovery image to convert them from autonmouse to LWAPP but I can't even see them in the topology map yet I can ping and web to them and they seem fine. I could probably leave them all autonomous and manually configure all 5 and have it work anyways but I'd be waisting the WLC 526 and it would serve no purpose?!?!?!
    Thanks!!!

  • How to migrate the Workbooks from BW3.1 to BI7

    Dear Team,
    How to Migrate the workbooks from Bw3.1 to BI7. We have recently upgraded to BI7. What are necessary steps and necessary cares needs to take for this.
    Best Regards,
    SG

    Migration is manual. When you open up a 3.x component in a 2004s tool in migrates it. There is no automatic migration available
    Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
    Migrating Advanced BEx Analyzer Workbooks - What VBA is Supported?
    Hope it Helps
    Chetan
    @CP..

Maybe you are looking for

  • Migrating individual applications.

    Is there anyway to migrate only specific applications from one Mac to another and not the entire drive? I am dealing with a 17" Powerbook that recently had it's hard drive wiped with a clean install of Tiger. Two of the programs on it were Photoshop

  • Any way to connect two external displays?

    Hello, I have a quick question about connecting my PowerBook G4 15'' (machine model: Powerbook 5,6) to some external displays. I am trying to connect it to both a Samsung Syncmaster LCD and my TV. Currently, I am able to connect to each successfully,

  • BAPI_ SALESORDER_CHANGE in MY SAP ERP 2005- Issues

    Hi Gurus, We are trying to change a Sales order using the  BAPI : BAPI_ SALESORDER_CHANGE in a Zprogram . The program  works fine in SAP 4.5B version. But in MY SAP ERP 2005,<b> we get error with the BAPI.</b> <u>Scenario :</u> The BAPI is working wh

  • Saving Pdfs smaller

    Hello, I have a large pdf, 2mb and I would like to be able to send this through email easily so I was hoping to be able to size it smaller. I was told that I could use "save as" and it would convert smaller but that application in Adobe Reader was "s

  • Swing with third party libraries

    I know that within the Java SDK there is an extensive ability to create 2D and 3D graphics for use in an application. However, what is the situation with 3rd part libraries (e.g. specifically looking at Open Inventor from numerical algorithms group).