Connections to other systems

Question

Hi,
    I came to know that BD97 is also used to check the connections from R/3 to APO or other systems.
Does anyone know what's the advantage of using BD97 compared to SM59 and how do we check the connections in BD97?
Thanks

Answer 1

HI
GOOD
SAP WMS - Decentralized Warehouse Management System Integration Setup
You can operate the SAP Warehouse Management System (WMS) as a stand-alone decentralized system that is independent of a central Enterprise Resource Planning (ERP) System.
You make the necessary settings for the ERP (Enterprise Resource Planning) system within the WMS component (Warehouse Management System).
The steps are set up as a checklist and guide you through the process of configuring the system parameters. 
Checklist (For those with the Table Views used transaction code SM30).
1. Customizing for "Enterprise Structure"
- Create storage location in OX09 (if necessary).
- Define warehouse number in Views V_T3001.
  (you should not copy the warehouse number in the ERP system) 
  Activities within a warehouse, like goods movements and physical inventory, are assigned to a  specific 
  warehouse number. 
  The physical warehouse where these activities take place is identified by the warehouse number.
- Assign plant/storage location to warehouse number in Views V_T320.
  (Valid if the component MM-IM (Inventory Management) is implemented.)
  Fields : Plant + Sloc + WhN
2. Customizing for "Decentralized WMS integration", section "Central processing" -> Application 
- Activate decentralized WMS in Views V_T340DM.
- Define interface to Inventory Management in Views :-
  V_156S_WM - Assign WM movement type references to IM movement types
  V_T3211   - Delivery-Relevant Parameters for Reference Movement Type
  V_T340DL  - Delivery-Relevant Data for Warehouse Number
- Exclude stock in decentralized WMS in Views V_T321B
  (if the decentralized WMS is not an SAP R/3 system) 
- Finally do a consistency check for decentralised WMS in transaction OL20.
3. Customizing for "Application Link Enabling (ALE)", section "Basis Components"
   Maintaining Logical Systems in Views V_TBDLS.
   Assign logical system to client in Views T000.
4. Make basic settings for RFC in transaction BD97.(if necessary)
5. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model"
You can define the Reduce message types and Activate message types in transaction BD53.
SAP recommends that you use message types :
"MATMAS" (material master tables) and 
"DEBMAS" (customer master) as a template.
Be aware that only those fields that are absolutely necessary are transferred from the master data tables in 
the ERP system to the decentralized WMS. 
6. Customizing for "Decentralized WMS integration", section "Central processing" -> Distribution
Use transaction OL19 to generate distribution model. As far as the application is concerned, when the model 
is generated, application-specific Customizing parameters are modified or set (for example, activate 
decentralized WMS). 
Display or check distribution model 
Generate partner profile in transaction BD82. 
(you can also perform this activity using ALE Customizing) 
Distribute distribution model in transaction BD64 (model view) using menu item "Edit"
If both the ERP system and the decentralized WMS are SAP R/3 systems, the distribution model should be 
distributed on a central basis only, that is, via the ERP system. 
7. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model" (transaction BD64)
Activate the change pointers for master data distribution using transactin BD61. 
If necessary, reduce the message types concerned with transaction BD53.
8. Customizing for 
"Logistics - General" - "Material Master" - "Tools" - "Data Transfer : Material Master" - 
-> "Define required-field check for ALE/Direct Input" (Views V_T130S)
Define whether an error message should be generated in the receiving system for required fields
from the material master.
thanks
mrutyun