6.20.2009

ABAP Tips - Help Guide

On request from our regular visitors. From this edition (Today), I am going to provide you a complete list of ABAP TIPS and GUIDE in a ZIP Format and easy to download and read at your convenience.

This is made for your convenience.

ABAP Tips - Click to Download

Hope you all appreciate. - If YES, Leave your comments. Which will encourage me further.
read more...

Selecting Sessions and Reading the Session Display

Use

The heart of the tool for managing batch input sessions is the session list. The management tool offers lists by status, and you can select lists according to other criteria as well.

Prerequisites

Start the batch input management tool: Select System ® Service ® Batch input ® Sessions. Alternate: Enter transaction SM35. Both paths take you to the session overview of the batch input system. transaction SM35.

Procedure

On the main menu, you can select sessions using any or all of the following criteria:

* session name

* date on which the session was generated (entered into the session queue)
* user who generated a session

* session status

In the session overview, you can start, analyze, or delete sessions in the queue. You can also display statistics on the transactions in a session and view the session log. All sessions generate a log when they are run. From the session log display, you can take further actions, such as displaying more information on the messages in a log.

Reading The Session Queue

The information in the session queue includes the following:

* Creator:The user who generated the session.

* Date and Time:
The date and time when a session was generated (entered in the session queue).

* Lock date:If a session is locked, this column shows the date upon which the system will release the session. A locked session cannot be started.
* Authorizations user: The user under whose authorizations the transactions in a session are to be run. When the session is run, it can execute only those transactions and functions for which this user has authorizations.
* Status: The status of a session (new, processed, contains errors, as shown in the tabs in the overview).

* Tran. and Screen: The number of transactions and screens, respectively in a session.

You can display statistics on the transactions in any session by marking the session and using the Statistics function.

Session Sorting and Status

Sessions in the session queue are sorted by date and time of generation and are grouped in different lists according to their status.

Possible statuses are as follows:

* new and not yet processed

The Tran. and Screen fields in the display show how many transactions and screens, respectively, the session contains.

* held in the session queue because of errors in transactions (Errors in sessions)

Transactions that contained errors are aborted; all correct transactions are processed. The Tran. and Screen fields in the session display show how many incorrect transactions were found in the session.

You can restart a session and correct the erroneous transactions with one of the interactive execution modes offered by the batch input system. For more information, please see Correcting a Session.

* processed

For further information on a session that has been successfully run, you can display the log generated by the session. All completed sessions generate a log. You cannot run a completed session a second time.

Only sessions that were generated with the KEEP option are held in the queue after processing. Other sessions are deleted after they are successfully completed.

* in generation

You will usually see this status only if you happen to display the queue while a session is being generated (entered into the session queue).

You can also encounter this status if a system failure has interrupted the generation of a session. If you suspect that a session has been interrupted, please see Releasing and Restarting an Interrupted Session for more information.

* in process

You will usually see this status only if you happen to display the queue while a session is being run.

You can also encounter this status if a system failure has interrupted the execution of a session. If you suspect that a session has been interrupted, please see Releasing and Restarting an Interrupted Session for more information.
read more...

Batch Input Sessions : Processing Sessions Automatically

Use

In most cases, batch input sessions can be processed automatically. It is not necessary for a session to wait until a system administrator explicitly starts the processing of the session.

This section explains how to have sessions started automatically soon after the session has been generated in an R/3 System.


Prerequisites


The ABAP program RSBDCSUB must be scheduled as a periodic job in the R/3 background processing system. RSBDCSUB checks for and starts any batch input sessions that have not yet been run. It schedules such sessions for immediate execution in the background processing system.

Procedure

Schedule RSBDCSUB to run periodically in one or more background jobs.

If you have regularly scheduled batch input runs, you can schedule separate jobs for each of the scheduled data transfers. The start time for the RSBDCSUB job can be set according to the batch input schedule. And you can use a variant to restrict RSBDCSUB only to the batch input sessions that you expect.

With RSBDCSUB, you can use all of the selection criteria offered on the batch input main menu to select sessions to run:

* session name

* date and time of generation

* status: ready to run or held in the queue because of errors

Result


Batch input sessions are started automatically rather than by hand. The RSBDCSUB program can be set up to start all sessions that arrive in an R/3 System, or it can be fine-tuned to start only batch input sessions that you expect.
read more...