Adding Custom Fields to a Fiori App Using Custom Fields and Logic

[abap_Sap]

Introduction: 

SAP S/4 HANA provides in-app extensibility and the Adaptation Transport Organizer (ATO) framework to safely create, enable and transport custom fields without modifying standard code. In this blog, I will walk through a step-by-step process to set up ATO, prepare custom fields, enable them, publish them and finally add then to a custom Fiori app.

Step 1: Initial ATO (Adaptation Transport Organizer) set up:

1. Go to transaction SCFD_EUI

2. Close the initial pop up and click on Auto Setup and following screen will populate:

3. Create below packages using SE80:

1. Local package TEST_KEY_USER_LOCAL
2. Sandbox package TEST_KEY_USER_SANDBOX

4. Now enter the local and sandbox package name and click on ‘Setup with specific data’.

5. It will then prompt you for a transport, for this first create a workbench transport and assign it in the popup to enter the transport and save your entries.

6. Input table name ‘GMGR’ and field ‘Z*’ and hit Execute:

Step 2 – Understanding Field Statuses

After execution the output screen shows three possible field statuses:

Enabled: This is already enabled and available in custom field APP

Can Be Enabled: This can be enabled by clicking Enable button in tool bar

Preparation Required: Click on Prepare button, it will show the further steps to make it

‘CAN BE ENABLED’ status.

Step3: Changing Status from preparation required to can be enabled

1. Select ZZPIAR_EMAIL and click on Prepare.

2. The message below will be shown:

3. Go to T-code SE11 and check GMGR table.

4. The field ZZPIAR_EMAIL does not have domain associated

5. Once Domain is created for this field, the status of the field will become ‘CAN BE ENABLED’.

Step4: Enabling the custom field

1. The below field ZZFINALEXP is in ‘CAN BE ENABLED’ status:

2. Select ZZFINALEXP and click Enable button:

3. Select correct enabling type and click ok:

4. Select the package and create a workbench transport and Provide Transport number at Request/Task click ok.

5. We can see that the field ZZFINALEXP status changed to ‘Enabled’ status:

Step5: Publish the custom Field

1. Go to T-code /n/ui2/flp
2. Login to FIORI
3. Execute ‘custom field’ app
4. The below screen appears, this app shows all ‘Enabled’ fields, we see ‘Final Expense’ field here which we have enabled in above steps(step3).
5. Now select ‘FINAL EXPENSE’ field and click on the arrow.

6. The screen below opens, now enable Additional selection-Grant

7. Click on publish

The field is published now.

Step6: Add Custom field to ‘Custom’ App

1. Now go to the custom app and click on ‘Adapt UI’ as shown below.

2. Now the page becomes ‘Editable’, right click on screen, we can see option add field

3. Select Final expense field here and click OK.

4. Final Expense field will be added to the screen, now click Publish and save and exit.

Conclusion:

By following these steps, you can manage custom fields using SAP’s standard extensibility framework without touching the core objects. This approach reduced upgrade risk, supports transport consistency, and aligns with SAP’s clean-core strategy. The same method can be reused for other tables and fields across S/4HANA landscape.

[MioYasutake]

@abap_Sap 

Great post! Just a quick heads-up: SCFD_EUI is actually designed to transform fields from classic extensibility into key user extensions, rather than creating them from scratch. Adding a small note about this might help prevent any confusion for your readers!