Vendor Scenario Advice required

[Former Member]

We have MDM 55 sp3 and need to implement the vendor scenario. Can someone advice on how the following scenarios can be implemented :

1. We have vendor groups in R3. Now whenever an attribute changes for any vendor, we need MDM to change that attribute for all vendors that belong to the same vendor group and syndicate the data back to R3.

Please advice the detailed steps for the same(we need information on the steps to configure MDM to change the attribute for all vendors of that group).

2. Is it possible to dynamically pass a mask name from portal (MDM business package) and get data for that mask only back into the resultset iview of portal. Point to keep in mind is that we will always have the same user mapped and we need to pass the mask dynamically to the search iview.

Any info would be appreciated

Nirmal

[Former Member · Accepted solution]

Hi Nirmal,

Here we go for the solutions

(I) Vendor group..R3 to MDM

a) Transfer the XML IDOCS from R/3 of all vendors, whos attribute value got changed.

b) Import the files from the File adapter location to Import manager and apply the corresponding map to the imported records.

c) Open the Datamanager and use free-form search to collect all the vendors related with particular Vendor group.

d) make the changes in all the vendors in the correspoinding attribute field. SAVE all

e) Open the syndicator and perform the syndication to the corresponding MDC R/3 system.

The above five steps are explained about the manual process, the complete process can be automated using E-catt(SAP R/3) & Test-Partner(Non-SAP), where corresponding Vendor group and the New Values of the attribute captured during the changes and will be used during MDM Data manager consolidations...

hope this might helps...

Please feel free to revert to me for further clarifications.

Thanks

Alexander

Note: Pls reward the points, if found helpful.

[Former Member · Accepted solution]

Alexender,

Thankyou for the detailed steps on the manual process. Could you please provide a more detailed information on the automated process as we will certainly go for an automated process. We are planning to use the import manager batch to import data. Would appreciate if we could be pointed to some documentation for making the search and change data automatic/ or provide some detailed steps for the same.

Nirmal

[Former Member · Accepted solution]

Hi Nirmal

The automation process can be achieved by both E-catt(SAP R/3)& Testpartner(Non-SAP). Kindly go thru the E-catt doc before proceeding.

<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm">E-catt</a>

E-catt basically talks about the scripts where we can record the sessions and customize the same for both Import & Export parameters and we can call Test partner scripts also.

Steps to be followed...

1. Install both E-catt & TestPartner in ur machine

2. Start recording the SAP R/3 part in the e-catt editor and do the customization for the parameters..(Vendor group, attribute values)

3. Test partner script can be created in the e-catt environment itself, as a external tool.

4. Refer the Test partner script in the e-catt script.

hope this might helps...

cheers

Alexander

Note:Pls reward the points, if found solved ur problem.

[former_member132278]

Nirmal,

Have you found a solution to your 2nd questions: Pass a mask name? I am hoping to only use the out of the box MDM iViews without creating this iViews from scratch.

Thanks.

[Former Member]

Hi Nirmal,

The first question is a perfect case of harmonisation.

When you make a change in the Vendor in R/3, you can send an IDOC to the XI system.

The IDOC is then mapped to XML using XI.

The XML file can be downloaded to the import READY folder in import manager server.

The file is picked up and the data is loaded into the central repository.

Also using the key mapping, the data is sent out back to the other systems using syndicator for harmonisation.

Hope that helps.

Please revert back for more clarification.

Regards,

Tanveer.

<b>Please mark helpful answers</b>

[Former Member]

hai,

Well the reply for point(1) is that analyze the data consistancy and format of your R/3 data. as you say its R/3 you can use MDM Standard Vendor Repository. You can download this along with your MDM software from SAP Marketplace. You need to build import maps from R/3 to MDM then you can perform Cleansing from Import Manager. Once the import is done you can use Form Search for identifying the Dupilicates (In Sp04 you have auto De-deuplicatoin facilty) Once you are done with de-duplicatoin you will have to build syindicator maps using syndicator. I recommend use XI for Import and Syndication.

point(2). Currently the MDM Standard Business package provide few iViews. You can build your own IViews for Masks.

i hope i tried to answer you questions.

Veera