EDI Invoice Verification - Suppressing Validation

We receive most of our supplier invoices via EDI. We don't use FI/CO (yet) but interface out of SAP to a non-SAP system. For reasons to do with the quality of our data, we don't want to validate inbound invoices against PO's but merely post them as liabilities against the supplier. Is there a way of doing this? We have tried manipulating the flags in the V_076S_M table without success. I know this is a slightly bizarre requirement but any help would be appreciated.

Hi Peter,
You can use the Directposting to G/L accounts with MM functionality by activating the user exit EXIT_SAPLMRMH_015 based on the SAP version you are using or you can directly use the FI functionality as you are not posting against a PO.
Please let me know if you require further details.
Thnaks & Regards
Kishore Kumar

Similar Messages

Urgent!!!! EDI- Invoice Verification - MRHR( INVL ) - IDOC_INPUT_INVOIC_MRM

Hi all,
I'm facing an error while uploading a EDI format
flat file into SAP.
An Idoc gets generated and the status error message number is 51 : and it tells that IDOC_INPUT_INVOIC_MRM
NOT ALLOWED.
The Basic Type is INVOIC02
The message type is INVOIC
The Process code is INVL
Inside the process code the Identification contains the function module : IDOC_INPUT_INVOIC_MRM
Pls help.

Option #1 is to use INVOIC01. The configuration for INVOIC01 is present in the standard system for MM invoices through ECC 6.0.
Option #2 is to add the ALE config to allow use of INVOIC02 with IDOC_INPUT_INVOIC_MRM. We have just done this ourselves because we want to use the same IDoc for both our FI and MM invoices, and it seems to be working OK thus far. The configuration to use INVOIC02 for MM invoices is not in the default system up through ECC 6.0.
To do option #2, call transaction WE57 - "IDoc: Assigment of Function Module to Logical Message and IDoc Type"
You will need authorizations to assign a package to this -- it is transportable config.
Function module: IDOC_INPUT_INVOIC_MRM
Function type: Function module
Basic type: INVOIC02
Message Type: INVOIC
Message Variant: MM
Object Type: BUS2081
Direction: Inbound
Description: Invoice/Billing Document
Name: Incoming Invoice
(This is a copy of the default config for INVOIC01, changing the IDoc type to INVOIC02.)
Save, assign to the appropriate package for transport. This configuration is cross-client, so do it once in your development client and it's active in all clients on that instance.
And that's it! Do everything else the same as you would with INVOIC01. (Just keep in mind that not all of the segments you use for FI invoices work exactly the same way in MM invoices -- some of the segment qualifiers are different despite trying to define the same business fields...)
--Dan King
SAP NetWeaver Integration Architect
Capgemini

EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

Hi,
We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification. When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)? because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received.
The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation. The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
We havd SAP version ECC 6.0
I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this? and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

Hi ,
You can use the program RBDMANI2 which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
We had the same scenario and we have scheduled this program as a daily job at night .
Regards,
Hari.

Planned delivery Cost invoice verification via LIV EDI

I have to verify the planned delivery cost in purchase order ( freight condition types). The invoice sent by the vendors via EDI ,have both material & freight cost. Unfortunately SAP doesnt allow to verify the planned freight cost via EDI. Is there a way to post freight costs along with material cost in EDI
Has anybody used the BAPI_INCOMINGINVOICE_CREATE for delivery cost invoice verification using data from the invoice idoc.

Hello
Purchase order: 100 pcs @ 1.3/pc
Planned delivery costs: 0.10/pc
Goods receipt for that PO: 100 pc
A/C postings @ GR
Stock account: 140 Dr
GR/IR clearing: 130 Cr
Freight clearing: 10 Cr
Invoice 100 pc @ 1.3/pc=130.00
freight @ 0.10/pc= 10.00
Total =140.00
A/C posting @ IR
Vendor a/c's: 140 Cr (130 for Goods vendor and 10 for freight vendor)
GR/IR clearing: 130 Dr
Freight clearing: 10 Dr
Since both are different vendors you have to credit the goods value to vendor A and freight charges to vendor B, you have to do them separately.
Regards
Gregory Mathews

