Kontakt

Ansicht
Dokumentation

RPUTX8D0 - Obsolete: Test Report to Check Encoding with SAPCryptolib

RPUTX8D0 - Obsolete: Test Report to Check Encoding with SAPCryptolib

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

Use

Obsolete - The program for checking the encryption is no longern needed. With the introduction of the signature for LStA and LStB, the functions for encrypting data have changed. Signing and encryption now take place in PI/XI or in BC with the certificates stored there. A PSE file is not longer needed for ELSTER in the HR system.

After setting up SAPCryptolib and creating the key file (PSE file), you can use this report to test the encryption and decryption.

Prerequisites

SAPCryptolib is installed (SAP Note 662340) and a PSE file was created with a key pair for the employer. After that, the open key of the clearing house was read. By generating credentials, it is possible to use the PSE without entering a PIN.

Features

For testing the functions of SAPCryptolib, the report performs the following steps in this sequence:

  1. Reading of the certificate of the employer (PSE file)

The program reads the PSE file of the employer and determines the employer’s DN (Distinguished Name).

  1. Encryption with DN of employer

The program encrypts a test string. The employer's public key is used for this purpose. The public key is determined using the employer's DN.

  1. Decryption with the employer's DN

The program decrypts the test string that it previously encrypted. Here it uses the employer's private key.

  1. Encryption with the clearing house's DN.

The the clearing house's DN is delivered in system table T50BS. The program encrypts a test string using the public key of the clearing house referenced by the DN. For this to take place, the public key must be imported in the PSE file of the employer.

  1. Reading of the DN list from the PSE file

All of the public keys imported into the PSE file are entered there with their DN. The list of DNs is read and output.

If errors occur when you execute the report, for more information see SAP Note 725508 "B2A: Troubleshooting Encryption of Employment Tax".

Selection

  • File Name of PSE

Name of the PSE file. Entering a path is not necessary. The system finds the file in the directory defined by the environment variable SECUDIR ($DIR_INSTANCE/sec).

  • PIN for PSE

No entry required. When the PSE is generated, a PIN is assigned for using it. The generation of credentials in the directory of the PSE provides an authentication mechanism that makes it unnecessary to enter a PIN again for the use of SAP applications. If there are no credentials for the PSE file, then you can also test the encryption by entering the PIN. The PIN is case-sensitive. However, the prerequisite for using SAPCryptolib for electronic tax returns (ELSTER) is that there are credentials for PSE. Example for Standard Variants

Entries for selection:

  • There are credentials for PSE

PSE file name: SAMPLECORP_1.pse

SAMPLECORP_1.pse PIN for PSE No entry; field remains blank

  • There are no credentials for PSE

PSE file name: SAMPLECORP_1.pse

PIN for PSE 123456






RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3494 Date: 20240601 Time: 195807     sap01-206 ( 64 ms )