The isue is with respect to WebADI data upload. Currently system allows the user to upload the same set of records multiple times, even though they might have already been pushed to the Project.
This system behavior leads to duplicate upload of records by user. It could be a valid case of when the user attempts to upload the data sheet first time, the sheet going to non-responsive state, with the transfer having got completed
though in the background.
Nowwhen the user re tries to upload, system doesn't validate if the records have already been processed and sent to Oracle Projects.
Is there a way to flag rows as processed, to avoid duplicate uploads.
Any custom extensions available?
One way to acheive is try to provide transaction id (Unique), if this is not the field, check for a field where its unique. then try uploading
In that case what happens is it would restrict in PA interface table ( duplicate records) or else you can select the option saying validate before processing during upload, then it would not process duplicate records
Challenge/risk is there might be transactions uploaded already/processed and then again trying to upload the same set of data later might process( need a process to be adopted by users for having the unique number provided in ADI sheet)
Below are the details, how to use your Transaction Source. Try n use Unique Trx ID..........
When WebADI imports data to Oracle Projects because this is data known to User and which is coming from Outside Projects.
But in case business does not want duplicate data to come-in, they can write a Transaction Import Client Extension (Pre-Import) so that you can put your custom logic to see already such exists in System or not. If already exists then you can stop the upload.
Allow Duplicate Reference
Enable this option to allow multiple transactions with this transaction source to use the same original system reference. If you enable this option, you cannot uniquely identify the item by transaction source and original system reference.
That answered my query. Verified a test case with that flag " Allow Duplicate Reference" unchecked, i find the system
validating now with the error message,
" DUPLICATE_ITEM - A transaction with the same ORIG_TRANSACTION_REFERENCE has already been imported into PA ".