|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/sap-ecc-to-sap-s4hana-aerial-view-of-migration/
课程评论：没有评论
课程名称：从SAP ECC到SAP S/4HANA - 迁移的全景视图 课程概述： 本课程针对SAP S/4HANA的迁移过程，使用企业架构工具，探讨了三种主要迁移方式：Greenfield（全新实施）、Brownfield（完全迁移）以及混合（Hybrid）方式。Greenfield方式意味着公司放弃现有的ERP系统，从头开始构建全新的系统。 1. **Greenfield方式** 此方式其实并不是一种迁移，而是全新实施S/4HANA，代表从无到有的重新构建。它可能只是迁移数据或根本不进行迁移，企业可以摒弃旧有的定制，简化流程。 2. **完全迁移（Full Migration）** 完全迁移是现有SAP系统完整转化为SAP S/4HANA的一种方法，通常被称为“lift-and-shift”。这一过程需要使用SAP软件更新管理器和数据库迁移选项，适用于没有使用SAP HANA数据库的企业。 3. **混合迁移（Hybrid Migration）** 在这种方式中，组织首先需要分析现有的SAP系统，识别定制应用、功能及接口，然后使用低代码平台提前开发非标准组件。这样可以保持SAP核心的干净，从而简化迁移过程。 **哪种方式最好？** 选择哪种方式取决于企业的特定情况和现有的SAP系统。例如，对于使用二十多年历史的老旧SAP系统的企业，Greenfield方式可能是最佳选择，而对于"全方位SAP支持"的企业，完全迁移更为合适。混合迁移则适合希望避免被单一供应商锁定、并需要在创新和实施之间取得平衡的企业。 **未来展望** 根据Gartner的说法，未来的ERP系统将是可组合的，打破传统的单一ERP系统结构，可以更好地满足现代企业的灵活需求。混合迁移在此背景下显得尤为适用，因为它提供了创新与灵活应对市场变化的能力。 通过本课程，参与者将深入了解SAP S/4HANA的迁移选项及其适用场景，以制定适合自己企业的迁移策略。
SAP S/4Hana migration is done with enterprise architecture tools using the Greenfield, Brownfield, or combination of both approaches. The Greenfield approach means that companies abandon their existing ERP system and build a completely new one through migration.SAP S/4HANA Migration OptionsAlthough experts at SAP and other tech leaders can reel off quite a few ways of handling a switch to SAP 4/HANA, three are more commonly recommended than the others.1. Greenfield ApproachOne option isn't really a migration option. Instead, it's an implementation of S/4HANA from the ground up."Greenfield" is a term adopted from architectural and environmental engineering that means starting fresh on land that has no previous construction. For S/4HANA specifically, it means either migrating data only or no migration at all. You retire legacy customizations and work to streamline processes.2. Full MigrationA full migration approach is a complete conversion of an existing SAP system to SAP S/4HANA, a method often referred to as "lift-and-shift."This scenario involves using SAP Software Update Manager with a database migration option for any enterprise not using SAP HANA as their database. To address application customization, enterprises can use SAP cloud and SAP partner development tools.3. Hybrid MigrationIn a hybrid migration, organizations need to analyze the current SAP system and identify the customized applications, functionality, and interfaces that are not part of the core.Before the migration, enterprises can use a low-code platform to develop the non-vanilla pieces and applications used by the system. By doing that work in advance, the SAP core is kept clean to make the migration easier.Afterwards, your business is using S/4HANA for what SAP does best-enterprise resource planning-and other apps for what it doesn't do best.Which Option Is the Best?The answer to this question is that each option is best for particular types of enterprises and their current SAP systems.Enterprises With Decades-Old SAP SystemsPrior to the pandemic, if enterprises had SAP systems that were 20 years old or more, greenfield was likely to be the best option due to the complexity caused by age and years of customizing. They could use the shift to technology as a springboard for redefining their processes from scratch.But due to the issue of remote work, very few have embarked in lift and shift due to the increased risk of not having all the players in the same room to handle issues as they arise.In addition to that, this approach also involved major investment in a brand new implementation and a complete, usually waterfall, analysis of the existing system and the processes to be reworked. So, although the greenfield option offers the possibility of running the old system while installing the new, business disruption of some sort is likely.One-Stop ShoppersFull migration works best for "SAP houses" that invest in every SAP tool they can. These enterprises like having a full suite of SAP solutions for migration and partner solutions for creating modern applications at their disposal. Why go through the hassle of stitching together multiple vendor offerings and assuring data consistency if they don't have to?The downsides are vendor lock-in with no graceful way to exit if technology changes, last-mile UI customization, and narrow parametrization of workflow and data. Also, of the three options, this one has the greatest likelihood of business disruption.Compose Your New FutureGartner says the future of ERP is composable meaning, monolythic ERP systems can't easily meet the agility requirements of our now "new" normal. Breaking an ERP into composable "parts" gives customers new options who want to integrate best-in-class functions, applications, and datasets unique to their business to create perfect-fit solutions and amazing customer experiences. In this case, hybrid migration is best for them because they:Do not want to be locked into a single vendor;Need to allot finite resources to innovation, not a major system implementation;Want the agility to respond to future changes in technology and the market.
