Hierarchy
BBPCRM (Software Component) BBPCRM⤷
EHS-DGP (Application Component) Dangerous Goods Management⤷
CBDG (Package) PI-EH&S Dangerous Goods Management
IMG Activity
| ID | GGA_200_204 | Assign DG Check Schemas for Sales Documents |
| Transaction Code | S_SH8_84000341 | IMG Activity: GGA_200_204 |
| Created on | 20001013 | |
| Customizing Attributes | GGA_200_204 | Assign DG Check Schemas for Sales Documents |
| Customizing Activity | GGA_200_204 | Assign DG Check Schemas for Sales Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | GGA_200_204 |
Use
In this IMG activity, you specify in which context dangerous goods check schemas are used in sales documents.
You use the following criteria:
- Sales organization
- Sales document category
You can only enter sales document categories that are supported for dangerous goods management (see the possible entries help (F4) for sales document categories).
- Sales document type
The dangerous goods check schema determination routine defined in one of the previous IMG activities checks the table entered in this IMG activity and processes the dangerous goods check schema it finds.
Standard settings
Default settings are shipped.
Activities
- Call the IMG activity.
- Choose Edit -> New Entries.
- Enter the sales organization, sales document category, and sales document type and assign a dangerous goods check schema to this context.
Further notes
The check schemas are determined according to the following logic:
The first step reads:
- Sales organization/sales document category/sales document type
If this fails, it reads: - Sales organization/sales document category
Then it reads: - Sales document category/sales document type
Then it reads: - Sales document category only
If no check schema is found, it reads without: - Sales organization/sales document category/sales document type
If is still finds no check schema, a message is displayed and the dangerous goods checks are not processed.
Using this processing logic, it is possible, for example, that the same check schema is always assigned to a sales document category, independent of the sales organization and sales document type.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired 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_200_204 | 0 | HLA0100684 A HLA0009601 |
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 |
| DGV_TDGB9 | V - View | SM30 | GGA_01 | Assign DG Check Schemata for Sales Documents |
History
| Last changed by/on | SAP | 20020314 |
| SAP Release Created in |
