Kontakt

Ansicht
Dokumentation

CM_IMPORT_CONSENT_FROM_SERVER - Consent Administration: Import Consent from Server

CM_IMPORT_CONSENT_FROM_SERVER - Consent Administration: Import Consent from Server

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this report to import consent records as copies that are stored on an application server. This might be necessary, for example, if Consent Administration is used for the first time and already existing consents need to be part of an initial load.

The import process is particularly important to make consent data available in your local system, so that a data subject’s consent can be proven if necessary.

Integration

Prerequisites

  • The consent record to be imported must be stored in a JSON file on your application server. You need the general permission to import consents as well as the permission for importing consent records, for example for certain data controllers or purposes.
  • The logical file path CON_CONSENT_UPLOAD_PATHmust be assigned a valid physical file path on the application server. Following this physical file path, the relevant files can then be selected using this report. The files must be located in the specified directory. You can make the assignment of physical paths to logical paths in the Maintenance Environment for File Management (transaction SFILE).

Features

The report offers several selection criteria to further define the import process of a file located on the application server. See section below for more information.

Selection

In the File Attributessection, use the Import Filefield to specify the file that contains the consent records you want to import. You can either do this by directly entering the file path and file name or by browsing for the path and file name. For the browsing option, position your cursor on the input field and choose the value help (F4).

In the Control section, you have the following options:

  • External Log ID
This field is optional. You can specify your own log ID to make the application log easier to find in transaction Analyze Application Log (SLG1). This only applies to saved logs.
  • Save Application Log
If you select this option, the application log will be saved. If not, the log of a particular file import and related log entries will only be temporarily available, i.e. directly after the import has been carried out. It is recommended to select this option, if you do not run the report in test mode and consent records are imported and stored in the consent administration system.
  • Application Log Detail Level
Position your cursor on the input field and choose the value help (F4) to specify the log level. The following levels are available:
  • Level 1: General info is logged, e.g. import file, date / time of import, number of successful imported consent records, number of erroneous consent records that could not be imported.

  • Level 2: In addition to level 1, log entries are created for each erroneous consent record.

  • Level 3: In addition to levels 1 and 2, log entries are created for each erroneous field of an erroneous consent record.

  • Level 4: In addition to levels 1, 2 and 3, also for successfully imported consent records log entries are created.

  • Other (not used)

  • Change Document for Insert
When importing and storing consent records in the consent administration system, change documents can be created. This is particularly important for consent records that are already stored in the consent administration system and that are updated by a more recent consent import, for example because they have been withdrawn.
If a consent record is imported for the first time, a change document is not created by default, because the consent record indicates the current status of the consent. If, however, you still want to create change documents, select the option Change Document with Insert.
  • Test Run
If you select this option, the import will be carried out in test mode. Consent records to be imported are analyzed / validated. Log entries are shown according to the specified log settings. No consent records will be stored in the consent administration system.
  • Skip Expired Consents
If you select this option, the import will skip expired consent records by sorting them out in the validation.
Please note that the lifecycle status is recalculated when triggering the import, e.g. consent records that were in status Activebefore might be rejected for the import, because their lifecycle status changed during runtime.
Choose Execute to start the import process.

Standard Variants

Output

The system displays the log entries according to the specified log settings.

If the control option Save Application Logwas selected, consent import logs can be viewed later on using transaction Analyze Application Log (SLG1).

Activities

To access this report on the SAP Easy Access screen, choose Cross-Application Components-> Data Protection-> Consent Administration-> Import Consent Records from Server.

Further Information

If your consent data is stored in a JSON file that has a structure different from the default file structure required by Consent Administration, you can implement BAdI: Define Source Format for Import Processing. This BAdI enables you to map the attributes maintained in your JSON file to the default structure required for the import. For more information, go to Customizing for Cross-Application Components under Data Protection-> Consent Administration-> BAdI: Define Source Format for Import Process Mapping.






BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 7140 Date: 20240520 Time: 061900     sap01-206 ( 126 ms )