Google+ SAP CRM Mobile Scenario in Customer Relationship - SAP ABAP

SAP CRM Mobile Scenario in Customer Relationship

The mySAP.com application part for Customer Relationship Administration consists of a central CRM server and numerous extensions to assist other ways of accessing the system. It also allows for connecting to different systems. Relying in your actual enterprise requirements, not all extensions should be installed or used.The CRM application element is known as the CRM part which suggests the sum of all CRM functionality. CRM system is used when addressing questions of information transfer to and from the central CRM server or set up configuration options.The CRM element can be accessed by means of the mySAP Office by CRM customers reminiscent of gross sales managers or contact center agents.Internet customers could configure and order services or products using the Web elements of the CRM software component.The cell sales force or cellular service engineers can connect with the system from their laptops or pervasive gadgets to alternate the newest data with the CRM component.Finally, prospects could use the phone, fax, or electronic mail to succeed in the sales or service representatives using the integrated contact center solutions.

The CRM part supports the handling of CRM enterprise objects, like prospects and prospects, activities and opportunities, merchandise and product catalogs in quite so much of application elements like Web Sales, Service Interplay Center, Telesales, Marketing campaign Administration and various others.Some of these elements want exterior extensions for communication or integration purposes, e.g. an Web Transaction Server (ITS) for the Web Gross sales component.The middleware layer primarily helps the controlled knowledge change with other programs, i.e. cellular clients, back end methods and data warehouses. The connections to external programs are established through software program adapters. The adapters map and convert knowledge to varied formats. The CRM application components additionally trade knowledge with the middleware layer through a CRM adapter.

The CRM part is constructed on the SAP Basis system, which offers a proven growth platform, scalability, platform independence, and various other R/3 tools. Due to this fact a CRM system will be configured in the identical versatile way as an R/3 system.The Mobile Sales and Mobile Service elements of CRM help a company’s cell sales pressure and cell service engineers respectively, providing full entry to all the required information on laptop computer computers. This data is stored up to date by regular data change using the middle ware part contained on the central CRM Server.CRM Cellular Gross sales and Service customers carry a full-blown PC application together with a local database on their laptops. They connect with the CRM Server every so often via phone or network to exchange information gathered and saved in queues at both ends. This connection is established via a Communication Station, the place DCOM calls from the cellular purchasers are reworked to RFC calls that go to the CRM Middleware.

Mobile Clients : normally laptops operating the Cell Sales/Service application (consumer) software,which can include the Gross sales Configuration Engine (SCE) and the Sales Pricing Engine (SPE).Cellular purchasers sometimes connect temporarily (e.g. by way of modem) to the CRM Server for knowledge exchange.They could also be permanently connected to the server. n CRM Server / Middle ware : the CRM Server accommodates the CRM Middleware, which is the center of the cellular scenario. It handles communication with the purchasers, information consolidation in the Consolidated Database (CDB), data exchange with other methods, administration etc. The CRM Server is built upon an SAP R/3 Basis system.

Mobile Clients

The Cell Gross sales/Service consumer accommodates the complete software software program needed for offline data entry and processing, in addition to the Transaction Layer, which is the middleware component wanted for knowledge change and communication with the CRM Server. The transaction layer additionally serves as the interface to the local database.Additional middleware components on the shopper are:
  1. The Connection Service , which handles the precise connection to the CRM Server and calls one or extra switch services.
  2. The Message Transfer Service , which handles the info alternate between the client and the CRM Server. Another transfer service may be, for example, a MAPI service (Microsoft Messaging Application Programming Interface).
CRM Server

The CRM Server is scalable similar to any standard R/3 system. It is built on high of an R/3 Basis system however as a substitute of the R/3 core purposes, it contains the CRM on-line elements, the CRM Middleware and the Consolidated Database.The R/3 Basis system gives SAP foundation technology and the ABAP workbench as a improvement environment recognized to many application developers.An necessary part of it's the replication and realignment service , which ensures that all Mobile Sales/Service users get hold of the info they require.The Consolidated Database (CDB) has a number of benefits like

Information misplaced on a laptop computer might be reloaded from the CDB.Special CRM knowledge, e.g. exercise or opportunity knowledge, is simply saved in the CDB and never within the database of the OLTP R/3 system.The efficiency, particularly of the realignment service, depends heavily on the supply of the info on the CRM Server.

BDoc messages inside the CRM Middle ware are the biggest unit of knowledge that can be handled. They characterize the usual format for data alternate between mobile shoppers and the CRM server.Definitions of all BDoc types are contained within the BDoc repository.

BAPIs: normal R/3 interfaces that allow you to integrate third-occasion software program into your R/3 System. They are outlined in the Business Object Repository (BOR) as methods utilized to SAP business objects in an effort to carry out particular business tasks.The replication mannequin consists of publications and subscriptions for certain replication objects. Note that the replication mannequin also accommodates replication objects and circulation definitions. Websites (cell purchasers) subscribe to publications via subscription rules, e.g. number ranges for replication-relevant fields.Information realignment is a redistribution of information that ensures that each one websites receive the information assigned to them via subscription. A minor realignment is triggered by modifications to data, and a significant realignment by adjustments to subscriptions.

Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
My SAP Project safety and security

No comments :

Post a Comment