IDOC trigger

Hi all !
I have a scenario in which the IDoc has arrived at XI from an R/3.Now this Idoc is to go to another R/3.
On Idx 5 it shows me successful inbound and outbound transfer of IDocs.
But at the outbound it is not showing me the client of the R/3 system to which this idoc has gone.
I have a doubt that this idoc has not gone to the system which it should actually go to.
So how can I check to which system this idoc has gone
And how can i rectify and make this idoc go to the desired output R/3 system?
Also plz tell if Idocs can be transferred to and from non sap R/3 systems
Kindly reply
Thanx

HI,
It is bit possible to transfer IDOC from even NonSAP systems (provided those should be certified prtner to use IDOC)
see below link
Sending and Receiving IDOC from SAP to Non SAP system
HOWTO: Process IDocs from non-SAP sender
Please follow below steps to trace the IDOC,
Troubleshooting IDOC scenario
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
thanks
Swarup

Similar Messages

  • IDOC trigger using Z change pointers for standard SAP table

    For IDOC trigger, is using custom change pointers on standard SAP master data tables, a good idea? A seasoned abaper told me "it will mess with the standard" and further told to go with scheduled job.
    So, for example, say that my data for table T001K is updated via transports in PRD and I need to transfer this updated data via IDOC to an external system. Since there is no standard message type for this data, I will create a new one. Further, I will create a new change pointer for table T001K (it already has six fields with their data elements activated for Change Documents). Then I link the message type and the new change pointer. And so on an so forth. I have followed the procedure given here:SAP Tips: A to Z of Custom Change Pointer
    Now, the question is, will this be a good idea to capture data and trigger IDOC? Or a batch program with calls to standard FM to read CDHRD/CDPOS be a more suitable option.
    I need to know if a near instantaneous data transfer (and an effecient one as far as the system performance and reliability is concerned) can be acheived. If there is any other way of doing this, I am not aware of it!
    Any one has any input/experience on this?

    Hi Viktor,
    I think the batch program approach would be a good solution as the by this way you are taking matter into your own hands rather giving control to the SAP framework because you may have to test out the other approach as to how the standard SAP framework is behaving for custom change pointers.
    Thanks,
    Ravi

  • Customer Payment outbound IDOC trigger

    Dear All,
    I am working on one of our customer requirement to send Customer Payment data from SAP ECC 6.0 to their application using SAP PI 7.0
    I have created a customer Invoice (in Transaction Code FB70) without any reference document .
    Now I want to generate a Customer payment document on the top of Customer Invoice generated as mentioned above.
    Can any one please suggest the following:
    1) Can we generate Customer payment document in transaction FII0
    2) What are the mandatory parameters to generate Customer payment document.
    3) If I need to send this data to external application using IDOCs , so can i use Program RFFOEDI1 as suggested in other threads.
    what are the parameters needs to given to run the program?
    4) How to configure the our output type so whenever we generate a Customer payment document, an IDOC should be genarated.
    Also please confirm if I can use IDOC PAYEXT with basic type PEXR2001 or should I go for some other IDOC.
    Best Regards
    Honey

    Hi...
    1.  First you need to create Invoice (TCode -- FB60)
          Document Number will get generated.
      2. For Automatic Payment Program (Tcode-F110)
        Fill all the details which are mandatory.
       Then go to WE02, check if idoc got genearted.
      And then you can trigger the idoc.
      You can use PAYEXT with basic type PEXR2002
    Regards,
    Leela

  • Regarding output type and idoc trigger issue

    Hi
    i need to copy pgi quantity into sales order quantity for that i write a code into user exit MV50AFZ1. code is working fine but
    output type and idoc is not trigger due to this. In this exit to update sales order quantity i used bapi *BAPI_SALESORDER_CHANGE . can anyone tell me why o/p type and idoc not trigger ,what is the reason and what is the solution for this?
    Thanks
    Dinesh

    Hi Dinesh,
    Did you activate the enhancement for user exit ?
    Did you check if the output type is configured correctly ?
    Put a debugging point and see if control is coming there.
    Regards,
    Nisha Vengal.

  • IDOC trigger for changes in condition records

    Hi Guru's,
    I want to trigger IDOC every time I create a condition record and every change in condition record. can you suggest me how to trigger IDOC COND_A01 in above scenarios.
    Thanks in advance.
    Suresh

    Oh, price condition.
    In Vk13, there is a icon "Condition Information", narrow your results in the selction criteria. In output, there is a 'Send Condition" icon. then enter your message type and logical system. After that, you can use WE02 to view the idocs.
    Please revert if answered.

  • IDoc Trigger Immediately

    Hi gurus. I just want to ask if for example an XI, BizTalk or any EAI applications send an IDoc to an SAP system and in the inbound partner profile it was set to TRIGGER IMMEDIATELY, does the EAI application waits until the process is completed (e.g the creation of Sales Order) before getting out of the SAP system?

    once idoc is received to SAP R/3 system,it will process immediately ( I mean idoc status will not be 64 ,it will be like application document is posted.
    TRIGGER IMMEDIATELY is related to SAP r/3 and it does not care about other system.
    if you choose background progra check box,then status will have 64 ,then we need run manually by using RBDAPP01 program to get status 53.
    hope you got my point

  • Idoc trigger for inventory updates.

    Hi ,
    we want to send our inventory update for a specific storage type to a third party system. when ever  the quantity in a particular bins of the storage type gets updated an IDoc should e created to send the remaining quantity to a third party system. the triggers include any goods movements (PGI, goods issues, goods receipts). So my question is where do I write the trigger. Do i have to write the trigger against each transaction that will impact in goods movements or is there any way that I could write it at a higher level  so every goods movement thats happening in the SAP system will check whether it has to create an IDOC or not.

    what happens if I use MB1A, MB1B, MB1C?
    what happens if I dont post material document and just perform bin to bin transfer.
    I want the the Inventoy level at a particular bin when ever there is a change to in the quantity.
    how can I achieve this??
    Edited by: deepu p on Mar 17, 2011 2:18 PM

  • IDoc trigger at customer creation

    Dear Gurus,
    I have developed a custom IDoc. Now i want to send this customer master IDoc to the legcy system whenver a new customer is created or existing customer is modified.Ive sent IDoc from BD12,it is working fine,now i want to send it at runtime.Is there any customizing part required to trigger the IDoc at creation if the customer master record ???
    please help me out.
    Reward points for helpful answers.
    Cheers,
    Deepthee Kasal

    Hi Deepthee
    Please correct me.
    U need that a idoc will be created in one system and this idoc will go to legacy system. Now are these both systems SAP. Or which is sap and which not.
    If the system is non sap and legacy is sap, then a XML file is sent from non sap and this is converted to idoc (DEBMAS) and processed in SAP and created or change customer master.
    Now if there is some sap system and it will create idoc after cration of customer and send to non sap to update. SAP doesnt provide o/p determination on customer masters. Here wyou will define a new idoc type use copy of DEBMAS and then create a idoc in sap for this and convert to XML and sent to legacy.
    Hope this helps
    Kind Regards
    Sandeep

  • Outbound IDoc trigger from TO

    I am developing an outbound interface with third party MES system. I have to send an outbound IDoc based on Destination storage Type =xyz in TO. How to achieve this?

    if you are planning to use the standard SAP then you have to set up the link in between your warehouse and External system(MES) and under interface control you need to specify on what condition (e.g. source storage type, destination storage type and movement type) you want to trigger the IDoc, or if you are not planning to use the standard way then then you have to make a custom table with logical system detail combination of source and destination storage type and write your own code in user exit (MWMTO001 or MWMTO002) to trigger an IDoc upon  creation or  successful confirmation of the Transfer order based on your requirement as this is not clear from your thread
    standard SAP link Sending Transfer Orders - IDoc Interface: EDI Application Scenarios (BC-SRV-EDI) - SAP Library

  • Invoice IDOC trigger only for particular bill to party

    Hi,
    I have a requirement to trigger the idoc once the invoice is saved. But the condition here is that whenever the bill to party is u2018DELLu2019 then only the idoc should get triggered.
    Can anyone help me out how can I proceed this and especially where can I check this condition?.
    Regards,
    Prabu

    Hi,
    Thanks for your input. Here i have one more check like as follows.
    First i have to check whether the partner of the document is DELL and if so, then should check the preceding document order type.
    If that is also DELL, then only the idoc  should get triggerred. I have the logic to find the partner. But strucking up where should i go and write the code?.
    Can any one help me on this?.
    Regards,
    Prabu

  • Problem in INVOIC02 Idoc trigger for Customer

    We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to the customer.
    We have configured the output type ZINV in NACE and are using while creating the invoice.
    This Customer is configured in the KU  partner types thriugh WE20.
    But when we try to create the invoice from VF03 and save for the output type then IDOC doesnt get trigerred.
    Whats missing ?
    Regards.

    Hi Amber,
    Then you click enter button.It is asking to create object with that include name ZXBC425G01U01 in a pop-up.You  should select YES option.It will ask package . Give the package name and save.Then include program is created and allowed you to write your own code.
    Thanks,
    Prasad GVK.

  • IDoc Trigger time

    Hi all;
    I have a IDocXIODS scenario .
    I want to map in the time the IDoc is triggered through change pointer to the ODS table.
    Is there a way to get in this time .
    Thanks
    Mudit

    Mudit,
    There are 2 options
    1. Use a user exit and populate the value in any of the IDOC filed that is unused.
    2. Use Date function in Message Mapping to get the system time. This option will only give you the time the mapping is done and not the time the IDOC is triggered from R/3.
    Regards,
    Jai Shankar

  • Workflow trigger an idoc

    HI
    How trigger a idoc from a workflow?????
    Hi
    idoc trigger from a workflow.please suggest.
    example like po change..
    Edited by: Abhijit Paul on Jun 26, 2009 8:42 AM

    Hi,
    You can follow following steps.
    1) Create a Z business object inherited from BUS2012.
    2) Create a Z-method in will have to create a method in your newly created business object.
        This method will have logic to create and send the idocs for PO. Delegate the business object so that you can call the method from SUPERTYPE in workflow.
    3) Create a workflow with triggering Event as Change of PO.
        This workflow will have a single step task which will call the Z method of your business object.If you have done the delegation then you can call the method using BUS2012 object type itself.
    4)  You will have to go in Tcode SWEC as mentioned in the post above.
        There you will have to do an Event linkage for change documents.
        Make an entry for EINKBELEG Bor Object ZBUS2012 or BUS2012, Event CHANGED and select on Change option.
    5) Change the PO and check if the event is getting triggered or not. Also if the method used to create and send idoc is correctly been called.
    Hope it explains the steps you need to follow.
    In case of any issues please let me know.
    KR Jaideep,

  • Idoc Acknowledgement

    Hi all,
    I am having small doubt regarding the setting acknowledgement to Idoc while doing Idoc to File scenario.
    Where we can set the ack. to IDoc and where we can see the ack. in XI whether ack. is already set to IDoc.
    Is this necesary to load meta data while IDOc is acting as receiver. What information contains the meta data.
    How it can identify the meta data First time when sending IDoc to XI in IDoc to File
    scenario?
    regards,
    Sridhar

    Hi Sridhar,
    The below link contains everything about IDOC acknowledgments
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    IDOC Acknowlegdments are enabled by default. You can disable by going to Transaction SE11 and do the lookup for “IDXNOALE” database table and clear the values for NEG and TYPE fields for your message type.
    Yes, it is necessary to load the metadata and this gets automatically loaded when you run your first transaction or idoc trigger from SAP.
    How to identify the meta data first time?
    Goto IDX2 and see if your message type is listed.
    Hope this helps,
    Regards,
    Vinayak Kamath

  • Sales Process And EDI Idocs Integration

    Hi Friends,,
    Good Day To You All !!!!
    Please enhance my knowledge with your valuable reply.
    I am new to ABAP and would like to learn the following .
    1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
    2 . Idocs -  Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
    I need the above information to get a clear picture of the process taking below.  
    What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
    And the idocs update the corresponding status in Siebel .
    I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
    Thanks.
    With regards,
    Learner .
    Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

    Hello,
             If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
    1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
    2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
    3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
                The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
    1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
    2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
         All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
    3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
    4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
    5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
    Hope it was clear enough.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

Maybe you are looking for