SAP Cloud Terminology

SAP Cloud terminology refers to the specialized vocabulary, acronyms, and service names used to describe SAP’s cloud ecosystem. Since SAP transitioned from a traditional on-premise model to a so called "Cloud First" strategy, many older terms have been renamed or evolved. Below list below doesn’t meant to be complete or exhaustive. It just serves as a quick intro into cloud terminology that SAP has. Not need to mention that these terms and their definitions are subject to change. Thus, always consult with SAP official sources. Such as SAP Trust Center that is official repository where SAP hosts all legal, compliance, and service-level documentation.

The most critical thing to know is that SAP Business Technology Platform (SAP BTP) is the foundation for almost all SAP cloud services.

Core Platform Terminology

SAP BTP (Business Technology Platform) - The "operating system" for the SAP cloud. It’s a Platform-as-a-Service (PaaS) that hosts everything from databases to AI.

Hyperscalers - The underlying infrastructure providers (AWS, Microsoft Azure, Google Cloud) that host SAP’s cloud services.

Subaccount - A structural unit within BTP used to manage applications, services, and users.

Environments or Runtimes - Within BTP where developers deploy code. Basically, they are two: Cloud Foundry and Kyma. Cloud Foundry is for standard web apps. Kyma is for Kubernetes-based containerized apps.

Agreement - Is the legal and structural framework that governs how a customer uses and pays for SAP cloud services. There are three types of them:

·        BTPEA - BTP Enterprise Agreement - "consumption-based" agreement, customer commits to a certain amount of cloud credits and spends them on any service you want.

·        CPEA - Cloud Platform Enterprise Agreement - The predecessor to BTPEA. It works similarly with a "commit-to-consume" model using credits.

·        PayG - Pay-As-You-Go - Agreement with no upfront commitment. You are billed monthly based on exactly what you used.

Unit – Typically refers to the standardized measurements used to quantify how much of a service customer is using. However, as per multiple commercial models, the unit can refer to three distinct layers of the BTP platform: Capacity Units, Units of Measure, or Cloud Credits.

Credits (Cloud Credits) – It is a prepaid digital currency used to pay for cloud services. The credits are bought upfront. One credit usually equals a specific monetary value (e.g., $1 or €1) as per a list price.

Entitlements - Are rights to use specific resources. If Credits are the money in customer’s wallet, Entitlements are the items the customer is actually allowed to buy and the "limits" on how much of them can be used.

Quota - Numeric limit of BTP service (e.g., 64 GB of RAM, or 2 instances of a database).

Usage - Is the actual consumption of services.

Usage Metrics - Are the specific units of measure used to calculate how much of customer balance (Credits or Subscription) is consumed. Usage Metrics may differ in case of different BTP services.

Capacity Unit (CU) - Is a ratio of services consumed via the Cloud Service and is calculated as set forth in the respective Product Supplement, Service Description Guide or Service Use Description.

Service	Usage Metric	Meaning
SAP HANA Cloud	Capacity Units	Combines RAM, CPU, and Storage into one power unit.
Integration Suite	Messages	Volume of data being moved between systems.
SAP Build Apps	Active Users	Number of people building or using apps.
Object Store	Gigabytes (GB)	Physical space files occupy.
SAC	Capacity Units	Compute, memory, credits.
DataSphere	Capacity Units	Multiple factors such as Data Lake usage, storage, memory, compute and more
BDC	Capacity Units	Those of SAC, DataSphere and on top of that DataBricks related as well: serverless SQL compute, SAP Object Store requests, and more

 

Cloud Package - Means a defined set of Cloud Services that are subject to a single subscription fee and collectively deemed a Cloud Service.

Content - Means any business logic, code, data models, configurations, user data, applications or other electronic materials created by customer.

Cloud Service - means any distinct, hosted, supported and operated on-demand solution provided by SAP.

Service Description Guide (SDG) - Is a legally binding document that defines:

·        Usage Metrics: Exactly what constitutes a "unit" (e.g., what counts as a "Document" vs. a "Record").

·        Service-Specific Terms: Rules that only apply to one specific tool (e.g., data retention limits for AI services).

·        SLAs: The guaranteed uptime for each specific service (e.g., 99.7% vs 99.9%)

Test, Demonstration and Development Cloud Services (TDD Cloud Services) - Refers to a specific category of licenses and environments designed exclusively for non-productive use.

