3810734 - Radio button to enable custom namespace is disabled in Extensibility Settings – SAP S/4HANA Cloud Public Edition

• In Key User Extensibility settings, the radio button to enable a custom namespace is disabled (cannot be selected).
• Need to import custom fields developed under the same namespace from another TDD environment.
• Attempt to enable the setting is not possible as the control remains disabled.

• SAP S/4HANA Cloud Public Edition

1. Open the Extensibility Settings app.
2. Locate the custom namespace originating from another environment.
3. Attempt to set it as “my namespace” using the radio button.
4. Observe the radio button is disabled and cannot be selected.

• By design: After registering a provider namespace in a consumer system, the namespace is categorized for abapGit consumption only. The “my namespace” radio button is available only for provider-side namespaces with the “abapGit Development” category. Import of key user custom fields does not require activating this radio button and is performed via abapGit in ADT.

1. If the namespace is not yet registered in the target system, in the source system open Extensibility Settings, enable consumers for the namespace, and download the namespace installation file.
2. In the target system, open Extensibility Settings, choose Register, and upload the namespace installation file to register the namespace in consumer mode.
3. Note: The “my namespace” radio button remains disabled for consumer-registered namespaces by design; this does not block importing custom fields.
4. Install and set up the abapGit ADT plug-in (if not already installed).
5. In ADT, open the abapGit Repositories view, link the ABAP package (for example, TEST_YY1_DEFAULT) to the provider’s Git repository, and pull the custom field definitions using the abapGit Staging view.
6. Perform imports to the correct clients: import key user custom fields to client 100 (customizing tenant); import Developer Extensibilities to client 080 (development tenant).
7. If required by your process, review and confirm the conditions described for extensibility template development and namespace/prefix handling before proceeding.

• refer to: How to Transport SAP S/4HANA Key User Custom Fields Using abapGit
• refer to: Key User Extensibility and abapGit
• refer to: Preparing for abapGit Integration (Consumer)
• refer to: Preparing for abapGit Integration (Provider)
• refer to: Extensibility Settings
• refer to: 2787809 - ATO: Enable Extensibility Template Development in SAP S/4HANA Cloud, public edition
• refer to: 2838282 - What is a CB User?
• refer to: 2914822 - Develop customer extensions and export them - SAP S/4HANA Cloud Public Edition
• refer to: 3252903 - ATO: Create key user extensibility prefix to store and transfer custom field definitions in an abapGit repository
• refer to: Install and Set Up abapGit

extensibility settings, namespace, radio button disabled, greyed out, my namespace, key user extensibility, abapGit, ADT plugin, import custom fields, template provider, consumer registration, client 100, client 080, TEST_YY1_DEFAULT, TDD , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem