SAP ABAP Data Element SIW_DTE_SERVICE_LEVEL (SIW Service Creation Type)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-ESI-SIW (Application Component) Service Implementation Workbench
     ⤷ S_SIW_TYPES (Package) SIW: Global Type definitions
Basic Data
Data Element SIW_DTE_SERVICE_LEVEL
Short Description SIW Service Creation Type  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SIW_DOM_SERVICE_LEVEL    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Crt. Type 
Medium 15 Creation Type 
Long 25 Service Creation Type 
Heading 21 Service Creation Type 
Documentation

Definition

Indicates how the service development process takes place.

Use

Service Implementation Workbench (SIW) differentiates between the following service creation types:

  • API-based (without Service Repository) (Value 0)

    In this service creation process, an application programming interface (API) in the backend system is the basis for the service to be created. You use SIW to create a web service in form of a virtual interface in the backend system, in addition to the functionality provided by the ABAP workbench for function modules that are RFC enabled.

  • API-based (with Service Repository) (Value 1)

    In this service creation process, an application programming interface (API) in the backend system is the basis for the service to be created. You use SIW to derive a Service Repository service definition that corresponds to the API signature, to create the corresponding proxies, and the service implementation in the backend system.

  • Proxy-based (Value 2)

    In this service creation process, you manually define a service definition outside SIW in the Service Repository (such as Enterprise Service Repository or Meta Data Repository). You then use the transaction SPROXY to create the corresponding proxies in the backend system. Thereafter, you use SIW to create the service implementation in the backend system.

  • Other, not service-related (Value space)
    SIW can also be used for defining projects that do not represent SOA use cases. No services or proxies will be generated in this scenario, but only the backend objects as defined by the configuration class.

Dependencies

Example

History
Last changed by/on SAP  20110908 
SAP Release Created in