Introducing SAP Fiori Apps

Objective

After completing this lesson, you will be able to evaluate the different SAP Fiori apps in the MaCo Cloud to determine their uses.

Overview

The business platform, SAP S/4HANA Utilities, smoothly operates in both SAP GUI and SAP Fiori interfaces, allowing for deployment in private cloud or public cloud configurations. However, for the purposes of this course, we will not focus on explaining the functionalities of SAP Fiori apps or GUI transactions associated with the business system. That information is comprehensively provided in other sections of this course.

The market communication system known as MaCo Cloud operates exclusively within the SAP Fiori interface, with the deployment being exclusively possible through a public cloud. This unit is dedicated to explaining the SAP Fiori apps used for monitoring and configuring the market communication system.

Diagram illustrating components of SAP Market Communication. At the top, under Market Communication in General, are: Message Exchange, CONTRL and APERAK, Aggregation, Reversal, Partner Management. Below, Market Communication by Role includes: Meter Operator, Distributor, Supplier, Settlement Coordinator. Utilities Business Data section lists: Master Data, Energy Data, Process Data, Settlement Data. At the bottom, SAP Fiori Apps features: Monitoring, Configuration. The background is light blue.

The following MaCo cloud's SAP Fiori apps are described in this unit:

  • Monitoring Process Documents
  • Monitoring Transfer Documents
  • Configuring Market Processes
  • Configuring Check Framework
SAP interface displaying process monitoring and configuration. Top section shows counts for: Erroneous Processes (6.87K), Erroneous Transfers (79.9K), Overdue Exceptions (111K), and Operation Settings (39). Below, Process Configurations lists: Define Process Clusters (28), Define Versions (129), Define Market Roles (21), Define General Configurations (2), Define Process IDs (803), Define Process Step IDs (1.15K), Define Process Activities (1.46K), Define Process Values (1.22K), Configure Processes (1.19K), Configure Actions (12), Configure Checks (1.11K), Configure Check Groups (1.27K), Define Exception Codes (381), Define Exception Parameter IDs (66), Define Exception Solution Codes (26), Configure Exception Solutions (36), Configure Exceptions (400), Define API IDs (6). Header includes navigation tabs and a search bar.

Monitoring

Monitoring Process Documents

The SAP Fiori app Monitoring Process Documents (PDOC) enables the monitoring of market communication processes. For each process that starts, the system creates a process document that collects all important information.

SAP interface showing a table of workflow process documents. Filters at the top include options for Document Number, Process ID, Process Status, Process Key Date, Business Object Type, Business Object, Common Access Reference, Owner, Communication Partner, and Blocked in Mass Execution. A search bar is present. The table lists various process entries with columns for Process, Process Status, Process Key Date, Business Object, Common Access Reference, Owner, and Communication Partner. Processes are marked as Active/New or Completed, with key dates and associated business details. Options to edit, execute, restart, change status, release, and view are available.

The selection screen has the following features:

  • Overview of all process documents and their statuses
  • Search and filter the process documents
  • Check if all processes are running properly or if action is necessary
  • Navigate to the details of a process document (see next figure)
SAP interface showing a process document for Start of Basic or Backup Supply for Electricity (DSO View). The top section indicates a Process Key Date of 01/01/2025, Business Object ID, Completed Status, and Status Timestamp. A table below lists steps with columns for Step Sequence Number, Step Description, Process Step ID, Process Step Status (mostly Completed or Active), Status Timestamp, Step Timestamp, Deadline, Communication Reference, and Additional Data links. Steps include actions like Start of Process, Send Request, and Check Before Ending Process. Tabs for Steps, General, Activities, Linked Documents, Log, and Administrative Data are visible.

The PDOC has the following detailed information:

  • Display the involved business partners and business objects
  • Navigate to the additional data, this is, paths, fields and values involved in the process
  • Display single activities and steps performed in the process
  • Navigate to the details of a process step
  • Display the data exchange and communication information of the step
  • Navigate to the communication vehicle for an inbound or outbound step
  • Check deadline details for a deadline step
  • Display the process step ID, version, and type
  • Navigate to the additional, this is, paths, fields and values involved in the process step
  • Display the check results and their follow-up actions, like exceptions raised or values set
  • Navigate to linked documents like other process documents, transfer documents, or exceptions
  • Analyze an extensive log of the system processing
  • Display further administrative information like access restrictions, data protection, lifecycle state, or change tracking

PDOC and TDOC are linked to each other.

Monitoring Transfer Documents

The SAP Fiori app Monitoring Transfer Documents (TDOC) enables the monitoring of the message transfer between business system, MaCo cloud and external market partners. For each transfer that starts, the system creates a transfer document that collects all important information.

