Transport Your Content Through Content Network Storage

Using the Transport option, you can move content privately and share it with other systems through Cloud.

Who does this apply to?

Users who are assigned a custom role with the following permissions. The custom role can be based on the Admin or BI Admin standard application roles.
- Read, Maintain, and Share permissions for Lifecycle
- Manage permission for Public Files and Workspace

About Transporting Using the Content Network

To receive the content, the destination systems must have settings that allow imports from your system. For details, see Get Business Content and Samples from the Content Network.

Note

The source and destination systems need to be on the same quarterly version of SAP Analytics Cloud, or the following quarterly version. If the importing system is on an older version, the package won’t appear. If it’s two or more versions ahead of the exporting system, the package’s content may not be supported.

In Transport, you can share content across systems from one or more landscapes and set access rights for each sharing destination, for example, to allow other systems to update a package and export it again.

Each system can store up to 2048 MB of exported content for free in the My Content area.

Note

Transporting content is not allowed between SAP Analytics Cloud tenants that are based on:

SAP Neo and Cloud Foundry platform
EUDP (European Union Data Protection) and non-EUDP framework
Canary and Production release strategy

You can also share content across systems using local files. See Transport Your Content Through File System for details. Note that exporting and importing workspaces and workspace content is not supported using local file transport.

Tip

If your export contains many objects, you may want to organize the content so that it's easier to find:

Save the objects in the same folder.
Or, include the same keyword in the name of each object so that you can search for it.

About Exporting Private Objects

To export a private object, your administrator must enable Allow Private Objects Export in the System Configurations tab of the SAP Analytics Cloud.

Once it is enabled, you are able to choose the private objects from the Users folder and Start of the navigation path Workspace Next navigation step Users End of the navigation path folder for the new export workflow.

You can have private objects inside workspaces too. An administrator must grant permissions to specific teams and users to manage the private objects inside workspaces.

To export any private object, you must have these permissions:

Lifecycle rights with Read, Maintain, and Share permissions – enables you to read, maintain, and share objects.
Private Files rights with Create, Read, Delete, and Manage permissions - enables you to view and manage all user’s private objects. If you don’t have Manage permission, you can only see your User’s private objects.

You can either export packages that has public objects, private objects, or both public and private objects.

When you export a package that contains private objects, it is imported to the public folder in the target system by default. However, you can move it to the custom location based on the required authorization.

Suppose your administrator disabled the Allow Private Objects Export toggle and there are few packages that contains private objects. In such a case, only you can include public objects to your package. No other user will be able to view or edit any private objects.

Note

If you are exporting a public package that has private object dependencies, those dependencies are also selected by default.
If you are exporting a private package that has public object dependencies, those dependencies are also selected by default.

About Importing Private Objects

To import any private object, you must have these permissions:

Lifecycle rights such as Read, Maintain, and Share – enables you to read, maintain, and share objects.
Public Files access rights such as Read, Create – enables you to create and import private objects.

If your package includes private objects, it is imported to Start of the navigation path My Files Next navigation step Public Content Network End of the navigation path . However, you can move it to the custom location based on the required authorization.

Since you have imported the package, you have the required access permissions to the Content Network folder. You can share this folder and move objects from the folder to a custom location.

Note

If you already have a user-generated folder named as Content Network in My Files before importing private objects, you won’t be able to proceed with the import workflow. To proceed with the import of private objects, you must either rename/delete the existing user-generated folder. The Allow Private Objects Export toggle need not to be enabled to import private packages or public packages with private object dependencies.
Imported private objects is present in the Content Network folder. You can share the folder to a specific user or to all users with defined access rights.
By default, the imported private objects reside in My Files Public Content Network. However, you can move it to the custom location with required authorization. If you import those private objects again, it is saved in the specified custom location by default.

Exporting Content

Procedure

From the side navigation, choose Transport Export.

Under the tab Content Network Storage, select My Content folder.

The My Content page shows a list of packages and folders, including the packages that you have exported and the packages from other systems that you have permission to edit or delete. You can select the name of a package to get an overview of it.

This page also has a toolbar:

Tool	Description
New Export	Lets you create a new export package.
Create New Folder	Lets you create a new folder.
Share	Share Lets you set the sharing destination of the selected package or the folder and its contents. You can also change the sharing destinations for a package.
Settings	Lets you review the system’s storage settings. You also can add or delete systems to block content sharing.
Edit Details	When used on a selected folder, lets you change the name and description for the folder. When used on a selected package, lets you edit the contents or details of a package and export it again..
Delete	Lets you delete folders or packages. Once a folder is deleted, the folder and its contents will be removed from My Content folder and will not be accessible to any system it was shared with. Once a package is deleted, it is removed from My Content folder and can't be imported or edited from any system. However, each system that imported the package will still have access to the content itself.
Upload	Lets you upload packages from your computer. If you are uploading a package that already exists in the My Content folder, you can chose to replace the existing package.
Download	Lets you download packages to your computer.
Refresh	Lets you update the list so that you can see all the latest packages.

