Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
EHS (Application Component) Environment, Health and Safety⤷
CBEHS (Package) EH&S: Interface Objects
Basic Data
| Data Element | ESEIEFILE |
| Short Description | Path or Name of Transfer File |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PATHEXTERN | |
| Data Type | CHAR | Character String |
| Length | 200 | |
| Decimal Places | 0 | |
| Output Length | 200 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | File |
| Medium | 15 | File with path |
| Long | 20 | File with path |
| Heading | 55 | File with path |
Documentation
Definition
Specifies the full name of the transfer file with path.
Use
This file name specifies to which export file on the application server the data is written or from which import file on the application server the data is read.
Dependencies
Logical file names and file paths are supplied for exporting and importing transfer files. A physical file path on the application server is assigned to a logical file path. The physical file path and name are determined based on the assignment in the logical file name and output as default values.
If a physical file path and name for importing and exporting specifications, phrases, and sources, as well as for importing reports, have been specified in the Customizing activity "Specify Exchange Profiles", this file path and name are always output as default values for the transfer file path.
Assignment with Validation
The standard system supplies the following logical file names and corresponding logical file paths. These enable the validation of physical file paths and names:
Program 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
The transfer file path must match the assignment specified in the logical file path. You can change the file name of the transfer file. Any name can be chosen.
Example:
The following default value is output as the transfer file path: /USR/SAP/EHS_DATA/IMPORT/SPECDATA.DAT. You can change the SPECDATA.DAT file name. The path /USR/SAP/EHS_DATA/IMPORT/ must not be changed.
If the default value is determined from the exchange profile, validation is carried out using the logical file path. This means that the physical file path in the exchange profile must match the physical file path of the logical file path.
Note: If a physical file path has not been assigned to the logical file path in the Customizing activity "Specify File Paths and Names", no validation is carried out. The physical file path and name are assigned without validation (see below).
Assignment Without Validation
The standard system supplies the following logical file names and corresponding logical file paths. The system uses these logical file paths and names to import and export data without validation of the physical path:
Program Logical File Name Logical File Path
Report Export List for Export by Program EHS_EXP_CHEMTR_DOCUMENTS EHS_EXP_CHEMTR_DOCUMENTS_PATH
DOKX 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_TREE 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
Note: You can change the file path and the file name.
Example
Supplementary Documentation - ESEIEFILE 0001
Definition
Name of transfer directory with path
Procedure
Enter the path and name of the transfer directory for your application server from which you want to import Dok-X MSDS reports.
Examples
/USR/EHS_DATA/INBOUND/
Dependencies
For every Dok-X MSDS report that is to be imported, the following two files must exist in the transfer directory on your application server:
- A *.KEY file
This file is delivered by the Dok-X system and contains all key information on the report (identifiers for the specification, specification key, and so on).
- A *.PDF file
This file must correspond to a document type in the SAP component Document Management.
Your system administrator must ensure that *.KEY files created on a DOS system are converted to Unix format before they are imported.
History
| Last changed by/on | SAP | 20110901 |
| SAP Release Created in |
