Skip to main content

Hi All,

I use external file assistant to upload the credit card transactions to IFS. Accidentally i uploaded the same file twice how can i remove the duplicated transactions? I can see all the transactions in the credit card transactions window since all belong to non reimbursable credit card type. It is not allowed to delete the transactions from credit card transactions window since the card type is not re imburasable

Thanks in advance.

@Tomas Ruderfelt - Any suggestions from you on this?


Hi @Dharshankumaar Mahendran  contact with your technical team they will remove the duplicate record using PLSQL direct from Database.

 

 

Thanks & Regads,

Zuhaib
IFS Consultant
https://www.linkedin.com/feed/


Hi @zuhaib,

Thanks for the response. Im aware that this can be deleted via the database from the table but I am looking to do it in the application level.

 


Hi @Martin Hulsenboom and @ADDMARIAE - Any suggestions on this?

 


Hi,

Not possible as I know. I know it was very restricted what you could really do with these transactions since you should not be able to manipulate them.

Regards,

Maria

 


Hi @ADDMARIAE 

Exactly, Itseems a limitation I will raise it as an idea. Thank you so much for taking the time to respond. 


Hi ​@Dharshankumaar Mahendran  we have a workaround for this.

  • Authorized person can change the credit card type to reimbursable, and then the relevant transaction can be deleted from the application by the person who made the transactions.

     

 

Hi ​@Rumesha -

Thank you for adding the workaround, Changing the credit card type from Non-Reimbursable to Reimbursable to delete transactions does work, but it carries several risks. It can impact data integrity (accidental deletion of valid transactions), create audit and compliance issues (unclear audit trail, possible policy violations), security concerns (misuse of privileges), and it can also lead to operational issues.

In addition, this approach is highly cumbersome when multiple employees (for example>100) are involved, as each user would need to perform deletions individually, which is time-consuming and prone to error.

A safer and more efficient solution would be to explore options for reversing the upload at the source or enabling duplicate detection controls in IFS.

Best Regards,

 

 


Hi ​@Rumesha -

Thank you for adding the workaround, Changing the credit card type from Non-Reimbursable to Reimbursable to delete transactions does work, but it carries several risks. It can impact data integrity (accidental deletion of valid transactions), create audit and compliance issues (unclear audit trail, possible policy violations), security concerns (misuse of privileges), and it can also lead to operational issues.

In addition, this approach is highly cumbersome when multiple employees (for example>100) are involved, as each user would need to perform deletions individually, which is time-consuming and prone to error.

A safer and more efficient solution would be to explore options for reversing the upload at the source or enabling duplicate detection controls in IFS.

Best Regards,

 

 

Hi ​@Dharshankumaar Mahendran 

Agree, I also think that bit of process improvement/functionality addition is needed here, this is an easy area where users can go wrong. This is the workaround given by IFS so far.


In addition, I noticed that it is not really required to have person made expense get involved to delete the expense. People who has privileges can delete them.


Hi ​@Rumesha - Hopefully we’ll have a solution from IFS soon, I remember adding this to the idea wall, Let me find it and send you the link.


Reply