Exposing 0UC_SALES_STATS_04 into SAP Datasphere

Step-by-Step Implementation Guide
From S/4HANA for Utilities to SAP Datasphere via Replication Flow

Context and Background

• The customer uses Sales Statistics as a core solution in their BW system, based on extractor 0UC_SALES_STATS_02
• In S/4HANA for Utilities, a new extractor 0UC_SALES_STATS_04 enables native integration with SAP Datasphere
• The older 0UC_SALES_STATS_03 has a critical limitation: initial load only in Replication Flows (SAP Note 3587890)
• 0UC_SALES_STATS_04 supports both Initial + Delta replication, making it the correct choice for Datasphere
• This guide documents the end-to-end activation and consumption process

Reference: SAP Roadmap item INNO_56121 - Native sales statistics and unbilled revenue reporting in SAP Datasphere (Delivered Q1/2026)

Extractor Comparison: Which One to Use

Prerequisites

• S/4HANA for Utilities system with IS-UT add-on installed (verify in transaction SAINT)
• Sufficient S/4HANA release level that includes the 0UC_SALES_STATS_04 DataSource
• SAP Cloud Connector installed and accessible (for on-premise connectivity)
• SAP Datasphere tenant with administrative access
• SAP BTP subaccount linked to Cloud Connector
• User with full authorization (SAP_ALL) for DataSource activation

Step 1: Verify IS-U Installation

Objective: Confirm the Utilities component is present on the S/4HANA system.

1.1 Check SAINT (Add-On Installation Tool)

1. Go to transaction SAINT
2. Look for IS-UT (S/4HANA IS-UT) in the Installed Components list
3. Note the release and level (e.g., Release 808, Level 0003)

1.2 Verify the Extractor Function Module Exists

1. Go to transaction SE37
2. Enter function module: ISU_BW_SALES_STATISTICS
3. Confirm it exists and is Active

If ISU_BW_SALES_STATISTICS exists, the extraction code is deployed. The DataSource just needs to be activated.

Step 2: Locate the DataSource in RSA5

Objective: Find 0UC_SALES_STATS_04 in the Business Content DataSource tree.

Why RSA6 Does Not Show It

• RSA6 ("Postprocess DataSources and Hierarchy") only shows already activated DataSources
• The "Find" button in RSA6 only searches within activated sources
• If IS-U DataSources were never activated, they will not appear in RSA6

Navigate RSA5

1. Go to transaction RSA5 ("Installation of DataSource from Business Content")
2. Do NOT look under the "IS" top-level node — the IS-U DataSources are not there
3. Scroll down to find 0IS_UC (Utility Company) — this is the correct node
4. Expand 0IS_UC > 0IS_UC-IO (Utility Company Master Data)
5. Scroll down to find:
   • 0UC_SALES_STATS_02 — IS-U Sales Statistics (Delta created by Mass Activity)
   • 0UC_SALES_STATS_03 — IS-U Sales Statistics (Delta Created by Mass Activity)
   • 0UC_SALES_STATS_04 — IS-U Sales Statistics (Mass Activity) for Datasphere

Key Finding: The IS-U DataSources are listed under 0IS_UC (Utility Company), NOT under "IS" in the hierarchy tree.

Step 3: Activate the DataSource

Objective: Register 0UC_SALES_STATS_04 in the system so it can be consumed.

User and Client

DataSource activation is cross-client — it registers the DataSource at system level regardless of which client you log into.

Activation Steps

1. Log on to client 000 with admin user
2. Go to transaction RSA5
3. Navigate to 0IS_UC > expand the tree
4. Select 0UC_SALES_STATS_04
5. Click "Activate DataSources" in the toolbar
6. When prompted for "Create Object Directory Entry":
   • Click "Local Object" (assigns to package $TMP — no transport needed for POC)
7. Check the Display Log:
   • Yellow warnings about DEC field lengths (ANZVERTR, CNTBILLDOC, CNTINVDOC) are harmless
   • Success = yellow warnings only, no red errors

Troubleshooting Authorization Errors

Step 4: Verify Activation

Objective: Confirm the DataSource is properly registered and functional.

RSA3 Test Details

1. Go to transaction RSA3
2. Enter DataSource: 0UC_SALES_STATS_04
3. An "Alternative Selection" popup appears asking for "Print document"
4. Leave all fields blank and click Execute
5. Result: 0 records with no error = DataSource is technically functional
6. The system may have no IS-U billing data (expected on sandbox/CAL systems)

ODQMON Context Mapping

ODQMON will only show 0UC_SALES_STATS_04 after a consumer (Datasphere) creates the first subscription. Empty queue before that is normal.

Step 5: Configure SAP Cloud Connector

Objective: Enable secure RFC connectivity from SAP Datasphere (cloud) to the on-premise S/4HANA system.

Access Cloud Connector

• URL: https://localhost:8443
• Credentials: Administrator / manage

Configuration Steps

1. Connect to BTP Subaccount:
   • Open Cloud Connector admin UI
   • Add your SAP BTP subaccount (region, subaccount ID, user/password)
   • Verify connection status: Green/Connected
2. Add RFC System Mapping:
   • Go to "Cloud to On-Premise" > Add system mapping
   • Back-end Type: ABAP System
   • Protocol: RFC
   • Internal Host: localhost (or the actual hostname of your S4H instance)
   • Internal Port: Instance Number 00
   • Virtual Host: Define a virtual hostname (e.g., s4h-virtual)
   • Virtual Port: 00
3. Add Resources:
   • Add resource with path prefix: /
   • Access Policy: Path and all sub-paths

System Details (CAL Fully-Activated Appliance)

Step 6: Create Datasphere Connection

Objective: Set up the SAP ABAP connection in SAP Datasphere.

Connection Configuration

1. In SAP Datasphere, go to Connections > Create
2. Select connection type: SAP ABAP
3. Configure:

1. Click Test Connection

Expected Validation Result

Connection "ABAP_NSC_S4H" is valid, but not all features are available.
- Data flows are enabled.
- Replication flows are enabled.          <-- THIS IS WHAT YOU NEED
- Remote tables can't be used because of errors in the connection.