BD95 - Specify ALE object types

SAP Transaction Code - Details

• Transaction Code: BD95

  Description: Specify ALE object types

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > BAPI > Receiver Determination > Define Filter Object Type
  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > BAPI > Data Filtering > Define Filter Object Type
  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > IDoc > Data Filtering > Define Filter Object Type
  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > IDoc > Serialization > Serialization Using Time Stamps > Define Serialization Object Type
  • Logistics > Logistics Execution > Transportation > Transportation Planning > External Planning System > ALE Monitoring > Goto > ALE Development > IDoc > Relationships > Define Link Object Type
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > BAPI > Receiver Determination > Define Filter Object Type
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > BAPI > Data Filtering > Define Filter Object Type
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > IDoc > Data Filtering > Define Filter Object Type
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > IDoc > Serialization > Serialization Using Time Stamps > Define Serialization Object Type
  • Logistics > Logistics Execution > Master Data > Transportation > Shipment Costs > ALE Monitoring > Goto > ALE Development > IDoc > Relationships > Define Link Object Type
  • Tools > ALE > ALE Development > BAPI > Receiver Determination > Define Filter Object Type
  • Tools > ALE > ALE Development > BAPI > Data Filtering > Define Filter Object Type
  • Tools > ALE > ALE Development > IDoc > Data Filtering > Define Filter Object Type
  • Tools > ALE > ALE Development > IDoc > Serialization > Serialization Using Time Stamps > Define Serialization Object Type
  • Tools > ALE > ALE Development > IDoc > Relationships > Define Link Object Type
  • Tools > Business Framework > BAPI Development > ALE Development > BAPI > Receiver Determination > Define Filter Object Type
  • Tools > Business Framework > BAPI Development > ALE Development > BAPI > Data Filtering > Define Filter Object Type
  • Tools > Business Framework > BAPI Development > ALE Development > IDoc > Data Filtering > Define Filter Object Type
  • Tools > Business Framework > BAPI Development > ALE Development > IDoc > Serialization > Serialization Using Time Stamps > Define Serialization Object Type
  • Tools > Business Framework > BAPI Development > ALE Development > IDoc > Relationships > Define Link Object Type

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: SALE

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: BD95 - Specify ALE object types

  
  Overview:
  The SAP transaction code BD95 is used to specify ALE object types. ALE stands for Application Link Enabling, which is a technology used to exchange data between different systems. This transaction code is used to define the types of objects that can be exchanged between systems. 
  
  Functionality: 
  The BD95 transaction code allows users to define the types of objects that can be exchanged between systems. This includes defining the type of object, such as customer master data, material master data, or sales order data. It also allows users to define the fields that will be exchanged for each object type. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code BD95 in the command field. 
  2. Select the “Create” button to create a new ALE object type. 
  3. Enter a name and description for the object type. 
  4. Select the “Fields” tab and enter the fields that will be exchanged for this object type. 
  5. Select the “Save” button to save your changes. 
  
  Other Recommendations: 
  It is important to note that when creating an ALE object type, it must be assigned to an application system in order for it to be used in data exchange between systems. Additionally, it is important to ensure that all of the fields that are specified for an ALE object type are valid and up-to-date in order for data exchange to occur successfully.