cancel
Showing results for 
Search instead for 
Did you mean: 

Master Data Conguration Tables

Former Member
0 Kudos

Hello,

We are setting up master data in MDM SP3. When maintaining master data we will be updateing the lookup tables in MDM. Before we syndictate the data back to R/3 we need an R/3 configuration update process to update configuration tables from MDM.

Has anyone set up a process to update R/3 configuration tables from MDM? How was this done?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Our strategy is to maintain master data centrally and distribute enhanced master data to global R/3 clients. To enable this we need to be able to update R/3 configuration code tables from the external MDM master repository.

We cannot distribute enhanced or changed master data without the updating code tables that maintain the updated value lists. If we wait for a migration from dev to QA to production we will not be able to update master data in a timely manner and no one will be able to maintain master data effectively.

Has anyone developed an effective method to achieve this?

Former Member
0 Kudos

Hi Owen,

I haven't tried this so it's just theoretical but it might help.

1. Create a Syndication map to produce an XML document for your code table(you'll need an XSD representation of the code table). You'll probably need as many maps as code tables. Make sure the maps have the "Suppress Unchanged Records" feature turned on. This way only inserts/updates produce XML documents. You can use the Syndication Server in order to have syndications run automatically on a periodic basis.

2. Configure XI to pick up the XML from MDM and map it to an RFC(hopefully this exist, if not you can create one) that updates the code table in R/3(usually IDOCs are used to update R/3 but I don't think there are any for code tables)

Hope this helps,

Richard

Former Member
0 Kudos

Hi,

We did not do it intentionally for the following reason:

1. To maintain standard process of verification and validation ( Test -> QA -> Production) of configuration and business processes.

2. To maintain transport mechanism in R/3.

Is there is any specific thing you have in mind why are you thinking about this?