Ansicht
Dokumentation

CRM_UBB_DFA - Define Analysis Views

CRM_UBB_DFA - Define Analysis Views

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you define analyzer views for the transaction analyzer. Using these analyzer views you can control how transactions are displayed in the transaction analyzer.

Assigning Business Object Type/UI Object Type

When you assign business object types to UI object types, you define the configuration that is displayed in the CRM WebClient UI. The configuration dictates the layout of the header details and item details, as well as the selection of assignment blocks on the overview page. The UI object types must have been created previously.

Evaluation Paths

The evaluation path also influences the number of transactions that are displayed. You use the evaluation path to determine which transactions, such as predecessor or successor transactions, are displayed in the analyzer view.

Excluding Transaction Types

In this view, you can specify the binary-linked transactions in a specific transaction category that you do not want to be displayed in the analyzer view.

Excluding Item Categories

In this view, you can specify item categories that you do not want to be displayed in transactions that are linked together with change processes in the transaction flow.

Type of Binary Relation - Transaction

In this view, you specify the type of binary relation for relationship type VONA for transactions. For example, you can specify that only leasing contracts, and not leasing quotations, are displayed in the analyzer view for the header view; you do this by selecting Link Without Data Transfer and Without Update. For a leasing view, we recommend that you select at least the entry Link with Data Transfer and Update. For a usage-based billing (UBB) view, we recommend that you select both Link with Data Transfer and Update and Link Without Data Transfer but with Update.

Type of Binary Relation - Item

You use this view to enter the type of binary relation for relationship type VONA for the items. For a leasing view, we recommend that you select at least the entry Link with Data Transfer and Update. For a UBB view, we recommend that you also select the entry Link with Data Transfer and Without Update.

Status Conditions - System Status

In this view, you determine the system status that an item must have in order to be displayed in the item overview. If the indicator Inactive is set, the item status must be inactive in order to be displayed. Otherwise, it must be active. If the indicator Filter is set, the status condition for both the item overview and the hierarchy display is taken into account. This means that you can also influence the displaying of items in the hierarchy display using status conditions.

Status Conditions - User Status

In this view, you determine the user status an item must have to be displayed in the item overview. If the indicator Inactive is set, the item status must be inactive in order to be displayed. Otherwise, it must be active. If the Filter indicator is set, the status condition for both the item overview and the hierarchy display is taken into account. This means that you can also use status conditions to influence the display of items in the hierarchy display.

Segments to Read

You can use this view to activate or deactivate datasets according to whether or not you want the analyzer view to read the data. We recommend that you deactivate datasets when they are not relevant for the analyzer view, as this will improve the performance of the transaction analyzer.

Example:When you define an analyzer view for service contracts for usage-based billing (only UBB service contracts), deactivate segment FINPROD_I. This segment has no impact on the display of the transaction flow of a pure UBB service contract.






Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4822 Date: 20240523 Time: 181844     sap01-206 ( 101 ms )