Ansicht
Dokumentation
EHFND_HCM_PTY_DEST - Specify Destinations for Integration
BAL Application Log Documentation Vendor Master (General Section)This documentation is copyright by SAP AG.
In this Customizing activity, you can specify destinations for integrating other SAP components into the Environment, Health, and Safety component or into the Product Compliance for Discrete Industries component. You can access the data in those components directly on your local system or using an RFC connection to a remote system. Some data is available only on the local system. You can also specify destinations for integrating the Environment, Health, and Safety component with external systems, so that you can send data to these external systems.
Access to Data Available via a Remote System
If you want to use data that is stored in a remote system, you can specify the RFC destinations individually in this activity.
You can integrate the following components and systems:
- Plant Maintenance
- Extended Warehouse Management
- Occupational health application of SAP EHS Management as part of SAP ERP
Note: For Product Compliance for Discrete Industries it is sufficient to use only the available data via your local system.
Note: You need to specify whether the remote system is SAP S/4HANA or not via the S/4HANA System checkbox.
Access to Data Available via the Local System Only
The system cannot read some data via remote access, such as data from Customizing and specific data from components that you may have already integrated. You can access this data via the local system only. For more information about the data that you cannot access via remote access, see Notes below.
Send Data via an HTTP Server
If you want to send data to an external system, you can specify an RFC destination in this activity. You can integrate with workers' compensation associations in Germany that are using the SIGUV interface.
You have defined RFC connections of connection type 3 (ABAP connection) or G (HTTP connection to external server). To check and define RFC connections, on the SAP Easy Access screen, choose Tools -> Administration -> Administration -> Network -> RFC Destinations or call up transaction SM59. You can specify a name for the RFC destination.
- Note: To maintain RFC connections, you require authorization object S_RFC_ADM and permissions for activities 01, 02, 03, and 06 (insert, modify, show, and delete). The user that needs to be able to read RFC connections at runtime, requires permissions for activity 03 (show).
You have ensured the following:
- You are using R/3 Enterprise 4.70 Extension Set 2.00 (Basis 620) or higher for the remote system of all other systems.
The standard system is delivered without RFC destinations. You can access data from the local system only.
To access data from a remote system or send data to an external system, perform the following steps:
- Choose the system for the destination type.
- Enter an existing RFC destination (connection type 3 or G) for the specified system.
- Note: The remote system for PM assets, PM notifications, and PM orders is always the same system.
- ,,Select the S/4HANA System checkbox if the specified remote system is SAP S/4HANA.
If it is necessary to improve performance when integrating to a remote PM system, you can create customer-specific indices on the remote PM system. The following are example indices that you can create:
- Table EQUI: Create an extension index with fields EQUNR and EQART.
- Table IFLOT: Create an extension index with fields TPLNR and EQART.
- Table ILOA: Create an extension index with fields ILOAN and SWERK.
You must access certain data directly on a local system. To make this data available on the local system, you can distribute it, for example, using an Application Link Enabling (ALE) or by replicating data from Customizing. The following is a list of the data required on the local system and the table or object where it is located:
| Data Required in Local System for Environment, Health, and Safety Processes | Table/Object |
|---|---|
| Business partner roles | Tables TB003, TB003T |
| Plants and plant descriptions | |
| Material and material description | Material number and material description from the material master |
| Currencies and exchange rates | |
| Attendance and absence types | Table T554S and T554T |
| Marital status texts for HR persons | Table T502T |
| Marital status texts for business partners | Table TB027T |
| Attendance and absence types | |
| Shift group and shift planning of the organizational unit | Info type 1039 and tables T77DB, T77DT, T77ED, T77ET |
| Organizational data, including organizational units and persons in PA-OS | Table T554S |
| Positions in PA-OS | Table HRP1000 |
Note that to make organizational data from PA-OS available in the local system, you can distribute the relevant HR master data between the PA-OS system and the Environment, Health, and Safetysystem. However, since the EHS applications only require specific PA-OS data, a distribution limited to the basic info types is sufficient. The distributed organizational data cannot be changed from the EHS applications as the system settings only allow read access.
The assignment of a user to employee (info type 0105) for workflows must be done in the HR system. The users must be maintained in the local system.
| Data Required in Local System for Product Compliance Processes | Table/Object |
|---|---|
| Business partner roles | Tables TB003, TB003T |
| Plants and plant descriptions | Table T001W |
| Material and material description | Material number and material description from the material master |
| Suppliers and contact person details | Table KNVK and tables in Business Address Services |
| Purchase Info Records | Table EINA with referenced foreign tables |
| Approved manufacturer part list | Table AMPL |
| Source list | Table EORD |
| Bill of material | Tables MAST, STAS, STKO, STPO, STZU, and TCGBA with referenced foreign tables |
