How to modify and extend SAP applications – Different approaches + Transaction codes

如何修改及延伸 SAP 應用系統
How to modify and extend SAP applications – Different approaches + Transaction codes

This part of series is focused on transactions that allow an ABAP developer enhance the original SAP reports with his own modifications. You will find here the list of transactions – possibilities how to extend SAP reports, internal logic within function modules, classes or dictionary objects.

---

This post is part of series about SAP transaction codes for ABAP Developers:

1. Basic SAP transactions for ABAP developers
2. How to modify and extend SAP applications
3. Transaction codes for database and table handling
4. How to analyse, debug and optimize your SAP programs with standard tools

---

Introduction

There are following options how to modify SAP’s standard code. Recommended approaches are BADI implementations and enhancement points.

• BADI implementations – SE18, SE19
• Enhancement points – implicit or explicit enhancements points – SE80
• User exits – CMOD, SMOD
• Modifications – SE95, SPAU, SPDD

1. Business Add Ins (BADI)

SE18 – BADI Builder – Definitions

BADI stands for Business Add Ins which is an advanced way of implementing modifications. Developer can use BADI builder definition for creating or searching for possible places where he or his customers can modify ABAP logic using BADI or enhancement spots.

SE19 – BADI Builder – Implementations

When the developer knows which BADI or enhancement spot he wants to modify, he can manage BADI implementations and enhancement spots in se19.

2. Enhancements

SMOD – SAP Enhancements

SAP Enhancements transactions is a former type of SAP’s way to modify programs using user exits. Anyway, it can still be handful for developer to know this transaction, since he may come across old solutions which used this technique. SMOD includes more type of user exits – menu, screen and function module exits.

CMOD – Project Management of SAP Enhancements

CMOD transaction is used for managing attributes, enhancement assignments, components and documentation of SAP Enhancement. Developer manages here Enhancement projects which are formed by Enhancements from SMOD.

3. Enhancement points

SE80 – ABAP Development Workbench

SE80 transaction was already mentioned in the first article about essential transaction codes for ABAP development. The reason why it is included here is the fact, that the developer can manage enhancement points through this transaction. When the developer clicks on a highlighted icon, enhancement implementation tools will be available for him. He can choose either from explicit or implicit enhancement points in the source code where he can insert his own code or modify already implemented enhancement points.

4. Modifications

SE95 – Modification Browser

When there is no other option, the developer can also create modifications in the source code using transaction se80. First he needs to obtain repair registration key from SAP OSS, then the modification will be possible. Be aware that this is the most painful way because the developer will have to take care about merging the changes after every service pack upgrade or note implementation using transactions SPAU and SPDD. Modification browser is the used by developer to manage all recent modifications in the system.

SPAU – Modification Adjustment

After every upgrade, modifications has to be rechecked. When there is a change in the standard code in the same place where is the modification, developer needs to adjust this modification.

SPDD – Modification Adjustment for Dictionary

The same approach must be used for dictionary objects. Whenever the dictionary object is changed, developer have to repeat the modification.

SAP 資料庫 Transaction codes for Database and Table handling

Transaction codes for Database and Table handling

In this part of series, I am going to describe several original SAP transaction codes (reports and utilities) for handling tables and database.

---

This post is part of series about SAP transaction codes for ABAP Developers:

1. Basic SAP transactions for ABAP developers
2. How to modify and extend SAP applications
3. Transaction codes for database and table handling
4. How to analyse, debug and optimize your SAP programs with standard tools

---

Basic transactions for table management SE11 – ABAP Dictionary, SE16 – Data Browser, SE54 – Generate Table Maintenance are described in the first post of the series. Just to remind you, se11 is used for managing dictionary objects including database tables, se16 is used for browsing the data in a database table and finally se54 is used creating maintenance views where you can manage that data.

Apart from these basic transaction codes, there are several more advanced utilities which are used for specific database operations. Those transaction codes(t-codes) are as following.

SE14 – Database utility

Whenever you change the structure of a table which is derived from ABAP dictionary object (transparent table, physical table pool, table cluster, indexes or database views) , you also need to run the database utility in order to synchronize changes between ABAP Dictionary and database layer. Moreover, this utility allows you to maintain terminated conversions, administer modification requests and manage incremental conversions.

SE16n – Table display

Transaction SE16N is actually an improved and more user-friendly data browser SE16 with ALV data grid. Until EHP5, it was possible to enter code &SAP_EDIT and edit data inside of tables, but due to security risk, this option is not available anymore. Anyway, there is still an option to turn on edit mode using debugger.

SM30, SM31 – Generate table maintenance dialog

Transaction SM30 allows you to run generated dialog where it is possible to view and change data in database tables and views. Those database objects must have set up the option Display/Maintenance allowed in ABAP Dictionary table management and have already generated table maintenance via SE54.

