cancel
Showing results for 
Search instead for 
Did you mean: 

Vendor update, BBPUPDVD and BBP_SUS_BP_TAXNUMMAP

Former Member
0 Kudos

Hello Experts!

To update/syncronise vendors in the SRM system (with ERP) we use the transaction BBPUPDVD.

Normally it works fine.

When we update the vendor with new taxnumber we want to have 2 tax-types: DK0 and DK3.

For that purpose we found the badi MAP_MODIF.

IF_EX_BBP_SUS_BP_TAXNUMMAP~MAP_MODIF

It looked promising, but it seems that it is not called from BBPUPDVD.

Debugging did not bring any clues.

What am I missing, perhaps another program change?

Can anyone help me out here?

Here is the code in MAP_MODIF, pretty much the suggested code.

DATA:
     lt_taxnum TYPE bbp_bupa_suppl_taxnum_tab,
     ls_taxnum TYPE dfkkbptaxnum.
     lt_taxnum = ct_taxnum.

   REFRESH ct_taxnum.


LOOP AT lt_taxnum INTO ls_taxnum.
     IF iv_country = 'DK'.   
       case ls_taxnum-taxtype.
          when 'DK0'.
               ls_taxnum-taxtype = 'DK0'.
               APPEND ls_taxnum TO ct_taxnum.
          when 'DK3'.
               ls_taxnum-taxtype = 'DK3'.
               APPEND ls_taxnum TO ct_taxnum.
       endcase.
     ENDIF.
    ENDLOOP.

Best regards,

Jeanette

Accepted Solutions (1)

Accepted Solutions (1)

ivy_li
Active Contributor
0 Kudos

Hi Jeanette,

BADI BBP_SUS_BP_TAXNUMMAP won't be called during vendor replication.
For bbpupdvd, please check the coding design in FM BBP_VENDOR_GET_NON_BAPI where it determineds the taxtype.

If you want to realize your own, you can modify the FM.

BR, Ivy

Answers (1)

Answers (1)

Former Member
0 Kudos

Thank you Ivy fo thre response.

I never came to try  your suggestion. It turned out that the problem was somewhere else.

Normally the system creates both DK3 and DK0, but in SRM the validation rules rejected the taxnumbers we tested. In ERP the validation has been turned off whereas we could use any taxnumber.

Br

Jeanette