You can integrate Records Management in all SAP applications. The following integration options exist:

• System-controlled execution of activities in records
• Navigation from an application to display a record
• Navigation from an application to display any element
• Integration of an application entity by implementing a new service provider

These integration options are described below.

You can specify that the system carries out activities in records in the background. SAP provides a range of Business Application Programming Interfaces (BAPIs) for this, which can manipulate the record without the need for user interaction. The BAPIs act on the business object RECORD. To view the available BAPIs, use the BAPI Explorer (transaction code BAPI). In this transaction, choose Basis ® Basis Services, and open the business object RECORD. The following BAPIs exist:

BAPI_RECORD_CREATE: Create record

BAPI_RECORD_ADDELEMENT: Add an element to a record

BAPI_RECORD_ADDELEMENTS: Add multiple elements to a record

BAPI_RECORD_GETPROPERTIES: Determine properties of a record

BAPI_RECORD_CHANGEPROPERTIES: Change the attribute values of a record

BAPI_RECORD_DELETEELEMENTS: Delete multiple elements from a record

BAPI_RECORD_DELETE: Delete record

BAPI_RECORD_GETLIST: Determine a list of records

For more information on these BAPIs, see the online documentation.

You can integrate a button into an application to enable the user to navigate directly to a record in the Records Browser. Users can go to an existing record, or create a new record.

Integration is carried out using by the business object RECORD. The integration is easily implemented and is sufficient for most application scenarios. You only have the options for manipulating a record that are offered in the methods of the business object RECORD. You can display the methods of the business object RECORD in the Business Object Repository Browser (transaction code SWO3). In the BOR Browser, choose Basis Components ® Basis Services ® Records Management. The methods contain the calls for the BAPIs named above, and also offer methods for displaying, changing, and searching for records.

You can integrate a button into an application that enables the user to navigate directly to any element within Records Management. The integration is enabled by function modules of the function group SRM_CLIENT. This integration requires more complicated implementation than the integration using the business object RECORD, but is not restricted to displaying records. You can navigate to the display of any element, and you can call all activities that are possible for the element. SAP provides the following function modules:

SRM_START_FRAMEWORK_RFC

This function module starts the Records Management Framework using a concrete element instance. The module is RFC-compatible, but can also be called locally. You can be call a model activity or an instance activity. A model activity is an activity for an unspecified element, for example, Search or Create. An instance activity is an activity for a specific element, for example: Display, Change, Delete.

SRM_START_FRAMEWORK_NEWMODE

This function module is identical to SRM_START_FRAMEWORK_RFC except that the element is displayed in a new session.

CL_SRM_START_FRAMEWORK

This class is the API with the most functions. You use this class in two situations:

• The current Records Management Framework is already required for selecting the element to be displayed. Example: The user selects the element to be displayed in dialog. Input help is offered in the dialog box.
• You want to set context parameters for displaying an element (prerequisite: The service provider to which the element belongs supports context parameters).

For more information on both these function modules, and the class, see the online documentation.

You need to implement a new service provider if you want to integrate entities in records that cannot be integrated using service providers supplied by SAP. Implementing a new service provider enables you to control which activities are offered, whether elements are displayed inplace or in a new session, whether an element-specific authorization check should be performed, and so on.

Information on implementing a new service provider is available in a separate document.