Process documentation Development Cycle in the Integration Repository Locate the document in its SAP Library structure

Purpose

The exemplary process portrayed here shows which steps are required technically speaking in order for development to be able to begin with design in the Integration Repository. It also explains the shipment options and the options for transferring to a new version.

Process Flow

...

       1.      Before development begins, software component version 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: Maintaining Third-Party Products).

       2.      When development begins, the development manager or project manager imports the software component version from the System Landscape Directory into the Integration 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 the design of the business processes in the repository. Changes are saved in user-specific change lists. To make these changes visible for all users of a repository, the developer must either activate the entire change list or individual objects.

       4.      To ship the objects in the repository, you must export them in a file. You may want to export the objects so as to import them into a test system, for example.

       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 release transfer, you can transfer objects from other software component versions into the new software component version.

       6.      Note the information contained in the Compatibility of Changes section of this documentation when developing the new version.