Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

PO-based invoice texts

Former Member

‎2008 Jul 01 5:56 PM

0 Likes
1,275

Hi,

Does anyone know of a way in which I can populate the header "Notes" tab of a MIRO (PO-based) invoice?

I am using IDoc INVOIC02 to create my invoices and the FM behind the IDoc only populates the header and item short texts. Similarly, BAPI_INCOMINGINVOICE_CREATE does not handle long text. I have looked on OSS for relevant notes and not found any for my version (4.7). It is suspicious that there are 3 constants defined in the top include of the IDoc FM which might be useful ...

My last resort is to write code in user exit 14 of the IDoc to populate the text tables directly.

Peter

Hi,

Does anyone know of a way in which I can populate the header "Notes" tab of a MIRO (PO-based) invoice?

I am using IDoc INVOIC02 to create my invoices and the FM behind the IDoc only populates the header and item short texts. Similarly, BAPI_INCOMINGINVOICE_CREATE does not handle long text. I have looked on OSS for relevant notes and not found any for my version (4.7). It is suspicious that there are 3 constants defined in the top include of the IDoc FM which might be useful ...

My last resort is to write code in user exit 14 of the IDoc to populate the text tables directly.

Peter

Reply
2 REPLIES 2
Read only

Former Member

‎2008 Jul 03 10:01 AM

0 Likes
941

I've investigated the function module behind the IDoc processing (IDOC_INPUT_INVOIC_MRM). Text in header segment E1EDKT2 (70 bytes) populates the header text field (only 25 bytes). Text in segment E1EDPT2 (70 bytes) populates the item text field (40 bytes), obviously risking truncation. Segments E1EDKT1 and E1EDPT1 are not read at all, but instead default values are inserted.

So I've written code in user exit 14 to blank out the header text, and append each E1EDKT2 segment to structure e_rbkpv-tnote, which is then processed by FMs MRM_INVOICE_POST and MRM_INVOICE_PARK. It is important to set e_rbkpv-xnotiz = 'I' too. However, the text is only saved if you are posting an invoice. MRM_INVOICE_PARK is written so that it only saves the text if you are using transaction MIRO (compare the last block of code in the 2 FMs and the difference is clear). I have checked OSS for this and only found Note 351872, which has already been implemented in my system. So I have raised this issue with SAP and await their response.

Peter

Read only

Former Member

‎2008 Sep 01 4:35 PM

0 Likes
941

All,

SAP's response was that LIV doesn't support the parking of invoices (at least, not to the extent I am looking for), so I've had to make copies of the standard FMs as far down as MRM_INVOICE_PARK to add the processing I needed. It is vital to get the correct includes in the top include of the IDoc FM when doing this! I suspect that this may be different in ECC.

Peter