Miro Verification Process

First, Introduction
Invoice validation is part of the material Management (MM) system. It provides a connection between the Material Management Section and the financial accounting, cost control and asset Management sections.
The invoice verification for the material Management module serves the following purposes:
It completes the whole process of material procurement-the material purchase starts with the purchase requisition, followed by the purchase and receipt, and ends with receipt of the invoice.
It allows processing of invoices that are not based on material purchases (for example, service charges, other expenses, process costs, and so on).
It allows processing of credit vouchers, either as a cancellation of an invoice or as a discount.
The invoice check does not process the payment, nor does it analyze the invoice. The information that needs to be processed is passed to other departments.
the tasks for invoice verification include:
Enter the accepted invoice and credit voucher.
Check the invoice for the content, price and calculation accuracy.
Perform an account accounting for an invoice
Update some data within the SAP system, for example, unsettled items and item prices.
Check for invoices that are frozen because they are too large to enter the purchase order.
The high degree of integration of SAP systems allows these tasks to be performed smoothly and efficiently.
Invoice Verification Process:
Each invoice contains a different information item. To account for an invoice, you must send this information to the computer. If an invoice reflects an existing transaction, some information is already stored in the system. The system suggests that this information is data that is missing, and that you only need to compare it and make any possible changes if necessary.
If the invoice is based on a purchase order, you only need to enter the purchase order number. The system selects the correct transaction and extracts the data from the purchase order, including the supplier, the item, the quantity ordered, the terms of delivery, the terms of payment. Of course, if there is a change, you can modify these data in the default. You can show the history of the purchase order, for example, how many goods have been delivered and how many have already been invoiced.
If there is a change in the purchase order or receipt and invoice, a warning will be issued on the screen. If the change is within the pre-set allowable range, the system will allow the invoice to be billed, but will automatically freeze it to be paid. The invoice must be approved in a separate step. If the change is not within the allowable range, the system will not allow the invoice to be billed.
When the invoice is entered, the system will find the appropriate account accounts. The system will automatically generate sales tax, cash discount liquidation and price variance, and these accounting records are displayed. If there is a balance, the user has to fix it because the invoice can be billed only if the balance is zero.
As long as the invoice is billed, some data is updated within the system, such as the average price of the ordered item and the history of the purchase order.
Invoice Accounting completes the invoice check. The data that needs to be paid in the invoice is now included in the system. The accounting department can read the data and make appropriate payments with the assistance of the Financial accounting department.
Invoice Check Type:
As a rule, an invoice represents a transaction, and the shipper of the transaction requires payment. Invoice verification varies according to the type of invoice involved:
Invoice based on a purchase order
Based on the invoice verification of the purchase order, all items of an order can be processed together, regardless of whether an item is received in a number of partial receipts. All receipts are aggregated and billed as a project.
Invoice based on receipt of goods
In receipt-based invoice validation, invoices are not associated with purchase orders, but are related to separate delivery activities. This means that the reference voucher for the invoice is not a PO for purchase orders, but a delivery notice or a receipt document. Whether or not you use this method to arrange your settlement with the supplier. This method may be advantageous, for example, when you know that the order will be divided into many batches when the delivery is complete.
In receipt-based invoice validation, you should be aware of the following issues:
A cargo receipt activity must be before the invoice has been entered into the system.
The invoice may be entered in a way that refers to a delivery notice or a cargo receipt voucher.
Pre-conditions
The PO item concerned must have an invoice check mark based on receipt.
Operation
Turn to the Purchase Order item Detail screen.
Select the field Gr-iv.
Save the purchase order.
You can show the relationship of goods acceptance and invoice at any time. You will find this information in the history of the purchase order item.
No invoice for order
If no purchase order is referenced, the transaction can be credited directly to an item account, a general ledger account, or an asset account

Two, background configuration:
1. Tolerance Configuration The:t-code:omr6    tolerance is based on the company code configuration, because the invoice is issued according to the company code. Configure the upper/lower limit check limit, or set%. General Enterprise to configure four tolerance, BD (automatically form small difference), DQ (excess amount: quantity deviation), PP (price change), VP (moving average price difference).
2. Configure the Vendor tolerance: PATH: Bill-to-post invoice check-and-Receive billing--Configuration for vendor tolerance, which is set up for supplier-specific parameters in invoice validation. In a company code, you can assign only one tolerance group to a vendor. In the Vendor Master data (XK02), there is a tolerance group
3.   Configure invoice Check conditions: PATH: Material management, post-invoice check, information confirmation, maintenance conditions, modification-Invoice validation
4.    Configuration Voucher Type:     path: Document Type
5, the number range of maintenance account vouchers, which are received by Bill-to-post invoice verification, item management.    Configure default tax code: PATH: The default value of the maintenance tax code, which is received for billing, invoice verification, material management, and so on (according to company code settings)
Prepare before invoicing:
          1. When making a purchase order, on the Project Details invoice page, the based on Receipt IV field is set to "X". This is very important, I do the invoice check when I found this error, after the query is this no tick.

