Ansicht
Dokumentation

/SMB/FILE_STATE - Delta-Based Content Lifecycle: File State

/SMB/FILE_STATE - Delta-Based Content Lifecycle: File State

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you can display, change, delete and generate File State records. The File State record is used in Delta-Based Content Lifecycle to restrict the number of files to be processed while upgrade/update.

Integration

The File State is evaluated in the Lifecycle of a Customer Solution while upgrade/update.

Prerequisites

You require authoring change authorization to delete/change/generate File State (authorization object S_SMB_AUTH activity 02).

Force Improvement is not set while Lifecycle.

Features

The File State is calculated for each file that is part of the Scope of the Customer Solution. The File State is used to identify which files of a new content version has been changed. Only changed files shall be uploaded and processed. The File State of a file consists of four hashes:

  • Hash of file content
  • Hash of Criteria assigned to the file
  • Hash of Activity where the file is assigned to
  • Hash of Modify Options assigned to the file

The calculated File State is stored per customer solution and used in the next upgrade/update for comparison.

Only following criteria take part in hashing: 'KEEP_DURING_UPGRADE', 'REMOVE_UNLESS_ACTIVATED', 'ASSIGNM_REL_FOR_EXTENSION', 'RELEVANT_FOR_EXTENSION', 'FLEXORG_COPY_RELEVANT'

The activity hash includes values of fields FILENAME, OBJID, OBJTY, IMG_ACTIVITY, CUST_OBJTYPE, CUST_OBJNAME, SUBOBJNAME.

Selection

Standard Variants

Output

Activities

The File State is calculated by system while the Lifecycle. You can delete or generate the File State of a Customer Solution to force that the file is imported and processed.

Example

When Content Lifecycle is executed, the system imports the new version of the reference content that consists among other things of TDC and installation files. In case of an upgrade/update only a subset of these TDC and installation files are new or have changed content. To process the new or changed files alone, the system calculates first for each file of the reference content the four above-mentioned hashes. Then system checks whether there is already a File State for that file and --if yes-- whether one of the hashes has been changed. When the file is new or changed, the indicator 'To be processed' (' Process ') is set. When there is already a File State and the file is not changed then the indicator 'To be processed' is returned (it may then be set or not). When indicator 'To be processed' is set then this file is imported and processed in the follow-up steps.






BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2950 Date: 20240329 Time: 135257     sap01-206 ( 62 ms )