CFD_ABAP_MANAGED_FLD - Custom Fields: Messages of ABAP-Managed Fields
The following messages are stored in message class CFD_ABAP_MANAGED_FLD: Custom Fields: Messages of ABAP-Managed Fields.
It is part of development package S_CFD_ABAP_MANAGED_FIELDS in software component BC-SRV-APS-EXT-FLD. This development package consists of objects that can be grouped under "Custom Fields: ABAP-Managed Fields".
It is part of development package S_CFD_ABAP_MANAGED_FIELDS in software component BC-SRV-APS-EXT-FLD. This development package consists of objects that can be grouped under "Custom Fields: ABAP-Managed Fields".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ABAP dictionary data type &1 is not supported. |
| 001 | Use a data element with domain to specify the data type of the field. |
| 002 | Could not check field |
| 003 | Use a domain in the data element of the field to specify its data type. |
| 004 | Field can be attached to already existing custom field &1. |
| 005 | Field may be attachable to already existing custom field &1. |
| 006 | Field in database table must be moved to an extension include structure. |
| 007 | Verify that all your related dictionary objects are active and retry. |
| 008 | Identifier is not valid. Use a letter as first character. |
| 009 | Identifier &1 is already in use. Enter a different one. |
| 010 | Value help view is not valid. Correct value help view first. |
| 011 | Identifier is not valid. Use alphanumeric characters and underscores. |
| 012 | Remove field from structure &1. Do not activate changes. |
| 013 | Could not determine preparation steps |
| 014 | Field &1 disabled |
| 015 | Append field to extension include structure &1. Do not activate changes. |
| 016 | Activate all preceding ABAP dictionary changes in one step. |
| 017 | Delete emptied append structures if there are any. |
| 018 | Database table &1 is not supported in the app Custom Fields and Logic. |
| 019 | Field &1 enabled |
| 020 | Select a business context first. |
| 021 | Select a custom field to which you want to attach your database field. |
| 022 | After removal from structure &1, field will be missing in structure &2. |
| 023 | Business context &1 is not available for this field. |
| 024 | Identifier is not valid. It must be at least three characters long. |
| 025 | Field in database table must be typed using a data element with domain. |
| 026 | Custom field &1 relocated |
| 027 | Field must be typed with the same data element as custom field &1. |
| 028 | Use data element &1 to specify the data type of the field. |
| 029 | Do not risk data loss. Read details before proceeding. |
| 030 | Set up adaptation transport organizer first (transaction S_ATO_SETUP). |
| 031 | Package &1 does not exist. |
| 032 | Operation canceled |
| 033 | Internal error occurred |
| 034 | Package &1 requires a transport request. |
| 035 | Package &1 is local and thus cannot be transported. |
| 036 | Package does not fit to reserved namespace of the custom field &1. |
| 037 | Package &1 is not valid for custom field &2. |
| 038 | Append structure &1 is not transportable. |
| 039 | Field &1 could not be enabled. |
| 040 | Custom fields can only be added to workbench requests. |
| 041 | Selected task &1 of transport request &2 is not modifiable. |
| 042 | Database field and custom field must be in the same software component. |
| 043 | Core Data Services (CDS) view &1 is not transportable. |
| 044 | You are not authorized to use the adaptation transport organizer (ATO). |
| 045 | Adaptation transport organizer (ATO) is not configured correctly. |
| 046 | Remove field from structure &1. Do not activate changes. |
| 049 | Customer include &1 is not transportable. |
| 050 | How to use transaction SCFD_EUI |
| 051 | Transport request &1 does not contain a task assigned to your user. |
| 052 | Transport request or task with ID &1 could not be found. |
| 053 | Task is assigned to user &1. Please choose another task. |
| 054 | Field needs to be removed from one or more ABAP dictionary structures. |
| 055 | Remove field from Core Data Services (CDS) view &1. |
| 056 | Remove field from Core Data Services (CDS) views. |
| 057 | Field type &1 requires a value help view. Please enter one. |
| 058 | Another field with the same name &1 is also used in include &2&3&4. |
| 059 | Reference field &1 must not be contained in persistence include &2. |
| 060 | Conversion Exit &1 specified on domain &2 not allowed in S/4 HANA. |
| 061 | &1 allows only uppercase code lists. Uncheck 'Lowercase' on your domain. |
| 062 | &1 allows only uppercase code lists. Code '&2' has lowercase letters. |
| 063 | Objects on Request lead to erroneous ABAP Managed Fields (T_cd SCFD_EUI) |
| 064 | ABAP Managed Field '&1' has errors (see T_cd SCFD_FIELDVIEWER) |
| 066 | Field &1 is on allowlist for multiple business context (by &2 on &3). |