1a Business Suite 7 - Anexo y Links De Utilidad

850 views

Published on

SAP Business Suite 7 - La nueva versión modular de rápida implementación que incorpora al paquete clásico las soluciones específicas para los distintos procesos de una empresa de acuerdo a su industria (ERP, SCM, CRM, SRM, BO, etc.)

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
850
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

1a Business Suite 7 - Anexo y Links De Utilidad

  1. 1. MOVE/Global Upgrade OfficeAccelerating the Adoption of SAP Business Suite, SAPERP 6.0, SAP Enhancement Packages, and EnterpriseServicesSimple Upgrade | Clear Value | Profound OpportunitySAP Business Suite 7 Service-oriented ArchitectureTechnical Considerations inthe Context of Release Upgrades SAP Enhancement Packages SAP ERP SRM SCM CRM PLM 6.0 SAP Business SuiteMay 2009 SAP NetWeaver Business Process Platform (BPP)
  2. 2. Legal Disclaimer This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAPs strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.© SAP 2009
  3. 3. This E-Book Background and Objectives SAP Business Suite software is a comprehensive, fully integrated and modular suite of applications that drives: End-to-end industry processes. End-to-end process scenarios across multiple applications. It is a collection of SAP applications containing the go-to releases of software for SAP customers that want a stable core and continuous, minimally disruptive innovation: SAP ERP 6.0 with SAP enhancement package 4 for SAP ERP. SAP CRM 7.0. SAP SRM 7.0. SAP SCM 7.0. SAP PLM 7.0. Industry Applications and Supplementary Applications. SAP Business Suite offers companies the opportunity to transform business processes efficiently and integrate business with minimal disruptive innovation. Focusing on technology, this session provides an overview on: Upgrading existing SAP Business Suite applications. Technical considerations of SAP Business Suite 7.© SAP 2009
  4. 4. Business Suite Upgrades 1 SAP Business Suite 7 - Overview: End-to-End Processes 2 SAP Business Suite 7 - Landscape Upgrade Drivers© SAP 2009
  5. 5. Benefits of the New SAP Business Suite - Addressing New Customer Expectations SAP Business Suite 7 No more stovepipes SAP Business Suite Flexible end-to-end processes NetWeaver Composition Deploy as you go Stepwise projects and installation No more upgrades SAP enhancement packages = innovation Industry Applications packages SAP ERP SAP SRM SAP CRM SAP SCM SAP PLM Supplementary Applications Dynamic Re-usable enterprise services EHP NetWeaver EHP Integration Industry-focused Delivers integrated industry solutions Extensible Easy expansion beyond SAP ERP 6.0© SAP 2009
  6. 6. Flexible End-to-End Scenarios - Expands Support for Lines of Business Flexible End-to-end Scenarios Finance: Financial close Human Resources: Talent management Sales: Territory management Marketing: Loyalty programs Service: High-volume call centers Procurement: Service contract management Product Design: Process engineering integration Supply Chain: Warehouse & transportation management Manufacturing: Collaborative supply chain planning© SAP 2009
  7. 7. Accelerating “Lead to Cash” is an End-to-End, Cross-Functional Process [1] Bridge to Value Scenario “Collaborative Demand & Supply Planning” [2] Bridge to Value Scenario “Logistics and Fulfillment Management”© SAP 2009
  8. 8. Accelerating Lead to Cash: Implementable Step “Sales and Marketing Planning” EX AM PL E SAP Business Suite 7 Applications SAP ERP SAP CRM SAP Price & Margin Mgmt by Vendavo SAP Netweaver Business Warehouse© SAP 2009
  9. 9. Implementation Content: Value Scenarios SAP Solution Manager Content and Scenario Component List Implementation content includes SAP Solution Manager content and scenario & process component list. Value scenarios can be found in the new folder “cross-application implementation packages”. SAP Solution Manager Content Scenario & Process Component list: http://service.sap.com/scl© SAP 2009
  10. 10. Business Suite Upgrades 1 SAP Business Suite 7 - Overview: End-to-End Processes 2 Transition to SAP Business Suite 7 Technology Considerations Overview A Upgrade per Application B Deploy further Applications© SAP 2009
  11. 11. Transition to SAP Business Suite: Business Scenarios Determine the Transition Path Target Key Technology Considerations Current Business Suite 7 Business scenarios in ONE application Upgrade per application SAP Appl. BS 7 Appl. 1 Complexity Drivers e.g. SAP e.g. EHP 4 Upgrade 2 Unicode R3 4.X A for SAP ERP 6.0 3 SAP Enhancement Packages Upgrade the respective application. Activate new functionality. 4 Upgrade Paths Business scenarios ACROSS applications Deploy further applications SAP Business Suite SAP Appl. NetWeaver Composition 1 Mandatory Components e.g. SAP Upgrade & Deploy Industry Applications 2 Upgrade Dependencies B R3 4.X SAP ERP SAP SRM SAP CRM SAP SCM SAP PLM Supplementary Applications EHP EHP NetWeaver Integration 3 Deployment Options Upgrade the respective applications. Deploy required additional applications. 4 SAP NetWeaver ScenariosSource: MOVE/GUO© SAP 2009
  12. 12. Business Suite Upgrades 1 SAP Business Suite 7 - Overview: End-to-End Processes 2 Transition to SAP Business Suite 7 Technology Considerations A Upgrade per Application B Deploy further Applications© SAP 2009
  13. 13. Complexity Drivers 1 Upgrade Complexity Classification Dependencies to Number of add-ons / Number of modified connected systems1 industry solutions objects Required downtime Code freeze strategy Upgrade Project Complexity Drivers Testing Source release requirements Number of Type of upgrade OS / DB migration codepages (technical/functional) requirements Duration/effort of an upgrade can mainly be determined based on system scope/system complexity2. Different upgrade complexity drivers per application to be considered. 1SAP and Non-SAP 2Other factors influencing the upgrade effort (i.e. organizational complexity, knowledge) are considered in a later stage© SAP 2009 Source: MOVE/GUO
  14. 14. Unicode - 2 Upgrade Paths to Unicode Example: SAP R/3 to SAP ERP 6.0 As-is Release including SAP enhancement package 4 R/3 4.0b SAP ERP 6.0 R/3 4.5b including Direct SAP ERP 6.0 Con- SAP enhance- upgrade non-Unicode1 version ment package 4 R/3 4.6b Unicode R/3 4.6c Other, more First upgrade, then conversion to Unicode2 recent releases1 If No. of Code Pages in old system > 1 then the Unicode Conversion MUST be done IMMEDIATELY after upgrade2 If MDMP is used (i.e. systems contains multiple code pages) then Unicode conversion can be done first, or with an upgrade© SAP 2009
  15. 15. SAP Enhancement Packages - Available 3 And Synchronized For The Entire Suite© SAP 2009
  16. 16. 3 Enhancement Packages - Lifecycle The roles mentioned on this slide refer to the SAP Standards for E2E Solution Operations.© SAP 2009
  17. 17. Upgrade Paths - How to Get to SAP Business 4 Suite 7 if You’re Running on... Core Applications of SAP Business Suite 7³ Install SAP enhancement package 4 SAP ERP 6.0 SAP ERP 6.0 plus for SAP ERP SAP enhancement package 4 for SAP R/3 4.0B¹ SAP ERP and above (including SAP PLM 7.0) Upgrade to SAP ERP 6.0 and include SAP enhancement package 4 for SAP ERP SAP PLM 4.0¹ and above SAP PLM 7.0 SAP CRM 4.0¹,² SAP CRM 7.0 Upgrade and above SAP SRM 3.0¹ Upgrade SAP SRM 7.0 and above SAP SCM 4.1¹ Upgrade SAP SCM 7.0 and above ¹ Direct upgrade from these source releases to the go-to releases of SAP Business Suite 7 is supported by SAP. ² If you upgrade from SAP CRM 4.0 or 5.0 to SAP CRM 7.0, customer-specific UIs (including the underlying UI-related coding) have to be migrated separately. ³ Besides the core applications, the SAP Business Suite provides also industry-specific applications (e.g. SAP Dealer Business Management, SAP Reinsurance Management) and cross-industry supplementary applications (e.g. SAP Portfolio and Project Management, SAP E-Sourcing). For these applications, the usual upgrade procedures apply. For an overview on the currently available and planned industry and supplementary applications, please refer to "SAP Release Strategy for Large Enterprises" on http://www.service.sap.com/releasestrategy© SAP 2009
  18. 18. Business Suite Upgrades 1 SAP Business Suite 7 - Overview: End-to-End Processes 2 Transition to SAP Business Suite 7 Technology Considerations A Upgrade per Application B Deploy further Applications© SAP 2009
  19. 19. Mandatory Components - 1 Scenario & Process Component List http://service.sap.com/scl© SAP 2009
  20. 20. Upgrade Dependencies - Evolution Path 2 Example: Implement “Lead to Cash” EXA MPL Selected Scenario E Current system landscape Goal: Customer implements value SAP R/3 Portal 7.0* SAP BW Portal 7.0* scenario “Lead to Cash” R/3 4.6C BW Server Server Required Steps ABAP ABAP 1. Install SAP Solution Manager 7.0. 2. Upgrade existing system landscape: Target system landscape - SAP R/3 4.6 C to SAP ECC 6.04. SAP ERP Portal 7.0* - SAP BW 3.5 to SAP Netweaver ECC Server ABAP Business Warehouse (BW) 7.01. SAP BW 3. Install and implement new components Portal 7.0* BW Server - SAP CRM 7.0 / NW7.01 - CRM ABAP Application Server ABAP. - SAP CRM 7.0 / NW7.01. - SAP SCM 7.0 - SCM Server.© SAP 2009
  21. 21. Deployment Options - SAP ERP/ 3 SAP ERP / PLM 7.0 Deployment PLM I: General Recommendation II: Reasonable Alternative Single System Scenario Layered PLM Deployment external internal Use Case Use Case Single System Scenario with SAP PLM 7.0 (PLMWUI and Product development with partners using external EHP 4) with PPM 5.0 (CPRXRPM) as Add-On. ("presentation only" mode) and internal ("data Project and portfolio management, design collaboration. persistency" mode) layers. Benefits Benefits Reduced TCO by shared use of infrastructure. Increased network security through separation of application servers. Reduced administration and operation effort. Intranet and extranet access controlled by authorizations Considerations inside internal application server. PLM scenarios running in SAP ECC Server might impact: Better scalability and load balancing capabilities. stability & performance. Considerations downtime for patching. Complex system landscape and higher TCO. Security.© SAP 2009
  22. 22. Deployment Options - 3 SAP SRM SAP SRM 7.0 Deployment I: General Recommendation II: Reasonable Alternative SRM Server Deployment Single System Scenario SAP SRM Server Use Case Use Case Centrally governed SAP SRM Server integrated to 1-n Single System Scenario with SAP SRM 7.0 (with EHP4 SAP ERP systems. and SRM_SERVER and SRM_EXT as Add On’s). Centralized procurement. Self-Service Procurement (classic Scenario), Temp. Labor Service Procurement, Supplier Self Service. Benefits Support different innovation cycles, individual availability. Benefits Separation of responsibilities (e.g. less alignment effort) . Reduced TCO by shared use of infrastructure and one organizational model. Independent scalability & performance. Master data distribution synchronously & bi-directional. Flexibility to change landscape layout. Considerations Considerations Functional Limitations, e.g. no extended classic Higher TCO. scenario, no multi backend deployment.© SAP 2009
  23. 23. Deployment Options - 3 SAP SCM SAP SCM 7.0 Deployment I: General Recommendation II: Reasonable Alternative SCM Server Deployment Single System Scenario Use Case Use Case Standalone, centrally governed SAP SCM Server. Single system scenario with EM and EWM Add-ons (with EHP3+ and SCM_BASIS, SCMEWM , SCEMSRV as Benefits Add On’s). Support different innovation cycles, individual availability. Event Management, Extended Warehouse Management, Separation of responsibilities (e.g. less alignment effort). planned: Transportation Management (SAP TM 8.0). Independent scalability & performance. Benefits Flexibility to change landscape layout. Reduced TCO by shared use of infrastructure. Full functionality available. Reduced administration and operation effort. Considerations Considerations Higher TCO. Functional limitations, e.g. no Supply Network Collaboration (SAP SNC) or Advanced Planner & Optimizer (SAP APO).© SAP 2009
  24. 24. Deployment Options - 3 SAP CRM SAP CRM 7.0 Deployment© SAP 2009
  25. 25. SAP NetWeaver Scenarios - 4 Deployment of SAP NetWeaver Portal General Recommendation General Recommendation Shared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite Shared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite application systems in the customer solution landscape. application systems in the customer solution landscape. SAP NetWeaver Portal is deployed as a separate system to support different innovation speed SAP NetWeaver Portal is deployed as a separate system to support different innovation speed and simplified landscape setups. and simplified landscape setups. Avoid embedded deployment of SAP NetWeaver Portal within the application system. Avoid embedded deployment of SAP NetWeaver Portal within the application system. Use Cases Central role-based access to different backend applications. Sharing central portal infrastructure for portal based applications. Benefits Centrally governed and administrated portal. Shared use of central SAP NetWeaver system to Central portal reduce administration effort. SRM Server Considerations Interoperability to connected application systems have to be checked. CRM Server Applications running in the portal might impact. stability & performance. downtime for patching.© SAP 2009
  26. 26. SAP NetWeaver Scenarios - Deployment of 4 SAP NetWeaver Business Warehouse General Recommendation General Recommendation Integrate, store, and manage company data from multiple connected data sources in a Integrate, store, and manage company data from multiple connected data sources in a central data warehouse system including central definition of all queries, web templates and central data warehouse system including central definition of all queries, web templates and enterprise reports. enterprise reports. Comprehensive set of planning and simulation capabilities with a simplified landscape setup. Comprehensive set of planning and simulation capabilities with a simplified landscape setup. Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated Implement SAP Netweaver Business Warehouse and Business Explorer Web capabilities on separated systems. systems. Use Cases Central Bex Web Integrate, store, and manage company data from multiple connected data sources in a central data warehouse system. Design and execute queries to analyze business information. Access analytic data based on web templates and enterprise reports. SRM Server Benefits Consolidated view of company wide reporting data. SAP BW Portal 7.0* Comprehensive Business Intelligence capabilities for planning and simulation. BW Server Reduced TCO by shared services and infrastructure. ABAP Highly scalable by separated technology stacks. SCM Server Considerations Central Data Warehouse Release & SP stack dependency between SAP Netweaver Business Warehouse and BEx Web² ² current planning: remove support package stack dependency with SAP NetWeaver 7.0 EHP2© SAP 2009
  27. 27. SAP NetWeaver Scenarios - Deployment of 4 SAP NetWeaver Process Integration General Recommendation General Recommendation Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as service enabling of the SAP Business Suite application systems. service enabling of the SAP Business Suite application systems. SAP NetWeaver Process Integration is deployed as a central, separate system to support SAP NetWeaver Process Integration is deployed as a central, separate system to support different innovation speed and simplified landscape setups. different innovation speed and simplified landscape setups. Avoid embedded deployment of SAP NetWeaver Process Integration within the application system. Avoid embedded deployment of SAP NetWeaver Process Integration within the application system. Use Cases Integration of A2A or B2B processes between SAP and Non-SAP systems. Service enablement of SAP and Non-SAP systems. Benefits Less complexity of system landscape. Central governance for meta data. Less effort by central maintaining of data for routing, mapping, connectivity, ccBPM, etc. Central PI Central responsibility for monitoring of services and processes. SCM Server Support of high volume scenarios, simplified modeling and configuration, enhanced standard support with SAP NetWeaver Process Integration 7.1.© SAP 2009
  28. 28. Resources (1/2) SAP Business Suite 7 Homepage: http://service.sap.com/businesssuite SAP CRM 7.0: http://service.sap.com/crm SAP PLM 7.0: http://service.sap.com/plm SAP SRM 7.0: http://service.sap.com/srm SAP SCM 7.0: http://service.sap.com/scm SAP ERP 6.0 – please see below SAP ERP Homepage: http://service.sap.com/erp Development news: http://service.sap.com/developmentnews Release notes: http://service.sap.com/releasenotes Release strategy: http://service.sap.com/releasestrategy Maintenance strategy: http://service.sap.com/maintenance Scenario & process component list: http://service.sap.com/scl SAP Enhancement Package Infocenter: http://service.sap.com/erp-ehp© SAP 2009
  29. 29. Resources (2/2) SAP Upgrade Info Center Homepage: http://service.sap.com/upgrade SAP ERP 6.0 Upgrade: http://service.sap.com/upgrade-erp SAP Upgrade Road Map: HTML Version SAP Upgrade Tools Upgrade Tools: http://service.sap.com/upgradetools System switch technology: http://service.sap.com/upgradetech SAP Solution Manager: http://service.sap.com/solutionmanager SAP Upgrade Services Overview and order information: http://service.sap.com/upgradeservices SAP Consulting upgrade services : http://service.sap.com/ufg SAP Netweaver Homepage: http://service.sap.com/netweaver SAP Netweaver administrator: http://service.sap.com/nwa System landscape directory: http://service.sap.com/sld Software lifecycle manager: http://service.sap.com/slm© SAP 2009
  30. 30. Transition to SAP Business Suite - Summary Target Key Technology Considerations Current Business Suite 7 Business scenarios in ONE application Upgrade per application SAP Appl. BS 7 Appl. 1 Complexity Drivers e.g. SAP e.g. EHP 4 Upgrade 2 Unicode R3 4.X A for SAP ERP 6.0 3 SAP Enhancement Packages Upgrade the respective application. Activate new functionality. 4 Upgrade Paths Business scenarios ACROSS applications Deploy further applications SAP Business Suite SAP Appl. NetWeaver Composition 1 Mandatory Components e.g. SAP Upgrade & Deploy Industry Applications 2 Upgrade Dependencies B R3 4.X SAP ERP SAP SRM SAP CRM SAP SCM SAP PLM Supplementary Applications EHP EHP NetWeaver Integration 3 Deployment Options Upgrade the respective applications. Deploy required additional applications. 4 SAP NetWeaver ScenariosSource: MOVE/GUO© SAP 2009

×