Ansicht
Dokumentation

ISUWA_BASIS_00000002 - Define Category of Service Type for Service Product Subitem

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Define category of activity type for a service product subitem

Now that you have activated the controlling cockpit for waste disposal orders, you will now define the subitem types that are used later in the other CO integration settings in this step.

You should choose a similar definition of the CO-relevant subitems as the one defined in the design of the service products.

You have a service product with a main item ISUWA_SP01 and the following subitems:

• ADDSERV1_MAT

• RENTAL_MAT

• TRANSPORT_MAT

• WASTE_MAT

In this case, it would make sense to make the following allocations in the CO-relevant Customizing:

• ADDSERV1

• RENTAL

• TRANSPORT

• WASTE

You should then use these settings so that the search strategy tables can be allocated semantically.

For example, when maintaining the CO data for the waste disposal order item (transaction EWACO04), the settings would be as follows:

Field name	Value
Service object	ISUWA_SP02 (service product)
Service type	01
Material	ISUWA_TRANSP
Valid from	01/01/2007
Sequence number	1
Activity type	FZGKM
Activity qty	0.000
Activity unit
Total price	0.0000
Currency	EUR
Sender cost center category	Vehicle
CO activity type	TRANSPORT
Plant
Valid to	12/31/9999
Field name	ZPOSDAUER

The service product definition specifies that subitem ISUWA_TRANSP_MAT is TRANSPORT. This defines the activity output type. The purpose of these settings is to design the corresponding service product items and their basic type flexibly.

It is also possible to group several related CO activity type allocations if there is more than one CO activity type-relevant allocation for ONE service product subitem.

Please see the notes on the search strategy mapping tables in the documentation.

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3419 Date: 20240523 Time: 160643     sap01-206 ( 36 ms )