Hi Deep
we are also working on MDM integration with BOBJ-DS, developing PoVs.
To start with I can share following findings on BOBJ capabilities, still unconfirmed though and may not be 100% correct.
1. BOBJ as ETL- We already have MDM along with PI/SAP-XI used as ETL, which is capable of most of the functions offered by BOBJ. BOBJ stands out more on doing complex transformations an dexception/error handling part.
2. BOBJ for DQ- MDM also offers DQ facilities, though not as extensive as by BOBJ. MDM along with Webdynpro can match most of the DQ features offered by BOBJ. BOBJ stands out wherein we have Address data cleansing as it is having out of box address directories in built for 240+ countries. It makes sense to use BOBJ-DS for DQ only if the (Customer, Vendor) Address data cleansing is of paramount importance. Fe- Postal code Validation.
3. BOBJ for reporting and data KPIs- We can deliver equivalent reports/KPIs with MDM and BI integration with customizations. Still a grey area for me, explring more for now.
BOBJ and MDM are complementary to each other as they enhance otheru2019s capabilities. But it is not mandatory and may not make sense to fit in BOBJ in all scenarios.
On implementation instaed of using slave repository and DB view for BOBJ-DS to connect to MDM we are using duplicate repository in productive environment to expedite the work.
I found a very good demo session on BOBJ capabilities for SAP based systems (CRM, ERP)-
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/c0634fdc-cbc6-2c10-1885-a93c2adfff0d&overrid...
Would definitely like to learn more from you and this thread.
Thanks-Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.