General Terms and Conditions for SAP Cloud Services (GTC) – Is the foundational legal document of an SAP cloud contract. While the Order Form tells what customer bought and the Service Description Guide tells how it works, the GTC defines the legal "rules of engagement" between the customer and SAP.

More Information:

SAP Agreements

General terms and conditions

Service-level agreements

Service Description Guide

SAP Business Technology Platform Supplemental Terms and Conditions

ABAP Function Group RS_GENERAL

Among ABAP class CL_RSAR_FUNCTION there are also other useful places of ABAP code important to BW development. This time I picked up Function Group RS_GENERAL. It bundles generic helper function modules that are reused across SAP. It contains following Function Modules:

RRSV_SYSTYPE_GET                                Determine System Type (SAP/Customer)

RSAR_DATE_CHECK_PLAUSIBILITY             Plausibility Check for Date

RSBB_URL_PREFIX_GET                           Return of Protocol, Server, and Port

RSDG_MSG_APPEND_TO_PROTOCOL          Add Message to Application Log

RSDG_WORD_WRAP                                Divides a String into Substrings of Defined Length (Word Wrap)

RSPC_SHOW_DOCUMENTATION                 Display Documentation for a Process Type

RSRA_GET_DEFAULT_LANGUAGE                Returns Default Language of System

RSR_SYSTEM_GET_UNIQUE_ID                  Temporary Wrapper of SYSTEM_unique_ID_GET

RSSM_ADD_TIMESTAMPS                          Adds Two Time Stamps (One of Which Is Earlier Than 1.1.0001)

RSSM_CHECK_ASSERT_BREAKLUXM_ON     break_luxm stuff

RSSM_CONVERT_DAYSEC2TIMESTAMP        Converts Days and Seconds into Date, Time, and Time Stamp

RSSM_CONVERT_TIMESTAMP2DAYSEC        Converts Date and Time or Time Stamp into Days and Seconds

RSSM_EVENT_RAISE                                Trigger BP_Event_Raise; Can Be Called Using RFC

RSSM_GET_TIME                                     Get Time

RSSM_GET_TIME_INT INTERNAL:               Get Time from Enqueue Server

RSSM_ICON_CREATE                               Create Icon with Quick Info Longer Than 30 Chars (132 Bytes in Total)

RSSM_SLEEP_DEBUG                               Sleep Debug User / Sap - System

RSSM_SUBSTRACT_TIMESTAMPS               Subtracts Two Time Stamps from One Another

RSSM_UNIQUE_ID                                   Temporary Wrapper for SYSTEM_UNIQUE_ID_GET

RS_POPUP_TO_CONFIRM_ONLY_ONCE        Confirmation Popup "Do Not Show This Question Again"

RS_RFC_IS_GUI_ON                                Determine Whether GUI Is Available for Popups and so On

 

The functions in there are focused to:

General BW operations: various supporting fields and functions (time etc).

Monitoring and Data Loading/Processing: functions used during BW data loading processes (e.g. RSSM_GET_TIME that handles timing and monitoring operations during BW data processes).

Especially FM RSSM_CHECK_ASSERT_BREAKLUXM_ON checks the breakpoint of SAP internal BW backend developer called Matthias Lux. He is mentioned in quite a few of BW objects I wrote about it here - Most famous BW backend SAP developer :)

Notice the functions in this group are not released to be used!

Year 2025 – bye bye

Year 2025 was full of challenges for me mostly at personal and family front.

However, as the year 2025 draws to its close I want to conclude it with a little bit of fun. Earlier this year there was an SAP Note 2440630 circulating within posts and discussions on social media. It was painted as a humorous/novelty entry titled something like “Accident at work: Growling noise in the stomach area.” Some posts described it as an SAP Note that jokingly diagnoses stomach growling due to hunger and prescribes eating food. Short excerpt from the note:

It’s filed under Industrial Hygiene and Safety / Incident/Accident Management and starts like a normal issue report:

“During work, you suddenly notice a strange growling background noise… your system administrator cannot find a solution.”

Then it rules out ABAP, DB, network, and hardware problems before stating the real cause:

“insufficient supply of resources for your stomach (hunger).”

The “manual correction steps” are basically: leave your desk, find food, chew, swallow, repeat until the sound stops — with a caution to avoid eating too fast.

 

Apparently after it went viral SAP has removed it. The Note page currently displays “SAP Note/KBA 2440630 does not exist” message. Users can no longer access it via the standard interface, but it was a quite funny things that someone at SAP did :)

