Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  z...

What are The Events in Module Pool Programming

What are The Events in Module Pool Programming
Dialog(Dynpro) programming Controls the multiple screens which are integrated hierarchically to the main program(Transaction) and they are executed in a sequence. The main elements of the module pool Programming are
Screens
Module pools
Subroutines
Menus
Transactions
Events in Module Pool Programming(Dialog programming)
In the PAI event, all of the Data from the screen is transported to the ABAP program when the automated input checks and before the primary PAI module is termed.
At the top of the last PBO module, and before the screen is displayed, all of the Data is transported from the ABAP program to any identically-named fields within the screen.
Data is transported between the screen and therefore the ABAP program at the start and finish of every dialog tread the appliance server.
There are four event blocks, each of which is introduced with the screen keyword PROCESS:

PROCESS BEFORE OUTPUT (PBO) is automatically triggered after the PAI processing of the previous screen and before the current screen is displayed. You can write source code in this block.
PROCESS AFTER INPUT (PAI) is triggered when the user chooses a function on the screen. You can write source code program the PAI processing of the screen in this block.
PROCESS ON HELP-REQUEST (POH) is triggered when the user requests field help (F1) or possible values help (F4) respectively.
PROCESS ON VALUE-REQUEST (POV) is triggered when the user requests field help (F1) or possible values help (F4) respectively

Comments

Popular posts from this blog

Created structur transaction

Created structur transaction UFD - Distribute Variant Functions CU01 - Create Dependency CU60 - Table Maintenance CU02 - Change Dependency CU65 - Create Function CU21 - Create Dependency Net CU61 - Create Table Structure CU03 - Display Dependency CU59 - Transfer Variant Table Contents CU22 - Change Dependency Net CU63 - Display Table Structure CU05 - Dependency Where-Used List CU04 - Dependency List CU62 - Change Table Structure CU23 - Display Dependency Net

What is BAPI in SAP ABAP with Example

What is BAPI in SAP ABAP with Example What is BAPI? The Business Application Programming Interface (BAPI) is a standardized programming interface (method) that allows external applications to access enterprise processes and R / 3 system data. BAPIs are defined in the Business Object repository (BOR) as SAP Business Object-type methods that perform certain business functions. They are implemented as RFC-compatible functional modules and are created in the ABAP Workbench function generator. Some BAPIs and methods provide basic functionality and can be used in most SAP business objects. These are called BAPI NORMALIZED. BAPIs for Mass Processing -ChangeMultiple(), CreateMultiple(), DeleteMultiple(). BAPIs for Reading Data - GetList() , GetDetail() , GetStatus() , ExistenceCheck(). BAPIs for Creating or Changing Data- Create() ,Change(),Delete() and Undelete() . They provide stable and standardized methods for perfect integration between the R / 3 system and external appli...

ABAP/4 DEVELOPMENT STANDARDS

ABAP/4 DEVELOPMENT STANDARDS These slides covers Object naming standards, ABAP/4 Programming standards and procedures. These programming standards are intended to aid ABAP/4 programming in the SAP R/3 software development. Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466).Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466). Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Following, we will define the standards for the use in this Project. Program The following program naming conventions have to be followed for creating ABAP/4 programs, functions, includes and reports.  Refer to Maintai...