Optimized performance of background jobs are a prerequisite in live production environments. No matter how optimized the ABAP code is, over a period of time due to accumulation of large amounts of data in tables, programs can go into a long run. In such instances, index definitions needs to be checked. If the query is such that it cannot use the primary key, creation of a secondary index can be considered. There are instances when the SAP Cost Based Optimizer (CBO) over-rides the secondary index and continues to do a sequential read on the table. At such times, coding an ABAP hint that would force the CBO to use the secondary index can be used.