Kontakt

Ansicht
Dokumentation

CRM_NOTIF_COND_ATT - Define Conditions of Subscription Processing

CRM_NOTIF_COND_ATT - Define Conditions of Subscription Processing

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In this activity, you define the conditions that you want to use for creating subscriptions. You can define the conditions depending on the business object type (BOR object). In the standard, you can use every field that is available in the following segments:

  • ORDERADM_H
  • ACTIVITY_H
  • CUSTOMER_H
  • SERVICE_H
  • SALES
  • STATUS
  • SRCL_H,,
  • APPOINTMENT
  • PARTNER
  • SRV_REFOBJ
  • SRV_SUBJECT
Note
Only header segments are supported.

If required, you can enhance the standard delivery.

  • You can use other fields contained in the segments mentioned above. The standard classes process these fields as well. Note that you have to implement input helps for these additional fields.
  • You can use customer-specific tables or segments. In this case you have to adjust the standard processing.
Example
For organizing your service help desk, you have defined tables containing components to group the different areas for which you provide services. In this Customizing activity, you can reference to these tables and make the related fields available in an input help.
Note
In the standard system, you can define conditions for service request transactions only (BUS2000223).

A sample implementation is available in the standard system. The sample implementation class CL_CRM_NF_CORE_OTYP_HNDL_1O compares the values of a one order object with the subscriptions in the shared memory. If a condition is fulfilled, it fills the queue table with the relevant entries.

The sample implementation provides also input helps for main segments of BUS2000223.

  1. Enter the business object type. We recommend copying standard entry BUS2000223.
  2. Enter class CL_CRM_NF_CORE_OTYP_HNDL_1O or your customer-specific handler class.
  3. Decide about sending a notification when subscription is changed.
Set the entry to active if you would like the system to send out a notification to all subscribers in case the Subscription is changed.
  1. Select your entry and choose Notification Filters.
  2. Enter the table in which the field is located that you want to use as condition.
  3. Enter the technical field name.
  4. If required, enter the logical criteria. For example, if you want to use the partner as condition, you have to enter the partner function.
  5. In field Description, enter the name that is to be used in the input help of the condition.

If the standard implementation does not meet your requirements, you can implement customer-specific methods.

Example
  • Implement a customer-specific comparison of one order object values with the entries in the shared memory

  • Provide customer-specific input helps

Inherit a customer-specific class (recommended)

  1. Create a new class inheriting from class CL_CRM_NF_CORE_OTYP_HNDL_1O.
  2. Redefine the methods that you want to change.
  3. If you want to execute the standard code, call the super method.
  4. Add your customer-specific enhancements.

Note
If you create a new input help (IF_CRM_NF_API_REF_BOR_HNDL~GET_F4_VALUES) for conditions, consider that the called method is concatenated (GET_VAL_ + ui_fieldname (customizing)). This applies also to method IF_CRM_NF_API_REF_BOR_HNDL~GET_OPERATORS.

Creating a customer-specific class

  1. Create a new class that implements interface IF_CRM_NF_API_REF_BOR_HNDL.
  2. Implement the following interface methods:
  • PERFORM_COMPARISON

The method compares a business document (BDoc) with the filters of a notification document. If the BDoc data meets all filter criteria, the method returns true.
  • BUILD_SEGMENT_KEYS

The method specifies the logical key for each BDoc segment.
  • GET_F4_VALUES

The method determines a value help or dropdown box (ddlb) for each filter criteria available on the UI.
  • GET_OPERATORS

The method determines the select option value for each filter criteria available on the UI.
  • CHECK_FILTERS

The method performs specific checks if the filter conditions can be handled





Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 5709 Date: 20240523 Time: 162604     sap01-206 ( 68 ms )