3764392 - SCFD_EUI “Attach Field to Existing Custom Field” shows error “Custom Field could not be retrieved” and Guidance on Enabling Legacy Fields - SAP S/4HANA

This KBA describes an issue when enabling legacy fields via transaction SCFD_EUI and addresses related follow‑up questions.

• A legacy field exists in multiple CI includes (for example, different business contexts) and is shown in SCFD_EUI with status as “Can be enabled”. However, when attempting to enable the field using “Attach Field to Existing Custom Field” option. An error message: “Custom Field could not be retrieved” occurs.
  
  Additionally:

• Another legacy field was successfully enabled as a new custom field for one business context and is visible in the Custom Fields and Logic app. However, there is a requirement to add another business context without creating an additional database field following the Custom Fields naming convention (for example, the field name with a postfix), and to continue using the same legacy database field name across contexts.

• SAP S/4HANA
• Custom Fields

scfd_eui, attach field to existing custom field, custom field could not be retrieved, custom fields and logic, abap managed fields, add business context, business scenarios, legacy field, persistence include, ci include, enable field as new custom field, name collision, multiple business contexts, field conversion, fiori custom fields , KBA , BC-SRV-APS-EXT-FLD , Custom Fields , Problem