My best wishes for a new year MMXXVI to all of you!

Which Support Package is recommended for BW?

Many customers I worked for were looking for a reply to this question. The thing is that it goes beyond the SAP BW’s usual "BW Support Strategy" according to which – a quote from SAP Note:

To assist SAP in providing an optimal level of support it is important for the customer system to be up to date. For this, SAP recommends running the latest (or latest – 1) BW Support Package available on the SAP service marketplace.

Thus, SAP doesn’t publish one single “recommended Support Package” number that fits all customers — instead it is the general recommendation - to always run the most up-to-date Support Package Stack that is available for particular release, or at least the latest and the one immediately before the latest.

OK clear. But there are also security issues fixes delivered via SAP Security Notes with high or very high priority. Those normally customers implement on ad-hoc basis as the Notes are published. But some customers may neglect those activities. Therefore, to stress this importance SAP issues following statement – again a quote from SAP Note:

We therefore strongly recommend to update the system at least once per year to the latest Support Package.

Last thing – where to check what is the latest support pack available for my BW? Go to PAM – Product Availability Matrix for that. Find your BW there and published SP are listed on Support Package Stacks tab.

 

More information:

2792181 Which Support Package is recommended for BW/4HANA-customers?

375631 Which Support Package is recommended for BW-customers?

PAM or PAM or PAM – listing more links as they may be changed in future

SAP BW/4HANA (B4H) versions

What is SAP GxP?

The term SAP GxP refers to the use of SAP software in highly regulated industries. These include, in particular, pharmaceutical, medical technology and biotechnology industries (also known as the life sciences industry).

In these industries, very specific and strict regulatory requirements apply to products - and therefore also to the processes and systems used to manufacture them. Means in those industries they need to comply with GxP regulations (Good Practice guidelines). Where x can stand for:

·        GMP (Good Manufacturing Practice)

·        GLP (Good Laboratory Practice)

·        GCP (Good Clinical Practice)

·        GDP (Good Documentation Practice)

These guidelines are monitored by regulatory bodies like in the case of pharmaceuticals the FDA (USA) and EMA (Europe) and aim to ensure product quality, safety, and compliance.

SAP GxP includes functions that enable companies to fulfil these requirements. Issues such as data security, traceability (tracing a drug production through so called batch number) and documentation play an important role here.

 

SAP GxP Solutions

SAP offers specialized solutions for regulated industries:

·        SAP S/4HANA Cloud for GxP, Private Edition - A version specifically designed for life sciences with built-in compliance features

·        SAP Quality Requirements Schedule - Additional documentation and audit rights for GxP customers

·        Support for Computer System Validation (CSV) - The regulatory validation process required for IT systems in GxP environments

ABAP CL_RSAR_FUNCTION class in BW4/HANA

I wrote about the ABAP class CL_RSAR_FUNCTION a long time ago here. In a nutshell it provides a collection of static utility methods for common data transformations and calculations, particularly focused on date and string operations. The methods can be called directly without instantiating the class.

Now in a BW4/HANA based BW system there are few more methods added into the class.

ALPHA                                       ALPHA conversion

FISCPER_FISCPER3                       Date -> Fiscal Period 3

GET_LOGICAL_SYSTEM                 Get Logical System

GET_SOURCE_SYSTEM_ID             Get Source System ID

L_TRIM                                      Left Trim (string)

QUARTER_QUARTER1                    Month -> Quarter1

RTRIM                                        Right Trim (string, string)

SECONDS_BETWEEN_TIMESTAMPS Difference between 2 timestamps in seconds

SECONDS_TO_DAYS                     Convert seconds to days

SECONDS_TO_HOURS                   Convert seconds to hours

SECONDS_TO_MINUTES                Convert seconds to minutes

SET_REQUEST                             Set request

SET_REQUEST_CLOUD                  Set request for cloud based BW4

UTC_LONG_TO_LOCAL_DATE         UTC Timestamp -> Local Date

UTC_LONG_TO_LOCAL_TIME          UTC Timestamp -> Local Time

UTC_SHORT_TO_LOCAL_DATE        UTC Timestamp -> Local Date

UTC_SHORT_TO_LOCAL_TIME        UTC Timestamp -> Local Time

Possibilities of checking ABAP code quality from HANA DB migration point of view

When migrating SAP NetWeaver based ABAP stack server from any DB to HANA DB there are a few steps to be done prior to the migration with the respect to the ABAP code.

