The Outbound Transmissions Process

This diagram illustrates the outbound transmission process:

JD Edwards EnterpriseOne Outbound Transmissions

These specifications apply:

  1. The Java program sends XML formatted files to Oracle Transportation Management through HTTP Post sequentially based upon time.

  2. There are no data validations performed against the XML file.

  3. Examples of directory structure for outbound transmissions are listed in this table:

    Structure Example

    Description

    c:\otm\sales\freightrequest\ready

    These are the files that the system has ready to send to Oracle Transportation Management.

    c:\otm\sales\freightrequest\processed

    These are the files that the system processed.

    c:\otm\sales\freightrequest\errors

    These are the files that the system did not process.

    Note: All successfully processed files have a Transmissions Acknowledgement XML file received from Oracle Transportation Management. This transmission file is stored in processed directory. This file includes the Oracle Transportation Management transmission ID for cross-reference purposes.
  4. The program expects an XML configuration file (for example, c:\otm\config.xml) location specified in the Java program. The configuration file contains:

    • Connection information. This connection information includes versions, XML encoding, XML schema URL location and Oracle Transportation Management HTTP post servlet and port.

    • Oracle Transportation Management userid and password. The system does not perform password encryptions.

    • Log file name.

    • Time-out settings.