MDM 7.1 Transport Management using CTS+

[Former Member]

CE: 7.2

MDM: 7.1

PI: 7.1 EHP1

ERP: 6 EHP4

Hi,

For central master data management, we are building a solution based on the components mentioned above. Our current landscape for ERP has 10 systems due to the requirements of the project. This includes SBX -> DEV -> QAS -> INT -> UAT -> PRE-PROD for project. Then we have SBX -> DEV -> QAS -> PROD for business as usual. The idea is that we the first phase goes live, BaU will be used to support the live environment while project environments can continue to be used for new functionality development in various phases over several years.

We plan to use CTS+ to manage the transports in the landscape. However, the question is whether we need 10 MDM system to match ERP, or could we use less systems without impacting the overall quality and effort of delivery?

Also keep in view that CE will be used to run the custom BPM workflows. Moreover, we'll deploy MDM web services on CE server to be consumed by Web Dynpro JAVA UI components. All in all, the overall solution will span several development components across ERP (custom enterprise services), PI (custom integration content), CE (custom WD JAVA UI, MDM web services, workflow), and MDM (tables, fields, relationships, roles, XML schemas, etc).

Given that MDM repositories are self-contained, and we can create more than one repositories on QAS e.g. for INT and UAT, I am trying to identify any potential pitfalls/technical implications of using less MDM environments for more ERP systems.

Lets say we had 3 repos on QAS MDM server: REP_Q, REP_I, and REP_U. If we wanted to test certain functionality in REP_I, we could transport it from REP_Q to REP_I hosted in the same MDM system. Similarly, these changes could be propagated to REP_U environment for further testing.

So the user can initiate a process on CE server which could call web services to create data in REP_I. Once successful, changes can be transported to REP_U and the user can use CE to call web services for REP_U for data management.

Do you have a similar landscape? Have you tried using less MDM systems to host multiple repositories without overcomplicating change management? Thoughts???

Thanks for your time.

Regards,

Shehryar

[Former Member · Accepted solution]

Hello Shehryar Khan

We are using 3 level environment DEV-QA-PROD.The same situation with ERP for ABAP development.

DEV and QA working on different physical servers but in the same LDAP.

PROD - has own physical server and own LDAP.

For migrated data tests we duplicate repository from PROD to DEV and named it - MIGRATED.

Business logic we are realize on DEV. If business logic and migrated data tests(on MIGRATED repo) have been finished succesfully We migrate data from MIGRATED repo to DEV and doing complex tests(business logic + new data).

The same steps we are doing on QA and then on PROD.

Regards

Kanstantsin Chernichenka