SAP ABAP Interview Questions on Data Dictionary

Welcome to SAP ABAP Interview Questions. SAP ABAP Data Dictionary is a central repository where we can maintain and organize objects related to databases. 

Here we are providing real time SAP ABAP Interview Questions for freshers and experienced. Refer this post for SAP Interview Questions on Data Dictionary.

Read more »

SAP ABAP Webdynpro Component Architecture MVC Windows

Welcome to SAP ABAP Interview Questions. SAP ABAP Webdynpro Component Architecture,Windows and Nested Views, MVC Architecture. 

A window in ABAP Webdynpro defines which views are displayed in which combination and how the view combination may be changed by firing outbound plugs.

Read more »

SAP WebDynpro Architecture Entities Concepts Mapping

Welcome to SAP ABAP Interview Questions. SAP WebDynpro ABAP Architecture Entities, Concepts, Context Mapping, Data Binding and Navigation between Views for webdynpro interview preparation . 

SAP ABAP Web Dynpro components allow structuring complex Web applications and developing reusable, interacting entities in SAP applications. These SAP ABAP Web Dynpro notes and tutorials will help you to face interviews on SAP ABAP Webdynpro.

SAP ABAP WebDynpro Architecture : Entities and Concepts

Read : SAP Web Dynpro ABAP Introduction

Web Dynpro components allow structuring complex Web applications and developing reusable, interacting entities. This enables the nesting of large application sections. Web Dynpro components are containers for other entities related to the UI and the WebDynpro program.

SAP WebDynpro Component

Entities related to the UI are windows and views. The layout of a view represents a rectangular part of a page displayed by the client (for example, a browser). The view contains UI elements such as input fields and buttons. 

The complete page sent to the client can be set up by only one view, but can also be a combination of multiple views. The possible combinations of views and flow between the views are defined in a window.

A window can contain an arbitrary number of views. A view can be embedded in an arbitrary number of windows. The Web Dynpro source code is located in Web Dynprocontrollers. The hierarchical storage for the global variables of controllers is called the context.

Web Dynpro components can be addressed in three different ways:

• Using a Web Dynpro application, a Web Dynpro component can be related to a URL, which can be called from a Web browser or another Web Dynpro client.

• When reusing a Web Dynpro component as a sub-component, the visual interface of a Web Dynpro component can be combined with the visual entities of the main component to form the UI.

• When reusing a Web Dynpro component as a sub-component, all methods and data defined in

Context Mapping and Data Binding

The variables defined in a WebDynpro Controller context can be referenced from other Web Dynpro controllers. This is called context mapping. This allows to sharing common attributes between different controllers, so copying these attributes between the controller contexts is not necessary.

Context and Data Transport

The values of UI elements, that allow a user input, have to be connected to context attributes of the corresponding controller. This is called data binding. 

Through data binding, an automatic data transport between the UI elements and the context attributes is established. Combining these two concepts, the data transport between UI elements located in different views can be defined in a purely declarative way.

Context Mapping in SAP Webdynpro ABAP

Context mapping allows a context node in one controller to be supplied automatically with data from a corresponding context node in another controller. This is the primary mechanism for sharing data between controllers. When two controllers within the same component share data through a mapping relationship, it is known as internal mapping.

The context node that acts as the data source is known as the mapping origin node, and the context node that is mapped is known as the mapped node .

The mapping between controller contexts located in different WebDynpro components is known as external mapping.

For a mapping relationship to be established, the following steps must first be performed:

• A node must exist in the context of the controller acting as the mapping origin. This node need not have any declared child nodes or attributes.

• The mapping origin controller must not be a view controller.

• The controller containing the mapped node must declare the use of the mapping origin controller as a used controller.

Putting Data on the Screen: Data Binding in SAP Webdynpro

Data binding is the means by which data is automatically transported from a view controller’s context to a UI element in its layout, and vice versa  You may not bind UI elements to context nodes or attributes defined in some other controller. UI elements are private to the view controller within which they are declared.

