SAP ABAP Data Element BS_SOA_SIW_DTE_SERVICE_TYPE (Service operation type)

Hierarchy

☛ SAP_BS_FND (Software Component) SAP Business Suite Foundation
   ⤷ CA-SOA (Application Component) Enterprise SOA
     ⤷ BS_SOA_REUSE_COMMON_OBJECTS (Package) Business Suite SOA: Reuseable Tools and Objects

Basic Data

Data Element	BS_SOA_SIW_DTE_SERVICE_TYPE
Short Description	Service operation type

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	BS_SOA_SIW_DOM_SERVICE_TYPE
Data Type	CHAR	Character String
Length	16
Decimal Places	0
Output Length	16
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	op type
Medium	15	operation type
Long	30	service operation type
Heading	30	service operation type

Documentation

Use

For synchronous inbound services, you have the following options:

• Create

  This pattern is used for service operations that creates a new object in the service provider's backend. It includes the Commit/Rollback logic and the idemptoency framework.

• Change

  This pattern is used for service operations that change a object in the service provider's backend. It includes the Commit/Rollback logic, activation of extendedXML during inbound processing and the idemptoency framework.

  From the SIW perspective this is the same as the Update type. The differences between these pattern are recognized in the coding spots.

• Update

  This pattern is used for service operations that change a object in the service provider's backend. It includes the Commit/Rollback logic, activation of extendedXML during inbound processing and the idemptoency framework.

  From the SIW perspective this is the same as the Change type. The differences between these pattern are recognized in the coding spots.

• Cancel

  This pattern is used for service operations that cancel an object in the service provider's backend. It includes the Commit/Rollback logic, and the idemptoency framework.

  From the SIW perspective this is the same as the Create type. The differences between these pattern are recognized in the coding spots.

• Single Read

  This pattern is used for Query operations that responds with at most one business object. This is typical for Read services.

• Multiple Read

  This pattern is used for Query operations that can respond with more than one business object. This is typical for Find services.

• Create Check

  This pattern is used for service operations that checks the creation a new object in the service provider's backend.

  You can also use this pattern for Cancel Check.

  You might use the re-use indicator to use the same service implementation class as for the corresponding service of operation type Create.

• Change Check

  This pattern is used for service operations that checks the changing of an object in the service provider's backend. It includes the activation of extendedXML activation during inbound processing.

  From the SIW perspective this is the same as the Update Check type. The differences between these pattern are recognized in the coding spots.

  You might use the re-use indicator to use the same service implementation class as for the corresponding service of operation type Change.

• Update Check

  This pattern is used for service operations that checks the updating of an object in the service provider's backend. It includes the activation of extendedXML activation during inbound processing.

  From the SIW perspective this is the same as the Change Check type. The differences between these pattern are recognized in the coding spots.

  You might use the re-use indicator to use the same service implementation class as for the corresponding service of operation type Update.

Dependencies

Example

History

Last changed by/on	SAP	20110908
SAP Release Created in