Solution Administration and Solution Documentation in Solution Manager 7.2 works with branches, to enable you to separate your productive solution content from new content that is currently being worked on. For example, if you run an implementation project to include new systems into your landscape, you can document the project in a separate branch (for example Development branch). When the project is finished and the new solution goes live, the contents of the Development branch can be brought into and merged with the contents of the Production branch. Please refer to SAP online help available at http://help.sap.com to find more details on the branch concept itself (follow the path Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Administration -> Solution -> System Landscape) and the lifecycle management in Solution Documentation (Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Documentation -> Lifecycle Based on Branches).
Interface Documentation participates in this lifecycle. When you release an Interface Details element or a superior element which contains Interface Details elements (like a dedicated folder in the Interface Library, or the Interface Library itself), a corresponding Interface Details element is created in the target branch in the same place.
Be aware that the original element in the source branch and the newly created object in the target branch are physically separated. Both objects carry their own LIFO ID (see chapter Technical Aspects). This means all changes you do in one branch won’t affect the corresponding object in the other branch. This applies especially to interface attributes which are system-independent. As described in chapter Maintain Interface Attributes those attributes are synchronized across all contexts (sites and system roles) in the same branch. However, they are not synchronized across different branches. This enables you to document a new version of the same Interface (for example in Development branch) without interfering with the currently active version of this Interface in the Production branch.