Note 736410: Objects mapped to SAP Application Components

I have been asked many times if I could tell what functional area a transaction, program, table etc. belong to. Each time I did a short onsite or online demo for clients I work as a virtual consultant and created a short documentation. Now, that I have setup a blog, I thought it would be a good idea to document this here so that I can just reference it via a hyperlink.

To look up the application area of an object, use transaction SE11 and enter the object you want to look up. (If you want to do this for a transaction, follow a similar procedure with transaction SE93, for ABAPs use SE38 and so on.

Now, let’s us focus on SE11 and how to find what application area a specific table has been assigned to, in this example table MARC. Click the ‘display’ button and select the ‘Attributes’ Tab:


By double-clicking the package from the attributes screen, you will be taken to the Package Builder screen where the Application Component is visible:


On the package builder screen, you can see to what Application Component the Package belongs to and also what Software Component the package belongs to.


You can follow the very same procedures for Reports, Function Modules, Transactions etc.

Another example for transaction ob08 via SE93:


The package SFIB is mapped technically to application component BC-SRV-BSF-CUR:


You can whip up a query or ABAP to get this information neatly listed in a report:


You can purchase the ABAP Query that lists the application component of objects for US$ 75.00 – 100% with 30 days money back guarantee!

By clicking the button below, I agree with the Terms & Conditions.

Note: 742767: e-Mail Notification for User Expiration

You have setup a procedure where contractors / temporary workers are limited to x number of days to make sure that these users won’t be active for ever. The downside of this procedure is, that someone needs to keep track on these user-ID’s before they expire so that access can be extended ahead of time to make sure users are not impacted.

Best case scenario would be that the access to SAP is in synch with the network ID and communication is setup so that everyone is informed in a timely manner about the upcoming expiration.

However, in many instances this is not the case.

We have setup a InfoSet query and procedure that will send an e-mail with a list of users expiring in x days in PDF format to helpdesk or SAP Security team so that necessary action can be taken to extend or terminate the user-ID. Please note, that this procedure could also be used to generate a list of users that have last logged on 90 days ago.

In order to follow this procedure, you need to have an adequate query or report and setup a printer device as PDF printer with capability to e-mail the output to a specific e-mail address.

Setup a variant that captures the expiration date (or last logon date) for a given time period:

a) User-ID expiring in x days

b) user logged on last time 90 days ago

Once you have setup a (transportable) report variant, you can schedule a background job that runs on a daily basis. Make sure you define the output device as PDF printer and for ease of use, add a title that will show up in the subject line of the e-mail you generate.

Once the report has been scheduled, the support team or helpdesk will get an e-mail with the list of users to be taken care of.

The attached PDF file will contain all the users that will expire (or have not logged on), depending on the purpose of your background job:

If you want to purchase the code (ABAP Query)  that contains additional fields, such as Single Sign-On information and more you can purchase it now for only US$ 75.00 with 100% 30 days Money Back Guarantee!

By clicking the button below, I agree with the Terms & Conditions.