Transaction SM31 refers to the same program which SM30 does, so there is no difference between this transaction. The old SM31 transaction is available as transaction SM31_OLD.

DB02 – Database analysis

DB02 is a database analysis tools which displays various statistics of database and database objects. The purpose of this tool is to check whether there are missing indexes in database tables and check consistency of database objects.  Moreover, this tool can give you overview of data area occupancy (available/occupied space) of the whole database.

How to analyse, debug and optimize your SAP programs with standard tools

There is a phase in development cycle when the programmer needs to optimize his final product. This post focuses on those transactions which help developers to analyse, debug and optimize already finished reports and programs.

---

This post is part of series about SAP transaction codes for ABAP Developers:

1. Basic SAP transactions for ABAP developers
2. How to modify and extend SAP applications
3. Transaction codes for database and table handling
4. How to analyse, debug and optimize your SAP programs with standard tools

---

SAP system offers several options how to analyze our programs. Let’s start with the debugger.

Developer tools

Debugger

There are basically two options how to use a debugger. You can either start the debugger when you set a session break point in your code while using se80 or se38. When you run the program additional window with (new) debugger will show up.

The other method to is enter one of these following codes into command field just before you run the report:

• /h – basic and most used command which will run the debugger
• /hs – start debugger and allow system debugging
• /ha – start debugger, skip screen handling and start directly debugging ABAP code
• /hmusa – start debugger and create memory snapshot which can be analysed in transaction S_MEMORY_INSPECTOR
  
  

BAPIs in Project Management (PRO)

Skip to end of metadata

• Created by Former Member, last modified by Former Member on Nov 25, 2016

Go to start of metadata

BAPIs can you find in SE37 when searching with:

BAPI	Operative Object
BAPI_BUS2172*	Project
BAPI_BUS2173*	Phase
BAPI_BUS2175*	Task
BAPI_BUS2176*	Checklist Header
BAPI_BUS2174*	Checklist Item
BAPI_BUS2177*	Role

BAPI	Templates
BAPI_BUS2170*	Project Template
BAPI_BUS2167*	Phase in Template
BAPI_BUS2169*	Task in Template
BAPI_BUS2171*	Checklist Template
BAPI_BUS2168*	ChkLst Itm in Temp
BAPI_BUS2178*	Role in Template

New BAPIs for resource management in Detail:

BAPI name	BAPI Role/ function
BAPI_BUS2177_ROLE_DIST_GET	Determine Demand Distribution
BAPI_BUS2177_ROLE_DIST_SET	Change Demand Distribution
BAPI_BUS2177_STAFF_DIST_GET	Determine Demand Distribution
BAPI_BUS2177_STAFF_DIST_SET	Change Demand Distribution

BAPI_BUS2177_ROLE_DIST_SET SAP Function module - BAPI Role: Change Demand Distribution

             Nederlands (Dutch)             English             Français (French)             Deutsch (German)             Italiano (Italian)             日本語 (Japanese)             한국의 (Korean)             Polski (Polish)             Português (Portuguese)             русский (Russian)             简体中文 (Simplified Chinese)             español (Spanish)             正體中文 (Traditional Chinese)             Türk (Turkish)         

 Hierarchy

☛  CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0
   ⤷  PPM-PRO-EXT-API (Application Component) BAPI Interface for cProjects
     ⤷  DEVELOPMENT_PROJECTS_BAPI (Package) Project Management - BAPI

 Basic Data

Function Module	BAPI_BUS2177_ROLE_DIST_GET	BAPI Role: Determine Demand Distribution
Function Group	DPR_BUS2177	Development Projects: Role
Program Name	SAPLDPR_BUS2177
INCLUDE Name	LDPR_BUS2177U40

 Parameters

Type	Parameter Name	Typing	Associated Type	Default value	Optional	Pass Value	Short text
Exporting	ES_DIST_ADMIN_DATA	TYPE	BAPI_TS_DIST_ADMIN_DATA				Distribution administration data
Exporting	EV_DIST_GUID	TYPE	DPR_TV_GUID				Application Object GUID
Exporting	EV_ENTITY_GUID	TYPE	DPR_TV_GUID				Application Object GUID
Importing	PROJECTROLE_GUID	TYPE	BAPI_TS_GUID-ROLE_GUID				GUID for Project Role
Tables	ET_DISTRIBUTION	TYPE	BAPI_TS_DIST_DATA				Distribution data
Tables	RETURN	TYPE	BAPIRET2				Return Parameters

 Processing Type

Normal Function Module
Remote-Enabled Module	BaseXML supported
Update Module	Start immediately
	Immediate Start, No Restart
	Start Delayed
	Coll.run
JAVA Module Callable from ABAP
Remote-Enabled JAVA Module
Module Callable from JAVA

 History

