Google+ SAP CRM Middleware for Mobiles Replication - SAP ABAP

SAP CRM Middleware for Mobiles Replication

SAP CRM Middle ware for Mobiles Replication needs information Sharing has Download: Solely part of the R/3 information is downloaded to the Consolidated Database (CDB),e.g. no controlling data.Upload: Solely a half of the information in the Consolidated Database is uploaded to R/3,e.g. no opportunity data.Each of the local databases contains only the info which the user of this explicit local database wants normally partly R/3 information and partly non-R/3 data. The native databases can differ in their size,can overlap and might contain each other. They symbolize mirrors of parts of the CDB.No pair of concerned databases is normally identical.Data replication can be defined as the problem of figuring out the receivers for a particular BDoc message.

Bulk Replication

  1. The simplest replication sort is the majority replication.
  2. BDocs are always distributed in accordance with their site IDs, regardless of their contents and their relation to different replication objects. On this example, all bulk BDocs are replicated to website A, B and D.
  3. These objects don't trigger content-primarily based realignment (data redistribution).
  4. Bulk replication is particularly suitable for small tables.
  5. Typical examples for bulk-replicated knowledge are customizing information (the T* tables) or employee data.
Clever Replication

  1. Essentially the most refined replication type.
  2. Replication objects are distributed relying on their contents and their relation to other
  3. replication objects (in this example, only website A receives the complete set of knowledge; websites B, C and D acquire a subset solely).
  4. Particular replication rules are necessary.
  5. Example: Replication object “CAP” (buyer and prospects).
  6. Dependent Replication :With dependent replication, a subscribed shopper receives all BDocs referring to a different BDoc acquired by way of clever replication by the identical client. For instance sales documents, which observe the corresponding customers.
  7. Each dependent BDoc must comprise the kinds and keys of the BDoc it follows.
  8. The guardian BDoc should be replicated by method of clever replication.
Publications group BDocs with specific standards for information replication. Publicatio ns might be subscribed to for sites.Subscriptions are assignments of sites to publications, specifying criteria values if necessary. The creation of subscriptions triggers the actual distribution of data to the sites.Publications and subscriptions are both defined and maintained with the Administration Console .

Example of a knowledge circulation:

  1. A BDoc message is generated on a client and appended to its outbound queue.
  2. After uploading the BDoc message to the Middle ware with the ConnTrans program, the BDoc message is appended to the inbound queue for the shopper .
  3. Depending on the form of the BDoc message, the message is assigned to one or more publications.
  4. The BDoc message is replicated to the sites that subscribed to the publications the BDoc message belongs to.
  5. After the purchasers synchronized their queues with the Middle ware, the BDoc messages are appended to the corresponding inbound queue of the clients for further processing .


A publication ought to only contain one clever BDoc, since in any other case there can be conflicts
arising with the realignment mechanism, which assumes a maximum of 1 clever BDoc type for every publication.Instance is the sites above subscribe to the clever publication Clients & Prospects with the ZIP code as selection criterion and with the 2 bulk publications Common Employee Information and Customizing.It is potential to mix the standards fields of intelligent publications utilizing operators AND (one publication) or OR (two publications required). Mixtures guarantee the belief of versatile and complicated replications. Watch out, because many combos are allowed however just a few are useful.

Examples:

  1. AND mixture: There are multiple publications for Clients & Prospects BDocs. The criteria fields Country and ZIP code of these BDocs could be combined utilizing the AND operation by subscribing to the publication CAP (by Country and ZIP code). On this case, a BDoc is replicated to a website if the Country AND ZIP code of the BDoc matches to the values specified within the subscription.
  2. OR combination: With the intention to obtain all BDocs of sort CAP for a particular country OR a explicit worker, it is necessary to subscribe to the two publications CAP (by Nation) and CAP (by worker).
For the creation of a publication, a wizard is offered. Depending on the replication kind (bulh, clever or simple intelligent) you'll have to choose a replication object and the criteria discipline names.Be deciding on a publication its details are displayed:
  1. Publication name
  2. Replication object
  3. Subscriptions for this publication
For the creation of a subscription (project of publications to a website using certain criteris) you
must enter:
1.A publication
2.In the case of an clever or easy clever publication the criteria values in your subscription.Via standards values you probably can resolve whether a site ID ought to receive the entire set of information referring to a replication object or only a subset of this data. It is potential to outline a value range for each subject on this object. This reduces the quantity of data that's sent to a cellular client.There is not any limit to the number of criteria fields you may outline for the replication of one object.

