COVP
(key fields that bring back results quickly)

Cost Overruns

View field	Key sample values	Table	Field name	Type	Length
PERIO	11	COEP	PERIO	NUMC	3
LEDNR	00	COEP	LEDNR	CHAR	2
OBJNR	PR00003078 (6453100)	COEP	OBJNR	CHAR	22
GJAHR	1998	COEP	GJAHR	NUMC	4
WRTTP	31,03-12	COEP	WRTTP	CHAR	2
VERSN	000	COEP	VERSN	CHAR	3
KSTAR	422342 (Costs in excess)	COEP	KSTAR	CHAR	10

This must be using the secondary index on COEP (COEP______1)

MANDT	CLNT	3
LEDNR	CHAR	2
OBJNR	CHAR	22
GJAHR	NUMC	4
WRTTP	CHAR	2
VERSN	CHAR	3
KSTAR	CHAR	10
HRKFT	CHAR	14
PERIO	NUMC	3

VRGNG	CHAR	4
PAROB	CHAR	22
USPOB	CHAR	22
VBUND	CHAR	6
PARGB	CHAR	4
BEKNZ	CHAR	1
TWAER	CUKY	5

It is a very fast retrieval. Would it be as fast against COEP? Yes. The view is not necessary.

I was told that the fields in a where clause should include all the fields in an index. This is clearly not necessary with this table/index. I suspect that it depends on the index and where clause. We would want the most selective parts of the index to be in the where clause. It is curious that HRKFT is not used and PERIO is used in this fast retrieval. I will test to see if there is any efficiency lost in skipping this field. It seems to be wicked fast even if PERIO is not there.

Physical Plant Problem

View field	Key sample values	Table	Field name	Type	Length
KOKRS	MIT	COEP	KOKRS	CHAR	4
BELNR	600000000-699999999	COEP	BELNR	CHAR	10
PERIO	5-7	COEP	PERIO	NUMC	3
LEDNR	00	COEP	LEDNR	CHAR	2
OBJNR	PR*	COEP	OBJNR	CHAR	22
GJAHR	1999	COEP	GJAHR	NUMC	4
WRTTP	31,03-12	COEP	WRTTP	CHAR	2
VERSN	000	COEP	VERSN	CHAR	3
KSTAR	0000600600-0000600604	COEP	KSTAR	CHAR	10
VRGNG	KOAO	COEP	VRGNG	CHAR	4

Library Invoice Load Problem

View field	Key sample values	Table	Field name	Type	Length
PERIO	08	COEP	PERIO	NUMC	3
LEDNR	00	COEP	LEDNR	CHAR	2
OBJNR	OR000002781500	COEP	OBJNR	CHAR	22
GJAHR	1999	COEP	GJAHR	NUMC	4
WRTTP	31,03-12	COEP	WRTTP	CHAR	2
VERSN	000	COEP	VERSN	CHAR	3
KSTAR	890100 (Revenue)	COEP	KSTAR	CHAR	10