Procurement Freight Request Assumptions

These assumptions apply to the Freight Request integration point:

1. When closing or canceling a line in JD Edwards EnterpriseOne, the release status for the remaining quantity only is updated in Oracle Transportation Management. If there are open shipments or order releases, you must cancel them manually before the purchase order line is closed or canceled.

2. The cancel date transmitted to Oracle Transportation Management may not actually reflect the date of the closed or canceled order.

3. The JD Edwards EnterpriseOne system extracts to Oracle Transportation Management units that are open on the purchase order. In some cases the open quantity in JD Edwards EnterpriseOne may differ from the open quantity in Oracle Transportation Management; especially when reversing an Oracle Transportation Management-eligible purchase order. Check Oracle Transportation Management to make sure the open quantities are correct.

4. The JD Edwards EnterpriseOne system calculates the weight and volume of the parent kit item by accumulating the weight and volume of all shippable components.

5. The JD Edwards EnterpriseOne system does not extract services or non-stock line type items that do not have weight or volume associated with the transaction. Thus, the JD Edwards EnterpriseOne system bypasses the purchase order line during Freight Request and does not select it for extraction. However, if a weight and volume is associated with the transaction, the JD Edwards EnterpriseOne system extracts the non-stock or service item.

6. Order quantities can be expressed in fractional numbers in the JD Edwards EnterpriseOne system; whereas in the Oracle Transportation Management system, order quantities are always expressed as whole numbers. Therefore, the JD Edwards EnterpriseOne system extracts order quantities into the packaged item count as a round up whole number at the time the Freight Request Order Release XML is built.

7. If the JD Edwards EnterpriseOne system places a purchase order on hold or cancels it after transmitting the freight request, orders are not removed from the order base in Oracle Transportation Management but instead the status is changed to "Hold Releasing" or "Cancel Releasing."

8. If an order line is eligible for extraction to the Oracle Transportation Management system, the shipment details in the purchase order grid are disabled in the inquiry mode. In the Add mode, if the user enters shipment details such as carrier or mode of transport, the system blanks out those details and, after issuing a warning, disables the grid columns.

9. In some exceptional cases such as a partial receipt reversal upon over receipts, the quantities may differ between the Oracle Transportation Management and JD Edwards EnterpriseOne systems. Thus, whenever a receipt is reversed, it is necessary to manually check the quantities in both systems to ensure that both systems are synchronized.

10. The JD Edwards EnterpriseOne system does not receive message transmissions from the Oracle Transportation Management system, except voucher information.

11. The JD Edwards EnterpriseOne system transmits short item number along with its assigned Branch/Plant to the Oracle Transportation Management system.

    You should complete procurement order entry override address changes within the Oracle Transportation Management system after the initial freight request.

12. There is no programmatic process which prevents the Freight Request program from selecting JD Edwards EnterpriseOne transportation orders or blanket orders. Customers must set up valid UDC values in the UDC 49/TP table to exclude these types of orders.

13. If a procurement order is created with foreign currency, the staged amount contains unconverted decimals. The XML builder converts the decimals.

14. The JD Edwards EnterpriseOne system transmits the extended price on the purchase order line to the Oracle Transportation Management system by data mapping to the Declared Value element in the Oracle Transportation Management system.