Skip to Content
0
Former Member
Sep 03, 2009 at 12:49 PM

ERP EHP4 causing dump when posting invoice in MIRO

81 Views

I originally posted this in the MM forum but was advised to move it here.

We just implemented ERP EhP4 w/SAPAPPL603 and are now getting a dump when using MIRO to posting a vendor invoice against a PO. The error seems to involve new logic for multiple account assignment introduced with this EHP. The dump is in include LMRMBWF02 of SAPLMRMBM, and indicates that data object S_MCRBPO does not contain component XHISTMA. The lines in LMRMBWF02 are (starting at 772):

FORM bw_read_co_history_dyn_sub USING event TYPE bwmode

s_index_mcrbpo TYPE eval_iv_index_key_s

s_mcrbpo TYPE mcrbitm

CHANGING s_mcrbco TYPE mcrbco.

DATA: s_ekbe LIKE ekbe,

s_ekbz LIKE ekbz,

s_ekbz_ma TYPE ekbz_ma, "MAA EhP4

s_ekbe_ma TYPE ekbe_ma, "MAA EhP4

f_arewr TYPE ekbz-arewr, "MAA EhP4

f_areww TYPE ekbz-areww. "MAA EhP4

CASE event.

WHEN c_recompilation.

IF s_mcrbco-xunpl = space.

  • Not for unplanned account assignments

IF ( s_mcrbpo-exkbe = 'X' ).

  • Read PO history for goods item

IF s_mcrbpo-xhistma = space. "MAA EhP4

...with the last line being the culprit. The actual break in execution occurs at line 119 of SAPLMRMP, BESTELLUNG_BUCHEN where function MRM_BW_PO_HISTORY is called.

Had some other errors where tables weren't properly activated after the EHP installation, but here most everything seems to be activated properly. The exception is table EKBE, which activates but with warnings about missing enhancement categories of tables or includes/subtypes for four active dependent tables. That's the only lead I've got.

Can't find any notes or other posts about this error, any ideas would be greatly appreciated!