1 / 4

Situation @Shell Downstream BW on HANA Migration & BW Solution R oll O ut

Situation @Shell Downstream BW on HANA Migration & BW Solution R oll O ut. Planned BW Roll Out for a large Business Unit (US Fuels) in 7/ 2014

malory
Télécharger la présentation

Situation @Shell Downstream BW on HANA Migration & BW Solution R oll O ut

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Situation @Shell DownstreamBW on HANA Migration & BW Solution Roll Out • Planned BW Roll Out for a large Business Unit (US Fuels) in 7/ 2014 • HANA Migration before this point in time (10/ 2013 or 2/2014) means that BW development for US Fuels will run in parallel with HANA Migration activities and dual productive BWs (BW on HANA and BW on Oracle) • How to eliminate risks for US Fuels roll out? Y weeks HANA/ Oracle in parallel X weeks prepare HANA migration US Fuels BW Development

  2. Situation @Shell DownstreamBW on HANA Migration & BW Solution Roll Out How to eliminate risks for US Fuels roll out? US Fuels development is fully done on BW Oracle Dev-system until HANA migration is successfully completed (end of parallel run of BW Oracle Prod and BW HANA Prod) Handover of US Fuels development to BW HANA Dev-system before Prod migration will take place – BW Oracle Dev-system as backup • General remarks: • First of all there are no adoptions to BW solutions (BWSP) on Oracle needed before a migration to BW HANA to run smoothly on BW on HANA! • BW on Oracle and BW on HANA is the same BW, the same code ! BW notices in which environment it is running. • There might be some adoption in Transformation rules (coding of routines) necessary after migration to HANA – I gave you the two –pager • One measurement is providing hints to the HANA DBSL and HANA itself – so this would not affect negatively affect a BW on ORACLE running in parallel with BW on HANA for a certain time • The other adoption is with select singles & working with internal tables – I cannot see a negative impact for BW on Oracle • Housekeeping on BW Oracle is recommended before migration (s. other worklist items) – but I am confident that your BW is in a good state -> these topics should be discussed in a future BW HANA migration assessment

  3. BW on HANA Migration & BW Solution Roll Out1. US Fuels development is fully done on BW Oracle Dev-system until HANA migration is successfully US Fuels development is fully done on BW Oracle Dev-system until HANA migration is successfully completed (end of parallel run of BW Oracle Prod and BW HANA Prod) US Fuels Dev BW OraDev BW Ora Prod Transports Migration Migration Transports BW HANA Dev BW HANA Prod Transports (US Fuels Dev) • No changes in BW on HANA possible as all changes in BW HANA Devwill be wiped out if the Objects are transported again from BW Oracle Dev • As no development in BW on HANA dev meaningful – no BW on HANA feature usage until handover • BW solutions on BW HANA prod will remain Oracle-like until handover of BW dev to BW HANA dev-system

  4. BW on HANA Migration & BW Solution Roll Out2. Handover of US Fuels development to BW HANA Dev-system before Prod migration will take place Handover of US Fuels development to BW HANA Dev-system before Prod migration will take place – BW Oracle Dev-system as backup (US Fuels Dev) BW OraDev BW Ora Prod Transports Migration Migration Transports BW HANA Dev BW HANA Prod Transports US Fuels Dev • All Fuel dev done on BW on HANA dev • Limited (to be defined) usage of BW HANA features and no new LSA++ design (must be controlled) • Allows e.g. usage of HANA-Optimized DSOs as they are in a transport to BW ORA converted to STD DSO • No changes in BW OraDev except (will not be overwritten by transports from BW HANA dev – to be verified!) • Oracle specific changes like data class (tablespace) assignments • Aggregates creation • Oracle track remains fully functional until retirement – makes overall risk acceptable

More Related