First there are functional modifications to the custom ABAP code to be analyzed. Those are places in the code that leverages specific DB features that need to be adjusted for the HANA DB. As an example, these are Native SQL statements in the ABAP code.

Secondly there is SQL Optimization of the custom ABAP code. To support this part there are a few of the tools available.

To identify the places of the code for both the cases it is possible to leverage Runtime and Static Checks.  Those are two different approaches also to support the code quality assurance and error detection.

Static checks analyze your ABAP code without executing it. They examine the source code itself to identify potential issues, coding standard violations, and best practice deviations. They are performed during development time in the ABAP Editor or through Code Inspector (SCI), no program execution required, checks syntax, adherence to coding guidelines, and potential logical errors.

Tools:

Extended Program Check (t-code SLIN)

Code Inspector (t-code SCI/ATC)

ABAP Test Cockpit (t-code ATC)

SQL Monitor (t-code SQLM or older /SDF/ZQLM)

SQL Performance Tuning Worklist (t-code SWLT or older /SDF/ZQLMD). It combines the SQLM data with the ATC tool results.

 

Runtime checks monitor and validate code behavior during program execution. They detect issues that only become apparent when the program runs with actual data.

They are: activated in t-code SLIN or through specific settings, to monitor memory usage, database operations, and system calls during execution, to impact performance when active, to provides detailed analysis of actual program behavior.

Tools:

Runtime Check Monitor (t-code SRTCM), is used for administrative tasks

Runtime Check Monitor (t-code SRTCMD): Data Display, is used for pure runtime data analysis

The above-mentioned SRTCM tool is solely focused to scan the code for two main issues:

Empty table in case of FOR ALL ENTRIES statement. If the internal table is empty then all data is fetched from DB table.

Missing ORDER BY or SORT statements after SELECT. In case the internal table is not sorted the SELET is slower performing is it could be.

 

More information:

1912445 - ABAP custom code migration for SAP HANA - recommendations and Code Inspector variants for SAP HANA migration

3242700 - ABAP SQL Monitor: Implementation Guide and Best Practices

SQL Performance Monitoring

SUPPORT CONTENT for BW enthusiasts

Help site of SAP – help.sap.com basically contains a documentation for SAP products. On top of that there is a suite of pages so called Support Content. What is meant by that is additional content provided by SAP but not considered the documentation as defined by the applicable SAP General Terms and Conditions.

Main page of the Support Content is: help.sap.com/docs/SUPPORT_CONTENT

Let’s explore what is in there in scope of SAP BW, Data Warehousing and SAP Analytics in general.

Business Warehouse - Data Warehousing and Business Content

Business Warehouse – Analytic Engine (OLAP) and Planning

SAP Datasphere      

Business Warehouse – Frontends

ABAP CDS Analytical Queries

SAP Analysis for Microsoft Office

SAP Analytics Cloud (SAC)

SAP BusinessObjects Business Intelligence Platform

SAP Crystal Reports

SAP Lumira

SAP HANA Smart Data Integration

Other topics:

Netweaver Technology

Basis Corner

Application Server Infrastructure

Application Services – SAP Cloud Connector

ABAP Development

ABAP Objects

ABAP - FAQ

ABAP How-tos Guides

ABAP Tools

ABAP Connectivity

Executing BW transformation in on-prem/cloud based system

There is a different call of ABAP method that executes the BW transformation introduced for cloud based BW systems. It can be spotted in method TRANSFORM of class CL_RSTRAN_TRFN_CMD. First there is a check if the BW is cloud based system. If so the request parameter (i_r_request) that is passed to a method call is l_r_request_cloud. In case it is on-premise based BW system the value of the same parameter is l_r_request.

 

The two request are generated by a same class and different method call:

cl_rsar_function=>set_request_cloud( i_r_request = l_r_request_cloud ).

cl_rsar_function=>set_request( i_r_request = l_r_request ).

 

In case cloud system the request is instance of IF_RSBK_REQUEST_PROXY_CLOUD.

For on-prem request it is instance IF_RSBK_REQUEST_ADMINTAB_VIEW.

Both the interfaces provide access to runtime attributes of a data load request during its processing. It acts as a bridge between an infoprovider admin screen/tab (in the class called as - IPRO Admin Tab) used for monitoring and administration of requests) and the request object itself in the BW system.

SAP Clean Core

