SRM MDM Catalog ---- SRM

[Former Member]

Hi,

Is there a middleware (Pi) required to connect "SRM MDM" with "SRM" ?

Can anyone explain the integration between these two.

Points will be given

Thanks!

[Former Member]

in a standard SRM-MDM scenario ,

you would need the PI ONLY if theres a auto distribute/update of contracts from SRM to MDM.

thanks

-Adrivit

[Former Member]

Hi,

PI is only required in case you want to replicate Suppliers/Contracts/Product from SRM to MDM. If it in not your case, PI is not required. You can initialize the repository with data like UOM, Currencies and Product Groups through (T-code MDMGX) FTP or manual import through Import Manager.

Thanks,

Anshuk Saxena

[rajesh_chavan]

Well it depends on what scenario you are building. and HOw you will manage to pull records in MDM.

If you are not pulling existing records form any remote system then you don't need PI inbetween. OCI will help you for data exchange between SRM and MDM system. For some scenario's like Catalogue content Management (Self-service Procurment) you can manage without PI.

Cheers,

Rc

[Former Member]

Hi,

Is there a middleware (Pi) required to connect "SRM MDM" with "SRM" ?

Yes, PI is required. Reason being SRM MDM is a MDM repository name. when we unarchive this predelivered .a2a repository from SAP, it does not contain any data that is Main table data as well as reference data (Countries, Regions etc). So in order to populate reference data from SRM we can populate this data in MDM repository (SRM-MDM Catalog) using some settings in T-code MDMGX of SRM system. But for main table data, we need to send this data from SRM system to MDM using middle-ware (PI). SAP has also provided pre-delivered content for PI using which you just need to do configuration of scenario in PI. So using some standard reports when you execute it, it sends this data to PI and thus finally to MDM (SRM-MDM) which is recommeded way to send data from SRM system to MDM.

Please also check SAP Note: 1177779

Regards,

Mandeep Saini

[Former Member]

Hi,

In the SRM MDM Catalogue bundle provided from SAP, there are 2 SCA files provided along with the other components. So your basis team need to deploy those SCA files through SDM (Software Deployment Manager) in SRM Portal. The files arovided are for background connectivity of MDM+SRM and the second one is for UI(User Interface) Management. So after deploying the same, your basis team will provide you 1 url which is composite of your server name, port etc.

Paste that URL in Internet Explorer and it will route you to that UI Manager. You should have UI Manager role assigned to your user ID so that you can access the UI. By Default there is 1 user created in MDM as Master with blank password which is used to maintain the UI as it has that role assigned to it.

So when you open that link, it will ask you for server name, password of that server and later User ID of SRM repository and Password. When you login into that, it will show you the configuration done for SRM Portal. There is one button named as OCI (Open Catalogue Interface)mapping. So when you press on that, it will open the OCI mapping sheet where the MDM fields will be mapped to corresponding SRM Portal fields to view the data. By this mean only the connectivity is done for SRM MDM Scenario.

XI is required in only case when you need both the functionalities like you need to use SRM MDM and normal MDM scenario in a single repository. For eg you have one catalogue consisting several materials which are displayed as Catalogue and all the materials which are changed, should be sent to XI to send it further.

Once OCI is done, you need to maintain the webservice in SRM System for accessing the catalogues in MDM directly. For that Masks are created and assigned to that particular user id. In web Service, you need to define the URL, Server Name, Repository Name, Password, Mask etc by which you can automate the process and bifercate the users to access the catalogues related to their country or organisation.

Please let me know in case of any issues.

Regards:

Gaurav