Version Control Mechanism for MDM

Hi All,
Can anybody please tell me how version control mechanism is used in SAP NW MDM.
Thanks in advance
Chandan

Hi Chandan,
If you are looking out for maintaining the history of all the Master records, then to the best of my knowledge its not available in MDM. MDM only deals with the latest version of records, however, you can still get back to the old values of records( in data base) , using the change tracking functionlity in MDM.
However, MDM GUI's will show you only the latest updated values.
To know about the change tracking and how it can be integrated with a UI, refer to the link below:
How to Configure SAP MDM Change Tracker for Any Repository:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807861ac-f941-2c10-8f8d-c57f9d421b99
Now, in case you are asking about the ALL VERSIONs feature of MDM, which we use in relation with Check out, then refer to the link below:
How to Control Versioning in SAP MDM
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0b392b8-d4b7-2b10-a189-b3b61df3d9c4
Hope it helps.
Thanks and Regards
Nitin jain

Similar Messages

Version control tool for Mac OS X?

Hi all
If using labview on Mac OS X,
do you have some version control tools to recommend?
Thanks a lot

As far as i know, LV for Mac does not integrate with source code control provider. LV for Windows has two requirements for this:
a) Professional Development Environment
b) A source code control provider compatible to the Microsoft Source Interface
There is still always (Mac, Linux and Windows alike) the possibility to control source files using the SCC providers client software.
Many open source project SCCs like CVS or Git integrate, at least in Windows, in the File Explorer.
I recommend you to research possible solutions like this for Mac.
The next question is if you want to use a distributed SCC or a local one. Depending on this, you will have to setup a network server with compatible provider (e.g. RhodeCode).
LV provides both a Diff and Merge tool as EXE (Professional). I am not sure if this is also true for the Mac version, so look for "LVCompare" and "LVMerge".
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Version control design for multi department collaboration

Hi all,
I've just implemented my first Hyperion Planning project. As a new commer, my design seem not good for the client.
- Requirement (Data flow): Marketing => Sales => Production (Manufacturing)
- Design: Each department data has its own version of data and use business rule to move data between versions
     + Marketing - Working version
     + Sales - Working version
     + Production - Working version
Each version is then assigned to a planning unit hierarchy for approval.
Is there any other way to resolve this data flow between departments? There's guy who suggests I should use Data Validation Rule and change approval path dynamically. Is it the best way to resolve my problem?
I really need a solution so that departments can collaborate with each other (result of previous department is base data for next department. If a department didn't finish their job, then next department can't enter data) but don't know how to implement it in Hyperion. Please help. Thank you so much.

Hi,
You seem to have over-designed the requirement. I think if you had used a single version (i.e. Working) for all the departments involved, you wouldn't have faced most of these issues. The key thing to remember is that Planning allows one planning unit to be edited by one user at a time. So when a particular user is done with the inputs (s)he can forward to another user (i.e. Department) for the next set of inputs.
Cheers,
Alp

Version Control for Application Express

Hi all,
We are using Application Express (HTML-DB) 2.0 with Oracle 10g Release 2. We have developed a number of pages within our application (basically sales reporting). We are starting to get ready move these pages to a test and production environment.
Before we move to a production environment we need to implement a version control and migration (development -> test -> production) system. I have read various posts about importing and exporting pages and applications that have been very informational. However, I am still not clear on certain areas, any help/information on the below questions/comments would be helpful.
1.     How are other people implementing version control? For some of our other environments (for example, PeopleSoft-SQR) we use Visual Source Safe. Can we use this along with Application Express or is there a way to keep track of versions within Application Express it self?
2.     I see you can view a pages history at Home>Application Builder>Application 107>Page Definition>History. Is there a way to view the differences between the pages or to revert back to an older page?
3.     I know you can export a single page but that leaves shared components behind that might leave the complex page in a non-working state if imported and installed in the production application. Is there a way export and import shared components, for example LOVs?
These are a few of the questions I havebut I thought it would be a good place to start.
Here are a couple of links that have given me some information related to the topic.
Synonyms
http://htmldb.oracle.com/i/doc/mvl_manage002.htm#sthref1206#BABFBBEE (I believe this is for HTML-DE Version 1.5I did look in the same area for 2.0)
Version Control
How do people version control HTML DB applications?
I would be interested in hearing your thoughts and ideas on this topic.
Thanks,
Stuff

Stuff - this is also something we've been grappling with.
Did you see the excellent tip about using Web server (or PL/SQL) redirects to point to the current app? The idea is that you copy the current prod app, work on the copy and then update the redirect to point to the new app when it's released and make the old app unavailable.
This is quite brilliant in its simplicity, and has the added benefit of leaving the old app intact for bug fixes and re-releases, (or even rollback) if necessary. However, the problem with it, and the reason it's no good for our purposes, is because it sits on top of the same schema, so if the version control applies to objects in the database (i.e. the schema itself or packages etc.), then you're snookered (as far as I understand it anyway).
In a previous project, our suppliers used VSS and versioned code at the app and function/procedure/package level - I'd love to know if anyone has a robust scheme for versioning at page level.
I suspect History is an audit trail rather than versioning - I can't imagine that all the objects in all their respective states are being persisted for anything other than 'undo' purposes.
Versioning at page level seems to be problematic but it can be done, provided that the shared components are sufficiently consistent. The trick is to edit the security group ID, but the usual caveats apply.
What seems problematic to us is how to create a build out of components at different versions, like you might in a conventionally-packaged exe. I think we might end up checking in (or just saving in the file system) consistent versions at app and package level (having developed and tested in a separate schema or instance), and doing an overwrite of the prod app plus running a DDL script for package/function/procedure updates with schema deltas and other things like image uploads applied manually at cutover.
I suspect that once I delve a bit deeper into where all these objects are stored, there will be more potential for scripting, but I'm not entirely confident that this will, reliably, give us entirely what we had in Pre-Prod. Another problem I've found with this approach is that packages don't get consistently replaced.
It may simply be that we're applying waterfall concepts to what is really a RAD tool, but in any case this is my first Web-enabled development so I've been at sea with everything from design methodology to version control.
Like you, I would be really interested to hear of other suggestions.
Regards,
John.

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Version control in BO 6.5 & XI

How is the versioning controlled in Business Objects? Do we need to use any configuration management tool for bO 6.5? Is it inbuilt in BO XI?

Hi Navneet,
There are some version control tools for BO, like BISolid.
What they do is versioning of universes and reports, and they control the deployment towards the different repositories.
Makes it easy to rollback a version in production, or automates the manual steps needed to promote a report/universe.
Regards,
Lisette Johnson

Version Control - Web(JSF) project

Hello fellows,
Which version control for Web project you are using? I have been using CVS for common java (and nojava) projects but is there any another version control tool for Web projects. Any suggestion how web projects should be stored in repository?, how web project should be maintained ?.
Any help and suggestion will be helpful.
Thanks in advance.

SVN is better then CVS

Putting ~ into a version control system

Hey folks!
I'm curious as to how one could put ones home directory into version control, to quote Codemac;
codemac wrote:I keep my ~ in mercurial, so all files are checked in and versioned. [...] I highly suggest you put your $HOME into version control. It's real fun to see what your home directory looked like 3 years ago
I once used Subversion under Mac OS X to download a random project just for kicks, but had no idea what it was all about really. I understand that a version control system assists (manually or automatically?) in labeling files/data/"units" with version numbers, and storing the data as well? I've also seen that a number of users here use Git, another version control system, to label and share their various configuration files. Where is the data stored? On a server belonging to someone else or on ones own computer?
I found a Wikipedia article on the topic, although Subversion isn't named there, so I may be wrong on that one.
Is there a CVS that is small in size and amount of features and easy to get the grasp of?
Thanks in advance.

I'm having my ~ under version control now for a while (I am using git - the decision to do so was mainly motivated by my desire to learn git). However, I don't track every file in my ~. Just the configuration files (.bashrc, .bash_logout, .zshrc, .awesomerc, vim ... etc. etc.) and some docs (though I keep them in a different private repository). I'd recommend that if you plan to put your ~ under a VCS that you should think about what you plan to track and what not first. It certainly means some additional work, because you have to remember to commit changes back into your repository every time you change a tracked file. Of course you can perform a commit on every logout, but if you want to revert/restore a single file, it's better to track changes in files individually. As I see it, the main idea of keeping your ~ in a VCS system is to have a backup from where you can restore a single file to every point in time you want, or to revert uncommited changes which broke sth. in an instant. So, IMHO it doesn't make that much sense to have the repository on your laptop only, but also to have a remote repository (in case your HD dies). For me, it's also a nice way to keep my home directory in sync over multiple machines.
As for the decision on which particular VCS to use. I first tried to do that a year ago using svn, and it didn't work out that well - for some reason I don't like svn - but that doesn't mean that svn is bad - it could be right for you . Darcs is an easy to learn VCS but it lacks some features like branches and the like (which you may not need in this szenario anyway). I don't know much about Bazaar or Mercurial, because I've never used them, however from what I've read, these two are very popular choices nowadays (maybe someone with some experience with those can shed some more light ). Also, you have to chose the VCS according to what you like to track, because they differ in performance and the extra storage they need to keep track of the changes (I read a good article which compared all named VCSs regarding repository/metadata size in differrent szenarios, small files only, big files only etc. etc. - but unfortunately I can't find it atm).

ODI Control Mechanism

I need to design a control mechanism for ODI(Sunopsis) if Any one design it for their client such document is highly appreciated.
I need following steps to include in the control mechanism
1.Organize Workflow
2.Restart strategy for Scenario
3.Log management for insert rows, start and end time.(Client is not interested in using operator for logs)
Thanks
Saif

Hi ,
The username you are connecting to from backend and fireing the query and its a success,
Is the same username being used for connection through the topology manager?
Reshma

Extremely slow performance on projects under version control using RoboHelp 11, PushOk, Tortoise SVN repository

We are also experiencing extremely slow performance for RoboHelp projects under version control. We are using RoboHelp 11, PushOk and a Tortoise SVN repository on a Linux server. We are using a Linux server on our IT guys advice because we found SVN version control under Windows was unstable.
When placing a Robohelp project under version control, and yes the project is on my local machine, it can take up to two hours to complete. We are using the RoboHelp sample projects to test.
We have tried to put the project under version control from Robohelp, and also tried first putting the project under version control from Tortoise SVN, and then trying to open the project from version control in Robohelp. In both cases, the project takes a ridiculous amount of time to open. The Robohelp status bar displays Querying Version Control Status for about an hour before it starts to download from the repository, which then takes more than an hour to complete. In many cases Robohelp becomes unresponsive and we have to start the whole process again.
If adding the project to source control completes successfully, and the the project is opened from version control, performing any function also takes a very long time, such as creating a topic. When I generated a printed documentation layout it took an astonishing 218 minutes and 17 seconds to complete. Interestingly, when I generated the printed documentation layout again, it took 1 min and 34 seconds. However when I closed the project, opened from version control, and tried to generate a printed documentation layout, it again took several hours to complete. The IT guys are at a loss, and say it is not a network issue and I am starting to agree that this is a RoboHelp issue.
I see there are a few other discussions here related to this kind of poor performance, none of which seem to been answered satisfactorily. For example:
Why does it take so long when adding a new topic in RH10 with PushOK SVN
Does anybody have any ideas on what we can do or what we can investigate? I know that there are options for version control, but am reluctant to pursue them until I am satisfied that our current issues cannot be resolved.
Thanks Mark

Do other applications work fine with the source control repository? The reason I'm asking is because you must first rule out that there are external factors causing this behaviour. It seems that your it guys have already looked at it, but it's better to be safe than sorry.
I have used both VSS and TFS and I haven't encountered such a performance issue. I would suggest filing it as a bug if you rule out that the problem is not related to external influences: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en
Kind regards,
Willam

Jdev support with PVCS Version control system

Hi,
Is there any JDev plugin available for PVCS source control system.
We have to use PVCS version control system for our SOA composites. If there is no plugin available, what is the approach commonly used for these scenarios.
Thanks for your response.

Which JDev version do you use?
AFAIK there is no extension for PVCS available for 11g (check http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml).
Anyway if you have an external tool which lets you work with PVCS you can use it outside of jdev without a problem. Depending on the interface you might be able to do some kind of integration into jdev using the 'External Tools...' interface.
Timo

Urgent Help Metadata Version Control

Hai Friends...
Any version control available for metadata at design time.
Cheers
Gopi

Gopi,
I think you have posted within the wrong forum...
Christopher

Version Control integration with SVN

We want to implement Version Control integration for Siebel Tools with Subversion (SVN).
After an informal chat with a consultant from Oracle, we got the reply like: Test, and see if it works.
Now for my question, does anyone know a project where they used SVN as the version control tool in a Siebel project?

Nothing much yet, but I found a website that has the batch file for integration with SVN.
Guess I have to contact the author to get more details:
http://arwaheem.wordpress.com/2008/04/30/siebel-version-control-source-code-integration-using-sub-version/

MS Visio 2007 for MDM Workflow

Hi,
We are working on MDM SP06 patch 2.
Just want to know whether MS Visio 2007 version is compatible for MDM workflow since only 2003 products work fine with MDM .Has anyone tried this out?
Please suggest
Regards
Nisha

Hi,
Just now went back to Master Guide of MDM SP06 it says That MDM doesnt support Microsoft 2007.
What version of MDM are u on?
Regards
Nisha

License Control Mechanism Implementation

Hi,
I am now trying to implement a license control mechanism for a web based application.
I've studied several websites about this topic, but they did not provide much about the
implementation details. So...could somebody please clarify for me
where(websites, paper, books,API...) should I find the information.
Thanx.

Hi,
Chapter 5: Software Piracy and Code Licensing Schemes of ISBN: 0072225653 has a nice and simple introductory chapter on this topic with full code examples.
Regards,
Duncan Eley.

Version Control Mechanism for MDM

Similar Messages

Maybe you are looking for