Ansicht
Dokumentation
CRM_OPPORT_MOBILE - Data Matching With CRM Mobile
ABAP Short Reference ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
In order to enable a correct data exchange with CRM Mobile, you must be sure to note specific rules in the CRM system and CRM Mobile, regarding the Customizing settings.
In the standard, Customizing is already set in both systems so that correct data matching is possible. SAP therefore recommends that you use the settings in the standard.
If, however, you wish to modify these settings, be sure to note the following rules and notes:
Equivalence of names of specifc fields:
The keys for the following fields must be the same in both systems:
- Business transaction type
- Opportunity group
- Priority
- Origin
- Phase
Example:
If you have chosen the key OPPT for the business transaction type opportunity in Customizing in the CRM system, you must also set the key OPPT for the business transaction in CRM Mobile.
In CRM Mobile, you make the settings for the above mentioned fields under System --> Selection Fields.
Caution!
In the CRM system, it is possible to define different sales cycles. You
can define different phases to a sales cycle (for example, a sales cycle consists of the phases Preselection, First Contact, Presentation and Contract Phase). In CRM Mobile, there is no sales cycle.
If you defined several sales cycles with different phases in Customizing in the CRM system, correct
data matching is not possible. The result here would be that all the phases set in the CRM system are
listed from all sales cycles in the CRM Mobile. For this reason, SAP recommends that you only define
one enterprise-wide with specific phases. If you wish to work with several sales cycles in the CRM system, you should always use the same phases within the sales cycles.
Data matching for reason for status
Note the following rules for data matching regarding reason for status.
The status in CRM corresponds to the result in CRM Mobile; the codes which you define in Customizing for the CRM system correspond to the reasons in CRM Mobile. Unlike in the CRM system, there is no user status schema in CRM Mobile.
In order that data matching can be carried out here, there is a table for the CRM system in Customizing. You can find this table in Customizing under Customer Releationship Management --> Transactions --> Settings for Opportunities --> Reason for Status of Opportunities --> Data Matching for Reason for Status with CRM Mobile.Here, you can assign the key to a catalog/code group/code, which you have set for the reason in CRM Mobile. Make sure that the code in the CRM system and the reason assigned in CRM Mobile match each other in contents (for example, if the settings in the CRM system is scheduled as "won due to best product functionality", then the reason assigned in CRM Mobile should not be scheduled as " lost").
Caution
SAP recommends that you only use a user status schema, as all the statuses contained in the user status schemas in CRM Mobile would appear as a result.
Specific rules for data matching in partner functions
As CRM Mobile does not use the same partner functions as the CRM system, you should note some rules in this area.
Naming of the keys for business partner role (CRM system) and role (CRM Mobile)
The role in CRM corresponds to the business partner role (for example, employee, sold-to party, competitor and so on) in the CRM system. Data matching takes place between these two objects. The key for the role in CRM Mobile has 6 characters, whereas the key for the business partner role in the CRM system has 8 characters. For data matching from CRM Mobile to the CRM system, a zero is added from the adaptor on the second and third position of the key.
Example:
The key for the role in CRM Mobile is XKEYAC
This key is first transferred to the adapter and then to the CRM system. A zero is added at both the second and third position.
The key X00KEYAC appears in the CRM system.
For data matching in the other direction, that is, from the CRM system via the adapter to CRM Mobile, the zeros are left out again at the second and third position.
Note the following rules in this case:
In Customizing in the CRM system, add a zero at the second
and third position (the first position is always reserved for the customer namespace). Also make sure that you use the same name for the other positions in both systems.
Example: Business partner role "Key account manager"
CRM System: X00KEYAC
CRM Mobile: XKEYAC
Notes
In CRM Mobile, the role is set under System --> Relationship Types. See also the documentation for CRM Mobile.
Partner role matching
At the moment, CRM is not using the same concept for business partners as for the general business partner in the CRM system. In CRM Mobile, a role must be assigned to exactly one of the following three objects:
- Business partner
- Contact person
- Employee
A partner role can always only be assigned to exactly one object. This means that, for example, the partner role "contact person" can only be assigned to the object contact person.
In order that correct data matching between the two systems is possible, you can only use business partners in CRM which are assigned to one of the above mentioned objects in CRM Mobile.
In Customizing in the CRM system, you set the possible business partner roles for a business transaction type in the business partner determination procedure. This business partner determination procedure is then assigned to the corresponding business transaction types for opportunities.
The following table displays business partner roles which are set for the business transaction type opportunity (OPPT) in the standard in the partner determination procedure for opportunities, and the corresponding object in CRM Mobile to which these roles refer:
| CRM system: business partner role | object in CRM Mobile | |
|---|---|---|
| Sales representative | employee | |
| Contact person | ||
| Sales prospect | business partner | |
| Person responsible | employee | |
| Competitor | business partner | |
| Sales partner | business partner |
Caution
Only use the business partner roles in the CRM system in the same way as they can be used in CRM Mobile, according to the object assignment.
Example:
If, when creating an opportunity in the CRM system, you enter a person responsible on the
Partner tab page, this partner role must be from the employee category and not an organizational unit (which would be possible in the CRM system), in order to enable a correct exchange.
Partner number matching
Make sure that the partner number in the CRM system is not identical to the customer number in R/3 and the customer number in CRM Mobile, although all have the same partner. Here, the system carries out data matching automatically.
Matching personnel numbers for employees
The employees' personnel numbers must be identical in CRM Mobile and the CRM system.
You set the personnel number in the CRM system in the business partner record for the role employee on the Control tab page. Here, the user name is also defined for logon to the system.
You set the the personnel number under Employees --> Details in CRM Mobile. You maintain the user name and password for logon in CRM Mobile in the administration console for Middleware (see also the documentation administration and monitoring in the SAP Library under Middleware).
Data matching for attachments and texts
At the moment, it is not possible to exchange attachments or texts which were added to opportunities between CRM Mobile and the CRM system.
BAL_S_LOG - Application Log: Log header data rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 9535 Date: 20240523 Time: 161712 sap01-206 ( 187 ms )
