IDoc triggered frm R/3

Dear All,
When an Idoc is triggered frm R/3 it shows status red(error to port), yellow(still processing) or green(succesfuly port)..
as an eg. green..
Does it mean a confirmation as a color in status grp that the Idoc has reached to the destination port or simply when the Idoc succesfully comes out of R/3 the status grp become green..
Please suggest..
- Pankaj

Hi Pankaj ,
Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
Thank
Sunil Singh

Similar Messages

  • Whenever the idoc triggers its contains two lines of record,

    Hi Experts,
    In my IDOC INFREC.INFRECMASS01 has two segments E1E1NAM and E1E1NEM.Both the Segments has some fields.In that E1E1NEM segment-WERKS contains two valuse, First its coming with 1010. Second its coming with 1014.So its Second line.So whenever the idoc triggers its contains two lines of record, Each i need to update in JDBC At same time.How? Even i tried SplitByValue with ValueChange its not working.... please help....
    Advance Thanks
    Arun

    We are working on IDOC to JDBC scenario.
    In my IDOC INFREC.INFRECMASS01 has one  segment E1E1NAM( parent segment), inside this parent segment we have one  child segment E1E1NEM containing two lines. On the basis of one field WERKS, the child segments should get repeated in the target  but in the target side we are getting only one of the values of WERKS .
    We have used SPLIT BY VALUE(each value) on WERKS but still only one of the values are coming on the target side .
    We are attaching the source xml and the target xml generated from RWB
    *Source XML  from SXMBMONI :*_
      <?xml version="1.0" encoding="UTF-8" ?>
    - <INFRECMASS01>
    - <IDOC BEGIN="1">
    + <EDI_DC40 SEGMENT="1">
    - <E1EINAM SEGMENT="1">
      <MSGFN>005</MSGFN>
      <INFNR>5300000074</INFNR>
      <MATNR>000000000000103260</MATNR>
      <LIFNR>0000009000</LIFNR>
      <ERDAT>20091116</ERDAT>
      <ERNAM>KAPIL</ERNAM>
      <MEINS>PK</MEINS>
      <UMREZ>10</UMREZ>
      <UMREN>1</UMREN>
      <TELF1>011-64612814</TELF1>
      <MAHN1>0</MAHN1>
      <MAHN2>0</MAHN2>
      <MAHN3>0</MAHN3>
      <URZDT>00000000</URZDT>
      <URZLA>IN</URZLA>
      <LMEIN>ST</LMEIN>
      <REGIO>30</REGIO>
      <VABME>1</VABME>
      <LTSSF>00000</LTSSF>
      <LIFAB>00000000</LIFAB>
      <LIFBI>00000000</LIFBI>
      <ANZPU>0.000</ANZPU>
      <RELIF>X</RELIF>
    - <E1EINEM SEGMENT="1">
      <MSGFN>005</MSGFN>
      <EKORG>1000</EKORG>
      <ESOKZ>0</ESOKZ>
      <WERKS>1010</WERKS>
      <ERDAT>20091116</ERDAT>
      <ERNAM>KAPIL</ERNAM>
      <EKGRP>101</EKGRP>
      <WAERS>INR</WAERS>
      <MINBM>0.000</MINBM>
      <NORBM>1.000</NORBM>
      <APLFZ>0</APLFZ>
      <UEBTO>0.0</UEBTO>
      <UNTTO>0.0</UNTTO>
      <ANGDT>00000000</ANGDT>
      <NETPR>0.00</NETPR>
      <PEINH>1</PEINH>
      <BPRME>PK</BPRME>
      <PRDAT>00000000</PRDAT>
      <BPUMZ>1</BPUMZ>
      <BPUMN>1</BPUMN>
      <WEBRE>X</WEBRE>
      <EFFPR>0.00</EFFPR>
      <MHDRZ>2</MHDRZ>
      <BSTMA>0.000</BSTMA>
      <STAGING_TIME>0</STAGING_TIME>
      </E1EINEM>
    - <E1EINEM SEGMENT="1">
      <MSGFN>005</MSGFN>
      <EKORG>1000</EKORG>
      <ESOKZ>0</ESOKZ>
      <WERKS>1014</WERKS>
      <ERDAT>20091116</ERDAT>
      <ERNAM>KAPIL</ERNAM>
      <EKGRP>101</EKGRP>
      <WAERS>INR</WAERS>
      <MINBM>0.000</MINBM>
      <NORBM>1.000</NORBM>
      <APLFZ>0</APLFZ>
      <UEBTO>0.0</UEBTO>
      <UNTTO>0.0</UNTTO>
      <ANGDT>00000000</ANGDT>
      <NETPR>0.00</NETPR>
      <PEINH>1</PEINH>
      <BPRME>PK</BPRME>
      <PRDAT>00000000</PRDAT>
      <BPUMZ>1</BPUMZ>
      <BPUMN>1</BPUMN>
      <WEBRE>X</WEBRE>
      <EFFPR>0.00</EFFPR>
      <MHDRZ>2</MHDRZ>
      <BSTMA>0.000</BSTMA>
      <STAGING_TIME>0</STAGING_TIME>
      </E1EINEM>
      </E1EINAM>
      </IDOC>
      </INFRECMASS01>
    TARGET XML FROM RWB:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_IB_VENDORISL xmlns:ns0="http://VENDORITEMSITELINK_NS">
    - <STATEMENTNAME>
    - <si_sku_vendor_link ACTION="INSERT">
    - <ACCESS>
      <Sku_Code>000000000000103260</Sku_Code>
      <Location_Code>1010</Location_Code>
      <Vendor_Code>0000009000</Vendor_Code>
      <Lead_Time>0</Lead_Time>
      <Pref_Vendor_Flag>Y</Pref_Vendor_Flag>
      <Active_Ind>Y</Active_Ind>
      </ACCESS>
      </si_sku_vendor_link>
      </STATEMENTNAME>
      </ns0:MT_IB_VENDORISL>

  • Idocs, idocs triggering

    Hi SAP gurus,
    Please send me some documentation/tutorials/learning material regarding IDOCS, Idoc Triggering. My mail id  - [email protected]
    Thanks in advance,
    Regards,
    Balu

    Hi Balu,
    Please check this online document for ALE and IDoc.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Also check this links for additional information.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    Hope this will help to start with.
    Regards,
    Ferry Lianto

  • IDoc triggering without Output type?

    Hi Experts,
    I need a help regarding triggering of IDoc. I need to trigger an o/b IDoc for message type SHP_OBDLV_SAVE_REPLICA without having output type on creation or save. Could you please anyone advise is there anyway to do it? It would be great if someone have come across for this kind of req and would helpful for me share same with me.
    Thanks.

    Hi Brad,
    Thanks for your input. Is there any o/b process code exists for Idoc type SHP_OBDLV_SAVE_REPLICA02? Could you anyone share if there is any.
    Thanks

  • IDOC triggerring when create/change in POP1/POP2/MM01 programatically

    Hello experts,
    Can u please help me with the below requirement how i should proceed.
    u2022Trigger a packing instruction IDoc from ECC to MII whenever the packing instructions are created/changed in ECC via t-code POP1/POP2.
    u2022Trigger a packing instructions IDoc from ECC to MII whenever a new or existing material with packing instructions are extended to an MII enabled plant in ECC via t-code MM01.
    regards,
    NTGS.
    Moderator message: please do more research before asking, show what you have done when posting.
    Edited by: Thomas Zloch on Feb 20, 2012

    Hi,
    For Triggering an IDOC on creation of new material you have to add the "KEY" field entry for the respective table in your BD52 transaction(Change Document Items for Message Type).
    There are 3 types of changes: Insert, Update and Delete.
    Insert : With the insert change type precisely one record is written (table name, table key, field name = "KEY", change type = insert, old value = empty, new value = empty). The field values are not documented as they can be found in the database. With this change type it is important that the special field name KEY is used.
    Pls refer to the following link for more details: http://help.sap.com/saphelp_470/helpdata/en/78/2178da51ce11d189570000e829fbbd/frameset.htm
    Note: I have provided the solution because this thread is marked as "Answered" but no answer is provided for the question. So I thought of updating the answer as it would be helpful for someone facing similar issue.
    Regards,
    Sridhar
    Edited by: Sridhar Upadhyayula on Jul 27, 2009 11:02 AM

  • Real Time Customer Master idoc triggering problem

    For a real time integration scenario of cust master idocs ,i had customized the customer master msg type Debmas to ZDEBMAS & used method CUSTOMER_ADD_DATA~CHECK_ADD_ON_ACTIVE ,for triggering the idoc whenever i press save button in XD01& i'm calling BD12 (BDC using call trasaction)in this method. the problem is that for some users when they logs in for the first time & creates any customer (XD01), idoc didn't get generated for the first time , this may occur for 2-3 times or some times it get generated for the first time itself ,after that it starts triggering as programmed.I need ur valuable solutions for this particular problem....................
    Moderator message - Cross post locked
    Edited by: Rob Burbank on Apr 24, 2009 10:06 AM

    Hi,
    if I correctly understand the process you try to setup:
    At save time of a customer master data,you want to distribute it via idoc.
    Currently, you try from BAdI method SAVE_DATA to generate your idoc.
    Well, to me, there is NO insurance that the customer is already created when your custom process triggers BD12.
    So, for me except if your try to define a process which is really time based, I would process that you simply remove the BAdI and setup a job that sends customers per change pointers every 5 minutes for example.
    This will be more simple and more reliable.
    If you really need that the sending process is trigger at save time, then I would suggest the following.
    In method SAVE_DATA or BTE 1321, start a routine that will ensure that BD12 is triggered after the customer has reached the database. In other words, the commit is fully finished.
    Nota: DO NO TRIGGER THE COMMIT WORK YOURSELF
    So my suggestion follows:
    method SAVE_DATA will trigger a custom FM in update task.
    In this FM, you will trigger either BD12 directly in BDC or start a new task that will call BD12 in BDC.
    This should work because, the update task triggered from SAVE_DATA will be enqueued after the real saving on the database of the customer in update task too.
    Please try to take the first option above. You process will be more simple and easy to support.
    Hope this helps.
    BR
    Alain

  • Idoc triggering

    Hi
    I am working on an Interface which has to send out material master fields and some fields which are to be obtained by calculations from fields of 3 different tables (keph kekp marm).
    Can I activate change pointers to the custome message type I will be creating with basic type as MATMAS05 and custom extension type.
    Can anybody explain me the steps for populating the custom fields and triggering the idoc creation, whenever there is a change in the material master data of materials from a particular plant and of particular type.( finished and semi-finished goods).
    Thanks and regards
    Pratyusha.

    Hi,
    check these steps :
    1.Go to the Data Element of the field and check whether change doucment option is checked or not .
    2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
    3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
    if not check the following config
    1.BD61- change pointers activated -generally
    2.BD50 -Activate change pointers for ur message type
    3.BD52 - add the triggering fields and corresponding tables and change document object.
    Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
    check this link for idoc enhancement details :
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
    Regards
    Appana

  • Idocs Triggering!

    Hi Guys!
         Can any one tell me how the idocs gets created step by step process after creating & saving the application document.
        Just tell me the steps in sequence
        like  the control goes from where to where from seqence.
       Looking for your answer.
       Rahul.

    Hi,
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    Regards,
    Priyanka.

  • Finding Z idocs triggering points

    Experts,
    In my system there are few Z message types and Z basic types .
    I wanted to know from which program these IDOCS are getting triggered.
    Can you please let me know how to find  IDOCS treggering points.
    Or is there any transaction to find " Where used list" for Z message types?
    Please let me know
    Your answers will be appreiated!

    You can find the method used for processing the given message type for inbound idocs.
    go to WE57 and enter message type for filtering.
    It will list down the functiona module used.
    If you further want to test go to we19 enter the basic type ,before this put a breakpoint inside the functiona module selected above.
    now click on inbound function module tab , select the function module from F4  and check  "call  n debugging mode".
    This will give an idea how the processing happens.
    hope this helps.

  • Regarding Idoc triggering

    I want to trigger an idoc from EC1CLNT 800 to XI  through change pointer .
    please provide the steps for that along with the Tcodes

    Try this
    Change pointers
    you need to schedule a raport that will create IDOCs  from your change pointes
    only then your idocs will be created
    use report : RBDMIDOC
    to create your IDOCs from change pointers
    Change documents are working based on change document technique which
    tracks changes made to the key documents (Material Master, Customer Master,
    Vendor Master.Etc) in SAP.
    Changes made to the keydocuments are recorded in the change document Header
    table i.e. CDHDR and Item table CDPOS, Additional change pointers are written
    in the BDCP and BDCPS tables.
    Change pointers technique is used to initiate the outbound process automatically
    when master data is created or changed.
    A standard program RBDMIDOC is sechuled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the Masterdata to the appropriate destination.
    'Object' is collection of fields of different database tables. T.code for creating an object
    is SCDO.
    Configuration for Change Pointers:
    1. BD61 Active change pointers generally
    - Check the checkbox "Change pointers activated -generally"
    - Save it
    2. BD50 Active change pointers for Message Type
    Message Type Active
    MATMAS Check the check box
    3. SCDO Change Document Objects
    - Check whether the "MATERIAL" is available in the object list.
    4. BD52 Maintain Table Views
    - Enter the Message type "MATMAS" and press enter.
    For example
    OBJECT TABLE NAME FIELD NAME
    MATERIAL MARA BISMT
    5. BD60 Additional data for message types:
    For example:
    Message Type Function Module Table
    MATMAS MASTERIDOC_CREATE_SMD_MATMAS MARA
    6. WE21 Port
    7. WE20 Partner Profile
    8. BD64 Distribution Model
    as michal said we have to use RBDMIDOC program.for executing this program we need to give message type like
    MATMAS or
    DEBMAS or
    CREMAS
    depending on your requirement.
    go to SE38 tcode
    --- copy RBDMIDOC to zprogram(i'e., ZRBDMIDOC)
    ---create variant
    use this zprogram(ZRBDMIDOC) in BACKGROUND SCHEDULING SM36
    STEPS IN BACKGROUND SCHEDULING:
    Use tcode SM36
    Click Job wizard in the button set
    Click Continue
    Enter Job name and press continue
    Select ABAP program and press Continue
    enter Program name and press continue
    and again press Continue
    set Schedule type immediately and continue
    Select periodic job checkbox, press continue
    Select none of the above and click on other periods – give one-minute and then press create
    Press continue and then press complete.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ab/27bde462848440ba70cf8eb348c86f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/69/7ada54a2737949ae6fbb082edb56a5/content.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6196507d11d18ee90000e8366fc2/content.htm
    Thanks

  • IDOC triggerred by which Output type?

    Hi Gurus,
    My requirement is to add a new segment in ORDERS05 and populate the values int he Zsegment based on the output type selected.
    I am using same user-exit to populate but i am not sure how to find the output type which user selected.
    How to find the Output type in FM IDOC_OUTPUT_ORDERS?
    Thanks GIRI

    Hi Giri,
    There is no direct provision to Read the Output type from the function module. But you can do this with the following Options.
    1) Find user Exit in PO Transaction while issuing the output. Export the output type from there and import it in your IDOC function module and then do you logic.
    2) Since you are going to Specify the Basic type and Extension in the partner profile you no need to worry about other partners. This extension will not trigger to the other partner and other output types.
    Let me know if you need any further details.
    Thanks,
    Venkat

  • Need of distribution model in IDOC triggering

    Hi,
    I have one question dat is it necessary to maintain distibution model in BD64 for outbound IDOCs or only maintaining partner profile in WE20 is mandatory.
    I have seen some cases in which distribution model is not maintained.
    Please let me know the cases in which we maintain distribution model
    Thanks in advance.

    hi,
    The distribution model describes the ALE message flow between logical systems u2013 that is, it determines which messages are distributed to which logical systems.
    For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model.
    please refer this blogs for more info:
    Data Ditribution Model BD64 config
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
    thanks ,

  • Custom Idoc triggered when material cost is changed

    Hi all,
    I have a requirement like this.
    1. When the cost data is changed the custom IDOC need to be genreated.
    2.We are using change pointers,but dont know we can track when cost details have changed for a prticular material..
    Regards

    Try Transaction POIM .
    Let me know if u have doubts .
    Regards,
    Vijay.

  • Relationship between the workflows what have been triggered frm parent workflow using container step

    Hi All,
    There is a scenario in CQ5.5 where "Workflow A" has container step to initiate another "Workflow B" from it. Now the requirement is to identity the Workflow A's instance ID in "Workflow B".
    Being quite unable to find any relationship between the workflows what have been triggered from parent workflow using container step.
    Could any one share the pointers for the same?
    Thanks in advanced.
    Regards,
    Saurav Jain
    7428081341

    Please do not keep reposting this.
    Those of us that answer questions here are volunteers ... not paid Oracle employees.
    If no one answered your question to your satisfaction it is either because they choose not to, don't know the answer, or because lacking a version number no one knows to what version you are referring.
    My recommendation is that you go to http://asktom.oracle.com where you will find extremely good explanations of cursor sharing.
    Thank you.

  • IDOC not getting triggered

    Im triggering an idoc IDOC_OUTPUT_ORDERS immediately when i create/change the PO
    However the idoc is getting generated when i change only certain fields.
    When i change other fields it does not get triggered.
    Why?
    -Dexter

    Hi Dexter,
      I hope these links might be useful to you.. refer all the links, you will get it..
    Idocs trigering
    Idocs Triggering!
    regarding Idoc triggering
    Idoc triggering
    Regards,
    Ahamed.

Maybe you are looking for