Intro
As organizations migrate to SAP S/4HANA Public Cloud, the shift away from SAP GUI fundamentally changes how operational data is accessed. SAP Field Service and Asset Management Checklist/Smartform data required a modern approach to remain visible to business users. This post walks through the background, the cloud-imposed constraint, and the two Fiori applications designed to close this gap.
This work started with a gap I kept seeing in Public Cloud projects: data replicated perfectly into CRMD_FSM_* tables but invisible to the business. We tried a few detours, but anything that look like SE16N was off the table in cloud. Aligning to the VDM and building RAP‑based Fiori Elements apps became the clean, supportable path—what you’ll see here.
Checklist vs. Smartform — A Terminology Note
The underlying technical data model and database tables use the term Checklist (e.g., CRMD_FSM_TM_HDR, CRMD_FSM_IN_HDR, CDS views prefixed I_SERVICECHECKLIST*). However, in the SAP Fiori app catalog and end-user documentation, the same concept is surfaced as Smartform — the product-facing name aligned to SAP Field Service and Asset Management terminology. Both terms refer to the same underlying entities throughout this article.
Background
What Are Field Service and Asset Management Smartforms and Why Do They Matter?
SAP Field Service and Asset Management enables field technicians to execute structured, digital forms during service activities — from routine maintenance inspections to complex equipment diagnostics. Each form is built from a Smartform Template (the structural definition, containing chapters, elements, dropdowns, tables, and conditional logic), executed as a Smartform Instance (the completed record filled by the technician), and organized under a Template Category (the grouping mechanism).
When FSA data is replicated into SAP S/4HANA, it lands in dedicated database tables (CRMD_FSM_TM_HDR, CRMD_FSM_IN_HDR, CRMD_FSM_TM_CAT, and their related element and text tables). This data holds significant analytical value — it reveals patterns in how technicians complete tasks, surfaces form compliance trends, and feeds KPI dashboards for service operations teams.
Business Value: Smartform instance data filled by field technicians can be used for analytics — helping customers create better KPI reports and identify trends across service operations.
The Core Challenge
The Public Cloud Constraint: No SAP GUI, No Transaction Codes
Limitation in S/4HANA Public Cloud
In S/4HANA Public Cloud, customers do not have access to SAP GUI. Transaction codes (tcodes) cannot be used to view or query database table contents directly. Without a dedicated UI layer, the replicated Field Service and Asset Management Smartform data remains entirely inaccessible to business users — despite being present in the system.
This is a fundamental architecture difference from on-premise deployments. In the cloud model, all user interaction must occur through browser-based Fiori applications or approved API surfaces. There is no back-door access to raw table data via SE16N, SM30, or similar transaction codes.
No SAP GUI Access
Customers in Public Cloud cannot use any SAP GUI transaction to view raw database table content.
Data Locked in Tables
Field Service and Asset Management Smartform data lands in CRMD_FSM_* tables with no user-facing display layer in Public Cloud.
Analytics Blocked
Without visibility into smartform instances, analytical use cases — KPIs, trend detection — cannot be acted on.
Prefill Instance Replication Scenario From S/4 to FSA can not be enabled
Without viewing the smartform data, customers can not enable the prefilled instance replication scenario from S/4 to FSA
The Solution
The Idea: Two Cloud-Native Fiori Applications Built on RAP
To solve this visibility gap, the team designed two purpose-built SAP Fiori Elements applications backed by the ABAP RESTful Application Programming Model (RAP). This approach adheres fully to SAP's cloud development principles — no custom tcodes, no direct table access, and full alignment with the Virtual Data Model (VDM) layering strategy.
Both applications are accessible through the SAP Fiori Launchpad, giving business users a clean, browser-based interface to explore smartform templates and completed smartform instances — with Template Categories surfaced as a navigatable sub-view within the Template Viewer.
DB Tables(CRMD_FSM*) → CDS Views (VDM Layers) → OData V4 Services → F9283 & F9286 Fiori Launchpad
Application Design
The Two Fiori Apps: F9283 and F9286
The solution delivers two dedicated Fiori Elements applications, each covering a distinct domain of the Field Service and Asset Management smartform data model. Template Categories are accessible as a navigatable sub-view within F9283 rather than a standalone application.
F9283 – Smartform Template Viewer
- Template ID
- Template Status
- Template Category ID
- Created By
- Template ID Default ↓
- Template Status
- Template Category ID
- Created By
- Account ID
- Object page — template elements
- Smartform Template Category
Semantic Object – ServiceChecklistTemplate , Semantic Action – display
F9286 – Smartform Instance Viewer
- Instance ID
- Template ID
- Instance Status
- Created By
- Instance ID Default ↓
- Template ID
- Instance Status
- Created By
- Account ID
- Object page — instance element values
- Template ID → F9283 Smartform Template Viewer
- Service Order → Manage Service Orders
Semantic Object – ServiceChecklistInstance , Semantic Action – display
Integration
Cross-App Navigation: A Connected Experience
F9283 and F9286 are not isolated experiences. They are interconnected through the SAP Fiori Launchpad intent-based navigation, allowing users to move between related records across applications without losing context.
Outcomes
What This Enables for Customers
Full Data Visibility
Business users can view template structures and completed instance records directly in the Fiori Launchpad via F9283 and F9286.
Analytics Ready
Smartform instance data is now accessible for KPI reporting, operational trend analysis, and downstream process integration.
Service Quality Validation
Service managers can inspect what technicians filled in the field — validating compliance, completeness, and job quality directly in F9286.
Connected App Navigation
Cross-app navigation between F9283, F9286, and Manage Service Orders creates a unified, context-aware service workflow.
Cloud Compliant
No SAP GUI, no tcodes — fully aligned with SAP S/4HANA Public Cloud development standards, access control via PFCG role CRMS4_FSMC.
Summary
For organizations leveraging SAP Field Service and Asset Management alongside S/4HANA Public Cloud, this solution provides the transparency needed to turn raw smartform execution data into actionable operational intelligence — accessible to any authorized user, from any browser, without a single transaction code.
Source link