Invoice verification posting and validation

Hi,
what is the trx to create a validation for invoice verification (the invoice is being posted by MIRO)
Regards

Transaction OB28/ GGB0
Regards,
SDNer

Block Invoice verification as per quality result

Hello,
I made GRN , lot gets generated. not cleared by quality.
still I can do the invoice verification.
Can I restrict this ? so i can not pass invoice before quality results and only ok quantity has to appear for invoice verification.
If such facility is available kindly advice.
Regards,
santosh joshi

Dear Santhosh Joshi,
Check in IMG (Transaction SPRO) under :
Materials Management -> Logistics Invoice Verification -> Invoice Block
You can implement a proper BAdi/Enhancement if you cannot configure your scenario:
BAdi:
BAdI MRM_RELEASE_CHECK for additional checks before invoices are released, in other words, you can restrict the list of invoices to be released by defining your own criteria.
The following SAP enhancements are available for maintaining the customer exits in Invoice Verification:
MM08R001        ERS (conventional Invoice Verification)
MM08R002        Tolerance checks
MRMH0001        ERS (Logistics Invoice Verification)
MRMH0002        EDI invoice receipt (Logistics Invoice Verification)
MRMH0003        Revaluation (Logistics Invoice Verification)
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defnied.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defnied.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amoutns.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper
and lower tolerance limits (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Hope this will resolve your issue.
Regards,
Naveen.

Difference in Invoice verification ( GR/IR)- for Line item wise

Hi,
I have done invoice verification against PO but in my PO having 4 line items 10 to 40 so while doing invoice verification i have made a mistake in line item 10 i made quantity +1008 made extra and in line item 20 i have made less 1008 and i get to know information while doing MR11 line itme show higher quantity and lower quanty so GR/IR Clearing in not possible bacause of difference quantity and so i already paid entry tax on this PO and i can not do MR8M, is their solution workaround to nullyfy the line item
could u suggest if any kind of solution i will appriciate for ur valid suggestion.
Regards
Vinu.

Hi
If MR8M is not possible, then you can post a credit note using the same T.code MIRO for the difference for the excess quantity and later later post an invoice for the short posted quantity.
Regards

Print out of invoice verification..

Dear All,
Is it possible to take print out of Logistic invoice verification - MIRO(Like PO)?
Application "MR" for this is available but i don't know how to use and configure it...can you please explain steps like where i have to assign smart form..output type,condition record and other settings?
or i have to create any T-code for this and assign smart form there..
Thanks,
Naren

Hello,
Please note that as Invoice Verification is posting of incoming document, SAP does not provide for direct print settings. You can only print Invoice Plans, EDI and any Invoice complaints. You can however try with INS (Invoice Plan) and REKL. Maintain the conditions for wither of these and it will work.
Go to NACE. You can configure all the documents in single Tcode.
for more clarification floww this link
http://help.sap.com/saphelp_45b/helpdata/en/a8/b99864452b11d189430000e829fbbd/content.htm
Regards
Mahesh Naik.

Same nr range in Invoice Verification (MIRO) and FI document

Dear all can you please help to solve this issue?
We would like to have the same number range for invoice verification and for financial document, what we have to do?
Regards
Marco

Please follow the steps as below
Step 1. Maintain FI document number range. Use transaction OMR4 and go to Number range for document types in FI. Select the company code for which you want to create the new number range interval and click on the change interval button. Insert a new document number range by clicking on the insert interval button on top of the screen.for example, I created number range interval 52 with the document numbers 5200000000 5299999999. Don't forget to set the external number range check box (Ext).
Step 2. Assign FI number range to FI document types. The second step is to assign the number range created in step 1 to the FI document type for invoices. Again use transaction OMR4 and go to Document type. Double-click on the document type, which you are using for LIV invoices. In my example, I used the SAP standard document type RE. In the number range field, assign the new number range interval 52
Step 3. Maintain MM document number ranges. Use transaction OMRJ and click on change interval button. Insert a new document number range by clicking on the insert button at the top of the screen. For MM documents, I created number range interval 52 with the document numbers 5200000000 5299999999. For the internal number range assignment, do not set the external number range check box (Ext).
Step 4. Update MM number range assignment. The last step is to assign the MM number range to your MM transaction via IMG menu path Materials Management>Logistics Invoice Verification>Incoming Invoice>Number Assignment>Maintain Number Assignments for Logistic Documents>Transaction Assign Number ranges. Two transactions are available. LIV contains the following two internal transactions that are used for the MM document number determination:
RD: manual invoice entry (MIRO)
RS: cancel, reverse invoice (MR8M), evaluated receipt settlement (MRRL), EDI invoice receipt, invoicing plan (MRIS), and revaluation (MRNB).
You need to update the number range interval for transaction RD.
hope now that things r clear
reward accordingly

Invoice Verification MIRO

Dear All,
This is about invoice verification block after MIRO posting-
In PO we have set it as 2 way match, once the PO is equal to Invoice verification then the system should not put any payment block. But if it doesnt match the value of PO to IV then the system should put invoice verifcation block (R) in the accounting document.
Here, whatever we post that is whether the PO value is matching or not the invoice verification block (R) is appearing in the accounting document. Does any one gone through similar issue....
I want to know how this can happen?
Checked validations but nothing that sort appears.....is there a way to find out how this happens....
Thanks to all in advance.

Hello
I do not know of any BAPI. But you can set an automatic block up through your payment terms.
Check the following customizing path for this:
Financial Accounting
->Accounts Receivable and Accounts Payable
   ->Business Transactions
     ->Incoming Invoices/Credit Memos
       ->Maintain Terms of Payment
Select the details for the payment term and check for the indicator there to set the default block key.
Hope this helps
Ray

Document contains some order item more than once - invoice verification

Hi,
we have one cross company stock transfer process in which when a billing is created in SD side, an IDOC will be triggered automatically and create an invoice verification at the MM side.
The problem is some of our billing of this process having an IDOC application error that said.
Document contains same order item more than once
Message no. M8321
Diagnosis
Under the following circumstances, you can settle an order item in an invoice received via EDI more than once:
- Goods-receipt-based Invoice Verification has been defined for the order item.
- The IDoc contains the delivery note numbers of the goods receipts.
System Response
If this is not the case, the system cancels posting of the IDoc.
Question:
1 - The funny thing is IDOC showing 51 IDOC error code message on status record of INVOIC. But the invoice verfication get created in PO history.
2 - I think this error is because we need to make the PO as GR-based Inverifcation. We have flagged it in Vendor master, and Info record, but this indicator is not flag automatically in the PO (and we cannot manually change the PO as this indicator is grey-out). How?
3 - how to solve this error?
Thanks

Once PO history is created, you cannot change the "GR-based-IV" flag. Two options are there before you.
1. Cancel all the GRs & Invoices posted in the STO then system will allow you to update the GR-based-IV flag. After updating this flag repost the GRs and invoices.
2. Create a new STO, now since you have updated the vendor maser & info-record, this flag will automatically get updated during the STO creation itself.
First option is tedious and should be selected only if you can go option 2 is not at all feasible

Align MM and FI Document Numbers in Logistics Invoice Verification

Hi All,
Need help!
Requirement : Align MM and FI Document Numbers in Logistics Invoice Verification
Followed all the steps as per the SAP documentation : Materials Management > Logistics Invoice Verification > Incoming Invoice > Number Assignment > Maintain Number Assignments for Accounting Documents
As per the SAP documentation the configuration done should be enough to pass on MM Document No to FI document. But its not working as expected.
I have done the following:
1. Assigned MM and FI documents the same number range and both are in sync.
2. MM Documents are configured to be internally generated,
3. FI Documents are configured to be externally generated.
While during MIRO system generates errror and tells "Accouting Doc number are externally configured" (Not remembe the exact error) ? What is the solution for this issue. I need to align the MM and FI Document Numbers in Logistics Invoice Verification.
Gone through articles on internet and all discuss the same steps and configuration.
http://wiki.sdn.sap.com/wiki/display/BPX/HowtoAlignMMandFIDocumentNumbersinLogisticsInvoice+Verification
Kindly provide inputs as to what could be the missing configuration or probable solution.
Thanks!
Dev
Edited by: dev ahuja on Aug 19, 2010 3:03 PM

Hi,
Following step should be missing in your system:-
*Step 4. Update MM number range assignment. The last step is to assign the MM number range to your MM transaction via IMG menu path Materials Management>Logistics Invoice Verification>Incoming Invoice>Number Assignment>Maintain Number Assignments for Logistic Documents>Transaction - Assign Number ranges. Two transactions are available. LIV contains the following two internal transactions that are used for the MM document number determination:
u2022RD: manual invoice entry (MIRO)
u2022RS: cancel, reverse invoice (MR8M), evaluated receipt settlement (MRRL), EDI invoice receipt, invoicing plan (MRIS), and revaluation (MRNB).
You need to update the number range interval for transaction RD.*
Please check.
Regards,
Gaurav

Check when saving Logistics Invoice Verification (MRMBADI_INVOICE_SAVE)

Hi everybody, we have an ECC 6.0. with IS-Retail platform, and we have noticed that during Logistics Invoice Verification process (Tx MIRO), it´s possible to make mistakes by choosing a vendor, then picking an invoice from another vendor, with the particularity that both invoices have the same delivery note number as PO reference (same vendor´s delivery note number / GOHEAD-LFSNR). The system doesn´t check if PO reference corresponds with correct vendor while saving the document.
Our question for you is if there is a Customizing way to activate a validation which allow us to solve mistakes describe before???
We found BAdI method IF_EX_MRM_INVOICE_UPDATE PROCESS_AT_SAVE which is processed when saving an invoice, the method calls are encapsulated in the function module MRMBADI_INVOICE_SAVE which is responsible for saving invoices.
If there isn´t a Customizing way to activate a check like that, the second question we have for you is if you have experience with this BAdI??? Does it work with this kind of validation??? We need to ensure that PO reference corresponds to correct vendor (GOHEAD-LIFNR / RF02K-LIFNR).
Thanks in advanced for your help,
Regards,
Miyuki Quiroz.

Hi,
Duplicate invoice check will fulfill your requirement. System will check is the invoice exists with same invoice date, reference and company code.
Follow the path SPRO -- IMG -- MM -- LIV -- Incoming Invoice -- Set Check for Duplicate Invoices
Also tick check box for "check double invoice" in vendor master accounting data.
In case you want amount also as one of the checking parameters, then you need to go for validation. No standard setting is allowed for that.
Nikhil

Tolerance keys & Message No. configuration for invoice verification

Hi Consultants,
I need to configure the tolerance limits for scheduling agreements Which should prevent :
accounts payable from posting invoices beyond a scheduling agreements validity end date.
Accounts payable from posting invoices when the quantity invoiced is above the quantity ordered on the scheduling agreement.
for this cofiguration can some body help me what are all the tolerance keys should be maintained and what are all the message No. should be configured in warning for invoice verification.
with regards
GNK

Hi,
Go to OMR6 for the company code set the tolerance limit for the tolerance key
DQ -Quantity Variance
PP --Price Variance
ST- Date
G.Ganesh Kumar

User exit for Invoice verification

Hi
We want to findout user exit for invoice verification/MIRO . Is there any user exits available for MIRO.

The below are for MIRO
LMR1M001 User exits in Logistics Invoice Verification
LMR1M002 Account grouping for GR/IR account maint
LMR1M003 Number assignment in Logistics Invoice Verification
LMR1M004 Logistics Invoice Verification: item text for follow-on docs
LMR1M005 Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006 Logistics Invoice Verification: Process XML Invoice
MRMH0001 Logistics Invoice Verification: ERS procedure
MRMH0002 Logistics Invoice Verification: EDI inbound
MRMH0003 Logistics Invoice Verification: Revaluation/RAP
regards
Aravind
Assign points if useful

EDI Invoice Verification - Suppressing Validation

Similar Messages

Maybe you are looking for