Select (New Export).

Tip

If you want to edit the contents or details of a package and export it again, select the package and select Edit Details. If you need to change the content, set the Modify Content switch to ON in the Choose Content page. Otherwise, leave this switch off.
On the Choose Content page, select the content that you want to include in your export.
The left-hand pane shows the list of all Object Types. You can use the list to select or deselect all of these object types.

The right-hand pane lets you navigate your folder structure and select objects or folders. When you navigate the folder structure, you can select content from the Public and System folders. Content from Team folders can be found within the System folder. You can also select content from workspaces by selecting Workspace.
When selecting the content you want to export, remember the following points:
- Workspace content can only be exported to and copied to new tenants with the exact same folder structure.
- If you select a translated story, the multilingual content is included in your export. For details, see Learn About the Translation Process.
- If an object you've selected depends on other content, the dependencies are automatically selected. For example, if you select a model, its dimensions will also be selected. To exclude selecting object dependencies, choose Ctrl or Command while selecting an object. If the object is selected with its dependencies, the Dependencies column shows a ✓ checkmark. If there is none, the column is empty.
- In the New Export workflow, the message strip about the dependency feature appears until you manually close it. When you select a object it selects its dependencies as well, but while unselecting that object it only unselects the object itself and not its dependencies.
Tip
- You can use the Search box to search for specific objects.
- You can show or hide the columns on the right side by selecting  (Show columns). By default, certain columns are selected to display, for example, Name, Description and Type. Select Restore Defaults to display the default columns. Selecting and deselecting the columns as per your needs allows you to define the visibility of the object properties.
Note
- When you edit a package, the Changed On details of the objects within the package reflects the updated date and time as it pulls the properties from the file repository. However, the object content remains same as it was during the last export/update time of the package.
  
  To update the whole package, you must modify the content at the package level. To do that, go to Package Edit Details.
- You can search the objects through the values of Name, Description, Type, Owner, Changed By columns. Also, sort the objects at column level.
- By default, Data column is not pre-selected. You can manually select the data checkbox to include the data of any object as per your need.
- Selecting the Data checkbox in export listing page adds the data of the parent as well as dependencies.
  
  To select or unselect specific object data, click Selected Objects option on the left pane and select Data checkbox for the required dependent objects.
When you've chosen your content, select Next.
In the Set Package Properties page, type a Name, Description, and Details for the package. If your content has terms and conditions, add them in the Details.
1. To export the package to a subfolder within My Content, type the folder path in the Location field, or select Browse next to it. You can create a new folder by selecting Browse and choosing (Create New Folder).
Use the Destinations section to choose the sharing destinations for the export, and their access level for the content.
1. Select (Add Destinations) to add a new sharing destination.
2. In the Destinations dialog, select the type of the destination that you want to add:
  - System: Select this option to add individual systems, based on their URLs. Select a Landscape, and copy the URLs to the Systems list.
    
    Note
    Two types of data centers host SAP Analytics Cloud systems: SAP data centers and non-SAP data centers. You can share to systems that use the same type of data center as yours. Systems hosted by SAP data centers use one digit in their URL, like us1 or jp1. Non-SAP data centers host systems that use two digits, such as eu10 or us30.
  - Customer: Select this option to add all systems that belong to one customer based on their ERP ID. Type the ID in the Customer field.
  - OEM: This option shares to all systems belonging to an OEM or partner, using their OEM ID. Type the ID in the OEM field.
3. In the Access box, choose the access level that you want the sharing destination to have. You can add more than one access level.
  - View: Your package will appear in the My Content folder for the destination systems, and their users will be able to view the name and summary.
  - Import: The systems' users can import the package from the My Content folder.
  - Edit: Your package will appear in the My Content folder for the destination systems, where users can make changes to the package and export it again.
  - Delete: From the My Content folder, the systems' users can delete the package.
4. Select Add to add the destination.
5. Add more destinations from as needed. You can also edit access levels or remove destinations from the Added Destinations table.
6. When you are finished, select OK.
If you want users to accept terms and conditions before importing the content, set the Terms and Conditions switch to ON.
Select Next to see an overview of your package.

