Re: BAPI FOR MIRO

Former Member — Thu, 12 Jul 2007 13:07:40 GMT

Hi Satish,

Kindly check this

Invoice Verification: Post Invoice

Functionality

You can use this method to create and post incoming invoices.

When passing on the header data, you use the INVOIC_IND field to determine whether the system posts a credit memo or an invoice. If you leave the field initial, the system posts a credit memo. If you enter an X, the system posts an invoice.

If you want to enter an invoice for a returns order, you must leave the INVOICE_IND field initial.

As in the online transaction, the system updates the purchase order history and stock valuation data in Materials Management. The system creates accounting documents in Accounting.

You can use this method to:

Enter and post invoices with multiple account assignment

Change the account assignment of invoices, add account assignments, and post the invoices

Enter invoices for blanket purchase orders

Enter and post invoices for purchase orders containing planned delivery costs

Enter and post invoices containing unplanned delivery costs

Enter and post subsequent debits/credits

Use document types with external number assignment

Enter and post invoices with withholding tax

Enter and post invoice with more than one vendor line and different payment methods and terms of payment

Enter and post invoices for returns orders

Enter and post invoices for transportation service providers

Enter and post invoices for external service orders

Post to G/L accounts

Post to material accounts

Enter and post invoices for a one-time vendor

Enter and post invoices with a different payee

Restrictions

The following fields in Financial Accounting are not passed on:

ISR number (ISR = inpayment slip with reference number)

Bank details

Payment reference

House bank ID

Notes

The following authorization object is checked using activity 01:

M_RECH_WRK: Authorization to create invoices in certain plants

Transfer

You use the structure HeaderData to pass on the header data of the incoming invoice.

You pass on the address data of a one-time vendor or a different invoice payee with the structure AddressData.

Tables ItemData and AccountingData contain the invoice item data. The table TaxData contains the tax information for the invoice.

The tables ItemData and AccountingData contain the item data of the incoming invoice. The TaxData table contains the tax information on the invoice.

The table GlAccountData contains data for posting to a G/L account and the MaterialData table contains data for posting to a material account.

You can use the table WithTaxData to pass on withholding tax information.

Via the table VendorItemSplitData, you can distribute the gross amount among several creditor lines with different payment methods and terms of payment.

Return

The document number of the invoice document and the fiscal year are returned by the system as key fields of the incoming invoice.

Return messages

Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.

Further information

The method can only perform your function if no error messages were generated in the Return table. This is the case if the header data and all the items were processed successfully.

Transaction control is not implemented. The calling program therefore has to execute the Commit Work itself after this method has been successfully invoked (in other words, if no errors were reported in the Return parameter).

Example: Incoming Invoice

This example shows the header data that you need to enter in table Headerdata and the item data that you need to enter in table Itemdata to post an invoice.

Purchase order: 10 pc of material A @ $10/pc

Goods receipt: 10 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007491, PO item 10, for a quantity of 10 pc of material A and an amount of $116, including 16% VAT. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 05.20.2000

PSTNG_DATE (Posting date): 05.23.2000

COMP_CODE (Company code): 1000

GROSS_AMOUNT (Gross amount): 116.00

CURRENCY (Currency key): USD

CALC_TAX_IND (Calculate tax): X

ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001

PO_NUMBER (Purchase order number): 4500007491

PO_ITEM (Purchase order item): 00010

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Item amount): 100

QUANTITY (Quantity): 10

PO_UNIT (Unit of measure): PC

For more information, see the parameter documentation for tables HeaderData and Itemdata.

Example: Incoming invoice in foreign currency, goods-receipt-based invoice verification and tax information

This example specifies the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata and the tax information that you need to enter in table TaxData to post an invoice in a foreign currency.

Purchase order: 10 pc of material A @ $10/pc

First goods receipt: 4 pc of material A

Second goods receipt: 6 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007505, PO item 10, goods receipt document 50010095, 2000, item 1. The invoice is for a quantity of 4 pc of material A, a gross amount of $46.60 and 16% tax ($6.60). Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 05.20.2000

PSTNG_DATE (Posting date): 05.23.2000

COMP_CODE (Company code): 1000

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 46.60

ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001

PO_NUMBER (Purchase order number): 4500007505

PO_ITEM (Purchase order item): 00010

REF_DOC (Goods receipt document): 50010095

REF_DOC_YEAR (Fiscal year of current period): 2000

REF_DOC_ITEM (Goods receipt document item): 1

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Item amount): 40.00

QUANTITY (Quantity): 4

PO_UNIT (Unit of measure): PC

TaxData table

TAX_CODE (Tax code): VN

TAX_AMOUNT (Tax amount in document currency): USD 6.60

For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice for blanket purchase order

This invoice shows which header data you need to enter in the table HeaderData, which item data you need to enter in the table ItemData, and which account assignment data you need to enter in table AccountingData to post an incoming invoice for a blanket purchase order.

You receive an invoice in respect of the blanket purchase order 4500015172, item 10 for an amount of $110 including 10% VAT. You want to apportion the invoice amount to the cost centers 1200 and 1500. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 02.19.2001

PSTING_DATE (Posting date): 02.21.2001

COMP_CODE (Company code): 1000

GROSS_AMOUNT (Gross amount): 110

CURRENCY (Currency): USD

CALC_TAX_IND (Calculate tax): X

ItemData table

INVOICE_DOC_ITEM (Item in the invoice document): 00001

PO_NUMBER (PO number): 4500015172

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Item amount): 100

AccountingData table

1st line: Change account assignment data

INVOICE_DOC_ITEM (Document item in invoice document): 0001

SERIAL_NO (Serial number for the accont assignment): 01

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 30

GL_ACCOUNT (G/L account number): 890000

COSTCENTER (Cost center): 1200

2nd line: Add unplanned account assignment

INVOICE_DOC_ITEM (Document item in invoice document): 0001

XUNPL (Unplanned acct. assignment from IV): X

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 70

GL_ACCOUNT (G/L account number): 890000

COSTCENTER (Cost center): 1500

In the case of the blanket purchase order, the following fields for quantities and units of measure must not be populated in the tables ItemData and AccountingDataAccountingData:

Quantity (QUANTITY)

PO_UNIT (PO unit of measure)

PO_UNIT_ISO (PO unit of measure in ISO code)

PO_PR_QNT (Quantity in PO price unit of measure)

PO_PR_UOM (PO price unit of measure)

PO_PR_UOM_ISO (PO price unit of measure in ISO code)

More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Change account assignments and add unplanned assignments

This example shows the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata, and the account assignment information that you need to enter in table AccountingData to change, add, and post account assignments for an invoice. If you want to change or add account assignments, there must be a non-valuated goods receipt or no goods receipt in the system. Goods-receipt-based invoice verification is specified.

Purchase order: 300 pc of material A @ $1.00/pc

Goods receipt: 300 pc of material A

This purchase order is subject to account assignment. You receive an invoice for it, referencing the PO number 4500006846, PO item 10, goods receipt document 50008849, 2000, item 1. The invoice is for a quantity of 100 pieces of material A, with a gross invoice amount of USD 116.00, including 16% VAT. You want to change the planned account assignment for the second account assignment item and add an unplanned account assignment. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 08.05.2000

PSTNG_DATE (Posting date): 08.08.2000

COMP_CODE (Company code): 1000

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 17.40

CALC_TAX_IND (Calculate tax automatically): X

PMNTTRMS (Terms of payment key): 0001

ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001

PO_NUMBER (Purchase order number): 4500006846

PO_ITEM (Purchase order item): 00010

REF_DOC (Goods receipt document): 500008849

REF_DOC_YEAR (Fiscal year of current period): 2000

REF_DOC_ITEM (Goods receipt document item): 1

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Item amount): 100

QUANTITY (Quantity): 100

PO_UNIT (Unit of measure): PC

AccountingData table

Line 1: Change second account assignment item

INVOICE_DOC_ITEM (Invoice document item): 0001

SERIAL_NO (Account assignment serial number): 02

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Amount in document currency): 10.00

QUANTITY (Quantity): 10

PO_UNIT (Order unit): PC

GL_ACCOUNT (G/L account number): 890000

COSTCENTER (Cost center): 1200

Line 2: Add unplanned account assignment

INVOICE_DOC_ITEM (Invoice document item): 0001

XUNPL (Unplanned account assignment in Invoice Verification): X

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Amount in document currency): 5.00

QUANTITY (Quantity): 5

PO_UNIT (Order unit): PC

GL_ACCOUNT (G/L account number): 890000

COSTCENTER (Cost center): 1200

More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice with planned delivery costs

This examples shows the header data that you need to enter in table HeaderData, the item data that you need to enter in table ItemData, and the tax information that you need to enter in table TaxData to post an invoice containing planned delivery costs.

Purchase order: 100 pc of material A @ $1.00/pc

Goods receipt: 100 pc of material A

You receive an invoice for this purchase order referencing PO number 4500006986, PO item 10, for a quantity of 100 pieces of material A and $136.00, including 16% VAT and $20.00 planned delivery costs. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 08.10.2000

PSTNG_DATE (Posting date): 08.12.2000

COMP_CODE (Company code): 1000

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 136,00

ItemData table

Line 1: Posting the purchase order item

INVOICE_DOC_ITEM (Invoice document item): 00001

PO_NUMBER (Purchase order number): 4500006986

PO_ITEM (Order item): 00010

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Item amount): 100.00

QUANTITY (Quantity): 100

PO_UNIT (Unit of measure): PC

Line 2: Posting the planned delivery costs

INVOICE_DOC_ITEM (Invoice document item): 00002

PO_NUMBER (Order number): 4500006986

PO_ITEM (Order item): 00010

ITEM_AMOUNT (Item amount): 20.00

QUANTITY (Quantity): 100

PO_UNIT (Unit of measure): PC

COND_TYPE (Condition type): FRB1

TaxData table

TAX_CODE (Tax code): VN

TAX_AMOUNT (Tax amount in document currency): 16.00

For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice with withholding tax

This example shows which header data you can enter in the table HeaderData, which item data you can enter in the table Itemdata, and which withholding tax information you can enter in the table WithTaxData in order to park an incoming invoice with withholding tax.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095 2000, item 1. The invoice is for a quantity of 10 pc and a gross amount of $100. You have to pay 10% withholding tax on the gross amount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X

DOC_DATE (Document date): 05.20.2000

PSTNG_DATE (Posting date): 05.23.2000

COMP_CODE (Company code): WT01

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): $100

ItemData table

INVOICE_DOC_ITEM (Item from invoice document): 00001

PO_NUMBER (PO number): 4500007505

PO_ITEM (PO item): 00010

REF_DOC (GR document): 50010095

REF_DOC_YEAR (Fiscal year of the current period): 2000

REF_DOC_ITEM (Item in a GR document): 1

TAX_CODE (Tax code): V0

ITEM_AMOUNT (Item amount): $100

QUANTITY (Quantity): 10

PO_UNIT (Unit of measure): PC

WithTaxData table

SPLIT_KEY (Grouping key for withholding tax split): 0001

WI_TAX_TYPE (Code for withholding tax type): R1

WI_TAX_CODE (Withholding tax code): 01

WI_TAX_BASE (Withholding tax base amount): 100

WI_TAX_AMT (Withholding tax amount in doc. currency): 10.00

For more information, see the parameter documentation for the tables HeaderData, ItemData, and WithTaxData.

Example: Incoming invoice with amount split

This example shows you which header data you can enter in the HeaderData table, which item data you can enter in the Itemdata table, and which information you can enter in the VendorItemSplitData table to create an incoming invoice with amount split.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095, item 1. The invoice is for a quantity of 10 pieces and a gross amount of $100. You want to apportion the gross amount to two creditor lines. 40% of the gross amount is to be paid immediately by check, and 60% of the gross amount is to be paid within 14 days, taking into account a 3% cash discount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X

DOC_DATE (Document date): 05.20.2000

PSTNG_DATE (Posting date): 05.23.2000

COMP_CODE (Company code): 0001

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 100.00

ItemData table

INVOICE_DOC_ITEM (Item from the invoice document): 00001

PO_NUMBER (PO number): 4500007505

PO_ITEM (PO item): 00010

REF_DOC (GR document): 50010095

REF_DOC_YEAR (Fiscal year for the current period): 2000

REF_DOC_ITEM (Item from a GR document): 1

TAX_CODE (Tax code): V0

ITEM_AMOUNT (Item amount): 100

QUANTITY (Quantity): 10.00

PO_UNIT (Unit of measure): PC

VendorItemSplitData table

1st creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0001

SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 40.00

PYMT_METH (Payment method): S

TAX_CODE (Tax code): V0

PMNTTRMS (Payment terms key): 0001

2nd creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0002

SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 60.00

PYMT_METH (Payment method): U

TAX_CODE (Tax code): V0

PMNTTRMS (Payment terms key): 0003

For more information, see the parameter documentation for tables HeaderData, ItemData, and VendorItemSplitData.

Example: Incoming Invoice with G/L and Material Account Posting

This example shows you which data you have to provide in order to enter and post an incoming invoice (header data in table HeaderData, item data in table ItemData, G/L account information in table GlAccountData, and material account information in table MaterialData).

You receive an invoice with reference to PO number 4500006846, PO item 10. The invoice is for a quantity of 100 PC of material A, a gross amount of 150.80 USD incl. 16% tax. Included in this is a G/L account posting of 10 USD to account 400000 in company code 1, and a material account posting to the material MAT01n for 20 USD.

Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_DATE (Document date): 08.05.2000

PSTNG_DATE (Posting date): 08.08.2000

COMP_CODE (Company code): 1000

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 150.80

CALC_TAX_IND (Automatically calculate tax): X

PMNTTRMS (Payment terms key): 0001

ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001

PO_NUMBER (PO number): 4500006846

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): VN

ITEM_AMOUNT (Item amount): 100

QUANTITY (Quantity): 100

PO_UNIT (Unit of measure): PC

GlAccountData table

INVOICE_DOC_ITEM (Document item in invoice document): 00001

GL_ACCOUNT (G/L account): 400000

ITEM_AMOUNT (Item amount): 10,00

DB_CR_IND (Debit/credit indicator): S

COMP_CODE (Company code): 0001

TAX_CODE (Tax code): VN

COSTCENTER (Cost center): 1

MaterialData table

INVOICE_DOC_ITEM (Document item in invoice document): 0001

MATERIAL (Material): MAT01

PLANT (Valuation area): 0001

DB_CR_INP (Debit/credit indicator): S

ITEM_AMOUNT (Item amount): 10.00

QUANTITY (MENGE_D): 1

PO_UNIT (PO quantity unit of measure): PC

TAX_CODE (Tax code): VN

More information is available in the parameter documentation for the tables HeaderData, ItemData, GlAccountData and MaterialData and in the SAP Library under Logistics Invoice Verification.

Example: Invoice for a purchase order for external services and service-based invoice verification

This example shows you which header data you must enter in the table HeaderData, which item data you must enter in the table ItemData, and which account assignment data you must enter in the table AccountingData in order to enter and post an incoming invoice.

You receive an invoice referencing PO number 4500000191, PO item 10. Two services, A and B, are invoiced, each with a quantity of six service units. Service A has a gross amount of 580 euros incl. 16% VAT. Service B has 812 euros incl. 16% VAT. Service A has an account assignment of 50% to each of the two cost centers 1000 and 2000. Service B also has a 50-50 account assignment, to cost centers 1000 and 3000. The service acceptance is performed jointly for both services in one service entry sheet, number 1000000022. You cannot change the account assignments. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X

DOC_TYPE (Document type): RE

DOC_DATE (Document date): 01.10.2002

PSTNG_DATE (Posting date): 01.10.2002

COMP_CODE (Company code): 0001

CURRENCY (Currency key): USD

GROSS_AMOUNT (Gross amount): 1392.00

CALC_TAX_IND (Calculate tax automatically): X

PMNTTRMS (Payment terms key): 0001

ItemData table

First entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000001

PO_NUMBER (PO number): 4500000191

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Item amount): 250.00

QUANTITY (Quantity): 1

PO_UNIT (Unit of measure): SU

SHEET_NO (Service entry sheet number): 1000000022

SHEET_ITEM (Line number): 10

Second entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000002

PO_NUMBER (PO number): 4500000191

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Item amount): 250.00

QUANTITY (Quantity): 3

PO_UNIT (Unit of measure): SU

SHEET_NO (Entry sheet number): 1000000022

SHEET_ITEM (Line number) : 10

First entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000003

PO_NUMBER (PO number): 4500000191

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Item amount): 350.00

QUANTITY (Quantity): 3

PO_UNIT (Unit of measure): SU

SHEET_NO (Entry sheet number): 1000000022

SHEET_ITEM (Line number) : 20

Second entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000004

PO_NUMBER (PO number): 4500000191

PO_ITEM (PO item): 00010

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Item amount): 700.00

QUANTITY (Quantity): 1

PO_UNIT (Unit of measure): SU

SHEET_NO (Service entry sheet number): 1000000022

SHEET_ITEM (Line number) : 20

AccountingData table

First account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001

SERIAL_NO (Sequential number of the account assignment): 01

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 250.00

QUANTITY (Quantity): 3

PO_UNIT (PO unit of measure): SU

Second account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001

SERIAL_NO (Sequential number of the account assignment): 02

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 250.00

QUANTITY Quantity): 3

PO_UNIT (PO unit of measure): SU

First account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000003

SERIAL_NO (Sequential number of the account assignment): 01

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 350.00

QUANTITY (Quantity): 3

PO_UNIT (PO unit of measure): SU

Second account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000004

SERIAL_NO (Sequential number of the account assignment): 03

TAX_CODE (Tax code): V1

ITEM_AMOUNT (Amount in document currency): 350.00

QUANTITY (Quantity): 3

PO_UNIT (PO unit of measure): SU

More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice for one-time vendor

This example shows you how to proceed in order to enter and post an invoice for a one-time vendor.

You do not need to enter data in the AddressData table. If you do not enter data in the AddressData table, the address data for the one-time vendor is adopted 1:1 in the invoice from the purchase order.

If you use table AddressData to transfer data, the address data for the one-time vendor is read from the purchase order into the invoice and is then either overwritten or supplemented by the fields of table AddressData.

The purchase order for the one-time vendor has the following stored data: Name 'SAP AG', postal code '60000' and street and building number 'Neurottstraße 16'. You receive an invoice with the one-time vendor address: Name 'SAP AG', postal code '69190', and place 'Walldorf'. Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): X

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

The invoice is posted with the following one-time vendor: Name 'SAP AG' street and building number 'Neurottstraße 16', postal code '69190', city 'Walldorf'.

For more information, see the parameter documentation for the table AddressData.

Example: Incoming invoice for different payee

This example shows you which address data you must enter in the table AddressData to enter and post an invoice for a different payee.

You receive an invoice for the different payee with name 'SAP AG', postal code '69190', place 'Walldorf', bank number '38070724' and account number '4711'.

Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): ' '

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

BANK_NO (Bank number): 38070724

BANK_ACCT (Bank account number): 4711

For more information, see the parameter documentation for the table AddressData.

Reward pts if found usefull 🙂

Regards

Sathish

topic BAPI FOR MIRO in Application Development and Automation Discussions

BAPI FOR MIRO

Re: BAPI FOR MIRO

Re: BAPI FOR MIRO