The data binding process decouples the UI element object from the application code within the view controller. Therefore, in order to manipulate UI element properties, the application code in the view controller needs only to manipulate the values of context nodes and attributes to which the UI elements are bound.

The Web Dynpro framework then manages the following two tasks:

• The transport of data from the context attribute to the UI element during the screen rendering process.

• Repopulating the context attribute from the UI element after data has been entered by the user and the next server round trip is initiated. Hereby, the values entered by the user are automatically converted and checked for type conformity. If an error occurs, a message is displayed.

Databinding is powerful, since not only the value of a UI element can be bound to a context attribute, but other UI properties like visibility can also be bound. This way, UI element properties can be manipulated from the view controller by acting on context attributes.

Navigation Between Views in SAP Webdynpro ABAP

Navigation between views is triggered by firing outbound plugs . Firing an outbound plug causes a navigation event to be raised. Navigation events are special asynchronous events that are placed into a navigation queue. Multiple outbound plugs can be fired from one view. This can be used to define the next UI, consisting of multiple views.

Navigation Between Views

The navigation queue is processed at a certain point of time in the WebDynproprocessing phase. Up to this point of time, the navigation stack can be extended by firing additional outbound plugs, or the complete navigation stack can be deleted. Outbound plugs should be named according to the action that caused navigation away from the current view.

Inbound plugs are special event handler methods that subscribe to navigation events raised when outbound plugs are fired. Inbound plug methods are called only when the navigation queue is processed. This will only take place once the views in the current view assembly have fired their outbound plugs and no validation errors have occurred that would cause navigation to be cancelled.

Inbound plugs should be named according to the reason for which the view being displayed. Outbound and inbound plugs are joined together using navigation links.

Technically, linking an inbound plug to an outbound plug means registering the inbound plug event handler method to the navigation event, called by firing an outbound plug. Outbound plugs and event handler methods related to the inbound plug can have parameters, allowing you to pass data between the views.

Read Articles on : SAP ABAP Webdynpro Interview Questions

Read more »

SAP Webdynpro Introduction Benefits for Beginners

Welcome to SAP ABAP Interview Questions. SAP ABAP Web Dynpro Introduction, Benefits for Beginners Tutorial. 

SAP Webdynpro is a technology used to build interactive web based applications in SAP using SAP Webdynpro ABAP or SAP Webdynpro Java. Here we are going to start a first SAP Webdynpro introduction, benefits tutorial for beginners. These SAP ABAP Web Dynpro notes and tutorials will help you to face interviews on SAP ABAP Webdynpro.

What is SAP Web Dynpro for ABAP or JAVA?

From a technological point of view, SAP's WebDynpro for Java and ABAP is a revolutionary step in the development of Web based user interfaces. It is completely unlike any design paradigm previously used by SAP and represents a quantum leap in the development of Web based enterprise resource planning (ERP) applications.

Web Dynpro applications are built using declarative programming techniques based on the Model View Controller (MVC) paradigm. That is, you specify which user interface elements you wish to have on the client, and where those elements will get their data from. 

You also define the possible navigation paths declaratively in your application. All the code to create the user interface is then generated automatically within a standard run time framework. This relieves you from the repetitive coding tasks involved in writing HTML and making it interactive with JavaScript.

SAP ABAP WebDynpro has been available since SAP NetWeaver 7.0 (SAP NetWeaver Application Server 7.0). For developing the entities of a Web Dynpro application, the Object Navigator (transaction code SE80) has been enhanced. SAP WebDynpro is designed to support structured development. The software modularization units are Web Dynpro components, which can be combined to build up complex applications in SAP.

Meta Model Declaration vs. Custom Coding

A Web Dynpro application is developed using a declarative programming approach. Within the ABAP Workbench there are special tools that allow you to build an abstract representation of your application in the form of a Web Dynpro meta model. The necessary source code is then generated automatically and conforms to a standard architecture known as the Web Dynpro framework. The Web Dynpro framework allows you to place the custom source code at predefined positions within the generated code.

