Show TOC

Process documentationAnalyzing Objects


Once you have identified the objects that you want to work with, you need to determine if they are obsolete. This involves analyzing the objects.


You can follow the following procedure to analyze the objects:

  1. Identify the objects that might be obsolete for example inactive objects, objects with no reference, and so on. You can use the features in the navigation menu or the filter options to do this.

  2. Assign a processor to these objects. Usually the processor is the person that created the object. To do this, choose the Change Mode icon. Highlight the corresponding row(s) and choose Assign Processor. Enter a name, and press enter. You must use the SAP user name of the processor.

  3. To send a notification to all the processors, choose Send Notification. The system sends an SAP mail to all processors specified in the list. The mail contains further instructions about analyzing the object. Note that this feature sends a mail to all the processors in the result list.

  4. The processors can then analyze the objects by using the following result list features:

    • Where-Used List: This feature helps you to identify if other references exist for a particular object, and identify how many references exist. It can be case that the person responsible for an object is not aware of all possible references for that object. For example, consider a customer function module used by colleagues in their objects. The author of this object may not be aware of these references.

    • Remote Comparison: This feature allows the author of the program to compare the version of an object with the version of that object in another system. For example, you can compare the version of an object with the version in the production system to determine if the object versions are equal. If the two versions are different, you must examine any possible reasons for this. You can use this information as a basis for clearing decisions.

    • Status tracking: Depending on your analysis, you can change the status of the objects. You can apply a green, red or yellow status, and define any status by adding an additional comment. You must define at least one status for each color, for example green for ‘used’, yellow for ‘pending’ and red for ‘not used’. If you want to apply the same status to multiple objects, highlight the rows and choose Status. You can set the status for all selected objects.

      Note Note

      If you have assigned a status to custom objects in a previous project, you can import them to the current project (Status Takeover). This can minimize the effort required to determine the delta objects.

      End of the note.
    • Additional Checks: You can execute a syntax check and a code inspector check for objects in the remote system. You can implement these checks for the following objects:

      • Programs

      • Function groups

      • Classes

      • Web Dynpro components

      • Table

      • Type groups

  5. When you complete this analysis process, you sort the objects. For example, you can use filter determine the used objects.

  6. Note: Only Relevant if you plan to work with a UCIA project. You create a piecelist for all used objects. This piecelist is the basis for any subsequent UCIA projects.

  7. For the ‘Not Used’ objects, decide if you want to delete them or not.

  8. Once you have decided which objects to delete, you can refer to the Clearing Guide.