Most unnoticed functionalities in SPRO

As a functional consultant, we might have seen SPRO screen day in and day out. But, many of us may have missed to notice, there are many additional functionalities available in SPRO. Usually, we just run to the node where we wish to do the changes, complete required changes and rush for testing.

Through this blog, I would like to bring to the notice of fellow community members about many unnoticed functionalities available in SPRO.

1. How to find the list of tables that are updated through particular SPRO node?

Place cursor on the node where changes are being done and go to below path in SPRO.

In next screen, double click on underlying view.

Note: Usually last 4 letters of IMG activity ID is transaction code for that node.

Select other view and double click on Piece list option.

Next screen shows the list of tables that are updated under this node.

2. How to Search in SPRO?

Looks pretty straight forward option right? I am sure everybody must have already used this option.

But did you notice “Text Index info” in the search popup?

SAP search engine uses Indexing concept. We can correlate this to normal text book index. Index have the address number of a topic like page number. Similarly, SAP stores the database address of the nodes of SPRO. When search is done, system would first go to this Index data and find the position of the node in SPRO path. Then respective node would be pointed out. If multiple addresses are found for the search word, complete list is displayed in popup. We can further navigate by selecting appropriate item.

System has the information on when was last index generated. If we have implemented some patches/upgraded system to next version, we may face issues with search engine. In this case, just regenerate the Index. It is suggested to do this activity in background with the support of BASIS team.

3. Expand all:

This option will expand all the sub-nodes of a particular parent node.

4. Position:

This helps in scrolling down a node to topmost row. Place the cursor on the node and click on position. This action moves the node to topmost row.

5. Change logs:

Precondition for this functionality is, change logs are active in system. For the reasons related to performance and database optimization, change logs are usually activated in development system only.

This displays list of all changes done in the node with details like date, time, change done by user ID etc.

Enter appropriate selection parameters in next screen and execute.

If the node has multiple tables (How to find was discussed earlier), select the required object in the popup and proceed. Output would show the changes done in the selected period and object.

6. Additional information:

Document name: This is the name of the documentation key with which IMG documentation is stored.

IMG activity: Each node of SPRO is stored with the key field as IMG activity name. This is the unique key to identify a particular node in SPRO.

Attributes: Each SPRO node has different attributes. These attributes are stored with key field attribute key.

E.G.: If a node is critical/non-critical, mandatory/optional, is it country specific etc.

Maintenance object: This shows the name of the maintenance object which has the information of list of tables/views which are updated through that node.

Enhancement ID: This is used to enhance SPRO/add any custom paths in SPRO.

E.G: If you want to add some custom add-on to SPRO paths, you can enhance it with this option. Check t-code S_IMG_EXTENSION for more details.

Release notes: By selecting show notes, we would see small ‘i’ Icon beside the SPRO node. Clicking this would list the component names and respective release version through which this node was created/changed.

Other attributes:

Below attributes are self-explanatory. Name itself says what that option stands for.

BC Sets:

BC sets (Business configuration set) are used for collecting the customizing settings. They can also be used for a group  rollout, where the customizing settings are bundled by the group headquarters and passed on in a structured way to its subsidiaries. SAP has delivered BC sets for some standard industry processes. We can create custom sets as well. Please check out below WIFI which has detailed information about this.

http://wiki.scn.sap.com/wiki/display/Basis/Business+Configuration+Sets+(BC+Sets)+and+their+use

Business add-ins: This option would display, if there are any BADIs available for a node.

Translation: This is used for maintaining translations for the text fields available in a node (If applicable).

Hope you enjoyed reading this and got to know some new things 🙂

Please feel free to share your feedback.

Thanks,

V V