Package Builder 

Purpose

The Package Builder tool allows us to implement the concept of the package in the ABAP Workbench for the first time ever. Packages are designed to help developers modularize, encapsulate, and decouple units in the SAP System. They are a further development of the concept of the development class used today and contain additional semantics.
In particular, the Package Builder is used to migrate existing development classes to packages, making it a new tool for developing and maintaining development classes.

The first projects to use the package concept come from the mySAP Workplace area. The emphasis is on technically decoupling resources from the Core R/3 System, so that different products can follow different release cycles.

A short tutorial is present at the internal website:

https://bis.wdf.sap.corp/twiki/bin/view/Sapinternal/PackageConceptShortTutorial

How to Call

Call the Package Builder using either transaction SE21 or transaction SPACKAGE.

Features

·        Create packages and sub-packages

·        Specify a package hierarchy

·        Define package interfaces for potential users

·        Add elements to package interfaces

·        Define use access for user packages

·        Restrict the use of interfaces to selected users

·        Create structure packages and define filter package interfaces.

Scenarios and Use of Packages

Packages can be either provider (server) or user (client) packages. Provider packages offer development elements (function modules, BAPIs, classes, ABAP programs, types, and so on) to other packages using one or more interfaces. A provider can also be a user, availing itself of the services of other packages.

In the documentation that follows, we have assigned a variety of scenarios to each of these two roles (provider and user). Each scenario explains how you use the Package Builder and which functions are relevant.

Tasks for Provider Packages

I. Creating packages and defining the package hierarchy

For more information, see Scenario 1: Defining the Package Hierarchy

II. Making Services Available

For more information, see Scenario 2: Making Services Available

Tasks for User Packages

I. Creating packages and defining the package hierarchy

For more information, see Scenario 1: Defining the Package Hierarchy

II. Using services

For more information, see Scenario 3: Using Services from Other Packages

Package Checks

Package Checks and System Settings

Package Architecture in R/3 Enterprise

Package Architecture in R/3 Enterprise