10-11-2007 5:50 AM
10-11-2007 5:53 AM
Hi
It is the Run time Environment on which the ABAP programming runs
for any programing languagae it will be there like JAVA run time environment.
ABAP programs run in the SAP application server, under control of the runtime system, which is part of the SAP kernel. The runtime system is responsible for processing ABAP statements, controlling the flow logic of screens and responding to events (such as a user clicking on a screen button). A key component of the ABAP runtime system is the Database Interface, which turns database-independent ABAP statements ("Open SQL") into statements understood by the underlying DBMS ("Native SQL"). The database interface handles all the communication with the relational database on behalf of ABAP programs; it also contains extra features such as buffering of frequently accessed data in the local memory of the application server.
Regards
Anji
10-11-2007 5:53 AM
Hi,
Abap Processor which interprets the code which we have written and
gives the output for our code.
Assign points if useful.
10-11-2007 5:54 AM
hi,
abap processor is a component that executes the processing logic of an ABAP program and communicates with the database interface.
regds,
ritika malhotra
10-11-2007 6:00 AM
Hi
<b>ABAP PROCESSER</b>
ABAP Runtime Environment (BC-ABA)
Component that executes the processing logic of an ABAP program and communicates with the database interface.
Component of the ABAP runtime environment that executes ABAP programs.
Superordinate term for:
Selection screen processor
Reporting processor
List processor
The screen processing is controlled by the screen processor.
10-11-2007 6:08 AM
When you run an ABAP program, you call its processing blocks. ABAP programs are controlled from outside the program itself by the processors in the current work process. For the purposes of program flow, we can summarize the screen processor and ABAP processor into the ABAP runtime environment. The runtime environment controls screens and ABAP processing blocks. It contains a range of special control patterns that call screens and processing blocks in certain orders. These sections are also called processors. When you run an ABAP program, the control passes between various processors.
In the R/3 System, there are various types of ABAP program. The program type determines the basic technical attributes of the program, and you must set it when you create it. The main difference between the different program types is the way in which the runtime environment calls its processing blocks.
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
When you run an application program, you must call at least the first processing block from outside the program, that is, from the runtime environment. This processing block can then either call further processing blocks or return control to the runtime environment. When you start an ABAP program, the runtime environment starts a processor (dependent on the program type), which calls the first ABAP processing block. An ABAP program can be started either by the user or by the system (for example, in background processing), or through an external interface (for example, Remote Function Call).
There are two ways of allowing users to execute programs - either by entering the program name or by entering a transaction code. You can assign a transaction code to any program. Users can then start that program by entering the code in the command field. Transaction codes are also usually linked to a menu path within the R/3 System.
01-08-2008 5:15 AM
ABAP processor is an interpreter which processes your programs and communicates with the database layer . it handles all the operations between the application layer and the database layer