Remodeling DataStore Objects (Advanced)
If your DataStore Object (advanced) is empty, changes are possible in the BW Modeling Tools without further activities. However, if it already contains data, to activate the object properly, the system follows a predefined logic to decide whether an additional manual remodeling task is required. This also applies to the transport management when you provision these changes to the production system finally. The separate remodeling job´s role is to keep the activation time to a minimum and thus to avoid terminations during the direct execution, for example, time-outs. This safety belt is justified, because changes to DataStore Object (advanced) with a lot of data can cause a lot of read and write operations to the existing data in the DataStore Object (advanced).
The remodeling requirements are not limited to the changes offered by the Remodeling button in the DataStore Object (advanced) modeling UI of the BW Modeling Tools. The remodeling framework is also used when other changes require crucial read and/or write activities on the DataStore Object (advanced) database tables. For example, changes to general modeling properties, changes to the DataStore Object (advanced) key, changes to indices, partitions, or Data Tiering settings.
In the SAP BW Modeling Tools, open the DataStore Object (advanced) that you want to modify. If you want to use the standard DataStore Object (advanced) remodeling options, select Remodeling on the Details tab. Then the following options are available. Refer to the SAP BW/4HANA application help for extra details on restrictions and ways of working:
- Replace InfoObject by another one
- Replace InfoObject by a field
- Replace field by another one
- Replace field by an InfoObject
- Fill with value of InfoObject
- Fill with value of field
- Fill with constant value
During activation, the system checks whether the object can be activated immediately, or whether it must be remodeled first. If remodeling is required, a warning appears: Remodeling is pending. DataStore object is not activated. Please run remodeling. This means, the object is not activated yet and a remodeling request is created. If you have made two or more changes to your object, these changes are compiled into one remodeling request. You can continue to use the old DataStore Object (advanced) version. Until then, the remodeling request is not executed.
Open the app Remodeling Requests in the SAP BW/4HANA Cockpit or use transaction RSMONITOR to open the remodeling monitor in your SAP BW/4HANA system. Identify the generated request and start or schedule it manually.
Let's say that you want to transport a remodeled DataStore Object (advanced) to the test system and then to the productive system. If the object already exists in the productive system, the system checks whether remodeling is necessary. The required remodeling request is then created in the target system. If you want to transport a DataStore Object (advanced) for which a remodeling request has been created but not yet executed, a warning informs you that the M version and A version are different. You can only transport the A version (without the current changes).
Hint
For more details, refer to the blog "Role of Remodeling in the ADSO Change Management Process": https://blogs.sap.com/2020/11/30/role-of-remodeling-in-the-adso-change-management-process/.
