SAP ABAP IMG Activity EHS_MD_160_40_01 (Set Up Distribution of Accident Data)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-IHS (Application Component) Industrial Hygiene and Safety
     ⤷ CBIH (Package) EH&S: Industrial Hygiene and Safety
IMG Activity
ID EHS_MD_160_40_01 Set Up Distribution of Accident Data  
Transaction Code S_XD9_88000056   (empty) 
Created on 20060608    
Customizing Attributes EHS_MD_160_40_01   Set Up Distribution of Accident Data 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_MD_160_40_01    

Use

In this IMG activity, you set the distribution of data for the incident/accident log (see also Concept Information under EH&S Application Link Enabling (ALE)).

Caution:

Initial distribution is not supported when using change numbers (versioning). In this case, start with the delta distribution.

Requirements

  1. Customizing settings for Application Link Enabling (ALE)

    You have made the required settings in Customizing for ALE.

  2. Settings in the SAP component Basic Data and Tools

    Make sure that the following prerequisites are filled:

    1. Edit environment variable for serialization
      2. The serialization collects the IDocs and makes sure that these are processed in the correct order. For more information, see the Implementation Guide (IMG) for ALE in the section Serialization for Sending and Receiving Data.
      You specify the serialization number of the logical sending system in the IMG activity Specify Environment Parameters in the environment parameter ALE_SERIAL_ID. In this way, you specify a unique channel for each logical system.
    2. Specify incident/accident log entries to be distributed
      3. For manual distribution of incident/accident log entries, you select the incident/accident log entries directly in the hit list of the Incident/Accident Management.
      Besides the standard filters (see below), you can use the BAdI: Handling of Enhancements in Incident/Accident Log BAPIs to define additional enhancements and filters.
    3. Check authorizations
      4. For the manual distribution and the automatic scheduling, you must have read authorization for all accident data to be distributed.
      You also require the relevant authorizations for the inbound processing in the target system.
    4. For the ALE distribution, it is important that the number ranges for the objects CBIHN_IAID and CBIHN_PRID are compatible in the source and target systems. The external number range interval of the target system must contain the key to be transferred from the source system.
      The number ranges and intervals can be set using the transaction SNUM.

Activities

  1. Specify distribution model in ALE Customizing

    In ALE Customizing, call the IMG activity Maintain Distribution Model and Distribute Views.

    For more information, see the documentation for the IMG activity.

    To guarantee communication between the systems during distribution, you must make the following entries in the IMG activity Maintain Distribution Model and Distribute Views using Add BAPI:

Field    Entry

Sender/Client:    <Key of EH&S system>

Recipient/Server:    <Key of target system>, for

    example, SD system in which

    EH&S is installed.

Object Name/Interface:    Incident (EHS: Incident/Accident Log)

Method:    SaveReplicaMultiple (EHS: Saving replicated incident/accident log entries)

Note:
The message type INCIDENT is supported.

You can set different filters.

In ALE Customizing, you can use the IMG activity Filter IDoc Segments to exclude other tables from the distribution.

Then perform the IMG activity Generate Partner Profiles in ALE Customizing.

  1. Make settings in the sending system and the receiving system

    Customizing of the incident/accident log must be compatible in the sending system and the receiving system. In particular, the settings in the activities of EH&S -> Basic Data and Tools must also be compatible.

  2. Check master data to be distributed

    Within this ALE process, the following master data must be distributed to all involved systems or created in the systems with the same logical keys if they are to be used in the incident/accident log.

    • Restrictions in Occupational Health if there are multiple restrictions (see notes)
    • Phrases
    • Phrase sets
    • Classes and characteristics
    • Persons (HR persons and business partners)
    • HR absences
    • Work areas
    • Functional locations and equipment
    • DMS documents
    • Maintenance measures or service tasks

      Notes:

    • Classes and characteristics are distributed via export and import. You use classes and characteristics to forward the help texts and phrase sets to other systems.
      Classes and characteristics can also be distributed via ALE.
    • When using multiple absences/restrictions, the restrictions must exist in the target system (created via Occupational Health or an accident). The assignment to the accident is then distributed.
  3. Check tax data to be distributed

    See above: Make settings in the sending system and the receiving system

  4. Check consistency

    A consistency check can be performed for the settings in the distribution model and partner profiles.

    To do this, you call the IMG activity Check Technical Consistency in ALE Customizing.

    A prerequisite for this is that the distribution model is distributed and the partner profiles are entered in all relevant systems.

  5. Handle errors

    As soon as an error occurs when processing an IDoc, the entire IDoc is not updated. You can include a workflow for resolving errors. IDocs can be modified manually and then updated retroactively.

General Procedure

  1. In a customer reference model, you define what data is distributed to what systems. Using sets of hits, you define the incident/accident log entries that are to be distributed and specify filters for accidents or accident data as required.
  2. You distribute the incident/accident log entries the first time manually using the REPLICATE method (for example, from the hit list of the transaction CBIH82) from the distribution model to the target systems. Serialization must be deactivated.
  3. You activate serialization and activate the delta distribution as follows:

    Activating Serialization

    1. In Customizing for Basic Data and Tools, in the IMG activity Specify Environment Parameters specify the channel for the parameter ALE_SERIAL_ID through which the Application Link Enabling (ALE) data is to be distributed.
    2. In Customizing for ALE in the section Serialization Using Business Objects in the IMG activity Activate Inbound Business Objects, specify the inbound object types for which serialization is to be performed.
    3. Schedule a job (RBDAPP01) that posts the IDocs that arrive in series in the recipient system.

      Switching On Delta Distribution

    4. Activating change pointers for a message type
      5. Changes to master data objects are logged in the form of change pointers during master data distribution. To activate the writing of change pointers, in Customizing for ALE in the IMG activity Activate Change Pointers for Message Types, set the Active indicator for the message type for which you want to use delta distribution.
    5. Activating change pointers for each field
      6. In the SAP menu, choose Tools -> ALE -> ALE Development -> IDoc -> Engineering Change Management -> Define Change-Relevant Fields and enter the message type for which you want to determine fields, for which the SAP system writes change pointers. All relevant data fields are delivered. If necessary, adjust the table to your requirements.
    6. Activating change pointers generally
      7. To generally activate master data distribution using change pointers, in Customizing for ALE choose the IMG activity Activate Change Pointers - Generally and set the Active indicator.
    7. Scheduling delta distribution as a job
      8. You can perform delta distribution manually or schedule it as a job.
      To perform delta distribution manually, in the SAP menu choose Tools -> ALE -> ALE Administration -> Services -> Change Pointers -> Evaluate, enter the message type you require, and choose Execute.
      To schedule delta distribution as a job, in Customizing for ALE in the section Create IDocs from Change Pointers in the IMG activity Define Variants and create a variant. Then in the IMG activity Schedule Jobs create a job (RBDMIDOC) for the variant. You can set the time at which distribution is performed, for example, immediately after a change or periodically.

The following applies for transferring the data:

  • If an incident/accident log entry is not found in the target system, it is created with the transferred incident/accident log key.
  • If an incident/accident log entry exists in the target system, its data is updated.




Note on Executing the Report Program RC1PHDEL:

You must NOT schedule the report program RC1PHDEL (physical deletion of data&#x

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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_MD_160_40_01 0 ALR0000065 Tools 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20060810 
SAP Release Created in 600