How to Write to Space-Owned Tables (FSDM_DEMO) in SAP Datasphere ?

[MayuraNalawade]

Hello,

We have a local table DQ_RESULTS in the FSDM_DEMO space in SAP Datasphere.
Using the Datasphere UI, we can load data into this table through Data Flows or Transformation Flows without any issue.

However, we want to implement a stored procedure that should:

1. Read records from the view DQ_RULE_GENERATED_VW, which contains dynamically generated SQL statements (as column values).

2. Execute each of these SQL statements dynamically.

3. Insert the results into the DQ_RESULTS table in the FSDM_DEMO space.

Since SAP Datasphere does not support creating stored procedures directly in the UI, we attempted to build the procedure using the HANA Database Explorer.
But the database user available to us does not have the required SELECT/INSERT privileges on the FSDM_DEMO schema, so the procedure cannot read from or write to the table.

We also tried creating a Database User Group (DUG).
The DUG schema that gets created does not have read/write access to the DQ_RESULTS table in FSDM_DEMO.

We tested multiple users:

• FSDM_DEMO# → does not have read/write access to DQ_RESULTS

• DWCDBUSER# → has only SELECT, no INSERT privileges

So far, none of the technical options allow us to run a stored procedure or write into FSDM_DEMO tables.

---

Additional Issue

We are also connecting to the DQ_RESULTS table via a Python script using the DWCDBUSER# user.
Again, this user can read the table but cannot write to it.

All our tables, views, and flows are created inside the FSDM_DEMO space, so we need a supported way to write to these Datasphere-owned objects from:

• Stored procedures

• Database User Group schemas

• External scripts (Python)

At the moment we are completely blocked due to insufficient privileges, and it’s unclear whether such write access is intentionally restricted by design or if we are missing a configuration step.

---

Question

Is there any supported approach in SAP Datasphere that allows:

• dynamic SQL execution,

• writing results into a space-owned table,

• or enabling external tools (like Python) to write into space-managed objects?

If stored procedures, DUG schemas, and tenant-level users are intentionally restricted from inserting into space object tables, guidance on alternative supported patterns would be very helpful.

Any help or clarification would be greatly appreciated.

Thanks,
Mayura