BD99 - Message type dependencies

SAP Transaction Code - Details

• Transaction Code: BD99

  Description: Message type dependencies

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > IDoc > Data Filtering > Dependencies > Define Dependencies Between Message Types
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > IDoc > Data Filtering > Dependencies > Define Dependencies Between Message Types
  • Tools > ALE > ALE Development > IDoc > Data Filtering > Dependencies > Define Dependencies Between Message Types
  • Tools > Business Framework > BAPI Development > ALE Development > IDoc > Data Filtering > Dependencies > Define Dependencies Between Message Types

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: SALE

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: BD99 - Message type dependencies

  
  Overview:
  The SAP transaction code BD99 is used to maintain message type dependencies. This transaction code is used to define the relationship between different message types in the SAP system. It allows users to define which message types are dependent on each other and how they should be processed. 
  
  Functionality: 
  The BD99 transaction code allows users to define the dependencies between different message types in the SAP system. This includes defining which message types are dependent on each other and how they should be processed. It also allows users to view and edit existing dependencies between message types. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code BD99 in the command field. 
  2. Select the “Dependencies” tab. 
  3. Select the “Create” button to create a new dependency between two message types. 
  4. Enter the source and target message type in the respective fields. 
  5. Select the “Save” button to save the new dependency. 
  6. Select the “Display” button to view existing dependencies between message types. 
  7. Select the “Change” button to edit an existing dependency between two message types. 
  8. Enter the changes and select the “Save” button to save them. 
  
  Other Recommendations: 
  It is important to note that when creating or editing a dependency between two message types, it is important to ensure that all of the necessary information is entered correctly in order for it to be saved successfully. Additionally, it is recommended that users familiarize themselves with all of the available options in order to make sure that they are using the correct settings for their particular situation.