What action with a configuration object creates a D record in the database?

When dealing with configuration objects in SAP Integrated Business Planning (IBP) and how they interact with the database, the creation of a "D record" signifies the process of marking data as deleted. This is an essential aspect of managing data integrity and tracking changes over time.

Performing an active deletion involves removing a record in such a way that it is flagged in the system without actually purging it from the database entirely. By creating a "D record," the system preserves historical context, allowing for better data governance and auditing, while also ensuring that users can see that a record once existed but is now marked as deleted.

When modifications are made to an active record, it typically updates the existing entry but does not create a deletion entry. Generating a new object will involve creating new records rather than altering or deleting existing ones. Similarly, modifying an inactive record focuses on changes to data that has already been archived or flagged as inactive, yet it would not generate a D record because that action pertains specifically to active records that are being marked for deletion.

In summary, the action that specifically creates a D record is performing the active deletion, as it accurately flags the relevant data in the database as deleted while preserving the necessary historical information.