Last changed by/on	SAP	20141109
SAP Release Created in	310

讀出功能模組文件 SAP Function Module Documentation

Get SAP function module documentation

Step 1 - Execute transaction SE37 
First, execute sap transaction SE37 and enter the function module name. Then press the display button 
 

Alternatively, choose menu option Goto->Documentation->Function Module Documentation. The only problem I find with this option is that the documentation popup box appears underneath the current SAP window so you don't actually see it without moving the window 
 

Step 2 - Display documentation 
If you selected display you will be taken to the FM details, now simply choose the menu option goto->Documentation. 
 

The Function module documentation will now be displayed 
 

Step 3 - Alternate way using tcodevSE80 
You also get the same options to view Function Module documentation within SAP transaction SE80 

ABAP/4 讀取　Database table, store procedure

1. data:
2. PAR1(30) type C,
3. PAR2(30) type C,
4. OUT1 type I,
5. OUT2(30) type C,
6. OUT3(30) type C.
7.  
8. exec sql performig sp_return.
9. select * from $PROC$sp_dummy
10. where ( :par1, :par2 )
11. into :out1, :out2, : out3
12. endexec.
13.  
14. form sp_return.
15. * some coding
16. endform

General Types

Predefined data types without special semantic attributes.

Numeric Types

Type	Valid Places m	Initial Value	Meaning	ABAP Type
INT1	3	0	1-byte integer, 0 to 255	b
INT2	5	0	2-byte integer, -32,768 to 32,767	s
INT4	10	0	4-byte integer, -2,147,483,648 to +2,147,483,647	i
INT8	19	0	8-byte integer, -9,223,372,036,854,775,808 to +9,223,372,036,854,775,807	int8
DEC	1-31	0	Packed number BCD format	p, length m DIV 2 + 1
DF16_DEC	1-15	0	Decimal floating point number stored in BCD format	decfloat16
DF16_RAW	16	0	Decimal floating point number stored in binary format	decfloat16
DF34_DEC	1-31	0	Decimal floating point number stored in BCD format	decfloat34
DF34_RAW	34	0	Decimal floating point number stored in binary format	decfloat34
FLTP	16	0	Floating point number	f

See Integers, Packed Numbers, Binary Floating Point Numbers and Decimal Floating Point Numbers.

Character-Like Types

Type	Valid Places m	Initial Value	Meaning	ABAP Type
CHAR	1-30000, maximum of 1333 for table fields	m blanks	Character string	c, length m
LCHR	256-32000	None	long character string	c, length m
SSTRING	1-1333	Empty string	Character string	string
STRING	256-...	Empty string	Character string (CLOB)	string

See Character-Like Types and Byte-Like Types.

Byte-like types

Type	Valid Places m	Initial Value	Meaning	ABAP Type
RAW	1-32000 maximum of 255 for table fields	None	Byte string	x, length m
LRAW	256-32000	None	Long byte string	x, length m
RAWSTRING	256-...	Empty string	Byte string (BLOB)	xstring

See Character-Like Types and Byte-Like Types.

Special Types

Predefined data types with special semantic attributes.

Date Types/Time Types

Type	Valid Places m	Initial Value	Meaning	ABAP Type
DATS	8	00000000	Date in the format YYYYMMDD	d
TIMS	6	000000	Time in the format HHMMSS	t
ACCP	6	6 blanks	Posting period in the format YYYYMM	n, length 6

See Date Types and Time Types.

Character-Like Types with Special Semantics

Type	Valid Places m	Initial Value	Meaning	ABAP Type
NUMC	1-255	m zeroes	Numeric text	n, length m
CLNT	3	000	Client	c, length 3
LANG	1	Blank	Language key	c, length 1

See Special Character-Like Types.

Currency Fields and Quantity Fields

Type	Valid Places m	Initial Value	Meaning	ABAP Type
CURR	1-31	0	Currency field in BCD format	p, length m DIV 2 + 1
CUKY	5	5 blanks	Currency key for currency fields	c, length 5
QUAN	1-31	0	Quantity field in BCD format	p, length m DIV 2 + 1
UNIT	2-3	2 or 3 blanks	Unit key of a quantity field	c, length m

‎See Currency Fields and Quantity Fields.

Obsolete Types

Type	Valid Places m	Initial Value	Meaning	ABAP Type
DF16_SCL	16	0	Decimal floating point number stored in binary format with scaling specified (obsolete)	decfloat16
DF34_SCL	34	0	Decimal floating point number stored in binary format with scaling specified (obsolete)	decfloat34
PREC	2	0	Obsolete data type	s
VARC	1-...	None	Obsolete data type	c, length m

Character-Like Types and Byte-Like Types

• Character Strings

• Byte Chains

