XML--- XI--- Flatfile---- GENTRAN---- EDI

Hi,
we are planning to implement xml to EDI scenario but its no possible just with XI without any EDI adapter.
so planning to get xml file with sender File adapter and then give out a flatfile with receiver file adapter using FCC and then GENTRAN picks the file from there and give out EDI structure to send out to partners.
we can buy a Seeburger adapter but we have GENTRAN in place ,so thinking of use the existing GENTRAN subsystem.
I am just wondering how far this solution is possible?for me I think its sensible but not sure how far its going to work in practical.so I want to make sure this is going to work before I start any development.
any comments please.

Babu,
I won't think any issues techinally in ur scenario development. But the problem is involving two EAI Tools in order to achieve single solution. Anyhow if its decided by the business team then there is no issues.
Converting XML to flat file can be done by XI -
Do u think any issues will occur here.
Converting Flatfile to EDI using GENTRAN -- Do u think any issues will occur here.
Where do u think its not possible practically, can u be lil more specific.
Best regards.
raj.

Similar Messages

  • Script needed at OS level to Convert XML to FlatFile

    Hi All,
    Can any one providde me Script to Convert XML to FlatFile at OS Level(Windows Based script).I'd thankful for your suggestions..
    Thanks
    Pullarao

    Hi !!
    You can execute a Unix script running in the XI server from the File communication channel. Ie. if you want to do something which was not part of XI adapter configuation , then you can make use of external unix script and you can execute those from the XI.
    For this, write a unix script and place in the XI OS level provided that path is accessible from PI Channel.
    E.g
    So u can use this in either Sender Channel to modify the data before it reaches into the Integration Server or in Receiver channel it is generally used to transfer the files into different location via Secure FTP
    SAP help: http://help.sap.com/saphelp_nw2004s/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    Blog:/people/sameer.shadab/blog/2005/09/21/executing-unix-shell-script-using-operating-system-command-in-xi
    XI can be in any OS.
    Go through this again first.
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    More in this blog,
    /people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang
    Check these links
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    <b>Pls Reward if useful</b>

  • Can we define a namespace in the B2B for the XML which generates for EDI

    Hi All,
    I have defined an EDI 856 document which is a inbound. When I give a input EDI message the translation happens and it generates an XML message. So, in the XML message that is generated it gives me a junk namespace.
    <Transaction-856 xmlns="NS_31CA8D0F33324F95A0BF15D85539C27E20081212182610" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="X12" Version="V5020" CreatedDate="2009-01-06T15:56:35" CreatedBy="ECXEngine_837" GUID="{C0F6BEDD-356C-41BA-A89F-775061F2EFAF}">
    So, is there a way in B2B where we could give the namespace of my choice .And that namespace would be generated in the XML File.
    Thanks in advance.
    Regards,
    Kaavya

    Hi Dheeraj,
    The XSD which i am using already has the namespace in the format which you mentioned.
    Ex:-<xsd:schema xmlns="urn:oracle:integration:b2b:DCC1FCD2811C47748DF43A39F735F4F0" targetNamespace="urn:oracle:integration:b2b:DCC1FCD2811C47748DF43A39F735F4F0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
    But still, while generating the XML file it gives the junk namespace.
    Regards,
    Kaavya

  • Missing flatfile of EDI 856

    Hi,
    Thanks in advance.
    EDI 856 program was extracted from Oracle by passing the customer name as parameter, however one of the delivery number for that partcular customer was never made available for EDI to pick up to generate a flatfile.
    Can anyone please tell me the cause of missing the 856 data.
    Thanks
    Satya.
    Edited by: user11048416 on Aug 5, 2009 4:35 AM

    Hi,
       Check with your team there can be some docs on the seeburger modules...
    which can be used for the same..
    basically you need to take care of generation of the no of segments as per your requirements ...but for the segment count..blah..
    some stuff will take care by seeburger..
    I dont have any documents regarding this....search SDN  you can find some..
    HTH
    gud luck
    Rajesh

  • Development of:  SAP- XML IDOC Validation - Mapping - EDI-VAN

    Hi ,
    I am novice to SAP.
    I would appreciate, if you would suggest best way to achieve following Scenario:
    With Minimum Cost. No High Cost middleware products, beacuse we have only following two scenarios.
    1.  SAP -
    > XML IDOC (SHPMNT01) Validation -
    > MapTo- EDI 404_4010------> FTP Loation
    2. SAP----
    >XML IDOC ZSHPEXT1 Validation -
    > MapTo  EDI 204_4010 -
    > VAN
       A. XML IDOC ZSHPEXT1 Validation  error send error message to SAP
       B.SMTP-  Email if there is IDOC validation error or error in message.
    Just for information: We have ERPConnect.
    Thank You,

    Hi
    Thanks for the answer.
    Regarding the FM IDX_XML_TO_IDOC, I thing that I can't use it directly because I have to write a program, I have to read the Xml file (that is located in a special directory of the operative system) and then use the FM putting xml data in the XML_DATA import parameter.
    It's correct?
    Bye
    Carlo

  • Migration - Gentran EDI -- Oracle Fusion Middleware B2B

    Hello All,
    Please share some docs, experiences and the best practices to migrate the existing EDI setup from the GENTRAN to Fusion B2B server.
    Thanks,
    Kamleshwar

    Hi Kamleshwar,
    As far as I know, in Gentran ddf and Unix ig files are used. You may import these files in Oracle AS B2B Document Editor and generate ecs file out of it, so mappings can be reused. For configuration, I think you have to do it from scratch.
    Regards,
    Anuj

  • VMI  EDI or XML to exchange data

    Hi Gurus,
    We are in process of setting up VMI  with one of  our bigest customer. We are working on SCM5.0  and ECC6. But customer has  non R/3 system and already have EDI infrastructure.
    This VMI implementation using APO ( that is  Customer system -> APO(DP/SNP)-> ECC6 (Sales order)),  Customer will be sending sales and stock data to APO and we may have to send  confirmation after Sales order create in ECC6.
    My questions is what is best method to exchange data between customer,  EDI or XML?  If so what are the advantages using one over other?
    Regards,
    Niranjan

    I agree with you that XML is better than EDI as it is latest and easy to maintain.  But we already EDI infrastructure (VAN etc) and using for different interfaces. That is initial investment has already been made for EDI.  Now I need to add new message, So in this scenario, is it smart to use existing infrastructure and use EDI OR going for XML  (we don't use XI in APO system, i don't know how work involved to setup)
    Thanks,
    Niranjan

  • Reg : Idoc Transfer From SAP R/3 to Gentran

    Hi Floks /
    Any body can transfer SAP R/3 idoc to external Sterling Gentran intgration suite . what are process steps required to sending and what are the transaction codes are available in Gentran and Sap .
    can u please help me out.
    thanks
    suresh

    HI,
    See the below links
    In Gentran
    XI with Gentran
    XI vs Gentran for EDI
    SAP ECC 5.0 Upgrade questions with Gentran, BDC, screens
    Gentran EDI ?
    Interuppting/debugging response from Gentran
    Gentran and XI 3.0 question
    Interuppting/debugging response from Gentran
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
    In R3 IDocs
    /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
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    File-XI-IDoc Scenario - File to Idoc
    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
    IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    see the below links to get more details about IDocs
    ALE/ IDOC/ XML
    Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    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
    serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
    http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
    Process codes in IDOC
    http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
    http://edi.stylusstudio.com/msg04418.htm
    Check this link to find out the difference b/w ALE,IDOC and BAPI
    http://www.sap-img.com/abap/ale-bapi.htm
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    ---Split messages :
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    Regards
    Chilla

  • XML IDoc file to IDOC .

    Hi,
    I am receiving XML idoc (Orders05) file from 3rd party to PI system , PI needs to create sales order IDoc ( Orders05) in ECC system. 
    1) Do I need to create source structure for XML IDoc file ? If yes should I create the structure as Orders05 ?
    2) How to map line items of xml file to Orders05 IDoc line items ?
    Please help.
    Thanks - Vinay.

    Hi Vinay,
    Please see Mikes reply in this thread. You may follow the same procedure:
    XML to FlatFile IDOC
    Regards,
    ---Satish

  • SAP PI for EDI

    Hi experts,
    We would like to use SAP PI for creating EDI Documents, Could you let me know what are the options available other than using Seeburger.We would be mostly using this for sending invoices to external edi systems.I would appreciate your help.Many thanks.

    Hi,
    >>>Could you let me know what are the options available other than using Seeburger
    you can send XML files to your EDI provider if the provider supports it
    or even IDOC-XML (there are also providers that support this)
    so it all depends on the EDI provider you use
    Regards,
    Michal Krawczyk

  • EDI SEEBurger Adapter

    We are evaluating  XI for ANSI X12 EDI , Have some  EDI Quesitions using SEEBurger Adapter.
    1) Does SEEBurger Adpater has ANSI X12 Enveloping and De-Enveloping capabilities ???  If Yes,how this is configured /Developed.
    2) Does SEEBurger Adapter has capability of generating sequential ISA control numbers by Trading Partner ??? If Yes,how this is configured /Developed.
    3) Can It perform  EDI Structure validation based on the  EDI standard  rules (For eg: Looping structures, Element qualifier restriction list .....)

    Hi,
    Seeburger is a tool which will conver any type of standard EDI format into XML.
    All standard EDi mappings are predefined in seburger,we have to install in XI Server and use that standard mappings.
    Check this links
    SEEBURGER
    http://www.seeburger.com
    Please see the below blogs
    /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

  • Xml code not working with new version

    Hi,
    my following code is not working with the xalan 2.7.0 version. Any one can help to convert this to work on new version.
    import java.io.*;
    import java.util.*;
    import org.xml.sax.*;
    import org.apache.xalan.xslt.*;
    public class XML2Edifact
    public static void main(String args[])
    throws SAXException, IOException
    if(args.length < 3)
    throw new IllegalArgumentException(
    "Usage is XML2Edifact in.xml xsl.xsl out.edi");
    InputStream sin = new FileInputStream(args[0]),
    sxsl = new FileInputStream(args[1]);
    OutputStream sout = new FileOutputStream(args[2]);
    EdifactFormatter formatter = new EdifactFormatter(sout);
    XSLTProcessor processor =
    XSLTProcessorFactory.getProcessor();
    XSLTInputSource in = new XSLTInputSource(sin),
    xsl = new XSLTInputSource(sxsl);
    XSLTResultTarget out = new XSLTResultTarget(formatter);
    processor.process(in,xsl,out);
    }

    Solved, had to repair the Z10 with the PC!  Would have thought that upgrading software would have saved the environment so that this step was not needed (played with this for several weeks on-and-off).

  • Changing IDOC Control Record for EDI inbound Orders Creatiion

    Hi,
         When I try to process the Inbound orders Idocs file through the GENTRAN EDI System.IDOC's were errored out, because of the Partner function was not defined for the Customer ( Legacy ) ( Type KU ) in the SAP.
            Is there any user exit/badi/Configuration to change the Legacy Partner(Customer) to the SAP Partner(Customer) mapping and update the IDOC Control record with the SAP Partner. I am calling EDI_DATA_INCOMING Function module and IDOC_INPUT_ORDERS.IDOCs errored out with Message EO-332 ( Partner function not defined ). 
    Advance Thanks,
    Balaji.

    It's been a long time since I have done any IDOC processing. 
    Go to SE37 and enter the function module IDOC_INPUT_ORDERS.  Display the source code.  Search for "CALL CUSTOMER".  You should see several "CALL CUSTOMER-FUNCTION" lines.  These are enhancements where you can manipulate the IDOC data.  If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value.  Double-clicking on the number in quotes will bring you to an "EXIT_" function module.  A "ZX" INCLUDE program is referenced.  If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it.  The values passed into the function module are available in the INCLUDE.
    Ideally, you should create a project in transaction CMOD that references the chosen enhancement.  This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

  • Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

    Hi All,
    Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
    For Supplier Invoice I assume R/3 will send data to Vendor (810).
    1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
    2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
    3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
    4. Which Interface and Adapter  I need to use for 810 and which Interface and Adapter  I need to use for 997.
        Pls send its setup with its Mappings defined in Modules.
    5. What is Disptach Advice?  Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
    Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
    Regards

    >
    Rickkk wrote:
    > Hi Ravi and All
    >
    > I am thankful to all of you for great help of yours.
    >
    > Steps:
    >
    > 1) I wil create an INvoice in your backend system. It will generate an IDOC.
    > 2) This IDOC will be sent to my XI system.
    > 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
    YOu have to login to the Physical box in which XI is installed (Take Basis Help.
    In one of the drives, you will find a folder called seeburger.
    Inside that folder, you can browse to find the XSD structure for your 810 .
    YOu will find different XSDs for different versions of 810.
    Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
    It will be there also in the software CD that seeburger provides when you buy it.
    > 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
    >
    > Below are the modules will be present in you suggested seeburger receiver AS2 adapter
    > module key                  Parameter name               Parameter value
    > bic                                destSourceMsg               MainDocument
    > bic                                destTargetMsg                MainDocument
    > bic                                mappingName                  <the name of your X2E mapping for 810>
    > exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    >
    Yes.
    > 5. As per blog  -
    /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    >
    > For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
    >
    > For this scenario will it be like this again like
    > For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
    >
    > For 810  Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
    >
    > I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
    >
    No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
    So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
    > Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
    > Do we have IDOC or something like that present and its mapping ?
    >
    like I said earlier, it is an outbound document if your company is the vendor.
    It will be inbound if your company is the Customer to some other company.
    The IDOC that is used usually will be DESADV idoc.
    > Regards

  • EDI & IDOC Configuration

    Hi Friends
    Any body please help me to my questions.
    1) How to configured to EDI (Send idoc to third party Aramex).
    2) What is the process code for Betmas01 IDOC.
    3) How to raise idoc automatically when we create a data on sitemaster. (Betmas01).
    Thanks
    Krishna

    Hi krishna,
    welcome to SDN
    Configuring EDI Integration
    BEA WebLogic EDI Integration must be completely configured before it can be used. Because EDI Integration depends on BEA EDI Connect for WebLogic Integration to operate properly, make sure you configure Power.Enterprise! correctly so that you can communicate with your trading partners.
    General Configuration
    This section discusses the general configuration information that you should perform before attempting to configure a specific document exchange with a trading partner.
    Configure Trading Partners
    Before configuring individual transactions, you should configure all trading partners, including your own company, using Power.Manager!. For more information about configuring trading partners, see the following topics:
    Configuring Trading Partners
    Chapter 4, "Partners," in the Power.Manager! User Reference Manual
    Configure VAN/Trading Partner Connectivity
    You should also configure your trading partner connectivity before attempting to configure individual document exchanges. See the following topics:
    Connections and VAN Connectivity
    Chapter 3, "Connections," in the Power.Manager! User Reference Manual
    Although you may not want to set up connectivity to your production trading partners at this time, you may want to configure them with file connectors for development and testing purposes.
    Configuring EDI Integration to Receive an EDI Document
    This section describes how to configure EDI Integration so that the BEA WebLogic Adapter for Power.Enterprise! 3.1 can receive an EDI document and send it to the WebLogic Integration process engine as an XML document.
    Pre-Planning
    Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
    Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
    Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide any export utility to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You will be responsible for creating both the DTD and XSD files.
    Within Power.Enterprise!
    Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
    Mapping XML and EDI Data
    Chapter 3, "Maps" in the Power.Map! User Reference Manual
    Define an inbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
    Define an RMI target connection. This connection is used to communicate with the WebLogic Integration process engine.
    Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. This exchange profile should connect the inbound connection from your trading partner to the RMI target connection.
    Within BEA WebLogic Integration
    Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise!.
    Create an event for the application view you just created, using the procedure in Configuring Events. Be sure to set the following parameters:
    Event Name: A descriptive name for the event, such as ReceivePurchaseOrder
    Event Description: Text that provides details about the event
    RMI Service Name: Should match RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section
    XSD: The XML schema of the XML message to be received (optional)
    XML Root Element: The XML root element of the XML schema (optional)
    Deploy the application view you have created and defined.
    Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
    Note: Always start the Power.Server! before you start WebLogic Integration or WebLogic Server. The WebLogic Integration connectors expect to see the Power.Server! running when they are initialized, and they throw exceptions if Power.Server! is not running when they are initialized.
    Configuring EDI Integration to Send an EDI Document
    This section describes how to configure EDI Integration to send an EDI document using an XML document in the WebLogic Integration process engine as the source.
    Pre-Planning
    Determine the EDI standard, version, and document type of the document you will receive. For example, you might select an X12 850 document v4010, which is an X12-standard, 850-type document, version 4010.
    Define the XML format that you will use internally. This XML format should contain a complete data map of the fields in the EDI document that you will use.
    Create a DTD and an XSD for the XML document. You must create both because Power.Enterprise! and WebLogic Integration do not use the same data file format for this step. WebLogic Integration requires an XSD (if you supply one at all), while Power.Enterprise! requires a DTD. You should note that Power.Enterprise! does not provide an export utility that can be used to export a DTD or XSD from a map definition once the DTD or XSD has been imported. You are responsible for creating both the DTD and XSD files.
    Within Power.Enterprise!
    Create a map between the XML document and the EDI document. Import the DTD into Power.Map! to load the XML document standard. The appropriate EDI document should already exist in the Power.Server! repository. If the EDI document is not present, contact BEA Customer Support. For more information about how to do this, see the following topics:
    Mapping XML and EDI Data
    Chapter 3, "Maps" in the Power.Map! User Reference Manual
    Define an outbound connection. This connection should use your trading partner's connection protocol, which you should have defined already. For more information, see Connections and VAN Connectivity.
    Define an RMI source connection. This connection is used to communicate with the WebLogic Integration process engine.
    Define an exchange profile, using the procedure discussed in Configuring Exchange Profiles. The exchange profile should connect the RMI source connection to your trading partner's outbound connection.
    Within BEA WebLogic Integration
    Create an application view, using the procedure in Configuring the BEA WebLogic Adapter for Power.Enterprise! in this document.
    Create a service for the application view you just created, using the procedure in Configuring Services in this document. Be sure to set up the following parameters:
    Service Name: A descriptive name for the service, such as SendPurchaseOrder
    Service Description: Text that provides details about the service
    Connection Name: Should match the RMI service name defined in the Power.Enterprise! RMI target connection set up in the Within Power.Enterprise! section.
    XSD: The XML schema of the XML message to be sent (optional)
    XML Root Element: The XML root element of the XML schema (optional)
    Deploy the application view you have created and defined.
    Verify that the Power.Server! instance is running. At this point, the application view should be available to the WebLogic Integration process engine through the application integration plug-in. For more information about the application integration plug-in, see Understanding the Application Integration Plug-In for BPM in Introducing Application Integration.
    see this link for complete edi information
    http://msdn.microsoft.com/en-us/library/bb246069.aspx
    for your second question......
    sapsdforum.files.wordpress.com/2008/03/idoc_handy_doc.pdf
    Assigning a Process Code (Direct Inbound Processing)
    This section describes how to assign a new process code to the new function module. This enables the function module to be identified from the partner profiles defined in the IDoc Interface when an IDoc of the new message type is received.
    Prerequisites
    You must have completed the required steps in Defining and Using a Basic Type .
    Procedure
    Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Development ® Inbound Processing ® Process Code (WE42), or navigate to Inbound Processing Process Code, then  and New Entries.
    Enter your process code and a description. Choose the Processing with ALE and Processing by function module options and save your entries.
    The maintenance screen is displayed (either automatically or manually), in which you can assign the inbound function module to the process code.
    Choose New entries and enter in the detail screen:
    Your process code
    Module (inbound) frame: Your function module and the maximum number of attempts permitted for posting the application data before exception handling is triggered.
    IDoc frame: Your object type, the trigger event inputErrorOccurred and the completing event inputFinished.
    Application object frame: Your object type
    Leave the other fields blank. Save your entries and return to the process codes inbound initial screen.
    Go back using  to maintain the inbound process codes and choose the Logical message navigation.
    In change mode choose New Entries.
    Enter the message type (logical message) and the process code and save your entries. As a result, the possible entries (F4) in the partner profiles can display the possible process codes from the logical message, that is, the business view.
    If you chose all types in the last step, the value help displays the process code for all message types. This is also valid for both other options for message type and function.
    Result
    This assignment has specified a new process code for the function module. You can now enter this process code in the partner profiles.
    Make the following entries for the example:
    Process code
    TESTEIN
    Basic type
    TESTER01
    Function module
    IDOC_INPUT_TESTER
    Maximum number of attempts
    0
    Message type (logical message)
    TESTER
    IDoc object type
    IDOCTEST
    Application object type
    BUS2032 (sales order)
    To generate Partner profiles automatically you may use BD82 or go to BD64
    thanks'
    karthik

