Show TOC

Background documentationFunctional Constraints of Processes Locate this document in the navigation structure

 

The lock logic between the load, activate, and delete processes of a DataStore object is as follows:

Recommendation Recommendation

To ensure that the various processes do not lock each other out, we recommend that you use process chains. See also the example for Including DataStore Objects in Process Chains. When designing complex process chains, you yourself have to ensure that these processes do not lock each other.

End of the recommendation.
While loading:

It is not possible to:

  • Delete the contents of the DataStore object

  • Archive data

It is possible to:

  • Delete data request by request

  • Delete data selectively

  • Activate data

During Activation

It is not possible to:

  • Delete the contents of the DataStore object

  • Delete data request by request

  • Delete data selectively

  • Delete master data

  • Archive data

  • Reactivate data

  • Update data to other InfoProviders.

While Deleting Individual Requests

It is not possible to:

  • Delete the contents of the DataStore object

  • Start deleting more requests

  • Delete data selectively

  • Activate data

  • Archive data

  • Update data to other InfoProviders.

During Selective Deletion of Data

It is not possible to:

  • Delete the contents of the DataStore object

  • Delete data request by request

  • Start deleting more data selectively

  • Activate data

  • Archive data

  • Update data to other InfoProviders.