In the SAP S/4HANA Cloud extensibility framework, once a custom field is saved using the "Custom Fields" app, its fundamental properties, such as the Field Type, are locked and cannot be changed. This is because the system prepares the metadata for the eventual generation of data dictionary (DDIC) objects upon publishing. Since the field in the scenario has not yet been published, it has not been activated in the system's repository or transported. Therefore, the correct and cleanest procedure is to delete the erroneously configured field and create a new one with the same name and the intended field type.

A. Clear and recreate the field with the same field name and the intended field type: The term "Clear" is not a standard function within the "Custom Fields" app; the correct action is "Delete".

B. Mark the field as Hidden, and create a new field with a slightly different name and the intended field type: This is an inefficient workaround that leaves an incorrect artifact in the system and prevents the use of the desired field name.

D. Change the field type by selecting the intended type in the dropdown and Save: The field type is immutable after the initial save to ensure consistency during the code and database object generation process.

1. SAP Help Portal

SAP S/4HANA Cloud

"Custom Fields" Documentation: In the section on "Editing Custom Fields

" the documentation explicitly states: "You can edit a custom field as long as it has not been transported to your production system. However

you cannot change the field type after you have created the field." This directly invalidates option D.

2. SAP Help Portal

SAP S/4HANA Cloud

"Custom Fields" Documentation: The section on "Deleting Custom Fields" states: "You can delete a custom field as long as it has not been transported to your production system." This confirms that deletion is a valid action for an unpublished field

making option C the correct procedure.

3. openSAP Course: "Extending SAP S/4HANA Cloud and SAP S/4HANA" (e.g.

s4h12)

Week 2

Unit 2: Creating a Custom Field: The course material demonstrates the lifecycle of a custom field. It shows that after the initial "Create and Edit" step where the type is set

subsequent edits before publishing do not allow the type to be altered. The only recourse for a wrong type is deletion and recreation.