SAP CRM Middle ware Enhancement

SAP CRM Middle ware Enhancement overview with a objective to add certain functionality to the Cellular Gross sales application, it could be very important perceive the processes involved in dealing with this functionality. Once that is understood, a stepwise implementation might be achieved on the varied parts involved in a cellular scenario.The info mannequin is normally an extension of the present Cell Gross sales/Service information model. If the processes are to be integrated with an OLTP R/3 system, and knowledge buildings exist already there, the information model extension should take this into account. n The functionality meant to be realized on the mobile Client is then applied utilizing the mobile Application Studio.

Modify the table with the ABAP Editor within the ABAP Dictionary (DDIC) on the CRM server.Export the modified knowledge model to the BDoc Modeler and the Cellular Application Studio. Modify the BDoc definition via the external BDoc Modeler (VB software).Modifications are saved instantly within the CRM Middle ware and the development station.Certain buildings and program code are generated from meta-stage information.Solely the meta-degree data is transported to different systems.Activation of repository objects through after-import methods and era on the R/3 vacation spot systems.

The Mobile Application Studio modifies the Consumer Interface Layer (UL) and the Business Object Layer (BOL) objects on the cellular client.Modified objects are regionally saved in change lists.Change lists are uploaded to the CRM server.Run time objects which may be generated from the change lists are replicated to the mobile purchasers via the normal replication mechanism.

Customizing Overview

Typical customizing steps are:
  1. Definition of a table within the CRM Middle ware DDIC that corresponds to an current table on the OLTP R/3 system.
  2. Copying the table definition from the DDIC into the dictionary of the BDoc repository (SFADDIC in the CRM Middle ware and on the event station) utilizing the RepGuardian tool.
  3. Creation and activation of a new BDoc type to trade the contents of the brand new desk between the CRM Middle ware and the mobile clients.
  4. Definition of a course of stream on the CRM Middle ware for the new BDoc type.
  5. Definition of the replication mannequin together with a replication object and a quantity of publications in order to replicate the BDoc messages to the cell clients.
  6. Configuring the R/3 Adapter in the CRM Middle ware to be able to fill the new desk with information from the OLTP R/3 system.
Additional customizing prospects :
  1. Using customizing exits for the upload and delta obtain of business objects.
  2. Present your personal services.
  3. Define your personal flow.
Data Model

Knowledge must be mapped earlier than or during add/download when being exchanged with the OLTP R/3 system.The CRM Middle ware knowledge model just isn't a 1:1 copy of the R/3 data model. Solely related data buildings seem within the CRM Middle ware data model, enriched by sure additional tables and fields to model further performance as Mobile Gross sales has market-specific wants for different industries (Pharmaceutical, High Tech and Client Goods Trade).Generally R/3 tables within the CRM Middle ware are prefixed with SMO.Some important improvement lessons are:
  1. SMOF (R/3 Adapter service)
  2. SMOG (CRM Middle ware Repository companies)
  3. SMOH (Replication & Realignment service)
GUIDs (Globally Unique Identifiers) function main keys for all tables in the CDB. A GUID is generated by a particular algorithm using as enter knowledge sure hardware information of the host laptop, the present system time, and a randomly generated number. The GUID might be represented in varied codecs; for CRM a 32-byte character sequence is used. It's globally unique within the sense that two GUIDs produced on any two computer systems (and even on the same one) at any time can by no means be the same.Major keys of all tables are known as SFA, corresponding to SFAKNA1, SFAMARA.

Repository and Generation

The CRM Middle ware repository accommodates all meta information associated to the CRM Middle ware. It consists of the:
  1. R/3 Adapter repository
  2. Movement repository
  3. BDoc repository
  4. Replication repository
  5. ASCII Adapter repository
The metadata contained within the CRM Middle ware repository is used to generate run time objects in the CRM Middle ware runtime repository. These are either table entries or runtime objects stored in the R/3 repository.Movement definitions are generated within the run time repository from the flow variants contained in the circulate repository.

R/3 run time objects are generated from the metadata contained in the BDoc repository.BDoc metadata is maintained by the BDoc Modeler.The generated runtime objects are used to process BDoc messages.R/3 runtime objects are generated from the metadata contained in the replication repository. Replication metadata is maintained by the Administration Console.The generated runtime objects are used to implement the replication and realignment service.

The various repositories in a mobile scenario are:

On the CRM Server the Middle ware services repository (incorporates the R/3 adapter repository, replication repository,Circulate repository and the ASCII adapter repository) the BDoc repository the ABAP knowledge dictionary . On the Mobile Repository Server the appliance repository (ars_db) the BDoc repository (trrep) the IDES database (ides).These repositories are modified by the next instruments:
  1. the Administration Console (solely server repositories)
  2. the Cell Utility Studio (solely client repositories)
  3. the BDoc Modeler (both server and shopper repositories)
  4. the SAP GUI (solely server repositories)
The take a look at client and the transport providers only exchange data with the shopper repositories.Software program growth in cell situations affects the five repositories listed above. They are all located on the CRM Server and/or the Cellular Repository Server.The brackets comprise the default names of the databases on the cellular repository server that maintain corresponding repositories.Because the BDoc repository has its own information dictionary (SFADDIC), objects created in the ABAP dictionary (DDIC) should be copied to this BDoc repository dictionary.Every object have to be copied twice, as quickly as to the BDoc repository on the CRM Server and once to the BDoc repository on the Cell Repository Server.The RepGuardian, a device located on the event station, is used for this purpose.

Related Posts

SAP CRM Organizational Model
Customer Relationship Management and mysap an introduction
CRM Management and sales and service strategy of mysap crm
MySAP CRM and customer as business partner

No comments :

Post a Comment