ECC Vs HANA Flashcards
Changes in HANA wrt master data
1) Customer Master, Vendor Master, contact person, Credit Master have been converted to BP (Business Partner) and the BP role will
differentiate whether it’s a Vendor or customer or Contact person….Etc
2) The access number in access sequence has been increased
3) Document pricing procedure and customer pricing procedure length has been increased from 1 to 2 digits
4) Document category length has been increased from 1 to 4
5) The material number length increased from 18 to 40 digits
6) Credit Management concept has been moved from FI Credit management to FSCM
7) The traditional Foreign Trade Functionality in SD and MM is moved to GTS
8) Rebate Process has been moved to “Settlement Management” or “Condition Contract
Management” (CCM)
9) Output Determination has been moved from NACE to BRF+
10) Transportation Management TM is used instead of Shipment in LE
11) SAP Revenue Accounting replaces ERP SD Revenue Recognition
12) SAP ERP transaction codes such as XD01 or VD01, XK01, MK01 are not available anymore in SAP S/4HANA
Differences between ECC & HANA
- Database: ECC supports databases from other providers such as Db2, Oracle, or Informix, however, S/4HANA only runs on SAP HANA. As a result, S/4HANA has much faster reaction times thanks to its in-memory database.
- A merger of controlling (CO) and finance (FI): When it comes to the merger of controlling (CO) and finance (FI), SAP S4 HANA’s structure of the universal journal stores both the GL account and the cost element, vs ECC where the FI GL accounts are mapped to CO primary cost elements.
- New general ledger: S/4HANA also only uses the new general ledger (GI), while ECC ran both “new” and “classic” versions.
- Customer vs. Vendor to business partner: In ECC, customer and vendor files were separate, while S/4HANA combines the common data structure elements of both into a Business Partner record.
- Rebates: S/4 HANA has replaced the SD rebate processing in ECC with settlement management through condition contracts.
Greenfield approach - new implementation
-> Complete reengineering of your SAP ERP
-> Starting from a clean slate
-> Any customization you’ve done on SAP ECC will be completely wiped out
-> Can be done on-premise or in the cloud,
-> Transformation begins with a new system, providing the flexibility to drive such topics as standardization and simplification along with the migration itself.
-> “selective Greenfield.” start with a blank slate in some areas to take the opportunity to simplify processes, integrations, and custom code.
Brownfield approach - system conversion
-> Brownfield approach is more like an upgrade
-> Can get SAP S/4HANA up and running, and at the same time, migrate your existing SAP workflows and systems over to the newest version of SAP S/4HANA
-> Shorter project runtime, and therefore there’s less disruption to your business.
-> Brownfield implementation is best-done on-premise
What is the primary motivation behind migrating from ECC to S/4HANA?
leverage the latest digital innovations, real-time analytics, and simplified data model offered by S/4HANA to drive business agility, efficiency, and competitiveness.
What are the key differences between ECC and S/4HANA?
S/4HANA is built on SAP’s in-memory database (HANA), offers a simplified data model, supports real-time analytics, and leverages modern technologies like Fiori UX and machine learning. ECC is based on a traditional database and has a more complex data model.
What are the deployment options for S/4HANA?
S/4HANA can be deployed on-premises, in
the cloud (public or private), or in a hybrid model
What is the Brownfield approach to S/4HANA migration?
The Brownfield approach involves migrating the existing ECC system to S/4HANA while retaining custom code, data, and configurations. This approach minimizes disruption but may require extensive testing and remediation.
What is the Greenfield approach to S/4HANA migration?
The Greenfield approach involves implementing a new, fresh S/4HANA system and migrating only the necessary data from the ECC system. This approach provides a clean slate but requires more effort in data migration and process re-implementation.
What are the key considerations for choosing between Brownfield and Greenfield migration?
Considerations include the complexity of the existing ECC system, the extent of custom code and modifications, the organization’s appetite for change, and the desired level of process optimization and standardization.
What is the Selective Data Transition approach?
The Selective Data Transition approach involves migrating only the relevant and necessary data from the ECC system to S/4HANA, leaving behind historical or obsolete data. This approach can simplify the migration process but may require additional data archiving and reporting solutions.
What is the role of the Maintenance Planner in an S/4HANA migration project?
The Maintenance Planner is a tool provided by SAP to analyze the existing ECC system, identify potential issues or incompatibilities, and provide recommendations for the migration process.
What is the Simplification List, and why is it important?
The Simplification List is a comprehensive document provided by SAP that outlines the changes, simplifications, and potential impact on existing functionality when migrating to S/4HANA. It is essential for planning and managing the migration process effectively.
What is the role of the Custom Code Remediation process in an S/4HANA migration?
Custom code remediation involves analyzing, testing, and adapting existing custom code to ensure compatibility with the S/4HANA environment. This process is crucial to maintain functional parity and minimize disruption during the migration.
What is the Business Process Redesign (BPR) approach in an S/4HANA migration?
The BPR approach involves reviewing and optimizing existing business processes to leverage the new capabilities and best practices offered by S/4HANA. This approach can drive significant process improvements but may require extensive change management efforts.
