INVOIC02 Idoc

Question

Hi,
I am trying to create an invoice linked to a PO using inbound INVOIC02 IDocs.
I am getting an error message "Formatting error in the field BKPF-BLART; see next message". This is puzzling me as BLART does not exist in any segment and there are no further error messages. I have populated the header segment with BSART = "INVO".
In vain, I have tried using output determination to automatically output an INVOIC02 IDoc when I create one manually in MIRO, in the hope I can just change the ports to post it back in with a new ID. I have set up the condition records OK, such that a message entry automatically appears when I create the invoice with the vendor in the condition record. I have set it to process immediately. When I save the invoice, no IDoc gets created (I have done something similar for POs and that works OK). I have even tried using program RSNAST00 to kick it off, but that doesn't do anything either.
Useful answers to either problem will be rewarded. Many thanks in advance,
Peter

Answer 1

The error message is caused by missing EDI configuration. In order to post invoices successfully using inbound INVOIC02 IDocs, it is necessary to maintain configuration using transactions OBCA, OBCB, OBCC, OBCD and OBCE (these can also be accessed through SPRO under Financial Accounting - Accounts Receivable and Accounts Payable - Business Transactions - Incoming Invoices/Credit Memos - EDI).
1) In OBCA, maintain an external company code for each of the SAP company codes used in table T001. Although the field called "Company code name in the invoice" is a free text field, it must be identical (it is case sensitive too!!) to the value in the Idoc segment E1EDKA1 with qualifier ‘RE’.
2) In OBCB, set up a relationship between each SAP company code and the vendor reconciliation account. Specify a goods/services number of *
3) In OBCC, you can maintain additional account assignment details
4) In OBCD, maintain the name of the tax code from the external system and the SAP tax codes - even if you don't need to actually change the values between the systems. Maintain a tax type and rate for each country's tax codes you intend to use. These match up with the values in the Idoc segment E1EDP04.
5) In OBCE, maintain the posting keys and document types for each company code. This is where the invoice document type is taken from. There are some other interesting flags here, such as park document and create a BDC session - I've played around with the parking flag but the invoice was always posted!
Finally, make sure that your partner profile for the external system in WE20 has a process code INVL and calls function module IDOC_INPUT_INVOIC_MRM (as I was initially using INVF!)
Hopes this helps everyone as it took me 3 weeks to work out!!
Peter