SAP Community - SAPUI5

cannot select the data from the list of our previous entries in SAP FIORI

2026-06-10T18:20:23.152000+02:00

we can populate the fields in SAP Fiori if we add them manually, but the problem is that we cannot select the data from the list of our previous entries in SAP Fiori

F0366 - My spend new app - Need to change period from Month-to-date to Year-to-date

2026-06-10T19:14:15.680000+02:00

Hi SAP community! 👋

I'm currently working with the Fiori app F0366 – My Spend (new version) and I'm trying to figure out if it's still possible to switch the period view from Month-to-Date to Year-to-Date.

📌 Maybe I'm wrong, but seems this option was available in the older version of the app, but I can't seem to find it in the new one.

A few questions I'd love to get input on:

Has this option been removed or relocated in the new version?
Is there a configuration or personalization setting I might be missing?
Could this be related to a role/authorization restriction?
Any workaround or alternative app that provides a Year-to-Date spend view?

Would appreciate any feedback from those who have worked on this app, whether from a functional, Basis, or Fiori/UI5 perspective. 🙏

S/4 HANA On-premise 2023 SP02

Fiori Tools Extension Pack in Cursor

2026-06-11T07:04:23.563000+02:00

Hi, I'm trying to use the SAP Fiori Tools Extension Pack in Cursor, but it seems that the extension pack (and its dependent extensions) are not available because they are not published in the Open VSX Registry, which Cursor relies on for extensions.

Has anyone found a way to install SAP Fiori Tools in Cursor, either manually or through an alternative extension source?
I'd appreciate hearing about any workarounds, custom installations, or experiences using Cursor for SAP Fiori development.

Thanks in advance!

Production Logging Strategy for Client-Side UI5 Application Deployed on SAP BTP

2026-06-15T06:49:06.806000+02:00

We are building an app using Ui5 freestyle that acts as a side-by-side extension in Sales and Service Cloud Version 2 (SSCv2).

Our goal is to add logging features to the app to assist developers in debugging and troubleshooting issues in the production environment.

Since we are not creating any backend services, we cannot utilize the Cloud logging services in BTP. This app is purely a client-side Ui5 application.

Could you please advise on how to implement logging within our app so that developers can access the logs when the app is deployed on BTP and running in SSCv2 as a mashup

Issue dynamically hiding a column in an adaptation project

2026-06-15T12:13:44.128000+02:00

Hello,

I'm working on an adaptation project for a custom app I've developed in RAP with annotations. My requirement is to hide columns of a table created through annotations according to the value of virtual fields.

Unfortunately as I've seen in other posts that using a boolean virtual element with a LineItem.hidden(#virtelementname) doesn't work, so I've moved to an adaptation project. My approach is to read the virtual fields from the odata4 model through typescript, get the columns from the table through and hide them through setVisible. This is the function that I attach this to the event modelContextChange of the table (the columns are visible for some objects and invisible for others) in the code file generated by the adaptation editor.

	setColumnsVisible = async function (this: ControllerExtension, table: Table ) {
		const bindingContext = this.getView().getBindingContext();
		if (!bindingContext) {
			return;
		}
		const path = `${bindingContext.sPath}`;
		const context : Context = this.getView().getModel().bindContext(path);
		interface VisibilityResponse {Column1Hidden: boolean; };
		const res = await context.requestObject() as VisibilityResponse;
		const columns: Column[] = table.getColumns();
		const columnToHide = columns.find( curr => curr.getPropertyKey().includes("ColumnToHide") );
		columnToHide.setVisible(!res.Column1Hidden);
	};

The result of this is that when Column1Hidden is true the label of the column is hidden but the values are still there. My objective is to hide the whole column including the values.

As a sidenote, just for kicks I tried getting the index of the column, removing it from the table with removeColumn, setting visible to false (on the column) and inserting it back at the right index, it didn't work either. I also tried to call invalidate() on the Table and Column controls after setting the visibility (in case it's evaluated during rendering) and still no luck.

Does anybody have any ideas how to achieve this?

Thanks,

Ben

Werb Service PW-SELF-SERV missing in system

2026-06-15T15:42:57.119000+02:00

Hello Support Team,

In our system Webservice (T-Code: SICF) WD_PW_SELF_SERV service is missing.

Please guide to solve the issue.

Thank you in advance for your support

Shujah

Story report - formula functions - Day of Week

2026-06-15T17:35:25.096000+02:00

Hi there,

In Canvas report, I have a column with a calculated formula to get the Day of Week from the date, I am trying to replicate the same in Story report, but have no function for that. May someone knows a workaround formula to bring this calculated column?

ODATA - FML_UPLMATINVPR_SRV usage

2026-06-25T12:53:41.786000+02:00

Hi Team ,

We would like to integrate this functionality directly from the SAP backend (ABAP) using the odata service - FML_UPLMATINVPR_SRV without using the Fiori UI. Specifically, our requirement is:

