Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
In the last blog we covered “Introduction - Custom Fields and Logic App capability”.

Here we will see  - "How to prepare and enable your existing custom fields in tables EBAN and EKPO and show on GUI ? "

Here in our case, we have custom fields in EBAN and EKPO.

Let's start with Table: EBAN.

Below are the custom fields we see EBAN Table.

CI_EBANDB - Custom Fields

Now as these were created in backend, we have 2 options:

Option 1. Prepare them from the backend (GUI) - Transaction code: SFCD_EUI. This transaction shows the fields that could be enabled to be used in CFL app from the backend.

This transaction also gives additional flexibility to add a custom F4 help if needed on the field when displayed on Fiori App. Fields created from this transaction can only be deleted from the backend transaction SCFD_EUI and not from CFL Fiori App.

Below picture shows the transaction:

Option 2. Create fields directly on Custom Fields and Logic App- These fields are comparatively easy to create and manage but then we won't be able to have a custom F4. These can only be deleted from this App.

For this option you can refer many blogs as well as its readily available there.


We will go with Option 1 for 2 reasons listed below:

  1. We do not want custom field names to be changed, as when we create via CFL app it also adds Suffix based on Business Context maintained in standard settings.

  2. We have custom F4 fields in our scenario.

To Prepare the custom fields in EBAN - follow below steps :

Step 1. Execute Transaction SCFD_EUI and provide the table name EBAN and run. Next screens show Field status -'Preparation Required' against the custom fields. This means we will have to prepare this field first. You may notice these fields are part of CI_EBANDB structure.

Step 2. Select any one field and click ‘Prepare’ button to get the list of steps to performed. Follow the steps in sequence to avoid any issue while activation. Below is the pop up of steps to be performed in sequence.

Step 3. After following the steps listed in the pop up the structure would look as below image. Within include structure: EBAN_INCL_EEW_PS, create the the append structure and add all the custom fields.

Please note always place custom fields within append structure.

Step 4. Now again go to transaction SCFD_EUI, provide table name as EBAN. We now see Field status as 'Can Be Enabled'. Now click the fields which you would like to enable.


Step 5. Below shows pop up details to be filled at time of Enablement of fields.

a. Text Field Enablement – Provide Semantic Type as ‘Text Field’ for a text field.


b. Field with custom F4 Enablement – Provide Semantic Type as ‘Code List’ and Value Help View as CDS Value Help view created. By click red generate icon seen on pop-up you will get the sample code of the 2 views that need to be created at the background. There are many articles on this topic available. But if further details are needed, please feel free to reach out. In my case this F4 field was for source id , that it is contained the partner systems from which the PR / PO is created.

Step 6. After all custom fields are enabled from backend. Open CFL App from the Fiori Launchpad. You will see these fields are available as below and in ‘Published’ status (green color):

Custom Fields Enabled from SCFD_EUI

Now 60% of our Task is done 😊

Pending step are custom fields in EKPO and making all these fields visible on the CFL screens. From this step onwards we will work on CFL App on Fiori Launchpad

Step 7. Now we want same fields in Table EKPO as well, for this do not manually create fresh fields again only delete the old custom fields in CI_EKPODB and CI_EKPODBX and activate structures.

Step 8. Now for creation of fields, we just need to do an additional step on CFL app. Activate Business Scenario, so that same fields are available in EKPO Table.


Step 9. After Step 8, we will start seeing 2 fields one for PR and other for PO, all the PO custom fields will be visible under Business Context – ‘Procurement: Purchasing Document Item’


Step 10. For all the PR custom fields, go to UI and Reports Tab and ‘Enable Usage’ of Purchase Requisition GUI and click on Publish

PR Fields

Available under UI and Reports Tab

Below screenshot shows how custom fields appear on Standard Transactions Purchase Requisition after enabling:

Transaction - ME53N Item Details

Step 11. For all the PO custom fields, go to UI and Reports Tab and ‘Enable Usage’ of Purchase Order GUI and click on Publish

Available under UI and Reports Tab

Below Screenshot shows, how fields appear in PO screen.

Transaction - ME23N Item Details


How the F4 looks when the fields are enabled for the GUI:  For F4 functionality multiple blogs are already available and can be referred, so not touching that topic here. However, if requested can create a new post detailing the same.

F4 on the custom field


Limitations of CFL fields:

  • No control of the Screen layout or screen visibility where Custom Fields are displayed on GUI like we had for custom field displayed on custom screen.

  • The tab where custom fields are displayed is displayed as ‘Custom Fields’, this can’t be renamed.

  • The fields get displayed in sequence we publish them on the GUI.

So now we know about how to enable existing custom fields in standard table as custom fields and publish them to the GUI. We also have identified the limitations we see so far. However we do hope to get features added in upcoming releases as its still evolving.


Hope , it was helpful. Suggestions and questions are welcome !! 😊

Next Blog: How to publish the custom fields on Standard Fiori App.