SAP ABAP IMG Activity GGA_800_060 (Set Up Distribution of Dangerous Goods Master Data Between ERP Systems)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ EHS-DGP (Application Component) Dangerous Goods Management
     ⤷ CBDG (Package) PI-EH&S Dangerous Goods Management
IMG Activity
ID GGA_800_060 Set Up Distribution of Dangerous Goods Master Data Between ERP Systems  
Transaction Code S_SH8_84000380   IMG Activity: GGA_800_060 
Created on 20001013    
Customizing Attributes GGA_800_060   Set Up Distribution of Dangerous Goods Master Data Between ERP Systems 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GGA_800_060    

Use

In this IMG activity, you set up the distribution of dangerous goods master data. (See also Concept information under Distribution (Application Link Enabling (ALE)).)

Requirements

  1. Settings in Customizing for Application Link Enabling (ALE)
    2. You have made the necessary settings in Customizing for Application Link Enabling (ALE).
  2. Settings in the SAP component Dangerous Goods Management
    1. Specify dangerous goods master data to be distributed
      2. For manual distribution of dangerous goods master data, choose Dangerous Goods Management -> Tools -> Dangerous Goods Master Distribution -> Start Distribution.
      For automatic distribution of dangerous goods master data, you can use the distribution with change pointer evaluation function. You can schedule this to run periodically as a report.
    2. Check authorizations
      3. You require read authorization for all specification data to be distributed, both for manual and automatic distribution.
      You also require the appropriate authorizations for inbound processing in the target system.

Activities

  1. Editing the distribution model in Customizing for Application Link Enabling (ALE)

    In Customizing for Application Link Enabling (ALE), call the IMG activity Maintain Distribution Model and Distribute Views.

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

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

Field     Entry

Sender/Client:     <source system key>

Receiver/Server:    <target system key>

Object name/Interface:    DangerousGood

Method:     SAVREPLICA (distribute to the target systems and

    update on the target systems)

Note:

The message type DANGEROUSGOOD is supported.

Then in Customizing for Application Link Enabling (ALE), edit the IMG activity Generate Partner Profiles.

  1. Editing settings in the sending and receiving systems

    The following objects must already be available on the target system in their required form:

    • Entries in Customizing tables
    • Materials of the logical key
    • Change numbers
    • Phrases
  2. Checking control data to be distributed

    See above "Editing settings in the sending and receiving systems."

  3. Checking consistency

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

    To use it, call the IMG activity Check Technical Consistency in Customizing for Application Link Enabling (ALE).

    The prerequisite is that the distribution model was distributed and the partner profiles edited in all relevant systems.

  4. Handling errors

    You can use the EH&S environment parameter DG_DISTRIBUTION_SAVE to determine whether an attempt should be made to update the IDoc in every case or whether the IDoc should not be updated in the case of an error.

    If errors occur when updating, you can check in the import log of the target system which errors occurred.

General Procedure

  1. Initial distribution

    Start the initial distribution without using change pointer evaluation.

    To do this, choose Dangerous goods master -> Send from the initial Dangerous Goods Management screen and do NOT set the Change pointer evaluation indicator.

    You can use the EH&S environment parameter DG_DISTRIBUTION_PACK to specify how many dangerous goods master objects are to be distributed in one IDoc.

  2. Switching on delta distribution
    1. Activating change pointers for a message type
      2. 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 Application Link Enabling (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.
    2. Activating change pointers for each field
      3. From the SAP Easy Access screen, 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.
    3. Activating change pointers generally
      4. To generally activate master data distribution using change pointers, in Customizing for Application Link Enabling (ALE) choose the IMG activity Activate Change Pointers - Generally and set the Active indicator.
    4. Scheduling delta distribution as a job
      5. You can perform delta distribution manually or schedule it as a job.
      To perform delta distribution manually, from the SAP Easy Access screen 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 Application Link Enabling (ALE) in the section Create IDocs from Change Pointers, choose 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 to the data transfer:

  • If a dangerous goods master record is not found in the target system, it is created and given the key that was transferred.
  • If a dangerous goods master record is found in the target system, its data is updated.
  • While dangerous goods master data is being sent, the dangerous goods master record is locked against changes. If this lock cannot be set, the dangerous goods master record cannot be processed. The IDoc switches to error status and a work item is created.
  • Updating can be speeded up if the verification of phrases is switched off. Use the environment parameter DG_SUPPRESS_PHR_CHECK to do this.

Note:

  • In manual distribution change pointers are not taken into account, meaning delta distribution does not take place, but all selected dangerous goods master records are distributed.
  • If the selection date is later than the date of a change number in the source object, the target system executes a data record split on the selection date when the dangerous goods master data with change numbers is distributed. This means the change number with change date is not taken into account in the target system because in the period before the selection date, the data record was not changed in the target system.
  • In the IMG activities Specify Checkbox Structure for Dangerous Goods Master and Specify Checkbox Structure for DG Packing Requirement you specify which fields of the dangerous goods master or the dangerous goods packing requirements are relevant for distribution and update.

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