SAP interface displaying a table of transfer documents. Filters at the top include Document Number, Transfer Status, Direction, Transfer Date, External Transfer Reference, Communication Partner, Business Status, Common Access Reference, Technical Message, and Business Message. The table contains columns for Document Number, Transfer Status (e.g., Sent, Completed), Direction (Inbound/Outbound), Transfer Timestamp, External Transfer Reference, Process Document, Technical Message, Business Message, and Common Access Reference. Options to execute, edit, and view specific rows are available. The interface includes a search bar.

The selection screen has the following features:

  • Overview of all transfer documents and their statuses
  • Search and filter the transfer documents
  • Check if all transfer are running properly or if action is necessary
  • Display the transfer direction, time, communication partners and client, external ID, and the related process document
  • Navigate to the details of a transfer document
SAP interface showing details of a transfer document. The document number is displayed, with Transfer Timestamp, Transfer Status (Completed), and Business Status (Positive CONTRL Sent). Sections include General, Business Objects, Linked Documents, Log, and Administrative Data. General section lists Identification details: External Transfer Reference, Aggregation Transfer Number, Correlation ID, and Common Access Reference. Communication Attributes: Direction (Inbound), External Communication Type, Applicability Statement. Communication Partner info: Sender, Receiver, and their Code Lists. Message details: Technical and Business Messages. Acknowledgements are noted. Payload section displays External Payload in detail and Internal Payload is empty. Options to generate explanation and copy payload are available. The interface includes Edit and Refresh buttons.

The TDOC has the following detailed information:

  • Display the internal and external IDs of the document and the contained message
  • Display the internal and external payload of the market message
  • Display the involved business objects, their IDs and operation details
  • Navigate to the business object data, this is, paths, fields and values of the transferred object
  • Navigate to linked documents like process documents, other transfer documents, or exceptions
  • Analyze an extensive log of the system processing
  • Display further administrative information like access restrictions, control parameters, technical attributes, lifecycle state, or change tracking

TDOC and PDOC are linked to each other.

Configuration

Configuration of Market Processes

A process configuration consists of the following parts:

  • General Data
  • Process Step Data
  • Preconditions

The General Data includes the process category and the process class. The process class is the technical representation of the process logic and refers to the root class /APE/CL_PROC.

Table titled Start of Supply for Electricity (DSO View) showing process steps for supply initiation. Columns include Sequence, Description, Process Step Type, Process Step Category, Process Step ID, Business Message ID, Check Group, and Period Type. Rows detail trigger processes, validations, requests, and checks with IDs and descriptions. Includes both standard and external events related to supply migration and business processes.

The Step Data includes

  • Step Category (standard, start, end)
  • Step Class
  • Step Type
  • Step Container Enhancement CI_PROC_STEP_EXTEND

The process step type in combination with the process step class defines what the step actually does:

  • The Business Validations step executes the validations defined in the check group assigned mandatory to this step.
  • The Data CRUD Operation step triggers a create or update operation in the connected system(s) by calling the API assigned to this step.
  • The Deadline step checks a deadline calculated based on a time stamp, for example, the current date and time or the process key date.
  • The Extension by Customer step performs a custom process (step) logic from a custom process you have specified under Trigger Process ID.
  • The Trigger Step in Linked Process step triggers a step of a linked process.
  • The Trigger Embedded Process step includes an embedded process in the current one.
  • The Trigger from External Event step gets triggered by an external event, such as an inbound message or another process.
  • The Trigger of External Event step triggers an external event such as the assigned outbound message.

The Preconditions define under which circumstances the current step is executed and consists of:

  • General Settings such as predecessor step and prerequisite
  • Mappings from source data container to target data container
  • Values to model decision points

Configuration of Check Groups and Checks

The Check Group groups together several Checks and consists of the following settings:

  • Inspection Type (standard, start, end)
  • Child Check Group (standard or extension)
  • Follow-Up Actions (stop/continue, process value, process step status, activity, exception code, business object code)
  • Preconditions to define dependencies of checks to control the order of check execution
SAP interface titled Configure Check Groups (SAP) for CHKGRP_CP_APERAK_INIT_MELO. Displays administration info, including configuration and deployment. The Checks section has one entry checking if MELO PoD Exists or Not with sequence 0100. The Descriptions section notes check for initiate process of metering. A detailed view on the right shows a single check with ID 0010, listing its category, actions, and check preconditions. Actions detail different statuses for MELO_PoD with various processing statuses.

The Check consists of the following settings:

  • Check ID
  • Check Result
  • Check Class and Method with reference to the root class /APE/CL_CHECK
  • BRFplus Rule and Class with reference to the root class /APE/CL_CHECK_BRF

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn