Shulou(Shulou.com)06/01 Report--

What is the MIRO checking process of SAP based on purchase order? aiming at this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

I. introduction

Invoice verification is part of the material Management (MM) system. It provides links between material management and financial accounting, cost control and asset management.

The invoice verification of the material management module serves the following purposes:

It completes the whole process of material procurement-material procurement begins with the purchase request, followed by procurement and receipt, and ends with receipt of invoices.

It allows the processing of invoices that are not based on material purchases (for example, service charges, other expenses, process costs, etc.).

It allows credit vouchers to be processed, either by cancellation of invoices or discounts.

Invoice verification is not a process of payment, nor an analysis of invoices. The information that needs to be processed is passed on to other departments.

The tasks of invoice verification include:

Enter the accepted invoice and credit voucher.

Check the invoice content, price and calculation accuracy.

Perform the bookkeeping of an invoice

Update some data in SAP system, such as unsettled items and material prices.

Check those invoices that are frozen because they deviate too much from the purchase order.

The high degree of integration of the SAP system allows these tasks to be performed smoothly and efficiently.

Invoice verification process:

Each invoice contains different information items. To keep 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 recommends that this information is the default data, you just need to compare it and make any possible changes as needed.

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 data from the purchase order, including suppliers, materials, quantity ordered, terms of supply, terms of payment. Of course, if there is a change, you can modify these default data. You can show the history of the purchase order, for example, how many goods have arrived and how many have been invoiced.

If there is a change in the purchase order or receipt and invoice, the system will issue a warning on the screen. If the change is within the preset allowable range, the system will allow the invoice to be booked, but will automatically freeze its payment. Invoices must be approved in a separate step. If the change is not within the allowed range, the system will not allow the invoice to be accounted for.

When the invoice is entered, the system will find the corresponding account account. The system will automatically generate sales tax, cash discount settlement and price differences, and these accounting records are displayed. If there is a balance, the user has to correct it, because only the invoice with a balance of 00:00 can be recorded.

As long as the invoice is accounted for, some data is updated within the system, such as the average price of the ordered material and the history of the purchase order.

Invoice bookkeeping completed invoice verification. The data that needs to be paid in the invoice is now included in the system. The accounting department can read these data and make appropriate payments with the assistance of the financial accounting department.

Types of invoice verification:

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 purchase order

Based on the invoice verification of a purchase order, all items of an order can be processed together, regardless of whether or not an item is received in several partial receipts. All receipts are summarized and accounted for as an item.

Invoice based on receipt

In receipt-based invoice verification, invoices are not associated with purchase orders, but with separate delivery activities. That is to say, the reference voucher of the invoice is not the purchase order PO, but the delivery notice or receipt voucher. Whether or not you use this method to arrange your settlement with your supplier. This method may be beneficial, for example, when you know that the order will be delivered in many batches.

In the invoice verification based on receipt, you should pay attention to the following problems:

A goods receiving activity must be before the invoice has been entered into the system.

Invoices may be entered by referring to a delivery notice or a receipt of the goods.

prerequisite

The relevant PO items must have invoice verification marks based on receipt of goods.

Operation

Turn to the purchase order item detail screen.

Select the field GR-IV.

Keep the purchase order.

You can show the relationship between the goods acceptance and the invoice at any time. You will find this information in the history of purchase order items.

Invoices without orders

If there is no purchase order for reference, you can directly charge the transaction to a material account, a general ledger account, or an asset account.

2. Background configuration:

1. Tolerance configuration: T-CODE:OMR6 tolerance is based on the company code configuration, because the invoice is based on the company code. Configure the upper / lower limit check limit, or set%. General enterprises need to configure four kinds of tolerances: BD (automatic formation of small differences), DQ (excess amount: quantity deviation), PP (price change), and VP (moving average price difference).

two。 Configure supplier tolerance: PATH: material Management-> Post-invoice Verification-> Billing received-> configure specified supplier tolerance, setting of supplier-specific parameters in invoice verification. In a company code, only one tolerance group can be assigned to one vendor. There is a tolerance group in the vendor master data (XK02)

3. Configure invoice verification conditions: PATH: material Management-> Post invoice Verification-> Information confirmation-> maintenance conditions-> revision-invoice Verification

4. Configure voucher type: PATH: item Management-> Post invoice Verification-> Billing received-> number assignment-> maintenance account voucher number range-> voucher Type

5. Configure default tax code: PATH: item Management-> Post invoice check-> Billing received-> default value of maintenance tax code (set according to company code)

Prepare before invoicing:

1. When making a purchase order, the receipt-based IV field is set to "X" on the invoice page of the project details. This is very important. I found this error when I was doing invoice verification. After inquiry, it didn't check.

3. Invoice verification operation TCode:

1. Invoice check with discrepancy

The difference is divided into quantity difference, price difference, plan difference, purchase order price quantity difference and quality inspection.

Quantity difference: the difference between the number of invoices greater than the quantity delivered and the quantity invoiced

Price difference: invoice amount / invoice quantity net order price

Plan difference: the difference between the receiving date of PO Delivery Schedule and the actual receiving date. Guess.

Purchase order price quantity difference: the difference between the quantity / price received and the quantity price of the purchase order.

Quality management: if quality management is activated, check the inventory when posting.

Invoice verification based on receipt:

T-Code:MIRO Logistics-> Retail-> Purchasing-> Logistics invoice Verification-> Certificate input-> input invoice

