Database Reference
In-Depth Information
13.2.3.5.3 Perform Baseline Confirmation
In ASAP, this task is the third important milestone of the project.
This task has the responsibility to formulate confirmation scenarios that could be enacted into the
system to verify the successful configuration of the system. This involves the following subtasks:
1. Confirmation Scenarios.
A confirmation scenario (or Process Group) corresponds to a complete business or an end-
to-end scenario. It can be subdivided into business cases that make it easier to confirm the
complete scenario in incremental steps. A business case includes the critical information
flow, associated conditions, and exceptions.
Compiling a Confirmation Scenario involves the following:
Choose the Baseline Confirmation Plan document and select the Baseline worksheet.
Set the confirmation and sequencing information for dependent processes; this can be
done by entering a case number and a sequence number to a group of related processes
in the subcolumns of Confirmation: Case and Sequence No.
Add information on confirmation procedures by selecting the Case Procedure form, and
add details.
Save.
2. Prepare Confirmation Scenarios agenda by the cross functional process owners, and assign
participants.
3. Perform Baseline Confirmation Session.
4. Review and sign off Baseline Confirmation.
13.2.3.6 Perform Final Configuration and Confirmation
As referred in the beginning of Section 13.2.3.5 “Baseline Configuration and Confirmation,” all
scenarios and business processes that are not included in the Baseline Scope are handled during
this task. These are the configuration cycles that were mentioned in Section 13.2.2.5.2 “Prepare
Business Blueprint.”
To make the configuration effort easier, ASAP recommends the formation of a series of con-
figuration cycles consisting of a selected set of business processes depending on the degree of their
importance. These are the configuration cycles that were mentioned in Section 13.2.2.5.2 “Prepare
Business Blueprint.” The cycles are configured sequentially till all issues are resolved and the con-
figured system is ready to be delivered for final integration tests.
A cycle represents an iterative process that systematizes the final configuration effort. The
cycles are defined based on the following guidelines:
Cycle 1 : The purpose of this cycle is to tune the configuration of the business processes for
the master data and high-priority transactions.
Cycle 2 : The purpose of this cycle is to tune the configuration of the remaining master data
and basic transactions.
 
Search WWH ::




Custom Search