BAPI_INCOMINGINVOICE_SAVE extensionin

[maria_merino]

Hi experts,

There is a custom field, YUUD, in an append (ZZUUID) of table RBKP.

We hace a report to create documents using bapi BAPI_INCOMINGINVOICE_SAVE  and I need to save this new field YUUD. My code is as follows:

DATA: i_extensionin TYPE TABLE OF bapiparex,
       w_extensionin LIKE LINE OF i_extensionin.

...

[fill header data]

[fill item data]

MOVE pe_factura-yuud TO wa_zzuuid-yuud.

   MOVE 'ZZUUID' TO w_extensionin-structure.
   MOVE wa_zzuuid TO w_extensionin-valuepart1.
   APPEND w_extensionin TO i_extensionin.

CALL FUNCTION 'BAPI_INCOMINGINVOICE_SAVE'
       EXPORTING
         headerdata           = headerdata
         additionalheaderdata = additionalheaderdata
         refdoccategory       = refdoccategory
*       ADDRESSDATA          =
       IMPORTING
         invoicedocnumber     = invoicedocnumber
         fiscalyear           = fiscalyear
       TABLES
*       SELECTPO             = selectpo
         selectdelivery       = selectdelivery
*       SELECTBILLLADING     =
*       SELECTSERVICE        =
*       SELECTPLANT          =
         taxdata              = itax
*       WITHTAXDATA          =
*       VENDORITEMSPLITDATA  =
         return               = return
         extensionin          = i_extensionin.

But the value is not saved into RBKP-YUUD. Is there anything wrong ? thanks in advance !

Maria

[raymond_giuseppi]

You must implement BAdI MRM_BAPI_MAPPING and map yourself your data to standard structure, but read also OSS KBA 2149315 - BAPI_INCOMINGINVOICE_CREATE and customer fields ?

Regards,

Raymond

[maria_merino]

Thanks Raymon, I'll check this Badi and tell you something.

This OSS affects bapis BAPI_INCOMINGINVOICE_CREATE/BAPI_INCOMINGINVOICE_CREATE1, but I'm using BAPI_INCOMINGINVOICE_SAVE

[raymond_giuseppi]

Seems you sniff it right out when selecting BAPI to use