Sei sulla pagina 1di 6

SAP CONFIGURATION RATIONALE

SAP
Configuration Rationale
Document Reference:
Title:

Business Owner:

Functional Author:

Overview

Page 1 of 6
SAP CONFIGURATION RATIONALE

Contents

PRODUCT HISTORY 3
Document Location 3

Revision History 3

Functional Quality Review 3

Functional Approval 3

1.0 REQUIREMENTS SUMMARY 4


1.1 Overview 4

1.2 Scope 4

1.3 Assumptions 4

1.4 Dependencies and Constraints 4

1.5 Timing 4

1.6 Issues 4

1.7 Risks 4

2.0 CONFIGURATION SPECIFICATION 5


2.1 Enter IMG Configuration Activity e.g. Document Type Purchase Order 5

2.2 Enter IMG Configuration Activity e.g. Document Type Purchase Order 6

Page 2 of 6
SAP CONFIGURATION RATIONALE

Product History

Document Location
The electronic source of the document can be found on:
/conversion/tmp/scratch/422811363.doc

Revision History
Version Revision date Summary of Changes Section Page

Functional Quality Review


The following people have been nominated as quality reviewers for this product:
Name Title Date of Issue Versions

Functional Approval
This document requires functional approval from the following people:
Name Role Date Signature

Page 3 of 6
SAP CONFIGURATION RATIONALE

1.0 Requirements Summary

1.1 Overview

This section should give a high level description of the change request and the business requirement
that will be addressed

1.2 Scope

This section should detail elements specifically included and excluded from the scope of this
document

1.3 Assumptions

This section describes any assumptions that have been made in completing the document:

1.4 Dependencies and Constraints

This section identifies any dependencies and constraints in developing and implementing the change

1.5 Timing

This section identifies when the change is required for and the significance of the date

1.6 Issues

This section identifies any issues that have been identified associated with the change

1.7 Risks

This section identifies any risks that have been identified associated with the change

Page 4 of 6
SAP CONFIGURATION RATIONALE

2.0Configuration Specification
Example: Purchase Order Document Type

2.1 Enter IMG Configuration Activity e.g. Document Type Purchase


Order

SAP Module: Materials Management

IMG Path: Materials ManagementPurchasingPurchase


OrderDefine Document Type

SAP Transaction Code: OMEC

Overview:

The SAP System manages purchase orders (POs) as documents. You can group POs together to
form any number of document types.

In this step, you can do the following:


 Create new document types
 Define item interval
 Define allowed follow-on document types
 Assign document types to a number range group
 Define a number range interval
 Choose type of number assignment:
o Internal
o External
 Choose update group
The update group determines how the data from the document header is updated in the
statistics file.

Rationale:
Explain reasons why configuration settings below were used

Configuration Settings:
o Provide details of setting configured in SAP – use screen prints as required.

Page 5 of 6
SAP CONFIGURATION RATIONALE

2.2 Enter IMG Configuration Activity e.g. Document Type Purchase


Order

SAP Module: Materials Management

IMG Path: Materials ManagementPurchasingPurchase


OrderDefine Document Type

SAP Transaction Code: OMEC

Overview:

The SAP System manages purchase orders (POs) as documents. You can group POs together to
form any number of document types.

In this step, you can do the following:


 Create new document types
 Define item interval
 Define allowed follow-on document types
 Assign document types to a number range group
 Define a number range interval
 Choose type of number assignment:
o Internal
o External
 Choose update group
The update group determines how the data from the document header is updated in the
statistics file.

Rationale:
Explain reasons why configuration settings below were used

Configuration Settings:
o Provide details of setting configured in SAP – use screen prints as required.

Page 6 of 6