Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Orders by VDATU

Former Member
0 Likes
1,164

I have a select-option for VBAK-VDATU.  I want to simply get all the orders that have a certain range for the requested delivery date.  Doing a simple (SELECT vbeln FROM vbak WHERE vdatu IN rvdatu) is really slow.  Does anyone know of a faster way to get this (either it be a view, etc.) without adding an index to VBAK?  I've looked for quite some time, and just can't find anything.  Any help would be appreciated.

Thanks,

CD

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
876

Read SAP Note 185530 for how to do efficient data retrieval for reporting for SD.  It contains references to SAP's proprietary index tables.  Use of these, or the search help tables or views, can be utilized for very rapid retrieval of orders, deliveries, etc.  IMHO, any new SD/LE report should begin with a review of 185530 for possible data sources....Once you have a pick list from these tables, or perhaps a join, you can proceed to populate the remaining data easily.

I would always advise against adding indices to SD  tables, because of the sheer number of other data sources that can be joined to these tables.  Pick the VDATU field in VBAK, do a where used for views, match codes, etc..  You'll get back a useable list of options, but also check 185530.

2 REPLIES 2
Read only

Former Member
0 Likes
877

Read SAP Note 185530 for how to do efficient data retrieval for reporting for SD.  It contains references to SAP's proprietary index tables.  Use of these, or the search help tables or views, can be utilized for very rapid retrieval of orders, deliveries, etc.  IMHO, any new SD/LE report should begin with a review of 185530 for possible data sources....Once you have a pick list from these tables, or perhaps a join, you can proceed to populate the remaining data easily.

I would always advise against adding indices to SD  tables, because of the sheer number of other data sources that can be joined to these tables.  Pick the VDATU field in VBAK, do a where used for views, match codes, etc..  You'll get back a useable list of options, but also check 185530.

Read only

0 Likes
876

Thank you for the reply.  I looked at the tables and it did help me in some other projects, but I couldn't find a good place to search via VDATU there.  However, there was a Z-table that another coder made awhile back that did have VDATU indexed.  Even though it's not an efficient way of doing things, it fits what I need.  Thanks again.

CD