Quantity Propagation Gets Null Pointer Exception when using OMD Agent with Multiple Order Movements (Doc ID 1383522.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

When attempting to propagate the changes from an Order to a Shipment the following issue occurs:

-- Issue
The Ship Unit count change is not updated when using multiple Order Movements

-- Expected Behavior
OMD agent does would propagate ship unit count change when multiple Order Movements are involved

-- Steps
The issue can be reproduced at will with the following steps.

Log into an instance running OTM version 6.2.2

1. Create an OMD Agent: OMD_Agent with the Agent Action of ORDER RELEASE - MOD - PROPAGATE CHANGES: Ship Unit Quantities
2. Create an Order Release - Order_123
3. Plan the order on an Order Movement (OM) using the Action > Manage Buy Order Movement > Show Options
4. Select itinerary: 3 LEG ITINERARY
5 OMs will be created - Select the middle leg and plan it on a Buy Side Shipment.
6. Select the order and edit – go to the ship unit tab and change the count.
7. Select Save
8. Viewing the log you should see the following:
java.lang.NullPointerException
at glog.business.shipment.TShipment.getRelatedTSShipUnits(TShipment.java:3368)
at glog.business.omd.ShipUnitQtyChangePropagator.applyInsertUpdate(ShipUnitQtyChangePropagator.java:260)
at glog.business.omd.ShipUnitQtyChangePropagator.propagateChanges(ShipUnitQtyChangePropagator.java:198)
at glog.business.omd.ShipUnitQtyChangePropagator.propagate(ShipUnitQtyChangePropagator.java:93)
at glog.business.omd.OrderModPropagator.propagate(OrderModPropagator.java:76)
at glog.business.session.OMDProcessorSessionBean.propagateORModChange(OMDProcessorSessionBean.java:111)
at glog.business.session.OMDProcessorSessionServerSideEJBWrapper.propagateORModChange(OMDProcessorSessionServerSideEJBWrapper.java:134)
at glog.business.session.OMDProcessorSessionHome_f09cq7_EOImpl.propagateORModChange(OMDProcessorSessionHome_f09cq7_EOImpl.java:210)
at glog.server.agent.business.order.ORModPropagateChanges.propagateChanges(ORModPropagateChanges.java:51)
at glog.server.agent.business.order.ORModPropagateChanges.process(ORModPropagateChanges.java:83)
at glog.server.agent.business.order.ORActionTopic.persist(ORActionTopic.java:47)
at glog.server.agent.PersistActionTopic.execute(PersistActionTopic.java:34)
at glog.server.agent.business.order.ORModPropagateChanges.execute(ORModPropagateChanges.java:37)
at glog.server.agent.ActionWorkflow.execute(ActionWorkflow.java:49)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper.execute(WorkflowSessionNonTransServerSideEJBWrapper.java:38)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.execute(WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.java:134)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:352)
at glog.server.workflow.Trigger.trigger(Trigger.java:122)
at glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:146)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:98)
at glog.util.event.EventThread.run(EventThread.java:86)
at java.lang.Thread.run(Thread.java:619)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.