Skip to Content
avatar image
Former Member

BAPI for Conventional Invoice Verification MR01 - SAP R/3 4.5B

Hello,

I am working on a custom interface that posts a Conventional Invoice Verification

to transaction code MR01.

I am looking for released function modules or BAPI's that will perform this function.

The aim is to avoid BDC due to a greater potential for upgrade issues.

I am working on version 4.5B and have had difficulty trying to find a solution.

I have tried :

1) BAPI_ACC_DOCUMENT_POST - this posts a FI document via FB01.

2) BAPI_ACC_INVOICE_RECEIPT_POST - this posts a FI document via FB01.

Neither of the options above post an Invoice Receipt

that hits MM.

3) IDOC Process Code - the process code behind IDOC processing calls a function module that

uses call transaction and hence BDC processing.

4) OSS searchs, web search, colleagues

I know that SAP moves to Logistics Invoice Verification in later versions and that BAPI

Incoming Invoice and Method CreateFromData is suitable for my requirements.

My question is for version 4.5B are there released function modules or BAPI's that will post

to MR01 without using a screen based approach.

Kind regards,

Mark

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Apr 19, 2004 at 02:03 PM

    Hi,

    Remember that it doesn't matter if IDOC finally uses BDC, Sap guarantees that the IDOC that today are working in 4.5b will work in future releases.

    You only must take care about using the right message type according to your release.

    I think it will work and you won't have to play with BDC. Anyway, I would finish the BAPI way before exploring IDOCs

    regards,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 19, 2004 at 02:04 PM

    Hi,

    Remember that it doesn't matter if IDOC finally uses BDC, Sap guarantees that the IDOC that today are working in 4.5b will work in future releases.

    You only must take care about using the right message type according to your release.

    I think it will work and you won't have to play with BDC. Anyway, I would finish the BAPI way before exploring IDOCs

    regards,

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi David,

      Many thanks for your response. I undertand your point on the IDOC and SAPs guarantee but unfortunately that doesn't

      help me.

      What we require is a BAPI/Function Module.

      I've tested both of the BAPIs I mentioned and neither are

      suitable.

      Kind regards,

      Mark

  • avatar image
    Former Member
    Apr 19, 2004 at 08:48 PM

    Look at the MRM* function groups...the EDI processor uses MRM_INVOICE_CREATE I believe - Else just be done with it and do BDC's. The BAPI's are VERY easy to implement once you're in 4.7.

    We just upgraded to 4.7 Enterprise --- YEAHHHHHH....but I had to convince our team here that we didn't want to use the EDI approach to LIV creation of invoices but use the new bapi's - BAPI_INCOMING_INVOICE_CREATE etc...very good bapi in 4.7 - it works. They have some work to do on the *PARK one though. Many discussions around ability to "PARK" errors in the invoice (I want them to use Parking like BDC error sessions -- it would be nice if SAP did the error collection instead of us having to write additional stuff...The reason why they wanted the EDI LIV invoice create was the ability to catch the errors in the idocs -- ugly world that is..)

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 22, 2004 at 09:06 AM

    Hi Mark,

    sorry to bring bad news, but the BAPI you look for does not exist and SAP will not create it.

    To explain that look at the sequenco of events:

    - in the beginning there was MR01 (no blasphemy intended 😊

    - then came the plans to replace MR01 by LIV (logistics invoice verification)

    - then came the time when SAP tried to create BAPIs for most functions. Since at this point in time it was already decided to replace MR01 by LIV, the invoice verification BAPIs were created for LIV, not for MR01.

    So for conventional invoice verification there will be no BAPIs.

    Regards,

    Robert

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      David/Connie/Robert,

      Thanks to all of you for your advice and time.

      I suspected that my search may have been in vain and

      at least this has been confirmed.

      Kind regards,

      Mark