Double Maintenance of Corrections
The provided sources do not contain enough detail to write a grounded, accurate definition — the snippet for Double Maintenance of Corrections into Development is truncated and supplies no substantive claims beyond the concept name and its URL. Without additional source content, any definition would rely on facts not supported by the provided snippets, which is not permitted. Please provide the full source text so a proper definition can be written.
Docs explaining this concept
Prerequisites
- Concept Versioning and Branches for ABAP Software Components The concept name provided is "undefined," which does not correspond to a specific SAP developer concept that can be defined. Based on the available sources, the closest identifiable topic is the **Maintain** phase in the SAP BTP add-on lifecycle, which refers to the ongoing development and delivery of updates to a SaaS solution after its initial release. Developers use this phase to ship patches, corrections, and new feature versions of their add-on to keep the SaaS offering current. For more details, see the [Maintain documentation on SAP Help Portal](https://help.sap.com/docs/btp/sap-business-technology-platform/9721f0fb92a84e2a95309acf445cb0a9?locale=en-US&state=PRODUCTION&version=Cloud).
- Concept ABAP Environment Branching Strategy A branching strategy in the ABAP Environment defines how development teams organize and manage branches within their software development processes. Developers use it to structure parallel workstreams, though they should be aware that there are [some restrictions for using branches](https://help.sap.com/docs/btp/sap-business-technology-platform/ea47e09911c24f658e5f111d21729ffd?locale=en-US&state=PRODUCTION&version=Cloud) in ABAP-based development processes on SAP Business Technology Platform.
- Concept Correction and Development System Landscape (COR/DEV) A **Correction and Development (COR/DEV) system landscape** is a transport landscape in which corrections and new development are maintained in separate dedicated systems. Because changes made in the correction system do not automatically propagate to the development system, developers must perform [double maintenance of corrections into development](https://help.sap.com/docs/btp/sap-business-technology-platform/1241b144b83b4ca9a317db326e36950d?locale=en-US&state=PRODUCTION&version=Cloud) to keep both systems in sync. This approach allows teams to deliver urgent fixes through the correction track while continuing new development independently, at the cost of applying the same change in two places.