SAP Business Warehouse Simulation Introduction

Simulation plays very important role in SAP Business Process and helpful in forecasting the business future requirements.Simulation is a procedure to analyze dynamic systems. In Simulation experiments are carried out based on a model of the reality, in order to gain insight regarding the real situation.Business simulations allow you to evaluate your business, identify key issues driving your processes and capture your company's specific business challenges Simulation models may range from simple linear equations with one unknown factor to sophisticated models that incorporate all known influences. Usually the focus of a simulation lies on aspects, which have the most impact on the simulated system, whereas minor important factors are left off or simplified.

There are different methods that support simulations: 

Forecasts: Forecasts examine trends in the presence and past and prolong those into the future. There is no guarantee that those trends will last, however besides day to day turbulence's there are a lot of development processes that are more linear than they look at first sight.

1. Driver-based simulation
2. Model-based simulation
3. System dynamics: Small events can cause unforeseeable processes. Watch the stock markets (or the weather) and you can see the effects any day. System dynamics is the attempt to predict future situations based on all available information and specific theories. 

 Driver-based Planning

Planning is often executed on a very abstract detailed level (e.g. cost elements). When a cost center manager is asked to submit the expected costs for salary, travel, office equipment, overhead costs, etc. that information is usually based upon an information behind those figures (e.g. based on the number of employees working in his department). The challenge is to translate data from across business functions into critical information that tells a company what drives their business plan Driver-based planning takes those dependencies into consideration. It simplifies planning on an aggregated level and enables simulations based on different assumptions about the drivers. Reactions on changing business conditions can faster be decided upon by using changed driver values. 

Methods to support driver-based planning are:

1. Attach documents: people are basically asked to submit a supporting narrative outlining the assumptions that are behind their numbers. 
2. FOX Formulas: model inter dependencies of drivers and related plan figures 
3. Planning sequences: Re-plan based on a predefined sequence of planning functions
4. Versions: Simulate different scenarios without overwriting
5. Reference Data: use relations and inter dependencies from the past  

Model-Based Planning

The planning process spans the whole organization. Decisions in one area of the company influence processes in other areas. These relationships may be executed sequential in the initial plan. For plan revisions the dependencies of the different plans may be modeled according to specific rules. That way it is possible to only change some plan assumptions and recalculate the full model.

Example:

Sales planning and production planning must be aligned so that based on the sales volume and assumed time for the demand the goods must be provided by production at the right time. Sales and production need resources in order to achieve their targets, e.g. sales representatives or production employees which influences headcount planning.

In addition to the integration aspect every department must conduct its internal planning process that in itself also may be model-based (e.g. calculation of capacity restrictions or scheduling in production planning)

Model-based planning reconstructs those inter dependencies and allows to simulate different scenarios based on alternative plan assumptions.

Methods to support model-based planning are: .
 

1. FOX Formulas: map data models (e.g. master data) and transfer data
2. Forecast Functions: predict future trends for value drivers which influence your overall model (e.g. sales growth)
3. Multi-Planning Area: Exchange data between different plan cubes 
4. Planning sequences: Re-plan based on a predefined sequence of planning functions 
5. Versions: Simulate different scenarios without overwriting 
6. Reference Data
7. Aggregation: Every planning process involves a lot of detail which cannot be mapped to another process. However there are similarities (e.g. Sales volume = Demand volume, time period) that may be used as an integration level. The aggregation in a planning level allows to exchange the integration
   values.

Limitations of BW-BPS Regarding Simulation

Circular references (A+B=C, C+D= A)

Excel formulas: no circular references possible
FOX formulas: circular references possible through planning sequences

Iterations

BPS offers no predefined functionality for iterations
FOX formulas: iteration only by re-execution
Planning function type exit: iterations possible 

Graphical display of relationships

Dynamic Simulation

System Dynamics (SD) is an experimental approach to System Analysis. It is a way of understanding complex systems and modifying or changing them in some way. It also an approach for validating and assessing the consequences of implementing analytical (prescriptive) models or recommendations of a case study report.

System Dynamics is both

1. a theory of structure in systems;
2. an approach to policy design.
3. System Dynamics is comprised of two concepts:
4. Feedback Theory that provides general guidelines for organizing system structure.
5. Computer Simulation that provides a means to deduce the behavior arising from a particular system structure.
6. System dynamics is concerned with the construction of graphical and mathematical computer-based models, with detailed descriptions, that tells us how the conditions at one point in time lead to subsequent conditions at later points in time. The constructed model can then be simulated and its behavior observed over time.

To sum it up,

1. System Dynamics is about studying complex and dynamic systems - systems which change over time.
2. System Dynamics is about finding the 'why' (cause[s]) and 'how' (pattern) of system changes.
3. The main benefit of system dynamics is to analyze single complex