Sometime around 2018 SAP finally realized that migrating from classing ECC to S/4 is not that easy for a customer. ECC systems are usually heavily customized, bloated with custom code, flooded with numerous background jobs - not clear what data they process and wired in with many interfaces that it is not possible to track what data they bring in/out.

Back then the SAP’s introduced a clean core strategy (remembers TechEd slogan – Keep the core clean). It is a modernization approach designed to keep the ERP system (especially SAP S/4HANA) as close to standard as possible. That means minimizing invasive customizations and technical debt. It aims to make systems upgrade-safe, cloud-ready, and innovation-friendly by shifting custom logic and extensions outside the core, typically to SAP Business Technology Platform (BTP).

Clean core principles:

·        Standardization of Business Processes – Adopt SAP Best Practices to reduce complexity.

·        Decoupled Extensions – Move custom logic outside the ERP core using BTP.

·        Integration via APIs – Ensure reliable, upgrade-safe connectivity.

·        Data Governance – Maintain clean, consistent data for analytics and compliance.

·        Efficient Operations – Reduce maintenance costs and security risks.

However, what SAP really wanted back then was to a kind of "cloud mandate" to their customers. For years there has been a pushback of that. Still many customers prefer to stay on-premise for various reasons. It makes no sense to dig to those reasons here now but surveys by ASUG/DSAG confirmed it many times. S/4 adoption did not go a pace SAP wanted it.

Now we are in 2025 when SAP comes with the lates iteration of the clean core strategy – document Clean core extensibility for SAP S/4HANA Cloud. To simply put it - they came from cloud mandate to practical reality the customers live in. Seems SAP finally gets the customers issues and they do not demonizing a custom development rather they address it more pragmatic and customer friendly approach. Within the latest strategy SAP introduces A–D extensibility model replacing old tiers for compliance and upgrade safety. Finally, a classic ABAP APIs and ABAP technologies (e.g. customer exits, SAP Script, Smart Forms, classic workflow, web dynpro ABAP) are classified as clean core compliant at level B which means are upgrade-stable.

 

Level A: Fully Compliant Extensions done with SAP Build by using only publicly released, stable interfaces backed by formal stability contracts.

·        Side-by-Side: Develop on SAP BTP using pro-code and low-code tools for applications and process automation.

·        On-Stack: Build within SAP Cloud ERP Private using the ABAP Cloud model and approved APIs.

 

Level B: Classic API-Based Extensions - Utilize SAP’s classic APIs and technologies with well-defined, documented, and generally upgrade-stable interfaces.

 

Level C: Partially Compliant Extensions - Depend on SAP internal objects for flexibility in legacy scenarios. SAP provides object change logs to help identify incompatible changes early and plan upgrades proactively.

 

Level D: Not recommended extensions not considered “clean” that use explicitly non-recommended objects or techniques (e.g., objects marked as “noAPI” in the Cloudification Repository, modifications to SAP objects, direct write access to SAP tables, or

implicit enhancements). These represent the highest risk and create significant technical

debt.

 

Level D: Non-Compliant Extensions (Not recommended/considered as clean core because it is the upgrade risk/technical debt.) - Use non-recommended objects or techniques such as:

·        Objects marked “noAPI” in the Cloudification Repository

·        Modifications to SAP objects

·        Direct table writes or implicit enhancements

 

More information:

Clean core extensibility for SAP S/4HANA Cloud

3578329 - Frameworks, Technologies and Development Patterns in Context of Clean Core Extensibility

Cloudification Repository Viewer – BW classic components listed here, none of BW artefacts has a successor in fact, but they won’t be missed as in modern BW (e.g. BW4/HANA, SAP Datasphere and BDC) replaces those old technologies completely.

Debugging process chains

There are few possibilities for debugging a process chain. In case BW system is based on older versions it needs to be debugged is a background process. This can be done via capturing the background process from the chain’s job.

In case the BW system is newer the chain debugging function is available out of the box. In the process chains related t-codes (e.g. RSPC1) when the chain is in EDIT mode there is a drop down menu called “Debug Loop…”.

 

After that a popup window is displayed. In that window it is possible to enter a number of seconds that represent how long the process waits before executing the task. During this waiting time you either go to Job Overview (t-code like SM37) or the Process Overview (SM51, SM50) and capture the process from there. Or make it simpler and set the break point in your code prior to the debugging). After entering the “Debug Loop…” the chain needs to be saved and activated.

The debugging itself can be started from RSPC1’s menu Execution -> “Execute Synchronous to Debugging”.

In a nutshell:

