teachSAP: LIV

New processing functionality has been added to the MIR7 - Park Invoice Transaction. The new processes, listed below will be effective Thursday, September 9, 2004.
Paying invoices when the unit price of the invoice is less than the unit price listed in a Purchase Order (PO). An error situation will occur if one attempts to process an invoice that is $750 or 30% less than the unit price listed in a purchase order line item. This functionality is being instituted to aid in the prevention of exhausting the entire quantity of a PO line item when making partial invoice payments. The following error message will be displayed when the conditions of the tolerance are met: “Price too low (below tolerance limit of $750 or 30%”). If you encounter this error, please review and compare the quantity entered in the MIR7 transaction against the actual quantity of the invoice being paid. In most cases, changing the quantity in the MIR7 transaction to match the quantity being invoiced will resolve the error. If the invoice price is accurate and the unit price is $750 or 30% less than the unit price of the PO, please contact your local purchasing department to discuss a possible modification of the PO.
Paying invoices against expired framework orders (FOs). All invoices and credit memos for purchases made during the effective period of a framework order must take place within 60 days after the expiration date of a FO. This rule applies to all framework order types. Attempts to enter invoices or credit memos with a posting date greater than 60 days past the FO expiration date will result in the following error: “Blanket purchase order 6500000000: validity (01/01/2003 – 01/01/2004) not complied with”. If you encounter this error, please use transaction ZME_NEW_FO_NBR - Find New Purch Contract FO Nbr to determine if a new framework order has been issued for the requirements of the expired FO. This transaction is appropriate for FOs that are issued against purchasing contracts and is not applicable to department specific FOs. Input the old framework order number in the appropriate field of the displayed transaction and select the execute button. If a new FO has been issued the new FO number will be displayed. In most cases you may use the new FO number in making your invoice payment. (**A word of caution about using a new FO number – please compare the vendor in the new FO to the vendor in your invoice. If the vendor in the new FO is not the same as the vendor in the old FO – do not use the new FO number.) If an invoice is greater than 60 days past the expiration date of the FO and a new FO has not been issued, you will need to contact your local Purchasing Department to discuss your options in processing the invoice.
Determining when framework orders expire: Copies of department FOs are forwarded to the department of record and the FO document will contain the expiration date. You may also access transaction ZME_FO_EXP_DT - Framework Order Expiration Date. This transaction is applicable to all FO types. Enter the FO number or a vendor number in the selection screen that will be displayed and select the execute button. The expiration date of the FO will be displayed. Additionally, for FOs issued by the UTK Purchasing Department against purchasing contracts, you may access the UTK Purchasing web site and monitor the status of purchase contract/FO that is scheduled to expire. Once the UTK Purchasing web site is accessed - select the “Announcements link”. Instructions have been attached that will aid in adding the UTK purchasing web address in the favorites section of your SAP main menu. Please note: Purchases should not be made against a framework order after it has expired. Any questions concerning framework order validity periods or the proper framework order to use in processing an invoice should be directed to your local purchasing department for additional clarifications.

MIR7 Park Invoice Functionality

Sunday, 14 March 2010

FU BAPI_INCOMINGINVOICE_CREATE

___________________________________________________
Short Text
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.

Parameters
HEADERDATA
ADDRESSDATA
INVOICEDOCNUMBER
FISCALYEAR
ITEMDATA
ACCOUNTINGDATA
GLACCOUNTDATA
MATERIALDATA
TAXDATA
WITHTAXDATA
VENDORITEMSPLITDATA
RETURN
EXTENSIONIN

Exceptions
Function Group
MRM_BAPI

Monday, 1 March 2010

SAP Note: 800866 Invoice IDoc with Unplanned Delivery Cost

In MM, an invoice cannot be posted if delivery costs were specified whenthe invoice was created in SUS. The IDoc terminates with status 51 'application document not posted' and the system issues error message M8 534 'Balance not zero'. The balance corresponds to the delivery costs.

Reason and Prerequisites

The delivery costs are not read in MM in standard inbound processing.

Solution

