ABAP Tutorials

It is a good sample of how to create dynamic table maintenance by utilized SAP function module “STC1_FULLSCREEN_TABLE_CONTROL”.

You can use it to replace funtion of SM30/SM31 with additional benefit.
1. Because it is written in as customer program we can add additional feature, for example change history.
2. There is no need to create screen maintenance for all table because screen will automatically generated.

But, remember, this is only a demonstration of how to use STC1_FULLSCREEN_TABLE_CONTROL. Use it carefully and only for customer table (Z*).

Continue Reading…

Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.

SAP Provide three type of Lock objects.  

- Read Lock(Shared Locked) 
   protects read access to an object. The read lock allows other  transactions read access but not write access to the locked area of  the table

- Write Lock(exclusive lock) 
   protects write access to an object. The write lock allows other  transactions neither read nor write access to the locked area of the  table.

- Enhanced write lock (exclusive lock without cumulating) 
  works like a write lock except that the enhanced write lock also  protects from further accesses from the same transaction.

Type of Locks

Continue Reading…

As an ABAPer, you probably know how combursome it is to work with classical exceptions (discussed in last post), since you must handle all of them immediately after a function or method call. Beside being labourious, these mappings clutter our code and make it difficult to read.

 SAP also have Object Oriented Class based exceptions which are easy to handle and less cumbersome.

  Continue Reading…