Google+ SAP CRM Middleware Replication Modeling - SAP ABAP

SAP CRM Middleware Replication Modeling

SAP CRM Middle ware Replication Modeling first of all, you must outline a replication object for a BDoc by specifying the replication type, i.e.bulk, clever, easy intelligent or dependent. For an clever replication object, you even have to specify potential distribution criteria.In a second step, you outline one or more publications to your replication object. An intelligent publication implies that it has one clever replication object assigned and that it specifies the actual standards fields used for data distribution.Lastly, you subscribe sites to those publications and you supply actual values for the factors fields.

To create a new replication object with the Replication Object Wizard, you first choose a BDoc from a record of all BDocs for which no replication object has been defined to this point and then enter an arbitrary but distinctive 3-digit quick ID in capital letters.After that, you choose the required replication sort, i.e. bulk, intelligent, easy intelligent or dependent.For intelligent replication, you then should enter distribution standards for the replication object. A construction of segments appears, from which you choose the corresponding fields and operators. A subject will be flagged as inter linkage subject here.Notice that operator EQ is assigned routinely when you select a area by double -clicking it.For intelligent and dependent replication, you could now choose the potential mum or dad objects.As quickly as the Replication Object Wizard has completed, the newly created replication object is mechanically activated.


Bulk replication implies that the BDocs are distributed completely to all sites with a subscription to the corresponding publication. Just one single look-up desk exists for bulk replication.Simple intelligent replication implies that no realignment takes place. A easy clever replication object has no personal look-up desk and only one potential distribution criterion can be specified. Distribution is completed via a receiver list.


To create a new publication with the Publication Wizard, you:
  1. first specify a name for the publication,
  2. then select the publication kind, i.e. bulk, clever or simple intelligent,
  3. and at last choose a quantity of replication objects relying on the publication type.
For clever and easy intelligent publications, you choose an clever replication object and specify the criteria fields to be used for information distribution.For bulk publications, it's essential to choose one or more replication objects that are to be sent completely to websites that must be defined.Once the Publication Wizard has finished, the newly created publication is robotically activated.An interlinkage publication signifies that you need to link two intelligent replication objects with every other through a hyperlink table.If you create an interlinkage publication, it's a should to specify:
  1. Two intelligent replication objects which may be to be linked to every other. You cannot hyperlink an clever replication object with a simple intelligent one and vice versa.
  2. The name of the bodily hyperlink table.
  3. The relation sort that's for use for the replication.
  4. The fields which are to be the source and destination fields of the inter linkage
  5. The identify of the sector wherein the relation kind is stored.
  6. The replication object that is to be the vacation spot object from the attitude of the client.
Replication modeling considerations

The amount of information subscribed for each website ought to be restricted as a lot as possible, since this reduces the realignment and information transfer load.

Examples:
  1. Do all mobile Sales customers actually need the complete order history for all clients, or might some of them use an internet access to the OLTP R/three system, or receive and use consolidated reporting knowledge?
  2. How much of a sales history is absolutely wanted on the laptop computer? Could three months be enough?
  3. Are pricing situations for all order line gadgets actually needed for all cell customers?
Attempt to foresee as a lot as potential what would be the replication requirements sooner or later and build the model accordingly.This will limit the number of knowledge realignments that should be carried out during later replication model changes.Take away objects in reverse order of their creation, i.e. remove subscriptions first, then the publications and at last the replication objects.Let processes triggered by a elimination end earlier than you continue, e.g. when deleting a subscription, wait until the realignment has been completely performed. (Examine the R&R queues on the CRM Server for this purpose.).Don't begin eradicating objects earlier than your complete new model has been designed and approved.

Word that information could additionally be destroyed whenever you transport objects from a improvement system into the manufacturing system and generate runtime objects on the manufacturing system.

Example : On the development system, all objects within the replication model hierarchy for a replication object have been removed properly before a brand new model is built. By transporting a model new replication object to the unchanged manufacturing system and beginning the technology, the buildings and information related to the BDoc type on the production system at the second are destroyed.


Efficiency Points Replication criteria:
  1. Delete unused publications
  2. Use standards fields with operator EQ if attainable
  3. Use criteria fields in top level (root) phase of BDoc, since they are often accessed faster than fields in child information segments
  4. Use few criteria fields in every publication
  5. Create table indices for standards fields (and combinations of standards fields) to make subscription checking quick
Bulk distribution is the fastest one, since No realignment is critical, which leads to fast processing on the server and Bulk insert into the client database is possible.Bulk distribution produces large quantities of data, since no criteria can be used to restrict knowledge for individual websites.

Related Posts

SAP CRM Organizational Model
People Centric SAP CRM Introduction
CRM Interaction Center Agent Perform
CRM Interaction Center Management 
CRM Software Architecture

ENHANCEMENTS TO ABAP DICTIONARY DAY 52

No comments :

Post a Comment