Instance for standards fields:

The BDoc sort Buyer incorporates the sector Sales Space, which is defined to be a standards field.Primarily based on the content material (criteria values) of this discipline, the Prospects are made available to the various sites.From inside the Administration Console, all obtainable BW workbooks could be requested for cellular customers and are then delivered to the corresponding cell clients. Path: Atmosphere ® Show BW Programs, Button „Run Requests“ Regular updates of workbooks will be scheduled. These updates normally only discuss with the question data contained throughout the workbook, since the workbook itself (the framework) is already current on the cellular shopper and needn't be transferred again.

The workbooks (based mostly on publications like „BW Workbook Reviews“ and „BW Query Experiences“ have to be subscribed by sites. Queries provide you different views of the data to be analyzed.CRM - BW integration: A BW sytem is made available to the Administration Console by means of the following procedure:
  1. A RFC destination is defined for the system on the CRM Server (transaction SM59)
  2. This method is selected and displayed in the Admin Console utilizing the button „Add BW system“.
If several websites should receive the same knowledge via the identical subscription, it's extra environment friendly to assign these websites to the subscription all at the same time, since then, the information extract is barely carried out once for all site queues.

DOC Dependencies

Within a replication model, you can have direct dependencies and oblique dependencies (inter linkages).Direct dependencies could be dependent replications or clever dependent replications.Dependent BDocs are routinely replicated together with the BDoc they observe, whereas intelligent dependent BDocs have to be explicitly subscribed.An instance for a dependent replication can be sales paperwork that follow the corresponding buyer, i.e. gross sales documents are replicated to the same websites as customers. An example for an intelligent dependent replication would be activities that would observe a buyer or an opportunity.Inter linkages may be defined between intelligent BDocs. With interlinkages it is doable to model very complex BDoc dependencies, the place arbitrary relationships between BDocs could also be used for replication.

An example of an inter linkage could be Clients & Prospects with Contact Individuals or Customers & Prospects with Opportunities.

Realignment

Realignment is a redistribution of information that ensures that all websites receive the data assigned to them by means of subscription. It has to be sure that that the distributed native databases remain consistent with the status of the central consolidated database.A minor realignment is triggered by changes to knowledge, i.e. when a worth of a standards discipline is changed.In this case deletion or update BDoc messages are replicated to the cell clients.A serious realignment is triggered by adjustments to subscriptions, i.e. when creating or deleting subscriptions. In this case the corresponding deletion or creation messages for the BDoc messages belonging to the subscriptions are replicated to the cell clients.The minor realignment is applied to single BDoc messages. n It takes place, for instance, while you:
  1. Create a BDoc message:Replication to all relevant website IDs together with all dependent BDoc messages
  2. Modify replication-related fields:Recalculation of the related web site IDs and, if vital, deletion or re-assignment
  3. Delete a BDoc message: Triggerin g the deletion of the BDoc message and all dependent BDocs
  4. It's executed automatically.
  5. The expressions minor realignment and BDoc-based mostly realignment are equivalent.

The major realignment shouldn't be related to single BDoc messages.It consists of many minor realignments.It's triggered when getting into/deleting subscriptions with the Administration Console.The expressions major realignment and packet-based realignment are equivalent.

Secure First Communication

To ensure a secure communication between a cellular shopper and the CRM Middle ware, a safe first connection protocol is used. A web site ID and a consumer for a newly put in mobile shopper are created on the CRM Middle ware using the Administration Console. On the mobile consumer laptop computer, the program ASiteID is started both immediately or by way of the Client Console to connect with the CRM Middle ware.Throughout this first safe connection, a unique web site ID is transferred and used for later communication sessions.

During subsequent connections, the consumer identifies itself using the positioning ID; an R/3 log on is no longer required.A subscription for worker information is then created for the cell shopper with the Administration Console. This subscription accommodates the consumer’s logon data for the cellular application. The mobile consumer can now initiate a communication (ConnTrans) for the primary time to receive the worker data needed for the first logon to the cell application.To acquire a web site ID from the CRM Middle ware, you can start this system ASiteID.exe from the Consumer Console. Right here you presumably can specify the name (Destination Name), the server identify (Server) and the System No. of your CRM Server, the suitable Client Quantity as well as your R/three Logon Identify and Password.

Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
SELECTOIN SCREEN FOR ABAP PROGRAM DAY 29
PROGRAMMING DATA RETRIVAL IN ABAP DAY 30

No comments :

Post a Comment