The Inbound Transmissions Process

The following diagram illustrates the JD Edwards EnterpriseOne inbound integration process:

The inbound integration process has three stages:

1. Stage 1: Oracle Transportation Management to Application Server. Oracle Transportation Management classifies shipment transmissions as either Transportation Arranged or Transportation Confirmation by the hard-coded transmission header remark of "TRANSPORTATION ARRANGED" or TRANS CONFIRMATION", respectively. The voucher transmission requires the hard-coded transmission header remark of 'VOUCHER'. Oracle Transportation Management uses HTTP Post to send the shipment an Oracle Transportation Management uses HTTP Post to send the shipment and voucher transmissions to the JD Edwards EnterpriseOne system. The httpReceive servlet receives the HTTP Post, updates the Inbound Transmissions (F49T90) table and sends an acknowledgment to Oracle Transportation Management confirming transmission receipt into JD Edwards EnterpriseOne. The JD Edwards EnterpriseOne system can process only one transaction in a transmission. Therefore, when setting up external systems in Oracle Transportation Management, limit the number of transactions in a transmission to one. The transmission acknowledgment to Oracle Transportation Management (TransAck XML) document is based on GLogXML-v2001.xsd TransAck schema.

2. Stage 2: JD Edwards EnterpriseOne transmission table to JD Edwards EnterpriseOne staging tables. The Inbound Transmissions Master (R49T90) program reads the records in the Inbound Transmission table and processes the records in the order received. The Inbound Transmissions Master program:

   1. Initializes XML DOM Parser and creates a document.

   2. Parses the document, thereby locating the transaction types and calling the appropriate Parser function to process the elements.

   3. Deletes the transmission records from the Inbound Transmissions table after successfully extracting records from the Inbound Transmissions table into the staging tables.

      Caution: If parsing a transmission fails, the system updates the error code in the Inbound Transmissions table. You can view and delete the transmissions. The JD Edwards EnterpriseOne system does not process the records again. Either these transmission must be sent again from Oracle Transportation Management if the current state has not changed in JD Edwards EnterpriseOne, or the latest transaction must be sent to JD Edwards EnterpriseOne. If transmissions fail to process into the JD Edwards EnterpriseOne staging table, the system does not communicate the failure to Oracle Transportation Management.

   4. Execution is required before the execution of import UBE Sales Transportation Arranged Import (R49T20) and Sales Transportation Confirmation Import (R49T40).

3. Stage 3: JD Edwards EnterpriseOne staging tables to JD Edwards EnterpriseOne transaction tables. After the transmissions are transferred to the staging tables for processing, UBE programs for the integration point processes the records to the JD Edwards EnterpriseOne transaction tables.

   For voucher transmissions, when the Inbound Transmissions Master program successfully processes the records, it calls a version of the Inbound EDI Voucher Edit/Create (R47041). For Transportation Arranged and Transportation Confirmation transmissions, when the Inbound Transmissions Master program successfully processes the transactions it calls a version of both the Sales Transportation Arranged Batch Import (R49T20) program and the Transportation Confirmation Batch Import (R49T40) program.