If you want to sendi nvoiceswith delivery costs from SUS to MM, you must use Transaction CMOD to program the EXIT_SAPLMRMH_014 user exit as follows:

Create a customer project and use Transaction CMOD to call it. Add the MRMH0002 enhancement and the EXIT_SAPLMRMH_014 component. Insert the source code into the ZXM08U25 include.

DATA: ls_data_s01 type E1EDS01,
lv_beznk type MRM_RBKPV-beznk.

IF I_IDOC_DATA-SEGNAM = 'E1EDS01'.
ls_data_s01 = I_IDOC_DATA-SDATA.

IF ls_data_s01-sumid = '020'.

lv_beznk = ls_data_s01-summe.

E_RBKPV-BEZNK = lv_beznk.

E_CHANGE = 'X'.

ENDIF.

INVOICE UNPLANNED DELIVERY COST IDOC

To post unplanned delivery cost using INVOIC01 we referenced OSS Note
800866. We continued to have issues with determining the tax jurisdiction
code and received this response:
I have done a detailed analysis and the
solution I propose is to use the FM 'EXIT_SAPLMRMH_014'. The options
are:
1. If the field TXJCD is blank in the idoc and if the tax code for the
unplanned delivery cost is same in invoice item and in the refered
PO item, then you can fill E_RBKPV-TXJCD_BNK from the PO item in the FM
'EXIT_SAPLMRMH_014'.
2. If the tax code for the unplanned delivery cost is not same as the
tax code in invoice item or in the refered PO item, you can find the
TXJCD from the tax condition's data for the tax code and copy it to
E_RBKPV-TXJCD_BNK within the user exit.
3. If the field TXJCD is filled in the idoc, you can fill the
E_RBKPV-TXJCD_BNK in the user exit from here.
We choice option 3 and we are successfully posting unplanned delivery cost
using INVOIC01.

GRN INVOICE WORKFLOW

We have a workflow which is triggered when an invoice is parked. It sends a work item to the contact center project manager to create a GRN.

Our problem is that when the GR is created through the transaction and not through the work item, the work item remains in the user's inbox. Is there a way to change the status of the work item to 'complete' and remove it from the user's inbox?

What I would do in this case is put in a parallel step with the work item that listens for the creation of the GR. When this event is received, the parallel step will terminate the work item in the user's inbox.

There is another approach which is to use terminating events on the work item but this requires you to specify the GR creation method as asynchronous.

Can I park incoming invoices when no goods entry is posted?

EXPERT RESPONSE FROM: Axel Angeli

QUESTION POSED ON: 13 May 2003
I am working with INVOIC01 in 4.6C using INVL as the process code. The problem I am having is that I want to post or park an invoice when goods receipt has not been posted. It seems that SAP rejects such invoices by default. Unfortunately, the majority of invoices have no goods receipt when received through EDI.
Also, is there a way to automatically clear these invoices when goods receipts arrive?

This is an application issue of your MM-PUR customizing.
The IDoc is handed over by the IDoc engine to application processing. It is the application that rejects the invoice. You have to see this issue with your MM-PUR functional team so that they set up customizing or prepare a user-exit that allows to accept invoices in this cases. Automatic clearance of blocked invoices has not been possible in older releases. I have not checked if it possible in 4.6. What you can do, is set up a custom workflow that does the job triggered by the goods receipt.

MESSAGE TYPE FOR SELF BILLING OR ERS

I have a question about SBWAP message type and EDI. I am looking to send ERS output (self-billing invoice), which generates IDocs with Message Type SBWAP, to suppliers using EDI X12. Which EDI message type (ANSI X12) can I use to send this? Do you know of any company that sends SBWAP to suppliers?

Self billing is usually done via FM IDOC_OUTPUT_GSVERF and IDoc type GSVERF01 . The matching ANSI X.12 transaction is 810 (invoice/credit). Any of the automotive manufacturers (Daimler, Ford, Volkswagen BMW, Peugeout, Renault, etc.) use self billing intensively, and so do many of the bigger automotive suppliers in the context of central billing.

Vendor invoices and adapting to unexpected charges or discounts

