GAP Document Template

Name of the GAP Document

Project Team / Track ASAP Phase
Enter Project Enter Team Enter Phase –
Name Name Project Preparation
(Translation) or
Business Blueprint
GAP Title
Enter a short description of the GAP.
Process No. Process Name Process Type
Enter Process No. Enter the Process Indicate whether
Name the GAP relates to
a WY or SCM
business process.
CI Template Reference
Enter the name of the CI Template / Enter the document name
PRICE-BI Cross Reference
Enter the tab and line number on the PRICE-BI Inventory Spreadsheet
Key Participants
Enter name of key participants

Version Control
Date Author Revision Description Version

Definition Section:
GAP Definition
Describe the functionality deficit that exists between SAP and the Business Process Requirement. Ensure that the following
items are addressed:
 Detailed business requirements
 SAP’s existing capability
 Any comments that further explain the requirement driving the gap

Impact Section:
Business Benefit
Describe business benefit gained from closing the gap





Risk Impact
Describe business risks associated with this gap





Doc ID: Created By: author Date Created: 10/31/2005

/opt/scribd/conversion/tmp/scratch6584/48474580.d Page: 1 of 4
Approved By: approver Date Approved :10/31/2005
oc
 GAP Document Template
Name of the GAP Document

Alternatives Section:
Options
Provide the short list of options considered.
 Option 1
 Option 2
 Manual Option / Workaround
 Do Nothing (as there is always an option to not fill the gap)

Option 1– Details / Advantages / Disadvantages

For each option:
 Describe the option in detail.
 Provide a bulleted list of key advantages.
 Provide a bulleted list of key disadvantages.

Option 2– Details / Advantages / Disadvantages

For each option:
 Describe the option in detail.
 Provide a bulleted list of key advantages.
 Provide a bulleted list of key disadvantages.

Option n – create as needed

For each option:
 Describe the option in detail.
 Provide a bulleted list of key advantages.
 Provide a bulleted list of key disadvantages.

Consideration items for selection

Document the criteria for selecting a recommend solution:
 Criteria #1
 Criteria #2
 Etc

Recommendation
Document the recommended option.
 Ensure that the supporting documentation in the GAP is consistent with the recommendation.

Resolution Section:
Resolution
Describe the final resolution agreed by the Project Team and the Business.
 Identify any changes or variations to the section above.

Date
Document the date the decision was made

Decision Makers
List the decision makers involved in this resolution:
 Must include the E2E Integration Team Lead, Business Solution Lead.

Email Attachment
Attach a copy of the email with all approvals.

Doc ID: Created By: author Date Created: 10/31/2005

/opt/scribd/conversion/tmp/scratch6584/48474580.d Page: 2 of 4
Approved By: approver Date Approved :10/31/2005
oc
 GAP Document Template
Name of the GAP Document

Doc ID: Created By: author Date Created: 10/31/2005

/opt/scribd/conversion/tmp/scratch6584/48474580.d Page: 3 of 4
Approved By: approver Date Approved :10/31/2005
oc
 GAP Document Template
Name of the GAP Document
Cross Integration Impacts
Deployment Considerations
List any specific considerations to be taken into account when developing the resolution:
• Impact on Weyerhaeuser enterprise wide business processes.
• Impact on individual business processes.
• Identify businesses, end user groups, user counts
• Changes to the existing organization
• Training and education considerations

Configuration Considerations
List any specific considerations to be taken into account when developing the resolution:
• Identify impacts on SAP Organizational Structures and Master Data.
• Identify impacts on non-SAP systems.

Data Considerations
List any specific considerations to be taken into account when developing the resolution:
• Ensure that the Enterprise Data Management Team are involved in the process of identify and evaluating options.
• Data cleansing, conversions, cutover activities, business resumption and data synchronization procedures.
• Ensure that SAP and non-SAP systems are considered.

Business Intelligence Considerations

List any specific considerations to be taken into account when developing the resolution:

Other
List any other considerations to be taken into account when developing the resolution

Technical Considerations
Technical Infrastructure
List any specific considerations to be taken into account when developing the resolution:
 SAP R/3, SAP BI. Portals, support packages, upgrades, bolt-on, new dimension products, Industry Solutions.
 Non-SAP systems.

Integration Services
 List any specific considerations to be taken into account when developing the resolution

IT Legacy Systems
List any specific considerations to be taken into account when developing the resolution:
 Identify key LOB systems.

Internal Controls
Business and Audit Controls
List any specific considerations to be taken into account when developing the resolution:
• Identify the key audit and business controls.
• Identify any special end user role considerations.

Doc ID: Created By: author Date Created: 10/31/2005

/opt/scribd/conversion/tmp/scratch6584/48474580.d Page: 4 of 4
Approved By: approver Date Approved :10/31/2005
oc