ASAP 8 Methodology Business Process Management Work Stream Quiz

You do not need to observe any specific order.

1. General Settings. 2. Business Processes. 3. Organisational Structure.

1. Business Processes. 2. Organisational Structure. 3. General Settings.

1. General Settings. 2. Organisational Structure. 3. Business Processes.

1. Business Process. 2. General Settings. 3. Organisational Structure.

Business Process Unit and String Test Case template

Business Scenario Design Document template

Organizational Structure Requirements and Design template

Test plans for the Baseline system

Functional Specification template

Provide project standards, documentation templates and work procedures for BPM activities (with or without usage of SAP Solution Manager).

Ensure access to and usage of the Business Process Repository (SAP reference content).

Define the business processes functional and technical specifications and document these, finally delivering the Business Blueprint document.

Map the Business Process Design to SAP Best Practices, Own Practice, the Business Process Repository and Best Insight.

Ensure integration work of BPM-team to other work stream teams to ensure knowledge transfer

The purpose of the business process map is to derive and agree on the scope for the start of the business blueprint phase and thus a deliverable of the project preparation phase.

As a result of the work in project preparation the Business Process Map should be finalized on scenario level and have drafted content on process level - to be finalised during blueprinting.

The accelerator "Business Requirements - Template" is one of the important documents to use in parallel to creating the business process map.

During blueprinting the business process map is refined and becomes the foundation for the process hierarchy.

The business process map serves as a framework for process modelling and helps manage process scope. It also serves as an important point of reference for further process modelling and deep-dive sessions.

Each RICEFW object needs to be documented via a technical specification after the object has been built. Test documentation must be included.

Technical specifications should be associated in SAP Solution Manager at the process level, or process step level, as appropriate. Technical specifications can also be consolidated under a dedicated node in the process hierarchy of SAP Solution Manager.

The purpose of the solution gaps and core enhancements deliverable is to develop the RICEFW objects: Reports, Integrations, Controversies, Engagements, Formulas & Work-Outs.

"Final Code Review" is not a task related to the deliverable "Enhancement Development - RICEFW Object #1 - n" but part of the work stream Technical Solution Management.

The purpose of the Enhancement Development - RICEFW Object #1 - n deliverable is to develop the RICEFW objects: Reports, Interfaces, Conversions, Enhancements, Forms & Workflows.

All business processes are documented using only the Business Scenario and Design template.

Project team members take part in Level 2 training.

The Business Blueprint generated in the ASAP Q&A database includes the business processes that have been set in scope, and the related documentation from the CPI template. The answers provided to the business process questions can be included in this document.

When using SAP Solution Manager for process-related documentation the final Business Blueprint document will be generated and stored in SAP Solution Manager.

The scope of business processes defined in the Business Blueprint has the same structure as the project IMG.

...thoroughly documents the current as-is business processes of the client.

...is a detailed process-orientated and technical documentation of the results gathered during requirements and design workshops.

...consists of multiple documents illustrating how the company intends to run its business using SAP solutions.

...identifies the specific order in which to configure the customer's SAP System.

...is subject for formal approval and sign-off by the customer project stakeholders.

The core configuration relates to the process configuration activities for standard SAP processes.

Core configuration should be done by customer project resources whereas Delta configuration is always completed by certified SAP consultant resources.

The purpose of the task 'Complete Core Configuration' is to implement the core configuration, write valid test cases and to document this in Solution Manager.

The purpose of core configuration is to ensure that exceptions and critical processes are configured first regardless of the complexity of system settings.

The purpose of the 'Delta Configuration' deliverable is to ensure that the configuration associated with bridging solution gaps is implemented, tested and documented.

The Business Scenario Design template helps to document Level 1 & 2 aspects regarding the Business Scenario, Values drivers and KPIs, organisational scope and impact and the functional process design.

After each workshop, the business scenarios must be documented in order to use them within the business process requirements workshops.

The inputs for the Business Scenario Design include among others: Value Maps (if available), Process Maps and Project Scope Statement.

The following roles participate during those workshops: Business Process Owner, Business Process Team Member, Solution Consultant, Project Sponsor and Integration Manager.

The purpose of the Business Scenario Design is to provide an understanding of the essential processes at scenario level (process level 1-2) and it builds the foundation to define the process levels 3-5.

Define General Settings and Master Data

Business Transactions Catalogue

Define Logical Data Model

Define Business Organisation Structure

Define User Role Concept

Technical specification documents per development object are completed and documented in SAP Solution Manager.

Approved business blueprint document (signed and approved by project sponsor). As a consequence, SAP and Customer Project Managers can smooth the change control.

Functional specification documents are completed defining development requirements for the workflows, reports, interfaces, conversions, enhancements and forms (RICEFWs)

Completed gap analysis identifying the business process requirements that are not provided with standard SAP functionality.

Approved business blueprint document (signed by the project sponsor).

Assure availability of qualified workers for business performance monitoring.

Design a strategy to balance and monitor data volumes in the productive system.

Design a strategy and process for set-up and monitoring of automated background tasks.

Balance workload between organisations in the business.