SAP Fiori: How to Troubleshoot SAP Fiori Errors?

We will actually take a look at the Troubleshoot SAP Fiori Errors and the most regularly experienced mistake while designing any Fiori Application.

Error – ‘Could not start the app due to a configuration problem’

SAP Fiori Application clients frequently experience the mistake “Couldn’t begin the application because of a setup issue” while getting to standard or custom Fiori applications.

Business Scenario

Allude to the beneath situation where you conjure Make Material Expert Application in Fiori platform. You can get to the Fiori platform utilizing exchange “/n/UI2/FLP”. Troubleshoot SAP Fiori Errors.

On the off chance that you don’t have any idea how to uncover SAPGUI Standard/Custom t-code to Fiori Application. Then, at that point, allude to Designing SAP GUI Exchange in Fiori Platform.

Click on the designed Tile of the Application and sadly it could prompt following mistake.

For amateurs, investigating such issues can be precarious, baffling and tedious as SAP Fiori advancement incorporates different foundation parts like Back-end, Front-end (Entryway), Web dispatched, UI application, and so on. On top of this, issues can be in any of these parts.

Anyway, the central issue is, from where do we begin investigating Fiori issues?

1.Frequently as an initial step, engineers can use the Well known Capability Key F12 (or right snap and select Review in the program where Fiori Application is racing) to summon front end troubleshooting and recognize in the event that issues exist in the front-end or back-end parts. In our model, no blunders are accounted for in the control center. Troubleshoot SAP Fiori Errors.

2.The following stage is to approve in the event that any mistake exists in SAP Entryway. It very well may be your front-end or back-end framework, contingent upon your passage arrangement system (Center point or Implanted).

Influence exchange “/IWFND/ERROR_LOG” to approve assuming any mistake log is accounted for in Door Administrations.

Luckily, for this situation, we see no blunders revealed.

Also Check – Course on SAP HANA

3.The following stage is to utilize exchange “/UI2/FLIA” to really look at the task of a given Expectation (semantic item – activity pair) to a Client with regards to Drain Fiori platform.

This report gives an outline of all plans for a client. It permits you to check to which authorisation job the aim is doled out and in the event that a given client is relegated to this job.

• • You can channel the outcomes from the report by gadget (like work area, portable, and so forth)

• • The default layer is the personalisation layer.

• • The check is framework subordinate. Begin the report in the framework for which you need to check the substance.

Check if “Design blunder” exists for semantic “ZMat” and Activity “Make”. For this situation no blunders were accounted for.

Then, at that point, affirm if “Customisation screw up” exists for semantic “ZMat” and Movement “Make”. For this present circumstance customisation botch is represented as shown under.

Select the blunder and snap in plain view to additionally break down the mistake message.

Detailed Error Message: “Platform ZMM/exchange/ZMM01 doesn’t exist in client 800”.

As a component of the total main driver examination step, confirm if “Personalisation mistake” exists for semantic “ZMat” and Activity “Make”. For this situation personalisation blunder is accounted for as displayed beneath, but this is like one revealed in the earlier assessment step.

4.Furthermore, engineers can likewise check Fiori Platform content utilizing exchange “/UI2/FLP_CONTCHECK”.

Here designers can channel Applications by bundles. Allow us to actually look at it exhaustively.

No error reported under Arrangement for Custom Application ZMM.

Approve something similar for Customisation. Mistake detailed as displayed beneath for the Inventory ZMM which is utilized for our custom Application.

Select the error and snap In plain view, to see the nitty gritty blunder message.

For this situation, a similar blunder was experienced in Sync 3.

Also Read: SAP Fiori: Start to finish Execution of Fiori Application

Presently, pretty much, we know the issue. Now is the right time to determine it and become the legend of great importance!

How about we grasp what Platform Job “ZMM” and Platform Example “exchange” nom de plume “ZMM01” highlight. It’s a similar Platform job and Case you design in exchange “LPD_CUST”

We can see in LPD_CUST that both Job and Example are kept up with. On the off chance that the Job and Occasion are designed, what’s going on?

Note that platform job and case are characterized in Target Planning, which can be conjured utilizing exchange/n/UI2/FLPD_CUST ( Fiori platform originator ).

Select the Objective Planning and snap on “Configure”.

We can see that Job and Example is Kept up with in Target Planning.

THEN WHAT IS THE ISSUE?

How are we veering off-track with the setup?

You want the perception force of Sherlock Holmes to address this secret.

Assuming you look at semantic planning and platform arrangement intently, you will see that the Occurrence is kept up with in Target Planning in Lower case (check the above screen capture). We really want to keep up with it in a similar case precisely according to the LPD_CUST setting.

How about we transform it to Capitalized.

Save and reload the Application. Bingo! It worked!

At the point when you get the mistake, you could feel that it is a beast. However, when you realize the main driver you could feel it is a lot of excitement about a trial matter. This is valid for the vast majority of the normal issues. The issue generally appear to be basic once we know the arrangement.

As we generally say, programming and it is not difficult to code the fix. Finding the explanation and underlying driver requires a large portion of the work and time.