My Oracle Support Banner

Managed Child Fails To Manage Shipment Stop Remarks For Actual Shipment (Doc ID 748726.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 5.5 to 5.5 [Release 5.5]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

-- Problem Statement:
On 5.5.04.02 Find that when adding the Integration Managed Child Map of Shipment Stop Remark into
the relevant table and processing a RC transaction XML with a Managed Child of Shipment Stop
Remark, the transaction fails to clear the existing Remark
EXPECTED BEHAVIOR
Expect that the remark is cleared

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Set up a new entry in the INT_MANAGED_CHILDREN_MAP for the element ShipmentStopRemark using the menu - Business Process Automation - Power Data - Integration - Managed Children Map with the following details

XML Element ID - Actual Shipment

Child Element Alias - ShipmentStopRemark

Table Name - ShipmentStopRemark

Child Element Path - ActualShipment.Shipment.ShipmentStop.Remark
2. Process an Actual Shipment XML with a RC transaction code and Managed Child Element of
ShipmentStop and ShipmentStopRemark
3. See that the existing remark on a shipment is not being wiped out

-- Business Impact:
The issue has the following business impact:
Due to this issue, users cannot wipe off existing Remarks as expected

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


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