In this mode, Activation of the data moved the data into internal MDG Active database tables (separate from ERP data dictionary tables). This interface is depicted in the chart below.
#Sap architecture pdf code
Integration with SAP Solutions Manager ChaRM system was considered in support of management of configuration objects such as company code information. Please note, however, that this portion of implementation was not finalized while I was involved with this project. Initial discussion with customer finance business team and their BPC implementation partner favored interfacing SAP MDG directly with BPC in a unidirectional mode – i.e., master data would originate in SAP MDG and be transferred via file transfer interface to BPC. However, in version 7.5 that this customer was implementing, BPC was able to maintain its own master data objects and had capability to support file transfer of master data from external systems directly into BPC. In earlier versions, BPC gott its master data (e.g., cost center and profit center hierarchies) from SAP BW structures. In previous version of BPC, SAP recommended to interface this system with SAP BW. The one exception was the new BPC (SAP BusinessObjects Planning and Consolidation 7.5, version for SAP NetWeaver). This customer had considerable experience using and managing CIF interfaces. Based on my experience, this is the most stable out-of-the-box way to interface these systems. These systems were to be interfaced with SAP ECC using the core-interface (CIF) technology delivered by SAP for each system. As depicted in the Hub chart above, these systems included SRM, BW, and APO. I recommended interfacing other SAP auxiliary systems directly with the SAP ECC central instance. This customer’s Basis support analysts had considerable experience implementing and supporting ALE interfaces. ALE is a proven technology when it comes to interfacing SAP systems. I recommended leveraging ALE interface technology for all interfaces between SAP MDG and other SAP systems including the legacy SAP ECC central master data system. This customer agreed with my recommendation implementing MDG in Hub architecture for the benefits presented above. Additional effort and complexity of maintaining synchronized configuration (IMG) environments between SAP ERP/ECC and MDG/ECC instances.
0 kommentar(er)
