On the Road to BW/4HANA – second stage finalized

This is the second Part of the Blog – On the Road to BW/4HANAfirst stage accomplished

Now we have to go back to the Solution Manager and make sure that the correct data is synchronized from the SAP BW Backend with the BW/4HANA Starter Add-On is replicated first to the SLD and then to the LMDB of the Solution Manager.
If you are struggling here, see the
– SAP First Guidance – SEM/BW Modelling in SolMan 7.1 with MOPZ

If there are Problems with the needed Attribute Change Packages, see the
– SAP First Guidance – complete functional scope (CFS) for SAP BW/4HANA


Transaction RZ70 in the SAP BW Backend

Note 1977240 – Extension of the AS ABAP SLD Data Supplier (RZ70)
Note 2188401 – Enabling HTTP(S) in RZ70

Resynchronize Technical System from SLD into LMDB

Upload the correct data from the Solution Manager to the SAP Support Portal

Log on to the Maintenance Planer and select your SAP Backend System

Check that your system data is replicated to the Maintenance Planer (this might take a few minutes)

Continue with the Maintenance Task …

Download the Stack XML and push the files to your Download Basket.

If the needed software component SAP_ABA 75A was not selected by the Maintenance Planer, you can also download the necessary files manually and add the files to the import queue.

Now we can continue with the technical migration to BW/4HANA.

Run the BW/4HANA Migration

The migration can be done without the software update manager (SUM) directly in the SAP BW system via Transaction SAINT. Make sure that your SAINT version is recent (7.50/0063)

Choose your created Stack XML File

Additionally you have to select the SAP_ABA 75A component in the selection here as well.

The technical migration to BW/4HANA is running now.

hmm, this is strange. Table RSADMINC has to be enhanced by two fields:
Field RSADMINC-PSAPARTSIZE_HDB does not exist
Field RSADMINC-PSAPARTSIZE_HDB_FS does not exist
Field => Data Element => Domain => INT4

After the Implementation is finished, run Transaction SPAU to reset everything back to SAP standard.

Once the SAINT procedure is finsihed, you can continue in you new system with BW/4HANA specific settings. Check the Document – SAP First Guidance – complete functional scope (CFS) for SAP BW/4HANA

If you are not yet using the BW Modeling Tools (BW-MT) now it is the time to activate them – see SAP First Guidance – Implementing BW-MT as the new SAP BW Modeling Experience

Congrats, your System is now migrated to BW/4HANA!!!

SP02 for BW/4HANA is released … – news with SP01 for BW/4HANA

Note 2379490 – SAPBWNews SAP BW/4HANA 1.0 SP 02 => Feature List attached

 


Roland Kramer, PM EDW (BW/HANA/IQ), SAP SE
@RolandKramer

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. InHouse Admin

    Hi,

    Thank you for the blog.

    We have upgraded our system from 7.4  to 7.5. We didn’t find the uninstall package  for POASBC_731 100 during the upgrade process. We have continued with upgrade process  by choosing “Keep version” for POASBC_731 100.

    Now we are unable to uninstall the add on “SAP PC 10.1 For SAP NW (component POASBC 100_731, SAP Note 2322477” as De-installble tab page not visible in SAINT transaction and we have updated our SPAM version to 750/63.

    Please advise how to get this De-installble tab page in SAINT transaction

    Regards,
    Manasa.

     

    (0) 
  2. Roland Kramer Post author

    Hello,
    When you upgrade from SAP BW 74 to 7.5 die BPC Add-On 10.1 is merged to the SAP_BW Component, see the Presentation

    Did you also had a look to the SAP Note 2256796?

    If you still have a POA 731 Component in you 7.40 System prior to the Upgrade to 7.50 there might be also an error in the System Definition in the connected Solution Manager.

    Therefore you have to repair the Source Vector before you can create the Target Vector of your SAP System, see – SAP First Guidance – SEM/BW Modelling in SolMan 7.1 with MOPZ


    Best Regards Roland

    (0) 

Leave a Reply