Hierarchy

⤷

⤷

IMG Activity
ID | EHS_SRE_IMP_70_OA | EHS: Maintain File Names and File Paths (Cross-Client) |
Transaction Code | S_EE6_85000099 | (empty) |
Created on | 20101105 | |
Customizing Attributes | EHS_SRE_IMP_70_OA | EHS: Maintain File Names and File Paths (Cross-Client) |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | EHS_SRE_IMP_70_OA |
Use
In the Customizing activity Cross-Client Maintenance of File Names and Paths, you specify the physical file paths and file names that correspond to the logical file paths and file names delivered.
There are two types of logical file names and paths in Customizing for EH&S.
- With '_2' ending: When data is imported or exported, the physical file path is validated. This means that the data can only be exported from the physical directory of the application server or imported to the physical directory of the application server. The physical directory of the application server must be assigned to the logical file path.
- Without '_2' ending: When data is imported or exported, the physical file path is not validated.
If you want to validate the physical file paths, you have to edit the logical file names and file paths ending with '_2'.
Requirements
Standard settings
Default Settings for Assignment with Validation
Description Logical File Name Logical File Path
Export of Phrase Libraries EHS_EXP_PHRASES_2 EHS_EXP_PHRASES_PATH_2
Export of Property Tree EHS_EXP_ PROPERTY_TREE_2 EHS_EXP_ PROPERTY_TREE_PATH_2
Export of Sources EHS_EXP_SOURCES_2 EHS_EXP_SOURCES_PATH_2
Export of Specification Master Data EHS_EXP_SUBSTANCES_2 EHS_EXP_SUBSTANCES_PATH_2
Export of Report Templates EHS_EXP_TEMPLATE_2 EHS_EXP_TEMPLATE_PATH_2
Import of Phrase Libraries EHS_IMP_PHRASES_2 EHS_IMP_PHRASES_PATH_2
Import of Property Tree EHS_IMP_ PROPERTY_TREE_2 EHS_IMP_ PROPERTY_TREE_PATH_2
Import of Sources EHS_IMP_SOURCES_2 EHS_IMP_SOURCES_PATH_2
Import of Specification Master Data EHS_IMP_SUBSTANCES_2 EHS_IMP_SUBSTANCES_PATH_2
Import of Templates EHS_IMP_TEMPLATE_2 EHS_IMP_TEMPLATE_PATH_2
Import Reports EHS_IMP_REPORT_2 EHS_IMP_REPORT_PATH_2
Upload and Download of Files EHS_FTAPPL_2 EHS_FTAPPL_PATH_2
Default Settings for Assignment Without Validation
Description Logical File Name Logical File Path
Report Export List for Export by Program EHS_EXP_CHEMTR_DOCUMENTS EHS_EXP_CHEMTR_DOCUMENTS_PATH
Dok-X Report Export List EHS_EXP_DOKX_DOCUMENTS EHS_EXP_DOKX_DOCUMENTS_PATH
Export of Phrase Libraries EHS_EXP_PHRASES EHS_EXP_PHRASES_PATH
Export of Property Tree EHS_EXP_PROPERTY_TREE EHS_EXP_ PROPERTY_TREE_PATH
Export of Sources EHS_EXP_SOURCES EHS_EXP_SOURCES_PATH
Export of Specification Master Data EHS_EXP_SUBSTANCES EHS_EXP_SUBSTANCES_PATH
Export of Report Templates EHS_EXP_TEMPLATE EHS_EXP_TEMPLATE_PATH
Import of Phrase Libraries EHS_IMP_PHRASES EHS_IMP_PHRASES_PATH
Import of Property Tree EHS_IMP_PROPERTY_TREE EHS_IMP_ PROPERTY_TREE_PATH
Import of Sources EHS_IMP_SOURCES EHS_IMP_SOURCES_PATH
Import of Specification Master Data EHS_IMP_SUBSTANCES EHS_IMP_SUBSTANCES_PATH
Import of Templates EHS_IMP_TEMPLATE EHS_IMP_TEMPLATE_PATH
Upload and Download of Files (Application Server) EHS_FTAPPL EHS_FTAPPL_PATH
Upload and Download of Files (Front-End PC) EHS_FTFRONT EHS_FTFRONT_PATH
Activities
- You can define paths in exchange profiles that you can assign to the import or export of the following data:
- Sources
- Phrases
- Specifications
- Reports (import only)
If you assign an exchange profile during an import or export, the original file path and file name are overwritten.
Activities for assignment with validation (for logical file paths and file names ending with '_2')
- Assign the corresponding physical file paths to the logical file paths.
- In the logical file name, you can enter a subdirectory in the Physical File field that differs from the values specified in the input help. The DIR file format in the logical file name may not be changed, however.
- In the logical file name without the '_2' ending, specify the physical file name with the ASC data format.
Note: The logical file name is used to determine the physical file path as the default value for the path of the transfer file. The physical file name is determined as the default value from the logical file name without the '_2' ending and added to the path of the transfer file.
Example: Importing specification master data
- The logical file name EHS_IMP_SUBSTANCES_2 is assigned the logical file path EHS_IMP_SUBSTANCES_PATH _2. The logical file path is assigned the physical file path /USR/SAP/EHS_DATA/<FILENAME>. In the logical file name EHS_IMP_SUBSTANCES, SPECDATA.DAT is specified as the physical file name. As a result, the system determines the following default value for the transfer file: /USR/SAP/EHS_DATA/SPECDATA.DAT.
- The logical file name EHS_IMP_SUBSTANCES_2 is assigned the logical file path EHS_IMP_SUBSTANCES_PATH _2 and the subdirectory IMPORT. The logical file path is assigned the physical file path /USR/SAP/EHS_DATA/<FILENAME>. In the logical file name EHS_IMP_SUBSTANCES, SPECDATA.DAT is specified as the physical file name. As a result, the system determines the following default value for the transfer file: /USR/SAP/EHS_DATA/IMPORT/SPECDATA.DAT.
Notes
- If a physical file path and name for importing and exporting specifications, phrases, and sources, as well as for importing reports, were specified in the Customizing activity Specify Exchange Profiles, this file path and name are always output as default values for the transfer file path. As a result, validation is carried out based on the logical file path. This means the physical file path in the exchange profile must match the physical file path of the logical file path.
- If you have not assigned a physical file path to the logical file path, no validation is carried out. The default value is determined from the logical file path without the '_2' ending (see below).
- If you change the path, the system validates the corresponding physical file path for logical file names and paths.
Activities for assignment without validation (for logical file paths and file names ending with '_2')
- Assign the corresponding physical file paths to the logical file paths.
- In the logical file name, specify the physical file name with the ASC data format.
Note: The logical file name is used to determine the physical file path as the default value for the path of the transfer file. The physical file name is determined as the default value from the logical file name and added to the path of the transfer file.
Example: Import of Specification Master Data
The logical file name EHS_IMP_SUBSTANCES is assigned the logical file path EHS_IMP_SUBSTANCES_PATH and the physical file name SPECDATA.DAT. The logical file path is assigned the physical file path /USR/SAP/EHS_DATA/<FILENAME>. As a result, the system determines the following default value for the transfer file: /USR/SAP/EHS_DATA/SPECDATA.DAT.
Notes:
- For importing and exporting specifications, phrases, and sources, as well as for importing reports, you can specify a physical file path and name in the exchange profile. The file path and name are then output in the File field as default values of the transfer file. If a file path and file name were not specified in the exchange profile, the default value for importing and exporting specifications, phrases, and sources is determined from the logical file name. A default value is not determined for importing reports.
- You can change the transfer file path manually before starting the import or export from the application. The report export is the only exception. The SAP system uses the physical file path specified here without prompting for a path.
Activities for physical report export path without validation
- Select:
- The logical file path EHS_EXP_DOKX_DOCUMENTS_PATH for the Dok-X report export
- The logical file path EHS_EXP_CHEMTR_DOCUMENTS_PATH for the report export by program
- Under Assignment of Physical Paths to Logical Path, choose the group appropriate for your system as the system group.
- Enter the physical file path in the detail view for the group.
Caution:
- To ensure that the report export orders are taken into account when they are created from the report information system and during automatic post-export in accordance with the initiator, you must include the placeholder <PARAM_1> in the path definition. The program replaces the placeholder with the initiator ID at runtime.
- If you run the report export from multiple clients or systems that use the same file system, you must also include the client <CLIENT> or the system <SYSID> as a placeholder in the path definition.
Example:
A definition of a physical file path on UNIX could look as follows: /USR/<SYSID>/LOCAL/DOKX/<CLIENT>/<PARAM_1>/<FILENAME>. Assuming the report export was started in client 011 in system SHE by initiator 0001, the actual export path would look as follows: /USR/SHE/LOCAL
Business Attributes
ASAP Roadmap ID | 250 | Define Number Range and Basic Structures |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | EHS_SRE_IMP_70_OA | 0 | HLB0009032 | Use Subcomponents |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20101105 |
SAP Release Created in | 606 |