Dear SDN community,
I'm glad that the Master Data Management forum is now open for you as a direct information channel. If you want to track and display MDM-related information that has been posted prior to the opening of this forum, simply enter "MDM" in the search field.
Kind regards,
Markus Ganser
Dear all,
Vendor master , Customer & Material master are three critical masters in any organization. So is the case with us. Since our organization has a large corporate wide INTRANET, one of the requirements being asked is to use this to create similar to SAP screen - pages for vendor master create, cust. mf create, etc. validate the different codes ( possibly show drop downs) and save the entries in a SQL table.
The master governance team will scan the entries created by corporate-wide users , periodically ( say weekly, daily, etc ) and take the entries ( after filtering some), use LSMW to create the customer master data, vendor master data, etc.
What we are also doing in case of vendor master is having a link between the SQL primary key and SAP vendor master unused field ( in SAP we store the SQL primary key here, created a secondary index on LFA1). The intranet user is able to see the status of the vendor code details created and the SAP vendor code via a RFC.
All this is in place, but the additional requirements is what bothers me. The new requirements are : --> eliminate LSMW, create an RFC to create vendors, customers,
--> give provision for changing details of vendor, customer, etc.
We also have IS OIL as add-on and hence direct BAPI call to create cust. master does not work fully.
Is MDM a viable solution for us ?
Add a comment