This tutorial is part of our SAP MM course and it talks about SAP Vendor Invoice report. The tutorial will help you to generate SAP vendor invoice report for various requirements/scenarios.
SAP Vendor Invoice
SAP Purchase Order Transaction Codes: ME21N — Create Purchase Order, ME22N — Change Purchase Order, ME23N — Display Purchase Order, ME21 — Create Purchase Order, ME2N — Purchase Orders by PO Number, ME9F — Message Output: Purchase Orders, and more. View the full list of TCodes for Purchase Order. In my earlier posts, I explained how you can create a customer invoice either by using the journal entry tcode F-02 or FB70. When a customer invoice is created, the next step is to clear the invoice once the customer makes a payment against that invoice. To post an incoming payment in SAP, you use the standard F-28 tcode in SAP. List of SAP MM Purchase Order (PO) Tcode in SAP, Important Transaction Code, Tcodes for MASS MAINTENANCE T-codes, LISTS T-codes, REPORTING T-codes, TRANSACTION DATA T-codes, MASTER DATA T-codes, MESSAGES T-codes such as MEMASSPO Mass maintenance of POsMEMASSRQ Mass maintenance of PRsMEMASSSA Mass Maintenance of Scheduling Agreements MEMASSIN Mass Maintenance of info records. May 21, 2009 You can enter/create invoice with using T-CODE:-ZFV60/F-43 Park vendor invoice. FV60/FB60- Post vendor invoice. ZFV70/F-22- Park customer invoice. FV70/FB70- Post customer invoice (as authorisation of your SAP ID) FV50- G/L to G/L entry. (Park G/L Document) FV65- VENDOR DEBIT ENTRY (DEBIT NOTE) FV75- CUSTOMER CREDIT ENTRY ( CREDIT NOTE). Hi, I want to know the tcode to display the invoice Document. Note: im aware that In MR90,i can fill Invoice Doc. Number & Fiscal year for printing the invoice.
SAP vendor invoice is a document which integrates both materials management and financial accounting modules. SAP purchase order would be placed and sent to vendor/supplier requesting to deliver the goods/services. The vendor supplies the goods/services along with the invoice which contains the amount to be paid back to the vendor. The amount in the invoice would be entered against the purchase order in the incoming invoice transaction. This amount would be verified against the goods received and the price in the purchase order. If there would be any deviation with the amount in the purchase order and incoming invoice, the invoice would be blocked from further processing. If the amount in the purchase order and invoice matches, then the payment to vendor would be processed and the amount would be transferred to the vendor’s account as per the payment terms that were agreed between the supplier and receiver.
This vendor invoice could be discussed under categories like logistics invoice verification and financial accounting. In logistics invoice verification, it is a three-way matching of documents. i.e. purchase order, goods receipt and invoice. If there is any mismatch between these, the invoice would be blocked for payment. So, this is why it is called logistics invoice verification. In accounting, a payment to vendor would be performed.
SAP Vendor Invoice Report Transactions
Now, let’s discuss some of the main important transactions enabling you to generate SAP vendor invoice report.
MIRO – Enter Incoming Invoice
This transaction is used to enter an incoming invoice against SAP purchase order. The invoice amount against the purchase order could be verified and the invoice could be held or posted.
MIR4 – Display Invoice Document
In this transaction, the already posted invoice could be displayed. The follow-on documents like accounting documents could also be displayed.
MIR6 – Invoice Overview
Invoice overview is a transaction which helps to extract the invoice report for various scenarios. This transaction would help to extract invoice per invoice document number, company code, posting code, etc.
Consider a scenario where we have a list of invoice numbers and its details would need to be viewed or extracted, then the invoice document numbers could be copied to document number field and the report can be extracted.
The other scenario is to download SAP vendor invoice report per company code and that could be extracted to know the invoice details. We could also filter our search criteria using invoice status like with errors, posted, etc.
The picture above shows different input selection criteria available and the same could be used for filtering out our desired output.
MB5S – List of GR / IR Balances
GR/IR stands for Goods Receipt and Invoice Receipt. This GR/IR account is a book keeping device which could be used when we receive goods before an invoice is generated or entered in system, or when an invoice is generated or entered into the system before the goods are delivered. The transaction MB5S would help us to extract such GR/IR balances.
The above figure shows the input selection criteria for the transaction MB5S. The input could be one of the following or a combination of the following like vendor, purchasing organization, purchasing group, material, purchasing document. You could input any one or the combination of input selection criteria and execute the report to extract the desired output.
Let’s imagine that I would like to extract a report for a particular vendor 15 belonging to any purchasing organization, and would like to analyze the GR/IR balances. Enter the input for the vendor filed as 15 and execute the report.
The output screen displays the GR/IR balances for the vendor 15 which then are linked with two purchasing documents.
The first line item in the report shows that the quantity is not received but the invoice is entered. The second line item in the report shows that the quantity is received but the invoice is not yet entered.
In either of these two cases, the invoice document cannot be posted. It could be either parked or held and the same could be extracted through invoice overview report. The balance shown in this report should be taken care and adjusted or the amount of both goods receipt and invoice should be balanced, so that payment could be paid to vendor.
FBL1N – Vendor Line Item Display
This is another transaction through which the accounting documents related to vendor invoices could be displayed. In this transaction, you could give the input selection criteria as line items viz. open items, cleared items, all items which are a combination of both open items and cleared items.
This screen has line item selection tab which contains open items, cleared items, all items. Below line item selection tab there is a tab with type which has the options for parked items, etc. We could describe this report in detail using one scenario for line item selection.
The vendor number is 15 and the company code is M100, then for line item selection – open items is selected. When this report is executed the output screen would appear as below.
The above picture shows the list of accounting documents that are in open status for the vendor 15 and company code M100. The type column contains KR – which denotes that it is a document type for vendor invoice. So, the above figure shows that the six line items displayed are the ones that are open and should be processed for payment or to be blocked.
The next scenario is to extract a report for cleared items. The report would be extracted for the same vendor 15 and company code M100 and option that was selected was cleared items. When we are done with the input selection screen, press execute button to view, analyze and also to extract the report.
The traffic light button in the above figure shows that accounting document are passed and the vendor account is cleared, so they don’t require any further processing.
Did you like this SAP MM tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP MM tutorials.
Go to next lesson: SAP Logistics Information System
Go to previous lesson: SAP Purchase Requisition Report
Go to overview of the course: SAP MM Training
In the last couple of posts, I explained how you can process the Inter-Company and Intra-Company asset transfer. I also shared the tutorial on AFAB that allows you to post depreciation for fixed assets. Today, I will show you how you can post an unplanned depreciation in SAP using t-code ABAA.
As you already know that AFAB is used for posting planned depreciation. It will post the depreciation amount every month for each fixed asset. On the other hand, ABAA allows you to post the unplanned depreciation in SAP. This situation occurs when an organization needs to adjust the Net Book Value (NBV) and Depreciation amount for an asset.
Usually, organizations post unplanned depreciation when there is untimely wear and tear for an asset. The organizations then need to reduce the net book value of the asset. Hence, they post the unplanned depreciation. In SAP, transaction code ABAA is used to post this kind of transaction.
Step 1: Create an Asset and Post the Acquisition and Depreciation
To execute any process in asset accounting, you need an asset master with some values. In this example, I’m taking an asset 1800010-0 that has an acquisition value of $1000. You can go through my tutorials on AS01 and ABZON to learn about creating an asset master and posting acquisition value without vendor.
This asset has an acquisition value date of 1st Jan 2021 with a useful life of 4 years, i.e. 48 Months. So the monthly depreciation amount comes out to be 1000/48 = $20.83. I have also posted the total planned depreciation of $62.50 using AFAB for the first 3 periods. The planned depreciation amount for Period 4 is $20.83 which the system will post once we execute the AFAB for Period 4.
Step 2: Execute ABAA to process Unplanned Depreciation in SAP
Once you have the asset master ready, you can post unplanned depreciation on it. Please execute the transaction code ABAA or navigate through the following SAP Easy Access path:
On the initial screen, enter the company code, Asset Code for which you want to post the unplanned depreciation. There are 2 transaction types for unplanned depreciation: 640 and 650. We use 640 if the asset was acquired in the previous fiscal years. And, 650 is used if the asset acquisition date falls in the current year.
Since our asset 1800010-0 is acquired in 2021, I will use transaction type 650. Click on the ‘Continue‘ button to proceed.
You need to enter the document date, posting date, and asset value date on the next screen. These are the dates on which you are posting the unplanned depreciation in the system. Also, enter the amount for unplanned depreciation.
Entering the data in the Additional Details tab is optional. By default, the system will extract the posting period from the posting date and the document type is AA. If you want to change the document type, then you can specify a different document type here.
You can also input additional information in the Reference and Assignment fields.
Step 3: Post the Unplanned Depreciation Asset Document
After entering the required data in the fields, click on the ‘Post‘ button to post the asset document. Please note that the system will only post the asset document and not the accounting document. The accounting document for unplanned depreciation will be posted once we execute AFAB for period 4.
When you display the asset values in AS03 or AW01N, you can see the transaction for unplanned depreciation with transaction type 650.
How To Display Invoice? SAP Community
Step 4: Post the Unplanned Depreciation Accounting Document
FI - Localization
In the last step, you need to execute the t-code AFAB to process the planned depreciation. Please note that the system will post the unplanned depreciation amount along with the normal planned depreciation amount when you post depreciation for the next period.
Execute AFAB for the next period, e.g., Period 4 in our example and the system will post both the unplanned depreciation of $500 and the ordinary depreciation amount of $20.83.
With this last step, we conclude this tutorial on Unplanned Depreciation in SAP using t-code ABAA. If you have liked it, please do share this post with others. Stay tuned for more!!!