Related Posts

ORGANIZING DATA BASE UPDATES 

Authorization and implementation of SAP 

SAP Financial Open Item Clearing 

CRM Sales Cycle Management 

Data Extraction from Finance Special Ledger using ..  

Scheduling of Global Planning for SAP BW

SAP CRM Middleware Software Distribution

The check client and the transport companies only exchange information with the client repositories.Software development in cell eventualities impacts the 5 repositories listed above. They are all positioned on the CRM Server and/or the Mobile Repository Server.The brackets contain the default names of the databases on the cell repository server that maintain corresponding repositories.

The assorted repositories in a mobile situation are:

1. On the CRM Server the Middle ware services repository (accommodates the R/3 adapter repository, replication repository,Move repository and the ASCII adapter repository) the BDoc repository the ABAP knowledge dictionary
2. On the Cellular Repository Server the application repository (ars_db) the BDoc repository (trrep) the IDES database (ides)

These repositories are modified by the next tools:

1. the Administration Console (solely server repositories)
2. the Cell Software Studio (solely shopper repositories)
3. the BDoc Modeler (both server and client repositories)
4. the SAP GUI (solely server repositories)

Transport to the manufacturing CRM server

The transport of the design time change lists isn't dealt with by the CRM Middle ware, since the Utility Repository is treated like customary ABAP Dictionary tables.The obtain to the involved improvement station is handled by transport providers of the growth station.The runtime objects of the transported change lists must be generated on the goal system by the mobile utility studio.

Changes to the BDoc Repository and the Middle ware Repository are transported via the Change and Transport System, first from the event to the take a glance at system, after which from the check system to the production system.With a objective to import software program transports and distribute the corresponding information to the mobile clients, you need to:

1. first cease all the inbound and R&R queues on the related CRM server,
2. then import the requests into the take a glance at or production system on that server,
3. afterwards activate the software program distribution course of, and
4. lastly start the inbound and R&R queues again.

Software replication to manufacturing customer

Software distribution is activated on the development statio n and involves the following steps:

1. to start with run time objects are generated from the transported change lists
2. then run time object packages are created by the Client Improve Wizard
3. afterwards these packages are uploaded to the CRM Middle ware
4. finally the software is distributed via BDocs using simple replication

Simple replicated BDoc messages aren't stored in the CDB neither is there any realignment possible. The circulation definitions for such BDocs include only the R&R service and the outbound adapter. The inbound adapter on the CRM Middle ware can obtain “outdated” BDoc varieties from the mobile client and converts them into “new” ones.The mobile consumer first receives and processes the “old” BDocs types. When receiving BDocs containing software updates, the shopper stops the processing of the inbound queue and performs the software updates. From this second the cellular client application can handle the “new” BDoc sorts and processes the remaining BDoc messages within the inbound queue.On the mobile consumer, the “old“ BDocs are then processed first.Afterwards the inbound queue on the cellular consumer is stopped in order to permit the software program update.Then the inbound queue is released once more and the “new“ BDocs may be processed.

Related Posts

CRM Mobile Replication Architecture 
CRM Middle ware Monitors 
CRM Middle ware replication Modeling
MODIFICATIONS TO SAP EXTENDED DAY 57
Master data for sap

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

SAP CRM MIiddleware Monitors

There are various queues inside CRM Middle ware which can be displayed and monitored, e.g.: . the outbound RFC queues, which might be monitored with transaction SMQ1 .The inbound RFC queues, which might be monitored with transaction SMQ2 the replication and realignment queues, which will be monitored with transaction SMOHQUEUE.

RFC monitoring

System path: Show Outbound Queues (SMQ1) and Show Inbound Queues (SMQ2).

qRFC queues are displayed in three steps:

After specifying one or more shoppers, queue names and queue destinations, the transaction SMQ1 or SMQ2 displays a listing of all queues that match the desired values. Now it's possible to pick out explicit queues of interest and think about further details. From the detailed view on the chosen queues, it is potential to display the queue entries by double-clicking the corresponding queue.

Replication Que monitoring





Monitoring Communication Stations

The data on individual sessions refers back to the information alternate throughout communication between a website and the CRM Server and is predicated on the data provided by the concerned Communication Station.

1. Carry out the next steps in the initial display of the Communication Monitor:

1. Specify the location, queue and required Communication Station within the Single Session tab page.
2. Then enter the desired interval (date and time) by which the periods to be analyzed were started.
3. Lastly, choose a status so that solely these sessions are displayed, which had this standing at the end of the beforehand chosen period. You can even choose several statuses.

