3731086 - Cannot add Opportunity Extension Fields to “Convert to Opportunity” Quick Create

• Two PDI fields on Opportunity header (ABC, XYZ a custom OVS that filters XYZ based on ABC) work on the Opportunity TI and standard Opportunity creation.
• During Lead → Opportunity conversion, the "Convert to Opportunity"Quick Create dialog has no anchor/Add Field, so these fields cannot be added or captured there.

SAP Cloud for Customer

1. Open any Lead and click Convert to Opportunity to open the Quick Create (QC).
2. Start Adaptation (Key User).
3. In the QC header, try Add Field and search for your Opportunity Root extensions (PDI/KUT).
4. Observe: No “Add Field” option/anchor is available; the fields cannot be placed in this QC. (Contrast: the same fields can be added on the Opportunity TI.)

SDK verification (UI Designer)

• Open the conversion QC component in UI Designer and check Extensibility Explorer for the view.
• Observe: No extensibility anchors are provided in UI Designer for this QC either.

The Lead → Opportunity "Convert to Opportunity" Quick Create (QC) has no UI extension anchor for Opportunity.Root. Therefore, Opportunity Root extension fields (PDI and KUT) cannot be placed in this QC. This is expected system behavior and independent of the field data type or attached OVS.

• Option A — Capture on Lead and transfer during conversion (recommended)
  • Create matching fields on Lead (PDI or KUT) for the same semantics.
  • Place them on Lead TI/QC so users enter values before conversion.
  • Transfer values to Opportunity at conversion:
    • SDK: In Opportunity Root BeforeSave/OnSave, detect "created from Lead" read the two Lead fields, and set the Opportunity fields.
• Option B — Default on Opportunity from Lead context (no entry on Lead required)
  • SDK only: In Opportunity Root BeforeSave, if created from a Lead, default the two fields from the source Lead (e.g., via predecessor reference).
  • Users see both values on the Opportunity TI immediately after creation.

• None of the above will make the fields appear in the standard conversion QC; there is no anchor in the current release.
• Your OVS dependency (XYZ filtered by ABC) continues to work on the Opportunity TI once values are mapped/defaulted.
• SAP Support does not provide consulting or custom development for SDK/ABSL. The SDK options described are guidance only, offered because the standard UI does not allow adding Opportunity Root extensions to the conversion Quick Create. 

lead to opportunity, conversion screen, ui designer, missing anchors, no anchors, extension fields, pdi, sdk, kut fields, adaptation, opportunity extension, COD_Mkt_Prospect_Convert2Opp, extensibility explorer, screen not extensible, add fields to conversion screen , KBA , LOD-CRM-OPP , Opportunity Management , Known Error