SAP ABAP IMG Activity EHS_MD_120_40_02 (Set Up Distribution of Specification Data)
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_120_40_02 Set Up Distribution of Specification Data  
Transaction Code S_SH8_72000985   IMG Activity: EHS_MD_120_40_02 
Created on 20001013    
Customizing Attributes EHS_MD_120_40_02   Set Up Distribution of Specification Data 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_MD_120_40_02    

Use

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

Caution:

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

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 made the required settings in Customizing for ALE.

  2. Settings in the SAP Basic Data and Tools Component

    Make sure that you have fulfilled the following prerequisites:

    1. Edit the environment variables for serialization
      2. Serialization collects the IDocs and makes sure that they are processed in the correct order. For more information, see the section Serialization for Sending and Receiving Data in the Implementation Guide (IMG) for ALE.
      You specify the serialization number for the logical sending system in the IMG activity Specify Environment Parameters in the environment parameter ALE_SERIAL_ID. You specify one unique channel per logical system.
    2. Specify specifications to be distributed
      3. If you want to distribute specification data manually, choose the specification directly from the hit list in specification management.
      For automatic distribution, the specifications must appear in a set of hits that is assigned to the distribution method. If a set of hits has not been assigned, all of the specifications are distributed, providing that you have not defined filters.
      Apart from standard filters (see below), you can use the following customer exits to define other restrictions and filters:
      - Specify Additional Table and Parameter Filter (1)
      - Specify Additional Table and Parameter Filter (2)
    3. Ensure unique identification of specifications
      4. The specification object must have a unique specification key. In the standard system, identification is supported by the specification key.
      You can use the customer exit Develop Enhancement for Identification to enhance the identification, for example, to link with one or more identifiers.
    4. Check authorizations
      5. For manual distribution and automatic scheduling, you must have read authorization for all the specification data to be distributed.
      You also need the appropriate authorizations for inbound processing in the target system.

Activities

  1. Specify 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 Add 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:    Substance (substance(specification), BUS1077)

Method:     SavRepMul (save replicated specifications)

Note:

The message type SUBMAS is supported.

You can set the following filters:

  • Reducing specifications by determining recipients:
    • You can reduce the specifications to be distributed by defining the following filters:
    - Specification type
    - Authorization group
    - Substance nature
    - Set of hits (external key of group object)
    You can enter several values for a filter field. Individual values are linked with OR, whereas the filter groups are linked with AND.
    If no filters are entered, all specifications are distributed.
  • Reducing specifications using IDENTHEADER filtering
    • You define the identification category and identification type whose specifications are to be distributed.
  • Reducing data using PROPHEADER filtering
    • You specify the value assignment types for which specification data is to be distributed.
  • In Customizing for ALE, you can use the IMG activity Filter IDoc Segments to exclude further tables from distribution, for example:
    • - Material assignment
    - Regulatory list assignment
    - Reference specification assignment
    - Usage
    - Assessment

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

  1. Make Settings in the Sending and Receiving Systems

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

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_120_40_02 0 ALR0000065 Tools 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010320 
SAP Release Created in