How to use transaction SCFD_EUI

What causes this issue?

To use your existing database fields in the SAP Fiori app <ZK>Custom
Fields and Logic</>, you need to enable them using the SAP GUI
transaction <LB>SCFD_EUI</>.

System Response

Once enabled for the SAP Fiori app <ZK>Custom Fields and Logic</>, the
fields are available in the app together with any newly created custom
fields, and can be added to SAP Fiori UIs and reports, form templates
and email templates as well as business scenarios in the same way like
custom fields.

How to fix this error?

On the start screen, you can restrict the selection of your database
fields by name of the database table and by field name. By default, the
field name selection is restricted to the standard customer namespace
patterns <LB>ZZ*</> and <LB>YY*</>. If your company uses, for example, a
dedicated ABAP namespace, this restriction can be added as well.
Press <PF>F8</> to display the resulting list of fields which were added
to database tables using append structures or customer includes. The
<LS>Field Status</> indicates whether a field can be enabled directly,
whether it needs to be prepared beforehand, or whether it has already
been enabled. When selecting a field, corresponding functions are
offered as buttons in the tool bar depending on their status:
<LB>Can Be Enabled</>: You can enable this field directly by clicking
<PF>Enable</> (see step 3 below).
<LB>Preparation Required</>: The field does not yet fulfill at least one
of two requirements for enabling. Either it needs to be moved from its
current location to an extension include structure first, or it needs to
be typed using a data element with domain, or both. Click <PF>Prepare</>
and follow the instructions given there (see step 4 below).
<LB>Enabled</>: The field has been enabled already.
If required, you can change its package assignment by clicking
<PF>Relocate</>.
If you do no longer want to use the field in the SAP Fiori app
<ZK>Custom Fields and Logic</>, you can remove it by clicking <PF>Di
sable</>. The field will then also be removed from the UIs, reports,
form templates, etc.to which it was added with the help of the app
<ZK>Custom Fields and Logic</>. The database field itself remains
untouched.
<LB>Cannot Be Enabled</>: The field either does not reside in a database
table which was prepared by SAP for use in the app <ZK>Custom Field and
Logic</>, or its ABAP dictionary data type is not supported by the app.
<LB>Enabling...</>/<LB>Disabling...</>: The field is currently being
enabled or disabled respectively. This process may take a few moments.
<LB>Enabling Failed</>/<LB>Disabling Failed</>: If enabling or disabling
failed, you can retry the operation by clicking <PF>Enable</> or
<PF>Disable</> again. If the issue remains, report an incident to the
component BC-SRV-APS-EXT-FLD.
<LB>Undefined</>: The field status could not be determined by the
system. Report an incident to the component BC-SRV-APS-EXT-FLD if this
issue persists.
To enable a field with status <LB>Can Be Enabled</>, select the field
and click <PF>Enable</>. A dialog with the following input opens:
<LS>Enabling Type</>: If your database field is only relevant for one
database table and its corresponding business context, the default value
<LS>Enable Field as New Custom Field</> is the right choice.
If another database field with a different name but the same data
element has already been enabled, both options, <LS>Enable Field as New
Custom Field</> and <LS>Attach Field to Existing Custom Field</>, are
available. If both fields have the same meaning and type of content, or
even a data transfer has already been established between those fields,
it is recommended to choose the option <LS>Attach Field to Existing
Custom Field</>. If the fields are independent from each other, choose
option <LS>Enable Field as New Custom Field</>. Once you have attached
this field to the existing one, both fields appear in the SAP Fiori app
<ZK>Custom Fields and Logic</> as one custom field which was added to
different business contexts. In the app, in case a business scenario is
available which connects these business contexts, you can establish a
data transfer from one database field to the other by enabling the usage
of the fields in this business scenario.
<LS>Custom Field ID</>: This is the unique identifier for the field in
the SAP Fiori app <ZK>Custom Fields and Logic</>. A proposal for this
identifier is derived from the database field name, but you can
overwrite this proposal using alphanumeric characters (also lower case
letters) and underscores. If you add the field to business scenarios
with the help of the app, the identifier will also be used as field name
in the business contexts which did not contain your field before.
<LS>Semantic Type</>: This attribute defines the nature of the field
content in general and how the field is to be displayed on an SAP Fiori
UI. The semantic type corresponds to the field type in the SAP Fiori app
<ZK>Custom Fields and Logic</>. The offered types depend on the ABAP
dictionary data type of the field.
If the field domain contains <LS>Fixed Values</> or if the field refers
to a <LS>Check Table</>, the default value for the semantic type is
<LB>Code List</>. When you choose this type, a corresponding <LS>Value
Help View</> is required.
If the ABAP dictionary data type has a clearly defined purpose like
<ZH>Date </>or<ZH> Time</>, its semantic type is set accordingly and
cannot be changed.
<LS>Value Help View</>: If the semantic type of your field is <LB>Code
List</>, <LB>Currency</>, <LB>Language</> or <LB>Unit of Measure</>, a
value help view is required to retrieve the fixed values which are
stored in the field domain directly or in a referenced value table. This
view is used as soon as the field is added, for example, to SAP Fiori
UIs and reports using the SAP Fiori app <ZK>Custom Fields and Logic</>.
If available, the system proposes a standard value help view like
<LB>I_LANGUAGE</> for the semantic type <LB>Language</>.
If not available, or if the standard view does not fit to your needs,
you can create templates for such a view and its corresponding text view
by clicking <PF>Generate</>. Copy these templates to new <ZK>Core Data
Services (CDS) Data Definitions</> in <ZK>ABAP Development Tools for SAP
NetWeaver (ADT)</> and replace the variables in angle brackets with
suitable values. You may change the data sources or apply WHERE
conditions to the views to restrict the allowed values. <ZH>Aliases,
associations and annotations must not be changed.</>
<LS>Package</> and <LS>Request</>: Upon confirmation of the dialog (
<PF>F8</>), you are prompted to enter a package and a transport request
for the objects which are being created by the system to enable your
field for the SAP Fiori app <ZK>Custom Fields and Logic</>. Make sure
that these objects (including any newly created value help views) are
kept in the same software component as the append structure with the
database field itself, and that they are always transported together.
To prepare a field with status <LB>Preparation Required</>, select the
field and click <PF>Prepare</>. A dialog opens with step-by-step
instructions on how to fulfill the requirements. As soon as you have
executed these steps, the field status changes to <LB>Can Be Enabled</>.
If the database table is associated to more than one business context,
you need to select the business context beforehand, which fits to the
selected database field<ZH>. Please note that this decision cannot be
revoked as soon as the field has been enabled.</>
After enabling, and before the app <ZK>Custom Fields and Logic</> is
used to add the field to UIs, reports or email templates, please check
whether your database field was added manually to any <ZK>Core Data
Services (CDS) Data Definitions</> delivered by SAP. If this is the
case, and if these <ZK>Data Definitions</> appear in the app <ZK>Custom
Fields and Logic</> as <LS>Data Source</> for your field, it is
recommended to remove the field using <ZK>ABAP Development Tools for SAP
NetWeaver (ADT)</>.

Procedure for System Administrators

Prerequisite for field enabling is that the <ZK>adaption transport
organizer (ATO)</> has been set up in this system. If this has not been
done yet, click <PF>ATO Setup</> on the start screen and follow the
instructions given there.

Error message extract from SAP system. Copyright SAP SE.