Transaction Code of "D" - Delete Only Checks For Primary Keys
Last updated on SEPTEMBER 22, 2017
Applies to:Oracle Transportation Management - Version 6.3.5 and later
Information in this document applies to any platform.
When uploading a csv file with a transaction code of "D" which uses a custom column which does not exist in the GL_USER table, the CSV upload process continues rather than stopping with error.
It is expected to have the csv upload failing due to the fact that the column does not exist in the database and to not have the records deleted.
The issue can be reproduced at will with the following steps:
CSV file contains an extra column that does not exist in the table GL_USER.
1. Integrate the csv file via Business Process Automation
2. Command of "d"
3. The user is deleted
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms