Ansicht
Dokumentation

AATP_PROD_ALLOC_DES - Data Destruction Product Allocation of advanced ATP

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.

Purpose

You can use this report to:

• Remove characteristic value combinations and all dependent data (allocation data, quantity assignments) based on selected customer(s), supplier(s) or contact person(s), based on the date on which a product allocation object was changed last or based on selected product allocation objects and characteristics.

• Remove past time series which have a (period) end date before a selected date.

• Remove aged data entirely or reduce the amount of aged data by defining the period end date for the allocation periods and any assigned and consumed quantities.

Features

You have five options for selecting data for destruction:

Option 1: Destroy characteristic value combinations based on customer(s), supplier(s) or contact person(s) defined on the Personal Data Selection tab.

To identify the characteristic value combinations for destruction, you must first create a policy and define retention periods per plant or plant country. If no policy is available for the ILM object, call transaction IRMPOL and select the following values:

• Policy Category: Retention Rules

• Object Category: SAP Business Suite

• ILM Object: AATP_PROD_ALLOC_DESTRUCTION

• Press New

To identify which characteristic value combinations and dependent data are to be destroyed, the system checks the product allocation object to which the characteristic value combination is assigned and the creation time stamp for the product allocation object. To identify the corresponding plant, the system checks the assigned product allocation sequence(s) and their assigned product-location combination(s).

Note:

• When this report is run, only those characteristic value combinations and their dependent data will be destroyed whose retention periods maintained in Customizing have been exceeded: any characteristic value combinations whose retention periods are still valid will not be destroyed.

• If multiple product allocation sequences have been assigned, the system must check all related product-location combinations to identify the relevant plant(s).

• If a product allocation object is not assigned to at least one product allocation sequence or if no product-location combination is assigned to the product allocation sequence, the data for the characteristic value combination(s) is destroyed.

• If you don't provide selection parameters on the Personal Data Selection tab, by default the system will only destroy all characteristic value combinations and dependent data containing blocked customers, suppliers and contact persons, if the retention periods maintained in Customizing have been exceeded: any characteristic value combinations whose retention periods are still valid will not be destroyed.

• All characteristic value combinations destroyed via the Personal Data Selection tab will be logged in the ILM notification framework. This helps to ensure that replicated data in connected systems can be handled accordingly to meet data protection requirements. For more information, see the ILM Notification documentation in the SAP S/4HANA product assistance under Cross Components -> SAP Information Lifecycle Management -> Using ILM Notifications.

• Data destruction will take place for aged data also.

Option 2: Destroy characteristic value combinations based on the date on which a product allocation object was changed last, as defined on the Last Change Date Selection tab.

Note:

• Unlike option 1, the destruction of characteristic values based on the last change date does not require a policy to be defined or retention periods to be checked. If you define a last change date, the system simply identifies all product allocation objects that were changed before the defined date and destroys their characteristic value combinations, their allocation periods as well as planned and consumed quantity data. The system does not, however, destroy the product allocation object(s).

• Data destruction will take place for aged data also.

• The default date displayed in the Last Change Before & Including field is five years from tomorrow's date.

Option 3: Destroy characteristic value combinations and all related data based on product allocation objects and characteristics specified on the CVC Selection tab.

Option 4: Destroy past time series which have a (period) end date before a date specified on the Delete Past Time Series tab (Delete Beforefield).

Note:

• For the date entered in the Delete Beforefield, UTC 0:00 a.m. will be taken as the point in time before which data will be selected for deletion. We recommend using the test mode to check whether all expected data is selected with the date entered.

• The default date displayed in the Delete Beforefield is five years from tomorrow's date.

Option 5: Destroy (complete or based on aging temperature) aged allocation periods and consumed quantity quantities, as defined on the Aged Data Selection tab.

Note:

• Selecting Destroy aged data before will destroy all aged allocation periods and assigned consumption quantity entries with a data temperature before the given date.

• The default date displayed in the Destroy aged data before field is five years from tomorrow's date.

• Selecting Destroy All Aged Data will destroy all aged allocation periods and assigned consumption quantity entries.

• Selecting Do Not Destroy Aged Data will not destroy any aged data. Use this option if you do not want aged data to be destroyed in batch mode running option 1 or option 2.

• You can display aged allocation periods and consumed quantities on the Aged Product Allocation Data card in the Product Allocation Overview app, provided you have selected the Aged Product Allocation Data card in the Manage Cardsfunction.

Further Selection Criteria

Note that:

• Depending on your settings for data aging, destroying aged data may result in a large data set for processing, potentially resulting in longer runtimes for this report.

• You cannot execute this report for more than one of the options detailed above simultaneously, otherwise you need to run the report in batch mode.

• If you run this report in batch mode, the report is executed according to the variant for which you provided selection parameters. However, option 1 (selection of personal data) cannot be executed in combination with option 2 (last change date) or option 3 (CVC selection). If selection parameters have been maintained for option 1, only option 1 is executed based on the selected parameters (entered selection parameters for option 2 or 3 are ignored). If you do not enter selection parameters for option 1, option 2 will be executed. If you do not enter selection parameters for option 1 and 2, option 3 will be executed.

You can combine option 1, option 2 and option 3 eachwith the following other options:

• Option 4 (using the default setting five years from tomorrow's date)

• Option 5 (using the default setting five years from tomorrow's date)

• If no selection parameters have been entered for option 1, the report will be executed based on the default setting (all characteristic value combinations containing blocked customers, suppliers or contact persons).

Activities

Irrespective of the option chosen to select data for destruction, you can run this report in two modes:

• Test Mode
  Simulates the destruction process as chosen in the selection criteria: the simulated results are logged and displayed using the standard functions defined in the Detail Log and Log Output fields.

• Production Mode
  Physically destroys the data as chosen in the selection criteria: the results are logged and displayed using the standard functions defined in the Detail Log and Log Output fields.

BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 10054 Date: 20240520 Time: 054637     sap01-206 ( 179 ms )