All SAP ABAP WebDynpro applications are constructed from the same basic units. However, through the use of custom coding, the standard framework can be extended to supply any required business functionality. Not all implementation decisions need to be made at design time. It is possible to implement a Web Dynpro application in which the appearance of the user interface is decided at run time. This allows a highly flexible application to be written without the need to directly write any HTML or JavaScript.

Application Scenarios with Web Dynpro

Web Dynpro applications can access different kinds of data sources:

• From an SAP ABAP WebDynpro application, all kinds of reuse components can be addressed directly (for example, function modules or methods). It is even possible to access the database via an ABAP SELECT. However, this leads to a mixing between flow logic and business logic and should therefore be omitted.

• Web Services can be used after having generated a Web Service client object.

• The SAP Java Connector (JCo) can be used to call methods of Enterprise JavaBeans located on a J2EE Engine.

Model objects are not yet supported in SAP ABAP Web Dynpro. The best way to have reusable entities encapsulating business logic is to create ABAP classes containing the source code.

It is also possible to develop UI-free (faceless) Web Dynpro components, which only offer reusable functionality. These components can then be accessed by other Web Dynpro components by means of component reuse.

Benefits of SAP WebDynpro ABAP

Web Dynpro‘s main goal is to enable application developers to create powerful Web applications with minimum effort using descriptive tools in a structured design process.

One guiding principle in the Web Dynpro philosophy is: The fewer lines offhand written code, the better. Web Dynpro pursues this goal in two ways.

• WebDynpro uses a declarative, language-neutral meta model for defining auser interface. From this abstract definition, the development environment generates the required source code. Hand-written code still has its place, but is confined to that required to manipulate the business data, not the user interface.

• WebDynpro provides technical features such as support for internationalization, flicker free interaction, and a clean separation of the business logic and the user interface.

This separation is achieved through a modified implementation of the Model ViewController (MVC) design paradigm. Since the repetitive tasks of UI coding have been eliminated, the developer can focus his attention on the flow of business data through the application. Web Dynpro applications can run on a range of devices and on various types of networks, an important feature for collaboration scenarios.

Read more »

Tcodes in SAP HR HCM

Welcome to SAP ABAP Interview Questions. Complete list of Tcodes in SAP HR HCM Tables. In SAP Transaction Code (Tcode) is used for calling a particular page or screen. Without  Tcodes in SAP we are nothing to do, we con't open a single page also. Here we are going to provide a complete list of tcodes in sap hr. TCODES in SAP HR categorized as Master Data Tcodes, Time Management Tcodes, Payroll Tcodes, Benefits Tcodes,  General Reporting Tcodes, Organizational Management Tcodes, Recruitment Tcodes in SAP, SE16 Tables for SAP HR, Programs and Reports in SE38 for SAP HR. Refer this post for complete list of SAP HR HCM TCODES.

Read more »

Webdynpro ABAP Controller Methods Attributes

SAP Webdynpro ABAP Controller Methods and Attributes, Methods and Attributes are available for all webdynpro abap controllers. These methods are Hook Methods, Instance Methods, and Attributes. Refer this post for more details on  Webdynpro ABAP Controller Methods and Attributes. Click on read more.

Read more »

SAP Webdynpro Controllers for ABAP Component View Window Custom

Webdynpro Controllers for ABAP, Component,View,Window,Custom Controllers. Controllers contain the source code of a Web Dynpro application, they hold the context data and care for event handling and navigation. Any programming of flow logic requires the knowledge of how controllers are defined and what kind of entities they offer. This post consist of brief information on Controller in Webdynpro for ABAP Programming for beginners who are looking for information on SAP Web Dynpro ABAP. Read more to refer this post on Webdynpro ABAP Controllers.

Read more »

SAP Webdynpro ABAP for Beginners Understanding Tutorial

SAP Webdynpro ABAP for Begginers Understanding Tutorial. Web Dynpro is a programming model provided by SAP. Web Dynpro is  implemented using Java and ABAP. It is suited to generate standardized user interfaces (UIs) using a declarative approach, resulting in a minimum time efforts to realize Web applications. Beginners have a look into this post for features and benefits of ABAP Web Dynpro Programming. Refer this post for more details on ABAP Webdynpro Tutorial.

Read more »