SAP application component browser custom tool, Check application component hierarchy of any object

Posted by -

As part of the custom tools series, today's post is about a tool that is helpful to both functional and technical counterparts.

Have you ever wondered, which table or t-code belonged to which application component in SAP?
Recently, I did and thought maybe others want to see that as well. But first,

What is an application component?

An application component is defined as a modular, deployable, and replaceable part of a software system that encapsulates its behaviour, data and exposes these through a set of interfaces. 

In other words,

In SAP, all sales and development related functions would be part of the SD application component, similar to other functions such as MM or LO(logistics).
Now, coming back to the tool.

Here is what the input looks like:
SAP application component browser Input screen

You can input the application component name or an object name. 
The other input defines what type of objects you want to browse or fetch.

Example:

I want to know where the MARA table belongs.


Execute the report:

As you can see,
MARA is part of the MG package under the LO-MD-MM Sub hierarchy under the LO-MD sub-hierarchy under the LO(logistics) hierarchy.
Cool, isn't it.
 
You can just browse all of the hierarchies by leaving the input object name blank.
The output would be something like this:

Expanding the node will give you all the hierarchies which are expandable.


One more example:

I want to know what all objects are under the ME package.

Input:


Output:


Expanding the ME folder:



The list of object types is controlled via input on the screen:



 Source: Application Hierarchy browser
or copy-paste the below code to a report and run:

Use the tool as it is or modify it to suit your needs.

As always, hope you like the post and use the information in your day to day work.

Popular posts from this blog

ABAP read excel(.XLSX) file to internal table in ABAP using CL_FDT_XL_SPREADSHEET

Posted by -
You are given a requirement to upload data to a custom DB table where the user provides you with the file path of the excel on his PC and the report loads the data from it to the Custom table. For experienced Abapers, the requirement is quite straightforward, except that the user wants to upload an XLSX file. There are not many options to read data from XLSX/XLS file. The TEXT_CONVERT_XLS_TO_SAP  function module is one of them but is a performance killer and uses OLE. In this post, I wanted to showcase How we can read data from the XLSX files using CL_FDT_SPOREADSHEET class. Let's start with uploading the file. Now that we have the file in xstring table, let's pass it to CL_FDT_XL_SPREADSHEET to get its object reference. From the object reference, we can retrieve each worksheet data. The data is returned in the form of an anonymous data object which can be dereferenced into a field symbol and passed to the target internal table. Below is the cod
Read more

ABAP convert internal table to excel (.xlsx) format and Send email or download

Posted by -
Reporting is incomplete without file interfacing. Sometimes the requirement is to send a file via email or download it to a PC. but what to do when the user requests the file in XLSX format? In today's post, I am sharing how to convert an internal table to .xlsx format and then send it to a PC or email. One of the quickest ways I found it been done is using SALV classes. Below is the Code snippet Now once you have the xstring with you, simply pass it to relevant libraries to handle the output. Downloading to PC: Sending via Email It's that simple. Hope you like the post and use it in your day to day work.
Read more

Application Logging in ABAP

Posted by -
Image
Whether you are working with integration or a critical application or a complex report, logging becomes an obvious choice and activity.  Traditionally, Abapers have been logging information using a custom DB table defined specifically for a particular application. While useful, The approach has some flaws,      - Every application needs to have its own logging table      - Record purging/archiving needs to be set up in order to make sure old records are either deleted         or archived.      - There is no reusability of either the setup or the logic to log. With the introduction of Application Logging from SAP, the traditional approach can be left out.  In this post, I will be talking about how we can leverage the SAP application Logging Library to make logging easy. What is an application log? An application log is a rich type log. It contains information like User, Time, Expiry date of the log along with the actual message raised by the
Read more