IDOC to EDI

Hi all,
I am working on Idoc to EDI ANSI X12 Invoice 810 scenario, I created a receiver communication channel with File adapter and included those modules. But I am not sure is there any other additional module parameter that needs to be specified other than the once that are mentioned below.
Processing sequence:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
and
Module configuration:
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_X2E_ANSIX12_810_V4010.
I am getting the following error in receiver communication channel,
"Message processing failed. Cause: java.lang.Exception: Cannot cast to XI message. Reason: BIC module error: Message which was recieved from module processor was null"
But the file in getting generated in the target directory as an xml file, actually the file has to be in EDI format.
Please let me know whether the module is not properly configured or the File adapter does not handle the IDOC to EDI conversion eventhough the module used does the conversion.
Regards,
Nithiyanandam

Hi,
Seeburger tool will not fail to conver the data into file format,they all are already predefined mappings and ANSI X12 is a common mapping used by most of the users and the module parameters which u have specified i dont find any thing more u have to give.
Check ur mapping which u have done and also check all the setting onces
any way iam giving some links on Seeburger check them.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards,
phani
Reward points if Helpful

Similar Messages

  • Tax with the help of idoc and EDI

    Dear gurus,
    how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

    Hi Amit,
         I do not understand how a non-sap system having an idoc adapte?
    Do you mean the non-sap system has the ability to understand the IDOC files?
    If yes, then your scenario is typically a IDOC-to File scenario.
    Read this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
    Regards,
    Ravi

  • Urgent: IDOC to EDI with SAP Conversion Agent

    Hi,
    I have a requiremetn like IDOC to EDI ( Gentran ) scenario.
    We have decided to use SAP Conversion Agent to deal the same.
    Can anybody share their experiences on this kind of scenario.
    Needed step by step information to complete would be appreciated with the full of points.
    Cheers.,
    E

    check with tis may helpful for you
    http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
    Regds
    Abhishek

  • Problem with mapping [Idoc to EDI]

    Hi experts,
    i am facing a new problem in my mapping (idoc to edi scenario)
    my target is as follow:
    InvoiceDME
    >Invoice 1..1
    >>InvoiceHeader 1..1
    >>>IncotermsCode 1..1
    My Idoc is as follow:
    IDOC
    >E1EDK17 0..20
    >>QUALF
    >>LKOND
    >>LKTEXT
    There can be 2 scenarios in my source:
    1st:
    IDOC
    >E1EDK17
    >>QUALF = 001
    >>LKOND = lkond001
    >>LKTEXT
    2nd:
    IDOC
    >E1EDK17
    >>QUALF = 001
    >>LKOND = lkond001
    >>LKTEXT
    >E1EDK17
    >>QUALF = 002
    >>LKOND = lkond002
    >>LKTEXT = lktext002
    If QUALF=002 then I have to take both values of LKOND and LKTEXT and map them to incotermcode
    else if qualf=001 alone, then map LKOND to incotermcode
    my mapping is as follow:
    http://www.flickr.com/photos/30317046@N05/2862446903/
    as you can see, the problem is if i am in my second scenario, i get the wrong value in incotercode (lkond001 instead of the concatenate of LKOND and LKTEXT for QUALF = 002)
    Do you have any idea how I can solve this??
    Thanks a lot,
    Regards,
    Jamal

    Actually i used java mapping:
        //write your code here
    try
         String returnString = "";
         for (int i = 0; i < QUALF.length; i++)
              if (("002".equals(QUALF<i>.trim())))
                   returnString = returnString +" "+ LKOND<i> +" "+ LKTEXT<i>;
                   result.addValue(returnString);                   
    catch(Exception e)
         e.printStackTrace();
    and the condition on the 'count' of QUALF (if = 2 then else)
    Thanks,
    Regards,
    Jamal

  • Facing Problem in IDOC to EDI FLAT File Scenario

    Hi,
    I am working on a scenario IDOC to EDI FLAT File. For this I have used ABAP mapping.
    The problem i am facing is that the EDI FILE contains the segment name as E1EDK01 for eg. while I need the name as per the latest segment definiton released. I have also tried this using File port and it gives the required segment names in file.  But we dont have to use File ports. Please suggest me if something is missing in PI Abap stack ?? Why I am not getting the segments name as per latest segment definition mainatined in R3.
    Thanks
    Neha

    Hi Neha,
                   Please check the segment name in sxmb_moni. Is this showing new value or the old value?
    If SXMB_MONI shows old value then the source SAP (R/3) system which is sending the idoc may not have released the segment after changing the name. You need to ensure that the idoc segment has been released properly. Then re-import the iodc into PI server again. Finally delete entry of the iodc structure in idx2 transaction, no need to re-import the idoc structute again in idx2, since once you run the scenario the metadata automatically gets imported.
    regards
    Anupam

  • IDOC to EDI scenario

    Dear All,
    need your help on how to configure and deploy a scenario for a IDOC to EDI (856)  .  I believe this is like "IDoc to X12 - > X12 to EDI" using AS2 adapter.  BASIS has configured the B2B addon installation and I am not sure about the EDI part in this scenario..
    can you please inform what that the steps (A to Z) needs to be followed and would be great if example scenarios can be uploaded .
    Thanks
    Fernando

    Hi Fernando,
    I guess you're referring to this thread: IDOC to EDI scenario
    For that reason, please do close this one.
    Thank you.
    Dimitri

  • IDOC to EDI Seeburger Mapping Issue

    Hi,
    I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
    As per my little knowledge i can understand that i need two step mapping:
    1) IDOC XML to EDI XML
    2) EDI XML to EDI
    Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
    Also i dont know how i can map the 2nd mapping.
    when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
    msg_PAYEXT_UN_D96A.xml
    msg_XML_PAYEXT_UN_D96A.xml
    XML_PAYEXT_UN_D96A.xsd
    Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
    Please experts reply soon as it is delaying my project
    Regards,
    Shradha

    Shradha,
    You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
    You can have a look whether PAYEXT is there and would be useful
    To start with
    1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
    2. You should also liase with your business partners to prepare an business rules and other conditions.
    3.Also decide whether you are going to deliver it via AS2 communication or via VAN
    4. Accordingly you need to configure the seeburger adapters.
    5.The mappings provided to you are from XML to EDI and EDI to XML which is a second  stage automatically done by seeburger once you specify the module steps in the comms channel.
    I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
    Regards
    Krish

  • IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

    Hi All,
    IDOC (Invoice) to EDI file scenario without Seeburger
    Pls let me know if anybody have blogs for the same
    EDI file to IDOC (Orders) scenario without Seeburger
    Pls let me know if anybody have blogs for the same
    Regards

    Hi Rachit,
    >>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
    Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
    Also java code for IDoc to EDI have some problems:
    1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
    2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
    All the best
    Regards
    Suraj

  • Idoc to edi scenarios (mapping help is required)

    hi expects ,
        i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
    INPUT IDOC :
                        Name                         M/C     Min Use      Max Use        Description                                                                               
    INPUT*                                              M               1           1                                                                               
    Record EDI_DC40*                                 C               0           1                       Control Record                                                                               
    Record E2EDK01*                                  C               0           1                       Document Header General Data                                                                 
         Record E2EDK14*                                  C               0          12                       Header Organizational Data                                                                   
         Record E2EDK03*                                  C               0          10                       Header Date Segment                                                                               
    Record TEMP_DATE*                                C               0           1                       Temporary Date Segment                                                                       
         Record DEL_DATE*                                 C               0           1                       Temporary Date Segment                                                                       
         Record E2EDK04*                                  C               0          10                       Header Taxes                                                                               
    Record E2EDK05*                                  C               0          16                       Header Conditions                                                                               
    Record E2EDKA1*                                  C               0       99999                       Header Partner Info                                                                               
    Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info                                                                               
    Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info                                                                               
    Record TEMP_PAYER*                               C               0           1                       Payer Info                                                                               
    Record TEMP_CARRIER*                             C               0           1                       Carrier Info                                                                               
    Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info                                                                       
         Record TEMP_NOTIFY*                              C               0           1                       Notify Info                                                                               
    Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info                                                                               
    Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info                                                                               
    Record TEMP_CONSIGNEE*                           C               0           1                       Consignee                                                                               
    Record TEMP_SHIPPER_INFO*                        C               0           1                                                                               
    Record E2EDK02*                                  C               0          10                       Header Reference Data                                                                        
         Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02                                                                               
    Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING                                                                               
    Record E2EDK17*                                  C               0         999                       Header Terms of Delivery                                                                     
         Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms                                                                    
         Record E2EDK18*                                  C               0          99                       Header Terms of Payment                                                                      
         Record TEMP_TERMS*                               C               0           1                                                                               
    Record E2EDK35*                                  C               0          10                       Additional Data                                                                               
    Group E2EDKT1:2*       
    OUTPUT FIELD:
    Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION                                       
         Segment B2A*                                     C               0           1                       SET PURPOSE                                                                               
    Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION                                                                     
         Segment CUR*                                     C               0           1                       CURRENCY                                                                               
    Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE                                                         
         Group DTM_GROUP*                                 C               0           1                                                                               
    Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE                                                                               
    Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE                                                                               
    Segment DTM:3*

    Hi,
    To do the mapping,,,,even you can go for graphical mapping....
    But some of the context handling issues you need to deal with,
    like....
    1.Never map set context of source fields to element level but Segment level.
    2. Always you need to check for qualifiers while mapping it to Traget field.
    Thanks & Regards
    Akshay.
    Dont Forget TO Give Points.

  • Mapping from PEXR2002 iDoc to EDI 820

    We are planning to use XI to map from the payment advice (PEXR2002) iDoc to EDI 820. 
    We have 2 options: (1) Use XI and an EDI adapter (e.g. Seeburger); or (2) Use XI's own mapping functionality.
    If you have done iDoc to EDI mapping with either of the above 2 options, please briefly advise about your experiences and how much efforts it took to develop the mapping.
    Thank-you
    Bac Quan

    Hi Bac,
    Although it is possible to create an EDI message in an XI mapping (or XSLT), this is not very nice.  The use of an EDI adapter (iWay or SeeBurger) is strongly recommended.
    The other way around (rom EDI to XML) is hardly feasiable without an EDI adapter.  Although I haven't worked the SeeBurger adapter, it looks quite nice.
    Kind regards, Guy Crets

  • IDOC to EDI Scenario using Seeburger....

    Hi Experts,
    On the Scenario IDOC to EDI when will I use As2 adapters or SFTP adapters of seeburger or just a simple FIle adapter?
    and any idea what are the modules I need to import on my comm channel using file adapter?
    Thanks.

    Hello
    Check this blog: /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    Regards
    Mark

  • Idoc using EDI for purchase order

    hi all,
    could someone explain me all  the steps required in generating purchase order idoc  using EDI butnot using ALE.
    i want all the steps to be in detail.
    thanks in advance
    suma sailaja pvn

    EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
    EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
    The difference between ALE and EDI process flows occurs at the communication level. The EDI process transmits IDocs to an EDI subsystem using flat file format. The ALE process transmits IDocs to an SAP system via memory, using asynchronous communication.
    Check the following links
    How Can I transfer invoice details to customer through IDOC in EDI
    Re: IDOC Types and their equivalent messages in EDIFACT and ANSI X12
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
    http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
    Reward Points if useful.

  • Functional Specs for Mapping Idocs to EDI

    Hello Friends ..
    Am new to world of EDI...
    can any one explain ..wat do u mean by devolping functional specs for mapping IDocs to EDI..
    If you can provide me with examples or if you guys can suggest any site where i can browse some material about EDI..i wud really appreciate...
    Best Regards

    Hi Rohan,
    >>>do u mean by devolping functional specs for mapping IDocs to EDI..
    you have to know which idoc fields you have to map to EDI message fields
    take a look at those links:
    they will show how do you map different IDOC message types to EDI messages
    <b>IDOC - EDI mappings:</b>
    http://www.sapgenie.com/sapedi/mapping.htm
    <b>Analysis of the compatibility of EDIFACT messages in the form of SIMPL-EDI with the IDoc Interface:</b>
    http://www.sapgenie.com/sapgenie/docs/SIMPL-EDI-E_ORDERS.doc
    Regards,
    michal

  • Idoc  and  EDI  for FI

    Hi all,
                 Can anyoune help me out with the topics.
    Idoc and EDI and how this are related to  FI.
    I was looking for some scenario.
    How to process inbound idoc and outbound idoc.
    Thanks advance for help.
    Regards,
    sha

    Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
    For idocs in delivery processing:
    http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
    LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

  • IDOC to EDI Conversion

    Hi, I am New to EDI-IDocs,We have a requirement over here to send the iDocs from SAP to Non-SAP sys(JCAPS).
    Need step-by-step details to convert the iDoc to  EDI format.
    Helpfull Answers will b Rewarded.
    Regards
    Giridhar Reddy

    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 u201CThe table is cross-client (see Help for further info)u201D. 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 u201CThe table is cross-client (see Help for further info)u201D. 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
    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.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    u2022 Create a Customer Distribution Model (CDM);
    u2022 Add appropriate message types and filters to the CDM;
    u2022 Generate outbound partner profiles;
    u2022 Distribute the CDM to the receiving systems; and
    u2022 Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC u2013 Creating IDoc Type from Change Pointers
    RSEOUT00 u2013 Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    There are two filtering in IDoc.
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Please check this link for more information.
    http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
    Regards,
    Shiva Kumar

Maybe you are looking for

  • Upgrade from 11i to r12 application servers with Discoverer 10g

    Hello, one and all. I have recently upgraded from 11i to r12 Oracle financial application server, after much patching and testing we finally came to the Discoverer application server. Most workbooks open fine, however it seems that some of them (abou

  • HP 6510 not printing black ink

    I bought a new black ink cartridge a few weeks ago, installed it, but I hadn't had a chance to print anything until tonight.  It worked before I installed the new cartridge, and now it doesn't print black ink. (It is an HP cartridge)  I have done all

  • Duplex not recognised when sharing HP 7210 All-in-one using Remote Desktop

    The HP 7210 is installed on a Windows 8/64 PC called Harmony. Duplex unit is correctly detected and a logged on Harmony user can print duplex. MSTSC is set up with printer sharing and a connection toa remote Windows 7/64 PC called Gerald. A user logg

  • How do I get my ipad and iphone to access wifi after it was dropped

    My Ipad2 and Iphone dropped my wifi connection and I can't get it to wotk again

  • Please help: variable headings problem

    hello, trying to get my headings on each page of my rpt, to change if it is a new location, new company, etc. when put in WORD header/footer, it does not alter, it stays with first value from my XML. When try put in for each block, only prints when n