0% found this document useful (0 votes)
242 views

SAP ABAP Enhancements

The document discusses different techniques for enhancing SAP systems including customizing, modification, enhancement, and custom development. It describes change levels in SAP and various enhancement options like dictionary enhancements, program enhancements using customer exits, business add-ins, and the enhancement framework.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
242 views

SAP ABAP Enhancements

The document discusses different techniques for enhancing SAP systems including customizing, modification, enhancement, and custom development. It describes change levels in SAP and various enhancement options like dictionary enhancements, program enhancements using customer exits, business add-ins, and the enhancement framework.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 70

Enhancements & Modifications

Objective

– Change Levels in SAP


– Enhancements Techniques
– Enhancement Framework
– Modification Tools
Change Levels in SAP
Change Levels in SAP
 Customizing: Configuration of system parameters
via a special user interface, the possible changes
are pre planned and organized. Customizing is
required during implementation of the system.
 Modification: Alteration of SAP Repository objects
in the form of custom changes when SAP changes
occur, the customer version and the new SAP
version must be reconciled manually.
Change Levels in SAP
 Enhancement: Changing of SAP Repository objects
by the customer without modification.
 Custom development: Creation of custom objects
within the customer name range.
Modification and Customer development involve
high maintenance and costs. Hence use these only
when customer requirements are not met by
customizing or by user exits.
Enhancements Change Levels in SAP

Advantages of Enhancements
 There are two main reasons why you should use
exits rather than modifying SAP software
Add-ons attached to exits have the advantage that:
 They do not affect standard SAP source code.
 They do not affect software updates.

Enhancements can be achieved by Exits.


Enhancement Options:

SAP CUSTOMER

Defines Uses
Enhancement Options:

– Dictionary Enhancements
– Text Enhancement
– Table Enhancement
– Program Enhancements
– Customer Exits
– Business Add In
– BTE
– Enhancement Framework
Dictionary Enhancements

– Text Enhancement:
– Field Description
– Field Documentation

CMOD -> Goto -> Text_Enhancement


Dictionary Enhancements

Table Enhancement:
– APPEND Structure:
Customers can add new fields to an SAP table by
creating an Append Structure
Dictionary Enhancements

Table Enhancement:
– Customizing Includes:
A predefined empty structure provided by SAP within
tables [CI_Structure] and customer can add new fields in
them
Program Enhancements

Represent potential customer requirements that have


not been developed in the standard. Instead, the
standard provides for further development of such exits
at the customer site, using logic specific to the customer

• It can be done using


– Customer Exits
– Business ADD-Ins
– BTE
SAP Application Enhancements
Customer Enhancements Projects
Enhancements and Enhancements Project

SAP
E Enhancements C Components
The SAP Enhancement Creation Procedure
Procedure at the Customer’s Premises
Creating Customer Enhancement Project

Name of Enhancement Project

Create
Assigning SAP Enhancements
Assigning SAP Enhancements to Customer
Projects

Project Management of SAP Enhancements Name of the enhancement project

Project Create Create


Sub-objects
Attributes Manage Attributes
Enhancement assignment
Components
Documentation

Display Change SAP Enhancements in Project

Enhancement Description

•Transaction Code: CMOD

 SAP AG 1999
Editing Components

Function module

Menu

Screen Painter

Change
Activate Enhancement Project

Activation

Deactivate
Transporting Projects
Customer Exits : Function Module Exit

Function Module Exit

Menu Exit

Screen Exit
Program Exits Overview
Function Module Exit: Process Flow
Calling and Creating Function Module
Finding Function Module Exits

Application hierarchy

Repository Info. System

IMG

Documentation
Editing Function Module Exits
Enhancements Step1
Enhancements Step2
Enhancements Step3
Enhancements Step4
Enhancements Step5

Activate Project !
Structure of a Function Group
Structure of an Exit Function Group
Exit Function Group: Global Data
Customer Source Code
Exit Function Group:
Exit Function Group:
Customer Screens
Summary: Function Module Exits
Customer Exits : Menu Exit

Function Module Exit

Menu Exit

Screen Exit
Menu Exits Overview
Menu Exit Requirements
Editing Menu Exits
Enhancements Step1
Enhancements Step2
Enhancements Step3
Enhancements Step4
Enhancements Step4
Menu Exits and Function Module Exits

Activate Project !
Summary: Menu Exits
Function Module Exit

Menu Exit

Screen Exit
Screen Exits overview
Subscreens in the R/3 System

abcd
Calling a Normal Subscreen
• Flow control of the main screen
Defining Screen Exits
Screen from SAP
application program

abcd
Enhancements Step1
Step2
Enhancements Step3
Enhancements Step4
Enhancements Step5
Enhancements Step6
Enhancements Step7

Activate Project !
Calling Customer Subscreens
Transporting Data to Subscreens

abcd
Transporting Data from Subscreens
Editing Subscreens (1)
Editing Subscreen (2)
Summary: Screen Exits

Sub-screen area

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy