Kontakt

Ansicht
Dokumentation

CRM_CIC_066 - Define Call State Mapping Profiles

CRM_CIC_066 - Define Call State Mapping Profiles

TXBHW - Original Tax Base Amount in Local Currency   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you define call list and business transaction call state 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 call states 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. The call list and business transaction attributes are already created. You only have to map the attributes to one another. The mapping can be one to many or one to one.

You map the call list attribute to a busines transaction status profile.

The following process is used for synchronizing call states:

  1. The user changes a call state 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 call states need to be synchronized.
The system looks at which status profile the business transaction is associated to and reviews the corresponding entries under Call State Mapping and Alternative Statuses. 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, then the system checks whether 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.
If the user changed the call state on a call, then the system uses the Call State Mapping entries to determine which field or fields are updated on the business transaction. If the user changed the business transaction call state, then the system uses the Status Mapping entries to determine which field is updated on the call.
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 status profiles are created.






CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3245 Date: 20240523 Time: 182123     sap01-206 ( 66 ms )