How to correct internal memory issue

[Former Member]

This is related to the standard SAP program SAPRCKM_MR11 in which there is one include RCKM_MR11F01 which contains a select statement :

SELECT *

INTO CORRESPONDING FIELDS OF TABLE t_bhistory

FROM v_ckmlgrir

WHERE bukrs EQ p_bukrs

AND ebeln IN r_ebeln

AND ebelp IN r_ebelp

AND lifnr IN r_lifnr

AND ekorg IN r_ekorg

AND ekgrp IN r_ekgrp

AND werks IN r_werks

AND bedat IN r_bedat

AND bsart IN r_bsart

AND bstyp IN ht_bstyp

AND vgabe IN ('1', '2', '3') "Wareneingang/Rechnung/Nachbel.

AND loekz_k NE 'L' "Loeschkz. Bestellkopf

AND loekz_p NOT IN ('L', 'S') "Loeschkz. Bestellposition

AND ( frgrl EQ space "Freigabe unvollständig

OR frgrl IS NULL )

AND ( memory EQ space "Bestellung noch nicht komplett

OR memory IS NULL ) "falls Feld nicht initialisiert

AND ( xwoff EQ space "Wertbildung offen

OR xwoff IS NULL ) "falls Feld nicht initialisiert

bei Dienstleistungsbestellungen werden mehrfach kontierte

Bestell-Pos. gegen das WE/RE-Konto gebucht, deshalb dürfen

mehrfach kontierte Pos. nicht generell überlesen werden.

AND vrtkz EQ space "keine Mehrfachkontierung

AND wepos EQ 'X' "Wareneingang wird erwartet

AND repos EQ 'X' "Rechnung wird erwartet

AND weunb EQ space "Wareneingang unbewertet

AND stapo EQ space. "Item is not statistical

There is one job FMT612P which contains this standard program and the job is going to abend

because of the select statement given above which is because of some memory issue with the internal table t_bhistory, please give us a suggestion how we can avoid the same.

[Former Member]

This is related to the standard SAP program SAPRCKM_MR11 in which there is one include RCKM_MR11F01 which contains a select statement :

SELECT *

INTO CORRESPONDING FIELDS OF TABLE t_bhistory

FROM v_ckmlgrir

WHERE bukrs EQ p_bukrs

AND ebeln IN r_ebeln

AND ebelp IN r_ebelp

AND lifnr IN r_lifnr

AND ekorg IN r_ekorg

AND ekgrp IN r_ekgrp

AND werks IN r_werks

AND bedat IN r_bedat

AND bsart IN r_bsart

AND bstyp IN ht_bstyp

AND vgabe IN ('1', '2', '3') "Wareneingang/Rechnung/Nachbel.

AND loekz_k NE 'L' "Loeschkz. Bestellkopf

AND loekz_p NOT IN ('L', 'S') "Loeschkz. Bestellposition

AND ( frgrl EQ space "Freigabe unvollständig

OR frgrl IS NULL )

AND ( memory EQ space "Bestellung noch nicht komplett

OR memory IS NULL ) "falls Feld nicht initialisiert

AND ( xwoff EQ space "Wertbildung offen

OR xwoff IS NULL ) "falls Feld nicht initialisiert

bei Dienstleistungsbestellungen werden mehrfach kontierte

Bestell-Pos. gegen das WE/RE-Konto gebucht, deshalb dürfen

mehrfach kontierte Pos. nicht generell überlesen werden.

AND vrtkz EQ space "keine Mehrfachkontierung

AND wepos EQ 'X' "Wareneingang wird erwartet

AND repos EQ 'X' "Rechnung wird erwartet

AND weunb EQ space "Wareneingang unbewertet

AND stapo EQ space. "Item is not statistical

There is one job FMT612P which contains this standard program and the job is going to abend

because of the select statement given above which is because of some memory issue with the internal table t_bhistory, please give us a suggestion how we can avoid the same.

[Former Member]

Hi Basus1,

This is one of SAP standard program. So do one thing you could ask to your Basis guys to check the Support Version. If it needed then update.

Thankx & Regds,

Rakesh Kumar

Edited by: Rakesh Kumar on Jun 1, 2009 1:44 PM

[Former Member]

Hi,

I am also facing the same issue. We had copied this report into a custom report and are trying to improve performance by breaking the view into separate queries on EKKO, EKPO and EKBE.

Can someone advise the best way to deal with this view v_ckmlgrir or a best approach to break down the view into separate queries.

Thanks

Edited by: Shreyas Shrikant Kulkarni on Jun 29, 2009 4:56 PM