If there are any problems, a warning icon () appears in the lower-left of the page. Click it to see how to fix them.
When everything looks good, select Export.

Results

You can check the progress of your export from the Notifications list. You'll also receive a message when it's complete, and you can check the Export Summary to see the status of all the objects in the package.

When the export completes successfully, the package becomes available in the My Content folder of the systems you chose. You can edit the content, share it with other systems, or delete it from here.

Importing Content

Procedure

From the side navigation, choose Transport Import.
Under the tab Content Network Storage, you can see a list of packages and folders.
Select the package that you want to import.

A dialog showing an overview of the content appears. In the Overview tab, look at the Import Overview table to get a quick summary of the import settings and whether any existing content on your system will be overwritten. If you need to change any settings, select the Import Options tab.
In the Import Options tab, select an option for the Overwrite Preferences.

If an object selected for import does not exist on your system, the object will be created and its data will be imported. For objects that already exist in your system, the Overwrite Preferences determine whether to update the object and its data.
Note
If objects or data on your system will be overwritten by the import, a warning appears in the import window, and next to the relevant objects in the Content list. If you have made changes or enhancements to your sample content, follow the instructions in the Next Steps section to avoid losing your work.
- Don’t overwrite objects or data:
  This setting prevents any existing objects in your system from being overwritten or updated with new data. You are notified if any of the objects selected for import already exist in your system.
  
  For example, you can choose this setting if you have replaced the data in an imported model with your own data, and want to avoid overwriting this data.
- Overwrite data only:
  If you have made changes to the structure of an imported model and want to avoid losing those changes, choose this setting.
  
  Data is imported into each object, but the objects themselves are not updated.
  
  The Privacy and Data Access Control settings for models, as well as the permission settings for users and roles, remain unchanged.
- Overwrite objects and data:
  Objects on your system can be overwritten and their data can be updated. The corresponding permissions assigned to each role are also updated.
  
  For example, you may choose this option if you are not using any of the content for business tasks.
  
  Select Remove permissions to remove the Privacy and Data Access Control settings for models and dimensions.
In the Import To field, navigate to a folder within the Public folder, where you want to import the package contents.
Note
- If you want to choose the import location for individual folders within the Public folder, set the Override Folder Import Location switch to ON. If you are reimporting a folder, the import location is automatically set to the same location as its previous import; it can't be changed. Also, you cannot modify the location of individual objects, such as stories or models present directly in the Public folder. For example, if you have imported some content into My Files/Public/Folder A, you can modify the location of individual folders in the package to Folder B and not any objects present in the root location.
- If the folders you are importing are within a workspace, you can't override the import location.
- If an imported object does not exist in the target, it is imported to the location you have selected in the target tenant and maintains same hierarchy as the source.
- If an imported object exists in the target, re-import updates the object in the respective target location.
- When importing private objects fails with error: Failed to create 'Content Network' folder, you must rename or delete existing 'Content Network' folder and retry import.
- Restoring Content Network folder from Deleted Files section, makes it available to All users.
In the Content list, choose which objects to import, and whether to include the data for each imported dimension and model.

You can select and deselect individual objects, or types of objects (for example, Models or Stories).

The Impacted Content column shows warnings for objects that will overwrite content on your system.
Select Import.

The import process begins. You receive a notification when the process is complete, or if an error occurs.

If you selected Don’t overwrite objects or data or Overwrite data only, a notification will let you know if any of the content wasn’t imported to avoid overwriting existing content.

To view the log of updates and imports for a package, select the package in the content network and choose (History).

Results

Note

The user who imports the package becomes the owner of it. However, the user must have read permissions on the relevant object types to access the package content.

Downloading and Uploading Files With the Content Network

You can download Analytics Content Network packages to a local file, and also upload those local packages to the Content Network storage.

To download or upload a package, the below points need to be taken into consideration:

The system toggle for Allow Download and Upload of Content Network packages is set to ON by default. Only the administrator can enable or disable the toggle.
You can perform download or upload only if you have Share permissions in the Lifecycle section..
The download or upload is available only to Private (My Content) packages.
Only one package can be downloaded at a time. Folders or multiple packages cannot be downloaded.
The package that is downloaded has a .package extension which is encrypted by default.
During upload, only encrypted .package files are uploaded.
When uploading a package, if the package version is greater than the SAP Analytics Cloud version, then the upload fails. Uploading a package succeeds only when the package version is less than or equal to the SAP Analytics Cloud version.
The packages that are pending for download are automatically downloaded when you sign in within 14 days. You have to initiate the download again after 14 days.