Logical Service

Use

This concept enables you to process certain objects of Incentive and Commission Management with your own methods. The implementation of the method does not have to be in the same system, and it does not matter whether it is started by a BAPI or an RFC in another SAP system or an external system. The method can also be used to call up an external program such as a non-ABAP program, and to transfer data to it via an interface.

The following graphic shows the link between object type class, tool, object and the corresponding methods and functions.

In the system, object type classes have been defined that are part of the object types implemented there, for example, performance-related remuneration , valuation or liability .

Methods have been defined for these object type classes. These methods describe the type of processing to be carried out. The Calculate valuation has been defined for the Valuation object type class.

You link each of these methods to a function, and assign the tool to an object. The assigned function module is always used during processing (executing a method).

See the List of Logical Services in ICM .

Features

One of the Advantages in Decoupling Object Methods from their Implementation:

Decoupling of the effective from the technical view

For specialist (business) purposes, the program used for executing the methods is not normally important.

Example Example

Likewise, it is also not important if commission is calculated, for example, using the condition technique or a customer function module.

End of the example.

Important for business use is the fact that the interface for maintaining method parameters is as non-technical as possible. The background technology is hidden from the processing clerk. The interface only contains the special parameters that create the link to the program and that can only be maintained by the user. The remaining technical parameters are reserved for the (commissions) system administrator.

Example Example

An important parameter for the condition technique is the procedure used for calculation. This is selected according to business requirements and must be maintained by the user. The access sequence is also relevant for selecting commission records. This must also be specified by the user.

End of the example.

The interface is split according to effective and technical views. The user gets a different view of the object methods and their parameters than that available to the IT department.

Example Example

The user initially does not know anything about the applied program, due to the interface available (unless the tool can be derived from maintaining the specific parameters mentioned above), whereas this information is very important to the IT department.

End of the example.

Logical Service versus BTE method

In the BTE (Business Transaction Events) method, function modules are called up in specified events, to which they have been assigned in Customizing. The event interface is predefined.

The method presented here is similar to the BTE method, but it cannot be replaced by it. Although the object methods are called up for predefined events, the selection of the required function module does not depend on the event, but upon the object itself.

Example Example

You need to call up a function module for the Remunerate Remuneration Type event for the Acquisition Commission object, other than the one used for the Commission on In-Force Business Maintenance object. The BTE method would only enable you to call up a function module for all objects at this point.

End of the example.

Activities

If you want to create your own tools, see Creating Customer Tools for more information.

If you want to use logical services for the following objects, assign them to the corresponding tools in Customizing.