To change the configuration of an APF-based application that was shipped by SAP, you must first import the corresponding JSON file as well as the text properties file into the APF Configuration Modeler. The options that are available for importing files depend on whether you use SAP Business Suite powered by SAP HANA or SAP S/4HANA.
The following video shows how to import and export configurations:
The files to be imported can either result from a configuration export or you can copy them from a shipped BSP application.
Configuration files of APF-based applications that were not created using the APF Configuration Modeler cannot be imported. You can easily recognize these configuration files because they do not contain a configuration GUID.
To import the files, proceed as follows:
During import, the content of the configuration file is written into a configuration table. The content of the text properties file is written into a text table.
If the application with the GUID specified in the JSON file does not yet exist in the APF Configuration Modeler, it is created and the description and semantic object are filled based on the information in the JSON file. Otherwise, the configuration of the JSON file is added to an existing application.
If a configuration with the same GUID already exists, you can decide whether you want to overwrite it or create a new one. You can now edit the configuration and save the changes.
If you use SAP S/4HANA, you have the following options:
Import Delivered Content
You can use Import Files to import files that result from a configuration export. The procedure is the same as described above for SAP Business Suite powered by SAP HANA.
If you want to import content that was delivered by SAP, you don’t have to copy the files from a BSP application. You can import them from the layered repository of the SAPUI5 flexibility services using the Import Delivered Content function. The configuration file of a shipped application and the text properties file in the development language reside in the VENDOR layer of the layered repository. When you import the content, it is written into the CUSTOMER layer. Changes you make to the configuration or the texts are also written into the CUSTOMER layer, so the original files in the VENDOR layer remain unchanged. At runtime, the system first checks whether there is a configuration file and a text properties file in the CUSTOMER layer. Only if there are no files in the CUSTOMER layer, is the application run from the files in the VENDOR layer.