MDM - Portal Integration scenario ...

[former_member469694]

I am new in the MD area.

We have over 500000 vendor records and we are planning to load these data manually by using the import Manager then do the de-duplication process manually in the MD Data Manager.

Once it is in the On-going/Steady state stage , we are planning to use the portal to create/modify vendors.

Could anybody explain how the MD Portal integration with the sequence of vendor creation and change process woks?. What about email notification between the requester and the data steward?

I am assuming the sequence of operation may be like this:

Requester entering the data in the portal and requesting approval from the Data steward, Data Steward approves it, then it crates the vendor record in the MD etc.

Anybody explain this in little more detail as the operational or user point of view?

[former_member469694]

NA

[Former Member]

User will log onto yor corporate federated portal

Will go to , hopefully the MDM page

This Page should be service oriented, to mimic the existing processes on paper/mail/request desk of your As-is state.

So for example, say the user click a button or link saying request creation of Vendor,

A interactive form or iview should be started where user can enter all the information necessary for creation of vendor.

once done with filling up , user should hit submit for Approval, if any needed. ( Provision for any attachments might be provided)

Guided Procedures running behind the screen can route the request to the proper approver based on

A) requestor

B) Any of the Vendor attributes.

Approver will get a mail saying a new approval entered his/her queue. ( can set a deadline).

Once approved the request is again routed to the data steward by GP.

Steward(s) will get an email notification about the request.

Once verified/enriched steward will hit that submit button , at which point a new records for Vendor should be created in MDM and next syndication should relay that record to the concerned source system(s).

Similar should be the process for modify/block/unblock.

technology pieces involved on portal side.

iview

Guided Procedures

MDM Java API embedded within Java webdynpro.

-Sudhir.

[Former Member]

oh And BTW

all along the process requestor can view the status of his/her request in the UWL queue.

also if Approver rejects the request approver can log comments and reauestor can act based on the comments and resubmit the request.

if Steward rejects the request, same case comments->requestor->modify request->resubmit-> " But herez the catch put a switch so that steward can decide if the modified request needs to be routed through approval or directed to steward back gain?

-Sudhir