2. Choose the Search perform and consider the search results. For each session discovered, a document containing info on this session appears within the table on the upper right-hand side of the screen.
3. Double-click on one of the periods displayed. The corresponding document is marked inexperienced and detailed information on this session seems within the Session Particulars tab at the lower right-hand facet of the screen.


These statistics give you information on the info trade for each site over a certain interval of time.

1. Choose the required day or week in the Statistics tab page within the preliminary display screen of the Communication Monitor.
2. Choose the Show function and check the selected period displa yed on the right-hand aspect of the screen. In addition, you probably can see the date and time of the beginning of the switch of the primary knowledge record, as properly as the date an time of the top of the switch of the last information record.
3. All of the sites that communicated with the CRM Server through the specified period appear in a table on the right-hand side of the screen. In response to the tab page, various info is displayed for each site.

The data displayed gives you information on the working system load of your Communication Station.The data is collected by the SAP Working System Collector and is distributed through the SAP Working System Monitor.

Related Posts

SAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Interaction Center Agent Perform
CRM Interaction Center ManagementCRM Software Architecture

DATA BASE UPDATA AN OVERVIEW DAY 45

SAP CRM for Mobiles Replication Architecture

SAP CRM for Mobiles Replication Architecture is the motivation of utilizing BDocs as knowledge container for processing business objects and for transporting them between the CRM Middle ware and the cell shoppers is you could process/transport them as one unit, as an alternative of getting to course of/transport a number of individual desk entries.

BDoc's

While you talk about BDocs, it's a should to distinguish between the BDoc sort, the BDoc instance and the BDoc message.A BDoc type or construction needs to be defined for every required business object, e.g. Contact Individual,Sales Order etc. It contains all the R/3 table entries that make up the corresponding enterprise object.A BDoc instance is a concrete instance of a given BDoc kind containing all field values.A BDoc message (or just BDoc) contains “modified“ fields only. These embody new fields as effectively as deleted fields. The distinction between a BDoc message and a BDoc instance is that there's just one BDoc instance for a Business Object however there can be multiple BDoc messages (with their own Ids) for one BDoc instance. However a BDoc instance is replicated to a cellular consumer utilizing a BDoc message the place all fields are filled.

A BDoc sort consists of a header and a body.The BDoc header consists of one single data section, the so-known as control segment.The BDoc physique consists of one or more data segments and of 1 error segment.The control section merely incorporates header information, whereas the individual data segments comprise the actual table entries that make up the corresponding enterprise object.The error section can be utilized to retailer error information.Every knowledge segment incorporates section fields, additionally known as segment attributes. These fields are mapped to actual data fields of physical database tables.In BDoc varieties used for knowledge alternate between mobile clie nts and the CRM Server, an information segment is mapped to exactly one database desk, whereas in BDocs used, for instance, on the shopper side only, a information section will additionally be mapped to a join of tables or to a desk view.

BDoc Message

The Header of a BDoc message comprises the message ID, the sender ID and details about the BDoc instance and BDoc type.The first data phase of the Body of a BDoc message can be referred to as root segment. In contrast to all other data segments, the basis segment solely comprises one key field. All subsequent knowledge segments include two key fields: an personal one and the one of many parent information segment.As effectively as, every knowledge phase accommodates the duty that has been carried out (i.e. INSERT, UPDATE or DELETE) and the so-referred to as SendBits , which inform about the subject on which this activity has been performed.

The Recipient Listing is decided and added by the replication service and utilized by the outbound adapter.On the cellular clients, BDocs appear only on the Transaction Layer (TL). The attributes of data segments correspond to fields of the physical database tables on the one hand and then again to properties of Business Objects.

Relation between BDoc and replication object:

The replication object bears information about how BDocs of one kind are replicated and which fields of the BDocs can be used as replication criteria.Every replication object refers to exactly one BDoc type of the BDoc repository. Nonetheless, not each BDoc type must have a corresponding replication object (since not all BDocs are used for replication purposes).Used abbreviations for replication object are for instance CAP (buyer and prospects), CON (contact persons), ACT (activities), OPP (alternatives) or QOM (citation and order management).

Guidelines for replication objects :

One physical knowledge file belongs to precisely one occasion of 1 BDoc kind and subsequently to not less than one replication object.A BDoc kind ought to comprise as much logically interrelated tables as possible.The key fields of root segments all the time have to be stuffed, as a end result of they could probably be relevant for replication. That is particularly necessary for modifications of dependent replication objects.

Used table: SMOKNA1 (Normal Information in Customer Grasp) with a number of units of information (key area buyer number K*) and the relating replication object type CAP or CON. Each of them is said to no less than one single replication object (buyer or contact particular person).One data document isn't included in a couple of replication object, for instance:

1. CAP (customer and prospects)
2. CON (contact persons)
3. QOM (quotation management)
4. OPP (alternatives)
5. ACT (actions)

Criteria for an Clever Replication Object:

1. The BDoc is distributed by approach of an own look-up table
2. Attributes are defined as standards fields
3. The look-up table is up to date routinely using defined guidelines

Intelligent replication object varieties trigger upkeep of an personal look-up table and are distributed based on the entries in this table. In the course of the upkeep of look-up tables, the standards for assignment on the replication objects stage is in contrast with the lively subscriptions.Clever replication objects have only one information document of their root segment. The replication key should be in the root segment.

Standards for a Dependent Replication Object:

1. The BDoc is distributed via an existing look-up table
2. No attributes are outlined as standards fields
3. No own guidelines exist, except these of the guardian object

Dependent replication objects are distributed referencing a BDoc look-up desk of an intelligent dad or mum replication object. They do not trigger a realignment. Additional replication standards can't be defined.Whereas making a dependent replication object, the consumer must take care of the replication key, for example SFAKNA1 for an order. This simplification is simply possible if the distribution refers to only one (and not several) mum or dad replication objects.It's impossib le to reproduce a extra advanced dependency - like actions with relation to clients, objects or employees. For realignment functions you will all the time want entries in an personal look-up desk and never in the one of many dad or mum object.

Standards for an Clever Dependent Replication Object:

1. The BDoc is distributed through an personal look-up desk
2. Attributes are outlined as standards fields
3. The look-up desk is updated automatically utilizing outlined rules and using entries of another current look-up table.

Further replication standards can also be defined for such an object.When you select a replication object in the hierarchical structure of the navigation window, the following is displayed in the particulars area on the proper hand facet:

1. The mother or father replication objects of the chosen replication object (in this case none).
2. The replication objects relying on the chosen replication object (on this case one intelligent
3. one and several other dependent ones).
4. All publications that contain the selected replication object.
5. Replication-relevant fields with operator and distribution kind (crittype) whether it is an intelligent one.

Throughout a realignment, the replication key (equal to the root ID, the system key in the root section) and the appropriate site ID are written into the Look-Up Table . For object replication, it is then only essential to learn the entries of the look-up table.The data movement between the cell purchasers and the CRM Middleware is handled via inbound queues and outbound queues located on each side, the place as every cell consumer has one inbound queue and one outbound queue and the CRM Middleware has one inbound queue and one outbound queue for each connected mobile client.

1. A BDoc message is shipped from the outbound queue of a mobile consumer to the CRM Middle ware.
2. The BDoc message is placed in the corresponding CRM Middle ware inbound queue.
3. The BDoc message is mapped to a replication object.
4. In the look-up table of this object, the replication secret is used to identify the positioning IDs for the subsequent replication.
5. Based on these website IDs, the BDoc is positioned within the outbound queues for the corresponding cellular clients.
6. The BDoc message is obtained within the inbound queue of each of these mobile clients.

Interlinking

Description of an n:m relationship between objects of the identical or of two completely different object sorts.Inside the client software, relations (interlinkages) seem as hyperlinks for navigation purposes.A number of the tables used for interlinkages of business objects are:

1. SMOKVBEZ4 (customer - associated actions)
2. SMOKVBEZ6 (enterprise companion - business companion)
3. SMOKVBEZ7 (customer - staff of gross sales crew)
4. SMOKVBEZ9 (buyer - opportunity)
5. SMOKVBEZ11 (activity - worker)

Every relationship between two objects is qualified by the attribute Relation Type (RELTYP).Generally there are tons of predefined relation types which should cowl the primary requirements of an implementation project. Nevertheless, extra relation types will be created. Desk name convention for interlinkage tables: SMOKVBEZ + Number.

BDoc Processing into the Middle ware

Frequent companies throughout the CRM Middle ware:

1. The R/3 Adapter uploads enterprise objects to the related OLTP R/3 system.
2. The CRM service exchanges enterprise objects with the CRM on-line components.
3. The CDB service saves the fields of a BDoc message within the corresponding CDB tables.
4. The Replication and Realignment service determines whether a realignment is critical or not.

If a realignment needs to be performed for a BDoc message, this message is copied right into a separate realignment queue for additional processing. If realignment shouldn't be required, the sites are decided, to which a BDoc message must be replicated. The Outbound Adapter receives the checklist of internet sites computed by the Replication and Realignment service and appends the BDoc message to the outbound queues for all sites on that list.When a BDoc is delivered by the stream, the Replication and Realignment service to begin with performs the info replication. The replication key in the involved look-up table is used to identify the site IDs related for replication, and the recipient record is decided by utilizing these site IDs.


The BDoc and the location IDs are then returned to the flow and from there handed on to the Outbound Adapter, which places the BDoc into the related outbound queues.Lastly the replication realignment service determines whether a realignment is required or not.
As quickly as a realignment is required, the BDoc message is copied into a separate realignment queue for further processing.The realignment course of is answerable for maintaining the look-up tables. In these look-up tables,assignments are maintained between replication objects and sites. If a beforehand made task is changed - for example, if new objects are entered or previous objects are deleted or distribution criteria are modified - this should be reflected in the relevant look-up table.The activities required because of these modifications to a glance-up table are written into an extract queue.By using a BDoc message, these actions are then handed on to the concerned websites by way of the Outbound Adapter and the corresponding outbound queues.

Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
ALV GRID CONTROL IN REPORTS DAY 34
INTERACTIVE REPORTS BASICS DAY 35

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

SAP CRM Administering Sites and Mobile Users

SAP CRM Administering Sites and Mobile Users use data replication to do the job of running the web sites in a effective way for mobile users.The replication happens in a star-like trend, for example, from the consolidated database (CDB) to the sector gross sales/service staff (A, B and C) and to the workplace-based staff (D). There is no hierarchy on this system. That signifies that knowledge is barely saved within the CDB and in the native databases of the shoppers; there is no “medium stage” storage which regulates distribution.The foundations how data is distributed to cellular purchasers is defined by a replication model. n Information is replicated to websites (local databases) and to not individual persons.

With transaction SMOEAC you start the Admin Console.Depending on the chosen object sort , it's attainable to filter out particular components of the objects, for example, to solely view the websites or the employees.

Creation of objects :

Some of the objects are created immediately within the application (staff, websites, organizational units),whereas for the creation of others a wizard is offered (publications, subscriptions, replication objects). After choosing the thing type you could create an object within the Change modus. Within the same transaction chances are you'll assign that object to others which already exist.

Creation of customer:

Four steps are required to create a brand new worker (mobile consumer).Press the create button.Enter the first identify and last name to establish the user. Specify the logon name and the password of the user.Assign the person to a number of web site IDs.End the creation process by urgent the save button.Please notice that a website,not an employee assigned to that web site is the receiver of the data exchanged. Here merely the employee‘s logon title and password and their assignment to websites are administered.

Creating Websites

Four steps are required to create a model new web site.

1. Press the create button.
2.Providing the positioning details, equivalent to a website identify and a site description.choosing a connection group.In this step, you may specify how the cellular shoppers connect to the communication station. If the connection has to be established utilizing the telephone, choose the default connection. If the cellular shoppers are completely related to the web, choose already connected.Here the kind of knowledge can be defined that's exchanged with the communication station. When you select the default switch, the ConnTrans program on the cellular consumer will switch the Cellular Gross sales/Service information as well as e mail knowledge to the CRM Middleware. When you choose messages solely, ConnTrans solely synchronizes the Cellular Gross sales/Service data.
3. Create a subscription for the site.
4. End the creation course of by pressing the save button.


Organizational structures:

It is potential to define up to ten hierarchical levels.The definition of the group may be used to build hierarchies within subscriptions.Sites, subscriptions and users can be assigned on each level of an organization.Word that these organizational constructions should not built-in into the organization sites of the SAP Human Sources enterprise scenario.

For the creation of a publication, a wizard is offered. Relying on the replication type (bulh, clever or simple intelligent) you will have to choose a replication object and the criteria discipline names.Be deciding on a publication its details are displayed:

1. Publication identify
2. Replication object
3. Subscriptions for this publication

For the creation of a subscription (project of publications to a website utilizing sure criteris) you should enter:

A publication and in the case of an intelligent or easy intelligent publication the standards values on your subscription.Via standards values you may decide whether a website ID should obtain the whole set of data referring to a replication object or only a subset of this data. It's doable to outline a price vary for every discipline in this object. This reduces the amount of knowledge that is sent to a cell client.There is no limit to the variety of criteria fields you can define for the replication of 1 object.

Instance for standards fields:

The BDoc sort Buyer incorporates the sector Sales Area, which is outlined to be a criteria field.
Based on the content (standards values) of this field, the Clients are made available to the various sites.

Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
DATA TYPES AND DATA OBJECTS DAY 20
ABAP STATEMENTS DAY 21

Connecting Mobile Clients to SAP CRM

Connecting mobile clients to SAP CRM has a mobile scenario includes an OLTP R/3 system, the CRM Server, the Communication Station,and several other Cell Clients.. The CRM Server consists of an R/three system, the place the core software components (like HR,LO, FI) have been changed by the CRM on-line parts and the Middle ware functionality. It also features a database server that comprises the consolidated database (CDB).The Communication Station hosts the Microsoft Transaction Service (MTS) and the DCOM Component Connector, which controls the access of the sales/service staff by approach of their frontends (laptop computer, workstation, PC). In addition, it might also include the Administration Console. . Crucial for connection purposes on the mobile consumer are the transaction layer, the connection handler and the switch service.

CRM Objects as Communication Interface

SAP components (written in ABAP or ABAP Objects) and . COM components (written in VB, Java, C++, Cobol, Delphi, etc.) n Part Object Mannequin (COM) is an open architecture for cross-platform improvement of client/server applications based mostly on object-oriented programming. The purposes and programs might even be provided by completely different vendors. This expertise supports improvement in numerous programming languages. With the COM technology, clients have access to an object via interfaces carried out on that object. COM is language-independent, so that any language that produces ActiveX parts also can produce COM applications.

Distributed COM (DCOM) allows COM software program components to communicate immediately over a community, e.g. between a mobile consumer and the CRM Middle ware. The DCOM Part Connector (DCOM CC) runtime setting gives a general interface to call the distant function modules used on this context.The Microsoft Transaction Server (MTS) serves as a transaction processor over distributed systems. It effectively helps connection pooling and will increase network safety by offering an authentication system.As soon as the connection between the consumer and the object on the server aspect is established (through MTS and DCOM CC), the various strategies of an object might be called.

The Transaction Layer on the cellular consumer handles the access to the native database. At the similar time (i.e. in the same COMMIT cycle), it stores the information in a local queue in a format that can then be transferred to the server.When the user decides to begin out the communication course of by invoking the ConnTrans program, the Connection Manager on the consumer aspect establishes the connection to the server and then activates the Message Transfer Service , which transfers the info to the server by calling the Switch Proxy on the Communication Station. Other switch companies might be included within the connection session, so that the consumer has to initiate the communication only once.

DCOM is used for client/server communication. The DCOM Element Connector, an SAP Middle ware product, acts as the interface between the Microsoft and ABAP environments by making RFC function calls available as COM components.The DCOM Component Connector translates the DCOM operate calls from the Message Switch Service into RFC function calls to the Inbound Adapter on the CRM Server. The incoming DCOM operate calls are not queued or saved on the Communication Station.On the client aspect the Connection Supervisor triggers the Transaction Layer to read the inbound queue when new data arrived.There are two principal causes to run the Microsoft Transaction Server (MTS) on the Communication Station: higher safety (authentication) and better performance (connection pooling).


Communication Layers

So really communication between the CRM Server and the mobile shoppers is carried out through three totally different layers:

1. The TCP/IP layer for the community connection. Alternatively UDP/IP or HTTP tunneling may be used because the community connection between the mobile shopper and the Communication Station.
2. The qRFC/DCOM layer that allows communication between the ABAP and Microsoft environments.
3. The BDoc messages layer for the precise message transfer.

The arrange of the connection between the Communication Station and the CRM Middle ware involves the following steps:

1. The MTS safety settings should be specified. This specifies the authentication stage and information encryption between the mobile consumer and the Communication Station.
2. An RFC destination has to be defined for the DCOM Element Connector on the Communication Station.
3. The communication between the Communication Station and the Middle ware might be tested using the program QmtCheck.

MTS Components

The MTS is totally built-in into the Home windows NT safety mechanism. It presents two sorts of safety management:

1. declarative safety (controls access to the business objects and denies access to customers who do not have the required privileges)
2. programmatic safety (permits the enterprise object itself to decide what the person is allowed to do; it has more detailed safety checks than the declarative safety)
3. Begin the MTS Explorer from the menu:
4. Programs -> Home windows NT 4.zero Choice Pack -> Microsoft Transaction Server -> Transaction Server Explorer.
5. On the appropriate hand side of the window there could be an icon with a number of hats which denotes a role. Several users may be assigned to every role. The definition of roles is simply legitimate for a specific package and for elements contained on this package. A task can contain one or more Home windows NT customers/groups.
6. A package deal is a form of container for numerous parts which usually serve a associated purpose.Several components can belong to at least one package. Throughout utilization of a component, the associated icon is rotating.
7. On the correct facet of the window you see the accessible roles on this package deal (Person and Administrator on this instance). Different customers are assigned to 1 role.
8. Roles can be defined on the package, element (proven in the slide) or interface stage, relying on the granularity of security required.

DCOM Connector

After having put in the DCOM Connector, the subsequent step is to create locations that define a set of parameters required to join to an R/3 system. You may create or modify these destinations.This entails the following duties:

1. Select the name of the model new connection, e.g. _.
2. Select the connection type (here R/3 connection), the dedicated server, the R/3 system quantity, the client of the used R/3 system and the log on language.
3. Specify the user (user ID and password); this user must have the best to call RFCs on the CRM Middle ware.
4. Choose a particular operation mode (normally none).

Usually it is doable to configure the DCOM CC to use NT person credentials for accessing R/3. In
this case no user or password have to be specified.

Mobile Client

On the networking level it is sufficient to provide a TCP/IP connection to the Communication Station.When installing the Cellular Shopper application, you're asked whether or not to change replication on or off.If the replication is switched off, the installation routine provides a pre-stuffed database for the client application. On this case, it's not potential to exchange data with the CRM Middle ware. For those who enable replication, you might be requested for the IP tackle of the communication station.The QmtCheck.exe program may be used to test the DCOM connection between the cellular clients and the Communication Station. It might be launched on the mobile shoppers by approach of the Shopper Console.The settings for the DCOM connection might be specified utilizing this system dcomcnfg.exe.

For the safe first communication, an RFC connection between the shopper and the CRM Middle ware needs to be established once. This RFC connection is configured and used by the program ASiteID (it could be known as through the Shopper Console), which requires that the customers and the mobile clients are already identified on the CRM Server. The user and sites administration on the CRM Middle ware as well because the safe first communication might be mentioned in the Unit Replication & Realignment Overview.
Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture
REUSE COMPONENTS IN ABAP DAY 10
MANAGING ABAP PROJECT OBJECTS DAY 11

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

SAP CRM Creating Web Client Profile

CAP CRM Creating Web Client Profile helps you to deal the business in a effective way and this can be done by creating profiles for each clients with whom who is in contact with corporates and wish to do the business.The Interaction Middle supports all CRM methods, comparable to:

1. Gross sales: processing of gross sales transactions, opportunities, product proposals
2. Service: E-mail processing and workflow, solution database, service transactions
3. Advertising and marketing: Campaigns, call lists, product proposals

In addition, the Interaction Middle supports multi-channel communication:

1. Telephone: Incoming and outgoing calls, routing, call lists,telephony (CTI) connection
2. E-mail, fax, SMS
3. Internet: Inclusion of Web and intranet pages, co-looking, call-me-again, Web telephony

In each the WinClient and WebClient UI, you can control which of these capabilities are utilized by particular person agents, agent groups, or total name centers by assigning individually configured profiles.The IC WebClient is a browser based application. The HTML pages of the WebClient are based mostly on Business Server Web page (BSP) technology. The IC WebClient Framework is a connection between customizing and the enterprise server pages that allows to combine buyer specific program enhancements. An introduction into superior customizing might be dealt with in a separate unit on the last day of the course.

The IMG customizing of the IC WebClient is controlled by the IC WebClient profile which is a list of all of the customizing profiles for the separate WebClient functions. The customizing of profiles for the capabilities of the the IC WebClient might be dealt with in the subsequent unit.The IC WebClient profile is a collection of all capabilities customized within the element profiles for the Web Client.After you may have defined an IC WebClient profile you could assign it to an organizational unit or place of your organizational model.
The ultimate step within the profile configuration and task is to assign the IC profile to an organizational level, both an organizational unit or a position in the Organizational Mannequin (OM).IC profiles can only be assigned to organizational models and positions. Assignment to user degree is not possible.The IC profile stores the Customizing for an agent. It is connected to the agent as an HR infotype. An infotype describes and defines totally different attributes or traits for objects.An IC profile assigned a Organizational unit degree means all agents throughout the organizational unit use the identical IC profile and Position stage means brokers assigned to the identical position use the same IC profile.
Scroll down in the record of infotypes and select IC WebClient profile.Select the Create or Change infotype icon.Within the next screen, use F4 for the sector IC WebClient profile to display a listing of available profiles.Select the required IC WebClient profile and select Enter/Save.

Customizing net client capabilities for sap crm

Usually the customizing of IC Web Client features will be separated into four steps:

1. First that you must find out which of the profiles is controlling the operate that you simply need to change. In this case, you want to change the buttons which are accessible within the navigation bar. You could create your own navigation bar profile.
2. Create the new profile by copying an current profile that roughly matches your requirements.
3. After creating the brand new profile, change the settings of the profile (for example, insert a model new navigation link (=button) into your navigation bar profile).
4. As a final step, any new profile needs to be assigned to your IC WebClient profile.

The navigation bar gives a vertical line of buttons within the IC WebClient UI that means that you just can navigate to completely different views of the IC WebClient.The navigation bar consists of two different areas:

1. The usual space administered only by the IMG customizing of the navigation bar profile.
2. The personalized area that can be customized by any agent utilizing the navigation bar index of their IC WebClient.

The separation of the two areas in addition to the separate button of the navigation bar is controlled in the navigation bar profile.Navigation bar entries can be used to trigger completely different navigation varieties:

1. Navigation Links trigger the navigation to native IC WebClient views.
2. Observe: You may find extra data on the technical idea of navigation within the IC WebClient BSPs in unit Software Architecture in this course. (The navigation links delivered by SAP are stored within the BSP utility CRM_IC_RT_REP which is assigned in customizing within the runtime framework profile.Because of this you have to choose the runtime framework profile to have the power to enter a navigation hyperlink through the F4 Help).
3. Launch Transactions: Launch Transactions can be used to embed non IC WebClient screens into the IC WebClient work area. Examples are SAP GUI transaction from R/3, ERP, CRM programs, PC-UI screens and different web pages. For this purpose you first have to customize the launch transaction .
4. Class: this is solely relevant if you want to implement your individual logic to discover out the navigation target.

The transaction launcher lets you join any distant CRM ERP or R/3 transaction as well as URLs to a navigation bar. This way distant transactions may be displayed and maintained immediately in the IC WebClient.Any link entry of the navigation bar that's presupposed to call the transaction launcher, wants a navigation bar entry that points to a launch transaction ID. Right here the small print of the transaction to be launched are described: the launch transaction type, the form of object to be referred to as the method (like create, display, change) and possibly parameters to be passed to the transactions. These settings will be configured using the transaction launcher wizard.

New features in transaction launcher and navigation bar customizing with CRM release 5.0:

1. Transaction Launcher and Navigation Bar customizing is no longer XML based.
2. There isn't any Transaction launcher profile any more. Thus all Launch Transactions could be known as by any Navigation bar profile.
3. Different IDs of Navigation links and Launch Transactions might be mapped in Navigation Bar customizing.
4. Navigation Links can now be built as quickly as and utilized in many Navigation Bar profiles. No have to rebuild the hyperlinks for every profile.

The transaction launcher helps two normal sorts of transactions:

1. Launching pages of Individuals Centric CRM: Any transaction of People Centric CRM will be built-in into the IC WebClient screen. The Individuals Centric CRM UI is predicated on Business Server Pages (BSP) expertise, just like the IC WebClient. Based mostly on the BSPs, the CRM system can immediately generate HTML views that be built-in into the IC WebClient.
2. Launching BOR transactions of the CRM system or any remote SAP system: Objects like the CRM enterprise companion, SAP R/3 buyer master or SAP R/three sales order can be known as by BOR transactions.BOR stands for Enterprise Object Repository. It is a listing of all types of business objects that exist in SAP systems. They are often called and integrated as SAP GUI transactions into the IC WebClient. On this case an ITS (Web Transaction Server) is required to translate the SAP GUI dynpros into HTML pages.
3. New with 5.0 is the option to integrate any BSP or non BSP URL into the IC WebClient via transaction launcher and navigation bar customizing.

New launch transactions do not solely require IMG desk entries but in addition some ABAP code: the so called Handler Class that controls most aspects of the launch transactions.There is a wizard to create new launch transactions that means that you just can make all required settings without having to manually implement the ABAP class coding.In the WebClient commonplace there are three buttons within the navigation bar that navigate to IC WebClient views of CRM business transactions.The interaction file stores all the communication associated knowledge of the telephone call (for example, data like direction (inbound/outbound), standing, end result, free text notes). The identical applies to other communication channels like e-mail or chat communication.

The sales doc can embody quotation and order status and stores all sales items the customer wants to order.The service doc represents the service facet of a telephone call. Here the agent enters data on the client’s product that must be serviced and the service gadgets like hours of restore service and amount of spare parts.The identical concept applies for leads and complaints which are available as native IC WebClient screens as of CRM launch 5.0.The following slide will clarify how the gross sales and repair doc can be related to the interaction report relying on customizing settings of the enterprise transaction profile.


The alert modeler presents vital info to the agent and automates processes to increase agent productivity.Enterprise guidelines (situations and actions) are outlined and assigned utilizing the alert modeler profile wizard.Alerts are displayed within the persistent context space so they're always visible to the agent.Alerts can have hyperlinks that take an agent directly to a relevant screen.

In our instance there are two alerts:

1. Time to wrap up indicates that the planned name length is exceeded. The hyperlink takes the agent to the interaction record to wrap up the interplay data and finish the call.
2. The opposite message notifies the agent that the knowledge search has decided two solutions for the customer’s problem. The link navigates to the information search to display the solutions.Alerts are controlled by customizing settings of alerts that are assigned to the alert modeler profile.

Related Posts

Roles in SAP CRMSAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Technical Infrastructure
CRM Interaction Center Agent Perform
CRM Technical Architecture

CRM Interaction Center Agent Perform
CRM Technical Architecture