importing Data Using DB.XML IU Transaction Code is Nulling Out Values That Are Not Sent in on the Update Payload
(Doc ID 2935784.1)
Last updated on MARCH 20, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 22.3 and laterInformation in this document applies to any platform.
Symptoms
Issue Description
Customer is uploading DB.XML data files with the Transaction Code equal to "IU" and when the data exists already - populated fields in the tables are getting nulled out and the expectations are that if data exists already in a particular field, it will not be set to null similar to what occurs in an XML data transaction.
Steps to Replicate the Issue
- Create a DB.XML file that has a data record that already exists in the database
- In the file - make a field that has a value in the database = null
- Upload the DB.XML file
- Examine the field that had a value - now this field is null
Changes
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 |