ASSIGN_TYPE_CONFLICT runtime error in CRM in program "SAPLZSMOUTIL"

Question

Hi,
We have made some mapping of BP fields from ECC to CRM and used the exit "SAPLZSMOUTIL".
As per the requirement we have created a FM Z_MW_CRM_SMOUTIL3 which contains the following Field symbol assignment:
FUNCTION z_mw_crm_smoutil3.
""Local Interface:
*"  IMPORTING
*"     VALUE(I_OBJNAME) TYPE  SMO_OBJNAM
*"     VALUE(I_OBJCLASS) TYPE  SMO_OBJCLA
*"     VALUE(I_SENDER_TYPE) TYPE  SMW1STID
*"     VALUE(I_SENDER_SITE_ID) TYPE  SMO_SITEID
*"     VALUE(I_TARGET_SITE_ID) TYPE  SMO_SITEID
*"  EXPORTING
*"     VALUE(E_DO_NOT_CALL_FLOW) TYPE  XFELD
*"  TABLES
*"      TI_BAPIMTCS STRUCTURE  BAPIMTCS
*"      T_MESSAGES STRUCTURE  BAPICRMMSG
*"      TI_KEY_INFO STRUCTURE  BAPICRMKEY
*"      TI_OTHER_INFO STRUCTURE  BAPIEXTC
*"      TI_BAPIIDLIST STRUCTURE  BAPIIDLIST
*"      TI_HEADER_MASS TYPE  MASSDATA_HEADER_T
*"  CHANGING
*"     REFERENCE(HEADER) TYPE  SMW3_FHD
*"     VALUE(MESSAGE)
*"     VALUE(MESSAGE_EXT) OPTIONAL
*"     VALUE(ERROR_SEGMENTS) TYPE  SMW_ERRTAB
*"     VALUE(OBJECT_LINKS) TYPE  TRL_BORID
*"     VALUE(E_BAPICRMDH2) TYPE  BAPICRMDH2
  DATA:
       ls_bapimtcs      TYPE bapimtcs,
       bus_ei_extern    TYPE bus_ei_extern,
       ls_txt TYPE c LENGTH 100,
       lv_lin TYPE i.
  FIELD-SYMBOLS: <fs_msg_bupa> TYPE bus_ei_main,
                 <fs_msg_bpext> TYPE bus_ei_extern,
                 <fs_r3a_main> TYPE r3a_main.
  CASE i_objname.
    WHEN 'BUPA_MAIN' OR 'CUSTOMER_MAIN'.
      FIELD-SYMBOLS: <source> TYPE x,
                     <target> TYPE x.
      ASSIGN message_ext TO <fs_msg_bupa>.
We are getting a dump in production system at  the line ASSIGN message_ext TO <fs_msg_bupa>.
The error analysis states that "You attempted to assign a field to a typed field symbol,
but the field does not have the required type."
Does anyone has any suggestion as to resolve this issue.
We are not facing issue in our quality system.
Regards,
PP

Answer 1

Hi,
I also wrote a Function Module which handled the data from the Message_ext and Message Data Objects. Those doesn't have any types and hence assigning them directly will always be a risk. So, you can have a look at the following module:
Product Material : Adapter Object : PRODUCT_MAT. Mapping Module : COM_MAP_BAPIMTCS_TO_PRODUCT.
In the code below, you will notice the Direct Assignment is avoided and in the assignment of the Field Symbols are done using the Reference Method.
* create reference to classical part:
  CREATE DATA ref_message TYPE (lv_string_classic).
  ASSIGN ref_message->* TO <classic>.
  <classic> = <classic_work>.
* create reference to messaging Bdoc:
  CREATE DATA ref_message_ext TYPE (lv_string_bdoc_tab).
  ASSIGN ref_message_ext->* TO <ddic>.
  <ddic> = <bdoc_tab>.
You need to follow a similar approach in your code.
One more thing. In order to avoid dumps in the production system, you need to handle the exceptions in all the assign operations.
Try using the TRY - CATCH Block.  [Handling Exceptions|http://help.sap.com/saphelp_nw04/helpdata/en/a9/b8eef8fe9411d4b2ee0050dadfb92b/content.htm]
The ASSIGN Catchable Exceptions are as follows:
Catchable Exceptions
CX_SY_ASSIGN_CAST_ILLEGAL_CAST
CX_SY_ASSIGN_CAST_UNKNOWN_TYPE
CX_SY_ASSIGN_OUT_OF_RANGE
Hope this helps.
Thanks,
Samantak.