Unpeg Connected Objects (business opportunity) in an Estimate

Question

In my testing for unpegging an Estimate from a Business Opportunity, I find sometimes I can and sometimes I cannot with different Version Statuses and scenarios. When I can’t unpeg the Estimate, I get the error:
BusinessOpportunityLine. The ‘Business Opportunity Line” has already been removed by another User.

Refreshing the page does not clear this error. What is this error really mean? Are there certain parameters that must be met in order to ‘Unpeg Connected Objects’?

Thank you,

Jo

Jane Perry · Answer

Hi Jo. In regards to your question, I found the following information -

Meaning of the Error Message

The error message:

BusinessOpportunityLine. The ‘Business Opportunity Line’ has already been removed by another User.

is a backend exception generated by IFS business logic during the unpegging routine.

What it actually means: Despite the wording, this error rarely means another user physically deleted the row at that exact second. Instead, it indicates that the system's backend key lookup for the connected BusinessOpportunityLine failed or was blocked because the linked record cannot be found in an active, editable state.
Why refreshing does not clear it: Refreshing reloads the UI, but re-triggering the "Unpeg" command executes the same database PL/SQL validation against the underlying records, hitting the exact same restriction.

Key Parameters & Conditions Required to Unpeg Connected Objects

For the Unpeg Connected Objects action to succeed between an Estimate and a Business Opportunity / Line, the following parameters and business rules must be met:

1. Estimate & Estimate Version Status

Editable Version State: The Estimate Version must be in an editable status (e.g., In Progress / Draft / New).
Locked States: If the Estimate Version has been set to a locked/finalized state—such as Confirmed, Approved, Completed, or Closed—the system locks the pegging structure to prevent structural changes.

2. Business Opportunity & Opportunity Line Status

Open CRM State: The connected Business Opportunity and its lines must be in an open/active state (e.g., Unconfirmed, Confirmed, or In Progress).
Terminal States: If the Business Opportunity or Opportunity Line has been moved to a closed or terminal status (Won, Lost, Cancelled, or Closed), or if a new revision of the Business Opportunity was created and made main, the CRM line becomes read-only. When the unpeg action tries to update/decouple the CRM line reference, the validation check fails and throws the exception.

3. Downstream Transfer & Traceability Restrictions

Sales Quotation / Project / Order Linkage: If the Estimate or Business Opportunity Line has already been transferred to a downstream object (e.g., generated into a Sales Quotation, Customer Order, or connected to a Project Activity), unpegging is blocked to preserve traceability across the sales and estimating lifecycle.

4. CRM Access & Security Privileges

You must have Update permissions on both the Estimate and the Business Opportunity (including CRM Access Group filter privileges if CRM Access control is enabled for Business Opportunities in your environment).

How to Resolve or Work Around the Error

Check Estimate Version Status: Ensure the Estimate Version is set back to In Progress if it is currently Confirmed or Approved.
Check Business Opportunity & Line Status: Navigate to the connected Business Opportunity. If the Opportunity or Line is Closed, Lost, or Cancelled, temporarily reopen or adjust the state (if business process permits) before attempting the unpeg action.
Verify Downstream Connections: Check if a Sales Quotation or Project Activity was already generated from this Estimate/BO connection. If so, downstream connections may need to be removed or unlinked first.

I checked for any open bugs and found the following -

No Open Active Bug Tracked Specific to BusinessOpportunityLine Unpegging Exception
- There is currently no open, active bug ticket in Jira specifically logging the exact error message (BusinessOpportunityLine. The ‘Business Opportunity Line’ has already been removed by another User) during the Estimate unpegging flow.
- This confirms that the exception is thrown dynamically by the standard PL/SQL validation package (when the linked Business Opportunity line key cannot be resolved or is in a locked/non-editable state) rather than being caused by an active known defect in the unpegging framework.

I hope this helps. Please advise if there are any questios. Thanks! Jane