Error at deploy app to fiori launchpad in different subaccount

[carlos_venturo]

Hello gurus,

Here is the scenario, we have develop some sapui5 apps in a subaccount of SCP called DEV, now we want to deploy this apps in a TEST subaccount.

We use the GIT service to do so, but the thing is that when we cloned the project in the TEST subaccount, and try to deploy it , there is an only choice to deploy once again like an update version to the DEV subaccount.

The second problem is that when we tried to register the app to the fiori launchpad the follow error occurs.

"The application you selected cannot be registered to the SAP Fiori launchpad because it was previously deployed to a different SAP Cloud Platform account."

I understand that maybe this is real problem if we tried to register the same app to the same subaccount, but we are talking about separeted subaccounts, with a different portal service as well.

The trust is configured to custom fyi.

Is there a way to archive a simple scenario to develop the app in DEV and just pull it to TEST ?

Greetings.

[pjcools · Accepted solution]

Hi Carlos

No - export and import option is not within SAP Web IDE. It is at the HTML5 app level. Go to the Applications -> HTML5 applications area, select the app itself (to go into the detail) and then choose [Export] from the Actions menu. That will download the application as a ZIP file.

Navigate to the new (TEST) subaccount and select Applications -> HTML5 applications and choose [Import from file]. Locate / Browse for the app file you just downloaded from the DEV subaccount, the Application name should be populated automatically. Update the version number and select Import.

The last step is to Activate it (if it is not already) and then go to the Portal site service and add the new application to the FLP. Ideally, the FLP from DEV should be migrated through to the TEST subaccount so all of the applications and settings line up. Then it is a case of updates to applications rather than deploying them and adding them into the FLP in each subaccount which is not really efficient.

Hope this helps some.

Thanks & Kind Regards

Phil Cooley

[Ivan-Mirisola]

I am not sure if this is what you want to achieve:

https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/f16cd5b03b8e4ba39a1328b15bd...

But it is my understanding that your application is deployed on one sub-account and you want to use the same application on another sub-account. If this is the case, there is no need to deploy the application twice. All you need to do is subscribe to your applications on the sub-account. That way you can keep your app centrally deployed while treating it as multi-tenant (each sub-account in Neo is a tenant to the application).

Best regards,
Ivan

[carlos_venturo]

Ivan,

Thanks for the answer, i will try your solution, but the main reason to have DEV and QAS subaccount is to separate the developing and testing .

If i subscribe to the DEV app in QAS subaccount, when i change the dev app, it will automatically change in QAS?

Thanks again

[Ivan-Mirisola]

Hi Carlos,

I now understand what you are trying to accomplish here.

I believe that what you need is to do is the following:

1) Export the HTML5 application source

2) Create an MTA project in Neo (I'd recommend using a different name for the html5 module).

3) Import the source code into the html5 module folder

3) Make the MTA with the mtabuilder to make it deployable via Neo's Solution menu.

4) Deploy the MTA on your QAS sub-account.

Detailed instructions can be found o this blog.

This could be optimized for Continuous Integration solutions since it uses the Neo's SDK to build the MTA and deploy it:

https://developers.sap.com/belgie/tutorials/ci-best-practices-fiori-sapcp.html

https://blogs.sap.com/2019/01/22/ci-cd-for-sapui5-on-scp-neo-with-gitlab/

Best regards,
Ivan

[carlos_venturo]

Ivan,

Your answer was very helpful also.

Greetings.

[rachit_sharma7]

Hi Carlos,

We had the same problem as we also have different Fiori launchpad site configured for Dev and QAS subaccounts. We were able to deploy the app(lets call it Test) on QAS FLP site by doing the below steps:

1. Exporting from Dev subaccount and importing the Test app on QAS as mentioned above by Phil

2. The imported Test app had Dev's subaccount name in the WebIDE

3. We created a new project in QAS workspace and copied all content from the imported Test app

4. When we went to activate it, it showed us the QAS subaccount just like we wanted and were able to activate this app.

I am not a developer but rather a Basis guy so might not be using the correct terminology when it comes to performing the above tasks. But I hope this gives you the right direction to deploy the app on QAS subaccount.

Thanks

Ricky

[pjcools]

Hi Carlos

I've tried a number of options over the years but the simplest method I still find is the simple Export / Import option. This is by far the easiest and makes sense to me because of the following:

- Development activities are kept to the DEV subaccount. That is, you don't need to startup SAP Web IDE Multi-Stack in each of the subaccounts so development is kept traditional and only in DEV.

- The Export/Import method is quicker than retrieving the code from GIT and then publishing to the subaccount.

- If you keep the same Destination name then you don't need to change anything to make the application work.

The only additional step which you need to do is to refresh the HTML cache for the portal site but this is required even if publishing the app from the GIT repository.

Hope this helps!

Kind Regards

Phil Cooley

[carlos_venturo]

Hello Phil, thanks for the answer, by importing/exporting you mean to do it at SAP Web IDE?

i've tried this aproach but when i tried to deploy the app, it only give me the option to update the app in the "dev" subaccount,

Beside this, if i tried to register the app to the portal of the QAS subaccount, it says that the app is already register in other subaccount which its true, but i am trying to have a DEV fiori launchpad and a QAS fiori launchpad.

So there is my the dilema, it seams that i cant deploy or register the app, and the only option is to create a new app with different id. witch its really but reaaaaally ineffcient.