Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
bour-rha
Explorer
1,887

Overview


In our organizations, specific projects often arise, but we sometimes overlook the importance of effectively organizing and structuring them, especially when it comes to managing configuration tables and documentation in SAP.

While standard SAP provides the SPRO functionality for this purpose, there is an option to create a customized SPRO environment tailored to our projects. This enables us to streamline the process of populating configuration tables, eliminating the need for repetitive inquiries such as understanding how a table works or why it is being used.

This is where the transaction SIMGH becomes valuable. Its primary purpose is to manage our specific projects. SIMGH allows us to consolidate various elements within a single project, including configuration tables, ABAP programs, and related objects. This transaction greatly simplifies the maintenance, documentation, and traceability of specific modifications made in the system.

By utilizing the SIMGH transaction, we can establish our own environment dedicated to managing specific projects. This contributes to an improved organization and structure of our customization activities within SAP, resulting in enhanced efficiency and effectiveness.

Configuration

T-code : SIMGH


We create our structure for our Company











With the SAP tool at our disposal, we have the ability to incorporate our own activities and customize the system according to our specific needs.







As SAP explains, we have these 4 options:

  • Insert Structure Nodes As Subnodes :





  • Insert Structure Nodes at same Level :






  • Insert Activity as Subnode :






  • Insert Activity at same level :



 

With these 4 Options we can Organize our structure as we want with the creation of Nodes & activities.

  • Header for Activity 


For each activity we have an ID which must be unique for this activity, and Name.

  • Tab Document


we can create a Document Name :  which allows us to create the documentation for our specific table ( ZDOCUMENT_TEST ) and add all information about this activity .




  • Tab Maint.Objects


We use is to call our specific tables or programs.

The important Fields are:

Customizing object : Choose any name. Recommendation: Enter the transaction code.

If we have a table Custo:

  1. Customizing object : Table name

  2. Types : S (TABLE)

  3. Transaction : SM30 .


If we have a program that we want to run:

  1. Customizing object: IMGDUMMY

  2. Types: D ( Dummy object )

  3. Transaction: Program t-code .


And we got this structure , that we can add others activity or change position of action by drag & drop …

 


 

How we can call our SPRO ?

We must create a program with the FM 'STREE_EXTERNAL_EDIT' which allows us to call our specific SPRO . with the ID that we retrieve via this 2 options:

Table TTREET Or via SIMGH : 



 

Once we create the program, we run it, it launches our IMG ( specifique SPRO)  directly.

We can create a transaction for this program via se93.

Overall

the use of SIMGH helps organizations streamline their customization efforts, reduce confusion, and improve efficiency when working on specific projects within the SAP system. It enhances organization, documentation, and traceability, enabling teams to effectively manage and maintain customization activities related to configuration tables and associated components.

Hope you found the blog helpful, and thanks for reading.
1 Comment
Labels in this area