Saving and Deploying Objects

This topic contains the following sections:

Save an Object

When you save an object, it is stored in the SAP Datasphere repository, which contains the design-time definitions of all your objects.

Design-time objects do not contain any data, but you can preview the data they will contain when they are deployed to the run-time environment (see Viewing Object Data). You can save an object even if it contains validation errors.

Create a Copy of an Object

You can create a copy of many types of objects by:

  • Selecting the object in the Repository Explorer and clicking Duplicate.

  • Opening the object in its editor and clicking Start of the navigation pathSave Next navigation step Save AsEnd of the navigation path

Deploy an Object

When you deploy an object, you create a run-time version for use in the SAP Datasphere database. All Data Builder objects must be deployed to be used productively.

To ensure run-time consistency, when you deploy an object, SAP Datasphere will review its lineage and deploy any objects that it finds that do not already have a status of Deployed. For information about viewing an object's lineage, see Impact and Lineage Analysis.

Deployment Status

The deployment status of an object is shown in its Status property, which can have the following values:

  • (Not Deployed) - The object has never been deployed and exists only as a design-time artifact.

  • (Deployed) - The object is deployed to the run-time database and its design-time and run-time versions are identical.

  • (Changes to Deploy) - The design-time version of the object contains changes that need to be deployed to make them available in the run-time.

  • (Design-Time Error) - The design-time version of the object is invalid. You can save an object with design-time errors, but you cannot deploy it. To correct design-time errors, review each of the validation messages in the editor, make the necessary changes, and then save the object.

  • (Run-Time Error) - The run-time version of the object is invalid and can no longer be used. Run-time errors may be caused by changes in one or more of the object's sources (see Modifying Objects That Have Dependent Objects). To correct the errors, review each of the validation messages in the editor, make the necessary changes, and then save and deploy the object.

Save Anyway and Deploy Anyway

When you try to save or deploy your object, the Validation Messages dialog opens to allow you to review these messages. You can still save or deploy your object (by clicking Save Anyway or Deploy Anyway), but you should aim to review and resolve these impacts as soon as possible. For more information, see Modifying Objects That Have Dependent Objects.

Debug View Deployment Issues with the View Analyzer

If your view contains very complex calculations or subqueries, includes multiple unions of large views, or has a complicated or deep dependency tree, then you may encounter performance issues (or even, very occasionally, out of memory errors) when deploying.

In such situations, you may be able to improve deployment performance or resolve the errors by persisting one or more of your view's sources. We recommend that you use the View Analyzer and look at the peak memory usage and duration values to guide you in these decisions (see Exploring Views with View Analyzer).

Run-Time Database Unavailable

The run-time database server might be unavailable under exceptional circumstances. In this case, a message strip is displayed informing you of the database status and the following features are disabled:

  • Deploy

  • Share

  • Delete

  • Source Browser

  • Preview Data

  • Import CSV File

  • Validate SQL and Preview Data

  • Run a flow

You can try to solve this issue by waiting a few minutes and refreshing your web browser. If the problem persists, open a support ticketInformation published on SAP site.