CRM-XI integration using Idoc

Hi all,
I search document that describes, how to connect XI from CRM using Idoc.
I`ve found an Description, but using BC.
which RFC destination type should be use (TCP/IP-Connection Destination type ? or logical Destination type? or ..)
Which setting I'd like on CRM site ?
Which Connection parameter I'd Llike ...
Thanks in Advence.
Regards.
Lemin

Hi
Go to https://websmp102.sap-ag.de/instguides->mySAP Business Suite Solutions->mySAP CRM
CRM Learning-
https://websmp203.sap-ag.de/rkt
Check here-
SRM/CRM/XI
CRM Middleware & XI
Go to https://websmp102.sap-ag.de/instguides->mySAP Business Suite Solutions->mySAP CRM
also check
http://www.sapgenie.com/mysap/crm/index.htm
http://www.sapgenie.com/mysap/crm/middleware.htm
http://eai.ittoolbox.com/groups/technical-functional/webmethods-l/sap-exchange-connector-xi-364858#
http://help.sap.com/saphelp_crm40/helpdata/en/c3/95fc381478ab6fe10000000a11402f/frameset.htm
For XI
http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
BW WITH CRM:
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
http://help.sap.com/saphelp_nw04/helpdata/en/af/ed833b2ab3ae0ee10000000a11402f/frameset.htm
Check threads for possible 'error' handling:
CRM Data source issue with Delta Load( For BW Gurus only)
Re: Activities : 0CRM_SALES_ACT_1
Re: CRM Service Contracts : no records with 0CRM_SRV_CONTRACT_H
Thanks !!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Regards
Abhishek Agrahari

Similar Messages

  • Creating a BP in CRM through LSMW using IDOC

    I am trying to create a buss partner in crm through LSMW using IDOC:
    Message Type:  CRMXIF_PARTNER_SAVE_M
    Basic Type:       CRMXIF_PARTNER_SAVE_M02
    I get an error: "No update is defined for BP role 000000".
    I am also filling
    IDENTIFICATIONCATEGORY: CRM001
    IDENTIFICATIONNUMBER:     12345678
    However i get this error only if the external ID does not exist in table BUT0ID.
    otherwise if the external ID is present in table BUT0ID and the object task is "U"pdate, the BP is saved.
    Has anybody worked on BP creation using IDOCs? If yes please guide me.

    Hi,
    This Check Box is required for Archiving Business Partners from the System. You can have a full idea about the same from the link below [Archiving Business Partners|http://help.sap.com/saphelp_crm60/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm]
    Also have a look at the following [Introduction to Data Archiving (CA-ARC)|http://help.sap.com/saphelp_crm60/helpdata/en/8d/3e4c11462a11d189000000e8323d3a/frameset.htm]
    Hope this helps.
    Thanks,
    Samantak.

  • SAP Cloud for Customer & SAP ECC/CRM OnPremise integration using WebServices!

    Hello All,
    I would like to ask if anyone has really created a working integration scenario between a Cloud Solution & an ECC/CRM OnPremise solution?
    We are trying to build some prototypes for this, however, due to connectivity errors/issues, unable to proceed.
    I'm looking for information on:
    > What certificates precisely are needed on both Cloud & OnPrem systems?
    > What configuration if any is required on Cloud & OnPrem solution, except for communication system/arrangements on Cloud solution?
    > Any use case if available from anyone which can demo integration between Cloud solution & ECC/CRM OnPremise solution.
    I'd really appreciate responses on this.
    Many Thanks
    Ankur

    Thanks Sathya for the response.
    https://scn.sap.com/community/cloud/blog/2013/10/10/new-e-learning-for-i
    ntegration-of-sap-cloud-for-customer-with-sap-erp-and-sa
    p-crm-now-available  : Not working! => Please check & confirm.
    Just to give you our background...we are SAP Cloud Partners & VARs, hence we are building few prototypes for Customer Demos & POC.
    Per my understanding, its just one of the OnPrem system, either an ECC OnPrem or CRM OnPrem that you can integrate with one C4C tenant at a time, i.e. to one single tenant. In our case, we are trying to integrate ECC OnPrem with C4C system.
    We are in the process of deploying SAP PI as the middleware platform for integration between C4C & ECC/CRM OnPrem., which is going to take few more weeks.
    SAP HCI will be the other approach, but we are currently not familiar with that, hence we have a trial to start in coming week for SAP HCI, so this is going to take some time as well.
    Hence, WebService is the only currently available option for us to build these prototypes, POC for Customer Demos, to show working integration scenarios between ECC OnPrem & C4C system.
    We have been facing some technical issues after setting up necessary communication systems/arrangements on C4C system & trying to do a WS call from SDK also we get error when we do a ping test from within C4C system to check connection.
    Has SAP developed any WS integration between C4C & either of the ECC or CRM OnPrem system? Or is it just PI & HCI which SAP has for integration?
    I'd truly appreciate if you can guide us on creating few integration scenarios (Working ones of course ) using Webservice between C4C & ECC OnPrem system.
    Many Thanks
    Ankur

  • Transfer data from one server to another server using idocs

    hi,crm
       i have a data in crm system, i want to download this data and upload into another crm system by using idocs.
      please any one explain.

    Hi Ravi,
          my senario is i have to transfer  data from  crm 5.0 to 7.0.
          i have marketing attributes
        t-code: bp----> marketing attributes
       i want to transfer marketing attributes from A to B.
           i created one structure for marketing attributes around 160. and i added this structure fields into custom segments.
          i created custom idoc type and i added segments into idoc.
        i created one function module for getting data from structure and passing to segments and idoctype.
       check the code below.
    FUNCTION ZCRMXIF_MKT_DATA.
    *"*"Local Interface:
    *"  IMPORTING
    *"     REFERENCE(EV_MKT_ATTR) TYPE  ZCRMXIF_MKT_STR
    Data : c_segment type ZE101CRMXIF_MKT_ATTR_DATA,
           c_segment1 type ZE101CRMXIF_MKT_ATTR_DATA1,
           c_segment2  type ZE101CRMXIF_MKT_ATTR_DATA2,
           c_segment3 type  ZE101CRMXIF_MKT_ATTR_DATA3,
           c_segment4 type  ZE101CRMXIF_MKT_ATTR_DATA4.
    data:  c_messagetype type c value'zcrmxif_partner_save',
           c_idoc_type type c value'zcrmxif_partner_save_mkt',
           idoc_control like edidc,
           t_comm_control like edidc occurs 0 with header line,
           idoc_data like edidd occurs 0 with header line.
    data: lt_mkt_attr type Zcrmxif_mkt_str occurs 0 with header line,
           ls_mkt_attr like zcrmxif_mkt_str.
    loop at lt_mkt_attr.
                c_segment-PARTNER = lt_mkt_attr-partner.
                c_segment-PARTNER_GUID = lt_mkt_attr-partner_guid.
                  idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA' .
                  idoc_data-sdata = c_segment.
                 append idoc_data.
               c_segment1-ADHAR_NUM = lt_mkt_attr-ADHAR_NUM.
               c_segment1-ADULTS = lt_mkt_attr-ADULTS.
               c_segment1-AGEGROUP = lt_mkt_attr-AGEGROUP.
               c_segment1-AG_CODE = lt_mkt_attr-AG_CODE.
               c_segment1-AMERICANEXPRESS = lt_mkt_attr-AMERICANEXPRESS.
               c_segment1-ANNUALINCOME = lt_mkt_attr-ANNUALINCOME.
               c_segment1-AUTO_TYPE_1 = lt_mkt_attr-AUTO_TYPE_1.
               c_segment1-AUTO_TYPE_2 = lt_mkt_attr-AUTO_TYPE_2.
               c_segment1-AUTO_TYPE_3 = lt_mkt_attr-AUTO_TYPE_3.
               c_segment1-A_HOMEDEL = lt_mkt_attr-A_HOMEDEL.
               c_segment1-BANKNAME = lt_mkt_attr-BANKNAME.
               c_segment1-BLOODPRESSURE = lt_mkt_attr-BLOODPRESSURE.
               c_segment1-BPRELATION = lt_mkt_attr-BPRELATION.
               c_segment1-BRAND = lt_mkt_attr-BRAND.
               c_segment1-CC1001 = lt_mkt_attr-CC1001.
               c_segment1-CC1002 = lt_mkt_attr-CC1002.
               c_segment1-CCCLASSIC = lt_mkt_attr-CCCLASSIC.
               c_segment1-CCGOLD = lt_mkt_attr-CCGOLD.
               c_segment1-CCOTHERS = lt_mkt_attr-CCOTHERS.
               c_segment1-CCPLAT = lt_mkt_attr-CCPLAT.
               c_segment1-CCREDIT = lt_mkt_attr-CCREDIT.
               c_segment1-ccsilver = lt_mkt_attr-ccsilver.
               c_segment1-CCTITA = lt_mkt_attr-CCTITA.
               c_segment1-CDEBIT = lt_mkt_attr-CDEBIT.
               c_segment1-CHILDREN = lt_mkt_attr-CHILDREN.
               c_segment1-CITIBANK = lt_mkt_attr-CITIBANK.
               c_segment1-CNAPP = lt_mkt_attr-CNAPP.
               c_segment1-CNC_PRINT = lt_mkt_attr-CNC_PRINT.
               c_segment1-CNC_SIZE = lt_mkt_attr-CNC_SIZE.
               c_segment1-CNC_SIZE_NEW = lt_mkt_attr-CNC_SIZE_NEW.
               c_segment1-CNC_STATUS = lt_mkt_attr-CNC_STATUS.
               c_segment1-CNC_TIME_ZONE = lt_mkt_attr-CNC_TIME_ZONE.
               c_segment1-CNC_TIME_ZONE_NEW = lt_mkt_attr-CNC_TIME_ZONE_NEW.
               c_segment1-CONDFIRSTZ = lt_mkt_attr-CONDFIRSTZ.
               c_segment1-COMPANY = lt_mkt_attr-COMPANY.
               c_segment1-CONDSECOND = lt_mkt_attr-CONDSECOND.
               c_segment1-CONDTHIRD = lt_mkt_attr-CONDTHIRD.
               c_segment1-CUSTOMERTYPE = lt_mkt_attr-CUSTOMERTYPE.
               c_segment1-CUST_BUSINESS_NAME = lt_mkt_attr-CUST_BUSINESS_NAME.
               c_segment1-DECL_DATE = lt_mkt_attr-DECL_DATE.
               c_segment1-DED = lt_mkt_attr-DED.
               c_segment1-DIST = lt_mkt_attr-DIST.
               c_segment1-DNC = lt_mkt_attr-DNC.
               c_segment1-DNCEMAIL = lt_mkt_attr-DNCEMAIL.
               c_segment1-DNCPHONE = lt_mkt_attr-DNCPHONE.
               c_segment1-DNCPOST = lt_mkt_attr-DNCPOST.
               c_segment1-DOB_FAM_2 = lt_mkt_attr-DOB_FAM_2.
               c_segment1-DOB_FAM_3 = lt_mkt_attr-DOB_FAM_3.
               c_segment1-DOB_FAM_4 = lt_mkt_attr-DOB_FAM_4.
               c_segment1-PLANG = lt_mkt_attr-PLANG.
    *           c_segment1-APPL_SNAME = lt_mkt_attr-APPL_SNAME.
                 idoc_data-segnam =  'ZE101CRMXIF_MKT_ATTR_DATA1'.
                idoc_data-sdata = c_segment4.
                 append idoc_data.
                c_segment2-DTPCARDGIVCOU = lt_mkt_attr-DTPCARDGIVCOU.
                c_segment2-DTPCARDOFF = lt_mkt_attr-DTPCARDOFF.
                c_segment2-DTPCARDOTHSTORE = lt_mkt_attr-DTPCARDOTHSTORE.
                c_segment2-DTPCARDRETCOU = lt_mkt_attr-DTPCARDRETCOU.
                c_segment2-DTPCARDSHREDDED = lt_mkt_attr-DTPCARDSHREDDED.
                c_segment2-DTWELCOMCALL = lt_mkt_attr-DTWELCOMCALL.
                c_segment2-DUDZ = lt_mkt_attr-DUDZ.
                c_segment2-EDUDR = lt_mkt_attr-EDUDR.
                c_segment2-DTPCARDSTORE = lt_mkt_attr-DTPCARDSTORE.
                c_segment2-EDUER = lt_mkt_attr-EDUER.
                c_segment2-EDUG = lt_mkt_attr-EDUG.
                c_segment2-EDUHS = lt_mkt_attr-EDUHS.
                c_segment2-EDULAW = lt_mkt_attr-EDULAW.
                c_segment2-FOURWHEELER = lt_mkt_attr-FOURWHEELER.
                c_segment2-FULL_NAME = lt_mkt_attr-FULL_NAME.
                c_segment2-FWLT15KCC = lt_mkt_attr-FWLT15KCC.
                c_segment2-FAMILY_MEMBER_NAME = lt_mkt_attr-FAMILY_MEMBER_NAME.
                c_segment2-FAMILYMEMBERS = lt_mkt_attr-FAMILYMEMBERS.
                c_segment2-FAMILY_MEMBER_NAME_2 = lt_mkt_attr-FAMILY_MEMBER_NAME_2.
                c_segment2-FAMILY_MEMBER_NAME_3 = lt_mkt_attr-FAMILY_MEMBER_NAME_3.
                c_segment2-FAMILY_MEMBER_NAME_4 = lt_mkt_attr-FAMILY_MEMBER_NAME_4.
                c_segment2-FAMILY_MEMBER_NAME_5 = lt_mkt_attr-FAMILY_MEMBER_NAME_5.
                c_segment2-FWLT1KCC = lt_mkt_attr-FWLT1KCC.
                c_segment2-FWLT2KCC = lt_mkt_attr-FWLT2KCC.
                c_segment2-GEO_WING_LAT = lt_mkt_attr-GEO_WING_LAT.
                c_segment2-GEO_WING_LONG = lt_mkt_attr-GEO_WING_LONG.
                c_segment2-HDFCBANK = lt_mkt_attr-HDFCBANK.
                c_segment2-HSBC = lt_mkt_attr-HSBC.
                c_segment2-ICICIBANK = lt_mkt_attr-ICICIBANK.
                c_segment2-INCMTO = lt_mkt_attr-INCMTO.
                c_segment2-INCT2F = lt_mkt_attr-INCT2F.
                c_segment2-INCT2T = lt_mkt_attr-INCT2T.
                c_segment2-IND_SECTOR = lt_mkt_attr-IND_SECTOR.
                c_segment2-INTERNETCHATTING = lt_mkt_attr-INTERNETCHATTING.
                c_segment2-LICENSE_INFO = lt_mkt_attr-LICENSE_INFO.
                c_segment2-INTERNET_CONNECT = lt_mkt_attr-INTERNET_CONNECT.
                c_segment2-MFAM_INCOME = lt_mkt_attr-MFAM_INCOME.
                c_segment2-MODEL_1 = lt_mkt_attr-MODEL_1.
                c_segment2-MODEL_2 = lt_mkt_attr-MODEL_2.
                c_segment2-MODEL_3 = lt_mkt_attr-MODEL_3.
                c_segment2-MOTHERS_NAME = lt_mkt_attr-MOTHERS_NAME.
                c_segment2-MO_OF_P = lt_mkt_attr-MO_OF_P.
                c_segment2-MO_OF_P2 = lt_mkt_attr-MO_OF_P2.
                c_segment2-MO_OF_P3 = lt_mkt_attr-MO_OF_P3.
                c_segment2-MY_OF_P3 = lt_mkt_attr-MY_OF_P3.
                c_segment2-NOMINEES_NAME = lt_mkt_attr-NOMINEES_NAME.
                c_segment2-NONE = lt_mkt_attr-NONE.
                c_segment2-OCCU_OD_OTHR = lt_mkt_attr-OCCU_OD_OTHR.
                c_segment2-OCC_FAM_1 = lt_mkt_attr-OCC_FAM_1.
                c_segment2-OCC_FAM_2 = lt_mkt_attr-OCC_FAM_2.
                c_segment2-OCC_FAM_3 = lt_mkt_attr-OCC_FAM_3.
                c_segment2-OCC_FAM_4 = lt_mkt_attr-OCC_FAM_4.
                c_segment2-OCC_FAM_5 = lt_mkt_attr-OCC_FAM_5.
                c_segment2-OCC_NOM = lt_mkt_attr-OCC_NOM.
               idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA2'.
               idoc_data-sdata = c_segment4.
               append idoc_data.
               C_segment3-PLANG_OTHR = lt_mkt_attr-PLANG_OTHR.
               C_segment3-REF_MAILADD = lt_mkt_attr-REF_MAILADD.
               C_segment3-RELATION_FAM_1 = lt_mkt_attr-RELATION_FAM_1.
               C_segment3-RELATION_FAM_2 = lt_mkt_attr-RELATION_FAM_2.
               C_segment3-RELATION_FAM_3 = lt_mkt_attr-RELATION_FAM_3.
               C_segment3-RELATION_FAM_4 = lt_mkt_attr-RELATION_FAM_4.
               C_segment3-RELATION_FAM_5 = lt_mkt_attr-RELATION_FAM_5.
               C_segment3-REL_ACTIVE_STAT = lt_mkt_attr-REL_ACTIVE_STAT.
               C_segment3-REL_KISAN_MITRA_STAT = lt_mkt_attr-REL_KISAN_MITRA_STAT.
               C_segment3-REL_NOM = lt_mkt_attr-REL_NOM.
               C_segment3-REL_PLASTIC_CARD_STAT = lt_mkt_attr-REL_PLASTIC_CARD_STAT.
               C_segment3-REL_STAFF_STAT = lt_mkt_attr-REL_STAFF_STAT.
               C_segment3-REMARKS = lt_mkt_attr-REMARKS.
               C_segment3-ROCN = lt_mkt_attr-ROCN.
               C_segment3-ROCN_FAM_1 = lt_mkt_attr-ROCN_FAM_1.
               C_segment3-ROCN_FAM_2 = lt_mkt_attr-ROCN_FAM_2.
               C_segment3-ROCN_FAM_3 = lt_mkt_attr-ROCN_FAM_3.
               C_segment3-ROCN_FAM_4 = lt_mkt_attr-ROCN_FAM_4.
               C_segment3-ROOMS_PER_FLAT = lt_mkt_attr-ROOMS_PER_FLAT.
               C_segment3-SCH_NUM = lt_mkt_attr-SCH_NUM .
               C_segment3-SECONDARYEMAIL = lt_mkt_attr-SECONDARYEMAIL.
               C_segment3-SERIAL_NUM = lt_mkt_attr-SERIAL_NUM.
               C_segment3-SOCIETY_MEMBER = lt_mkt_attr-SOCIETY_MEMBER.
               C_segment3-SOC_CONTNO_LL = lt_mkt_attr-SOC_CONTNO_LL.
               C_segment3-SOC_CONTNO_MOB = lt_mkt_attr-SOC_CONTNO_MOB.
               C_segment3-SOC_CONT_DESIG = lt_mkt_attr-SOC_CONT_DESIG.
               C_segment3-SOC_CONT_PER_NAM = lt_mkt_attr-SOC_CONT_PER_NAM.
               C_segment3-STANCHART = lt_mkt_attr-STANCHART.
               C_segment3-ST_CODE = lt_mkt_attr-ST_CODE.
               C_segment3-ST_CODE_OLD = lt_mkt_attr-ST_CODE_OLD.
               C_segment3-ST_EMP_CODE = lt_mkt_attr-ST_EMP_CODE.
               C_segment3-TEENAGERS = lt_mkt_attr-TEENAGERS.
               C_segment3-SBI = lt_mkt_attr-SBI.
               C_segment3-ZLAT1 = lt_mkt_attr-ZLAT1.
               C_segment3-ZLONG1 = lt_mkt_attr-ZLONG1.
               C_segment3-ZWING_GEOCODE = lt_mkt_attr-ZWING_GEOCODE.
               C_segment3-ZNAMEPLATE_PHOTO = lt_mkt_attr-ZNAMEPLATE_PHOTO.
               C_segment3-ZLATITUDE = lt_mkt_attr-ZLATITUDE.
               C_segment3-ZLONGITUDE = lt_mkt_attr-ZLONGITUDE.
               C_segment3-ZLATITUDE_N_LONGITUDE = lt_mkt_attr-ZLATITUDE_N_LONGITUDE.
               C_segment3-ZWING_PHOTO = lt_mkt_attr-ZWING_PHOTO.
               C_segment3-ZCATEGORY_SHOPS = lt_mkt_attr-ZCATEGORY_SHOPS.
               C_segment3-ZNUM_OF_SHOPS = lt_mkt_attr-ZNUM_OF_SHOPS.
               C_segment3-ZELECT_SURVILL = lt_mkt_attr-ZELECT_SURVILL.
               C_segment3-ZBUILDING_TYPE = lt_mkt_attr-ZBUILDING_TYPE.
               C_segment3-ZFLATS_PER_FLOOR = lt_mkt_attr-ZFLATS_PER_FLOOR.
               C_segment3-ZBULDNG_FLOOR = lt_mkt_attr-ZBULDNG_FLOOR.
               C_segment3-ZSWIMMING_POOL = lt_mkt_attr-ZSWIMMING_POOL.
               C_segment3-ZGYM = lt_mkt_attr-ZGYM.
               idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA3'.
               idoc_data-sdata = c_segment4.
               append idoc_data.
              c_segment4-others = lt_mkt_attr-others.
              c_segment4-OCCU_OD = lt_mkt_attr-OCCU_OD.
              c_segment4-ZFLAT_TYPE = lt_mkt_attr-ZFLAT_TYPE.
              idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA4'.
               idoc_data-sdata = c_segment4.
               append idoc_data.
            ENDLOOP.
            IDOC_CONTROL-MESTYP = c_messagetype.
            IDOC_CONTROL-DOCTYP = c_idoc_type.
              CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
                EXPORTING
                  MASTER_IDOC_CONTROL                  = IDOC_CONTROL
    *             OBJ_TYPE                             = ''
    *             CHNUM                                = ''
                TABLES
                  COMMUNICATION_IDOC_CONTROL           = t_comm_control
                  MASTER_IDOC_DATA                     = IDOC_DATA
    *           EXCEPTIONS
    *             ERROR_IN_IDOC_CONTROL                = 1
    *             ERROR_WRITING_IDOC_STATUS            = 2
    *             ERROR_IN_IDOC_DATA                   = 3
    *             SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
    *             OTHERS                               = 5
              IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ENDIF.
    ENDFUNCTION.
    i implement a badi "CRMXIF_PARTNER_MAP"
    data ls_mkt_attr type zcrmxif_mkt_str.
      LOOP AT cs_data_mapped INTO  ls_data_mapped .
        lv_tabix = sy-tabix.
        loop at ls_data_mapped-ZZPARTNER-ZZMKT_ATTR into ls_mkt_attr.
          read table ls_data_mapped-zzpartner-ZZMKT_ATTR into ls_mkt_attr index 1.
           if ls_mkt_attr is not initial.
                   CALL FUNCTION 'ZCRMXIF_MKT_DATA'
                     EXPORTING
                       EV_MKT_ATTR       = ls_mkt_attr
                   endif.
         endloop.
         read table ls_data_mapped-zzpartner-ZZMKT_ATTR into ls_mkt_attr index 1.
             MODIFY  cs_data_mapped FROM ls_data_mapped INDEX lv_tabix.
      endloop.
    i ddn't get data into sructure.
    please explain how to doit.

  • Issue in BP creation in CRM 7 connected using XIF from CRM 4

    Hi All,
    We have connected CRM 7 and CRM 4 using XIF
    We are facing an issue where 2 IDOCs (with same Basic type CRMXIF_PARTNER_SAVE_M01) are generated at same time while using XIF adapter dring busines partner creation. First IDOC is succesful and other fails with error message " Business patner locked by you".
    Can you please share some expertise on this.
    Thanks & regards,
    Mohit SIngh

    Hi Bala,
    Which version of CRM are you using? There are some notes for CUST_HIERARCHY BDoc errors. Please have a look at them in the Support Portal.
    CRM_BUPA_MAIN_VAL is used for validation of rules set in CRM Server and maybe you dont have the same mandatory rules in MSA.
    Best Regards,
    Ankan

  • Delete non-picked items in delivery using iDoc

    Hello gurus,
    I'm integrating SAP ECC and external WM solutions using iDocs. The outbound delivery is created in SAP ECC and sent to WMS using DESADV iDoc. The picking is performed in WMS and the list of shipped items with batch numbers are returned to SAP and Goods Issue is posted. iDoc WHSCON is supposed to be used for that purpose.
    The problem is that in case if not all the line items were shipped it's necessary to delete them from the delivery because otherwise GI will not be posted. But the non-picked items no longer exist in the response iDoc WHSCON so it's even impossible to set QUALF=DEL for these items. WMS sends back only actually shipped items in iDoc, and not the deleted ones.
    Do you have any solutions for overcoming this problem?
    Maybe there is any BAPI or iDoc qualifier that will allow to delete all items from the delivery so that they will be recreated by the same iDoc? Or there is any checkbox in SAP that will automatically delete unpicked items during posting of GI?
    Thanks!

    hi
    in this both error comes ,
    1)E VL 609 20 Delivery has not yet been put away / picked (completely)
    a) picking quantity not entered , in delivery , first you enter the picking quantity ,
    you create the 2 lines for sale order , so create for one line item for delery , go to vlo1n enter shipping point , sale order number line item number  1 to 1 enter press enter system will take only one item in delivery then you enter the picking quantity , and pgi ,
    in delivery two line item only line item enter picking quantity and another line item not enter the picking quantity , it not possible to pgi , both line item you enter the picking quantity ,
    you create the same delivery number for 2line item , so first complete the 1st line item pgi and , go to vl02n and enter , click on menu bar out bound deliverrs-delivery sale order -enter sale order number and line item , and do the pgi ,
    2)VL 608 20 Delivery has not yet been completely processed by WM
    you process activate the wm , so you can do the lt03 , then it will come vlo2n and check the picking quantity it will come auto matically

  • How can we post data from CRM to SAP using ABAP proxies???

    Hi ,
      Can anyone hep me to create interface for the following scenario How can we post data from CRM to SAP using ABAP proxies???, can I find any document ???????
    Thanks in advance
    Andy

    Andy,
    Please look at these weblogs.
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    /people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    These should give a good idea about implementing Proxies.
    Regards,
    Ravi

  • How to resolve error while importing data using IDoc method in LSMW ?

    Hi
    I am trying to import my data using IDoc method in LSMW.
    But after completing the whole LSMW process, when I look into the IDOC generated, the error description is as this.
    It talks about the process code and other stuff.
    Function module not allowed : APPL_IDOC_INPUTI
    Message No. B1252
    Diagnosis :
    The function module APPL_IDOC_INPUTI and the application object type which were determined are not valid for this IDoc.
    I am not able to resolve the problem.
    Please help.
    Regards,
    Rachesh Nambiar

    check the below link.
    /people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter

  • Wheh to use abap proxy and when to use idoc

    Hi All,
    Please provide some clarifications for the below points :
    What is Sproxy?
    2.     Why we are using Sproxy instead of Idocs
    3.   When we are going Proxy ?
    4.   What are the types of proxy ?
    5.   How to Create to Proxy ?
    6.   What the Difference between SProxy  and Idocs
       7.   What is SOAP file? When we are using SOAP file ?
    Thank you.
    Regards,
    Bharat

    Hi Bharat,
    You seem to have a range of Questions. I will try and answer as many as possible.
    What is Sproxy?
    SPROXY is a transaction [T-Code] on the SAP ECC/CRM etc side where you can see the objects designed in SAP PI ESR and develop its corresponding ABAP code. SPROXY T-Code displays the Service Interface. You can read more about it in the following site:
    **************** - XI - ABAP Proxy communication
      2.     Why we are using Sproxy instead of Idocs
    For Certain implementations Standard IDocs may not be available and it is quite tedious to create a Z- IDoC and therefore it is advantageous to use Proxy. You can read more about this doubt in the following links:
    Choosing to use IDOC standard or ABAP Proxy?
    IDOC vs Proxy
    ABAP Proxy Vs IDOC
    3. When we are going Proxy ?
    When there are no Standard IDocs available. Please refer above links to get an answer for this.
    4.   What are the types of proxy ?
    5.   How to Create to Proxy ?
    Again the following link has the answers for both these questions:
    **************** - XI - ABAP Proxy communication
    6.   What the Difference between SProxy  and Idocs
    Difference is in the way the communication happens. Standard Idocs are already provided and you can use them directly while Proxy you will require to write the code on ECC side. You can refer the following link to understand more:
    Advantage of ABAP proxy over BAPI
    7. What is SOAP file? When we are using SOAP file ?
    I have not heard of anything called SOAP file. SOAP is a protocol used for communication and you can send files as attachment in your SOAP to Any(file/idoc/Soap etc) or vice Versa Interfaces. Infact Proxy itself is SOAP based communication with XI 3.0 Protocol.
    Please explore SCN to know more about the various scenarios. There are endless possibilities in SAP PI.
    Hope this Helps.
    Thanks &  Regards,
    Tejas Bisen

  • CRM-GATP Integration

    Hello Gurus,
    I'm configuring CRM-GATP integration in our server. I'm facing few challenges while doing so.
    CRM team has configured customized transaction types & Item categories in CRM. These ord types & item categories do not exist in ECC system. Also the sales org being used does not exist in ECC side. Still as a part of urgent requirement, I need to configure CRM-GATP scenario for existing ord type in CRM.
    I am done with basic settings in CRM like - ATP profile, RFC connections, Transaction type-item category determination, user ATP parameters etc.
    When creating order, ATP check is triggered, but I'm receing an error in order: "Message no. CRM_APO 203"
    Availability check/information: ATP error log (display via long text)
    Message no. CRM_APO 203
    Diagnosis
    Errors occurred during availability check or availability information in the ATP System.
    If you use an SAP APO System or an SAP R/3 System for availability check/information, the relevant system issues an error log to CRM Online. The messages of the error log are listed below with the message ID (message class) and message number. If more detailed help is available in the form of long texts, these long texts are listed right under the short texts.
    System Response
    The ATP System cannot report any results of the availability check/information until the errors have been fixed there.
    Procedure
    You can obtain the meaning of the messages from the ATP System. If you cannot fix the errors yourself, contact the responsible administrator of the ATP System.
    Procedure for System Administration
    Follow the recommendations of the ATP System.
    Error Log ATP System: SC1CLNT001
    Msg ID /SAPAPO/ATP Msg. no 059 With follow. descript:
    No business system could be determined for logical system CR1CLNT200
    CRM team is using the Z ord type (not in ECC) for the service part availability check in GATP. From GATP point, I have done basic settings of RBA, requirements profile etc.
    Could you please help me out sorting the problem and the solution? Is it really not possible to call GATP from a stand alone CRM system?
    Thansk,
    AP.

    Michael,
    Kudos.....you are master... It solved my issue !!! Now I can ATP my product from CRM system.
    Now need just a small help, I'm configuring service order scenario in CRM where I'm entering a service name (defined as a product in CRM, not in ECC/APO) and under spare parts, I need to enter my ATP relevent product. ATP will happen to the spare part item and relevent location to be appeared in order.
    Till now I was only entering the spare part product in CRM just to ensure trigger to GATP and by working on above mentioned issues, GATP was triggered.
    But now I'm entering service product & spare part at the same time in CRM, and ATP check is not happening, throwing some error asking for correlation profile maintainance. Please see the screenshot attached. (line item 10 is service material & 20 is Spare)
    Can you please guide on how to go ahead?
    Many Thanks,
    AP.

  • Issues in retrieving the Planning profiles in CRM from BW while doing CRM-BI Integration

    Dear Folks,
    We are in the process of doing the SAP CRM & BI Integration wrt Trade Promotion Mangement.
    For testing purposes, we tried to create a planning profile in BPS end i.e BW SEM system & trying to retrieve it from the CRM system using the below navigation.
    SPRO-->CRM--> Define Transaction types--> ZBPD is the transaction type we had created.
    And in Customizing Header level, in SEM Planning tab, trying to retrieve the Planning profile created in SAP SEM-BW.
    Tried to search in both ways i.e prefixing the 'zprofile' with /prf/zprofile but still CRM system is not reading the same from BW system.
    What ever the pre-requisites that are needed to be followed before doing all these, the same had been done in terms of creating the RFC Connections etc but still unable to retrieve the same.
    And also not finding any standard content in the form of Planning areas & profiles at BW end after installing the SEM BW component add on in BW system.
    Could you pls let us know what we are missing here.
    Thanks in advance.

    I meet the same problem, any solution?

  • R/3 - SNC 7.0 - oracle integration using PI 7.0

    Hi All
    There are three systems in our landscape R/3, SCM (SNC 7.0) and oracle based third party system and we are integrating these with PI 7.0.
    for R/3 to SNC we are going to use standard mappings and for communication between R/3 - Oracle and SNC - Oracle we are going to use JMS.
    Communication with third party system is through Flat File (inbound & outbound).
    I have never worked on JMS, could you please give me guidelines what all adapters and methodologies I should use for  communication between R/3 - Oracle and SNC - Oracle.
    Thanks for your valuable inputs.
    Regards
    Amol.

    Dear Amol,
    R3-SNC -> for this there are std mappings available on SDN
    SNC->Oracle - > you will have to use ABAP proxy to file if you are sending files to 3rdparty
                              or u can use ABAP proxy to JDBC adapter if you are directly updation oracle tables...                           
    R3->Oracle - > you can use IDOC to file(if file is used as communication)
                                        or  IDOC to JDBC adapter(if you want to update tables directly)
                                         or ABAP proxy(if std idocs are not available) -> file
                                         or ABAP proxy -. JDBC
    Hope this helps

  • Hi Using IDOCs with LSM Workbench????

    Hello,
    I wanted to use IDOCs as one of the methods with the LSM Workbench. I am going to load the data from flat file to a transaction in CRM.  I am just curious to know that how do I go forward with it.  The first step of LSM Workbench is asking Message Type, Basic Type, Enhancement and structure assignment for EDIDC40.  I have used other methods such as Direct input and Batch input.  I have not used IDOCs with LSMW.  Is it possible that you can give me the steps what we have to follow in order to set up the IDOCs and then use it with LSMW.
    I will really appreciate if you can give me the steps or give a link which shows steps of LSMW with IDOCs..
    Thanks much.
    Warren

    hi warren,
       first u have to configure the partner profile in lsmw
    lsmw->settings->idoc inbound processing.
    then u have to choose the basic type message type all those stuffs.if u have any enhacement u can use it or else leave it blank.
    lsmw->settings->idoc inbound processing.
    partner profile..
    File port              IDOC_TEST 
    tRFC port                        
    Partn.type             KU        
    Partn.number           106                                                                               
    Message type         ORDERS        Purchase order / or
      Basic type           ORDERS05      Purchasing/Sales  
      enhancement blank                                                 
        tick it. Enable structure relation for EDIDC40 
    steps are:
    Maintain object attributes                     
    Maintain source structures                     
    Maintain source fields                         
    Maintain structure relations                   
    Maintain field mapping and conversion rules    
    Maintain fixed values, translations, user-define
    Specify files                                  
    Assign files                                   
    Read data                                      
    Display read data                              
    Convert data                                   
    Display converted data                         
    Start IDoc creation                            
    Start IDoc processing                          
    Create IDoc overview                           
    Start IDoc post-processing                     
    please don't forget to reward points....
    regards,
    murali.

  • Business Partner distribution from  CRM-PI-MDM using XIF and PI Proxy

    Hi,
    I would like to know if there is any step-by-step documentation on configuration of ABAP proxy with XIF in SAP CRM for distribution of Business partner information to MDM system. There is XI Content for this but there is no documentation which highlights configuration of proxy.
    I did looked at following links but was looking for any other document with details.
    http://help.sap.com/saphelp_crm50/helpdata/en/42/b6efbe82103120e10000000a1553f7/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f
    (Talks about using IDoc)
    Thanks,
    Divyakumar Jain

    HI,
    Have checked the blog
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Here you will get the steps to generate the client proxy in R/3.
    Or You can configure the proxy settings as per below blog
    You need to Setup the HTTP connection for ABAP Proxy,
    http://help.sap.com/saphelp_nw70/helpdata/en/da/11df3a9b10355ae10000000a11405a/frameset.htm
    Thanks
    Swarup

  • Problem in CRM - CO Integration...

    Hi Experts,
    Currently in ECC we did not activated Operating Concern. Our Organization don't required that. But when we are doing CO integration with CRM It is asking to assign controlling area to Operation Concern(COPA). Even though Operating concern component is not activated in ECC.
    For time being i assigned the Sample Operating concern to Controlling area i.e. S001. So far i did not get any error in development. even though the curreny of this Op.Concern is EUR. Actually my Company code currency and Controlling area currenty is OMR (Omani Rial).
    My question is if i tranport this to Quality & Production. Will i get any error. (My organization doesn't want any Profitability analasys Because we are using BW.)
    Advice me how to go about this. Any settings are there in CRM-ECC integration to avoid assignment of Op.Concern.  OR can i use Sample Op.Concern.
    Tks in advance,
    Abhinesh

    Completed

Maybe you are looking for