Third, the invoice check operation Tcode:
1. Discrepancies in invoice verification
Difference is divided into quantity difference, price difference, plan difference, purchase order price quantity difference, quality check
Quantity Variance: The invoice quantity is greater than the difference between the delivered quantity and the invoiced quantity
Price Variance: Invoice amount/Invoice Quantity <> net order price
Plan variance: The difference between the receipt date of the PO Delivery Schedule and the actual receipt date. Guess.
Purchase order Price Quantity variance: The difference between the receipt quantity/price and the quantity price of the purchase order.
Quality Management: If the product activates quality management, the inventory is checked at the time of posting.
Invoice verification based on receipt:
Input invoice, document input, logistics invoice verification, retail
Enter the company code, and then select the voucher type (Credit voucher/invoice), the total settlement amount of negative is the credit voucher, as a regular invoice, when the invoice is included in the input purchase order number to the right of the button, click Enter, the return is selected into the loan, the purchase is selected to borrow, otherwise unable to do invoice verification, When creating invoices outside the SAP system, such as BAPI "Bapi_incominginvoice_create", you do not specify the direction of the voucher to be returned and entered, and SAP will automatically enter it.
If you want to post a discrepancy invoice, as stipulated by the company, you can count on the variance account or set the tolerance range, the difference account Select the invoice "G/L Account" page, enter the variance account, note the borrower, the difference of the borrower and the normal invoice in the opposite of borrowing, such as credit to the voucher, the difference account debited.
Generally just finished invoice payment to be set to freeze, payment method also set (debit), Baseline date (Financial start processing payment date).
Display invoice vouchers, further processing, logistics invoice verification, retail, procurement, logistics
2. No difference in invoice verification
The process is the same, but the quantity and amount are no different.
3. Pre-built Invoice
Proforma invoice, input invoice, logistics invoice verification, retail
SAP can do a pre-set invoice, which is equivalent to the invoice request, the request can be modified several times, after saving does not automatically post. After completing the pre-invoicing, execute Miro and select the preset invoice.
4. Background Invoice Check
The invoice for input background check, such as logistic invoice check, purchase
Background invoice verification is the background of the invoice check, if within the tolerance range, will be posted directly in the background.
5. Background check the correctness of the invoice
T-code:wc23

******************************************************

1) for possible input-to-Invoice validation (MIRO) on the calculation of the delivery order, see rm08rl82
Calculation instructions:
1) Read the appropriate Ekko
select  * from    "Ekko"
WHERE
   "Mandt" = ' + ' and "Bstyp" in (' L ', ' F ') and "ebeln" = "4500000005" and "BUK RS "= ' 1002 '
  and" lifre "= ' 0011000843 ' and ' frgrl ' = '   and ' loekz ' = '   and (" MEM ORY "="   or "MEMORY" is NULL)
2) Read Ekpo and Ekbe
select  * From  ekpo According to the read Ekko where "Mandt" = ' + ' and ' ebeln ' = ' 4500000005 ' and ' REPOS ' = ' X ' and ' loekz ' = '
SELECT * from Ekbe WHERE ' Mandt ' = ' Ebeln ' = ' 4500000005 ' and ("vgabe" = ' 1 ' OR "vgabe" = ' 2 ')
3) loops through the inner table of the Ekko to calculate the quantity and amount of ekbe deliveries and shipments to generate the amount to be invoiced.

2) Miro functions
Call function ' ckmv_ac_document_post '
Call function ' Post_document ' In update task
Call function ' g_fi_posting ' on update task
Call function ' g_lc_posting ' on update task
Call funct ION ' ac_document_mm_update ' in update task
Call function ' MCE_STATISTICS_UPD_V2 ' in update task
Call function ' Me_u Pdate_invoice ' in update task
call FUNCTION ' mrm_invoice_document_post ' in update task

Call FUNCTION ' sd_scd_iv_selcriteria_save_db ' in UPDATE TASK

Call FUNCTION ' Swe_event_create_for_upd_task ' in UPDATE TASK

3) Miro the data sheet used to save the operation
New CKMI1
New BKPF

New EKBE
INSERT VALUES (' 800 ', ' 4500000005 ', 00030, 00, ' 2 '  , "5105614013", 0006, ' Q ', ', 2 0071022, 1, 1, $, $ '
Note 2 Here indicates the processing of the purchase invoice, 1 indicates the processing of the purchase order receipt, New RBKP
INSERT VALUES (' + ', ' 5105614013 ', ' + ', ' RE ', 20071022, 20071022, ' SDSUPPORT01 ', ' MIRO ', 20080222 , 191406, ' RD ', ', '
new RESG
INSERT VALUES (' 800 ', ' 5105614013 ', 2007, 000006, ' 4500000005 ', 00030, 00, ' 00049251 ', ' 1101 ', ', ' 1002 ', ' 1101 ', Bsik
add

New BSIs

Added the actual line Item table with the IDES feature range Glfunca

New index to find FI-SL base voucher on Awkey GLIDXA

New SAP Merge: Journal entry label (actual) ECMCA

Update Vendor master data (business amount) LFC1
UPDATE SET "um10s" = "um10s" + 0, "um10h" = "um10h" + 29062.8, "um10u" = "um10u" + -29062.8 WHERE "Mandt" = ' + ' and ' L Ifnr "= ' 0011000843 ' and" Bukr = ' 1002 ' and "Gjahr" = 2008
UPDATE SET "Umsav" = "Umsav" + -29062.8 WHERE "Mandt" = ' + ' and ' lifnr ' = ' 0011000843 ' and ' bukrs ' = ' 1002 ' and ' Gjahr ' = 2008
Update total table with Ides functional Range _ Glfunct

Update SAP consolidation: Total table ecmct

Update General ledger account Master record business amount GLT0

Miro Verification Process