Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

New Features

Retention management - Legal hold

Build-in retention management was extended with so much needed functionality to set Legal hold for a specific selection of stored ADK files. You are able to create multiple legal holds that selection can overlap, in such cases, files are not in legal hold only after each of them are released. When the legal hold is created for a particular file, it will not be marked for deletion and deleted until it is not released. You can access new functionality using cockpit transaction /DVD/EM or directly using /DVD/CRP_RMI_LH transaction.

Retention management - Support for multiple legal entity fields

There was a need to create retention rules that consider a combination of multiple legal entity values, like company code, plat, etc. Now you can define as much legal entity field as you please. The only limitation is that the result entity value that is a combination of the defined fields separated by dash cannot overcome 255 characters.

Retention management - Re-registration of the ADK files

Customizing retention fields for archiving objects is important to have it set before you start registering the ADK files into retention management. There can be situations that you need to do the change this customizing even though you already registered some of the files. When the customizing is changed, you need to register your files again to take into account the new setup. This feature will enable you to do it.

Lookup translation tool

When data is archived there is a limited possibility to access this data. Multiple standard SAP transactions are handling access to the archived data but this could not be the case for your custom reports. To get data to your reports, you need to adjust your custom development to be able to read data from the archive. This can take a lot of time and effort to identify the places in code that needs to be adjusted and then do the adjustment the right way. The functionality of Lookup translation will do this for you automatically. Together with ADK storage, you can easily access archived data from your custom reports with very little effort. If you would combine this functionality with our transparent archive it will give you the possibility to access your data even with good performance.

Mass archiving - new archiving objects supported

Functionality was extended with the following archiving objects:

Archiving object

Description

BC_DBLOGS

Archiving Changes to Customizing Tables

CHANGEDOCU 

Change Documents

MM_EINA 

Purchasing Info Records

PP_ORDER 

Production Order

RL_TA 

MM-WM: Warehouse management: Transfer orders

WORKITEM 

Work Items from Workflow System

Mass archiving - variant preparation in the background

Allowing execution of preparation (execution of analysis and variant creation) of the variants in a background job. Formerly this was executed in dialog and for some cases, it would be sufficient. But for some cases when the header table contains too much data it can lead to timeout of dialog sessions that end up in runtime error.

Mass archiving - implicit filter functionality for specific archiving object

In order to get more accurate results for variant generation, there is a need to add implicit filters that are intercepted with user-defined selection. An example of such archiving object is IDOC where filter status is automatically intercepted with user-given selection.

Usability improvements

General

  • Rename of the product and logs

  • Go to the menu for /DVD/EM transaction to access main product features

Content server

  • ICM parameters check - save current parameters

    • In the ICM parameter checking functionality was enhanced with the save function. You are able to save current values that are set as ICM parameters and when these parameters are changed in the future you will be able to directly see which parameter value was changed and what was the value. This comes in handy during troubleshooting that could relate to changed ICM parameters.

  • Source deletion - check before deletion

    • Before the deletion of the Source ID, the check was added to check whether all dependent tables are already deleted. This prevents deleting Source ID that still contains stored data.

  • New authorization role /DVD/CRP_SERVICE_ALL

    • New authorization role was created that contains all necessary authorizations needed to use any binary storage from storage management.

  • Source definition - check whether the user selected binary storage

Retention management

  • Search helps for fields in Retention definition

  • Retention scan/delete - Added "Document ID" as select option

Mass archiving

  • Variant description as archiving sessions notes

    • Variants are generated with description that reflects the selection of the variant, this information is now also propagated into archiving notes. These notes are visible in archiving session management in transaction SARA, so it is easy to say which session consists of which selection.

  • Check of the logical file name in archiving object customizing is SARA

    • To avoid wrong customizing for archiving object in execution, we are executing check in the Phases step whether the logical file name is valid and accessible.

  • Minimum number of objects in a variant

    • In order to have more control of creation and grouping data into variants, we added the possibility to limit the number of objects in a variant. If the variant defined by selection and possible semantic groups doesn’t overcome a specified number then it will be excluded from execution.

  • Time distribution based on retention date field for a variant generation

    • Data that should be archived can be split based on date ranges like a month, quarter, and half a year

  • Check parameters of the write report

    • Generation of the variants expecting specific parameters of the write report of archiving object, if these parameters differ from which generation of the variants was designed it cause the troubles during the execution of the archiving. Therefore we are checking the parameter list for archiving objects whether is the same as during design time, if there is any change user is notified that such change was done.

  • Check retention date field is in screen

    • Checks whether the same field defined as retention date field is used on write report of archiving object

  • Disable retention management phase when storage phase is not checked

Transparent archive

  • Single language in search help - selection of archiving object in setup

  • Search help that displays only transparent storage

  • Possibility to execute transparent archive for files for which wasn’t executed store phase

Analyzer

  • Straggler analysis - blocking rule percentage below 1%

    • If the rule is blocking less than 1% of the object’s data it will be shown as <1 %, previously it was rounded to 0 % which is inaccurate.

Bugs fixes

Analyzer - dropdown shows only one arch object

When you want to access the result of the analysis run that was analyzing multiple archiving objects, you were not able to choose between them using the dropdown popup menu. This issue was relevant only for users that are using web access or the Java version of SAP GUI.

Mass archiving - wrong archiving object in run list

There was a situation when you got into mass archiving wizard but did not choose to archive object and got back to run list and you could see the wrong archiving object of your run.

  • No labels