Maybe you are looking for

  • How to use Start Routine for this requirement

    Hello, I am having data in 2 ods and should load that data into cube, but there isn't any common object in both the ods's. I need to analyze based on these ods objects. so I thought of pulling some objects into 1ods which are used for analysis and ad

  • ODBC driver with Oracle 10G on 64bit Windows OS.

    I m facing a issue with my peoplesoft application which is installed on Windows 2003 64bit OS. Setup Details Oracle 10G Server on AIX 5.3. peoplesoft CRM tools 8.48,Oracle 10G client in on Windows 2003(64bit) installed. When i open ODBC administrator

  • HT1423 ram for macbook pro

    I  have a 17" mac book pro that needs ram. How do I purchase and install?

  • ITunes 10.3 Music purchase history

    Hi.  Itunes 10.3 isn't showing my purchase history for music, in order for me to be able to download old content.  It shows apps, but no music.  Isn't it supposed to do this now as part of iCloud?  I've bought stacks of music in the past and to be ab

  • Commander un équipement pour récupérati​on de données

    Bonjour,  J'ai pour projet l'automatisation d'un equipement qui est un flash tester. Il est censé avoir à sa sortie // une imprimante mais qui est introuvable. J'en ai par conséquent trouvée une mais étant donné qu'il s'agit d'un cable C36 Male Male,