Show TOC

Process documentationAnalyzing Objects Locate this document in the navigation structure



To analyze objects in the UCIA result list, proceed as follows:

  1. Filter the objects, for example by using the features in the navigation menu, (e.g. by object type or severity and usage of sorting options). When you filter by object type, you can also restrict the selection by severity. This allows you to determine the SAP objects that are impacted by the upgrade. You can use this information to calculate the total adjustment times for all objects affected by the upgrade. The total adjustment time corresponds to the total effort estimation for adjusting the custom objects so that they work for the new release.

  2. In the Detailed View, you can select an entry in the column Reference Object Name to navigate to the customer code where the SAP object is called. This feature is only available for customer objects such as classes, function groups, and programs.

  3. In the Detailed View, you can see the adjustment times that you specified during the activity Maintain Adjustment Times. In the Compressed View, you can see the columns Planned Adjustment Time and Actual Adjustment Time. You specify the time taken to adapt a customer object in the Actual Adjustment Time.

    Note Note

    If your control system is a solution manager system then you can only specify the actual adjustment time once for each customer object. When you save an adjustment time for a customer object that is part of more than one business scenario, the adjustment time it is reflected across all business scenarios for that customer object.

    End of the note.
  4. In the Detailed view, you can view how many references of an SAP object exist to other customer objects. This allows you to determine the detailed impact of change for the SAP object and communicate these details to the processors of the other customer objects that SAP object refers to. This approach saves time, as the other authors do not have to determine the detailed impact of the change. If you face a scenario that involves hundreds of customer objects that have different authors, this approach saves a significant amount of time.

    To do this, first sort the list by column Ref Object Name, then highlight the row of the SAP object and choose Remote Comparison. When you have specified he RFC destinations for the comparison, the system returns the comparison result according to the standard version comparison.

    Note Note

    The RFC user to the remote system must be of type Dialog. You can only compare one referred SAP object at a time.

    End of the note.
  5. For every custom object, you need to decide if this object must be adjusted in the course of the upgrade or if this is not necessary, for example because the object is not business-critical and the adjustment work can be postponed to a later point in time, or because the object is obsolete. Obsolete objects should occur only if no clearing analysis has been performed prior to the UCIA. For every customer object that must be adjusted, you can assign a processor by choosing Assign Processor.

  6. Once you have assigned processors to the objects that must be adjusted, you can send a notification to them by choosing Send Notification.

  7. Every processor then accesses the result list, and can filter the objects to view the ones that they want to work with.

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

    • Comparison Result

      Custom objects can have either a direct or an indirect reference to SAP objects. In the Detailed View, you can view information about all the referred SAP objects that are changed because of an upgrade. For example if the attributes of a domain change because of the upgrade, then the column Attributes for that domain is set to X.

      Typically, objects that have the reference type Indirect are automatically adjusted during the upgrade, and objects with the reference type Direct must be adjusted. You can view the reference type (direct or indirect) in the column Directly Impacted. A space indicates an indirect reference.

    • Where-Used List

      For customer and SAP objects, you can use the Where-Used List to check whether any references exist for objects. You can use the Where-Used List for customer objects in the Compressed View, and for SAP objects in the Detailed View.

    • Additional Checks

      You can execute a syntax check and a code inspector check for objects. You can implement these checks for the following objects:

      • Programs

      • Function groups

      • Classes

      • Web Dynpro components

      • Tables

      • Type groups

  9. To get an overview of the status of the project, for status reporting or otherwise, ensure that you update the status column of every custom object that you work with. You can also include a comment with the status.

    If you change the status of an object in the compressed view, the status of any referred objects does not change. If you change the status of an object in the detailed view, the status is propagated to any referred objects.

    Note Note

    You can assign a status to custom object (Not Started, Not Relevant, Completed, Uncritical and In Process). 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.
  10. As soon as the processors implement the adjustment changes successfully, the person responsible changes the status to Completed.