SAP MDM Interview Questions
Q1. What is SAP Master Data Management?
Ans: SAP Master Data Management (SAP MDM) empowers data honesty across the business organization, in a heterogeneous IT scene. SAP MDM assists with characterizing the business network climate in light of nonexclusive and industry explicit business components and related ascribes - called ace information. Ace information, for instance, cover colleague data, item masters,product designs, or specialized resource data. SAP MDM empowers the sharing of fit ace information, previously caught in various frameworks, and guarantees cross framework information consistency paying little mind to actual framework area and merchant. It assists with adjusting ace information by offering types of assistance that perceive indistinguishable expert information articles and keep them reliable. Furthermore, it empowers the league of business processes, by giving steady dissemination components of expert information objects into different frameworks, inside the organization and across organization limits.
Q2. What are the MDM Functional Components ?
Ans: Import Server, Syndication Server, Console, Import administrator, Data chief, Syndicator, Publisher and so on.
3. What are the MDM Business Scenarios?
Ace Data Consolidation
Ace Data Harmonization
Focal Master Data Management
Rich Product Content Management
Client Data Integration
Worldwide Data Synchronization
Q4. What is Master Data Consolidation?
Ans: In Master Data Consolidation situation, clients use SAP NetWeaver MDM to gather ace information from a few frameworks at a focal area, distinguish and tidy up copy and indistinguishable items, and deal with the nearby article keys for cross-framework correspondence.
Q5. What is Master Data Harmonization?
Ans: In Master Data Harmonization situation upgrades the Master Data Consolidation situation by sending the united expert information data to all associated, far off frameworks, in this way keeping bound together, excellent information in heterogeneous framework scenes. With this situation, you can synchronize internationally pertinent information across your framework scene.
QQ6. What are the capacities and elements of SAP NetWeaver MDM?
Ans: SAP NetWeaver MDM is utilized to total expert information from across the whole framework scene (counting SAP and non-SAP frameworks) into an incorporated vault of combined data. High data quality is guaranteed by partnering orchestrated ace information that is universally pertinent to the bought in applications. An organization's quality guidelines are upheld by guaranteeing the focal control of expert information, including support and capacity.
Q7. What are SAP MDM's significant advantages?
Ans: SAP MDM: Helps organizations influence previously dedicated IT speculations since it supplements and incorporates into their current IT scene. Diminishes generally speaking information upkeep costs by forestalling numerous handling in various frameworks. Speeds up process execution by giving complex information dispersion systems to associated applications. Guarantees data consistency and exactness, and along these lines diminishes mistake handling costs that emerge from conflicting expert information. Further develops corporate dynamic cycles in essential deals and buying by giving modern data to all individuals.
Q8. What is Parametric Import ?
Ans: Parametric Import is a new and profoundly more effective way to deal with bringing in and changing information that is reasonably like parametric hunt. Parametric import records the total arrangement of particular qualities for each field in the source information.
Q9. Mightn't you at any point accomplish this by utilizing the present EAI and additionally ETL applications ?
Ans: EAI instruments give the association between various frameworks on the specialized layer to guarantee message dealing with, semantic planning, steering and lining of information. ETL instruments give comparative usefulness however are ordinarily conveyed less as a message dealing with layer and more as a bunch situated, huge volume joining component. As a structure block of the SAP NetWeaver stage, SAP MDM use the cycle coordination capacities of SAP's Exchange Infrastructure (SAP XI), be that as it may, likewise, additionally offers types of assistance for content union, information harmonization, focal support and controlled information conveyance as per the business interaction semantics.
Q10. When will SAP MDM open up? How might it be estimated ?
Ans: Customer increase is booked to start in September 2003. It will be evaluated independently as a motor, in view of the quantity of overseen information objects in the associated frameworks.
Q11. Is SAP MDM an augmentation of my SAP PLM ?
Ans: No. SAP MDM can be utilized related to mySAP arrangements including mySAP PLM or non-SAP arrangements.
Q12. Why is SAP MDM part of SAP NetWeaver ?
Ans: SAP NetWeaver is a mix and application stage that brings together and adjust individuals, data and business processes across advances and associations. SAP Master Data Management (MDM) is a structure block of SAP NetWeaver to empower data honesty across the business organization and to work with a superior correspondence of data across a heterogeneous IT scene.
Q13. What provoked SAP to start improvement of SAP MDM ?
Ans: Integration is the way to outcome in business. Furthermore, since heterogeneous framework scenes are ordinary today, just organizations with nonstop cycles and ideal admittance to reliable data can get themselves a definitive upper hand. The essential standard behind this is the accessibility of solid and reliable expert information.
Q14. Is SAP late to this market ?
Ans: No. There are a couple of uses declared in the market today, which are tending to parts of the arrangement. Anyway those arrangements are regularly restricted to colleague data just and don't address the interaction joining necessities to keep up with and convey the orchestrated expert information. SAP is the main supplier that offers a wide and various availability and business content created by SAP and its accomplice organization, in light of SAP's close, longstanding information on thorough business processes in excess of 20 enterprises. This business content abbreviates the improvement cycle for clients and drives down the expense of incorporation projects.
Q15. Is SAP MDM a xAPP ?
Ans: No. SAP MDM is a structure block of the SAP NetWeaver stage. SAP MDM can be authorized and utilized independent in heterogeneous conditions as well as related to other mySAP.com arrangements or xApps in future.
Q16. How might SAP MDM be executed ?
Ans: Implementation administrations will be given by SAP's Global Professional Services Organization as well as along with chose framework integrators.
Q17. Will this arrangement supplant the current expert information dispersion methods between my SAP CRM and SAP R/3 (SAP BC, CRM middleware) or SAP R/3 and mySAP SCM (CIF interface) ?
Ans: Those connection points including ALE will keep on being utilized in lined up with process functional information. Supplanting those connection points with SAP MDM isn't arranged.
Q18. Will it be feasible to utilize SAP MDM just with SAP Exchange Infrastructure or might an organization at any point likewise utilize other EAI instruments ?
Ans: The utilization of the SAP Exchange Infrastructure is the establishment for SAP MDM. SAP arrangements are controlled by the SAP NetWeaver stage with high accentuation on interoperability to :NET and J2EE/Java.
19. For which outsider items will SAP give the connectors ?
In the main stage the connectors to outsider items will be given on a task premise. SAP intends to make chosen connectors to outsider frameworks to a piece of the standard arrangement in future.
Q20. How might MDM squeeze into Enterprise Services Architecture? Which Web administrations will be given and when?
Ans: MDM is fundamental to SAP's ESA system. The underlying rundown of archived Web administrations with MDM 3.0 were given MDM 3.0 data discharge. These allude to the capacity to get to dominate information data in MDM as a help to make records, and so forth. New web administrations will be accessible according to the guide. With SAP MDM 5.5 related to SAP Exchange Infrastructure, one can make web administrations by uncovering MDM capabilities utilizing MDM JAVA or .NET APIs.
Q21. What articles will be upheld by SAP MDM? What administrations will be offered ?
Ans: The underlying arrival of SAP MDM will uphold the accompanying expert information objects: colleague, item ace, item structures, archive joins, specialized resources and change aces.
Administrations gave rely upon the kind of articles and will incorporate support of items, look for objects, work process, mass changes, change notices, copy checking, and notices for object creation and suspension.
Q22. How coordinated is SAP NetWeaver MDM 5.5 with SAP NetWeaver and applications?
Ans: SAP Net Weaver MDM 5.5 is a fundamental piece of the NetWeaver stack. In the ongoing component discharge, venture application coordination, both SAP and non-SAP, is achieved through SAP XI. Interoperability with different frameworks is conceivable by means of SAP Net Weaver MDM 5.5's APIs (remembering ABAP whose improvement is right now for process). Tight, local mix is essential for the SAP Net Weaver MDM 5.5 guide and further pre-fabricated joining focuses will be carried out as we progress along the advancement way. SAP MDM 5.5 SP2 will give view-just iViews to SAP Enterprise Portal.
Q23. Is the Product Catalog Management application part of the SAP NetWeaver Integration and Application Platform? Does print distributing have a place with this stage too?
Ans: Yes, these are all essential for the SAP NetWeaver stage and print distributing is an expansion of the capacity to item happy administration. By definition, this is the situation since the previous A2i xCat application, presently further expanded and known as SAP NetWeaver MDM 5.5, is important for the SAP NetWeaver MDM group of items.
Q24. Will the arrangement give the connectors to all SAP arrangements ?
Ans: SAP MDM will give connectors to mySAP CRM, mySAP SRM and SAP R/3 in the principal stage. MySAP SCM will be upheld through SAP R/3 in the main stage. In the following stage, an immediate connector will likewise accommodated mySAP SCM.
Q25. What instruments are accessible to incorporate SAP MDM and other non-SAP applications and stages?
Ans: SAP MDM 5.5 uncovered its center capabilities utilizing distributed JAVA and .NET APIs. Any reconciliation among MDM and other non-SAP programming can be taken care of utilizing APIs. Additionally, MDM capabilities can be uncovered as web administrations involving APIs related to SAP Exchange Infrastructure. More extensive coordination between SAP MDM 5.5 and other SAP NetWeaver parts will be accessible through item guide.
Q26. What choices are accessible for resending from MDM inside XI or R/3 in the event that an update fizzles?
Ans: If the disappointment lies with XI or R/3, a similar XML can be gone back over (no resending is required). On the off chance that there is an approval or information issue, the records should be recognized and changed in MDM Data Manager Client and the Syndicator bunch will resend them as they were refreshed since the last partnership.
Q27. How simple is it to keep up with the front-end when the information model changes?
Ans: The work relies upon the quantity of fields expected for the front-end. Fields that are added have no effect. Fields that are erased (and kept up with in the front-end), should be taken out. Fields that are renamed should be refreshed.
Q28. Establishment work process
Ans: We are currently introducing work process. Aside from introduced workflow.exe and vision proficient 2003, is there something else we want to ensure that should be introduced?
To make new MDM WF Templates, then on your PC introduce SAP MDM Workflow, Data Manager and Vision. Assuming there are requirements to arrangement jobs for specific clients for WF Steps, then, at that point, you will require Console as well.
For a main client process or execute some basic WF errands/steps, the SAP MDM Workflow, and Data Manager is sufficient.
Q29. Is it conceivable to dole out the saved hunt models to a job or individual to limit what the person can see in the pursuit?
Ans: The saved inquiry choice is client PC explicit. That implies that a client's inquiry standards are accessible just to the client and not to different clients. Consequently the saved pursuit isn't a choice for this situation. Utilizing job limitations you might accomplish the necessary outcomes.
Q30. Are connectors/expansions accessible in MDM for coordinating observing apparatuses? (ie. does Tivoli enlist in the event that a special case happens in MDM?)
Ans: MDM as of now doesn't set off outside processes on blunders. The framework utilizes logging abilities to enlist blunders and there are explicit log records for the different parts of the framework. In the event that the checking framework/s can be set off on changes to the log records then the framework can be observed.
Q31. About MDM
Ans: I am working in CCM 2.0 on SRM 5.0 and am intrigued to find out about MDM. I as of now fill in as a Functional Consultant. I'm intrigued to realize how does the MDM respond, and as a utilitarian specialist, what might be my job.
Q32. SRM-MDM 1.0 - Missing MDM pieces
Ans: I as of late downloaded and introduced SRM-MDM index 1.0. I discovered a portion of the pieces missing like MDM Syndicator, MDM Syndication Server, Image chief, and so forth.
Q33. How would I get these devices? A portion of these are exceptionally basic to our execution.
Ans: SRM-MDM does exclude the MDM Syndicator. On the off chance that you want the Syndicator, you really want to buy a full MDM permit.
Q34. MDM 5.5 SP4 Patch 01, 02 Install guide
Ans: I have introduced MDM.5.5 SP4 and I really want to introduce the Patch 01 and Patch 02. I have downloaded the patches from the help commercial center yet unfit to track down any documentation on the best way to introduce the fix.
Q35. Is there any aide on fix establishment?
Ans: MDM patches are normally finished establishment of the MDM parts that have had enhancements made to them. These parts should be reinstalled which typically requires around 2 minutes for every part.
You would follow a similar technique as though you were moving up to another SP.
Likewise, MDM Patch 3 is now accessible in Service Marketplace. You don't need to independently introduce Patch 1 and Patch 2.
On the off chance that you are utilizing MDM4J or Portals, you need to ensure the Software Component Archives you are conveying match the MDM Server adaptation.
I suggest you eliminate the old SCAs and afterward send the new SCA matching the server form.
Q36. MDM Installation
Ans: I'm introducing SAP MDM 5.5 SP04 following the Installation Guide in the Marketplace. Nonetheless, toward the finish of the establishment I don't have the default stores for Materials, Vendors and Customers.
Q37. Is there a method for telling in the event that I skirted any step that produces this default tables or storehouses?
Ans: You want to download "MDMBC55004P_3-10003437.ZIP" which contains Business Content (Repositories, Import/Export Maps, XSDs and so forth) and duplicate .a2i records into <MDM Server Folder>/Archives catalog so you will actually want to un-document them.
Q38. Is it conceivable to foster web structures (beyond EP6) that connect to standard Java MDM APIs and speak with the MDM vault?
Ans: Yes it is conceivable as you are not restricted to the utilization of iViews that exist. Your own application-explicit iViews can be made. You can likewise get to the server with direct calls to the API from the java climate.
Q39. MDM console GUI on Windows
Ans: This is a managerial issue. I'm an accomplished Basis individual, introducing SAP MDM 5.5 SP04 interestingly.
I have arranged the MDM server (mds) on Solaris 10 framework. I have additionally arranged MDM import server (mdis) and Syndication server (mdss) on a similar machine. I have introduced the data set programming and designed the vacant archive on a similar host machine. The information base and all the 3 MDM administrations (mds, mdis, and mdss) are running on a Solaris machine.
From that point forward, I introduced "MDM console fat client GUI" part on my work area and attempted to "mount the server" by determining the "hostname" of the Solaris machine where MDM administrations are running, however I am not ready to mount it. It says invalid server and doesn't mount.
According to which, you ought to have the managerial right on Solaris machine where MDM server is running; yet how would I have that being a Windows client.
Q40. Could you at any point offer some guidance on the best way to move toward this issue?
You want to actually look at the accompanying:
Ensure that the MDM Server form and the MDM Console variant are the very same.
There are no firewalls or traffic-interfering with applications between the client and server machines.
There's nothing clearly off-base signed in the server's log document (search for a ServerSomethingSomething.xml record in/pick/MDM or/select/MDM/receptacle).
At the point when you start "mds" on the server, it runs mds-r utilizing nohup. Is there anything important in nohup.out?
Ensure that other organization correspondence (FTP, SSH, and so on) between the client and server works impeccably.
Q41. MDM Expressions: Count, Max, Min, Concat, and so on
What are the purposes of the orders in the MDM articulation manufacturer?
Ans: There is by all accounts no documentation accessible regarding the matter. Concat doesn't acknowledge various boundaries, so how is it that one could link at least two strings?
Additionally, the total capabilities (Max, Min, and Count) don't appear to work across records.
Q42. Might you at any point give any pointers concerning these?
Ans: The COUNT, MAX, MIN, SUM, AVERAGE and CONCAT capabilities are for use with multi-esteemed query fields.
The COUNT capability "Counts the quantity of all appointed multi-esteemed query field values". The MAX capability "Returns the biggest number of all relegated multi-esteem query fields (for example Cost)". MIN, SUM and AVERAGE return appear to be obvious.
CONCAT "Records generally doled out upsides of a multi-esteem query field isolated by a semicolon"
To connect strings, use "and".
Q43. How would I check in the event that the client is running or not?
Ans: Each MDM client like control center, import supervisor, etc is its very own program. So assuming that you start it, it's running. To check assuming that the MDM server is running, the least demanding way is to begin the MDM Console and to mount the comparing server.
The server symbol will show you the status. A red symbol implies: server is halted. The green symbol implies: server is running. The equivalent is substantial for any store introduced on your MDM Server. Mount a storehouse and afterward the symbol tells you on the off chance that it's running or not.
Q44. MDM utilization?
Ans: I have gone through certain articles about MDM which says that MDM gets the information from various applications utilizing XI and pushed something very similar to SAP BI.
Q45. Is MDM utilized exclusively to give information to BI?
Ans: MDM isn't simply used to send information to BI; it is additionally utilized for Master Data harmonization so every one of the various frameworks in an association like CRM, R/3, and Legacy have similar expert information.
It is additionally for Rich item satisfied administration, Customer information combination, Global information synchronization, and so on.
MDM is utilized for different purposes also, however its primary intention is to keep up with 'Expert Data', in light of what you want.
Q46. MDM preparing?
Ans: I am a starter client of SAP MDM.
Might you at any point give me the critical regions or subjects that I need to zero in on in learning MDM?
It would be useful in the event that you can likewise provide me with the quantity of days every subject would take.
There are chiefly 4 themes: Console (multi month), Import Manager (15 days), Data Manager (multi month), and Syndicator (15 days). Clearly, days required are subject for banter.
Q47. What is combination and harmonization?
Ans: There are really three fundamental procedures in information unification. The utilization of either will rely predominantly upon the corporate practices for IT where MDM is being carried out.
* Ace information harmonization: Here the expert information is replicated from every client framework into MDM. A matching is required to recognize copies, and construct the MDM interpretation tables that will permit to know where the information is, and which records compare to a similar genuine "object" in your various frameworks (Key Mapping Tables). All things considered, each single framework simply functions as in the past, and the additional worth of MDM is that you know EXACTLY where your information is, and the number of "genuine articles" you have across your frameworks.
* Ace information combination: This above and beyond; here you perform initial a harmonization (as above), merge the sections on worldwide fields, and rearrange the information to the first frameworks. In that situation NO DATA is made in MDM. The additional worth is connected with the way that information will be steady across the company. You might envision that the trouble here is to sort out which data ought to "win" in struggle cases. Here you really want a decent purifying instrument, with pertinent matching methodologies.
* Focal expert information the board: This the last jump. Just business as usual above and beyond, and you begin making midway information in MDM, and circulate it to the different client frameworks.
Q48. MDM Main Table
Ans: When you make another vault in MDM, it consequently makes a principal table named Products. I would rather not utilize this as the principal table and I need to make my own primary table with various qualities.
Q49. How would I erase this Products table?
Ans: You can't erase the principal table, however you can rename it.
At the point when the storehouse is dumped, you can re-name, add new fields to the primary table. You can likewise make new sub tables.
For a more definite interaction, you can allude from the MDM Console Reference Guide.
Q50. Missing Import Map?
Ans: I have saved an import map. I can see it when I attempt to trade it yet I am ready to see it in the control center.
Q51. How would I persuade this guide to be apparent in console?
Ans: The main spot where you see an Import Map is while you make "Port". You want to choose the proper "Client System" to see "Guide" drop down loaded up with the fitting Import map.
You can likewise take a stab at restarting the control center.
Q52. Send out, import the jobs and clients tables
Ans: Is there any likelihood to product and import the job and client definitions?
We have a SAP MDM store with a great deal of jobs and clients and furthermore with a ton of changes. I'm looking for a quick and effective approach to dealing with the jobs and clients.
There is no product/import usefulness for jobs and clients. The best way to deal with these in a mechanized manner is compose a program that utilizes the Java or ABAP APIs. Both APIs open usefulness to make, update and erase jobs and clients.
Q53. How would you connect a picture to an information record, field, and characteristic in MDM SP03?
Ans: Images are not straightforwardly connected to a record/field/property. All things being equal, they are connected to a field or property text esteem.
To connect a picture, you first need to stack it into the storehouse. This is generally finished in the Data Manager by going to the "Pictures" table and adding a record there. Pictures are held in holders called "Gatherings" which permit you to consistently bunch pictures (logos, symbols, full-page, and so on). You first need to characterize the gathering you need to store your pictures in. You can do this by tapping the "Alter" button while adding a record to the "Pictures" table. Bunches are put away in a various leveled structure; right snap the design when altering gatherings to add another gathering.
When a gathering has been chosen, you simply add the documents you need to make pictures from. When the record has been added to the "Pictures" table, you can choose that picture for a picture field/characteristic.
The advantage of connecting is that the genuine picture (the double information) is just put away once in the archive and can be referred to different times.
Q54. MDM in business situation
I need to know when and where precisely we use MDM. What are the upsides of MDM?
Ans: Master information the board for the most part becomes an integral factor when you work based on a heterogeneous IT scene. This implies, you have a few or numerous application frameworks running and every one of them has its own arrangement of expert information records, for example, merchant, client, item and so on. For this situation almost certainly, you have excess information - that is, copy records in a single framework, or indistinguishable information scattered north of a few frameworks inside the scene however without the overall information collection. Notwithstanding the overt repetitiveness issue, scattered ace information is probably going to have different quality levels, which again may prompt unfortunate business execution.
With ace information the executives, you can acquire generally speaking information on your lord information across your IT scene to empower combined revealing, and increment the general nature of your lord information records in your IT scene through information purging, advancement and de-duplication.
For a utilitarian outline of SAP NetWeaver MDM, allude from the accompanying URL:
In the mean time, SAP NetWeaver MDM highlights the accompanying abilities:
Information Extraction. It extricates ace information on a consistent article level from a client framework.
Information Transformation. It changes construction and content qualities during import and partnership of expert information.
Information Cleansing. Standardize and normalize data capabilities.
Information Enrichment. Reciprocal information capabilities to accomplish total and significant expert information. For instance, utilizing outsider administrations.
De-Duplication: Match and union items to dispose of uncertain and excess information.
Key Mapping: Provide cross-framework distinguishing proof to guarantee venture wide information quality.
Information Validation: Ensure consistence as per characterized measures.
Information Modeling: Provide the climate for making and expanding information models for object stores.
Information Distribution: Distribute midway merged ace information on object level to client frameworks with delta taking care of.
Distributing: Enable multi-channel distributing. For instance, it distributes item information in printed lists or Web lists.
Q55. Trait - TEXT field Limitation
Ans: What is the most extreme length of text that can be obliged in an "Quality"?
Q56. Is there some approach to bringing in text from a record not from the Import cycle but rather from the information director?
Ans: The greatest length for a text characteristic worth is 128 characters.
While bringing into your principal table by means of the Data Manager Import, the import cycle will provoke you when it finds message quality qualities that are absent in your scientific classification (skip, add, and so forth.).
Bringing ascribes into scientific classification isn't totally imaginable with the Data Manager's import. Utilize the Import Manager all things being equal.
Q57. Blunder while perusing object PartnerGUID
Ans: When we sent the sellers data from MDM into R/3 utilizing XI, we got this blunder:
"Blunder while perusing object PartnerGUID"
Q58. Might you at any point make sense of what this implies?
Ans: I accept the qualities are case delicate. Actually look at your case and send it once more.
Q59. Populate scientific categorization tables?
Ans: How would you populate scientific categorization and order tables?
Q61. What is the distinction among scientific categorization and order in SAP MDM (5.5 - 0 SP03)?
Ans: Taxonomy is likewise a pecking order. In any case, it is an exceptional sort of progressive design where you can characterize credits and join those credits to scientific categorization classifications. The basic role of scientific classification is to characterize your information.
Q62. Separate the rearranged and conventional Chinese in MDM
Ans: We characterized one multilingual field in the primary table, which support Chinese [CN], Chinese [TW] and different dialects. In the partnership XML record, we found the language key of Chinese [CN] and Chinese [TW] are same. The two of them equivalent "ZH". They ought to appear as something else, truth be told.
Q63. Is this a bug? How could we separate the worked on Chinese and conventional Chinese?
Ans: We have applied SP3 Hotfix5.You simply have to pick "Nation Code" as the worth of "language design" in Syndicator Map properties.
Q63. How do work processes for XI, MDM, and EP vary? What sort of work process could you suggest from a Portal/MDM arrangement?
Ans: Workflow for XI is for business process situated, not individuals arranged.
Work process in MDM is information situated and approvals/focal information creation arranged.
Work process on Portal, as I have seen, is individuals situated for things like Knowledge Management.
For a Portal/MDM situation, you could utilize Guided Procedures, which is the way SAP is wanting to deal with every one of the various work processes across the scene. The Guided Procedures handles and screens either process on SAP and on Non-SAP frameworks.
Q64. Un-documenting Inquera Repository
Ans: I attempted to un-document the Inquera Demo Repository that I downloaded from the Inquera Website. I've done as such far this.
I set the chronicle document InQuera_Demo_55_060227.a2a in the accompanying catalog: C:\Program Files\SAP MDM 5.5\Server\Archives.
The MDM Server and the SQL Server Database is on a neighborhood have.
At the point when I attempted to un-chronicle the example vault from the control center, I didn't see the document record that I set in the envelope C:\Program Files\SAP MDM 5.5\Server\Archives. I had a go at renaming the record as well; to "Sample.a2a." yet I actually didn't see the demo storehouse chronicle.
The record size is around 150 MB. I have another document record in the very registry that is around 2MB that I'm ready to see when I un-chronicle from the control center, and it's anything but a secret document. I'm ready to see the .a2a document in Windows Explorer.
Q65. Might you at any point give me a few thoughts on the best way to fix with this?
Ans: You can attempt these means:
You want to un-mount different storehouses that you have.
Re-start MDM Server.
Revive (Hit F5) in the Windows Explorer (C:\Program Files\SAP MDM 5.5\Server\Archives).
Open the control center and un-chronicled vault.
Q66. Not ready to Un-chronicle Repository?
Ans: I have this issue that at whatever point I un-chronicle a vault in the control center (server and client variant 18.104.22.168), the MDM Server administration stops in the center, in which the un-filing activity gets cut in the middle between.
The storehouse is then set apart as invalid.
This appears to happen each time I document a store as well. Other than that I am ready to mount and make vaults.
Q67: What may be the reasonable justification?
Ans: I ended up dealing with a similar issue some time back. By and large, restarting MDM server or MDM administrations will tackle the issue. It will be far superior on the off chance that you do a reinstallation of the MDM Server.
Q67. Vault chronicle alerts
Ans: Recently, when I chronicled a vault, it expressed that it contained alerts. I ran check on the storehouse and it detailed no blunders or non-lethal mistakes, just alerts. After checking the log, the alerts all comprise of: Warning (1385) the table 'xyz' has not been examined as of late.
68. How would I fix this?
Ans: You can attempt the accompanying cure in the Console part of the MDM:
Check Repository - > Repair;
Q69. Is there a method for chronicling and un-document Repository without information?
Ans: Yes. While filing, in the "Chronicle MDM Repository" spring up, click on "Choices" button and select "Mapping as it were".
At the point when you un-chronicle this, you will get a store with mapping in particular; no information.
MDM Program organizers
Q70. Might we at any point indicate the "Prepared" and "Document" envelope to be organizers other than the envelope under MDM program envelopes?
Ans: One model is to determine an organizer in a far off server as the "Prepared" envelope.
Indeed. You should design these qualities in mds.ini document.
Conveyance Root Dir=C:\PROGRA~1\SAPMDM~1.5\Server\Distributions\
These envelopes can be anything the length of MDM Server approaches those catalogs in the Remote Server.
After you set the property for Distribution Root, then, at that point, make the Port in Console.