Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Hi All,


This blog intends to educate customers and partners about why they should avoid editing custom forms from UI or uploading custom forms downloaded from UI. This is a frequently encountered scenario and below are the relevant details related to the same.


You can edit a custom form in the SAP Cloud Applications Studio (Studio). You can also edit it in the Form Template Maintenance work center. However, the impact of the two cases is different. When a custom form is edited from the Studio, the changes are stored in the solution branch. Whereas when a form is edited from the UI, the changes are stored in a separate branch called customer branch.

The main problem that you might face is the loss of changes that you have made in custom form using the Form Template Maintenance work center in the UI. You will have to make the same changes again in the Studio. Therefore, we recommend that you use the Studio to edit custom forms.


The image below shows the Form Template Maintenance work center:


The image below shows the XDP file which can be edited from the Studio:


We recommend that you do not edit custom forms from the UI for the following reasons:

  • During activation of FTHD (form template header file) file, the corresponding XDP files are cleaned up. And the clean-up ultimately fails because of customer branch. The only way to proceed is to remove the customer branch.

There can be following possibilities:

    • Solution is in development: When this issue happens for an in-development solution, there is no way we can proceed for assembly without removing this customer branch. Removing this branch also removes changes done corresponding to it.

    • Solution is assembled or deployed: In this case, there can be an issue while creating patch. Also, every time tenant copy is triggered, manual correction must be done in target tenant every time or corrected once in source tenant.


  • Secondly, this increases the maintenance load. Incidents related to this issue are encountered frequently and many of them have very high priority. So, every time you make a change from the UI, a customer branch is created that stops the activation leading to incident creation.


We have already communicated to customer and partners to edit forms from the Studio only and not do from the UI. However, a lot of incidents are raised and we have to correct them manually. In addition, customers and partners have concerns about data loss corresponding to the files being corrected. So, it is better to avoid this behavior and consider editing forms from the Studio itself.


Best Regards,