Question Re: FI-MM account modification user exit/badi in Enterprise Resource Planning Q&A

FI-MM account modification user exit/badi

Former Member — Wed, 14 Aug 2013 15:12:35 GMT

Hi ,

In our company we do use mark up cost , for example US to Europe , US std cost + X% mark up will be the EU standard cost and at the time of Inter company Stock Transfer from US to EU, due to the difference in cost at the time of GR the difference is being pushed to PPV account ( OBYC-PRD - Gl account) and our goal is to use a different GL account for the same movement type / Modifier level at the time of GR in order to avoid the I/C STO PPV in to regular PPV. I tried the below BADI and USER EXIT but they are not promising.

The BADIS I looked for MB_DOCUMENT_BADI- This seems like it works at the time of material document but the posting ( PPV happens at the time of GR and accounting document created)

The user Exit LMR1M002 – Not sure if this is useful.

Thank you,

Vamshi KV

Re: FI-MM account modification user exit/badi

Former Member — Thu, 15 Aug 2013 16:35:38 GMT

I created a new " General Modifier" for PRD with a different GL account ( I did not make any changes in OMJJ for 101 Mtype) and trying to use LMR1M002 , but this one speaks about WRX only need to find a way.

Also can't we change 101 Mtype to have another line that can have new transaction Combination for account grouping? Seems like it is not allowed amd OMJJ is being populated by SAP itself? all I can se only Account Modifier and Check Accnt. Assignment can be changed and rest of the columns are fixed

I appreciate if any one can show some light or another approach.

Thanks,

Vamshi KV

Re: FI-MM account modification user exit/badi

Former Member — Thu, 29 Aug 2013 14:04:06 GMT

Hi Folks, so I am answering my own Question thinking it may be useful for any other memebers who may run in to this issue,

Initially I created a new account modifier and added this to OBYC against PRD transaction key with a new GL account.

later we used the user exit LMR1M002 and made changes like below and it is calling the function module ( enhancement framework) MR_ACCOUNT_ASSIGNMENT and include Program ZXM08U18. we followed the logic to pull all I/C STO with a unique identifier (ABCD) that sits in LIPS/ table as delivery type , and it worked fine by triggering the New GL account if it is I/C STO PO

But after speaking to our seniors and changing actual User exit functionlaity is not good idea as it speaksspecifically about the WRX GR/IR account , therefore we made changes to above MR_ACCOUNT_ASSIGNMENT and achived the same functionality and I am happy to give the below logic for reference.

Function Module ,
MR_ACCOUNT_ASSIGNMENT

ENHANCEMENT 1 ZGFI_MODIFY_ACCOUNT.    "active version
** ECDKxxxxxxxxx - Call customer function for PRD instead of WRX
IF VORGANGSSCHLUESSEL = 'BSX'.
    KONTO_MODIF = SPACE.
ELSEIF VORGANGSSCHLUESSEL = 'PRD'. "PRD User Exit     "ECDKxxxxx

    CLEAR KONTO_MODIF.
    CALL CUSTOMER-FUNCTION '011'
         EXPORTING
                I_WRXMOD      = I_WRXMOD
         IMPORTING
                E_KONTO_MODIF = KONTO_MODIF.
ENDIF.
ENDENHANCEMENT.

FUNCTION EXIT_SAPLKONT_011.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_WRXMOD) LIKE WRXMOD STRUCTURE WRXMOD
*" EXPORTING
*" VALUE(E_KONTO_MODIF) LIKE T030-KOMOK
*"----------------------------------------------------------------------

INCLUDE ZXM08U18 .

ENDFUNCTION.

*&---------------------------------------------------------------------*
*& Include ZXM08U18
*&---------------------------------------------------------------------*

DATA: lv_lfart TYPE lfart.

SELECT SINGLE k~lfart
      INTO lv_lfart
      FROM lips AS p
      INNER JOIN likp AS k
        ON k~vbeln = p~vbeln
      WHERE p~vgbel = I_WRXMOD-ebeln
        AND p~posnr = I_WRXMOD-ebelp.

IF sy-subrc EQ 0 AND lv_lfart EQ 'ABCD'.
E_KONTO_MODIF = 'MKP'.
ENDIF.

Thanks,

Vamshi K

Re: FI-MM account modification user exit/badi

reactrv — Fri, 18 Apr 2025 05:52:29 GMT

Hi Vamshi, Thanks a lot by updating resolution. We had the same requirement and this helped us addressing the issue. Thanks