Announcement

Collapse
No announcement yet.

OTM integration with E2open

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OTM integration with E2open

    Can anyone suggest how E2OPEN works with OTM. Is it similar to the other EDI standards. What all is required form OTM standpoint. Is it the same XML, schema mapped to EDI elements . How does the carrier link up with E2OPEN.

    Please let me know.

  • #2
    Re: OTM integration with E2open

    Moved to the Integration forum.

    --Chris

    Comment


    • #3
      Re: OTM integration with E2open

      BTW - I'll ask the E2open guys to tackle this one, so you'll have an official answer. We've been working with them a lot and I'm a big fan of the solution.

      --Chris

      Comment


      • #4
        Re: OTM integration with E2open

        Thank you for the inquiry

        E2open Logistics Network (ELN) comes bundled with an OTM Application Connector that talks in the native OTM XLM schema and the native OTM protocol.
        So there is no change required in OTM and no additional functionality required.
        There is a couple of OTM settings that need to be configured in a specific way.
        For example, ELN requires OTM Transmission Reports to be sent back to ELN so we can keep track of successful or failed processing of the transactions by OTM.
        Oracle is publishing documentation as part of the standard OTM documentation that explains these configuration settings.
        E2open and Oracle work together to pre-test the OTM Application Connector when new versions of OTM are released.
        Currently, we have experience connecting to OTM 5.x and 6.x environment but earlier ones could be supported if there is customer demand.

        Once the OTM XML is received by ELN, it is transformed into the relevant EDI elements, or the reverse if the transaction is from EDI to OTM.
        E2open is working with Oracle to make available standard maps for all transformations applicable to OTM business processes (e.g. tender, tender response, shipment status, invoice, etc….)
        These maps are also bundled in ELN.
        Of course, there may be requirements to deviate from ELN standard maps to handle unique requirements and ELN can support that.
        Also additional processing logic can be enabled in ELN.
        For example, ELN can take an incoming EDI transaction and first use it to create a shipment in OTM using the SAW approach available in OTM, and then send a second transaction with the actual content (e.g. a shipment status or a shipment invoice) once it has received confirmation by OTM that the shipment was successfully created.

        Standard maps are available for common industry standards like EDI-X12, EDI-EDIFACT, etc… as well as a flat file CSV that can be used to connect to carriers that do not have EDI capabilities themselves.
        For these carriers, E2open provides a free E2open software download, or a hardware appliance, that can be used by them to receive and send this flat file CSV files.

        From the carrier perspective, a carrier choose whatever method they prefer to connect to ELN such EDI-VAN, EDI-Internet (AS2), FTP, etc…. or the free E2open software download, or a hardware appliance.
        They can even chose different methods for different transaction types.
        There is no charge for trading partners (e.g carriers) to use ELN

        In summary, think of ELN as fully featured any-to-any B2B gateway that is provided in a Software-as-a-Service model and that is pre-integrated into OTM, including all the relevant transformation maps, and is already connected to a growing list of carriers and LSP’s.

        If you require additional information, please contact me
        Seibo Shen
        E2open Logistics Network – Information Desk
        [email protected]
        __________________________________________________

        Seibo Shen, E2open
        [email protected]
        yahoo IM - seiboshen
        E2open Logistic Network for OTM

        Comment


        • #5
          Re: OTM integration with E2open

          Thanks for the information Seibo. Could you pls share the list of carrier who are already in the E2open network, because it gives an edge for us to convince our customers by providing this information during the proposals.
          Cheers,
          Murthy

          Comment


          • #6
            Re: OTM integration with E2open

            Thanks Seibo,
            Currently we are using OTM 5.0. I have few questions.

            Can i get a sample of standrd map for Tender offer
            Does the communication method still remain same. Can we use HTTPPOST to send files to URL.
            Who does the mapping of EDI elements to XML.
            Do we bother about schema at all.
            Can you give a example of a configuration change that needs to be done
            IF ELN is in place, can we use others like GTNEXUS as well

            Thanks for your response.


            Ram

            Comment


            • #7
              Re: OTM integration with E2open

              Hi Chris / Ram,

              Is OTM 6.0 / 6.1 has out-of-box integration with E2Open?
              Cheers,
              Murthy

              Comment


              • #8
                Re: OTM integration with E2open

                With v6.x, the interfaces between OTM and E2open have been built out for the main integration flows.

                There may still be some work that needs to be done on the OTM side (agents, workflow, define external systems, etc), based on the business requirements.

                Seibo, feel free to add in any comments you or Lorenzo have.

                --Chris

                Comment


                • #9
                  Re: OTM integration with E2open

                  Originally posted by djjram21 View Post
                  Thanks Seibo,
                  Currently we are using OTM 5.0. I have few questions.

                  Can i get a sample of standrd map for Tender offer
                  Does the communication method still remain same. Can we use HTTPPOST to send files to URL.
                  Who does the mapping of EDI elements to XML.
                  Do we bother about schema at all.
                  Can you give a example of a configuration change that needs to be done
                  IF ELN is in place, can we use others like GTNEXUS as well

                  Thanks for your response.


                  Ram
                  @djjram21

                  Can i get a sample of standard map for Tender offer

                  - E2open Logistics Network (ELN) is designed to take the native OTM XML format and convert it to appropriate format that can be consumed by the carriers and LSP (EDI X12, EDI EDIFACT, CSV flat files, RosettaNet, etc….)
                  - So our current starting point is the OTM XML from the specific OTM customer deployment.
                  - Over time, Oracle and E2open will publish standard configurations that can be used by customers out of the box, or as the basis to add deviations based on customer requirements
                  - So for now, you only need to give E2open a copy of your OTM XML schema and we will work with you to deploy the relevant transformation maps

                  Does the communication method still remain same. Can we use HTTPPOST to send files to URL.

                  - Yes, we have implemented the standard HTTPPOST defined in the OTM API
                  - The only thing you need to do is to configure certain parameters and attributes
                  - Oracle is working to publish a standard OTM documentation that describes these settings
                  - In future OTM release, you should expect to see further simplifications in this area

                  Who does the mapping of EDI elements to XML.

                  - E2open does all the mapping of EDI (or any other protocol/payload) elements to OTM XML. E2open works with each OTM customer to define the map specification, and then E2open implements these maps with the specific carriers

                  Do we bother about schema at all.

                  - No, all communication to/from the OTM instance is in OTM schema-compliant XML instances

                  Can you give a example of a configuration change that needs to be done

                  - In OTM you would need to configure ELN as a service provider and apply an XSL template to extract a specific message addressing information that ELN needs to route the messages to the correct carrier

                  IF ELN is in place, can we use others like GTNEXUS as well

                  - Yes, ELN can be used to connect to other portals/networks such as GTNexus. The first one on the Oracle-E2open priority list for ocean portals is INTTRA. Oracle-E2open is also working with mobile network providers for connection between OTM Fleet Management and in-truck devices.
                  __________________________________________________

                  Seibo Shen, E2open
                  [email protected]
                  yahoo IM - seiboshen
                  E2open Logistic Network for OTM

                  Comment


                  • #10
                    Re: OTM integration with E2open

                    Originally posted by MURTHYKO View Post
                    Thanks for the information Seibo. Could you pls share the list of carrier who are already in the E2open network, because it gives an edge for us to convince our customers by providing this information during the proposals.
                    @murthyko

                    E2open currently has 75,000 trading partners on-boarded onto our network with approximately 300 that are LSPs and carriers. The rest are suppliers, contract manufacturers, customers, distributors, retailers, etc…

                    The first OTM customer went into production at the beginning of 2010 so we are at the beginning stages of connecting carriers and LSP directly to OTM instances, vs other transportation applications.

                    What is important to note is that E2open is pricing ELN as if every carrier and LSP is already connected to the E2open Logistics Network.

                    Therefore, all the additional effort required by E2open to bring a new carrier/LSP onto the network is an investment made by E2open.

                    From a timing perspective, on-boarding a new carrier/LSP requires on average an additional couple of weeks, compared to an existing carrier/LSP which typically requires 1-3 weeks.

                    Please let me know if you have any additional questions.
                    __________________________________________________

                    Seibo Shen, E2open
                    [email protected]
                    yahoo IM - seiboshen
                    E2open Logistic Network for OTM

                    Comment


                    • #11
                      Re: OTM integration with E2open

                      Thanks Seibo, this is quite good information. We use E2open's RosettaNet-Glog XML industry standard mapping. Along with that, the carriers use E2open's FTP servers to drop message files using standard E2open's file naming conventions.
                      Best Regards,
                      Rishabh Garg

                      Comment


                      • #12
                        Re: OTM integration with E2open

                        Hello All,

                        We have three different servers for OTM Web, application and DB
                        We have OTM web server for DEV and QA on first server, OTM application server for DEV and QA on second server and OTM DB server for DEV and QA on third server

                        We have one critical situation for our QA

                        We are able to send messages from OTM to E2Open for QA but while messages coming from E2Open to OTM we are getting it on DEV environment instead of QA

                        Where is the configuration url is situated for E2Open to OTM and vice versa?

                        Could you please help me out in this situation?

                        Thanks in advance
                        Let's connect on LinkedIn
                        Mobile: +91 973 049 6886
                        E-mail: [email protected]

                        If my post was helpful, then click on the Like button

                        Comment

                        Working...
                        X