Tcode for triggering DESADV idoc

Hi Gui's,
I have to trigger the idoc type DESADV will  you please any body provide the tcode.
Thanks,
Santosh
Moderator message: please do more research before asking.
Edited by: Thomas Zloch on Mar 28, 2011 9:09 AM

Hi,
To trigger a event, u shld use the Tcode SWUE.
Here u have to specify
1) Object category = Bus. obj Type
2) Object Type = ur BUs. obj
3) Object Event = which event u wan to trigger
4) Click on Object Key button & enter the key field value(s)
5) There is a butoon 'Event Parameters' . Click on tht to enter the event parameter values.
6) If u click on 'Event Receiver' button, u can c which WFs r linked to this event
7) Now click on 'Create Event' to trigger the event
Regareds,
Sivagami

Similar Messages

  • Reg : change pointer mechanism for triggering the IDOC for delivery note

    Hi ,
    I am working on a change pointer mechanism for triggering the IDOC for delivery note and will be using this message class DESADV.
    So SAP has suggested for assigning the message class DESADV with the function module in MASTERIDOC_CREATE_SMD_DESADV in BD60 transaction code.
    So I was looking to create this MASTERIDOC_CREATE_SMD_DESADV function module in SAP and SAP suggesting that  we should create this MASTERIDOC_CREATE_SMD_DESADV function module as same as the function module MASTERIDOC_CREATE_SMD_MATMAS.
    So do anyone knows that is there any tool has been provided by SAP for creating this function module MASTERIDOC_CREATE_SMD_DESADV in SAP system for triggering the change pointer mechanism for outbound Delivery.
    Thanks !
    Regards,
    Kiran

    Hi,
    When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention.  If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen.  Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
    Thanks,
    Mahesh.

  • TRIGGERING THE IDOC

    Hi
        I have one Zxxx table.. that contain some master data  details... now  i want to send these details to external systems... i created one custom IDoc and  Message type.. every thing... 
      but for triggering the idoc what we need to do.. for  example..  for predefined data we have option   like BD10, BD12, BD14...  these executable programs.. or  Chnage pointers(RBDMIDOC) we can trigger the idoc for predifined data..
    but for user defind  data tables.. what can we do for triggering the idocs..
    thanks
    BABU

    Hi,
    check the below sample code for triggering the idoc..The same thing u can do for ur requirement..slect all then data from ur custom table and finally call the FM
    "MASTER_IDOC_DISTRIBUTE".
    *& Report ZZ_Program_To_Create_Idoc
    report zz_program_to_create_idoc .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
    item_segment_name like edidd-segnam value 'Z1EKPO',
    idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
    item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
    i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
    ebeln like ekko-ebeln,
    aedat like ekko-aedat,
    bukrs like ekko-bukrs,
    bsart like ekko-bsart,
    lifnr like ekko-lifnr,
    end of i_ekko.
    data: begin of i_ekpo occurs 0,
    ebelp like ekpo-ebelp,
    matnr like ekpo-matnr,
    menge like ekpo-menge,
    meins like ekpo-meins,
    netpr like ekpo-netpr,
    end of i_ekpo.
    start-of-selection.
    select ebeln aedat bukrs bsart lifnr from ekko
    into table i_ekko where ebeln in s_ebeln.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
    exporting
    master_idoc_control = control_record
    OBJ_TYPE = ''
    CHNUM = ''
    tables
    communication_idoc_control = i_communication
    master_idoc_data = i_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.
    else.
    loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
    endloop.
    commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    Reward if hlpful.
    Regards,
    Nagaraj

  • Tcode for IDOC

    Dear friends ,
    can any one give me important Tcodes for IDOC & workflow
    Reddy

    Tcode list for ALE IDOC:
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    WE02     List Of All Idocs Created. (Default, Additional, EDI)
    WE05     List Of  Idocs Created.    (Standard, Additional)
    WE06     Active Monitoring For Idoc Processing.
    WE07     Idoc Statistics.
    WE08     Display View u201CFile Statusu201D:Overview-Path Name.
    WE09     Idoc Search For Business Contents (Database).
    WE10     Idoc Search For Business Contents (Archive).
    WE12     Modification Of Outbound File, Triggering Inbound Processing.
    WE14     Process All Selected Idocs.
    WE15     Selection Program For Issuing Output.
    WE16     Trigger Inbound Processing.
    WE17     Trigger Status Processing.
    WE18     Generate Test Status File For Outbound Idocs.
    WE19     Test Tool For Idoc Processing
    WE20     Partner Profile.
    WE21     Ports In Idoc Processing.
    WE23     Display Test Catalog Test Idoc Interface.
    WE24     Maintain Table View. Direction-1.(Outbound)
    WE27     Maintain Table View. Direction-2.(Inbound)
    WE30     Develop Idoc Type.
    WE31     Develop Idoc Segments.
    WE32     View Development.
    WE33     Maintain Table Views.
    WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
    WE40     Display System Process Code.
    WE41     Display View: Logical Msg Overview. For Outbund.
    WE42     Display View: Logical Msg Overview. For Inbound.
    WE43     Display Status Records.
    WE44     Display Partner Types
    WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
    WE46     Global Parameter For Idoc Interface.
    WE47     Status Maintenance.
    WE50     Display Text For Process Code System.
    WE54     Idoc Function Module For File Name
    WE56     Display Status Process Code
    WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
    WE58     Text For Process Code Status.
    WE60     Documentation For Idoc Type.
    WE61     Documentation For Idoc Record Type.
    WE62     Documentation For Idoc Segment Type.
    WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
    WE64     Process Code In Idoc Inbound And Outbound.
    WE70     Conversion Table For Basic Types.
    WE71     Conversion Table For Extensions.
    WE72     Conversion Table For Field DOCTYP.
    WE73     Conversion Table For Logical Message Type.
    WE81          EDI:Logical Message Type.
    WE82     Message Types And Assignment To Idoc Types.
    WE84     Assignment Table Between Idoc And Application Field.
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    BD10     Send Material (Matmas)
    BD11     Get Material.
    BD12     Send Customer.
    BD13     Get Customers
    BD14     Send Vendor.
    BD15     Get Vendor.
    BD16     Send Cost Center. (Cosmas)
    BD17     Request Cost Center.
    BD18     Send G/L Accounts.
    BD19     Get Master Data G/L Accounts.
    BD20     Inbound Processing Of Idocs Ready For Transfer.
    BD21     Creating Idoc Types For Change Pointers.
    BD22     Delete Change Pointers.
    BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
    BD24     Send Cost Elements.
    BD25     Send Activity Type (COAMAS)
    BD26     Request  Activity Type
    BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
    BD28     Cost Center/ Cost Elements: Send Control Records.
    BD30     Material Bom Distribution. (Bommat).
    BD31     Document Structure Distribution. (Bomdoc)
    BD32     Plant Allocation To Material Boms Distribution.
    BD33     Distribution Of Material Variants. (STTMAT)
    BD34     Distribution Of Boms (BOMORD)
    BD35     ALE: Send Business Process Group.
    BD36     ALE: Send Business Process.
    BD37     ALE: Send Business Process Price.
    BD40     Generate Idocs For Serialization Group From Change Pointers.
    BD41     Dispatch Of Idocs  Of Serialization Group.
    BD42     Check Dispatch Status Of Idocs Of Serialization Group.
    BD43     Processing Inbound Idocs Of Serialization Group.
    BD44     Change View u201CSerialization Groupu201D.
    BD47     Dependence Between Methods.
    BD48     Dependence Between Methods And Message Type.
    BD50     Activate Change Pointers For Message Type.
    BD51     Characteristics Of Inbound Function Module.
    BD52     Determine Work Area.
    BD53     Reduce Message Type.
    BD54     Change View: Logical Systems
    BD55     Idoc Conversion.
    BD56     Maintain Idoc Segment Filters.
    BD57     Link Type And Serialization Type Of Message Type.
    BD58     Convert Organizational Unit.
    BD59     Allocation Of Object Type.
    BD60     Additional Data For Message Type.
    BD61     Activate Change Pointers Generally.
    BD62     Display Conversion Rule.
    BD63     Transport Of Ale Tables For A Message Type.
    BD64     Display Distribution Model.
    BD65     Maintain Idoc Type Required Fields.
    BD66     Change Idoc Fields.
    BD67     Function Module For ALE/EDI Overview.
    BD68     Maintain List.
    BD69     Assignment Of Idoc Type To Message Type.
    BD70     Cross-System Comparison Of Number Range Objects.
    BD71     Attributes For Receiver Determination.
    BD72     Active Events For ALE/EDI
    BD73     Start Error Handling For Non-Posted Idocs.
    BD75     Status Conversion With Trfc Execution.
    BD77     Generate Transport Requests For Distributing ALE Customizing Data.
    BD78     Monitoring Ale Customizing Data Transport
    BD79     ALE IDOC Segments - Conversion Rule
    BD81     Filter Objects For BAPI Parameter Filtering
    BD82     Generating Partner Profile
    BD83     Re-Processing Incorrect Outbound Odocs.
    BD84     Re-Processing Of Idocs After ALE Input Error.
    BD85     Consistency Check: Reassignment Between Two System.
    BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
    BD87     Select Idocs
    BD89     Customizing Data Modeling For Distribution Model.
    BD91     Distribute All Characteristics Via ALE.
    BD92     Distribute Class Via ALE: Send Direct.
    BD93     Distribution Of Classification Data Via ALE.
    BD95     Ale Object View
    BD96     Filter Object For Receiver Determination Of Methods.
    BD97     Assign RFC Destination For Synchronous Method Calls.
    BD98     Consistency Check With Workflow Link
    BD99     Dependencies Between Message Types.
    BD100     Display Serialized Idocs. (Serialization Using Object Types)
    BD101     Serialization Using Object Types: Consistency Check.
    BD102     Ale: Outbound Channel Registry.

  • Idoc error mapping error for segment "E1EDT13 006" in DESADV idoc

    Hi SAP Gurus,
    DESADV IDOC for few articles is not getting passed from SAP to legacy system. It is missing one segment"E1EDT13 006" for goods issue.
    Why is this mapping error happening. How can this be resolved.
    Regards.
    Sumi

    Hi Nsangle/SAP gurus,
    Thanks for  that. But, I have already compared the failing idoc with the successful one. It's the segment E1EDT13 006 missing in the wrong idoc. I have already added that idoc and reprocessed it.
    But, I wanted to know why such kind of idoc segment missing/ mapping error happens.
    Regards.
    Sumi

  • Triggering inbound idoc for FI T.Code F-02

    Hi,
    Anybody has triggered idoc for posting key 40 & 50 for F-02 T.Code in ECC 6.0, plz share their experience & triggering inbound idocs.
    rgds,
    balu

    closed

  • What is the TCODE for number change of idoc

    Hi all,
    can anyone help me in chnaging the number range of IDOCS in R/3 system..
    what is the TCODE for that...
    Thanks in advance.
    Cheers,
    Raghavesh

    Hi,
    Please go to transaction SNUM/SNRO and use object EDIDOC.
    Select number range and change to specific number that you wish.
    Hope this will help.
    Regards,
    Ferry Lianto

  • Automatic triggering of idoc for Personal Actions T Code (  PA40 )

    Hi Experts,
    I wanted to do automatic triggering of idoc after performing Personal Actions by transaction PA40.
    Needed some info .
    Thanx in Advance,
    Pradipta

    Hi Pradipta,
    You can use the change pointers for this.  Just check for what fields you want to trigger an IDOC.  But this can not be triggered immediately.  You have to run RBDMIDOC frequently.  It will take the input as messaeg type and generate the IDOCs.
    Before that please check if the change pointers are activated for this message type or not.
    shylesh

  • Tcode for Exchangerate01  idoc

    HI Guis,
    What is the tcode to generate standard idoc for  Exchange_rate.
    Regds,
    Santhosh

    Hi,
         Could you elaborate on your requirement?
    Regards
    Ram

  • Tcode for global idoc interface parameters

    hi,
      can any one say me the tcode for global idoc interface parameters.

    Hi,
    Welcome to SDN.
    check this link might help you.
    tcodes for ALE
    Regards,
    Amit
    Reward all helpful replies.

  • No change triggered for assortment list IDOC

    Dear all expert,
    I'm facing a problem and below is issue reproduction steps.
    1. Article 'A' listed to Assortment 'ASM01' which is assigned 3 sites as assortment users.
    2. I executed WDBI for assortment list initialization. 3 IDOC files are generated successfully.
    3. Now, I unassigned one of the site from the assortment ASM01.
    4. I execute WDBU for assortment list IDOC change message. No IDOC is generated for this site.
    Any idea?
    Thank you very much!
    Regards,
    Wso

    Hi Tobias,
    Thanks for your reply!
    Actually i'm newbie on SAP Retail and now looking at listing and assortment stuff. I've configured the Assortment List Profile with checkbox 'Deletions for Listing' selected. Below is the SAP help explanation:
    "Indicator: Generate Deletion Records for Listing
    When you set this indicator, special material header records, carrying the information from the store retail system about the deletion performed, can be sent during deletions of assortment assignments between plant and assortment or during physical deletions of listing conditions in the change version of the assortment list. In the IDoc, these materials are marked with the change indicator AENKZ = 'DELE' in segment E1WBB01."
    So i wonder a IDOC file will be generated for the unassigned site with change indicator DELE for all articles listed to that site.
    Thanks again!
    Regards,
    Wso

  • Auxiliary Packaging missing from DESADV IDOC

    Hi Experts,
    I have a delivery attached to a shipment, when the output for the shipment triggers an outbound DESADV IDOC, the segment E1EDP08 and E1EDP06 contain normal packaging material information, BUT Auxiliary packaging material information (which do not have a handling unit number) is missing.
    How to get this aux pack info into E1EDP08 and E1EDP06 segments of DESADV IDOC? any configuration, user exit, coding?
    maximum points would be rewarded, if the solution is helpful.
    Br,
    Ankur

    I have checked these field available in DESADV original message in WE19 transaction.You need to add in Functional module program if the packing material has AUXilary packing then system should populate these fiels.Check why the current program it is not populating?.If the logic is not written in existing program then you need to modify the code.

  • How to block the status mail for an inbound Idoc to a specific user

    Hi,
    I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
    Thanks,
    Santosh

    Hi,
    I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
    Thanks,
    Santosh

  • How to find out the Tcodes for the exits

    Hi All,
    how to find out the Tcodes for the exits. i have a list of exits (customer, user, badi ). i need to find out what are the Tcode affected by this exits.
    Customer Exits: EXIT_RFEBBU10_001
                              EXIT_RFEKA400_001
                              EXIT_RFFOEXIT_100
    User-Exits:  USEREXIT_DELETE_DOCUMENT
                       USEREXIT_FIELD_MODIFICATION
                       USEREXIT_MOVE_FIELD_TO_VBAK
                       USEREXIT_PRICING_PREPARE_TKOMP
    BADI: CUSTOMER_ADD_DATA_CS
              HISTORICAL_VALUES
              MD_ADD_ELEMENTS
              MD_CHANGE_MRP_DATA
              MD_PIR_FLEX_CONS
              MD_PLDORD_POST
              ME_REQ_POSTED
              NOTIF_EVENT_SAVE
    Can anyone help on this <urgency factor removed>.
    Regards
    Ksihore
    Edited by: Suhas Saha on Feb 20, 2012 12:58 PM

    i have just started reading about all these-user exits ,customer exits etc.
    i have read somewhere that:call to customer exits are triggered by function modules exits.
    the structure of function modules are like this:
    EXIT_RFEBBU10_001
    MEANS
    Keyword EXIT followed by program name fllowed by three digits.
    and the call is like this:
    call customer function 0001.
    From above we can conclude that this customer exit must be used in program RFEBBU10.
    GOTO SE38 andenter prog name RFEBBU10.check for above function module.
    for the rest i stick to the same method for user exits and BADI that we can findthe corresponding TCODES
    using Where used lists.
    please Tell me if i m wrong!

  • DESADV idoc

    Hello,
    I have a question regarding DESADV idoc.
    DESADV idoc creates and inbound delivery.
    We have this problem : we need to create our inbound delivery right after the PO creation.
    Do you know if the DESADV idoc can update an existing inbound delivery ?
    Thanks,
    Regards,
    PYR

    how can system up date the same inbound delivery in different PO ............as inbound delivery is created with reference to the PO and it gets updated automatically in the PO.
    If you want the DESDAV should update the PO right after the creation of the PO then  its possible but you need to write a Z program for that  because DESDAV means vendor has informed you that he has shipped the goods and the thing is that if the PO is created then at any point of time DEDAV can update the confirmation in PO.
    If you want that the moment you save PO system should trigger the DESDAV then i have some question
    1. for what quantity system should update the PO thru DESDAV
    2. from where will the DEDAV would be getting all the required information

Maybe you are looking for