Preventing re-pricing in CRM for document created in MSA

Question

Hi All,
I am trying to prevent a document (specifically a quotation) that was created in MSA being re-priced in CRM as we have differences in the pricing, specifically user exits for field catalogs which result in errors in the pricing if it is redone in CRM.
As I understand this, you should be able to control this by implementing the BADI CRM_30A_USER_EXITS Method USER_EXIT_UPLOAD_SALESDOC and set the Pricing parameter to 'A' in structure BAD_BUS_TRANSN_MESSAGE-ACTIVE_SWITCH.
However, even after implementing the code below, pricing is still re-determined in CRM, if I look at the mBDOC in TR SMW01 the entries that I wrote into the ACTIVE_SWITCH table in the BADI are not present.
Any help with this would be greatly appreciated, I've been tearing my hair out for a day and this is a major problem on our project.
Many thanks
Jason
Data declarations
  FIELD-SYMBOLS: <fs_sdgen_object> TYPE /1crmg0/sdgen_object01,
                 <fs_active_switch> TYPE bad_active_switch_mess.
  DATA: lt_fields_active TYPE STANDARD TABLE OF smog_sfldn,
        wa_fields_active TYPE smog_sfldn,
        lt_ddfields TYPE STANDARD TABLE OF dfies,
        wa_ddfields TYPE dfies,
        lv_sfavbak TYPE smo_sfavbk,
        lv_auart TYPE smo3auart,
        lv_sendbits TYPE smog_sinc-sendbits.
  CONSTANTS: lc_active_struct TYPE smog_sname VALUE 'BAD_ACTIVE_SWITCH_MESS'.
Get the order details
  LOOP AT salesdocgen_write-sdgen_object[] ASSIGNING <fs_sdgen_object>.
    lv_sfavbak = <fs_sdgen_object>-sfavbak.
    lv_auart = <fs_sdgen_object>-auart.
  ENDLOOP.
Check the order is relavant for pricing - THIS SHOULD BE CHANGED TO A CONFIG TABLE
  CHECK lv_auart = 'ZD01' OR lv_auart = 'ZD02'.
Get the active switch details
  LOOP AT bus_trans_msg-active_switch[] ASSIGNING <fs_active_switch>.
Get the table structure
    CALL FUNCTION 'DDIF_NAMETAB_GET'
      EXPORTING
        tabname   = lc_active_struct
      TABLES
        dfies_tab = lt_ddfields
      EXCEPTIONS
        not_found = 1
        OTHERS    = 2.
    LOOP AT lt_ddfields INTO wa_ddfields.
      CLEAR wa_fields_active.
      wa_fields_active-fieldname = wa_ddfields-fieldname.
      wa_fields_active-position = wa_ddfields-position.
      INSERT wa_fields_active INTO TABLE lt_fields_active.
    ENDLOOP.
Fill Sendbits
    CALL FUNCTION 'SMO_SNDBITS_SETX'
      EXPORTING
        structurename       = lc_active_struct
      TABLES
        sfields             = lt_fields_active
      CHANGING
        sndbits             = lv_sendbits
      EXCEPTIONS
        structure_not_found = 1
        wrong_fieldname     = 2
        OTHERS              = 3.
    CHECK sy-subrc = 0.
Switch off the pricing
    <fs_active_switch>-sendbits = lv_sendbits BIT-OR <fs_active_switch>-sendbits.
    <fs_active_switch>-ref_guid = lv_sfavbak.
    <fs_active_switch>-pricing = 'A'.
    <fs_active_switch>-task = '2'.
   MODIFY bus_trans_msg-active_switch FROM <fs_active_switch>.
    APPEND <fs_active_switch> TO bus_trans_msg-active_switch.
  ENDLOOP.
ENDMETHOD.

Answer 1

Hi,
I am quite sure that there is no need to do this in some BADI but on customizing level itself (depending on process type or pricing determination), at least for 4.0.
Regards,
Wolfhard