Browse ABAP related topics under this category
Module Pool Program (also called Online programs , dialog programs, or transactions) is a collection of screens (the actual, physical image that the users sees), their Flow Logic(code behind the screens ), and the code within the main ABAP program.
In this up-to-date training presentation you will find handy notes on:
In this post, you will find links to set of ABAP presentations of following topics:
The word “hard-coding” will make any SAP consultant serious. Consultants always doubt the enhancement / reports / programs which has hard coded logic. Because they believe that it may work temporarily and not a permanent solution to the requirement. So, should it be avoided 100%? As per SAP experience of this document’s author, hard coding has not to be avoided 100%. Hard coding has to be used in most of the ABAP programming to meet the requirement. But the ABAP consultant has to understand what can be hard coded, how and why? Author of this document aims to differentiate good and bad practices of hard coding in this document.
This document is intended for ABAP consultants. Also, will help the functional consultant to prepare a better functional specification to avoid reworking. The document will help the consultant to understand the hard coding concept with some samples which are taken from the SAP projects.
Structure is a database object which is a group of fields which can be used in multiple tables in SAP ABAP. The advantage of structure is that it is reusable in multiple tables. The difference between the table and structure is , structure can hold single record only where as a table can hold multiple record.
In this document, you will find step-by-step guide to structure implementation in two ways:
In this document you will find a set of ABAP Dictionary sample exercises with solutions, step-by-step screenshots and in-depth explanations. In exercises you will do practices for following scenarios:
Exercises in first chapter will teach you how to create and manipulate the basic objects to be used for a simplified payroll processing system in ABAP Dictionary: tables, data elements, and domains. You will also enter data into one of your tables, and you will learn how to write a simple program that extracts data from an ABAP Dictionary table.
In addition to exercises in first chapter, you will take a step further by establishing appropriate foreign keys in the ABAP Dictionary in second chapter.
In chapter 3 you will become familiar with manipulating existing tables, their structures, and their data.
In chapter 4 you will learn how to creat and use structures (tables of type INTTAB) in SAP.
The purpose of chapter 5 is to give you experience using the ABAP Repository Information System. This facility can provide a great deal of information on objects created and maintained within SAP.
and you will find more minor exercises in this document…
Providing examples on OOPS in SAP ABAP, entire content on this document has been designed and documented in such a way that the reader can easily grasp the matter and implement it in his course of learning. You will find notes of individual sections in detail and examples illustrating the important concepts.
This document aims to help the ABAPers to set up the necessary configurations to send IDoc from one system to another. This document will provide developers a good starting point on how to start and where to start after studying all the theoretical aspects of ALE/IDoc.
Scope of scenarios on EDI systems is outside the scope of this document. Also, sending Idoc by message control mechanism is not described here. Not there is any discussion of sending Idoc using BAPI.