Suppose a vendor's invoice includes an unanticipated surcharge, discount or freight charge at the HEADER level (=not at the PO-line-item level). Such an amount was not part of the original PO, so we'd be booking a non-PO-based additional amount. How can we book the unanticipated charge using the INVOIC02 IDOC?

One approach might be to create an additional E1EDP01 segment, (or the appropriate sub-segments, like E1EDP26, etc.), but then SAP would want to know the GL account (and cost center?) to which book that amount. I cannot determine which INVOIC segment would carry such account-assignment information.

The offset to that additional E1EDP01 segment would be to adjust the net amount of the invoice within the E1EDS01 segment (SUMID = 010 for net amount, SUMME for the new net amount, WAERQ for the currency-code).

Can you provide some assistance?
===============================

The question you raise needs to be properly discussed with your auditors. Generally it can be said that an incoming billing IDoc is a legal document, like a paper invoice is also a legal document. This means that you are not allowed to change the information contained therein when booking them into your system. So if unexpected surcharges occur, you have to book them as it is sent by the vendor.

How to book the additional amounts? Mapping them into an additional E1EDP01 may be the proper approach. Finding the correct GL account is not the task of the IDoc mapping software, however, but needs to be carried out automatically (or with some assistance of the billing manager) within R/3. Usually this works the same way as it does when you would create a new item in your purchase order. I have limited information about how your SAP installation is set up, but a common approach would be create an appropriate item category and customize the finding of the proper COPA and FI accounting from the item category.

But principally, your approach is designed well, and should work that way

Unplanned Delivery Cost – Idoc - Invoic02

Use the user exit EXIT_SAPLMRMH_014.

OSS note 119092 identifies the solution to not being able to process planned freight as processing it as unplanned freight.

