Best Way to Debug an Inbound IDoc

Hi
As previous posts suggest I am having trouble with IDoc PORDCR101 message type pordcr   bapi_po_create
i input
comp code 3000
doctype      NB
vender        58121
purchorg     3000
purchgrp     000
doc date     01112007
item           0010
material     scw1212
qty            0001000.000
currency    USD
scheduleitem  0010
deldate           01/18/2007
qty                 0001000
i put this exact info in se37 with bapi_po_create
I can successfully create a new po
now i try to do the same thing in we19 standard inbound
using idoc pordcr101
each time i try i get status 51 enter purchasing org
what is the best way to debug this thing so that i can see what is going on
i am entering the purchasing org and for some reason it does not see it
what can i do in the way of debugging?????
HELP!!!!!!

Janice,
conversion-exit routines are used when the contents of a screen field(SAP GUI) are converted from display format to SAP-internal format and vice versa.
--Archana

Similar Messages

  • Where to put break point when debugging the inbound IDOC processing

    Hi, Dear Experts,
    If IDOC has error and want to debug, which program or function module  to put break point when debugging the inbound IDOC processing
    Thank you so much!
    Helen

    It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
    If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

  • Best way to debug KDE process crashes

    I've got a relatively fresh install of ARCH with KDE running.  However every time I reboot and log in I immediately get 2 pop-ups stating that KMix and a KDE Deamon closed unexpectedly.  The "executable" for both is listed as kdenitit4.  I'm assuming that is the app that started the failed process?  Checking the PIDs for each in the process list before closing the pop-ups show kmix and kded4 as the actual stopped processes.
    Question then, what is the best way to debug this.  I know there are system logs but I'm really not that familiar with where or what to look for and really want to learn and also fix the crashes :-)   What is the best way to start.  Thanks,
    John.........

    Here is some of the lines around the 2 KCrash errors:
    Known subscriber "AkonadiAgentServer" subscribes again
    void Akonadi::NotificationSource::addClientServiceName(const QString&) Notification source "AkonadiAgentServer" now serving: (":1.48", ":1.47")
    Known subscriber "AkonadiAgentServer" subscribes again
    void Akonadi::NotificationSource::addClientServiceName(const QString&) Notification source "AkonadiAgentServer" now serving: (":1.48", ":1.47", ":1.49")
    Database "akonadi" opened using driver "QMYSQL"
    Database "akonadi" opened using driver "QMYSQL"
    Known subscriber "AkonadiAgentServer" subscribes again
    void Akonadi::NotificationSource::addClientServiceName(const QString&) Notification source "AkonadiAgentServer" now serving: (":1.48", ":1.47", ":1.49", ":1.46")
    plasma-desktop(889)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    >> KCrash: Attempting to start /usr/bin/kded4 from kdeinit
    knotify(887)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.NoReply", "Message did not receive a reply (timeout by message bus)")
    korgac(944)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "The name org.kde.kded was not provided by any .service files"
    knotify(887)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded was not provided by any .service files")
    QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    kdeinit4: hcontrol.c:764: snd_hctl_handle_event: Assertion `elem' failed.
    QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    >> KCrash: Application 'kded4' crashing...
    KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
    [0x2853108] main input error: ES_OUT_RESET_PCR called
    KCrash: Application 'kmix' crashing...
    KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
    Known subscriber "akonadi_maildispatcher_agent" subscribes again
    Known subscriber "akonadi_maildispatcher_agent" subscribes again
    Agent instance created in separate process.
    I marked the original two KCrash's with >> to make them easier to find.  Looking a few lines down from the 2nd one I also see a KCrash for 'kmix' which is also part of the problem.  Don't really see anything else interesting.  Open to ideas.  Thanks,
    John...........

  • The best way to debug a deployment

    I have an application written in JDeveloper and it runs like a dream. The problem is that when I deploy it to Oracle App Server, I cant get it to run. I am using the JDeveloper deployment profile for creating my jars/wars/ears. I have build many of these in the past and they all work well. There is obviously something I am doing wrong with this one. How can I go about debugging my deployment. I've been stuck on this one for a long time and need to make some progress. Please help.
    Thanks,
    Cory

    In my personal opinion there is no "best" way, but here's what I always do:
    1. Check main settings
    2. Check main logfiles
    3. Check database
    First you have to check the main settings, like data sources, OC4J-settings and JVM-settings. A type-o in your settings could kill your deployment. Also, if you are using jms, make sure that the correct topics are registered in jms.xml If all is o.k., then proceed to step 2.
    Secondly you should check the standard out for the OC4J where you are deploying the application. This is located at $ORACLE_HOME/opmn/logs/$OC4J_NAME_default_island_1. You can also redirect the standard out by setting de -out parameter in the server settings. This should also contain some helpfull clues (like missing references to property files, typ-o's, wrong classpath, etc.)
    Finally if all this is OK and you application still isn't starting (but by then it is deployed) you should check the state of the database. It should be up and running, and containing the correct version of the application's datamodel. Removing rows from quartz tabels (if used) also helps while redeploying.
    This is roughly my starting debugging route. Does this give you any pointers?

  • Threading issues - Best way to debug

    Hey everyone... I have a small server program that I wrote in Java. Its module based where each thread that is created runs through a list of modules and returns the output. It works just fine and I am doing a little stress test using Siege. I set it up running 50 concurrent users with no delay and take millions of requests with no errors at all.
    However, when I move it up to 125 concurrent users, I start getting NullPointerExceptions on a fairly routine basis (inside of one of the modules). The server is still running with no issues, just with that many users it appears to have a bug.
    I was wondering what the best way figure out why this would be happening. Or is this kind of thing to be expected and I should just implement some method of throttling for the threads. I plan to do that eventually, just trying to get the bugs out first.
    Thanks in advance!

    I think you are seeing the NPE concurrent scenario because of the assumptions you code is making about how JVM should behave. You code may be making assumption of "happens-before" pattern which may seem valid when you look at the code, but in fact are not.
    Take a look at this presentation that outlines the Java Memory model and defines the contract between concurrent programs and JVM.
    http://developers.sun.com/learning/javaoneonline/j1sessn.jsp?sessn=TS-1630&yr=2006&track=coreplatform
    Throttling the method is a bad idea (and a cop out). How would you arrive at the optimal number threads that can safely access your program ? Will your code be portable when it is deployed on a computer with different computing power than what you are testing on ?
    Hope this helps.
    -Prashant

  • Best Way to debug Javascript

    Hi,
    I have a random bug in Javascript which locks the loaded page
    sometimes when i executed the pages outside Dreamweaver. What is
    the best way to denug?
    Thanks.

    Found that microsoft provides a script debugger.. 
    Thanks..

  • Receiver port missing in inbound idoc

    Hi All,
    I am posting idocs from XI to R/3. All the ALE settings have been done correctly. Idocs were being posted to R/3 successfully, however suddenly the idocs started failing in R/3 with error: EDI: Partner profile inbound not available
    When i checked the control record for the errored idocs i found that the receiver port is missing. I am not sure why this is happening as in the idoc adapter we have provided this and also the idocs were being posted successfully with the same setting.
    Pls help to find the root cause for this problem.
    Further what would be the best way to reprocess these failed idocs? The number is huge around - 30,000 hence manual processing through we19 is not possible. Also BD87 cannot be used as i need to edit the idoc to add the receiver port information before reprocessing.
    Kindly suggest. Any help in this regards would be welcome.
    Thanks
    Anand Chavan

    hi
    Go thru  the below blogs
    check the partner profile settings
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm     
    Idocu2019s not  posted in the receiver SAP Systemsu2026.
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133     
    Troubleshooting File-to-IDOC Scenario in XI.          
    Troubleshooting  File-to-IDOC Scenario in XI.     
    reward points if helpfull
    regards
    kummari

  • Inbound Idocs: Queue Processing (non-stop queue?)

    Hi everyone!
    I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
    There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
    I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
    I'm using PI 7.0 SP30.
    Thank you in advance!

    First, this is not serialization, it's the queuing design EOIO... they are not the same.
    So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
    Basically the serialization is not a good fit for these requirements.
    Here is one solution:
    1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
    2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
    3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
    4- There is  standard report that you have to schedule and restart the queues
    5- Reprocess the IDOCs from steps 2
    The enemy of EOIO design is the user locks in the target system...
    Cheers,
    Fouad

  • Inbound idoc number

    Hi,
    Is there any way to get the inbound idoc number which created the sales order in the system.
    I have the sales order no. form that i want know the inbound idoc number which created this sales order.
    I am looking for any FM or Tables.
    Thanks,
    Patil

    Hi..
    Table EDID4 stores the Data records of an IDOC.
    You can search for SDATA field to get the Sales doc no.
    Try this Sample code
    report ztest1.
    tablEs edid4.
    data : it_data type table of edid4 with header line.
    PARAMETERS : P_MATNR TYPE MARA-MATNR DEFAULT '100-100'.
    DATA : V_pattern type string.
    CONCATENATE '%' P_MATNR '%' INTO V_PATTERN.
    SELECT   * FROM EDID4 into  table it_data
      WHERE  
      segnam = 'E1EDK01'  "To check the Segment name
      and  SDATA LIKE V_PATTERN
    LOOP AT IT_DATA. 
      WRITE: IT_dATA-DOCNUM.
    ENDLOOP.
    <b>Reward if Helpful</b>

  • How to start WF on inbound IDOC?

    Hi,
    the spec is to on every inbound IDOC to trigger an WF.
    If the IDOC has an error it works fine, but if its ok i don't konw how to catch it.
    Thanks in advance to all

    Hi,
    Try this way:
    1. For inbound IDoc processing, the event triggered is PROCESSSTATEREACHED from BOR IDOC.
    2. Create your workflow to act upon this event. You can refer to standard task TS30200090.
    3. Don't forget to create the event type linkage SWETYPV between the event and your workflow.
    Regards,
    Lim...
    Edited by: Ruslim Chang on Mar 5, 2009 2:11 AM

  • Inbound IDoc using LSMW

    Hi..
    I am trying To Upload customer master data using LSMW with IDOc.
    I am debugging the Inbound IDoc Using BD87 and INPUT_METHOD = 'A'
    One segment E1KNB1M data is not passed to transaction 'XD01'  due that my company code data is not updated
    Pls tell me how to pass segment E1KNB1M data to transaction.
    I am using Message type :  /SAPSLL/DEBMAS_SLL
               Idoc type    :  Debmas03
            Function Module  : IDOC_INPUT_DEBITOR

    Hi Rishi,
         Thanks for the document. But the document mainly concentrates on LSMW(I'm aware of generic LSMW with BDC), it doesn't explain the inbound IDoc, segment merging, Creation of partner function or Message and Basic types WRT inbound IDoc. Please send any document with that relevance.
    Kiran

  • Testing Inbound Idocs

    Hi All!
    I am trying to fix an inbound Idoc program that is erroring in our testing environment with a REALLY big IDoc.  I need to move this IDoc to our development environment in order to be able to accurately fix the program.
    Is there any way to move an inbound IDoc from one environment to another without manually re-creating it or having to create an outbound IDoc process of some sort?
    Help is MUCH appreciated - thanks!
    Abby

    Try out this
    On the source system
    Go to WE19 - > IDoc -> Test Inbound IDoc ->Inbound File
    Here enter application server path like
    /appl/interfaces/MDDC/MLGA01
    Also Uncheck the check box Start IDoc inbound processing of file imm.
    On the target system
    Go to WE16
    Give the same application server file name in Directory + File name
    In Port give EDIPORT  and run it.  
    This will create an IDoc
    Regards
    Kesava
    Message was edited by:
            Kesava Chandra Rao

  • Reg: inbound idoc

    hi all,
    i got a task related to posting of idoc from particular vendor.
    but they didn't gave the idoc(ORDRSP) number for the vendor .i searched thro(we02) the vendor number and partner type it gives no idocs selected . is any other way to find the inbound idoc?
    please give me suggestion on this.

    Hi Sukumar,
    Did you search WE02 or WE05 with the following selections?
    Enter Direction as "2" and Logical message as "ORDRSP" and creation date accordingly. This will give you all inbound idoc's pertaining to ORDRSP with the creation date mentioned. Pick up the IDOC relevant to you and post it using WE19.
    Hope this will help you.
    Let the forum know if you need any help.
    Regards,
    Vivek
    PS: Award points if helpful

  • What is best way to connect a non-sap sys sending  xml idocs to SAP system

    Hi Can some one please guide as to what will be the best approach in connecting a NON SAP system to a SAP system.
    The non sap system should not be connected to access real time data,it does not support RFC,it can send data in IDOC xml format and i think in teaxt files also.Also I dont think there is any EDI subsystem in place.
    There has to be a periodic upload of material data from SAP /stock status/
    then there will be incoming data into SAP for sales order/purchase order etc
    What would be the best way to connect the two systems,IDOCs with partial EDI looks the best way ,but I am confused as to how will the XML IDOC be converted to normal IDOC and viceversa,how to handle the event triggering mechanism.
    If someone has experience in such a scenario ,please help.
    There is a option to update the database of the application through SQL also...

    Hi,
    Check this link.
    Web Services from Function Module
    it might help u.
    Thanks.

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    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
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

Maybe you are looking for