SAP Note
Header Data
Symptom
When you display implemented equipments on the corresponding tab page in the master record of a Technical Object (Functional location, equipment) the system might generate in longer runtimes up to a timeout.
Other Terms
IL02, IL03, SAPMILO0, functional location. IE02, IE03, SAPMIEQ0, equipment. IEL2, SAPLIEL2, IS_EQUI_IN_FUNCLOC. TIME_OUT, timeout, termination, runtime error, runtime, performance. Sub-equipment, structure, structure tab title, structure list, table-control. ILOA, ILOA~F, index, table index, database index.
Reason and Prerequisites
In the master record of the Technical Object a tab page is designated (by default or through a special view profile) that contains as a subscreen the table control with the implemented equipments. For three reasons, the selection of the equipments can be very time-consuming:
l The Technical Object has a large number of sub-equipments (generally on several hierarchy levels).
l Table ILOA has many entries; upon the individual access with fields TPLNR and OWNER, however, the system does not use suitable index ILOA~F.
l Table EQUZ has many entries; upon the individual access with fieldHEQUI, however, the system does not use suitable index EQUZ~H.
The problems with the ignored index can be recognized in the Performance Trace; they occur when the Cost Based Optimizer considers field TPLNR (or HEQUI) as not satisfactorily selective (and thus ignores the index). A missing selectivity occurs particularly when the stock of database table ILOA (or EQUZ) contains only few different characteristics of field TPLNR (or HEQUI).
Solution
First of all, make sure whether you actually need the indicated table control with regard to the provided functionality of a pure condensed overview. For example, you should bear in mind that
l the branching to the master record of the implemented equipment is not supported,
l the overview is no longer ensured in case of a large number of objects.
On the other hand, the branching to the structure list provides you with an extensive overview of the entire structure and additionally offers the possibility to branch directly to the master record of an implemented equipment. If the performance problem is caused by a large number of sub-equipments, a renunciation of the table-control will probably the only possibility to solve the problem. Depending on your release you must proceed as follows:
l Release 4.6B or higher:
Use suitable view profiles for the affected object types in the Customizing:
¡ Creating or changing a view profile for Technical Objects, which does not include the subscreen with the implemented equipments (access number 045).
514221 - Techn.object:Long runtimes when displaying implemntd equpmts
Version 11 Validity: 13.06.2003 - active Language English
Released On 13.06.2003 12:42:34
Release Status Released for Customer
Component PM-EQM Equipment and Technical Objects
PM-EQM-EQ Equipment
PM-EQM-FL Functional Locations
Priority Recommendations / Additional Info
Category Performance
Other Components
Customizing-path: - Plant Maintenance And Customer Service --> - Master Data In Plant Maintenance And Customer Service --> - Technical Objects --> - General Data --> - Setting View Profiles For Technical Objects.
¡ Assignment of the view profile to the type of the Technical Object.
Customizing-path for functional locations: - Plant Maintenance And Customer Service --> - Master Data In Plant Maintenance And Customer Service --> - Technical Objects --> - Functional Locations --> - Define Category Of Functional Locations. Customizing-path for equipments: - Plant Maintenance And Customer Service --> - Master Data In Plant Maintenance And Customer Service --> - Technical Objects --> - Equipments --> - Equipment Categories --> - Maintain Equipment Category
l Release 4.5B:
Here, you cannot define a view profile. The subscreen for the equipments can only be removed by a program modification throug which an empty screen is displayed. The corresponding changes for Release 4.5B are described in the correction instructions. If the problem is caused by the Cost Based Optimizer, you can alternatively proceed as follows: First of all you must check whether an update (as exact as possible) of the database statistics would improve the behavior. In this process, you must also check whether the use of histograms would also have a positive effect. For more information on this matter refer to OSS-note 335415. If the update of the DB statistics does not have an effect (also for histograms), you can make use one of the following options to make the index more "interesting" for the database:
l Artificial generation of a higher selectivity by creating dummy master records. An example for this is available in OSS Note 515769.
l An explicit index specification upon execution of the SELECT statement by means of a so-called "Hint" (if supported by the database). The specification occurs by means of a suitable modification of the basic program place (the ABAP select statement can be regarded at the corresponding place in the Performance Trace). An example for this is available in OSS Note 515769.
Other Attributes
Validity
Correction Instructions
References
This document refers to:
SAP Notes
HIER
IE02
IE03
IL02
IL03
Software Component From Rel. To Rel. And Subsequent
SAP_APPL 45B 45B
46B 46B
46C 46C
470 470
Correction Instructions
Software Component Valid from Valid to Number
SAP_APPL 45B 45B 396182
534746 Technical object: Performance problem for data transfer (2)
Transaction codes
This document is referenced by:
SAP Notes (4)
515769 Techn.obj.:Runtime during search for install.eqpmts (EQUZ~H)
335415 Creating and Maintaining Histograms
182463 Functional location: Performance during creation
182463 Functional location: Performance during creation
335415 Creating and Maintaining Histograms
515769 Techn.obj.:Runtime during search for install.eqpmts (EQUZ~H)
534746 Technical object: Performance problem for data transfer (2)
Top Related