Invoice Verification on the Internet (MM-IV)
Use
With the Invoice Verification Internet Application Component (IAC), your vendors can create invoices themselves for purchase orders that you have issued to them. Vendors can also display invoices that they have already entered.
Internet Application Component Category
Business-to-Business
Prerequisites
Internet User
You must create an Internet user for each vendor (using Tools ® Administration, User maintenance ® Internet user). Enter the vendor number as their ID. When a user logs on, the system checks the validity of the Internet user ID and the password, and checks the vendor ID against the vendor table.
Authorizations and Security
You must assign the following authorizations to the vendor’s R/3 user with activity 03 (display):
Authorization object |
Description |
M_BEST_EKO |
Purchasing organization in purchase order |
M_BEST_EKG |
Purchasing group in purchase order |
M_BST_BSA |
Document type in purchase order |
M_BEST_WRK |
Plant in purchase order |
Customizing Settings
Invoice Verification settings |
Menu path in Implementation Guide (IMG) |
Enter the document type to be used for posting the invoice. Assign the document type to transaction MR1W. |
Invoice Verification ® Incoming Invoice ® Maintain Document Types and Number Ranges |
Payment block W has been created for the Invoice Verification IAC. This payment block is the only one that you can use. |
Invoice Verification ® Invoice Block ® Determine Payment Block |
Tolerance key WI has been created for defining the tolerance limits for the Invoice Verification IAC. You configure these tolerance limits. |
Invoice Verification ® Invoice Block ® Set Tolerance Limits |
We recommend that you index table RBKP (Document header: invoice receipt) by vendor. This improves system performance when vendors display their invoices. |
Invoice Verification ® Logistics Invoice Verification: Index |
Activities
R/3 Development Objects and Adjustment Options
The data entered in the Internet is transferred to the R/3 System via BAPIs (Business Application Programming Interfaces). Data in the R/3 System is accessed via BAPIs as well. Furthermore, a simplified R/3 transaction with screens was created for this Internet Application Component. The following development objects are affected:
Development class |
MRM |
Transaction |
MR1W |
Program |
SAPMMRHW |
BAPIs |
Helpvalues.GetList Creditor.ExistenceCheck Creditor.CheckPassword PurchaseOrder.GetItems PurchaseOrder.GetDetail |
Function module |
MRM_INVOICE_CREATE (to create invoices) |
As well as changing the layout, this Internet Application Component offers further adjustment options.

Each change to an R/3 development object used for the Internet Application component counts as a modification.
You should not change the development objects of the standard system under any circumstances.
If you create a transaction of your own based on the Internet Application Component in the standard system, you have the following options:
To do this, you analyze your options using transaction MEW0 in the ABAP Workbench and add the other functions required to your Internet Application Component.
You can create a completely independent transaction with other screens. If you do this, you must satisfy the technical prerequisites for Web transactions.
Service name
The service name of this Internet Application Component is MR1W. You can find all the relevant files under this service name in the SAP@Web Studio.