My Oracle Support Banner

When Updated Through Integration, OTM/GTM One Update Remark Record Is Getting Re-Inserted Into Database Upon Completely Deleting The Previous Record Instead Updating The Existing Remark Text (Doc ID 3004393.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Transportation Management - Version 6.3.7 and later
Oracle Global Trade Management - Version 6.3.7 and later
Oracle Transportation Management Cloud Service - Version 19.3 and later
Oracle Global Trade Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

In OTM / GTM when an existing Remark record is being tried to update through Integration, it is observed that, existing Remark record is completely replaced with a new record.

Actual Outcome :

This means, when an update feed is sent for an existing Remark record, the actual outcome is as below:

  • REMARK_TEXT is updated as expected
  • REMARK_SEQUENCE is appeared to be a new value
  • INSERT_USER and INSERT_DATE are updated correctly
  • UPDATE_USER and UPDATE_DATE are null/blank

 

Expected Outcome :

For a Remark record with Remark Qualifier having Updates Allowed field set to One, Update, when updated through Integration, the desired outcome is that-

  • REMARK_TEXT will be updated as needed
  • REMARK_SEQUENCE must be same as previous
  • INSERT_USER and INSERT_DATE must not be changed
  • UPDATE_USER and UPDATE_DATE are populated as per latest details

 

Changes

No changes has been made on this logic.
 

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
Changes
Cause
Solution
References


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