Friday 18 August 2017

Developing on ABAP Application Server

In ABAP, applications are developed in Application server, not in your local file system.

What I mean is, you connect to the ABAP Application server using SAP GUI (or) from IDE like Eclipse. You create a program in the Application Server, open that program in Editor, update the program, and Activate it. Once you activate the program, the program is stored into the database and available to all other users, who has access.

Let me explain with an example.


User1 connect to the Application server and start developing the programs. Once he activate the program, it is deployed to the database.

In real-world, there are multiple users work parallely. Let me explain how it will work in ABAP.

user1 creates ‘Z_EMPLOYEE_LIST’
Suppose your organization wants to list all the employees in a report. User1 creates a program ‘Z_EMPLOYEE_LIST’.

When user1 creates a program ‘Z_EMPLOYEE_LIST’, internally it is created in Application server and gets the lock. Unless this lock is released by user1, no other user can able to modify this program.

Until user1 save the program, the program will reside in Application server main memory. Once user1 save the program system automatically place the program in central database as inactive version.


What is INACTIVE version?
INACTIVE version files are only visible to the program owner. It is only visible to user1. Other users are not able to see the source code of the program ‘Z_EMPLOYEE_LIST’.

Once user1 implemented complete program and ready to test, user1 activates the program. Once user1 activates the program, it is active and visible to all other in the system. Now other users can able to see the source code, but they can’t change. It is because the lock is still assigned to user1.

When the lock will be released on the file Z_EMPLOYEE_LIST?
Once the user closes the program ‘Z_EMPLOYEE_LIST’ from source code editor, the lock will be released automatically.

Previous                                                 Next                                                 Home

No comments:

Post a Comment