1.    Open the PC in Edit Mode

2.    Find a process you want to debug

3.    Right click and select “Debug Loop”

4.    Set a time in seconds e.g. 5 seconds

5.    Save and activate the chain

6.    In the menu -> Execution -> Execute Synchronous to Debugging

 

More information:

Finding any process in Process Chain that deals with certain object

Reassigning of Process Chain’s InfoArea

Streaming for Process Chains

Possibilities of Process Chain monitoring

Other ways of starting Process Chains

Critical path of a process chain

Process chain where used

Dummy report for process chain decision processes

Skip Process Chain’s process – some details

DTP runtime:739444Days 12H 59m 29s?

Recently I encountered a strange DTP runtime figure. The runtime value was displayed in the DTP monitor screen and when I saw it, I rolled up my eyes. The duration of the DTP runtime was 739444Days 12H 59m 29s.

That looked really strange to me. When I debug it I saw that the duration is calculated by FM RSSM_SUBSTRACT_TIMESTAMPS. The FM is called by a method TSTMPS_TO_DURATION in ABAP class CL_RSDSO_MNG_TSN_UTIL.

What the FM is using is to provide a values of the duration in days/hours/minutes/seconds. How it calculates it is basically just a subtraction from the two timestamps: the starting and finishing one. There is one more FM involved in this calculation - RSSM_CONVERT_TIMESTAMP2DAYSEC. That one is counting with a date that is equal to '00010101'. This date is basically the first January of the year 0001 (year one).

What could happen in my case is that for my request the starting timestamp was not available for the calculation for whatever reason. Thus, the BW system based duration’s calculation starting at time the vey morning ('000000') of the first January of the year 0001 ('00010101'):

 

  DATA: l_c_datum TYPE d VALUE '00010101', 

        l_c_time TYPE t VALUE '000000'.

 

As I ran the DTP on 13^th of June 2025, the difference between that data and date year one is 739444Days. Plus, there were some hours/minutes/seconds added.

Notifications and Subscriptions in BW4/HANA

Notifications and Subscriptions functionality is available in BW4/HANA based BW systems. In case of the Notifications, the user has a chance to receive notification either via email or to mobile devices about different events that happened in the BW system. The events are following:

Process chain run aborted

Process chain run completed

Process chain run is overdue

Process chain run is seriously delayed

Process chain run takes longer

Process chain run takes much too long

Request ended with errors

Subscriptions on other hand defines specific conditions of BW∕4HANA objects that user receives the notifications for.

Settings related to notifications and subscriptions are available SAP BW∕4HANA Cockpit – (BW Fiori Launchpad). From here the notifications/subscriptions can be enabled/disabled.

From the BW backend perspective the functions are needed first to be customized.  In a t-code SPRO there is an item called Notification Channel -> Notification Channel Provider Enablement. Here all customizing needs to be done from the Configuration and Administration perspective. To switch the function on - the customizing under Administration -> Notification Provider Settings -> Manage Notification Providers (t-code /IWNGW/VB_REG_P, maintenance view /IWNGW/VB_REG_P and table /IWNGW/B_REG_P) needs to be activated.

There are a few tables that holds data about the settings:

BW4FLPNOTIF                    BW/4 FLP Notifications, each notification has a unique ID (NOTIF_ID), TYPE_KEY identifies type of the notification (BW ones e.g.: BW4_RSPC_VERY_LONG, BW4_RSPC_LONG, BW4_RSPC_BERY_LATE, …)

BW4FLPNOTIFREC                 BW/4 FLP Notification Receivers, a list of the user per unique notification ID

BW4FLPNOTIFSUB                 BW/4 Notification Subscriptions, each subscription has unique ID (GUID), user (USER_ID) specific the user to whom the subscription belongs to, OBJECT columns defines object which the subscription is related to (e.g.: ADSO, PC, PREC, etc.), validity columns from – to, who created, when,…

BW4FLPNOTIFSUBCO               BW/4 Notification Subscriptions Conditions, condition has unique ID (SUBSCR_GUID), FIELDNAME, and SEL_LOW and SEL_HIGH define object e.g. PC tech name

Some of these tables can grow fast thus housekeeping needs to be performed on them. There are standard programs like RS_BW4_FLP_NOTIF_DELETE and RS_BW4_FLP_NOTIF_OFF to support that.

 

More information:

Online documentation

2922364 - FAQ: BW/4HANA 2.0 Cockpit Notifications