How to use DGPEX2 - Gefahrgutrechtliche Ausnahmen:

SAP Transaction Code - Details

• Transaction Code: DGPEX2

  Description: Gefahrgutrechtliche Ausnahmen:

  Release: S/4HANA and ECC 6

• • Program: SAPLDGEXC_DL01

    Screen: 1000

    Authorization Object:

  • Development Package: CBDG

    Package Description: EH&S: Dangerous Goods Management

    Parent Package: EA-EHS

  • Module/Component: EHS-DGP

    Description: Dangerous Goods Management

Smart SAP Assistant

• SAP Tcode: DGPEX2 - Gefahrgutrechtliche Ausnahmen:

  
  Overview:
  The SAP transaction code DGPEX2 is used to manage exceptions to the Dangerous Goods (DG) regulations. This code allows users to create, change, and delete exceptions to the DG regulations. It also provides a list of all existing exceptions and their details. 
  
  Functionality: 
  The DGPEX2 transaction code allows users to manage exceptions to the DG regulations. This includes creating new exceptions, changing existing ones, and deleting them. It also provides a list of all existing exceptions and their details. Additionally, it allows users to view the status of each exception and its associated documents. 
  
  Step-by-step How to Use: 
  1. Enter the DGPEX2 transaction code in the SAP system. 
  2. Select the “Create” option to create a new exception. 
  3. Enter the required information for the exception, such as the type of exception, description, and associated documents. 
  4. Select “Save” to save the exception. 
  5. To view existing exceptions, select “Display” from the menu bar. 
  6. Select an exception from the list and view its details by selecting “Display” from the menu bar. 
  7. To change an existing exception, select “Change” from the menu bar and enter the required information for the changes. 
  8. To delete an existing exception, select “Delete” from the menu bar and confirm your selection by selecting “Yes” in the confirmation window that appears. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all relevant DG regulations before using this transaction code in order to ensure that all exceptions are created in accordance with these regulations. Additionally, users should ensure that all changes made to existing exceptions are properly documented in order to maintain an accurate record of all changes made over time.