Move Query from One Client to Another( SQ01)

Moving Query / Infoset from one client to another.

1. Generally a query can be created in the standard area or in global area, You can find then when you enter the SQ01 Query screen. 

2. Now as a  per-requisite to download the query you need to have them in the Standard area. 

3. IN case if the query was in the global area  you need to move to the global area.
  For this select SQ01>Environment>Transports .

4. Now select the Copy Global to Standard

5. Now run in test mode and later in real mode to copy the query to standard area.

6. Now when your query is in the standard mode then again go to the environment   and now you will find the download button. with this provide the required information to the Infoset / Query and download to the local server

7. After this go to the target client and then set the import area as standard area.
8. Import the same in this step.
9. Assign them to the user group.
10. Execute.

Note: This will address your requirement and not intended to replicate all the steps. for any doubts and query leave a comment.

User Exit – Identification Simple method.

Many times when we are not able to cater a standard solution for the customer requirement, then we tend to look for User exit, Badis, etc.

If you like to analyze what user exits are available and what logic can be used then the below details will help you

1. Identifying the User exits

1.1. One of the easiest way to identify the user exits is to use the T.code SMOD

1.2 Go to T.Code SMOD

1.3. Now you need to click the help button or enter F4 key

 1.4. Next select the SAP application(Module) relevant for you

1.5.Now you will be able to select the exit and one exit can have one or many components.

 1.6. The required logic can be build inside the Function module.

2. To check the logic, for already implemented user exits, you can use the SE37 , fill the user function module name  and look for the code.

SE03- Analaysis of the Configuration

When we work in the SAP project or support , during the configuration we will be interested to see the configurations done for the same objects.

Few of the Configuration tables has history , this will help to trace them. 

In case if we do not have the history of the tables then we can use this nice transaction to find the details of the configuration made for that particular object

T.code: SE03

* Enter the T.code SE03
* select the “Search for object in the Requests/ Tasks”

* Once you select the above said option you will find the new screen like below.
* Post that you can find the object.
* You need to only enter the object name and provide your table details against the same.
* The execute

Now you will find the results with the configurations which are having the details.

SAP- Enhancment Package

Earlier, People used to discuss on the version of SAP like 4.7 or ECC  then ECC5 /ECC6 etc.
But currently the trend is about what EHP levels we are exposed and how much new functions we are aware of.

What is EHP ?
SAP delivers all the new functions that are delivered for different modules in a one single package called EHP.

So when you upgrade to the EHP 5 to EHP6 technically all the new EHP6 functionalities will be made available in the system

But there are instances that few functions needs to be activated in the Business Framework to make it work. This is because not all the new functionalities in the EHP6 will be applicable to the business.

To know about the new functions in each of the EHP kindly CLICK HERE.

This link will take you to the screen like below and from there is it self explanatory.

Do leave a comment of what lates EHP levels you are working and what functionality is being used by you.


SM36 – Language key

When we work in any global project engagement we will have many jobs running for different countries.

In such condition when any new job is created / scheduled importance is to be given to the language key in the Job creation step.

this will ensure that the users receives the text in the local language.

In case of global report , it is better to maintain the common language.

Application server ( Al11) File Download and Upload

Often we will be using the application server to Upload the file or to download the files from the SAP application server.

There are 2 standard program which support this process.

1. Download File:

* T.code: CG3Y – This is used to Download the file from the application server
* The below 2 datas to be entered:

Source file on application server : This is the patch in which the file has to be read.

Target file on front end  : This is the presentation server ( P/c)  where the data has to be written.

2. Upload File: 

* T.code : CG3Z this is used to Upload the file from the Presentation server

Source file on front end:   Define  path from  which the file has to be read.

Target file on application server  : Define the path to the application server  where the data has to be written.

You can use the T.code AL11 to see the data in the  application server. 

FILE – Logical File Path Vs Physical File Path

Many times we work with the logical file path and also physical file path. I like to make this post to have a over view on both the Path.

You should be aware of the Transaction code: FILE.

This is the T.code which help you to map both of them

Logical File Path: 
1) This is not physical, it is only a representation of the physical path. Generally the physical path will have the folder representations so to make it simple it is being used.

Physical File Path:
1) This represent the details of the folders/file which can be seen on the application server.

This. FILE t.code helps to map you between them and also other functionalities.

Hope this helps to start with the T.code..