• Notes on Strings

• Use in Open SQL

Character Strings

The following predefined data types in ABAP Dictionary are available for general character strings:

• CHAR for text fields

The predefined type CHAR, mapped to the ABAP type c, is used to describe general text fields with a maximum length of 30000 characters (only 1333 characters for table fields).

• LCHR for long text fields

The predefined type LCHR, also mapped to the ABAP type c, is used to describe general text fields with lengths between 256 and 32000 characters. In database tables, the maximum length must be specified as the value of a preceding INT2 or INT4 field. Table fields of this type cannot be used as key fields of database tables or in any positions in Open SQL statements.

• SSTRING for short text strings

The predefined type SSTRING is mapped to the ABAP type string, but handled like the type CHAR or VARCHAR in ABAP Dictionary and by database tables. The length is restricted to a maximum of 1333, but table fields of this type can also be used as key fields by database tables and used by Open SQL statements in almost all positions where text fields are possible.

• STRING for text strings

The predefined type STRING is mapped to the ABAP type string and also handled like a text string (CLOB) in ABAP Dictionary and by database tables. Table fields of this type cannot be used as key fields or index fields in database tables or in any positions in Open SQL statements.

Notes

• In general structures, the length of a component of type CHAR is not restricted to 1333.

• In database tables, there can be only one table field of the type LCHR and it must be the last table field. This means that the type LRAW cannot be used simultaneously in the same database table. If the statement SELECT is used to read an LCHR field, the preceding length field must also be read. In writes using Open SQL, the length field must be given the correct value or data may be lost.

• LCHR is no longer recommended for new developments. The type STRING is recommended instead, however it is also not suitable for key fields of database tables or for unrestricted use in Open SQL. Where possible, SSTRING can be used here instead.

• Switching existing dictionary objects from LCHR to STRING or SSTRING, on the other hand, can be critical, since all ABAP types and ABAP objects that reference dictionary objects like this are then given a deep data type. A switch from a flat data type to a deep data type usually constitutes an incompatible change and can produce syntax errors in ABAP programs.

Example

Like the example for literals; the row to be read is here also specified using host variables. The addition STRUCTURE is specified after INTO. However, this is not necessary since wa can be identified statically as a structure. The structure wa is handled in the INTO clause as if all substrings were specified separately: INTO :wa-cityfrom, :wa-cityto.

PARAMETERS: p_carrid TYPE spfli-carrid,
            p_connid TYPE spfli-connid.

DATA: BEGIN OF wa,
        cityfrom TYPE spfli-cityfrom,
        cityto   TYPE spfli-cityto,
      END OF wa.

EXEC SQL.
  SELECT cityfrom, cityto
         INTO STRUCTURE :wa
         FROM spfli
         WHERE mandt  = :sy-mandt AND
               carrid = :p_carrid AND connid = :p_connid
ENDEXEC. 

Example

Reads multiple rows from the database table SPFLI using cursor handling and host variables in static Native SQL. If rows are found, sy-subrc is set to 0 and sy-dbcnt is increased by one for each row read.

PARAMETERS p_carrid TYPE spfli-carrid.

DATA:  connid   TYPE spfli-connid,
       cityfrom TYPE spfli-cityfrom,
       cityto   TYPE spfli-cityto.

EXEC SQL.
  OPEN dbcur FOR
    SELECT connid, cityfrom, cityto
           FROM spfli
           WHERE mandt  = :sy-mandt AND
                 carrid = :p_carrid
ENDEXEC.

DO.
  EXEC SQL.
    FETCH NEXT dbcur INTO :connid, :cityfrom, :cityto
  ENDEXEC.
  IF sy-subrc <> 0.
    EXIT.
  ELSE.
    ...
  ENDIF.
ENDDO.

EXEC SQL.
  CLOSE dbcur
ENDEXEC. 

Bad Example

Reads multiple rows from the database table SCARR and calls the subroutine evaluate for each row read.

DATA wa TYPE spfli-carrid.

EXEC SQL PERFORMING evaluate.
  SELECT carrid FROM spfli INTO :wa WHERE mandt = :sy-mandt
ENDEXEC.
cl_demo_output=>display( ).

FORM evaluate.
  cl_demo_output=>write( |{ wa } | ).
ENDFORM.

Good Example

Explicit cursor processing.

DATA wa TYPE spfli-carrid.

EXEC SQL.
  OPEN CUR FOR
  SELECT carrid FROM spfli WHERE mandt = :sy-mandt
ENDEXEC.

DO.
  EXEC SQL.
    FETCH NEXT CUR INTO :wa
  ENDEXEC.
  IF sy-subrc <> 0.
    EXIT.
  ENDIF.
  cl_demo_output=>write( |{ wa } | ).
ENDDO.
cl_demo_output=>display( ).