Validate Button Create New Object With System Generated Object Number Assigned That Is Not Related To AutoNumber (Doc ID 2566662.1)

Last updated on AUGUST 23, 2021

Applies to:

Goal

ACTUAL BEHAVIOR
During Import, get below message like below when pressing Validate button having source file
with no object number specified for Document Type. Below message appears on the import
screen after the process finishes because Agile try to change an existing
object number : XX to change from Document2 to Document type. This number : XX is not related to
Autonumber that is being assigned to the Document subclass.
It seems that Agile is generating pseudo number : XX internally, but since
there is already an existing object number : XX for different Document subclass,
it is displayed as below message.

ERROR
Existing object 'XX' is of type 'Document2' but the incoming object is of type 'Document' - can't update.

STEP
0. Login to Java Client
1. Save as role : Component Engineer
   and Create a new role : Component Engineer Without Delete Privilege
   and remove all delete privilege
2. Assign Import privilege to role : Component Engineer Without Delete Privilege
3. Create a new user : user1 and assign role : Component Engineer Without Delete Privilege
4. Login to Web Client with user1
5. Press Tools and Settings > Import and set following file : test.csv

"ITEM_NUMBER","DESCRIPTION","DOCUMENT_TYPE"
"","test","Document"

6. Import Preference

Default Type

Default Document Type : Document
AutoNumber Source
Document : Document Number

7. Next
8. Item Only
9. Next
10. Define attribute mapping in next step
    No transformations are necessary
    Updates do not require redlining
11. Next
12. Map 3 attribute

ITEM NUMBER
DESCRIPTION
DOCUMENT TYPE

13. Validate

QUESTION
1) What the logic behind this behavior?

2) This issue occurs when the import user does not have delete privilege for the Document subclass. If
adding delete privilege to the user, will it automatically modify existing object number. For example, if there
are actual object with number XX with Document2 subclass existing in Agile, when the import user try to 
press Validate button having source file with no object number specified for Document Type, will it get modified?

3) Are we able to confirm what pseudo number will be assigned in the next round when pressing validate button at SQL level?


 

Solution

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