SAP CRM Middle ware Administration and technical back ground

SAP CRM Middle ware Administration and technical back ground is the point of discussion here and that explains you the way customer relationship management of this ERP works.The motivation for using Business Documents (BDocs) as a knowledge container for processing business objects that logically belong together (for instance, all information about one order or one accomplice and so on) and for transporting them as one unit is that this avoids having to course of or transport a quantity of individual desk entries.BDoc messages are used for knowledge processing throughout the CRM system and for information replication toward Mobile Clients.BDoc sorts are defined and managed within the BDoc Repository with the the BDoc Modeler.

When talking about BDocs, a distinctions should be made between BDoc type, the BDoc occasion and the BDoc message:
  1. A BDoc type or structure have to be defined for every required enterprise object, for example, Contact Person, Sales Order. It accommodates all of the R/3 table entries that make up the corresponding business object.
  2. A BDoc instance is a concrete instance of a given BDoc type containing all discipline values. It doesn't exist as a BDoc but however is still to be found in the database.
  3. A BDoc message (or simply BDoc) contains modified fields only. These embody new fields and deleted fields. The difference between a BDoc message and a BDoc occasion is that there is just one BDoc instance for a business object however there might be a number of BDoc messages (with their own IDs) for one BDoc instance. Nevertheless a BDoc instance is replicated to a mobile shopper utilizing a BDoc message the place all fields are filled.
Adapters are special services that present connectivity to exterior systems with the intention to change BDoc messages between the Middleware Broker and the Cellular Purchasers, the SAP R/3 system or other systems.


  1. Information/discipline restriction: Some management segments such as the recipient record should not delivered to the Cellular Client.
  2. Mapping: The R/3 adapter fills up the import fields of R/three BAPI calls with data coming from a BDoc.
  3. Conversion: Knowledge that is imported from external techniques through the XIF or the ASCII adapter is transformed into BDoc messages before it's delivered to the BDoc flow.
  4. Key completion: A model new sales order is transferred by the R/3 adapter to the SAP R/3 system. The BDoc is retained until there's a solution from the SAP R/three system. Then the R/three key's inserted into the existing BDoc and the BDoc is returned to the BDoc flow.
  5. Defaulting: Fields that need to be filled receive default values.

For knowledge exchange can come into the CRM Server by manner of the appropriate queue. The info is validated by means of a validation service. The messaging layer uses messaging BDoc sorts for knowledge exchanges with the CRM Server functions, SAP R/3 again-ends and exterior systems.The Administration Console will decide the receivers of the data. The appropriate adaptor services are called and sent to the outbound queue.The CRM middleware can apply simple clever replication to Messaging BDoc types. A messaging BDoc type acts like an envelope: The CRM middleware can't access the data contained in the envelope however can access knowledge on the envelope. Each application uses totally different address info in order that, for example, gross sales orders can be routed in maintaining with the sales organization.

The replication takes place in a star-like style from the CRM Server to the Cell Shoppers (sites A, B and C), SAP R/three back-ends (web site D) or non-SAP R/3 again-ends (website E). There isn't a hierarchy on this system. That means that information is saved solely within the CRM database and in the local databases of the purchasers; there isn't any intermediate storage that regulates distribution. Information is replicated to sites (native databases) and not to particular person persons. A replication mannequin defines the rules for the way knowledge is distributed. The replication model is created and administered within the Administration Console.

The principle tasks performed with the Administration Console are:

  1. Setting up and maintaining the replication, that is, sustaining replication objects, publications and subscriptions
  2. Managing cell employee (customers) and their passwords
  3. Defining websites, the logical representation of data receivers inside the CRM Middle ware
  4. Assigning workers to sites (website sort Cellular Shopper solely)
  5. Defining and administering organizational structures.
  6. To entry the Administration Console, choose Structure and Expertise-middle ware-Administration-Administration Console (or use the transaction SMOEAC).

In an SAP CRM system environment, native parts or sites should be linked to the central element permanently or briefly in order that messages may be exchanged. Sites (not users) are the smallest addressable unit in Replication and Realignment. They're recognized by a world identifier (GUID).Each site has a website type. Websites of the same sort use the same adapter for exchanging information between the CRM Server and the sites. There's a range of website sorts accessible for connecting SAP components. Sites are created in the Administration Console, a CRM Middleware device for the administration of the information trade of websites (native parts). An SAP R/3 system is created, for instance, as a site using the positioning kind R/3. SAP supplies many normal web site types: CRM, CDB, R/three, Cell shopper, External interface for XML, Exterior interface for Idocs.

You presumably can create your personal customer-defined site varieties in Customizing beneath SAP Implementation Guide-Cust.Relationship Management-Middleware and related parts-Communication Setup-Create New Site Types.

Publications group BDocs for knowledge replication.Determination of criteria fields by which subscriptions can be taken out (for instance, all clients in a specific postcode area).Grouping of BDoc types to be distributed by distribution sort (replication sorts, for instance, bulk, clever) Definition of dependencies (relationships) between completely different sBDoc types (for instance, if customers are transferred by realignment, their contracts may also be transferred) comprise only one intelligent BDoc kind (and all dependent ones) or multiple bulk BDoc sorts Subscriptions are assignments of net sites to publications, specifying standards values if necessary. The websites are thus recognizable as receivers of replicated data. The creation of subscriptions triggers the actual distribution of data to the sites.

Project of sites to publications

Dedication of values for distribution criteria (for example, all customers in postal code area 6) Predefined publications are delivered by SAP as department templates. Subscriptions are particular person and should be decided by customers.Publications and subscriptions are defined and maintained with the Administration Console.Creation of objects: Some objects are created instantly in the software (employees, sites, organizational items). A wizard can be used to create other objects (publications, subscriptions, replication objects). After choosing the object sort, you presumably can create an object in Change mode. Within the similar transaction, you can assign that object to others that already exist.

Creating or changing these administration objects requires particular user rights:
  1. Role SAP_CRM_MWAC_ADMINISTRATOR for employees, websites, organizational models and subscriptions
  2. Function SAP_CRM_MWAC_CUSTOMIZER for replication objects and publications
  3. Whenever you create a brand new site, it's essential to present the positioning particulars similar to the next:
  4. A site name and a website description
  5. A site type - R/3, Cellular Client or different
  6. Site attributes (for non-mobile websites) - the RFC vacation spot of the site that you created earlier utilizing transaction SM59

For the creation of a subscription you will need to enter a publication and, for an intelligent or simple intelligent publication, the criteria values (primarily used in a cellular situation) for your subscription.Via standards values you presumably can decide whether a web site ID should obtain the entire set of knowledge referring to a replication object or solely a subset of this data. It's doable to outline a price vary for every subject in this object. This reduces the amount of data that is dispatched to a mobile client.There is no such thing as a limit to the variety of criteria fields you possibly can define for the replication of one object.

Instance for criteria fields: The BDoc sort Customer contains the Gross sales Space subject, which is outlined as a standards field. Based mostly on the content material (criteria values) of this area, the Customers are made obtainable to the various sites.Thus SAP CRM Middle ware Administration and technical back ground explains the way that we need to work with for better results.

Related Posts

No comments :

Post a Comment