The Service Implementation Workbench (SIW) offers a single point of entry for you to create, implement, and recreate enterprise services quickly and easily in a semi-automated and guided process to ensure reusability of business functionality.
The SAP Application Interface Framework provides you with an SIW configuration and template. You can generate SAP Application Interface Framework relevant objects and data entries via SIW in different system landscapes. In the SAP Application Interface Framework, you can use the delivered SIW configuration to integrate with ECH (see Error and Conflict Handling Integration).
You require authorization for the following 3 authorization objects:
S_CTS_ADMI
S_CTS_SADM
S_SIW_CFG
You must define the SIW system landscape and configuration.
The SIW template delivered with the SAP Application Interface Framework supports you in generating many of the objects needed for an SAP Application Interface Framework interface. For example, the following objects can be generated with the template:
Proxy class implementation
Interface definition
Action
Action function
SAP data structure
In order to guarantee flexibility and scalability, the custom SIW configuration does the following:
Supports both bulk and single service
Supports both synchronous and asynchronous
Provides all the needed context variables
Provides one template for above mentioned functions
Is able to inject Customizing entries into transport request
In SIW, a project is created based on a configuration defined for the proxy-based creation type. On the SIW Project Creation Screen
, there is an SAP Application Interface Framework-specific creation sub-screen for proxy-based services where an interface developer
can enter the following key variable values:
Prefix
Used for all repository objects generated with the SIW
Package
The package storing generated objects
Function group
Contains the generated action function module
Namespace / interface name / interface version
The AIF interface keys. The namespace is not generated by SIW, but must be defined in advance.
Interface description
Action
The AIF action used by the AIF interface. The generated action function module is assigned as a function of this action.
Action description
After the project is created, the Project Implementation Screen
is displayed. Here, you enter the project-specific context data, for example, the SAP data structure name used for DDIC structure generation. You specify the function module or BAPI that should be
called in the action function. The SAP data structure is generated to fit this function module’s or BAPI’s parameters. Interface developers can define their SAP Application Interface Framework interface via the context variables.
Once all the required context variables are correctly maintained, a service developer can generate the following:
An implementation based on the existing proxy class
DDIC objects, for example, table type and structure
An SAP Application Interface Framework-specific action function module, as well as generate code snippets for the action function module
Basic Customizing data for the SAP Application Interface Framework, for example, interface definition
For more information about SIW, see the SAP Library for SAP NetWeaver 7.0
.