Error "(Un)-Publishing of Service Binding SRBV XXXXXXXXX in Customizing Client not allowed"

This error occurs when you try to use the Publish Locally button in ABAP Development Tools (ADT/Eclipse) for an OData V4 service binding inside a client configured for customizing or testing.

ADT local publishing is restricted in these clients; instead, you must publish the service manually using SAP GUI transaction /IWFND/V4_ADMIN.

How to Fix the Error

Activate in ADT: Open your Service Binding in ADT (Eclipse) and make sure it is activated, but do not click "Publish Locally". 
Open Gateway Administration: Log in to your SAP system and run transaction [/IWFND/V4_ADMIN](https://help.sap.com/docs/SAP_FIORI_OVERVIEW/9b4ee51ce91e4a9cadd5e6d43c2992ba/10ac7f6e59fa43508d486aa8997384c1.html). 
Publish Service Group:
• Click the Publish Service Groups button.
• Select your system alias (e.g., LOCAL) and click Get Service Groups.
• Find and select your Service Group ID from the list, then click Publish Service Groups again. 
Assign Request: Provide a customizing or transport request if prompted by the client settings. 
Refresh ADT: Go back to Eclipse, select your Service Binding, and press F5 to refresh

Fiori App Failed to Launch. Error Message "Could not open app. Please try again"

Problem:

Fiori App Failed to Launch. Error Message "Could not open app. Please try again"

SICF checked and Service has already been activated.
What to do?

Solution:

Run transaction /IWFND/ERROR_LOG - SAP Gateway Error Log 

Look for the user ID. 
In this case, The Service Binding 'ZQMSB_INSPECTION_LOT' is still not published yet.
Activate via ADT like Eclipse

Once published, App can be opened.

Steps to Install Eclipse for SAP ABAP and FIORI Developer

One correction before the steps: Eclipse is not the right tool for Fiori/UI5 frontend development — SAP deprecated the old SAPUI5 Eclipse tools years ago. [Certain] For Fiori you'd use SAP Business Application Studio or VS Code with the UI5 tooling/Fiori tools extensions. What Eclipse does give you is the ABAP side of Fiori work: RAP, CDS views, behavior definitions, service bindings, metadata extensions — everything backing a Fiori Elements app. If that's what you meant, the steps below cover it.

1. Install Java (usually skippable)

The latest Eclipse packages are bundled with Eclipse Temurin (OpenJDK), and ADT is validated against Java 21 — so no separate JDK install is needed. Ondemand

2. Download Eclipse

Get Eclipse 2026-06, e.g. the "Eclipse IDE for Java Developers" package from eclipse.org/downloads. Extract the zip and run eclipse.exe — no installer needed if you take the zip package. Ondemand

3. Install ADT

• In Eclipse: Help > Install New Software..., enter the URL https://tools.hana.ondemand.com/latest and press Enter Ondemand
• Select "ABAP Development Tools", choose Next, confirm the license agreements, and Finish Ondemand
• Trust the certificates when prompted, then Restart Now Sapvista

4. Open the ABAP perspective
Window > Perspective > Open Perspective > Other > ABAP. SAP

5. Create your system connection

File > New > ABAP Project. Eclipse will offer the systems from your SAP Logon (saplogon.ini) — pick your server and log in with your credentials. [Likely] You'll want SAP GUI for Windows installed first for on-prem systems, since ADT reuses those connection entries and launches GUI for classic transactions (SE11 embedded views, debugging of dynpro screens, etc.). For BTP ABAP Environment / S/4HANA Cloud, use "ABAP Cloud Project" instead with the service key or browser login — no GUI needed. Sapvista

6. Backend prerequisite (on-prem only)

[Certain] The backend must have the ADT services activated (SICF nodes under /sap/bc/adt) — on any reasonably current S/4HANA system this is already done, but if you get HTTP 403/404 errors on connect, that's where Basis needs to look.

Recommended extras from the same update-site dialog or marketplace: ABAP Cleaner, abapGit plugin for Eclipse.

For the Fiori frontend side, install VS Code + the "SAP Fiori tools" extension pack and Node.js — that's the current toolchain, not Eclipse.