Read an existing Excel file stored within SAP (e.g., MIME repository / application server)
Pass the file content programmatically to the OData service
Trigger the same processing flow (upload → validation → batch → post)
Is it supported to use the OData service FileContentForUploadSet in a backend-driven scenario where:
The Excel file is not uploaded via Fiori UI
Instead, the file content (XSTRING) is read directly from SAP repository
And sent programmatically via HTTP client (CL_HTTP_CLIENT) or similar framework?

Thanks & Regards

Ritushree

Saving Variants and Layouts after upgrade

2026-06-26T12:01:59.791000+02:00

Hi Team,

We are currently in process of upgrading our existing S/4 Hana from 2022 to 2025 Version. As end users have created multiple Variants (Public and Private) and layouts in Fiori, Webdynpro and GUI applications in Launchpad.

Could you please let us know, how we can make sure that variants and layouts are not impacted post Upgrade?

Additionally, if possible , can we save these old variants and layouts in the 2025 Version?

Fiori Elements V2 (Adaptation Project) – Need to enforce mandatory field validation before Save/Appl

2026-07-01T02:02:00.292000+02:00

Hello SAP community,

I am working on a Fiori Elements V2 application (Object Page / List Report) using an Adaptation Project (SAP BAS – codeExt Controller Extensions + UI Adaptation).

I am trying to enforce a business requirement where a specific field must be mandatory before saving the document.

Technical Context

Application: Standard SAP Fiori Elements V2 app (Object Page)
Extension approach: Adaptation Project (no full custom controller, only Controller Extensions via codeExt)
Backend service: OData V2 service
Field source: Edm.Decimal field in OData entity
Field name: NoDaysReminder1
Annotation applied:

com.sap.vocabularies.Common.v1.FieldControl = Mandatory

Field also appears inside a FieldGroup in Object Page sections.

Observed Behavior

The field is displayed as mandatory in the UI (red asterisk appears correctly).
However, the application still allows saving the document when the field is empty.
No frontend validation blocks the Save/Apply action.

What I already tried

1. Controller Extension (codeExt)

I attempted to override lifecycle hooks in the Object Page extension:

beforeSaveExtension
onAfterRendering
Custom validation logic

However, none of these hooks are triggered during Save/Apply in this Adaptation Project context.

2. UI interception attempts

I also tried:

Intercepting the Apply button (OverflowToolbar / DOM inspection)
Using event delegates on SmartField/Input controls
Using extensionAPI and TransactionController

None of these approaches allowed reliable interception of the Save event.

3. Metadata analysis

The OData metadata shows:

<Property Name="NoDaysReminder1"
          Type="Edm.Decimal"
          sap:field-control="NoDaysReminder1_fc" />

The field is NOT marked as Nullable="false", so from a service contract perspective it is optional.

Key Issue

It seems that:

FieldControl annotation only affects UI behavior
OData V2 service contract allows null values
Fiori Elements V2 does not expose a supported Save-interception hook in Adaptation Projects

Question to the community

Given the limitations of Fiori Elements V2 Adaptation Projects, what is the recommended SAP-supported pattern to enforce mandatory field validation BEFORE Save/Apply for a standard Object Page?

Specifically:

1. Is there any supported Fiori Elements V2 extension point (within Adaptation Projects / codeExt) that allows intercepting or validating the Save/Apply action?

2. If frontend-only enforcement is not supported, what is the recommended SAP backend approach for enforcing mandatory business validation in OData V2 services (e.g., BAdI, enhancement spots, gateway validations)?

3. In standard SAP design, should FieldControl be considered only a UI indication, or can it ever enforce transactional validation without backend support?

Additional context

This requirement is strictly frontend-driven at the moment, as backend modifications are currently uncertain or restricted.

Additional technical detail:

The application is part of SAP standard S/4HANA Fiori Elements V2 (Object Page) and is extended via SAP Business Application Studio Adaptation Project.

The extension is limited to controller extension artifacts generated via @SAP-ux/adp tooling (codeExt), meaning:

- No full override of standard controller lifecycle
- No access to Fiori Elements internal Save lifecycle hooks
- Limited access to extensionAPI hooks only

I am trying to confirm whether this is a limitation of the Adaptation Project framework or a misunderstanding of the available extension points in Fiori Elements V2.

Any clarification from SAP experts or official pattern references would be highly appreciated.

Issue in Fiori Apps in selecting the value from the History

2026-07-01T03:34:09.401000+02:00

We have been having this issue recently where value is not getting populated in the input field when selecting the value from the History.

Does Accessing Applications Hosted in HTML5 Application Repository Incur Costs?

2026-07-01T16:42:59.290000+02:00

We are trying to better understand the licensing model for applications hosted in the HTML5 Application Repository.

Does accessing an application deployed in the HTML5 Application Repository generate any licensing or usage charges by itself?

If so:

Which SAP BTP service is responsible for the billing?
How is the usage measured (e.g., requests, active users, connections, storage, runtime, etc.)?
Is there any difference in the billing model when the application is accessed through a custom AppRouter instead of SAP Build Work Zone?

The reason for this question is that we are evaluating replacing SAP Build Work Zone due to the high licensing costs associated with external user connections. We would like to understand whether using the HTML5 Application Repository directly would avoid those charges or simply shift the costs to another BTP service.

