MDM - Import Repository schema

Hi all,
Have any one tried "Import Repository Schema" operation in MDM Console ?
I want know the purpose and how this works.
Please provide me the materails if you have any.
Thanks in advance.

Hi ArunParbhu,
We perform "Import Repository schema" in order to import i.e. define schema of the repository. We can import repository schema using an MDM schema file.For this operation ,the repository must be unloaded."Import repository schema" operation will create new tables and fields in the repository.
U can get more details about how to import repository schema from console reference guide available at service market place.It is very well explained after page 210 onwards.
Hope it will help u.
Thanks,
<b>
Shiv Prashant Dixit</b>

Similar Messages

Error Importing Repository Schema Into Repository

Hi,
I am currently working on a project at a client and I am having an issue importing an XML Repository Schema into a repository.
I have Development and Quality Repositories which are supposed to be nearly identical. There have been quite a few changes made to the Quality Repository and the client wants me to export the Quality schema and import it into the Development repository and accept a few changes (I realize changes are typically migrated from Development to Quality). This should be a relatively simple task however I keep receiving the following error: u201COne or more of the selected items requires that you select additional itemsu201D, when I attempt to change just one field. I have scoured the SAP forums and exhausted the Reference Guide for MDM and I cannot find a solution. Any help or suggestions would be greatly appreciated.
Thanks,
Don

Hi,
You are facing this issue because you are trying to import changes in an object, but rejecting changes for its dependent objects. For example, you are trying to import a new port with a new remote system, but not accepted change in the remote system table.
I would suggest you to check the MDM log files. it will give you more details why your import repository schema is failing, and which dependent object need to be imported.
Kindly check the log files and revert.
Best Regards,
Shiv

SRM MDM 3.0 BMECAT Repository Schema

Hello at all,
I have currently run the SRM-MDM 3.0 with the standard respository delivered as archive on the install CD. I still have created some data with the data manager and it runs all very well.
Now I want to import a catalog based on BMECat 1.2 standard. I Have the complex catalog data XML from the vendor Bechtle and the images folder for the articles.
When running the Import Manager there are many fields and tables in the source xml that do not excist in the destination hierachy (repository).
My question is how do I create a repository based on the BMECat 1.2 standard to import the vendor catalog xml ?
What I still tryed was. Creating a new repository. It's empty except of the standard table like Admin, Images, Products etc.
Than go to Transport -> Import Repository Schema -> choose the vendor XML
That doesn' work. I get the Error Message: "There are problems with the transport (XML) which prevent it from being processed"
I have learned that an XML schema data is described with the ending .xsd but when I try to import the databrowser looks for .xml endings.
Could someone please advice what's I have done wrong?
Thanks a lot.
Rico

Hi Rico,
I am not aware of BMEcat standard but in MDM terms you can take the backup of repository in two forms:
1. Archive/UnArchive -> If you want to move the repository from one MDM server to another i.e. from dev to QA then you can Archive the repository which creates the .a2a file and place the file in the Archives folder of MDM Server installation directory which can then be copied and moved to Archives folder of target MDM server and you can UnArchive it on that MDM server.
Archive = Repository Schema + Data
2. Export / Import Repository Schema -> With this method you can export the schema of the repository and create the new repository on some other MDM Server using Create Repository from Schema command. When you perform the export repository schema command, it will ask for the file name and path. You can then copy this schema file and place in the file system of another server.
Export / Import Repository schema = Repository Schema only
Regards,
Jitesh Talreja

Error while Importing customer repository schema

Hi All,
I want to import a customer repository schema into vendor repository so that i can have multiple main tables.
I exported the customer repository schema and tried to import it in Vendor repository.
In the pop up that apperas when we click the Import repository schema and select the file from the source location i selected the below options
1. for all the modify operations i selected the operation as "Reject "
2. For all the delete operations i selected the operation as "Reject"
and
3. for all the add operations i selected the Operation as "ADD"
for Vendors table(main) the operation was to delete for which i selected the reject operation and for customers table(main) i selected the add operation.
Now when select ok the system throws the below error
"One or more selection Items require that you select additional Items. would you like to see the report".
On clicking yes to see the report i get the below message
*Transport operation failed:
Dependency check failure. A reference to object of type: MatchingStrategy named: Customers:MDM_CUSTOMERS cannot be resolved because the object is not being added.*
Can anyone please help me in understanding where i am going wrong?
regards,
Sharma.

