📋

Description

Error 5428, 'ERR_TEXT_FCA_FILE_READ', indicates that SAP S/4HANA failed to read a required text or FCA (Financial Compliance Analytics) file from the specified location. This error typically occurs during processes that involve importing data, generating reports, or executing specific business functions that rely on external text-based input.

💬

Error Message

ERR_TEXT_FCA_FILE_READ

🔍

Known Causes

4 known causes

⚠️

File Not Found

The SAP system could not locate the required text file at the specified path or the file was deleted.

⚠️

Insufficient Permissions

The SAP S/4HANA system or the user account lacks the necessary read permissions for the file or its containing directory.

⚠️

Incorrect File Path or Name

The file path or name specified in the SAP configuration, transaction, or user input is incorrect, leading to a failed lookup.

⚠️

File Corruption

The text file itself is corrupted, damaged, or in an unreadable format, preventing SAP from processing its contents.

🛠️

Solutions

3 solutions available

1. Verify File System Permissions for SAP Application Server easy

Ensures the SAP system user has read access to the directory containing the text file.

1

Identify the directory on the SAP application server where the text file is located. This is usually configured within SAP or specified in the program attempting to access it.

2

Log in to the SAP application server using SSH (Linux) or Remote Desktop (Windows).

3

Determine the SAP system user (e.g., `<sid>adm` for Linux).

4

Check the read permissions for this user on the target directory. On Linux, you can use the `ls -l` command.

ls -l /path/to/your/directory

5

If permissions are insufficient, grant read access to the SAP system user. On Linux, use `chmod`.

sudo chmod o+r /path/to/your/directory

6

Alternatively, if the file is meant to be accessed by a specific group, ensure the SAP system user is part of that group and the group has read permissions.

sudo chown <user>:<group> /path/to/your/directory
sudo chmod g+r /path/to/your/directory

7

On Windows, use File Explorer to navigate to the directory, right-click, select 'Properties', go to the 'Security' tab, and add/modify permissions for the SAP service account or `<sid>adm` user.

8

Retry the SAP operation that caused the error.

2. Validate File Existence and Path Correctness easy

Confirms the text file actually exists at the specified path and the path is correctly referenced.

1

Identify the exact path and filename of the text file that SAP is trying to access. This information is often found in the error message details, SAP ST22 dumps, or the program's configuration.

2

Log in to the SAP application server where the file is expected.

3

Navigate to the specified directory and verify the file's existence.

ls -l /path/to/your/directory/your_file.txt

4

If the file is missing, upload it to the correct location. Ensure the filename and case match exactly.

5

If the path is incorrect, correct the path in the SAP configuration or the program logic. This might involve checking transaction codes like `AL11` for directory structures or consulting with the functional consultant.

6

Review any SAP notes or documentation related to the specific function module or program that is failing, as they might specify expected file locations or formats.

7

Retry the SAP operation.

3. Check SAP Gateway Configuration for Remote File Access medium

Ensures the SAP Gateway is correctly configured to allow remote file access if the file is on a different server.

1

Determine if the text file is located on the same application server as the SAP instance or on a different host. This error can occur if SAP is trying to access a file remotely.

2

If the file is on a different server, verify the SAP Gateway configuration on both the source and target servers. Transaction `SMGW` is used to monitor and manage the Gateway.

3

Check the `gw/acl_mode` parameter in transaction `RZ10` (or `RZ11`). A value of '1' means the gateway uses the ACL file (`secinfo` and `reginfo`), while '0' is less secure and might not be suitable for file access.

4

Examine the `secinfo` file (usually located in the SAP instance's work directory) for rules that might be blocking the specific connection or file access. This file controls which external programs can connect to the Gateway.

5

If the `secinfo` file is restrictive, you may need to add an entry to allow the specific host and program to perform file operations. Consult SAP Note 1408081 for details on `secinfo` syntax.

# Example entry in secinfo file to allow remote file access from host 'remote_host' to program 'rfcp' (for RFC file transfers)
P TP=* HOST=remote_host ACCESS=* CANCEL=* DISPLAY=*
P TP=rfcp HOST=remote_host ACCESS=* CANCEL=* DISPLAY=*
# For specific file access, you might need to look at program names used by SAP for file transfer (e.g., `SAPFTP`, `SAPHTTP`).

6

Restart the SAP Gateway or the entire SAP instance after modifying `secinfo` or `gw/acl_mode`.

7

Ensure that the necessary network ports (e.g., SAP Gateway port) are open between the SAP application server and the server hosting the file.

8