Could not open app – SAP Fiori

In continuation to my previous blog cannot load tile – SAP Fiori, I continue discussion the other error we faced after the upgrade of S/4HANA system from 1511 to 1610.

“Could not open app. Please try again later”.

could not open app

Troubleshooting steps:

Ensure that the following steps are taken care off after the upgrade:

  1. Review OSS note 2346431 – SAP S/4HANA 1610: Release Information Note (https://launchpad.support.sap.com/#/notes/0002346431) and apply all the recommended notes mentioned for the target FPS/SPS level you just upgraded to. As a suggestion, apply all SAP_ABA, SAP_BW, and SAP_BASIS to both Frontend and Backend. While S4Core are only for backend.
  2. Ensure the scheduling of report /UI5/APP_INDEX_CALCULATE is running and if not, please schedule and run the job.
  3. Ensure the scheduling of report /UI2/GET_APP_DESCR_REMOTE is running and if not, please schedule and run the job.
  4. Ensure the following reports are also run in the Frontend Server:
    a. /UI2/CHIP_SYNCHRONIZE_CACHE
    b. /UI2/DELETE_CACHE_AFTER_IMP

If this does not solve your issue, jump to next steps:

Create RFC destinations as per SAP note SAP Note 2269272 and Replicate App Descriptors from Back-End System.

Check again if your app works. If not continue with next steps:

Compare the App details from the app launcher with the details on the SAP Fiori App Reference Library. 

App launcher url looks like:

<http/s>://mys4hanasystem<HTTP/HTTSport>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html

On app launcher, you  should find the Odata (/n/iwfnd/maint_service) and ICF service (SICF) details for the app that should be active on the front end server:

app launcher

Ensure that the SICF services are active and you are able to test it successfully and also the odata service is active and mapped to right System Alias.

Odata:

odata service

Note: Service here points to local system alias as I have my front end and back end configured on the same application. Please check correctness of your alias to be used.

SICF:

sicf.png

If you are not able to find the services for the app, its time for an incident towards SAP.

Please let me know if this solves your issues or if you have any questions in the comments below.

 

GDPR for SAP – Are you ready?

Everyone keeping track of GDPR Clock should be already gearing up for compliance. Because the consequences of non-compliance could be damaging.

Under the new law, Personal data of your customers can only be gathered legally under strict conditions. Processing/handling/archiving/deleting this data should also be handled under strict rules.

We are part of Brexit! We do not have offices in EU countries! I do not know if this applies to us! By when should we be compliant!

You can find the answers to these questions at FAQ’s and Timelines.

It applies to everyone who is processing/using any data for customers from EU.

So even if you do not have a office in EU but do business with EU customers, you are in purview of GDPR.

When it comes to SAP, you should be thinking of but not limited to following aspects of Data.

  1. Any personal data of your customers should be secured. This includes from their official title (CEO/CFO/Director etc..) to their postal code. Make informed decisions.
  2. Be prepared to secure the data in you system already. Prevent unauthorized access to this information. Many might think this only applies to production systems, which is incorrect. Personal data in your Pre-Prod, Test, Development etc.. all are considered sensitive.
  3. Data should be archived/deleted unless it is absolutely required. Archived data should be safeguarded from unauthorized access.

This of course is a complicated and time taking process. But the great thing is there are already multiple tools readily available in the market which can completely automate this process.

Since we are talking about SAP, I would like to bring some of these tools to your notice which can help you make your SAP systems compliant.

  1. Lets start with Basics and the most crucial aspect. Check your authorization matrix. Ensure that only people who need access to personal data has access. Use tools like SAP GRC to  control authorizations, manage/mitigate/document risks.
  2. Protect the data in your non-production systems. Strict authorization controls on your non-production SAP system. Use tools that scramble test data in non-production systems. Some examples include, SAP TDMS and DATA Secure by EPI-USE. Another interesting tool could be SAP Field Masking Solution.
  3. Handle the data in your production system wisely. Archive or delete your data that is not necessary. Use tools like SAP ILM to manage the life cycle of your data.

Above are just some actions for compliance. There is much more to this than just using the tools like, appointing a Data Protection Officer (DPO), Legal advise etc..

Please share your experience regarding GDPR under comments.

 

Important SAP Notes:

2616471 – Data Protection and Privacy Features for SuccessFactors Reporting & Analytics

2649596 – GDPR Technical Basic Check

2579631 – GDPR (General Data Protection Regulation) in HCM