Hi Sharma,
I am quite sure that this problem is related to MDM Strategy only.If you delete your strategy and try u will be able to do so:
Please check you strategy or check may be in strategy u have some lookup field and corresponding lookup table is not transported.
See the error says:
Dependency check failure. A reference to object of type: MatchingStrategy named: Customers:MDM_CUSTOMERS cannot be resolved because the object is not being added
Regards,
Neethu Joy

Create MDM repository from repository schema.

Hi,
I have exported MDM repository from one MDM console schema and saved it. Now I am trying to create a Repository from a different MDM console using this Schema. I am getting the Error "ERROR LOADING FILE".
The versions of these MDM are different. Is this causing the failure? How can I overcome it?
regards,
MRao

Hi Mahesh,
This is an Un-usual error, which even I am facing. In my case there is no version mis-match. I am trying to take the Export the Schema from a rep in 1 MDM server and then importing into another rep in another server.
Hence it might not be a version issue.
However, check the following things in your case.
1. Check the Original repository for error and repair them if found any. Upload your repository with Updated indices. Export the schema out and save it on your desktop.
2. Try creating a new repository using Import Schema on the same MDM server and check if its still showing you an error.
3. Try importing the schema on an Existing repository on the same MDM server.
4. Try Importing the schema and create a new repository on a different MDMserver.
Please check it in a test environment and no need to press the OK button while Import schema. We just need to see if the Import schema windows opens.
If in any case, you do not find the error, then probably we can understand the clear reason of the Error.
If error still persists, then would advice you to raise an SAP ticket for the same.
Hope this info helps.
Thanks and Regards
Nitin jain

MDM 7.1.4 SP4 don't Export Repository Schema

Hi,
I am using SRM-MDM Catalog3.0 , MDM 7.1 SP04 , in console , to operate Export Repository Schema failed.
MDS log:
Could not transport expression because it contained a non-transportable element: 'Item Status [Approved]'
Assignment Code='Set_Status_Code13' of Table Code='MDMSRM_CATALOG_ITEMS' requires additional steps before transport.
how to solve?
thanks in advance
Jesse

Hi Jesse,
Please refer SAP Note: 1385073:
In the Note>Navigate to General>Note the following
1. A code field was added for Validations and Assignments. All repositories must undergo verify/repair before loading for
the first time in MDM 7.1 SP04 so that the added codes for Validations and Assignments are implemented.
2. Validations and assignments from previous versions that contain lookup values will need modifying before the repository schema can be transported as the lookup values in expressions will now internally include the lookup table ID in addition to the value itself. This change was made to ensure that expressions with lookup values are transported correctly.
In order to modify these expressions you will need to load the repository and delete all the referenced lookup values from
each expression and then add them back into the expressions. If you try to transport the repository schema before modifying
the expressions, you will receive a transport error and a message will be generated in the MDS.log stating the assignments or validations that need to be updated.
Regards,
Mandeep Saini

MDM Import Manager Batch

Hi everyone,
We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
[Source]
Type=XML Schema
XML Schema=CREMDM04
File name= \...\... CREMDM.CREMDM04*.xml
DSN=
DBMS Server=
Database=
User=admin
In advance thanks,
Aklilu

Hi Aklilu,
the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael

Exporting and Importing of Schema

The Export and Import of Schema is not working consistently in SP4.
When I create a new repository from the schema, all the subtables get created. The main table is has only one field in it. It reads Category.
The other fields in the main table are missing and are not imported during the Import Schema operation.
Has anyone encountered the same issue?
If so, please let me know how you overcame this errorneous behaviour?

Hi Adhappan
I have tried importing without success. The import is not consistent. The same schema creates different sets of tables & fields each time. Sometimes if you reimport some more tables which were not set up the first time gets selected for import.
I did a simple exercise to test the import / export functionality.
1. I unarchived a repository from standard content provided by SAP
2. I exported the schema
3. I tried importing the schema without any modifications to schema
4. The results were highly inconsistent.
Arvind
Pls reward useful answers

Exporting and Importing the schema with AQ capability

Hi,
We have a production DB which is using Advance queuing and this whole queuing is working fine in Prod but now we have a problem in test Env and it seems that somebody has already tampered the test DB. (the queue reads and sends the messages to DB2)
So i wanted to export the prod schema and import it to the test schema that we have.
i wanted to make sure that if i import it to test db , it doesn't send the messages to the prod DB2 database!!
now it should send the messages to the test DB2 database.
How can i see where it sends the messages after i imported it ? how can i change it?
i'm not sure if i have explained my problem in a correct way and if you have understood my question. Please send me messages and i can explain more about it.

Hi Adhappan
I have tried importing without success. The import is not consistent. The same schema creates different sets of tables & fields each time. Sometimes if you reimport some more tables which were not set up the first time gets selected for import.
I did a simple exercise to test the import / export functionality.
1. I unarchived a repository from standard content provided by SAP
2. I exported the schema
3. I tried importing the schema without any modifications to schema
4. The results were highly inconsistent.
Arvind
Pls reward useful answers

Identifing duplicate master data records using the MDM Import Manager

hi all
I read the Topis "How to identify duplicate master data records using the MDM Import Manager</b>"
i tried to create import maps and to set rules. but when i import them it creates the new vendor records for each rule with rest of the fields blank.
when i import vendor data all the three fields i.e Match rate , match type and match group are blank.
My Question is :
I am getting vendor data from SAP R/3.
In which source (in lookup xml file or data xml file) do i have to include these above three fields and how all the rules will be reflected in repository?

Hi Sheetal
Here we go when do you Import any data (vendor master) please follow the following steps;
1. First of all apply the map to the source data
2. In the Match Record tab there are 3 possiblities
   a.[Remote Key] : Checks the current source rec with
     repository along with all the fields - This is
     default
   b.Remove [Remote key] - by double click the same; and
     choose any single fields like Vendor Number or
     name - Then the current record will be matched
     with the repository based on the field.
   c.Instead of single field you can choose combination
     also.
3. Based on the Match results, match class will be set
   automatically;
   a. None
   b. Single
   c. Multiple
4. Then Match Type
    a.Exact-All the individual value matches are Equal.
    b.Partial-At least one value match is Equal and at least one Undefined; no value matches are Not Equal.
    c.Conflict-At least one value match is Equal and at least one value match is Not Equal.
5. then chek the Import status and Execute the import.
Hope this helps you.
cheers
Alexander
Note: Pls dont forget reward points.

What is meant by criteria of Updateability in MDM Import manager

Hi,
What is meant by criteria of Updateability in MDM Import manager? i read some information, but i could understand, it says original data source be updateble. what is meant by Original data source.?
what is the use of option "Read-only" in Import manager logon screen.
Thanks

Hello Ankam,
You can check the Read-only option to prevent MDM from updating your data source.
Kindly see the below information on "DATA SOURCE UPDATES"
DATA SOURCE UPDATES
Some MDM Import Manager operations require that the original data source be updateable, thereby allowing new fields and/or entire new tables u2013 and the corresponding data values for each record u2013 to be automatically added to the data source before further processing.
Other operations simply create virtual fields in the MDM Import Manageru2019s workspace, although if the data source happens to be updateable, some of these operations instead add the new fields to the original data source as well.
NOTE ►► Updating the data source when possible allows you to
perform additional operations on the new fields as if they were part of
the original source data, and also use them as record matching fields.
NOTE ►► Fields that are added only if the data source is updateable
can be deleted automatically by the MDM Import Manager when you
exit or switch data sources based on the setting of the Delete Created
Fields on Exit configuration option.
Updateable Data Sources
Whether or not a data source is updateable depends upon the following:
u2022 Source type. The source Type must permit the MDM Import Manager to update its schema and insert the additional fields of data; some supported types are updateable and some are not.
u2022 Media. The media on which the data source resides must itself be updateable. If the media on which the data source resides is readonly, such as a CD-ROM, the data source cannot be updated.
u2022 Permissions. You must have the proper file system permissions to update the file, or the proper DBMS permissions to update the schema of the database.
u2022 Read-only option. You cannot have checked the Read-Only option, which prevents MDM from updating the data source even if the other conditions would otherwise permit it.
NOTE ►► The Read-Only option is: (1) enabled for source types that
can be updated (Access, Oracle, SQL Server, and XML); (2) disabled
and unchecked for those that use Access as an updateable staging
area (Delimited Text and Fixed Text); and (3) disabled and checked for
those that cannot be updated (Excel and ODBC).
NOTE ►► When the data source is SQL Server, the table names in
the database must not contain spaces; otherwise any operation that
would update the data source will fail.
Hope this helps.
Regards,
Vikas

Differences between various source files in mdm import manager

Hi,
Can anyone tell me the differences between the source files(access,xml,xml schema,excel) available in mdm import manager?
Thanks and regards,
Rithesh
Edited by: rithesh_shet on Mar 30, 2010 1:04 PM

Hi Ritesh,
MDM Import Manager provides flexibility to Import Data from different types of Sources into MDM.
You can import data into MDM from below mentioned sources using Import Manager:
1. From Files (Access, Delimited Text, Excel, Fixed Text, XML and XML Schema)
2. Directly from Data base source (SQL server and oracle)
As mentioned by Mandeep, XML Schema is something which you define in MDM console in advance. and then later select the Data source XML file and XML schema from drop down list (it will show all schema defined in console ) to validate XML source file against the XML schema.
For automated Import, Ports are used. Ports are nothing but a logical point of contact with other systems i.e. other systems or middleware will drop file on the port for authomatic import and MDM import server will scan the port directory and if file is present then will import data automatically from file into MDM using a predefine Import Map. (this map needs to be defined manually in import manager and then assigned to port using console).
Please check page no 45 of import manager reference guide for more details about various source properties of Import Manager. (*link for import manager reference guide is already provided on the earlier post)
Also check, page no 53 to 64 for how to import process. Kindly revert if you have any query.
Regards,
Shiv

SAP MDM Import Server

Hi,
I need to work in SAP MDM Import Server.
I have already worked in SAP MDM Import Manager.
I need to know a more about SAP MDM Import Server.
Is it an application?
Regards
Kaushik Banerjee

Hi Kaushik,
I need to work in SAP MDM Import Server.
I have already worked in SAP MDM Import Manager.
I need to know a more about SAP MDM Import Server.
Is it an application?
The Import Server is a separate MDM application that uses import maps created within the MDM Import Manager to automatically load source data files into a repository.
The MDM Import Server (MDIS) automates the task of importing source data into MDM repositories. It is designed to reduce the processing complexity, resource requirements.
To know more about MDM Import server, which is also called the MDIS, please follow the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
Go to MDM IMport Server (MDIS).
You will find the complete infomration about it.
You can find the complete process of Automated Import ansd Syndication in the link mentioned below:
Master Data Management Import Server and Master Data Management Syndication Server - Webinar Powerpoint
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
Hope it helps.
Thanks and Regards
Nitin Jain

Redo the syndication map if the Repository schema changes?

Hi ,
We have changed the repository structure after creating the syndication map which is based on the repository schema.Now when I load the syndication map with the updated schema ,i am not seeing the newly added fields on the destination items,so we loaded the destination properties with new schema again but the map of all the fields are no more available which leaves us to redo the map again.Is there anyway that the destination is updated with new fields without redoing the map again.
Thanks

Hi Aravind,
unfortunately there is no way to solve this issue but rebuilding the map. The reason is the way syndciation maps are stored in MDM 5.5. This is subject to change (and improve a lot!) in MDM 7.1. But in 5.5 you'll have to rebuild the syndication map completely if you change the repository schema, respectively the XSD file you use as a basis for XML distribution.
Best regards
Michael

Import/export schema with ODI

Hi all,
do you know if with ODI11g I can import a full schema from Oracle database to another Oracle database?
Thanks
Erika

why don't use imp/exp command to export schema from source db and import into target db.
1) export11g ODI repository schemas in DMP files
example : my 11g schemas are "ODI_MASTER" and "ODI_WORK"
exp userid=odi_master/*odi_master* file=c:\odi_master.dmp
exp userid=odi_work/*odi_work* file c:\odi_work.dmp
2) import the dump file into new schemas in the new database (or is it the same database ? in my case, it was a different one)
imp userid=SYSTEM/password touser=odi_master fromuser=odi_master file=c:\odi_master.dmp
imp userid= SYSTEM/password touser=odi_work fromuser=odi_work file=c:\odi_work.dmp
--nayan

MDM - Import Repository schema

Similar Messages

Maybe you are looking for