Moving shipment data using IDOC SHPMNT05

Hi guys,
I want to configure ALE process across two SAP systems and moved shipment data using IDOC SHPMNT05.
May I know how to do that.
Plz help me...................
Thankz in advance,
Swetha.

Hi Shwetha,
Please check the following links to start with.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217da751ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Thanks,
Naren

Similar Messages

  • 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

  • Customer creation in R/3 from PI data using IDOCs

    Hi All,
    I am creating customers in SAP r/3 system using IDOCs which are coming from PI system in the form of XML files.
    For that DEBMAS and ADRMAS message types and DEBM process code is used for creating or changing customer master data.
    Existing functionality : 1 IDOC is creating/changing 1 customer master data using standard function module IDOC_INPUT_DEBITOR.
    Required Functionality: need to create/change data for multiple customers using only one IDOC file.
    I have tried using DEBMDM. Unlike DEBMAS, message type DEBMDM can hold  multiple customers but if any DEBMDM IDOC sent to R/3, it was remaining in status 75 with message 'IDOC Received via qRFC'.
    Any help will be appreciated.
    Thanks & Regards,
    Anshoo

    Hi,
    Status 75 refers to that "IDoc is in inbound queue".
    Transaction SMQ2 (qRFC Monitor - Inbound Queue)
    Transaction WEINBQUEUE (IDoc Inbound Queue).
    The transactional asynchronous tRFC guarantees that all database operations are fully executed or, if one of the function modules responds with a termination, they are fully rejected (rollback). If an LUW is executed without errors, it cannot be executed again. In some cases it may be necessary, to rollback an LUW in an application program, for example, because a table is locked.
    Regards,
    Srilatha.

  • Need to transfer Custom infotype data using IDOCs

    Hi,
    My requirement is to transfer custom OM infotype changes using IDOCs.
    But its not creating any change pointers for that infotype.
    The message used is a copy of standard message OM_HRMD_A.
    Can any one please help me out in this issue.
    Thanks,
    Sarika

    You'll need to erase the drive by booting up holding command-option-r keys into your Recovery Volume.
    Use Disk Utility to erase the disk and then Internet Recovery. That will take a while.
    http://support.apple.com/kb/HT4718

  • How to upload data using idoc in lsmw

    plz let me know how to upload material using idoc using lsmw. urgent

    Hi Vrishali,
    refer to the link below:
    http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
    Hope this helps.
    Reward if helpful.
    Regards,
    Sipra

  • Create shipment from inbound IDOC SHPMNT05 ?

    Hello All,
    I would like to create an individual shipment when i receive from a partner an inbound IDOC.
    I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
    How can I start the creation of the shipment with this inbound IDOC ?
    Is it possible ? or is it necessary  to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)? 
    Thanks a lot,
    My

    Hello Reddy
    thanks for your answer.
    is there particular customizing to be done ?
    i exactly use function BORES_IDOC_INPUT_SHPMNT
    The inbound idoc is generated but i have the following status message 51 "Application document not posted"
    What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
    Thanks a lot
    MY

  • How to use segment ZCRMXIF_PARTNER_SAVE01 in LSMW to Generate/Change BP data using IDOC

    Hi Gurus,
    I have an requirement to add contact person first name and last name using Relationship kind as '0001' for an BP.
    This requirement i need to work with LSMW and generate IDOC for respective changes.
    To work with LSMW and IDOC i need to pass data to ZCRMXIF_PARTNER_SAVE01.
    Can you all suggest me what are the mandatory fields to be passed to this segment and what are the fields to which i can pass FIRST NAME and LAST NAME of the CONTACT PERSON of the BP.
    Please post me your replies in detail iam new to crm i can understand.
    Thanks & Regards,
    Saravanan Sambandam

    Hi Saravanan,
    Which method you used.
    Regards,
    Madhu.

  • Can we use idoc technique to change or delete the vendor master data?

    Hi,gurus,
    Can we use idoc technique to change or delete the vendor master data?You know we can create vendor data using idoc CREMAS03 as the receiver adapter,but when change or delete the specified vendor data,must we use RFC adapter technique?
    Another question:I found the bapi which creates a vendor master data doesn't have the parameter account group,then we turned to idoc technique.But which adapter should I use when change or delete the vendor data?
    Thanks in advance.

    Hi,
    >>>I found the field of the segment of deletion flag at different level,and very appreaciate your help.
    yes - LOEVM  - but remember this will not delete the record but only mark it for deletion
    >>>It's a long time to wait for your new blog,what new and interesting things do you find?
    at least 4 new in my head - 2 simple but important and 2 new + I'd also like to write something for XI guys about
    BO data integrator which can also work as EAI tool (BTW I know it's ETL) but how knows when they will appear
    Regards,
    Michal Krawczyk

  • IDOC_INPUT_SHIPPL - Shipment creation/Mod using Idoc

    We have set up an external Transportation Planning System. And are trying to create Shipments in SAP using IDOCs from external system.
    The External system has been configured. We are now getting an error saying Shipment XYZ has not been saved (V6 513). It does not give any other message other than this.
    If we send some error value then the corresponding SAP application error message is shown, along with the above message.
    This has eaten my brain for a week. Anyone solved this?

    Hi Cyril,
    Can you successfully post the IDoc using exactly the same data (for all the segments/fields) that is received from the external system in SAP via transaction WE19? Use the data in one of the failed IDocs to post this in test mode. What message do you get?
    Also, I suppose the data is converted to IDoc format from the external system by a middleware? Is this middleware working correctly? To confirm, change SAP settings as not to post the IDoc immediately when received so that you can post it manually using BD87. Before you push it thru BD87, put a break point in the FM IDOC_INPUT_SHIPPL at the very beginning and check the IDoc segments/fields to confirm data is received correctly as SAP expects it. If data OK then put another "break point at message" statement to check what's going wrong.
    Hope this helps.
    Cheers,
    Sougata.
    okay, debug the FM then as I suggested above up to the error message.
    Don't forget to reward points.
    Message was edited by:
            Sougata Chatterjee

  • Data transfer b/w SAP to Java using IDOC and Interface SAP Jco

    Dear Experts,
    The challenging requirement we are having is, we need to create the interface for data transfer between SAP system and the Java system. The data will be transferred from SAP to java and similarly once some processing done in Java again the details needs to be transferred from Java to SAP.
    For this data transferred we are planning to use IDOC process and for interface "SAP Java connector (Version 3.0.5)" we are planning to use. As per our understanding, from Java side one program needs to be written to connect with SAP as "Registered program". This registered program will appear in SAP GATEWAY automatically and using tRFC, TCP/IP connection both SAP and Java system will be connected.
    In this case we are having some doubts.
    1. The data from SAP is going to be transfered from one Custom transaction (Z tcode). Once "Outbound IDOC" will get triggered and will carry the details. Now the doubt is, whether the data / details will get transfered to JAVA system automatically or we need to perform any other steps from SAP ABAP coding...(like converting in to flat file, XML file and etc) ??
    2. We are planning to install "SAP Jco" in Java server. Is this correct...??
    3. Other than SAP Jco any other softwares needs to be installed or not..??
    4. Since we are going to trigger the "outbound IDOC" from custom transaction, we are planning to develope one program in SE37. Other than this any other program we need to develop or not..??
    5. Any sample Java program for the SAP Jco version 3.0.5 to create the "Registered program" with SAP..? (e.g. SAP Listener program).?
    If anybody has detailed steps or explanation please share it with us.
    Thanks in advance
    Warm Regards,
    VEL

    Hi All,
      For the above mentioned issue, we implemented JCo software in JAVA system and created the JAVA program including SAP logon credential details like Client, User name, password and Language details.
    When this JAVA program was compiled successfully then, that non SAP system will appear in SAP gateway Tcode.
    Once non SAP system started appearing in SAP gateway that means, both SAP & Non SAP are connected automatically.
    Regards,
    Velmurugan P

  • 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.

  • Error while uploading the data Using LSMW - Idoc method

    Hi Experts,
       I am working on LSMW using Idoc method. Till 12th step (Display converted data) i wasn't got any problem. For the Idoc method, I have to specify details to Idoc inbound processing from the menu settings.
    In that screen I have to specify file port, partner type and partner no. I have created a file port ZFILE. Can u tell me what ahould I pass in that screen? Where should be the file i.e in the application server or presentation server? What should be the directory and function  module. Can u provide step by step?
    After that I have to specify partn.type. What should I select for that?
    After that I have to specify partner no. Whether it is inbound or outbound?
    I got No data found for the following detials.
    port - ZFILE
    in the inbound file tab, e:\ as physical directory; EDI_PATH_CREATE_USERNAME as function module.
    Partner type - US
    Parnter no.  - LSMW with the inbound parameters message type - MATMAS and Process code - MATM.
    Please tell me how can I upload properly? Please don't ignore as i am asking same question again becasue I have gone through related threads also. But i didn't find the exact requirement.
    proper documentation will be rewarded.
    Thanks in Advance.
    James.

    Hello,
    I could identify the error. It was due to incorrect UOM. Problem resolved.
    Thanks,
    Madhura

  • Update the "remark" field in general data of a BP (using IDOC in LSMW)

    Hi,
    I have to create and udpate BP with comments in the general data. I have no problem to manage this field in creation mode. I only use the segment "E101BAPIAD_REM" from the "CRMXIF_PARTNER_SAVE_M02" Idoc basic type. I fill the following fields: "LANGU, LANGU_ISO, ADR_NOTES".
    However in update mode I don't success to update the value for the field "REMARK". I use the second segment "E101BAPIAD_REX" and i fill only field "ADR_NOTES" with value "X" and "UPDATEFLAG" with value "U".
    I tried several value and several cases but i failed each time. If anybody has already managed this data with IDOC I would be very interesting...
    regards,
    Fabrice Mouyebe.

    Hi Thirumala,
    thank you for your answer but you speak about the field "AddressGUID" of E101BUS_EI_ADDRESSREMARK but I haven't this field at this level. This field is linked to the segment "E101BUS_EI_BUPA_ADDRESS_KEY", isnt'it ?
    Effectively i have certainly a problem with the Address GUID. I have to test it because it doesn't work with only UPDATEFLAG at 'X' and CURRENT_TASK too.
    Thanks,
    fabrice.

  • How to upload the data from XML file to SAP database using IDOC

    Hi,
    I need some steps  to upload  data from XML format file from other directory to SAP database using IDOC.
    how to approch this please if any one knows give me ans
    it will be a great help ful to me
    Thanks in Advance
    Mallik

    Thank you vijay,
    But i heard that by using this Fun modules, when we are passing IDOC in back ground schedule,  so some other depended FM not supporting, so how to approach this and how to avoid this problem. 
    Have you worked on this before if any one worked on this please help me out
    And thank you once again for your valuable information
    Best Regards
    Mallik

  • How to upload different views of customer master data using LSMW-IDOC

    I need to upload customer master data  using LSMW Idoc method for my client. Now customer will have different views like main view, Sales data, Company code data, Partner function data etc. And except main data all other data can be multiple for each customer. We are going to upload data from tab delimited .TXT file. Should I propose different LSMW for upload different views for the customer from different .TXT files? or we can upload all the customer related data (like main view data and partner function data )from a single .TXT file. Kindly suggest which one in convenient and how we can prepare the data file in both cases.

    convinient is the method that you can handle.
    but as the guy who loads the data you have to load the data like they are available, like it is convinient for others to prepare the data.
    In general there is no problem to use an IDOC method to load a customer master with multiple comany codes and several sales orgs in one shot.
    the data can be in one source file, but need then to be maintained in a certain way
    Example1: all data in 1 structure
    GD1 - CC1 - SO1
    GD1 - CC2 - SO2
    GD1 - CC2 - SO3
    in this case the GD (general data) is redundand in each line which has different Company code data or different Sales Org data
    Example2: all data in 3 sturcures but one file
    GD1
    .CC1
    .CC2
    ..SO1
    ..SO2
    ..SO3
    Example3: data delivered in 3 files - you join the files in LSMW, they must have a common identifier like the old customer number in the beginning of each file
    FILE General data:
    GD1
    GD2
    GD3
    file Compamy code data:
    CC1
    CC2
    CC3
    file Sales org data:
    SO1
    SO2
    SO3
    LSMW is flexible and can handle each of this scenarios, are you flexible too?

Maybe you are looking for

  • Report in the following form

    Hi All, I have to create a report which is like it will prompt me for which account I want to see the hierarchical structure of its decendant. For doing so I have kept account in the row dimension,and in the member selection pane of account I have ta

  • XML Elements Ordering according to XSD

    I have a XML document having XML Tags out of order but have parent child relationship intact. I have a XSD to follow. How do i convert this XML document instance into the properly ordered (Elements) XML document instance progrmatically. Need some poi

  • How can I download an earlier version of Firefox?

    I am using an iMac computer. Some banking institutions will not recognize Firefox 5.0 and instead need to see Firefox 4.0. How can I download Version 4?

  • Question about malformed path

    Hi, I may have overlooked something very simple, but in the log files I get an error: For host x.x.x.x trying to GET /, uri-clean reports: CORE4393 malformed path /sun/webserver7/https-bravo/docs/http://bravo.simplymine.com. What does this error indi

  • Table T001I and its use?

    Hi all, I know that with the table T001I it is possible to define some additional fields that are supposed to hold some country specific data that is needed for reporting and similar stuff. But when I add some definition there, where do I see it, thi