1
ASAP IMPLEMENTATION
METHODOLOGY
How to use the Template
Blue text is always intended as instructions, guidelines, explanations, hints, and tips. It has to be removed when the
document is finalized. To provide a consistent representation of this document to the customer, chapters should not
be deleted or inserted. Required additions should be made as sub-chapters to existing chapters.
Chapters that are not relevant should be marked as such (that is, add “not relevant” or “not applicable”).
Be sure to delete these instructions when you have finished!
CONFIGURATION REFERENCE
TEMPLATE
NAME OF CONFIGURATION AREA
PROJECT IDENTIFICATION
Delete Project Identification table if not applicable for the document!
Project Name CPI Project Number
<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>
Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Confidential
2
REVIEW AND APPROVAL
Delete Review and Approval section below if not applicable for the document!
Name Date (YYYY-MM-DD)
Customer Project Manager
Name Date (YYYY-MM-DD)
SAP Project Manager
Name Date (YYYY-MM-DD)
Key Stakeholder
Name Date (YYYY-MM-DD)
Key Stakeholder
3
TABLE OF CONTENT
Scope............................................................................................................................................................... 4
Project Header................................................................................................................................................ 4
Document Revision History........................................................................................................................... 4
Business Requirements................................................................................................................................. 4
Configuration Rationale................................................................................................................................. 4
Technical Requirements................................................................................................................................ 5
Business Rules or Data Requirements............................................................................................................. 5
Programming or Configuration Logic................................................................................................................ 5
Configuration.................................................................................................................................................. 6
Client (Server Name) SAP Easy Access Menu................................................................................................ 6
Name Configuration Area (1)............................................................................................................................ 7
Name Configuration Area (2)............................................................................................................................ 7
Name Configuration Area (As Many As Needed....).........................................................................................7
Integration Points with other Modules/Other Systems...............................................................................7
Name of Module, Area or data stream)............................................................................................................. 7
(Name of Module, Area or data stream)........................................................................................................... 8
REPORTING.................................................................................................................................................... 8
Business Requirements:................................................................................................................................... 8
Reporting Requirements................................................................................................................................... 8
Job Scheduling Requirements.......................................................................................................................... 9
TESTING.......................................................................................................................................................... 9
Testing Consideration / Assumptions............................................................................................................... 9
Test Scenarios Identified.................................................................................................................................. 9
Unit / Integration Testing................................................................................................................................... 9
User Acceptance Testing............................................................................................................................. 10
4
SCOPE
Describe the basic purpose and scope of configuration. Describe the functionality that will result
from the configuration.
PROJECT HEADER
Date of Request: 00/00/00
Change Initiator: Name
Department: X
Business Priority: High, Medium, Low, On Hold
Business Owner: Name
Module/ SAP Area: Module/Area
IS Resource(s): Name, Name, Name
Program names: Reports/ Jobs
Triggers/Interfaces: On-line
System Objects: Batch
Transaction Codes:
DOCUMENT REVISION HISTORY
Date Version Revision Description Issue # Process Author
(Projects Flow
Only) Verified
00/00/00 1.0 Initial Document Name
BUSINESS REQUIREMENTS
Describe the business requirements in brief language. If necessary reference the relevant
Business Process document, and where it may be found. The requirements should describe at
minimum, the required functionality, limiting factors and expected performance.
5
CONFIGURATION RATIONALE
Describe how the configuration will support the business requirement, integration points,
dependencies on other configuration, and why the IMG objects are being configured per the
documentation. If necessary reference supporting documentation, process flows, or other
applicable documentation.
■ Narrative description of the configuration and how it supports the business requirement
■ Configuration Dependencies
■ Integration Points with other configuration
■ References/Supporting Documentation used to determine configuration rationale
TECHNICAL REQUIREMENTS
Business Rules or Data Requirements
■ Describe in concise language the technical and data requirements. Use short sentences,
and separate ideas with bullet points.
■ Business rules indicate how data will be manipulated; Data requirements inventory which
data will be required and with what frequency.
Programming or Configuration Logic
(Figure 1: Name of Process)
Illustrate in simple flow chart the basic elements of the process and their flow toward the intended result.
Describe relation of business requirements to the process.
(Figure 2: Name of Process)
Illustrate in any signature behaviours in the data or business rules that must be taken into account; for
example volume of transactions over time.
Describe relation of trends or signature behaviors to business requirements and the process.
*Note any special settings required by trends or signature behaviors.
Example:
(Figure 3: Annotated Screen Shot of location of special settings)
6
Process Model (place model of process from Visio or Solution Manager or Aris)
Process XYZ
XYZ SERVER
CONFIGURATION
Client (Server Name) SAP Easy Access Menu
Changes are performed in (Transaction Pathway)
7
Transaction XXX_XXX_XXXXXXXX
Menu Path: SAP Easy Access X X X X
Transaction XXX_XXX_XXXXXXXX
Menu Path: SAP Easy Access X X X X
Transaction XXX_XXX_XXXXXXXX
Menu Path: SAP Easy Access X X X X
Transaction XXX_XXX_XXXXXXXX
Menu Path: SAP Easy Access X X X X
Transaction XXX_XXX_XXXXXXXX
Menu Path: SAP Easy Access X X X X
Figure 4: Screen Shot Showing Access from SAP Easy Access Menu
Name Configuration Area (1)
Describe which settings to apply. Note important deactivations, values and indicators to be checked.
Figure 5: Screen Shot Showing correctly configured object
Name Configuration Area (2)
Describe which settings to apply. Note important deactivations, values and indicators to be checked.
Figure 6: Screen Shot Showing correctly configured object
Name Configuration Area (As Many As Needed....)
Describe which settings to apply. Note important deactivations, values and indicators to be checked.
Figure 7: Screen Shot Showing correctly configured object
INTEGRATION POINTS WITH OTHER MODULES/OTHER SYSTEMS
Name of Module, Area or data stream)
Describe point of intersection between current configuration and other processes affected or leveraged by it.
Name: (Name of Document)
Documentation Type: (Doc. Type, from Solution Manager)
Status: (0%, 25%, 50%, 90% 100%)
Attach Descriptive Document (Do not use links)
Name: (Name of Document)
Documentation Type: (Doc. Type, from Solution Manager)
8
Status: (0%, 25%, 50%, 90% 100%)
Attach Descriptive Document (Do not use links)
(Name of Module, Area or data stream)
Describe point of intersection between current configuration and other processes affected or leveraged by it.
Name: (Name of Document)
Documentation Type: (Doc. Type, from Solution Manager)
Status: (0%, 25%, 50%, 90% 100%)
Attach Descriptive Document (Do not use links)
Name: (Name of Document)
Documentation Type: (Doc. Type, from Solution Manager)
Status: (0%, 25%, 50%, 90% 100%)
Attach Descriptive Document (Do not use links)
REPORTING
Figure 8: Process Model Illustrating Generation of Reports and Processes Involved
Business Requirements:
Describe any business requirements that will current reports.
Table Name: XXX_XXX_XXXX
Table Name: WFMCAS_AGT_WRKAR
Job Name Table Name Function Change Department/ Recovery/Escalation
Business Owner Process
<Need XXX_XXX_XX Describe Describe Department <Need Information>
Information> X Function Change Name
<Need XXX_XXX_XX Describe Describe Department <Need Information>
Information> X Function Change Name
Reporting Requirements
Describe any changes to reports or impacts of configuration on current reports.
Headers for the Report, Screen Layout
List all the column headers, row headers, sub-total headers and other fixed format that should be used for
the report. (Business Define)
Sort Options, Selection Parameters, Filters
If the report must be sorted in multiple sort orders, list all the unique sort orders here. Include any sub-total
requirements that will dependent on each sort order.
9
SAP Technical Fields Names and Program Logic
For each column and row, enter the technical SAP fields names. The business process person and the
technical developer will need to work together to find these names. The technical field names from the
screens in SAP may not be actual table names because the screen values are from structure. The
developer can help the business process person find the actual table names.
Tables, Transactions, Batch Jobs
List all transactions and batch jobs that will be using the Report. Without this information, the technical
team will not be able to validate that the Report works for accesses to the business procedure.
Job Scheduling Requirements
Job Name Program Variant Frequency/ Department/ Business Recovery/Escalation
Name Time Owner Process
TESTING
Testing Consideration / Assumptions
Define:
Specific IDs to be used
Data Requirements for testing
Test Scenarios Identified
Define:
Known testing scenarios at this time, regression testing
Unit / Integration Testing
Environment:
Test Scenario:
Date of Test:
Resource(s):
Step Action Data Input Expected Results Actual Results / Pass / Resolution
Documents Fail
1
2
3
4
5
Environment:
Test Scenario:
Date of Test:
10
Resource(s):
Step Action Data Input Expected Results Actual Results / Pass / Resolution
Documents Fail
1
2
3
4
5
USER ACCEPTANCE TESTING
Environment:
Test Scenario:
Date of Test:
Resource(s):
Step Action Data Input Expected Results Actual Results / Pass / Resolution
Documents Fail
1
2
3
4
5
