SAP ABAP IMG Activity GGA_300_180 (Specify Dangerous Goods Check Schemas)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ CBIMG1 (Package) EH&S: IMG Migration
IMG Activity
ID GGA_300_180 Specify Dangerous Goods Check Schemas  
Transaction Code S_SH8_84000310   IMG Activity: GGA_300_180 
Created on 19990127    
Customizing Attributes GGA_300_180   Specify Dangerous Goods Check Schemas 
Customizing Activity GGA_300_180   Specify Dangerous Goods Check Schemas 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GGA_300_180    

Use

In this IMG activity, you combine dangerous goods check methods into one dangerous goods check schema and set up a reaction for each check schema and check method that influences how the SD document is processed further.

Requirements

The dangerous goods incompleteness status must have been created in status management for SD documents (see chapter: Incompleteness Control for SD Documents).

New messages must be created using the ABAP Workbench.

Standard settings

Sample settings are delivered.

Activities

  1. Call the IMG activity.
  2. Create a new check schema and record descriptions in the required languages.
  3. Select the required dangerous goods check schema.
  4. Choose Assignment check schema/check methods in the navigation.
  5. Assign a sequence number for the dangerous goods check method.

    Note:

    You MUST have entered the check method with the function module HAZMAT_CHK_VARIOUS in each check schema as check method with sequence 1, or if you want to change this module, you must have entered your own module for the completeness check.

    The check methods are processed in the sequence specified.

    The initialization module DG63_CHK_INIT_HEADER must come before the first header check method (for example, mixed loading checks).

  6. Assign a reaction type to the respective check method.

    You can enter the following reaction types:

Value    Meaning

I    Information
W    Warning
E    Error
A    Termination due to negative check results
X    Termination due to positive check results

When processing the dangerous goods check methods, an overall reaction for the dangerous goods check schema is determined from the reactions of the check methods that have 'reacted'. For this, A > E > W > I/X. The strictest reaction type determines the overall reaction for the check schema. If several check methods react with the same reaction type, the save setting decides which method determines the overall reaction. Reaction type A leads to a termination of the dangerous goods check schema. Dangerous goods check methods present in the dangerous goods check schema are not processed any further. The system exits the dangerous goods check. Reaction type X leads to a termination of the dangerous goods check schema for the current material. The system proceeds to the next SD document item.

For dangerous goods checks in sales, a complete reaction is determined for each expected delivery and the complete reaction for the document results from the strictest reaction of the individual expected deliveries.

  1. Assign a message class and message number to the respective dangerous goods check method.

    The message set up is displayed in the dialog box for the dangerous goods check and written to the check log. For the check method you entered in the schema with sequence 1, you need not make these entries if you use the standard SAP module HAZMAT_CHK_VARIOUS. This sets both entries. If you replace this module with one of your own, you must assign it a message class and number.

  2. If the SD document is to be blocked (shipment document) or the incompleteness status is to be set (sales and shipping document), set DocBlk (document block).
  3. If the SD documents are to be saved after the dangerous goods check is finished, set either SaCoPr or SaOnli.

    The SaCoPr indicator has no relevance for dangerous goods checks in sales as documents cannot be created using collective processing in sales.

    In the shipping document, the SaOnli indicator controls the structure of the dialog box used to display the message set up here in the SD document. If the indicator is set, a selection of functions to save the document is also displayed in the dialog box. As the indicator is set according to the dangerous goods check method and reaction, you can specify if the person processing the document is to be permitted to save it in the case of reactions of type "E = Error", for example. The person processing the document can then decide whether to save the document or not.

    You use the SaCoPr indicator to specify if the document can be saved in collective processing. In the shipment document, the setting 'do not save' (the SaCoPr and/or SiOnli fields are not set) cannot be processed for technical reasons. This setting is automatically changed to 'save with document block' (SaOnli and DocBlk indicators).

    You use the DocBlk indicator in the sales and shipping document to set the previously set incompleteness status that prevents subsequent functions. If the incompleteness status is set in the sales document, the system prevents a shipping document being created with a reference to this job.

In the shipment document, a block indicator is set in the shipment header. The block indicator or incompleteness status is removed if a new check has positive results. Sales and shipping documents are not saved if you only set the DocBlk indicator and do not set the SaCoPr and SiOnli indicators.

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_300_180 0 HLA0100684 Dangerous Goods Checks 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VCDG_TDGB1 C - View cluster SM34 GG_01 Definition of check schema and check routine assignment 
History
Last changed by/on SAP  20020314 
SAP Release Created in 46C