Ansicht
Dokumentation

CRM_OPPORT_MAPPING - Data Matching for Reason for Status With CRM Mobile

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

So that data matching regarding the reason for status can take place between the CRM system and CRM Mobile, you must make specific settings in Customizing. In the standard, Customizing in both systems is preset to allow correct data matching. For this reason, SAP recommends that you use the standard settings.

If, however, you want to modify the settings, please note the following rules for data matching regarding the reason for status:

The status in the CRM system corresponds to the result in CRM Mobile; the codes that you determine in Customizing for the CRM system correspond to the reason in CRM Mobile. In CRM Mobile there is no user status profile as there is in the CRM system.

Assign to a catalog/code group/code the key that you set for the reason in CRM Mobile. Note that the content of the code in the CRM system and of the reason assigned in CRM Mobile must correspond (for example, if the settings in the CRM system say "won because best product functionality", the reason assigned in CRM Mobile should not say "lost").

Careful!
SAP recommends that you use only one user status profile in the CRM system, as in CRM Mobile all statuses included in the user status profile would appear under result.

ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 1434 Date: 20240523 Time: 180410     sap01-206 ( 40 ms )