0% found this document useful (0 votes)
42 views2 pages

Defination

This document discusses ABAP custom programming. It defines custom ABAP as programming used to create SAP screens. It lists the main transaction codes used for screen painter, logic, and menu painter. It describes the mandatory and optional events in ABAP programming. It explains the modularization techniques using include programs. It compares report programs and dialog programs, noting that dialog programs are linked to screens and transactions while report programs are standalone. It lists the main components of a custom ABAP program as the transaction code, screen, GUI status, ABAP program, screen flow logic, and dynamic program (DYNPRO) combining the screen and flow logic.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views2 pages

Defination

This document discusses ABAP custom programming. It defines custom ABAP as programming used to create SAP screens. It lists the main transaction codes used for screen painter, logic, and menu painter. It describes the mandatory and optional events in ABAP programming. It explains the modularization techniques using include programs. It compares report programs and dialog programs, noting that dialog programs are linked to screens and transactions while report programs are standalone. It lists the main components of a custom ABAP program as the transaction code, screen, GUI status, ABAP program, screen flow logic, and dynamic program (DYNPRO) combining the screen and flow logic.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

DEFINATION:

It is a special type of programming which is used to create custom sap screens.

Transaction codes:

Se80-object browser se51- screen painter, se38 – logic , se41- menu painter

List of Events:

Process before output (Mandatory)

Process after input (Mandatory

Process on value request

Process on help request

Modularization techniques
_TOP "top include program ,All data declarations.
_O01 "PBO include program , All logic related to PBO event
_I01 "PAI include program , All logic related to PAI event
_F01 "Forms include program , All logic related to subroutines

Differnece

Report Programs:
1. Reports are stand alone programs.
2. We use reports to read data base tables & represent results in Lists
3. Reports are collection of processing blocks, controlled by System calls depending on events.
4. Reports can use LDBs or SELECT STATEMENTS
defined by DEVELOPER.
5.Reports can call Dialogue programs and vice versa.
Dialog Programming
1.Dialogue programs are not stand alone programs. (we
have to link the dialogue programs to at least one or
more SCREENS & TRANSACTION CODES)
2. We use Dialogue Programs to read & change
Database tables.
3.Dialogue programs are controlled by Screen flow logic.
4.Dialogue program is also called as Module pool program
or TRANSACTION.
5.These module pools are separated in to PBO and PAI
events.

Components:

Transaction code

Screen

GUI STATUS

ABAP PROGRAM

SCREEN FLOW LOGIC

DYNPRO – screen together with flow logic

You might also like