Welcome to Amrit's World of SAP

 Welcome back everyone, So we have discussed how to create a transaction code in last blog and we will continue with database utility in this blog. Database Utility :- The database Utility acts as a interface between ABAP dictionary and the database. The purpose of database utility is that, it allows you to edit database objects. You can call the database utility from the initial screen of the ABAP Dictionary with Utilities → Database Utility or we can use the transaction code SE14. Requirements :- We have to change the length of the domain order number. Suppose, we have to increase the length to 12. As soon as, I will try to activate the domain, a pop up screen will appear showing where our domain is being used. Click on continue, we will get 2 errors, because our domain is being used in 2 tables as shown above. So, for this kind of purpose we use database utility. Step 1 :- Go to se14 Step 2 :- give the header table name and click on edit. S

  Welcome back everyone, So basically we were discussing about lock objects in our previous blog. You have noticed, I have been using the term transaction codes very often, In this blog we will learn how to create transaction codes for tables. How to create a transaction code ? We use transaction code SE93 for creating our own transaction codes manually. Creating transaction code for our Order Header Table:- Step 1 :- Go to transaction code SE93. You will see a screen, same as below Step 2 :- Give a name and click on create button. Step 3 :- Provide Short description and for creating transaction code for table ( In Start object select the radio button → Transaction with parameters ( parameter transaction ) ). Note :- We will discuss and use the remaining radio button, in the nearby future in other upcoming topics. Step 4 :- Press enter. Step 5 :- Since, we want to open SM30, whenever we open our TCODE , therefore provide SM30 in transaction field and cl

 Welcome back everyone, so basically we were discussing about Single Record buffering and we had discussed that in single record buffering at a time, only single record will pass. Full Record Buffering :- In case of full buffering, full table records load into the buffer at a time. When to use :- Tables that are best suited to full buffering are frequently accessed and rarely changed. A table which stores transaction data should not be opted for full buffering. Advantage :- There is a significantly reduction in number of database access. Disadvantage :- This type of buffering requires more memory on application layer. Practical Implementation of Full Record Buffering :- Step 1 :- Open our order header table in change mode. Step 2 :- Go to technical settings, and select fully buffered → activate the table. Step 3 :- At this moment, if you go to transaction code al12 and open the buffer. Step 4 :- you will see nothing will be in the buffer. Step 5 :- Open the

 Welcome back everyone So basically we already have created database view and projection view in our previous blog and in this blog we will see about Maintenance view and help view. Maintenance View Creation :- Note :- We can only create help view, if not more than one record should exits in dependent/secondary tables. Step 1:- Go to se11 and select view radio button and give some name for maintenance view and click on create button. Step 2:- Select maintenance view radio button and press enter → give short description. Note:- Since in our order item table we have multiple data for same data in order header and since maintenance view does not allow presence of multiple data in secondary table. Therefore, we will be creating two more tables with the following data in them, and then we will start with the maintenance view.      So, basically create the two tables, I don’t think it will cause any problem to anyone because we already have discussed in details how to create a ta