A custom SQL event trying to update a Customer's credit limit hits ORA-20115 ('Customer Info has already been removed by another user'), even though nothing else is touching the record. Why?

All FAQ questions / Finance

Answer

Credit Limit isn't actually stored on CUSTOMER_INFO — it lives on CUSTOMER_CREDIT_INFO (the Credit tab), so a MODIFY__ call against CUSTOMER_INFO_API silently does nothing useful to it and can surface this misleading concurrency error instead. Target CUSTOMER_CREDIT_INFO_API.MODIFY__ for that field instead, remembering that the Credit tab is company-specific (so Company needs to be in your key attributes) and that you need the current OBJID/OBJVERSION from CUSTOMER_CREDIT_INFO_CUST for the update to succeed.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Finance questions