ASAP (Accelerated SAP) project implementation cover several phase such as:
Phase 1: Project Preparation
Phase 2: Business Blueprint
Phase 3: Realization
Phase 4: Final Preparation
Phase 5: Go-Live and Support
below detail checklist and step by step for ASAP implementation
Popularity: 73% [?]
Checklist and Step by Step template for SAP Governance Risk Control Implementation Toolkit
1. Document the control environment. What are you doing? What are your processes? Where are the risks?
2. Test: Implement the process and access controls needed to address the risks identified.
3. Remediate: Resolve exceptions found by the controls.
4. Analyze: Use the information gathered to gain a deeper understanding of the business.
5. Optimize: Improve both GRC and business processes as insights are gathered.
Popularity: 12% [?]
Scenario testing is the testing of chains of SAP transactions that make up a process within a single area or module. Scenario testing includes testing of a process with data from external systems and applicable SAP roles/profiles. Scenario testing is primarily a manual effort but can include some partial automation with test tools for processes that are stable, frozen, and proven to have worked manually. The scenario testing is owned by the configuration teams but includes participation from SMEs and members of the test team and development team.
Integration testing is the testing of chains of SAP transactions that make up an end-to-end process that cuts across multiple modules, for instance, order-to-cash, purchase-to-pay, and hire-to-retire with external data and converted data. Integration testing (more…)
Popularity: 13% [?]
Development testing is the testing for reports, interfaces, conversions, enhancements, work flows, and forms (RICEWF) development objects developed primarily with ABAP code. Testing of development objects includes testing for security authorizations, performance, extracts, data transfer rules, reconciliations, and batch scheduling jobs. In many SAP projects, third-party tools such as Control-M and AutoSys are acquired to schedule reports and interfaces with dependencies, and these scheduled jobs need to be tested prior to releasing the system into the production environment. Development testing should also ensure that data can be tested through the intended target system. The owner(s) of the target system can specify the applicable or representative sets of data needed to test interfaces and conversions, which allows the development or ABAP team to conduct white box and black box testing on ABAP programs. (more…)
Popularity: 8% [?]
