SAP CRM MW Badi
§1. For all data flowing from crm to mobile – can be enhanced using Mobile Bridge badi called – CRM_30A_USER_EXITS
§For sales order data flow from CRM to R3 can be enhanced using Badi CRM_DATAEXCHG_BADI
§For data exchange of Product from R3 to CRM can be exchanged using badi - PRODUCT_CUSTOMER*
§In case CRM data needs to be uploaded to custom table or other application then Bdoc flow can be enhanced using transaction SMW3FDCUST.In order to investigate such development – break point needs to be set up at FM SMW3_flow_SERVICE_EXECUTE.
Integrating HR with CRM - I
§HR can be used as a Lead System to maintain employee and Organizational structure. The same data can be passed back to CRM . Such integration between HR and CRM is done through ALE – Message Type “HRMD_ABA “. .
§External number range needs to be set up in CRM for employees.
§Along with ALE setting table T77S0 needs to be maintained for the data flow between SAP CRM and HR using SM30. After activating the switches HRALX-HRAC = 'X' and HRALX-PBPHR = 'ON', the ALE integration between HR and CRM is Activated. You can no longer manually create or change Business Partners in the Role BUP003 (Employee) in CRM. They must be maintained as HR employees first and then replicated via ALE.
§The program HRALXSYNC enables you to run a consistency check for the integration of HR Master Data and Business Partner data and must be setup as a background job as part of the ALE integration between HR and CRM
Integrating HR with CRM - II
Creating a middleware enabled application
§This example is intended to provide a real life hands on scenario on using the CRM middleware for application data exchange
§The model used can be broadly followed in majority of the cases, including where mobile applications are used
§It covers the creation of sBDoc type and mBDoc type, creation of mapping modules and of writing a Mobile Bridge.
§The design of a CRM application must be such so as to separate the user interface from the business logic, and the business logic from the transaction handling.
Designing the CDB & mbdoc data type
§The CDB table used for storing MSA relevant data is created in data dictionary (SE11)
§The complex data type used in the mbdoc is then created in data dictionary
No comments:
Post a Comment