AP – Vendor-Invoice

Accounts Payables :

Invoice thru MM-FI (MIRO) PTP (Procure to Pay – against a Purchase Order) Direct Procurement	Finance – Invoice (FB60) Indirect Procurement
MIRO : if you have open PO and system needs to post the Invoices to close the status of POs – MIRO if you wanted to generate inventory then you have to follow the PTP process and post invoices through MIRO For background run, use MIRA. You can not post LIV documents online using MIRA	If you do not have any open PO, then FB60
MIRA is for Invoice Verification in the Background MIRA covers the activity necessary for entering invoices for verification in the background. You can only enter the invoice data at header level, the system only determines the items to be verified during background verification using report RMBABG00. For further invoice overview use MIR6	LSMW+with+RIFBIBL00

MIRA (MM-FI)

• MIRA – This process is suitable for the following transactions
  • Posting invoices with mass amounts of data for which no item check is required
  • Posting invoices referring to transactions not yet entered in the system
  • Entering Invoices for Verification in the Background (Without Item List) [ report RMBABG00 ]
• When verifying invoices in the background , you enter only a small set of document header data, such as the invoice amount, the currency and the tax information. You also allocate the incoming invoice to a purchasing document or a vendor. The system saves the data and allocation criteria you enter.
• At a later point, the system verifies the invoice in the background. It uses the allocation criteria you entered to determine the item list. It then calculates the net total from the item list.
  • If the net total = gross amount invoiced – tax amount (+/- tolerance), the system posts the invoice in the background.
  • If the net total ¹ gross amount invoiced – tax amount (+/- tolerance), the system does not post the invoice in the background. It saves the document header data and the items determined in the background; the saved document then has to be processed manually in Invoice Verification.
• With Invoice Verification in the background, the system does not check for any quantity or price differences at item level. Since you do not enter any actual invoice item data, the system uses the default data for comparison

---

LSMW with RIFBIBL00 (FI Invoice : FB60)

https://wiki.scn.sap.com/wiki/display/Snippets/LSMW+with+RIFBIBL00

Step 1: Maintain Object Attributes
For creating the FI document with the RFBIBL00 using LSMW, we have to select the object 0100, method 0000 and program RFBIBL00.

Step 2: Maintain Source Structures
We will create total two structures: One for header and another for item. We could have at least two line items in the FI document. So, we need to upload at least 2 records per document. To upload 2 records, we should able to pass those two records in the mapping as well as in the conversion.

Create a structure with name ZFI_HEAD for the Header (BKPF).

Under the ZFI_HEAD, create another structure ZFI_ITEM for items (BSEG). Put cursor on the ZFI_HEAD and press the create button to create lower level structure ZFI_ITEM.

Step 3: Maintain Source Fields
We need to have one link field which will link the Header record with the Item record which system will use later to link the records from both different files.

These are the fields for the ZFI_HEAD structure

These are the fields for the ZFI_ITEM structure

Step 4: Maintain Structure Relations
Here we will define the structure relationship between source structure (BGR00, BBKPF, BBSEG, etc) and target structure (ZFI_HEAD, ZFI_ITEM, etc). 

Step 5: Maintain Field Mapping and Conversion Rules
Assign all the fields from the ZFI_HEAD to respective fields from BBKPF and ZFI_ITEM to respective fields from BBSEG. Don’t assign the CNT field to any of the field.
Make sure we pass correct formatted date (YYYMMDD) to the BBKPF.

Step 6: Maintain Fixed Values, Translations, User-Defined Routines
We don’t to maintain anything in field.
 

 Step 7: Specify Files
Create 2 files: 1 for header, 1 for Item. Sequence of the fields in the Structure must be same as the fields in the file. You can download my test files: Header and Item.

Create a header file.

Create another file for the Items in the same fashion.

You can change the names of the Read and Conversion files.

Step 8: Assign Files
Assign the files to the structures.

Step 9: Read data
Read the files specified in the Step 7

Step 10: Display read data
Displaying read data

Step 11: Convert Data
Run the convert data report to convert the input data to .conv file

Step 12: Display Converted Data

Step 13: Run program
Run program RFBIBL00 to create a session.

Use BBTAX:

• To use the BBTAX structure also in the RFBIBL00, we need to create another structure (e.g. FI_TAX) under the ZFI_HEADER and same level of ZFI_ITEM.
• As ZFI_ITEM (BBSEG) and FI_TAX (BBTAX) are at the same level so, we can use the same CNT field to link them.
• Create a Separate file as we have created for the header and item.

Use BWITH:

• BWITH is the subitem level data for the FI document. With-holding tax data is attached to the line item. So, we need to create a child structure under the ZFI_ITEM.
• Since we have created the structure at child level, we need another field to link the item data to the withholding tax data.
• Create a separate field as we have created for the header and item.