Replication of CUSTOMER fields (Z fields) for a material

Question

Hi *,
I have followed a manual to replicate z fields in CRM.
I have just defined :
a Z fm in R/3 , in order to fetch a brand new material created in R/3
then  a set type with attributes and I have assigned this set type to this category and hierarchy.
Finally I have implemented the badi PRODUCT_CUSTOMER2.
The Bdoc comes empty, meant that the z fields are not transported from R/3.
I think that the fm in R/3 ,inspite off no errors is badly defined.
I think parameters of FM (export, import, tables, changing) are fine.
Have u got any example of code concerning your Z fm.
My code is the following:
FUNCTION Z_SEND_PROD_TO_CRM.
""Interfase local
*"  IMPORTING
*"     REFERENCE(I_OBJ_CLASS) LIKE  BAPICRMOBJ-OBJCLASS
*"     REFERENCE(I_OBJ_NAME) LIKE  BAPICRMOBJ-OBJ_NAME
*"     REFERENCE(I_BAPICRMDH2) LIKE  BAPICRMDH2 STRUCTURE  BAPICRMDH2
*"       OPTIONAL
*"     REFERENCE(I_KEYWORD_IN) LIKE  CRM_PARA-KEYWORD_IN
*"     REFERENCE(I_CRMRFCPAR) LIKE  CRMRFCPAR STRUCTURE  CRMRFCPAR
*"  EXPORTING
*"     REFERENCE(E_DO_NOT_SEND) LIKE  CRM_PARA-XFELD
*"  TABLES
*"      T_INT_TABLES STRUCTURE  BAPIMTCS
*"      T_BAPISTRUCT STRUCTURE  BAPIMTCS
*"      T_MESSAGES STRUCTURE  BAPICRMMSG
*"      T_KEY_INFO STRUCTURE  BAPICRMKEY
*"      T_BAPIIDLIST STRUCTURE  BAPIIDLIST
*"      T_OTHER_INFO STRUCTURE  BAPIEXTC
*"  CHANGING
*"     REFERENCE(C_BAPICRMDH2) LIKE  BAPICRMDH2 STRUCTURE  BAPICRMDH2
*"     REFERENCE(C_RFCDEST) LIKE  CRMRFCPAR STRUCTURE  CRMRFCPAR
*"     REFERENCE(C_OBJNAME) LIKE  BAPICRMOBJ-OBJ_NAME
DATA: ls_mara        TYPE mara.
*       ls_marc        TYPE marc.
Communication Structure
  DATA: BEGIN OF ls_com_key,
           struct(20),
           matnr(40),
        END OF ls_com_key.
Communication structure (additional MARA data)
  DATA: BEGIN OF ls_com_data1,
           ZZ_AREA_PR LIKE mara-ZZ_AREA_PR,
           ZZPROD_EJEC LIKE mara-ZZPROD_EJEC,
           ZZ_COD_UER LIKE mara-ZZ_COD_UER,
           ZZTIP_PROD LIKE mara-ZZTIP_PROD,
          ZZ_EMISION_PROG LIKE mara-ZZ_EMISION_PROG,
          ZZ_COD_CONTRATO LIKE mara-ZZ_COD_CONTRATO,
          ZZ_CANAL LIKE mara-ZZ_CANAL,
          ZZ_NAT_ID LIKE mara-ZZ_NAT_ID,
        END OF ls_com_data1.
Communication structure (additional MARC data)
DATA: BEGIN OF ls_com_data2,
          mfrgr(8),
          ladgr(4),
          vbamg(13),
          vrvez(7),
          vbeaz(7),
       END OF ls_com_data2.
Field Symbol for Casting BAPIMTCS
  FIELD-SYMBOLS:
      <source_x> TYPE x,
      <target_x> TYPE x.
Additional Fields used
DATA: lv_matnr TYPE mara-matnr.
DATA: ls_BAPISDCOND TYPE BAPISDCOND.
DATA: ORIGNAL_COST TYPE BAPISDCOND-COND_VALUE.
  DATA:
BEGIN **************************************************************
ATTENTION: This declaration is needed, to get the right offset for
           a later assign (to prevent alignment error at statement
           ASSIGN ... CASTING ...)
   lv_casting          TYPE f,                             "#EC NEEDED
           Never insert a new definition between LV_CASTING and
           and LS_BAPIMTCS !!!
   ct_bapimtcs         TYPE bapimtcs.
END ****************************************************************
  FIELD-SYMBOLS:
      <ledsource_x> TYPE BAPISDCOND,
      <ledtarget_x> TYPE BAPISDCOND,
      <lfs_data> type any.
DATA: gc_condition TYPE tabname30  VALUE 'BAPISDCOND'.
  CASE i_obj_name.
    WHEN 'MATERIAL'.
We want to pick up the additional fields from MARA
Mapping of MARA fields into table t_other_info
      LOOP AT t_int_tables WHERE tabname = 'MARA'.
        ASSIGN t_int_tables-data TO <source_x> CASTING.
        ASSIGN ls_mara TO <target_x> CASTING.
        IF <source_x> IS ASSIGNED AND
           <target_x> IS ASSIGNED.
          <target_x> = <source_x>.
        ELSE.
          CONTINUE.
        ENDIF.
        ls_com_key-struct  = 'MARA'.
        ls_com_key-matnr   = ls_mara-matnr.
        MOVE-CORRESPONDING ls_mara TO ls_com_data1.
        t_other_info-field1  = ls_com_key.
        t_other_info-field2  = ls_com_data1.
        APPEND t_other_info.
We want to pick up the additional fields from MARC
       lv_matnr = t_int_tables-data+3(40).
       CLEAR ls_marc.
       CALL FUNCTION 'MARC_SINGLE_READ'
         EXPORTING
           matnr = lv_matnr
STILL NEEDS SOME WORK HERE
There is a 1 to many relationship between MARA and MARC
and we need to determine how to handle this.
For testing purposes Plant 10 is hard coded
werks = '10 '
END
         IMPORTING
           wmarc = ls_marc
         EXCEPTIONS
            OTHERS = 5.
       MOVE-CORRESPONDING ls_marc TO ls_com_data2.
       t_other_info-field3  = ls_com_data2.
       APPEND t_other_info.
      ENDLOOP.
      WHEN 'LEDELIVERY'.
*t_int_tables
      LOOP AT  T_BAPISTRUCT WHERE tabname = 'BAPISDCOND'.
        ASSIGN T_BAPISTRUCT-data TO <ledsource_x> CASTING.
        ASSIGN ls_BAPISDCOND TO <ledtarget_x> CASTING.
        IF <ledsource_x> IS ASSIGNED AND
           <ledtarget_x> IS ASSIGNED.
*Following will pass data from T_BAPISTRUCT-data to ls_BAPISDCOND
*Both are having separate memory areas.
          <ledtarget_x> = <ledsource_x>.
        ELSE.
          CONTINUE.
        ENDIF.
        ORIGNAL_COST  = ls_BAPISDCOND-COND_VALUE.
*As <ledtarget_x> refers to ls_BAPISDCOND memory,
*in debugging, you can see  <ledtarget_x>-con_value becomes 5000.
        ls_BAPISDCOND-COND_VALUE = '5000'.
*<ledsource_x> refers to data field of header line (workline) of
*internal table T_BAPISTRUCT
*So following will change data field of header line of T_BAPISTRUCT
        <ledsource_x> = ls_BAPISDCOND.
      ENDLOOP.
  ENDCASE.
Any help will be considered and rewarded.
Regards,
AndreA
ENDFUNCTION.

Answer 1

Hi all,
basically bear in mind when you extend BDOCs in CRM 4.0 two things:
1.     create API structure
2.     Put x in Badi PRODUCT_CUSTOMER2 in  order to map all Z fields.
For example:
     ls_zprod_xport-data-zz0010 = ls_com_mara-ZZ_AREA_PR.
       ls_zprod_xport-data_X-zz0010 = 'X'.
Regards,
AndreA