Encrypting and Reassigning Payloads

Use

You use this report (FEHR_CHANGE_ENCRYPTION_KEY) to encrypt, reassign, and decrypt the payloads for postprocessing orders.

Prerequisites

• To be able to reassign a payload, you need to have assigned an encryption key to a business process. Before you make this assignment, you need to create the encryption key in the Personal Security Environment (PSE).

  For more information, see Customizing for Cross-Application Components under General Application Functions  Error and Conflict Handler  Define Payload Encryption and under Encrypting Payload on Database Level.

• To be able to reassign or decrypt a payload, it needs to have been encrypted.

Features

The following functions are available in this report:

• Encryption

  To encrypt a payload, you need to specify three things in the report: The component, the business process, and the private address book for SSF (key).

• Reassignment

  If you change the Private Address Book for SSF into a business process, the encrypted payloads are decrypted and then encrypted with the new key.

• Decryption

  If you have not defined a private address book for SSF for a business process, or if the entry for the business process is missing, then the payloads are encrypted.

Activities

You use this report to execute the following activities:

• Check the use of keys in payloads

• Encrypt, reassign, or decrypt payloads

To call up this report, select transaction SE38 and run the report FEHR_CHANGE_ENCRYPTION_KEY.

Check the use of keys

You can find out which payloads have been encrypted with which key. To do so, execute the program in simulation mode.

Reassign payloads

The program divides the worklists for payloads of postprocessing orders that are to be reassigned into work packages and executes the reassignment for the payloads. You use the maximum number to define the number of objects to be processed. You need to switch of simulation mode.