Seraching IDOC to transfer longtexts from subsystem

Hi,
I am searching for a standard IDoc,
to transfer long text informations from a subsystem to SAP.
If anybody has a hint about universal idocs to transfer longtext to SAP
please send me a short information.
THX in advance
Benjamin

Re: Urgent information required regarding message type and process code
Information regarding IDoc Parking

Similar Messages

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

  • How to transfer data from ECC to CRM via IDocs (Clfmas01),

    Hi all,
    how to transfer data from ECC to CRM via IDocs (Clfmas01), that to material master data from ECC to Production master data in CRM.    
    Need Information regarding, how to upload file to CRM from ECC, through, IDocs......Plz help me...
    Edited by: khaja fareed on Jan 11, 2010 12:44 PM

    First of all push ECC data in to GTS server through T.code:/N/SAPSLL/MENU_LEGALR3. First click on Master data tab there enter customer/vendor number then execute.
    2-Go to document tab there enter Sales order no/PO number then execute it.
    Then go to GTS server in compliance management module you can get all the information.
    Regards
    Sitanshu Panigrahi

  • How to transfer data from legacy system  to SAP

    Hi Friends,
    I would like to know the process and the steps followed to transfer data from my legacy system to SAP.
    Suppose if i have all the data in the form of Excel sheet or doc type. How can i transfer this data into SAP.
    Please explain the steps followed.
    Appreciate your help
    Anil

    Hi ,
    Conversion of legacy data into SAP can be uploaded using a standard SAP Tool called LSMW ( TCode:LSMW).
    the below link gives a brief explanation of the LSMW tool
    http://tutorialsap.com/abap/sap-lsmw-tutorial-with-steps-to-create.html
    There are various methods to upload data within LSMW. If the number of records are very high like Article Master or  Conditions for Retail the IDOC method must be used.
    Standard IDocs
    1. Article Master - ARTMAS
    2. Conditions - COND_A
    3. Source list - SRCLST
    4. Customer Master or WRF3/WRF6 tables - DEBMAS
    5. Vendor master- CREMAS
    Etc. Use transaction code WE60 to see the structure of each of the idocs. New enhancements can be done for the idocs if the required field is not available.
    Regards
    Prabhu

  • IDOC Data transfer

    Hi Experts,
                      I have few questions related to IDOC Data transfer. I have two different SAP Systems S1 and S2,  S1 Creates sales order and send the data through  IDOC Type ORDERS05 to S2,  To create sales order in S1.
    As i know, Program IDOC_INPUT_ORDERS is used for I/B IDocs in S2. Will be there be any programs to push the data from S1 System.
    Thank you
    Kris

    hi,
    idoc is not meant for sending files to another system, they are basically data containers which are sent to other systems like to send the data related to sales orders you can send idoc ORDERS.
    you need to first be clear with the requirement for which business object you want to transfer the data, then need to look out if the Idoc is available for the same then only u can sent it.
    for more info on idocs you can easily search on forums.
    Reg,
    NJ

  • How does IDOC data transfer happensbetween two system?

    Hi,
    If there are data in system A and I need to transfer to system B using IDoc.
    What are the key things which will enable data transfer from system A to system.
    It would be great if someone can explain how does IDOC data gets transferred from system A to sytemB.
    Regards,
    Rachel
    Moderator Message : Search for available information or Read SAP documentation. Thread locked
    Edited by: Vinod Kumar on Apr 26, 2011 12:37 PM

    thanks for all your replies...
    let me write down what i have understood ..plz correct me if i have not followed properly..
    1) Once IDocs successfully reach R3 , a function module specific to the Idoc type is called "<b>automatically</b>" and updates database...
    2) this function module we specify in the process code while creating partner profiles
    basically all we need to do is to specify correct function module, right?
    the rest of the process ie . updation in the tables(database) is done automatically..
    Once database is updated, where can i see the added/updated records in database?
    also how do we find this function module?
    I am using MATMAS05...
    Regards,
    Roshani

  • Transfer postings from other application components to accounting

    Hi expert, we have to transfer posting from other application components(SD,MM) (system A) to accounting (system B, FI/CO module only).
    Is there any related documents of this aspect? 
    Best wishes,
    Evan

    Hi!
    It will be not so easy. You have to set up an interface between the 2 systems.
    If you are using IDoc based interface, you can send IDocs from SD, when an invoice is enable to accounting.
    You might check out user exits (programs) RV60AFZA, RV60AFZB for this.
    Sorry, but this task will be not ready in 10 minutes...
    Regards
    Tamá

  • IDOCs creation - Transfer Orders(TOs)  for Deliveries - Basic doubts, thanq

    Hi Experts,
    Am new to IDOCs.  I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
    My doubts:
    1- I hv been asked to create IDOC, Wht does it mean?
    2 - How the created IDOC will be get posted?
    My requirement is:
    Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product.  The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
    I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D.  Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc.  Create a new TO confirm idoc per delivery idoc being processed.  Create a line item on this idoc for every line on the delivery idoc.  Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc.  There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP).  There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
    The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality.  Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process.  The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
    Source = DELVRY03     Destination = WMTCID01
    Record Name-Field Name-Record Name-Field Name-Description---Comments
    E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
    E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
    E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look  w/ idoc delivery line nbr
    EVERY THING IS DATA TRIGGERED!!!
    thanq
    Edited by: Srinivas on Jun 27, 2008 4:41 PM

    IDOC Programming
    There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
    NEED FOR ABAP PROGRAMMING arises if
    1)New IDOC was created
    Depending upon the triggering mechanism i.e change pointer,message control
    etc the programming technique changes and the type of process.
    2)Existing IDOC was extended
    User Exits are used to populate data in new segments added and to read them
    back.
    3)To enhance an exsiting process.
    User Exits are used .
    Basic structure of an OUTBOUND PROGRAM
    The basic structure of all outbound programs is same. The CONTROL
    record which is of TYPE EDIDC has to be filled. It contains important fields like
    IDOCTP IDOC type
    MESTYP Message Type
    RCVPRN Recieving Partner (Destination)
    RCVPRT Partner Type (it is LS i.e Logical System)
    The DATA RECORD internal table which is of TYPE EDIDD has to be filled
    in the same order as there are segments in the IDOC definition.
    It has 2 important fields which are to be filled ,these are
    SEGNAM Name of the segment
    SEGDATA Data in the segment and can be upto 1000 bytes.This field
    is corresponds to each data segment in the IDOC.
    e.g.
    DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    DATA W_SEGDATA LIKE zsegment "custom segment zsegment
    INT_EDIDD-SEGNAM = 'ZSEGMENT'
    W_SEGDATA-field1 = value "taken from some table
    W_SEGDATA-field2 = value "taken from some table
    INT_EDIDD-SEGDATA = W_SEGDATA
    APPEND INT_EDIDD
    This will fill the data record corresponding to the segment ZSEGMENT . For all
    segments the sam steps will be repeated until all the data corresponding to all the
    segments in the idoc is filled in the internal table of type EDIDD.
    There is only one control record and can be multile data records in the idoc
    structure.
    Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
    In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
    OUTBOUND PROCESS AND OUTBOUND PROGRAM.
    Outbound programs are used in outbound process to genearte IDOCs . There
    purpose is to extract the data from the tables and to fill the IDOC data records
    and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
    Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
    1)Message control
    Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
    In outbound programs(function module) that use message control the key of the
    application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
    message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
    The parameteers passed to the function module are
    IMPORTING PARAMETERS
    OBJECT LIKE NAST
    It contains documents key.
    CONTROL_RECORD_IN LIKE EDIDC
    It contains the partailly filled control record
    EXPORETING PARAMETER
    OBJECT_TYPE
    CONTROL_RECORD_OUT LIKE EDIDC
    TABLES
    INT_EDID LIKE EDIDD
    The internal table used to fill the data records in the same order as they exists in the IDOC.
    The important parameters that should be filled in the custom function module are
    CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
    2)Stand alone programs
    Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
    Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
    Data is filled in an internal table of TYPE EDIDD according to segment definitions
    and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
    3)Change pointer
    Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
    ALE/IDOC Transaction
    SALE Area Menu for ALE configurations.It includes transactions for
    Logical System definition and linking it to a client, Transactions for
    RFC Destination and Port Definition Etc.
    SM59 RFC Destination
    Here we specify the login settings for the destination including
    the I.P address or Application Server name and the User name and
    password.The information entered here is used to run Remote Function
    Calls(RFC ) on the destination server .We can create number of types
    of RFC Destinations but 3 types are important .
    R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
    The name of the RFC destination should be same as that of Logical
    System as it helps in creation of automatic partner profiles.
    WE21 Port Definition.
    There are 6 types of ports but only 2 types File and Transactional RFC
    types of ports are important.
    We have to specify the RFC Destination before a port can be created.
    WE57 This is used to assign the Inbound function module to the Message Type
    and to the IDOC Type.
    WE42 This is used to define the process Code for Inbound Processing.
    BD95 Define Filter object type .We can specify the field and the table it belongs
    to as a filter object .
    BD59 Assignment of Filter object type to the Message Type .Here we create the
    link between Filter object and the segment and the message type and the
    segment Field.
    BD50 Set message Type to reducible.
    BD65 Define Mandatory Fields.
    BD64 Distribution Model . Also known as Customer Distribution Model Used to
    define all the messages that will be exchanged between remote systems
    and the name of thes logical systems. Any filters can also be specified.
    The model once created has to be distributed on every system which will
    be communicating ,It can be maintained on only One system.
    BD21 Creating IDOcs from change pointers.
    This can be used to create IDOCs from change pointers for a particular
    message LIKE MATMAS.
    BD22 This can be used to delete change pointers.
    BD87 Status Monitor. Idocs can be selected base on number of criteria and there
    processing status can be seen in detail.
    BD10 Material Master Data Distribution .
    Based on Message MATMAS.
    BD12 Customer Master Data Distribution .
    Based on Message CREMAS.
    BD14 Vendor Master Data Distribution
    Based on Message DEBMAS .
    BDFG Generate ALE Interface for BAPI.
    Here we specify the Business Object and the BAPI Function module for
    which the interface has to be created.
    WE31 Segment Editor.
    This is used to create segments. We create the segment type and
    segment definition is automatically created by editor e.g. Z1DUMMY is
    segment type and Z2DUMMY is the segment definition .We specify the
    fields and the data elements these cp\orresponds to create segments.
    WE30 IDOC Editor
    It is used to create a new IDOC Type or IDOC Extension .We specify the
    segments that will be addd to the IDOC type.
    WE02/05 IDOC List.
    Various selct options and parameters are provided to select IDOCs
    depending on the date, direction , mesage type etc.
    WE20 Partner Profile
    Here we create partner profile for each and every partner from / to which
    the messages will be exchanged.There are 6 types of PF generally only
    profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
    We specify the partner number and partner type and the agent and
    the agent type responsible for handling of errors .
    For every message send to the partner we have a outbound record and for
    evry message coming from the partner we have the inbound record .
    We specify the message in the otbound/inbound records ,double
    clicking will take us to the detailed screen where the IDOC Type ,Port
    and whether the IDCO will be immediatelt processed or collected are
    mentioned.

  • What are ways to transfer data from online system to SAP

    Hi all,
    We have a requirement to transfer data from an online system (Non SAP) to SAP.
    What are all the possible ways to  do that and which one is preferred?
    Thanks!
    Rahul.

    Dear
    for transferring data from online system to SAP there are different ways follow this links
    http://searchsap.techtarget.com/answer/Using-IDocs-to-connect-a-non-SAP-system-to-an-SAP-R-3-system-online
    https://help.sap.com/saphelp_nw70ehp1/helpdata/en/c7/eff2280d0511d3a6300060087832f8/content.htm
    Regards

  • Standard IDOC to transfer Work center master

    Hi all,
    Please tell me the tcode of Standard IDOC to transfer Work center master from one system to another.
    Thanks.

    Hello,
    There will be no standard Idoc like this we have an std idoc type.
    if so u want search goto tcode we02 .
    Thank u,
    Jay..............................

  • How do i transfer music from one account to another?

    I want to transfer music from my account to my friends account, how do i do that?

    You can't transfer content from one account to another.

  • How can i transfer songs from one itunes to another?

    I have a new computer and want to transfer all of my songs from one computer to another.  I have home sharing turned on but can't figure out how to save the songs to the new computer.

    I have home sharing turned on but can't figure out how to save the songs to the new computer.
    First, make sure you've got the home share set up on both computers, as per the following document. If material on the original PC was bought from the iTunes Store, I'd use the AppleID you used for the purchases to set up the Home Share on both PCs.
    iTunes: Setting up Home Sharing on your computer
    Have both computers running and have iTunes open on both computers.
    Now, in the iTunes on the computer you want to transfer music to, select the library that you want to transfer music from, as per the following screenshot:
    Once the other library loads, go down to the bottom of the screen and in "Show:" select "Items not in my library":
    If you want to import all of the songs you can now see, head up to the iTunes menu bar and go "Edit > Select all". Then head down to the bottom of the screen again and click the "Import" button in the bottom-right-hand corner.
    If there's a lot of stuff in your original PC's library, the transfer may take some time.

  • How can I transfer work from one computer to another?

    How can I transfer work from one computer to another?

    Welcome to the forum.
    I can think of three basic ways to accomplish what you wish to do:
    Use the Project Archiver to archive your Project (and check the box to gather the media files), to an external HDD. Probably the easiest way to do it.
    Copy the Project and ALL media files to an external HDD, but be prepared to relink the media files to the Project, as the drive letter (part of the Absolute Path) will have changed.
    Edit loosely, and Share to an AV file, which will be Imported into a New Project on that second computer. Or, edit VERY tightly, and do the same. I like the first, as removing, replacing Transitions, etc., can be much more difficult, unless that "tight edit" is 100% done.
    Good luck,
    Hunt
    Message was edited by: Bill Hunt to correct formatting

  • How can I transfer information from one ipad to another?

    how can I transfer information from one ipad to another ?

    What kind of information? You can sync things like Contacts and Calendars by using iCloud. You can backup one iPad to iTunes on a computer and then sync the backup to the other iPad. You can configure your iTunes content and sync the same content to both iPads.
    It is based on what you want to do. Or are you looking for a way to send files from one iPad to another wirelessly? There are apps to do things like that, as well as cloud services, such as DropBox.

  • How can I transfer songs from one computer to another

    How can I transfer songs from one computer to another

    Type "move itunes library" or similar into the Google search bar.

Maybe you are looking for

  • If i backed up my iPhotos on an external hard drive can i delete them off my mac?

    I recently backed up my Macbook pro on to an external hard drive. I was wodnering if i could delete my photos from my iphoto library to save space, and if so can i then get them back on my computer from my external hard drive?

  • Error in cacelling billing document in t.code VF11

    Dear Friends, When i have Cancel billing document with t code VF11, following error occuared Error Log 1102277799 000000 Cancellation document is not the same as the original billing doc. 1102277799 102277799 000000 Data inconsistency during processi

  • EBS: Posting on account to Customer  through search string

    We are attempting an on account posting to the customer account based on the customer name in the bank statement. The configuration looks as follows. 1. Posting rule reflects the setting for posting area 1 and 2. For the second posting area the credi

  • Query language for CTXRULE MATCHES

    I am trying to build an alerting application when, on receipt of a new XML document, user's are alerted if the document matches one or more of the profiles that they have defined. I have created a CTXRULE index that does this but only with very simpl

  • Problems with the FIREBOX presonus

    i leave the computer on sleep and the box is always on gets hot and blue turns to red. lately headphone plugs get one channel only , if i restart and do all kinds of manips with AUDI MIDI and the firebox mixer including pulling out the firewire cable