How To Fix /UI5/APP_DESCRIPTOR013 - No inbound defined in manifest.json with ID &1&2. Created tile with &3-&4

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI5/APP_DESCRIPTOR -

• Message number: 013

• Message text: No inbound defined in manifest.json with ID &1&2. Created tile with &3-&4

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /UI5/APP_DESCRIPTOR013 - No inbound defined in manifest.json with ID &1&2. Created tile with &3-&4 ?

  The SAP error message /UI5/APP_DESCRIPTOR013 indicates that there is an issue with the application's manifest.json file, specifically that there is no inbound defined for the application with the specified ID. This error typically occurs when you are trying to create a tile for an application in the SAP Fiori Launchpad, but the application does not have a corresponding inbound definition in its manifest.json file.
  Cause:
  
  Missing Inbound Definition: The application does not have an inbound definition in the sap.app section of the manifest.json file. Inbound definitions are necessary for the Fiori Launchpad to know how to navigate to the application.
  Incorrect ID: The ID specified in the error message may not match any defined inbound in the manifest.json.
  Manifest.json Structure: The structure of the manifest.json file may be incorrect or incomplete, leading to the inability to find the inbound definition.
  
  Solution:
  
  
  Check the manifest.json:
  
  Open the manifest.json file of your application.
  Ensure that there is an inbound definition under the sap.ui.generic.app section or the appropriate section for your application type.
  The inbound definition should look something like this:
  "sap.ui.generic.app": {
    "navigation": {
      "RouteName": {
        "target": {
          "semanticObject": "YourSemanticObject",
          "action": "YourAction"
        }
      }
    }
  }
  
  
  
  
  Define the Inbound:
  
  If there is no inbound defined, you need to add it. Make sure to define the semanticObject and action correctly.
  Example of an inbound definition:
  "sap.app": {
    "id": "your.app.id",
    "type": "application",
    "inbounds": {
      "yourInboundId": {
        "semanticObject": "YourSemanticObject",
        "action": "YourAction",
        "title": "Your Title",
        "description": "Your Description",
        "target": {
          "type": "UI5",
          "name": "your.app.view.Name"
        }
      }
    }
  }
  
  
  
  
  Check the Tile Configuration:
  
  Ensure that the tile you are trying to create is correctly configured to point to the inbound defined in the manifest.json.
  Verify that the tile's semantic object and action match those defined in the inbound.
  
  
  
  Deploy and Test:
  
  After making changes to the manifest.json, redeploy your application and test the tile in the Fiori Launchpad to see if the error persists.
  
  
  
  Related Information:
  
  SAP Fiori Launchpad: The Fiori Launchpad is a central entry point for SAP Fiori applications. Each application must have a proper configuration in the manifest.json to be accessible via the Launchpad.
  Manifest.json Structure: Familiarize yourself with the structure of the manifest.json file, as it is crucial for defining application metadata, including inbounds, routes, and other configurations.
  SAP Documentation: Refer to the official SAP documentation for more details on configuring the manifest.json and understanding the Fiori Launchpad setup.
  
  By following these steps, you should be able to resolve the error and successfully create a tile for your application in the SAP Fiori Launchpad.