Solution : https://service.sap.com/sap/support/notes/35992 (SAP Service marketplace login required)
Summary :
This SAP Note addresses how to correctly establish logical and physical names and paths for archived files when utilizing application archiving tools, namely Transactions F040 for SAP Release 2.1/2.2 and SARA from Release 3.0 onwards. For F040, maintain logical names and assign physical paths accordingly. As of SARA Release 3.0, follow customization menus to define logical names, paths, and assign the necessary physical elements using Transaction FILE. Importance is placed on ensuring accurate syntax group settings for file paths, especially across UNIX and NT servers, to allow seamless archiving operations and accessibility across diverse system infrastructures. Attention must be given to client-specific settings and dynamic parameters to avoid conflicts and ensure file integrity during archiving runs.
Key words :
<param_1>_<date>_<time>_<param_2>, \\my_host\sapmnt\<sid>\sys\global, \usr\sap\<sid>\sys\global, sap archivelink processes physical file names, /usr/sap/<sysid>/<client>/<filename>, \usr\sap\<sysid>\<client>\<filename>, /usr/sap/<sysid>/archive/<filename>, 'client-independent file names/paths, message long text states, sap archivelink root directory
Related Notes :
| 1268106 | Archiving object for tables CEPZ, CPZP and CHZP |
| 946519 | Archive Routing at directory level |
| 395766 | Storage of archive files as of SAP Basis Release 4.6C |
| 147721 | Request management and asynchronous archiving |
| 110923 | Archives cannot be read or accessed |
| 103733 | COMPOSITE SAP NOTE: ALL NOTES ON DATA ARCHIVING |
| 89324 | Archiving: Revised ADK versions |
| 80563 | EM BA110 in single doc.access from optical archive |
| 68519 | Archiving/Reorg.: no request for ArchiveLink |
| 41363 | Archive files are not found |
| 32344 | No deletion of equipments and functional locations |
| 24207 | Platform-independent file names do not function |