Execution of Check Methods 
Use
This function executes the dangerous goods check methods after the dangerous goods checks have been started and the system has determined the relevant data.
Check methods are executed in the same way in sales documents, shipping documents, and shipment documents.
Prerequisites
See:
· Dangerous Goods Checks in Sales Documents
· Dangerous Goods Checks in Shipping Documents
· Dangerous Goods Checks in Shipment Documents
Features
If no errors occur when determining data, the check methods in the check schema are executed. This means that every material is checked with every check method in the check schema. „Checking“ means that the material data is checked against data from the dangerous goods master record.
The check method (or in other words the function module HAZMAT_CHK_VARIOUS with sequence 1) for the completeness check must be entered in each check schema. If you want to change this function module, the function module you change must be entered with sequence 1.
The system performs the following program steps:
...
1. The system uses material number, mode-of-transport category, and country (or validity area for check methods with usage profile) to select the dangerous goods master record to be checked. If the system determines several dangerous goods master records with different validity areas for one combination of material and mode-of-transport category, it selects the dangerous goods master record with the smallest validity area. (Nonoverlap or distinction principle.)
The term dangerous goods regulation is used in the dangerous goods master. It is defined by the mode-of-transport category and validity area in Customizing for Dangerous Goods Management.
2. The function module for the check method is called.
3. If the function module returns a corresponding parameter (return code), the system executes the response that is set for this check method in Customizing. For example, the message set in Customizing is written to the check log.
Each check method can generate further log entries in addition to the message set in Customizing. For more information, see the documentation for function modules in the function group DG63.
4. The system uses the responses for the individual check methods to determine an overall response for the check schema. This overall response determines how the document is to be processed further.
The strictest response is used as the overall response according to the hierarchy A (terminate if check result is negative) > E (error) > W(warning) > I (information) / X (terminate if check result is negative, the system executes no further check methods from the check schema for this material). For example, if several check methods reacted with the response type E, the strictest response setting is Save not allowed. You should not have set the SaOnli (save online) or SaCoPr (save in collective processing) indicators.
The dangerous goods check schemas are executed for each expected delivery within the dangerous goods checks in the sales document. The overall response for the document results from the strictest response of the individual expected deliveries. In the sales document, an Aresponse causes the system to terminate the execution of the check schema for the current expected delivery and to start determination of the next expected delivery. For more information, see Determination of Expected Deliveries.
The document specifies that the shipment is to be sent using the mode-of-transport category Road through the country Germany. For the check method Permissibility of mode-of-transport category, the relevant dangerous goods master record is read for the material currently being checked. The relevant master record is the one with the mode-of-transport category Road and a validity area containing Germany (see also Checking of Validity Areas).
If the Transp not permitted (transport not permitted) field is not set for this dangerous goods master record, the message set in Customizing is written to the check log and the next check method is executed.