
Hi,
We had a session on security hardening done in our ECC system by the SAP Basis team. As it was related to security hardening, from a vendor creation /update process perspective we were not much worried. The assumption was how was security hardening going to impact the process. And we were unpleasantly surprised while we tested in the QA environment.
Initial Analysis
We noticed that vendor update programs were going on error. There are certain programs to convert employee records to vendors. These were the first to go on error.
The error was something as below.
“ File ‘Filename’ is not in directory area ‘File path’ .”
Why the errors started?
As a part of the security guidelines by SAP released in 2021, Logical Path and File Names are to be used to protect Access to the File System. This is a part of feature which was already present before the upgrade. But it was backward compatible and was INACTIVE by DEFAULT. To activate this, we need to maintain the physical path using the transactions FILE (client-independent) and SF01 (client-specific). To add the aliases for the view V_FILEALIA, we can use transaction SM31.
So that security issues due to directory traversal are avoided, it is not possible to specify the target file system for the download directly in the syntax of the operating system. Instead you define one or more target directories as “logical files” and specify them in the configuration of the ABAP download service (see Maintaining Execution Parameters).
What was the config at vendor master which was failing.
The vendor master updation program RPRAPA00 uses path “/interface/<SYS ID>/<A FILE NAME> to update some vendor details in a named file in a file path defined on selection screen. This file path set on screen via variants.
Access to this path was no longer allowed directly, unless configured the way the system expects it.
Steps to maintain the config are as below.
The physical path is assigned to the logical path on system dependence syntax group(OS) level.
A logical path is mapped to physical path as below.
Thus, the vendor programs which were accessing a location “/interface/<SYS ID>/<FILE NAME>, to update vendor records in a named file in the file system were correctly pointed to the correct file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |