Recommended approach for Fiori Adapt UI in S/4H On-Premise system (Customizing client) with no data

[ankurbabu]

Dear Experts,

For a client's S/4HANA greenfield implementation with Private Cloud (RISE with SAP), there are two clients in the Development system i.e. Customizing client (400) and Test Client (410). The client has decided not to allow any (test) data creation in client 400 but only in test client 410 (this approach seems standard in many projects).

To implement Fiori Adapt-UI enhancements and test Key-User Extensibility, we need those UI screens where we want to implement changes. For example, to change something on a Product (detail) screen, we need to navigate from the Products list in the Manage Product Master Data Fiori app. But without any data, this navigation is not possible.

The question is, what is the best or recommended to work on such Enhancements? Should we allow such Enhancements in the Test client which means also the possibility of creating a Transport Request where such enhancements could be locked for further systems?

Had anyone been in a similar system environment and what kind of approach was used there?

SAP Fiori Launchpad SAP S/4HANA Private Cloud @Jocelyn_Dart @MioYasutake 

[Jocelyn_Dart]

Hi Ankurbabu. We usually suggest making the Adapt UI change in the Unit Test client where you have the data - publishing it to a customizing transport request. Then use the usual transport options to copy the customizing request back to your master configuration client, from which you then transport the changes to the rest of your landscape 

Best, JD