Qry For EKBE

[Former Member]

hi all,

we're having a problem querying table EKBE using belnr, gjahr. It is taking too long. Too long we don't even bother to finish it.

Any help is appreciated.

tnx,

sid

[Former Member]

Hi SID,

Please paste the EKBE select query.

[Former Member]

hi sdn powered,

actually i tried using se11 and filled up one specific belnr and gjahr in the data browser selection screen.

[christian_wohlfahrt]

Hi Sid!

Table EKBE is for finding follow-on documents for purchase orders. If you have already the follow-on document (e.g. a goods receipt), then the preceding document already exists and is stored on header or item level directly (e.g. MKPF-XBLNR, MSEG-EBELN, MSEG-EBELP).

-> no EKBE for searching a PO

Regards,

Christian

[Former Member]

hi all,

thanks for your help. i think we're gonna use mseg-ebeln instead as christian suggests.

regards,

sid

[Former Member]

Hi,

You are not consuming full key of EKBE. i.e the problem. It leads performance problem.

Please use full key in WHERE clause of EKBE, Otherwise define secondary index on belnr, gjahr fields (As if can't consume full key).

If helps, Plz reward points.

Regards

Bhupal Reddy

[former_member181962]

Hi Sid,

EKBE has the PO History data. It makes sense to query the table with the PO Number atleast, to find the relevant history documents.

Regards,

Ravi