You can account unplanned delivery costs with the aid of User Exit EXIT_SAPLIEDI_111 (for Transaction MR01) or EXIT_SAPLMRMH_014 (for Transaction MR1M / MIRO.

FU EXIT_SAPLMRMH_014
____________________________________________________
Short Text
Customer Exit: EDI Invoice Receipt - Change IDoc Segment

Functionality
This customer-specific function module is called after the system has read each IDoc segment while processing IDocs. This allows you to use the information in each IDoc segment to determine data in the invoice document to be created in a different way to that in the standard system. In addition to the IDoc segment, the document header data and the document items created so far are available.

Notes
The system only adopts the change if parameter E_CHANGE = 'X' is passed on.

Parameters
I_IDOC_DATA
E_CHANGE
E_RBKPV
T_FRSEG

Exceptions
ERROR_MESSAGE

Function Group
XM08

SAP R/3 форум ABAP консультантов View topic - IDoc User Exit List

IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
- ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
- ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
- ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
- ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
- ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
- ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
- ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
- MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
- MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
- MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
- MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
- VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
- VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
- VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
- VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
- LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
- MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
- CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
- CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
- VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
- VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
- VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
- VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
- F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
- F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
- FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
- FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
- F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
- VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
- RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
- RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
- RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
- MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
- MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
- FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
- FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
- FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
- FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
- FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
- FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
- FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
- FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
- FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
- MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
- MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
- MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
- MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
- MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
- WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
- MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
- SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
- VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
- VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
- VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
- VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
- VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
- VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
- VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
- VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
- VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
- VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
- MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
- MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
- MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
- MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
- VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
- VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
- VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
- VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
- VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
- VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
- VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
- VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
- VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
- VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
- VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
- WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
- MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
- MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
- MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
- WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
- SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
- SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
- WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
- FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
- FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
- VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
- VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
- VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
- VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
- VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
- VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
- VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
- VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
- VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
- VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
- VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
- VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
- VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
- VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
- VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
- VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
- VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
- V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
- V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
- V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
- V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
- V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
- V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
- MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
- MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
- BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
- BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
- V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
- V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
- V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
- V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
- V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
- V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
- V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
- V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
- V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
- MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
- MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
- MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
- MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
- MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
- MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
- WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
- WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
- WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
- WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
- WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
- WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
- WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
- WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
- WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
- WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
- WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
- WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
- WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
- WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
- WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
IDoc Outbound User Exits
72. ACCONF
Confirmation of IDoc processing from the application
- ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
- ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
- ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
- ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
- ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
- ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
- ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
- MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
- MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
- MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
- MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
- VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
- VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
- VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
- VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
- MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
- MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
- FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
- CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
- CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
- CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
- CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
- F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
- F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
- F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
- FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
- FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
- FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
- FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
- FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
- F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
- MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
- RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
- RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
- RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
- MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
- LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
- LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
- LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
- LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
- MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
- MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
- WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
- MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
- MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
- MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
- MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
- MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
- MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
- MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
- SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
- SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
- SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
- SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
- SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
- SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
- SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
- SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
- WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
- WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
- FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
- FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
- FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
- FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
- VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
- WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
- WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
- VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
- VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
- VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
- WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
- FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
- VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
- VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
- VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
- VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
- VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
- VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
- VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
- VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
- MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
- BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
- BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
- SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
- SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
- SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
- SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
- SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
- SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
- SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
- V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
- V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
- V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
- V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
- V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
- V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
- V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
- WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
- MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
- MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
- MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
- MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
- WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
- WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
- WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
- WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
- WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
- WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
- WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
- WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
- WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
- WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
- WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
- WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
- WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
- WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
- WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
- WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc

SAP R/3 форум ABAP консультантов View topic - IDoc User Exit List

Tuesday, 23 February 2010

payment block, - Toolbox for IT Groups

payment block,

Asked by gangadhar.redd... on 4/19/2004 5:59 AM

Hi,
We have 3 invoices which are blocked for payment due to Schedule date
variance. While doing MRBR these document does not show up to release for
payment, Not able to understand what is the problem. System shows the
message "M8 658 :- no blocked invoices found". There is note 679788 on
message # M8 657. can I implement it in this situation? Would it give the
expected results!!

payment block, - Toolbox for IT Groups

Tuesday, 16 February 2010

Payment Block

Payment block R can come for various reasons like delivery schedule,terms of payment,quality reasons etc.
Use
You can block an invoice manually. You have two options for doing this when you enter the invoice:
You can block an invoice by entering an R in the field Payment block in the document header data.
You can block an item by selecting the M (manual blocking reason) field in the item list. When you post the invoice, the system automatically sets an R in the field Payment block in the vendor line of the accounting document. Manually blocked items are given the blocking reason Manual block (M).

================================================================================================================================================================================================

Re: Prevent removal of invoice verification paymt block in F

Guys, what the hell you are talking about? It's much more simple... Tr. OB27. the very right column - "not changeable". Blocking indicator R should have this tick (plus check box "manual payment block to be not ticked), all other blocking indicators which are supposed to be set/removed through FB02 - not ticked (along with check box "manual payment block ticked), it does the job.

================================================================================================================================================================================================

Invoice verification Error Message

Every time I try to do invoice verification in MM, I get the message below. PL tell me how I can resolve the issue. And also The amount you enter by default is alaways in USD, could we use any other Currency.
Error Msg --> You may only enter amount upto USD 10,000.00

Hi,
Go to SPRO > MM > Logistics Invoice Verification > Authorization Management > Define Tolerance Groups
Here check the following;
Amount per document
Amount per open item account item
Cash discount per line item
And increase the amount if you want
Here we do following activities;
1. By choosing Edit -> New entries, you create a new combination of tolerance group and company code.
2. To reach the allocation table on the detail screen, position the cursor on a line and choose Details. Enter the maximum permissible values for the tolerance group in the area "Upper limits for posting procedures".
The area "Permitted payment differences" is only important for employees in Financial Accounting.
SPRO > MM > Logistics Invoice Verification > Authorization Management > Assign User Tolerance Group > Here Assign a tolerance group to each user
If you don't want this message for the user then delete this user ID from this and then check

================================================================================================================================================================================================

Manual Payment Block

You can remove payment block manually by following method aprat from MRBR:

In purchasing at the time of posting.

Go to :Logistics >> Material management >> Purchasing >> Purchase Order>> Follow-on Functions >> Logistics Invoice Verification >> EnterInvoice(MIRO)

Step 1
To remove a block at the time of posting, you must access the payment document (51XXXXXXXX) immediately after completing theposting. Click on Invoice document >> Display
The document you just posted will be displayed. Click on Following Documents.
A pop-up box listing the accompanying (system created documents) is displayed.
Click on Accounting document. The invoice document will be displayed.

Step 2
Double click on the vendor line item, which is the first line item to display the payment screen.
If this in an OTA Vendor, you will need to click on or hit enter when the Address screen appears
To remove the block, simply click on the change icon, this will open the Pmnt block field for change. Delete the R and click onto save the document.

2.In accounts payable after posting.
Accounting >> Financial Accounting >> Accounts Payable >> Document >> Change
To remove a block after posting, you must access the payment document (51XXXXXXXX) through Accounts Payable and remove the block.

At the Change document: Initial screen, enter the document number and press enter.
Double click on the vendor line item (line item 1) to display the payment screen.
If this in an OTA Vendor, you will need to click on or hit enter when the Address screen appears.

In the Pmnt block field, the R (Invoice verification) must be removed. To remove the block, simply delete the R in the Pmnt block filed and click on
to save the document.

Sunday, 14 February 2010

MM-IV-LIV-MRBR Invoice Release in LIV Transaction MRBR

Welcome Guest

Added by Guest , last edited by Guest on Jun 04, 2009 (view change)

Labels:

(None)

Add Labels

Wait Image

Enter labels to add to this page:

Tip: Looking for a label? Just start typing.

Content

Use and Overview

Before you can pay a blocked invoice, you must release it in a separate step. You do so by canceling the blocking indicator that was set when the invoice was posted.
Since the total invoice amount is to be paid and not individual invoice items, the blocking indicator is set in the vendor line of the accounting document. As a result, all the items in an invoice can only be released at the same time.
MR02: invoice release transaction for blocked invoices that were posted in CIV (MR01)
MRBR: invoice release transaction for blocked invoices that were posted in LIV
Releasing LIV blocked invoices that were posted before 4.6A: MR02 or MRBR if you first convert them with report RM08RBKPBLOCKED
two processes for releasing invoices for payment:
- Releasing Automatically
- Releasing Invoices Manually

Settle with transaction MBRR: selection

Move cash disc. Date:
- To specify when exactly an invoice is to be paid, you agree terms of payments with the vendor. These terms of payment contain the baseline date from which your cash discount period applies. If an invoice was blocked for payment for a long time, your cash discount deadline could expire. If you release this invoice, you can select the field Move cash discount date on the initial screen of the invoice release transaction and retain the agreed cash discount.
Canceled invoices are not taken into account.

Settlement with transaction MBRR: Releasing Automatically

Use
When you release invoices automatically, the system deletes all blocking reasons that no longer apply.
When all blocking reasons in an invoice are deleted, the system automatically releases the invoice.

Prerequisites
It is only possible to automatically release invoices if their blocking reasons are no longer valid. This can be the case for invoices blocked due to quantity, price, or schedule variance s, or due to quality inspection.
You can only use the function Release automatically for the blocking procedure Blocked due to variances.

Result
The system issues a list of the invoices released. The system will also release invoices for which a manual block was set in the document header if the blocking reasons in all items no longer apply.

Settlement with transaction MBRR: Releasing Manually

Deleting Blocking Reasons

Use
You can delete individual blocking reasons while processing a blocked invoice item.

Procedure

Place the cursor on the blocking reasons that you want to delete.
Choose Delete blocking reasons. The system highlights the deleted blocking reason in color.
Check your entries.
Choose Save changes.

Result
If there are other blocking reasons in this item or other items in the invoice, you receive a message
indicating that the selected blocking reason was deleted.
When you delete the last blocking reason in an invoice, the system automatically releases the invoice. The following message appears:
nn invoice(s) released

Releasing Invoices

Use
When you release an invoice, the system reverses the blocking indicator in the accounting document for the invoice. In the vendor line, the R in the field Payment block is deleted.

Procedure

Select the invoice document that you want to release. The system automatically selects all other items in the invoice since you cannot release individual items.
Choose !6 Release Invoice.jpg!Release invoice.
Check your entries.
Choose Save changes. The invoices selected are only released for payment when you save them.

Technical details: Database Structure

Database Structure of Incoming Invoice:

RBKP: Header data of an Incoming Invoice
RSEG: Item data (reference to a PO)
RBMA: Item data (reference to a material)
RBCO: Item data (Direct posting to G/L account)

Specialities of an Incoming Invoice blocked for payment:

There exists a record in the index table RBKP_BLOCKED (containing 10 fields for fast selection of blocked invoices)
Important field in RBKP_BLOCKED: Logistics payment block (MRM_ZLSPR) with possible values
- A Automatically blocked due to existence of blocking reasons
- S Stochastically blocked
- M Manual payment block set in header - no blocking reasons
In an automatically blocked invoice (MRM_ZLSPR = 'A') there is at least one blocking reason in RSEG / RBMA / RBCO:

Database structure of the FI follow-on document:
- First (vendor) BSEG Item: Payment Block is set (BSEG-ZLSPR = ‚R')
Attention: RBKP contains exactly the data the user has entered, so RBKP-ZLSPR is only filled when the user has entered a value. This means
- The field RBKP-ZLSPR is not necessarily set in the case of blocked invoices:
- The field RBKP-ZLSPR will never be changed in the Release process

Technical Details: RM08RELEASE - Overview Flow Logic

Technical Details: Debugging tips (1)

Why does MRBR not show an invoice as blocked for payment?

First check the corresponding database entries (RBKP_BLOCKED, first BSEG item: BSEG-ZLSPR)
Debugging: breakpoint on SELECT of RBKP_BLOCKED in RM08RELEASE:
...
START-OF-SELECTION.

* Selection from RBKP_BLOCKED -----------------------------------------*
SELECT * FROM rbkp_blocked INTO TABLE tab_rbkp_blocked
       WHERE    mrm_zlspr = f_mrm_zlspr
         AND    bukrs      IN so_bukrs
         AND    gjahr      IN so_gjahr
         AND    lifnr      IN so_lifnr
         AND    belnr      IN so_belnr
         AND    usnam      IN so_usnam
         AND    budat      IN so_budat
         AND    faell      IN so_faell
         AND    ekgrp      IN so_ekgrp.
...

Technical Details: Debugging tips (2)

Why does (does not) MRBR release an invoice automatically?

Check the prerequisites for releasing invoices automatically. Check if with processing option „release manually", blocking procedure „blocked due to variances" the blocking reason is white (~valid) or coloured (~not valid)

Why does MRBR show a blocking reason as valid (not valid)?

Check the IMG documentation of the corresponding tolerance key.
Debugging:
Put a breakpoint on:
RM08RELEASE form BLOCKING_REASON_VALIDITY_CHECK
Put another breakpoint on
function module: MRM_TOLERANCE_CHECK
(MRM_TOLERANCE_CHECK is executed e.g. in RM08RELEASE from function module MRM_BLOCK_REASON_VAL_CHECK_P which is called from BLOCKING_REASON_VALIDITY_CHECK for tolerance key PP.
MRM_TOLERANCE_CHECK is also the function module which -in general- determines whether an invoice is blocked for payment when you post it e.g. with MIRO)

Technical Details: RM08RELEASE - Summary

Transaction MRBR
Report RM08RELEASE
Works only for documents of LIV when they have a record in the index table RBKP_BLOCKED. Cancelled Invoices are not selected by MRBR because they do not have a RBKP_BLOCKED entry.
Selection Screen: like a usual report
List: ALV
Automatic Release in the background possible
Database update not immediately but after saving explicitly

Update of the Incoming Invoice

Deletion RBKP_BLOCKED
Deletion blocking reasons in RSEG if necessary
Update of FI follow-on document (Deletion BSEG-ZLSPR) via Accounting Interface (TRWPR-PROCESS = ‚PYMNTBLK')
- AC_PAYMENTBLOCK_CHECK