The process portrayed here shows which steps are required – in a technical sense - in order for development to begin with design in the ES Repository. It also explains the shipment options and the options for transferring to a new version.
1. Before development begins, software component versions must be available in the System Landscape Directory and assigned to a product version. This is normally carried out by a development manager.
○ At SAP, software component versions and products are imported into the System Landscape Directory from the PPMS system.
○ Customers can create their own software component versions and products in the System Landscape Directory (see: Defining Third-Party Software).
2. When development begins, the development manager or project manager imports the software component version from the System Landscape Directory into the ES Repository and defines the namespaces for development. Furthermore, for each imported software component version he or she can define a system from which RFCs or IDocs can be imported (see: Importing Software Component Versions).
3. With the namespaces now available, development can begin with design in the ES Repository.
○ Changes are saved in user-specific change lists. To make these changes visible for all users of an ES Repository, the developer must either activate the entire change list or individual objects.
○ SAP developers assign a release state for data types and service interfaces. This informs customers of the development status and the usability of the services delivered by SAP.
4. To ship the design objects in the ES Repository, you must export them in a file. You may want to export the objects to import them into a test system, for example. See also: Transports.
5. When developing a new version of the product, you normally increase the version number of the software component and the product from step one. By using a release transfer (more information: Transferring Design Objects), you can transfer design objects from other software component versions into the new software component version.
6. For more information about developing new versions, see Compatibility of Changes.