Enter the company code, and then select the voucher type (credit voucher / invoice). If the total settlement amount is negative, it is credit voucher and regular invoice. When the invoice contains both entry and return, the Button to the right of the purchase order number is entered. After clicking enter, the return is selected as the loan, and the purchase is selected to borrow, otherwise invoice verification cannot be done. When creating invoices outside the SAP system, for example, transfer BAPI "BAPI_INCOMINGINVOICE_CREATE". At this time, the voucher direction of retreat and advance can not be specified, and SAP will be recorded automatically.

If the invoice with discrepancy wants to be posted, according to the regulations of the company, it can be included in the difference account or set the tolerance range, the difference account can be selected from the invoice "General Ledger account" page, enter the difference account, and pay attention to the borrower. The debit of the difference is the opposite of the loan in the normal invoice, for example, the loan to the voucher, and the difference account is recorded as the debit.

Generally speaking, the invoice payment just finished should be set to freeze, the payment method should also be set (account deduction), and the baseline date (financial start processing payment date).

T-Code:MIR4 Logistics-> Retail-> Purchasing-> Logistics invoice Verification-> further processing-> Show invoice vouchers

two。 Invoice verification without discrepancy

The process is the same, except that there is no difference in quantity and amount.

3. Preset invoice

T-Code:MIR7 Logistics-> Retail-> Purchasing-> Logistics invoice Verification-> Certificate input-> input invoice-> prefabricated invoice

SAP can make a preset invoice, which is equivalent to an invoice request, which can be modified many times and is not automatically posted after saving. After completing the preset invoice, execute MIRO and select the preset invoice.

4. Backstage invoice verification

T-Code:MIRA Logistics-> Retail-> Purchasing-> Logistics invoice Verification-> Certificate input-> enter backend verified invoice

Background invoice verification is to check the invoice in the background, if it is within the tolerance, it will be posted directly in the background.

5. Check the correctness of the invoice in the background

T-Code:WC23

* * *

1) for possible input to invoice verification (MIRO) for calculating delivery orders, see RM08RL82

Description of the calculation:

1) read the EKKO suitable for the condition

SELECT * FROM "EKKO"

WHERE

"MANDT" = '800' AND "BSTYP" IN (' L','F') AND "EBELN" = '4500000005' AND "BUKRS" =' 1002'

AND "LIFRE" = '0011000843' AND "FRGRL" =' 'AND "LOEKZ" =' 'AND ("MEMORY" =''OR "MEMORY" IS NULL)

2) read EKPO and EKBE according to the read EKKO

SELECT * FROM EKPO WHERE "MANDT" = '800' AND "EBELN" =' 4500000005' AND "REPOS" ='X' AND "LOEKZ" =''

SELECT * FROM EKBE WHERE "MANDT" = '800' AND "EBELN" =' 4500000005' AND ("VGABE" ='1' OR "VGABE" ='2')

3) cycle through the inner table of EKKO to calculate the quantity and amount of delivery and shipment of EKBE to generate the amount that needs to be invoiced.

2) functions used in saving MIRO operations

CALL FUNCTION 'CKMV_AC_DOCUMENT_POST'

CALL FUNCTION 'POST_DOCUMENT' IN UPDATE TASK

CALL FUNCTION 'GambiFIY POSTINGG' IN UPDATE TASK

CALL FUNCTION 'Globe LCSD POSTING' IN UPDATE TASK

CALL FUNCTION 'AC_DOCUMENT_MM_UPDATE' IN UPDATE TASK

Call function 'MCE_STATISTICS_UPD_V2' in update task

CALL FUNCTION 'ME_UPDATE_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) the data table used to save the MIRO operation

New CKMI1

New BKPF

New EKBE

INSERT VALUES ('800',' 4500000005', 00030, 00,'2', 2007, '5105614013', 0006,'Q', 20071022,1,1,36,36, 'RMB'

Note that 2 here indicates the processing of the purchase invoice and 1 indicates the processing of the receipt of the purchase order, which will be used in calculating the possible input of the delivery order to the invoice verification.

New RBKP

INSERT VALUES ('800',' 5105614013', 2007, 'RE', 20071022, 20071022,' SDSUPPORT01', 'MIRO', 20080222,191406,' RD','

New RESG

INSERT VALUES ('800',' 5105614013', 2007, 000006, '4500000005', 00030,00,' 00049251', '1101', '1002', '1101', 36

New BSIK

New BSIS

Add an actual line item table GLFUNCA with functional scope for IDES

New index GLIDXA to find FI-SL basic credentials on AWKEY

New SAP merge: Journal entry mark (actual) ECMCA

Update supplier master data (business volume) LFC1

UPDATE SET "UM10S" = "UM10S" + 0, "UM10H" = "UM10H" + 29062.8, "UM10U" = "UM10U" +-29062.8 WHERE "MANDT" = '800' AND "LIFNR" =' 0011000843' AND "BUKR = '1002' AND" GJAHR "= 2008

UPDATE SET "UMSAV" = "UMSAV" +-29062.8 WHERE "MANDT" = '800' AND "LIFNR" =' 0011000843' AND "BUKRS" = '1002' AND "GJAHR" = 2008

Update the summary table with IDES functional scope _ GLFUNCT

Update SAP merge: summary table ECMCT

Update general ledger account master record business volume GLT0

The answer to the question about the MIRO verification process of SAP based on purchase order is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.