EDI Formats

Hello B2B Experts,
Oracle B2B supports EDI feeds including 850,855,810
Does B2B supports these feeds
860(Change),
856(ASN),
820(PAY ADV),
824(Error Ack) ..?
Any pointers available for this ?
Thanks

Hi Dhiraj,
Thank you for your response.
Also can u let me know if volumes in below table are supported for these X12 documents. ?
Feed Type Expected Volume/Day
850" Inbound 75-100 (with avg. 5-10 lines perPO)
855" Outbound 75-100 (with avg. 5-10 lines per PO)
860" Inbound
856" Outbound
810" Outbound 50-75 (with avg. 3-5 lines per Invoice)
820" Inbound
824" Inbound
Thanks
Kranti
Edited by: user780436 on Apr 14, 2009 8:15 AM

Similar Messages

  • Help needed on Transforming input File to EDI Format

    I have an input flat file in one location. Using BizTalk, i need to pick that file from that Recieve location, transform it to EDI format and send it to Destination location.
    Now, when I place input file in the "Recieve location", it is being processed and it is erased from recieve location. But I am not able to see the output in the Destination location.
    And when i query it in BizTalk Administration console, the state is "Completed" without any errors.
     Any guidance/suggestions are appreciated. Thanks in advance.

    Hi all, I have just collated everything and have put it in my words below..Please
    let me know your valuable inputs as I am struck in this point from more than a week.
    I need to fetch an input flat file (.txt format) from the "Receive location" and I am supposed to transform that to an EDI message X12 format and send it to Destination folder.
    I have set up the receive port and send port configurations in the Admin Console, have created the Trading Partners, agreement and other settings.
    The problem I am facing : Now, when I place input file in the "Receive location", it is being processed and I am able to pick up the file from the input folder
    but I am not able to figure out why the file is not being processed and sent to the destination folder.. (If I query for All In Progress instances, suspended instances or Running instances : I am not getting any results and the below grid is always empty).
    And when i query it in Biz-talk Administration console for Tracked instances, the Receive pipeline component's state is "Completed" without any errors.
    And I am not using any Orchestration in between..
    Thank you all in advance....

  • Invoice in EDI format

    A customer of my company wants us to send invoices in 810 EDI format from SAP. Does any one know how to do the necessary set ups/configuration in SAP to send the invoice IDoc?
    Points rewarded for helpful answers.
    Thanks,
    Archana

    Hi,
    For configuring of EDI for Invoice, you have to do following things :
    1. Use Outbound IDOC type u2013 INVOIC01 (Message type u2013 INVOIC)
    2. Maintain Condition Record for Billing Output (EDI)
               Transaction Code : VV31 / VV32 / VV33
               Output Type : RD00
    3. Port in IDOC processing
               Transaction Code : WE21
               Port Type - > File Port : For eg . - EDIFACT
               Maintain all the relevant field like physical path for directory, Functional module for file name.
    4. Create Partner Profile
               Transaction Code u2013 WE20
               Select Partner type KU (Customer) and maintain outbound parameters for Outbound IDoc - INCOIC01
    Some Important Transaction Codes for EDI Configuration which you have to know.
               WE63 - Documentation IDOC Type
               WE46 - IDOC Administration
               WE16 - Trigger Inbound processing
               WE19 - Test Tools for IDOC Processing
               WE02 u2013 IDOC Status
               WE05 u2013 IDOC Status
               We07 u2013 IDOC Statistic
    Hope you can configure now.
    Cheers.....
    Imran

  • EDI Formats for SAP

    What are the different Electronic Data Interchange  (EDI) formats available  for SAP B1?With complete details.

    hi,
    please check the ff.
    http://www.di-international.com/Solutions/SAP-Integration.aspx?gclid=CJic7Pat4K0CFU4b6wodlU3J4A
    http://www.dicentral.com/sap_edi/
    http://www.highjump.com/solutions/truecommerce/business-system-plugins/sap-business-one
    http://www.youtube.com/watch?v=_KhBs2Sh7Pg
    regards,
    Fidel

  • How to convert Idoc file to EDI format?

    Dear Expert,
       I've config outbound process of purchase order and send idoc out put to idoc file(XML) after that I would like to convert IDoc file to EDI format. How to conver IDoc file to EDI format?
    Please suggest me.
    Big thanks,
    Sak

    Consult Abaper..
    Interface is going to do this activity

  • EDI format i'm getting  source documents..

    Hi
       from my source i'm getting EDI documents.. i need to load this data into IDOCS in R/3 system .. ..but here i got one doubt..  the source format is always EDI format only.. then why  again they are choosing XI integration.. with out XI also dircetly we can load those  edi documents through EDI sub system....
       here what is the adavatages..  by using XI insted of directly  load the data into R/3 system..
    Thanks
    Babu

    Hi,
    For understanding the EDI file we need to use the third party seeburger adapter like As2,X400,OFTP.
    We need to write a module program in the module parameter tab of adapter which does the conversion of EDI to XML and XML to EDI so that it will be understood by XI.
    Refer all my threads which gives you more idea.
    Refer this forum which is replied by me which talka about the configuration which need to be done for AS2 adapter. This is very helpful:
    Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
    Re: Seeburger AS2 adapter...
    Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
    Seeburger info:
    Re: seeburger adapter
    Re: SEEBURGER's VAN Adapter
    AS2 info:
    Re: Regarding Seeburger AS2 Adapter
    SEEBURGER EDI adapter
    Seeburger :
    please look in to this links u will come to know about seeburger adapter.
    HI,
    /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
    /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
    Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
    The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
    Supported EDI formats include:
    • ANSI
    • EDIFACT
    • INHOUSE
    • IDOC
    • XML Schema
    • XML DTD
    • CSV
    • Delimited Data
    • positional data
    • SWIFT
    • EANCOM
    and many more.
    See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
    Thnx
    Chirag

  • EDI Format in SAP without Gentran Subsystem

    Hello,
    Our customer currently use Gentran to generate the EDI Formats, and then send it to the WebSphere broker. They do not want to use the Gentran subsystem anymore, and  ask if there is a solution in sap for creating this EDI Formats directly. I investigated that SAP does not supply the EDI subsystem for several reasons, so i have to give the customer a valid reason if this is not possible. Also i would like to know if it is possible to send directly the Idocs to the Broker and convert it to the EDI Format there .Any help would be appreciated.
    Thanks.

    Hi Francisco,
    I am not aware about Gentran system. But i can give you some information related to EDI format with help of PI
    You can send or receive EDI files via PI with Seeburger insertion.
    Seeburger is used to convert XML to EDI or EDI to XML.
    For example I am sending an IDOC from SAP system and want an EDI file in third party system. for this scenario you have to use PI with seeburger. SAP IDOC ->PI->Seeburger->EDI file (third party)
    In PI you have to create 1:1 mapping to convert IDOC to EDI XML and this EDI XML is send to seeburger to create EDI file.
    There are many standard EDI mappings available in seeburger. You can check all the maping from there.
    I hope this answer will help you.
    Regards,
    Shradha

  • Best EDI-Format (excl. I-DOC)

    Hello everybody!
    Normally we are using I-DOC for data exchange.
    But more often our EDI-Partners are not supporting this format.
    So my question is, what is the best alternative to I-DOC (low costs and without circumstances)?
    Does EDIFACT need an external converter?
    What is the difference (advantages / disadvantages) between EDIFACT and XML?
    PS: I already used google for finding more informations about this compare, but wasn't successful.
    Thx in advance

    Bill,
    in FrameMaker you design each table to have certain column widths because you are limited by the size of your page (and the paper).
    HTML browsers have more freedom unless they are explicitly instructed to create certain column widths. The basic rule for HTMl tables (and there is only a single table "format" in HTML) are those:
    Check each column for its minimum width, specified by a graphic or a very long unhyphenated word.
    Look in each column for the longest content. i.e. as if multi-line content would be written in a single line (attention: <br> tags force line breaks)
    If all columns expanded to hold the longest content fit inside the browser window: scale them accordingly: This may result in tables which are smaller than in print, because they contain only very short texts
    If the columns do not fit the current browser width, scale them down to fit the browser width, but only as far as the minimum width.
    If the sum of minimum widths is wider than the browser window: create a horizontal scrollbar.
    Of course, using CSS instruction like {width: 12em;} one can force certain column width independent from content, but this is usually not the default.
    If you want all your tables to always span the full width of the browser window, you have to add the following to your CSS (maybe via the Webworks UI):
    table { width: 100%; }
    HTH,
    - Michael

  • Conversion of EDI File format to IDOC format

    We have a file in u201C.ediu201D format. We could not process this file with RSEINB00 ( IDoc inbound processing using file ) program.
    1-) Could we directly do our process with this u201C.ediu201D file ? Or do we have to convert this u201C.ediu201D file to IDOC format?

    If it's EDI format file (Ex: EDIFACT, X12 ...etc), we should convert the file to IDOc file by using mapping in subsystems like Gentran or TLe..etc. Conversion from edi format to idoc format will not be done in SAP.
    Reddy

  • Exception in XML Parser (format problem?)

    Hi Experts,
    I am working on IDOC -> AS2 Configuration and the AS2 Configuration has the below structure
    <RecordSet>
         <Row1>
                       <row1 - field1>
                       <row1 - field2>
                       <row1 - field3>
         </Row1>
         <Row2>
                       <row2 - field1>
                       <row2 - field2>
                       <row2 - field3>
         </Row2>
         <Records>
              <Record1>
                        <Record1-Field1>
                        <Record1-Field1>
                        <Record1-Field1> 
              </Record1>
              <Record2>
                        <Record2-Field1>
                        <Record2-Field1>
                        <Record2-Field1> 
              </Record2>
         </Records>
    </RecordSet>
    We are getting the expected Structure when we AS2 Receiver has the xml format. But while doing module development with the strctxml2Plain, we are getting the below error  in RWB CC Monitoring.
    Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
    Any ideas, why this error we are getting.....
    Thanks in advance,
    Regards,
    Vasu

    Hi Vasu,
    Not in the Mapping of IR.
    In BIC Mapping Designer you have to test with the standard Mappings by providing the sample file whether the Conversion is happening correctly or not.
    You have to take the same input file that what ever you are having now.
    So that it will say clearly what is the problem in converting the XMLto the required EDI Format...
    Check whether you have any Date Format Values are comming from the input file.
    Regards
    Seshagiri

  • Using B2B for sending PAYMUL files in EDIFACT format

    Hi B2B Gurus,
    One of our client has the following requirement.
    1) Create Payment batches in Oracle AP and Format the payments using an EDI format program.
    2) Translate the EDI format file into PAYMUL EDIFACT format.
    3) Send the PAYMUL file across to the bank and receive the acknowledgments.
    At the moment our client uses the services of a third party vendor to take care of the EDI translation, document management and transportation
    features.
    Would it be possible to achieve the above requirement using Oracle B2B Integration + Adapters?
    If yes, would request you to provide me with the Adapters we need to buy (license required) and also the components that would be required to achieve the above functionality.
    Thanks and Regards,
    B2B Naive
    Edited by: user5546779 on Feb 9, 2010 11:05 PM

    Hi,
    Oracle B2B can translate the EDI XML to native EDI format and vice-versa. It has support for both the flavours of EDI - EDIFACT and X12. It has the support for almost all the transport protocols as well. Moreover, for any customization, there is facility of java callouts as well.
    Would it be possible to achieve the above requirement using Oracle B2B Integration + Adapters?From the high level requirement you posted, I can say that it is very much possible to achieve this using Oracle Integration B2B product only.
    If yes, would request you to provide me with the Adapters we need to buy (license required) and also the components that would be required to achieve the above functionality.Now this will vary as per your network design, solution design and detailed requirements but at high level you need to buy only Oracle B2B. First of all you should decide the scope and requirements and then go for estimation. After that decide whether you may go with 10g version or you need 11g (as it has various supports which are not there in 10g).
    For the start, below documents may help you out -
    http://www.oracle.com/technology/products/integration/b2b/pdf/edi_cookbook_oracle_b2b.pdf
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_002_B2B_Standards_Supported.pdf
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_014_Questionaire_Sizing.pdf
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_015_Questionaire_SI_Assessement.pdf
    http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_016_Questionaire_Trading_Partner.pdf
    http://www.oracle.com/technology/products/soa/b2b/collateral/b2b_11g_ds.pdf
    http://www.oracle.com/technology/products/integration/b2b/Oracle_B2B_10g.html
    Regards,
    Anuj

  • IDOC to EDI file in PI 7.0. ( exchange infrastructure)

    i have to do one application
    SAP ECC 6.0 -> SAP XI -> Non SAP File Server
    Non SAP file server accepts only .edi format files.
    m trying IDOC to File scenario. IDOC generated is not giving exact EDI format which needs to send. How to transfer EDI format file from this scenario.
    if its done by file content conversion, pls describe more.
    eg . file output(.edi file) should be in below form
    EDI_DC40 100000000000027837646C 3012 O
    E2EDK01005 100000000000027837600000100000001 XSEK 5.23120

    Hi,
    There are two ways:
    1. You can find out if an EDI provider (3rd party) which supports XML EDI Messages  so you can just send XML EDI messages You can use Seeburger Adapter to conver into EDI Format.
    In general , If sender side is File the that file must be generated by EDI mappers tool like BIC.
    If file is in receiver side you have to use some Adapter to conver into EDI format.
    -you can use FILE/FTP Adapter with Seeburger modules.
    -you can use Seeburger OFTP Adapter.
    See the following documents to help you ..
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    /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
    2. You can use EDI 834 Enrollment messages with XI you don't need an adapter - you can use adapter module:
    a) you can develop the adapter module for file adapter yourself
    for one message it will ont be that difficult
    b) you can use SAP conversion agent to create the EDI adapter module
    (it has many EDI messages included)
    Thanks
    Swarup

  • 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

  • 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

  • Generating EDI from a non-SAP, non-EDI-savvy database to go INTO a SAP sys?

    I am a FileMaker geek.
    I have been asked about developing EDI transaction modalities from within a FileMaker Pro database for facilitating data exchange between the FileMaker db and a SAP environment owned & maintained by the same company.
    It seems like an odd request (these days, most exchange to/from FileMaker and other in-house systems is done "live", writing directly to the rows & columns of the various non-FileMaker tables using standard ODBC drivers;... but ignoring that, I've looked at what EDI is, and does, and I gather that the following are true?:
    u2022 System A's data structure is "flattened" down and then that data is arrayed as a "document" such as an invoice or a purchase order, etc etc....
    u2022 EDI is a venerable and well-established system allowing that resulting "document" to be conveyed, usually to a different company such as a trade partner, (in this case NOT, it will all be internal), which can then, in some fashion, import the data from the "document" into its own very different table structure in what we'll call System B.
    u2022 EDI in some fashion creates a standard, and that standard replaces the need for the folks using System A and the folks using System B to do a lot of cumbersome comparison of "what table and what column in your system represents the unique identifier for invoice and which column is invoice number" etc etc, -- by having both folks "speak EDI" the need to map out those matchups is eliminated.
    Please correct me if I'm on the wrong track up until that point, thanks.  Now, assuming I am NOT wrong, my main questions:
    u2022 File format!  Is the EDI "document" a plain text file that can be assembled and exported from a system that is itself oblivious to EDI, by a developer who is given the schema of how that text document has to "look" to System B?  Or is it binary and/or of sufficient complexity that no one DOES that, that instead some sort of driver or program is generally acquired or purchased that encodes data (say for example tab-delimited ASCII text) into EDI format?
    u2022 Schema?  I know how to flatten relevant information and export it out of FileMaker, but for most such requests I would be given a sample document, e.g., "data that goes into QuickBooks has to be in XML format with the relevant XML headers & data in the following order..." or "data that goes into our MAS 90 should be in tab delimited text with the following column order and without column name as top row..." or "data that is to go into our SAS system should be a plain text file with each column a precise char length padded with the standard space char as need be, in the following order..." etc etc.  Would I be given a similar schema and then just export out of FileMaker and assume that they will convert it (if need be) to EDI format from that, or is the art of spitting out data as an EDI "document" a very different sort of task?
    u2022 Is there a good reason that my initial gut reaction is necessarily WRONG, i.e., that since Company X owns both System A (FileMaker) and System B (their SAP system) and presumably have the hi-level passwords for full access to both, it would make more sense to write directly to the appropriate corresponding tables rows & columns instead of using EDI?  If so can you give me a sense of why they would want to use EDI for this?
    with sincere gratitude, thanks in advance.
    Edited by: Allan Hunter on Feb 3, 2009 2:25 PM elaborated on thread title

    Thank you, <b>Amit Kulkani</b>, for your replies.  I'm afraid neither answer is really an answer to my questions.  May I elaborate?
    a) In the first reply post, you write: " if we did not use EDI there might be many mannual error take place in operation.  So In short only the security point of view EDI works better."
    Assuming your target (SAP) tables have rules per each column and per each row, a direct SQL statement should not allow inappropriate information to be entered.  I can accept that perhaps SAP was written without such safeguards, if that is what you are telling me, but in that case any direct data entry process is going to be vulnerable to data entry error.  Or do you mean that no data entry <i>whatsoever</i>, at any point, at any time, occurs other than via EDI?
    b) In the second reply post, you cite these advantages.  Advantages over hand-writing the data on the back of a paper napkin and mailing it in a manila envelope for someone to retype into the system, yes, but how are any of these improved by using EDI instead of a direct connection from FileMaker?:
    u2022 Reduced postage costs  <i>Huh?</i>
    u2022 Reduced expenses <i>what expenses?</i>
    u2022 Speed <i>I would think directly writing to the data would be considerably FASTER than exporting to EDI and then importing from EDI into SAP</i>
    u2022 Elimination of paper documents <i>Who said anything about paper documents?</i>
    u2022 Elimination of labor intensive tasks, such as data entry <i>Yes, what I propose would eliminate that also</i>
    u2022 Greater accuracy of information <i>See above</i>
    Can you re-read my original post and give the same thoughtful consideration, but this time comparing EDI to what I am proposing (direct connection to the SAP tables), <i>not</i> comparing it to sending the data in on a piece of paper to be retyped manually when it arrives?
    Thanks in advance, and thanks again for your answers so far.

Maybe you are looking for