Detailed Definition of Enhancements
Task Notes
- Create a detailed description for each system enhancement.
To do this,
you:
- Work with, and if necessary add to, the results of the work you did in the Define interfaces and enhancements activity in the Define functions and processes work package. These results are in the Shared -> 7.ENHANCMNT folder;
- Define what SAP standard data is needed at what time;
- Define what additional data is needed at what time;
- Determine where that data comes from;
- Define any new data fields, tables, etc., that have to be created in the R/3 System for the system enhancements;
- Document which standard processes will be influenced by the enhancements;
- Determine the effort and expense to create your enhancements
- Have enhancement designs approved.
This should be done
in accordance with the standards for approving enhancements: refer to the
project standards and procedures activity in the Project
preparation work package.
Additional information
- Software enhancements using user exits
The R/3 standard
software already contains user exits. They are provided without content for
individual activation and use by customers. User exits are placeholders in the
original code that can be filled with customer logic. This is the simple,
secure and inexpensive way to enhance the functionality of SAP's standard
software. It avoids unmanaged and uncoordinated intervention in the standard
software. User exits are customer-specific configurations that are not changed
by a new release. This avoids additional cost of subsequent
maintenance.
The different types
of user exit are:
- function exits (CALL CUSTOMER FUNCTION)
- menu exits
- screen exits
- keyword exits
You have
context-sensitive access to user exits from your Project IMG. You can also
open a list of available enhancements from the ABAP/4 Development Workbench by
choosing Utilities -> Enhancements -> Project management. From there,
choose Utilities -> SAP enhancements to open a selection list and find
exits available in a standard application.
- Enhancement of the standard software by customer development
Use the R/3 ABAP/4
Development Workbench to develop and maintain your own objects, such as
reports, tables, module pools and screens. You should comply with the
conventions on customer name ranges. New objects of this kind are
release-compatible, that is to say they are generally not affected by a change
of release and do not need to be changed to work with a new
release.
- Modifications to the R/3 System
It is not always
possible to avoid having to make modifications. Find out about the following
from the R/3 documentation before you make modifications:
- name conventions
- the SAP Software Change Registration procedure
- Workbench Organizer -> Modification support.
Observe the
standards for carrying out modifications. Refer to the
project standards and procedures activity in the "Project
preparation" work package.
- If you are planning extensive enhancements and
want to manage their creation, you can add suitable project activities to the
R/3 Procedure Model. They should be inserted into Phase 2: Detailed design and
system set-up, as subnodes of the corresponding activities in the
Create Interfaces and Enhancements work package.