Ansicht
Dokumentation

CRM_CIC_065 - Define Calling Times Mapping Profiles

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

In this IMG activity, you define call list and business transaction calling times mapping when used for business transaction synchronization. Business transaction synchronization allows you to use data from call lists to update the associated business transaction, and vice versa, when data is saved. Post Processing Framework (PPF) technology is used for the basis of the synchronization. You define when the synchronization occurs in define action profiles and actions.

Call lists and business transactions have their own defined calling times which are maintained and used in each separate application, so changing one value in one object will not simply select the same value for the other object. You must define which values from one object are equivalent to which values in the other object. You map the call list attribute to a date type defined in the business transaction profile. The call list and business transaction attributes are already created. You only have to map the attributes to one another. This mapping is on a one to one basis only.

The separate use of calling times has no effect on call lists that are not associated to business transactions, however, most call lists are associated to business transactions.

The following process is used for synchronizing calling times:

1. The user changes a calling time on either the call list or business transaction.
2. The PPF starts and determines when and if the synchronization starts.
3. The system determines if the calling times need to be synchronized.

The system looks at which date profile the business transaction is associated to and reviews the corresponding entries in this customizing table if one exists. It uses the attribute you changed, on either the call list or the business transaction and determines if the attribute is mapped.

• If the attributes for the call and the business transaction are not mapped, then no synchronization occurs.

• If the attributes for the call and the business transaction are mapped, the system checks to see if the attribute values are the same or different.

- If the values are the same, then no synchronization is needed.

- If the values are different, then the synchronization is needed.

The system changes the value in the object that the user did not change. For example, if the user changed a call, and if synchronization is needed, the system updates the business transaction.

Business transaction date profiles are created.

The following attributes are mapped:

Date Profile	Call Attribute	Appointment Type	Appointment Attribute
000000000001	Complete By	ORDERPLANNED	Timestamp To
000000000001	Start On	ORDERPLANNED	Timestamp From

A user changes the Complete By date on a call from 07/07/06 to 07/10/06. (The user did not change any information on the business transaction. The Timestamp To field has value of 07/07/06.)

The system checks if the business transaction synchronization needs to occur. It sees that the 000000000001 date profile is associated to the business transaction and uses the corresponding entries. The business transaction Timestamp To attribute is mapped to the Complete By attribute, so the system checks if the attribute values are the same or not. The current values are 07/10/06 for the call and 07/07/06 for the business transaction. Since the values are not the same, the system triggers the synchronization.

The system updates the Timestamp To field on the appointment type ORDERPLANNED to 07/10/06, so it is now in sync with the Complete By field on the call.

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4719 Date: 20240523 Time: 152232     sap01-206 ( 86 ms )