SAP ABAP

SAP : Using USER EXIT For FI SUBSTITUTION

Substitutions can be used for validating data at the time of entry in SAP system. This wiki can be used for creating custom user exits so that one can set his validations & conditions. User exits are user defined FORM routines that are used to calculate/replace values with in a substitution .I have shown demo for FI but same steps with some minor modifications can be used for other areas too.

What are substitutions?

Whenever a data is entered in a system, validations are invoked to check its integrity .Once validations are done, one can substitute the entered value with some other value. This gives you the opportunity of having the system validate values that are to be substituted. A substitution value can be numeric or a string. The system first performs some validations and then substitutions.

Transactions used for substitutions are :

GGB1 : Substitutions maintenance.

OBBH : Activation of FI substitutions.

Substitutions can be performed using three ways:

1.Constant values.

2.Field -Field assignment.

3.User exits.

Steps for creating user exits for substitutions....click here for fully story

Author: Rajneesh
Source: sdn. sap. com

Analyzing Problems Using ABAP Short Dumps: Part I

ABAP 'short dump' (German Kurzdump) is a misnomer. There is nothing 'short' about an ABAP dump. Should the ABAP AS no longer be able to execute a program - because of an unhandled or unhandleable exception, a resource or system problem, or an error in coding - it may document the problem with 20 or more pages of diagnostic information.
Very often, a short dump contains not only the exact diagnosis of the problem that occurred but also the solution, or at least important pointers toward the solution of the problem. But experience has shown that developers often don't even read dumps - not even the highly useful Error analysis - much less make use of the diagnostic resources that short dumps offer.
The lack of attention to short dumps is understandable but regrettable.
Understandable because the report that your program is dumping in a customer system is about the worst news you can get. It's time to drop everything and switch to emergency mode.
Regrettable, because often developers who don't take a good look at the short dump waste a lot of time thrashing around in the debugger, trying to understand what went wrong. Taking a good look at the short dump is usually a better use of your time. And then there are the situations in which the dump is the only diagnostic resource that you have - when the dump occurred in a production system and is too sensitive to repeat, when the dump occurred several hours after the background job started, and so on.
In this pair of weblogs, we will take a quick tour through the ABAP short dump as of NetWeaver Release 7.0 EHP1, pointing out important analytic aids that it offers and how to make the best use of them.

In the first weblog, we will just get ready to analyze a dump. The weblog looks at the ABAP dump lists and how to get the most out of them, as well as at a couple of related sources of information.

Click here for Full Story

Author: Stephen Pfeiffer

Source: sdn. sap. com

Analyzing Problems Using ABAP Short Dumps: Part II

The first part of this weblog did not quite manage to open a short dump as of Release NW04s 7.0 EHP1 for display. Instead it reviewed ways to extract contextual information from the short dump lists and elsewhere.
In this second part of the web log we, in the words of W. C. Fields, grab the bull by the tail and face the issue. In a short dump, you want to answer these primary questions:

What exactly happened?
Where did it happen?
How can the problem be corrected?

We will look at the diagnostic information and aids that the short dump offers for answering these questions.

Read full story Click here

Author: Stephen Pfeiffer

Source: sdn. sap. com