-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- Double Maintenance
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Double Maintenance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012 May 10 2:13 PM
- SAP Managed Tags
- ABAP Development
Hi everyone,
I have a question here. What is Double Maintenance and why do we need it?
Moderator message: no interview-type questions please, search for available information.
Message was edited by: Thomas Zloch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012 May 10 2:56 PM
- SAP Managed Tags
- ABAP Development
Hi,
This might be needed in two situations:
- upgrade to higher version of SAP (ex. 47c to ECC6)
- You implement separate systems for project and maintenance
The first case is a temporary situation; it is a project to upgrade the system.
The second situation is probably permanent; The company intends to facilitate (maybe) the coexistance of ongoing projects and day-to-day -possibly urgent- maintenance of the system.
Either way, imagine that during the course of a project, where a good deal of existing objects have been modified, you have a problem in the production system that requires an urgent correction. Say no invoices can be printed.
Since you do not want any new modifications (from project) to be transported to production, you may have to comment many objects, make the correction, then uncomment, with the risk of a mistake.
Having two separate transport chains like:
> Project: DEV - TST - QUA - PRD
> Maint: DEV2 - TST2 - PRD
allows you to quickly correct any problem and transport it production without disrupting the project.
This correction will have to be copied manually from DEV2 to DEV or else you will lose the correction when the project moves to production.
That's double maintenance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2012 May 10 2:56 PM
- SAP Managed Tags
- ABAP Development
Hi,
This might be needed in two situations:
- upgrade to higher version of SAP (ex. 47c to ECC6)
- You implement separate systems for project and maintenance
The first case is a temporary situation; it is a project to upgrade the system.
The second situation is probably permanent; The company intends to facilitate (maybe) the coexistance of ongoing projects and day-to-day -possibly urgent- maintenance of the system.
Either way, imagine that during the course of a project, where a good deal of existing objects have been modified, you have a problem in the production system that requires an urgent correction. Say no invoices can be printed.
Since you do not want any new modifications (from project) to be transported to production, you may have to comment many objects, make the correction, then uncomment, with the risk of a mistake.
Having two separate transport chains like:
> Project: DEV - TST - QUA - PRD
> Maint: DEV2 - TST2 - PRD
allows you to quickly correct any problem and transport it production without disrupting the project.
This correction will have to be copied manually from DEV2 to DEV or else you will lose the correction when the project moves to production.
That's double maintenance.
Bluesky