Any clarification or references to the official SAP documentation would be greatly appreciated.

Existe forma de registrar no DRC(Public) notas históricas já autorizados em outro sistema?

2026-07-01T20:25:48.780000+02:00

Olá, pessoal!

Estou passando por uma situação no SAP S/4HANA Cloud Public Edition (release 2602) no Brasil, e chegamos em um cenário que não encontramos documentado em nenhum lugar. Se alguém do time de DRC puder ajudar, agradeço muito.

**Cenário**
O cliente operava em um sistema legado (não-SAP) antes desta implantação. Esse sistema legado emitiu e transmitiu notas fiscais de saída (NF-e modelo 55) que já foram autorizadas pela SEFAZ em períodos fiscais anteriores (ou seja, já possuem chave de acesso, protocolo de autorização e XML autorizado pela SEFAZ).

O cliente agora precisa que esses documentos históricos apareçam no monitor fiscal do novo sistema S/4HANA Cloud Public Edition (app Administrar Documentos Eletrônicos / SAP Document and Reporting Compliance, opção de faturamento de saída para o Brasil) — unicamente para fins de registro interno e continuidade de auditoria. Não queremos retransmitir esses documentos à SEFAZ, já que eles foram autorizados sob uma numeração/série diferente, gerada pelo sistema legado.

**Perguntas**
1. Existe algum relatório, app ou objeto de migração padrão para registrar documentos de saída (NF-e e possivelmente CT-e/NFS-e) já autorizados, no monitor DRC do Brasil, sem disparar transmissão à SEFAZ?
2. A funcionalidade "Upload Electronic Documents to eDocument Cockpit" (documentação DC_NFe) se aplica a esse cenário, ou tem outra finalidade?

Qualquer indicação — documentação oficial, SAP Notes ou experiência real de projeto — ajudaria muito. Desde já, agradeço!

Unable to select data from the entries list

2026-07-09T03:39:34.093000+02:00

Regarding the issue where data cannot be selected from the entries List, I previously checked the related SAP Note and found that this issue is planned to be fixed in version 2606 or 2608.

In that case, what actions are required on our system side to resolve this issue? Do we need to take any additional steps, or will the issue be fixed automatically after the upgrade?

I would appreciate your guidance.

SAP Note reference: 3763555 - WEBGUI: History not working after Chrome / Edge 149 update - SAP for Me

sapui5 - updating the bootstrap to release 1.149 / 1.150

2026-07-10T15:51:29.274000+02:00

My apologies ahead of time, but I am looking for the note containing the TCI for those UI5 update(s). I've looked at 3155948 - ABAP SAPUI5 patch version update, following the instructions under "Solution", but can not find any relevant note for the updates. I've also searched other notes/documentation, but I still can't find a thing.

This request is because of a notification we received under SAP event ID: EVB13291295

Thank you for your time.

Herman

SAPUI5 Versions Ending Cloud Provisioning in Q3/26

2026-07-15T10:30:25.383000+02:00

依照附件的公告內容, 請問我們要如何檢查及確認現有的BTP application 是否有受到影響.

是直接在Work Zone平台上進行確認即可 ?

亦或要從UI5專案開發的角度，檢查 index.html or manifest.json 之類的檔案 ? 」

Metadata error in BTP Cockpit when trying to reach S3P system

2026-07-15T12:02:31.271000+02:00

Hi Team,

As I am trying to do changes in the existing UI5 application developed in the BAS from my trail account I am unable to get the data for the app from S3P system from the backend. I am facing the Metadata Error and SAP Client Error.

Fieldglass SSO - Client wants to implement SSO for their MSP users

2026-07-16T18:19:59.457000+02:00

Hello All,

The company I work for is the MSP for a Fieldglass client that utilizes SSO for their internal users (AKA Hiring Managers). They would like to enhance security by having the MSP users who support their program go through SSO as well. Are any of you in the same situation and how was this accomplished in your case? I'm looking for any/all the different options to share with our client so that they can evaluate each. I'm not an SSO expert nor am I a very technical person so please use simple words/terminology. 😜

Thank you in advance.

Reforma Tributária - Contabilização efetiva dos lançamentos

2026-07-16T22:50:32.617000+02:00

A contabilização efetiva (lançamento contábil real, com débito/crédito impactando resultado) entra em vigor em 2027 para CBS e 2029 para IBS, desta forma existe alguma atualização da SAP disponível para aplicarmos nos ambientes e iniciarmos a validação?

Alguém já iniciou esta tratativa? pois alguns clientes estão questionando e solicitando a contabilização efetiva no ambiente de teste para validação.

Obrigada.

Persona Flavour Issue

2026-07-20T19:42:57.007000+02:00

Hi Team,
We observed 2 issues in the Opentext as below.
1) We made changes to a Personas flavor in the Development system (SD2) and transported them to the Quality system (SQ2), but the updates are not reflected in SQ2.

2) Additionally, any field position changes made to standard fields are not being retained. After saving the flavor, the field positions revert back to the previous layout