One important aspect of LiveCompare's SAP analysis is the way it distinguishes between custom objects and standard SAP objects.  LiveCompare uses a set of naming conventions based on object type to do this.  In LiveCompare 2.2, we've enhanced the patterns. Brent Halford explains the details:

LiveCompare includes an external data source called "Custom Object Naming Patterns" that is used in several workflow templates.  It is used to distinguish custom objects from SAP standard objects; if an object's name matches one of the naming patterns, it is considered a custom object.

Most custom objects have names that begin with a Y or Z, so the patterns include Y* and Z*.  However, SAP generates some objects automatically from other custom objects.  For example, a function module whose name begins with ENQUEUE_ gets generated when you define a Lock Object in SAP, so there are patterns to match these generated objects.

All LiveCompare objects are in the ICORP namespace, so there's a pattern /ICORP/* to identify LiveCompare objects as custom.

For completeness we've added a pattern to match SAP-generated names that include the ICORP namespace:  */ICORP/*.

In testing on our EC6 system, we found about 130 of these generated objects.  With the additional pattern, these objects will now be correctly identified as custom objects.