SAP Knowledge Base Article - Public

3489447 - Datasphere shared object cannot be exported


  1. Exporting an object that uses shared objects in another space cannot be completed. After selecting the object, SAP Datasphere UI is hanging.
    In the network trace the request will be failed with the following error message: 400 Bad Request
  2. Bad Request when browsing/expanding Folders.


SAP Datasphere Wave 2024.14

Reproducing the Issue

  1. Navigate to Transport >Export >New Export (+)
  2. Open the developer tool and navigate to the Network
  3. Choose the space where the shared object is located
  4. Click on the object to exported
  5. In meantime see the error message in network trace as shown below:


Request sent by ACN is not valid.


The fix for this problem is planned to be deployed in SAP Datasphere Wave 2024.15.

Before that, following recommendations can be applied as a workaround:

  1. Create transport package for the shared object .
  2. Create transport package for the object which is deployed in another space.
  3. Do the export using the repository packages created.

For example, object O1 in space S1 and shared with space S2. In space S2, object O2 is using this shared object O1. If users want to export object O2:

  1. Create transport package P1 for object O1.
  2. Create transport package P2 for object O2 (make the P1 as required package).
  3. Export these transport packages.

See Also

Creating Packages to Export | SAP Help Portal


400 Bad Request, shared object, space, export, acn , KBA , DS-MD-REPO , Repository Backend , DS-MD , Modeling (Data Builder) , DS-MD-TAB , Tables , DS-SM , Space Management , Problem


SAP Datasphere all versions