topic Re: MMBE sql trace in Application Development and Automation Discussions

MMBE sql trace

Former Member — Sat, 02 Feb 2008 06:44:21 GMT

I have a problem. MMBE runs fast on all materials except for one. Based on the sql trace comparison, I found, for that material, the table "EKBE" is also included in the select stmts unlike for other materials, and the fetch / open commands takes a lot of time for that "EKBE" table. Digging furthur, that select statement occurs in the function module: MMPUR_EKBE_ARRAY_READ. But I searched the websites regarding this, yet to no avail. Please help.

Re: MMBE sql trace

Former Member — Sat, 02 Feb 2008 14:24:55 GMT

Hi Tom,

SAP has forecasted performance issues with MMBE and created a rather useful FAQ note number 982345 which can be viewed from [Service Market Place|http://service.sap.com/notes].

Hope perusing through this note will help you find a solution to your performance woes.

Cheers,

Aditya

Re: MMBE sql trace

Former Member — Thu, 14 Feb 2008 09:44:57 GMT

SELECT * FROM "EKBE" WHERE "MANDT" = :A0 AND "EBELN" = :A1 AND "EBELP" = :A2 OR "MANDT" = :A3 AND "EBELN" = :A4 AND "EBELP" = :A5 OR "MANDT" = :A6 AND "EBELN" = :A7 AND "EBELP" = :A8 OR "MANDT" = :A9 AND "EBELN" = :A10 AND "EBELP" = :A11 OR "MANDT" = :A12

AND "EBELN" = :A13 AND "EBELP" = :A14

This is the sql statement seen in the beginning of sql trace list, taking lot of time when running MMBE.

Why is that, the phrase "MANDT" = :A0 AND "EBELN" = :A1 AND "EBELP" = :A2 being repeated many times in the sql statement?

At the end of the sql trace list, the sql statement SELECT * FROM "EKBE" WHERE "MANDT" = :A0 AND "EBELN" = :A1 AND "EBELP" = :A2 runs pretty fast.

Please help.

Re: MMBE sql trace

Former Member — Tue, 04 Mar 2008 03:37:05 GMT

Please help in the above query. It is urgent.

Re: MMBE sql trace

Former Member — Thu, 13 Mar 2008 05:17:16 GMT

Please help in the above query. It is urgent.