SAP ABAP IMG Activity EHS_MD_150_40_01 (Set Up Distribution of EH&S Reports)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBUI (Package) Company Environment Information System
IMG Activity
ID EHS_MD_150_40_01 Set Up Distribution of EH&S Reports  
Transaction Code S_SH8_72000983   IMG Activity: EHS_MD_150_40_01 
Created on 20001013    
Customizing Attributes EHS_MD_150_40_01   Set Up Distribution of EH&S Reports 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_MD_150_40_01    

Use

In this IMG activity, you set up distribution of EH&S reports (see also Information About the Concept under EH&S Application Link Enabling (ALE)).

Requirements

  1. Setting the Active Code Page

    To transfer the data using ALE, you must ensure that the active code pages are the same in the receiving system and sending system as follows:

    • You must select a code page for transfer (for example, SAP(ISO) code page 1100) that you set up on all SAP systems that belong to your ALE distribution model.
    • In Customizing for Basic Data and Tools in the IMG activity Specify Environment Parameters in the environment parameter ALE_TRANSFER_LANGUAGE, you must specify a language of the previously selected code page as the transfer language in the sending system. This language controls which code page is active in the sending system during data transfer.
    • The RFC destinations of the target systems must be defined with the logon language that corresponds to the specified code page.
    • If data is to be transferred to different SAP(ISO) code pages, the operating systems of the sending and receiving systems must use the same character sets (ASCII or EBCDIC):

Sending system        Receiving system        Transfer possible

AS400        AS400        Yes

UNIX        UNIX        Yes

NT        NT        Yes

NT        UNIX        Yes

UNIX        NT        Yes

AS400        NT        No

AS400        UNIX        No

NT        AS400        No

UNIX        AS400        No

For more information, see:

  • The IMG activity Specify Environment Parameters
  • The IMG activity Set Up EH&S Native Language Support
  • The section EH&S Native Language Support in the Basic Data and Tools documentation

  1. Settings in Customizing for Application Link Enabling (ALE)

    You have configured the required settings in Customizing for ALE.

  2. Settings in the SAP Basic Data and Tools Component

    Ensure that the following prerequisites are met:

    1. Ensure EH&S reports have unique identification
      2. A unique report key is a prerequisite for distributing EH&S reports. This EH&S report key is made up of the following attributes:
      - Specification ID
      - Report generation variant
      - Report language
      - Document type
      - Internal version
    2. Check authorizations
      3. To distribute EH&S reports, you need read authorization for all reports to be distributed.
      To edit entries in the target system, you need authorization to create and change EH&S reports.

Activities

  1. Edit the Distribution Model in Customizing for ALE

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

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

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

Field     Entry

Sender/client:     <Key for EH&S system>

Receiver/server:    <Key for target system>, for example,

    sales and distribution system (SD), on which

    EH&S is installed.

Object name/interface:    SubstanceReport, Bus 1092

Method:     SAVREPMULT (distribute to target systems and

    post to target systems)

    REPLICATE (request reports to be distributed)

Note:

The message type REPMAS is supported.
The basis IDoc type is REPMAS01. If you want to distribute extended safety data sheets (eSDSs), use basis IDoc type REPMAS02.

You can reduce the reports to be distributed using recipient determination. The following filters are available by default:

  • EH&S report header
    • - Report generation variant
    - Report language
    - Report category
  • Specification header
    • - Object type
    - Object authorization group
    - Specification listing
    Note:
    Entering filter criteria can be very time-consuming because many entries may need to be made, depending on how detailed the filter is. For this reason, filters such as report distribution list and document number do not appear in the input help.

    Then edit the IMG activity Generate Partner Profiles in Customizing for ALE.

  1. Configure Settings in the Sending and Receiving Systems

    The following objects must be identical in the sending and receiving systems:

    • Report generation variants
    • Specifications
    • Report categories
  2. Check Control Data to Be Distributed

    See above: Configure Settings in the Sending and Receiving Systems

  3. Check Consistency

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

    To run the consistency check, call the IMG activity Check Technical Consistency in Customizing for ALE.

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

  4. Error Handling

    If an error occurs when an IDoc is being processed, the whole IDoc is not posted. You can include a workflow to correct errors. IDocs can be modified manually (you can change the identifier, for example) and subsequently posted.

General Procedure

  1. You define which EH&S reports are to be distributed in a customer reference model.
  2. When you first distribute reports, you distribute them manually to the target systems using the REPLICATE method based on the distribution model.
  3. You activate serialization and switch on 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 when data is transferred:

  • If a report is not found in the target system, it is created using the report key that was transferred.
  • If a report exists in the target sys
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_150_40_01 0 ALR0000065 Tools 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010320 
SAP Release Created in