Analytical SAP CRM Overview

From a more technical standpoint, SAP CRM consists of an operational CRM system plus a data
warehouse that serves as a constant customer data base.Using a standard set of metadata as your basis, you may easily synchronize your grasp information,hierarchies, and transactional knowledge along with your information warehouse, which ensures the very best degree of consistency and accuracy of your data.SAP Enterprise Info Warehouse (SAP BW) offers all the features you want to extract, transfer, and upload knowledge in addition to to store information in operational knowledge stores or OLAP cubes. Moreover,it offers complete reporting and navigation functions, akin to Excel-based mostly or Web-based queries.This knowledge warehouse is delivered with data mining engines that seamlessly access the info and write the analytical outcomes again to your customer data base. For extra sophisticated knowledge mining
necessities, the answer is also fully integrated with IBM’s clever Miner.

Predefined, enterprise-particular purposes, akin to Customer Lifetime Worth, ABC Evaluation, Marketing campaign Optimization utilizing RFM, or Churn Administration, are also included in the solution.A Web-primarily based portal entrance-end ensures simple, position-based mostly entry to all functions.Information Warehousing with SAP BW forms the idea of an extensive enterprise intelligence answer to convert data into useful information. The next graphic illustrates the integration of information warehousing and its function areas into the architecture of SAP BW.

For management of most Knowledge Warehouse Administration processes, the Administrator Workbench (transaction RSA1) of SAP is the central entry point. It supplies knowledge modeling functions as properly as features for control, monitoring and maintenance of all processes in SAP BW having to do with data procurement, data retention, and information processing.In modeling, you may create and edit all of the objects and rules of the Administrator Workbench which might be wanted for information transport, replace and analysis. You may also execute capabilities associated to these.Information Retrieval: (ETL and Open Hub Providers): Information retrieval is one in every of the data warehousing processes in SAP. SAP gives mechanisms for retrieving data (master information, transaction data, metadata) from varied sources. You possibly can differentiate as to whether the SAP BW is the goal or the supply of the information transfer.

  1. BI Platform: The Business Intelligence Platform offers a technological infrastructure, together with various analytical technologies and features:
  2. Online Analytical Processing(OLAP) is used for data preparation of large amounts of operative and historic data. The OLAP processor allows permit multi-dimensional analyses based on various business perspectives.
  3. The Metadata Repository allows information on metadata objects for the BW system to be displayed in running system or to use them independently of BW system operation.
  4. With Enterprise Planning and Simulation (BW-BPS), you create planning applications. The areas of software vary from easy guide information entry to complicated planning scenarios.
  5. Special evaluation processes such as Data Mining can be realized with the Analysis Course of Designer (APD). Using an evaluation course of, info might be combined within the BW system to generate new information. This new info can be attained utilizing analytical processes akin to information mining methods or easier buyer-specific calculations and transformations.
  6. The Reporting Agent is a instrument used to schedule reporting functions within the background.
  7. Enterprise Explorer Suite: The Enterprise Explorer is the SAP Enterprise Info Warehouse part that gives flexible reporting and analysis instruments for strategic analyses and decision making assist within a company. These tools embrace query, reporting and evaluation functions. As an worker with authorization for the Business Explorer, you may evaluate outdated and current knowledge to varying degrees of detail and from completely different perspectives on the Web and in addition in MS Excel.
Data Flow

The PSA is the inbound store for data from the source system in BW. The requested data is saved unchanged in the SAP BW system. Earlier than transferring knowledge into an InfoSource, you may have the option of saving transaction and master knowledge within the PSA, that is, you should use the PSA as a brief retailer for operative data. You can modify the data within the PSA tables manually and use it for added updates into Basis Cubes. The PSA is also used as a further control occasion to make sure the information high quality and a right load process. Nevertheless, the PSA is meant only as a brief lived store and never for permanent information storage.An Operational Information Retailer object (ODS object) is used to retailer consolidated and cleansed information (transaction information or grasp data for instance) on a doc degree (atomic degree). It describes a consolidated dataset from a number of InfoSources. You can analyze this data with a BEx query. In contrast to multi-dimensional knowledge stores for InfoCubes, data in ODS objects is saved in flat, transparent database tables. Fact and dimension tables are usually not created.

An InfoSource is a amount of data that logically belongs together and that has been summarized into a single unit. InfoSources include transaction data (this knowledge is stored in InfoCubes) and master information (attributes, texts, and hierarchies - this information is stored in separate tables). InfoSources describe all the information that's available for a business process or a kind of business course of (for example, value middle accounting).Switch constructions help the switch of data in a DataSource between a source system and a connected SAP BW system. The transfer construction transports the DataSource knowledge from a source system to a SAP BW system and uses transfer guidelines to pass the information on to the InfoSource.The communication construction is independent of the source system and is generated from the InfoSource. It is crammed from the transfer construction in accordance with the switch rules. The communication construction contains all of the fields in an InfoSource. This means of extracting and transferring cleansed knowledge to the communication construction is named data staging.

Data Deployment

You presumably can combine the enterprise contents of the Enterprise Information Warehouse into an Enterprise Portal seamlessly. The Enterprise Portal lets you access applications from other systems and sources, such because the Web or Intranet. Utilizing a single level of entry, you can obtain structured and unstructured information. Because of this enterprise information from data evaluation is on the market in addition to contents from information management, from the Web, and from the Intranet.

Business Content CRM

The contents of Business Content material are structured in accordance with functions in addition to industries.Software-specific Business Content consists of for instance Customer Relationship Administration,Supplier Relationship Mangement, Supply Chain Management, ....Enterprise Content was enhanced for SAP BW Launch 3.5 with regard to analytical applications.Analytical applications measure and optimize business processes based on an integrated information basis.They add existing raw data to a surplus value, because a remedy choice has already been deliberate throughout all programs and applications. They always refer to a process and measure the success of this process.Analytical purposes acquire knowledge, transform them into information, add intelligent algorithms to them, and assist the execution of the necessary steps in the system.

Data Flow in CRM

A DataSource describes (within the type of field constructions) the info that's available in a supply system (f.ex. SAP CRM). Within the utility part hierarchy all DataSources are displayed in an outline tree, grouped by analytical applications. The DataSource consists of the extract structure (all prepared fields) and the transfer structure (a number of fields from the extract structure). The DataSource and the appliance part hierarchy is replicated into SAP BW system. An InfoSource is a set of data that logically belongs together gathered right into a single unit. The communication structure is the field structure wherein this information is stored.Transfer guidelines remodel data from several switch structures right into a single communication structure.

Replace rules rework information from a communication structure into one or more information targets (ODS, Master Information, InfoCube, ..)


Service API is the standard interface in SAP BW atmosphere for source systems. Data extraction from a source system with assist of the Service API known as generic extraction.In CRM, texts and master knowledge are often extracted using the standard functionality of the generic BW Service API.For the add of time-dependent grasp data or of transactional knowledge, the BW Adapter (BWA) in CRM offers a delta mechanism, extracting information from BDocs. CRM-specific DataSources are used for this purpose.The delta course of must be initialized with an preliminary add of all business information for a selected CRM object from the CRM database. BW Adapter then monitors adjustments to existing objects with assist of the CRM Middleware, and passes them by means of the BW Service API and the so known as BW Delta Queue to the BW system. Knowledge transfer from CRM to BW is performed with the qRFC know-how for the delta upload.

Data Extraction

Service API is the standard interface in SAP BW atmosphere for source systems. Data extraction from a supply system with help of the Service API is named generic extraction.In CRM, texts and grasp knowledge are normally extracted utilizing the usual performance of the generic BW Service API.For the add of time-dependent master information or of transactional information, the BW Adapter (BWA) in CRM provides a delta mechanism, extracting information from BDocs. CRM-specific DataSources are used for this purpose.The delta process must be initialized with an preliminary upload of all enterprise knowledge for a particular CRM object from the CRM database. BW Adapter then displays changes to current objects with assist of the CRM Middleware, and passes them by the BW Service API and the so referred to as BW Delta Queue to the BW system. Knowledge transfer from CRM to BW is carried out with the qRFC expertise for the delta upload.

System Landscape

A typical system landscape consists of a development, consolidation and manufacturing system each on the CRM and on the BW side.BW uses the idea transport system (configuration with STMS).Changes on BW objects are saved in local change requests. They can be built-in to a transportable change requests using the BW Administrator Workbench (RSA1 >> Transport Connectoin).Transports make only sense between CRM programs or between BW systems.Communication between CRM and BW methods via RFC (it's endorsed to connect solely system pairs similar to growth methods, consolidation methods and manufacturing methods).

System changeability in consolidation and productive BW and CRM system is ready to ‚not modifiable‘ (SE06 and SCC4).PI should be put in on CRM (most current version beneficial). You might find extra information in SAPNet underneath alias: r3-plug-in.Default system setting: New BW objects are created as native objects (bundle: $TMP). Transports of new objects should be accomplished with the “Transport connection” within the Administrator Workbench (RSA1).Throughout metadata upload the metadata will not be assigned to any package deal, the uploaded metadata can’t be transported between BW system. The metadata add needs to be executed for every pair of methods (CRM - BW) separately (no transportation attainable.).In a BW-System only one productive shopper is possible.

Data Extraction from CRM

The consumer units the switch methodology (PSA or IDoc) and maintains the transfer rules. During the generation of the InfoSource, the strategy is transferred to the SAP source system (Repository). The info load process is launched by a request IDoc to the source system. Information IDocs are used with both transfer methods. Nevertheless, they are always transferred by way of ALE.Over the Information Idocs, the BW system generates the visitors gentle settings for monitoring the load processes.A data IDoc consists of a management document, an information record, and a standing record. The management record incorporates administrative information about the recipient, the sender, the consumer, etc. The status document describes the status of the IDocs, such as processed.The saved knowledge within the ALE enter and output have to be emptied or reorganized manually. In the tRFCs, the variety of fields is proscribed to 255. For tRFCs, the data record length is proscribed to 1962 bytes. For IDocs, the restrict is 1000 bytes.

Non-SAP methods are usually not coupled directly to the suitable switch method. The info format is adapted to the inner BW format (similar to removing separators within the flat file, or capitalization). Non-SAP methods may be flat files or direct methods (coupled through BAPIs).
The scheduler is the connecting hyperlink between the source systems and the SAP Enterprise Information Warehouse. Utilizing the scheduler you'll be able to determine when and from which InfoSource, DataSource, and source system, knowledge (transaction data, master information, texts or hierarchies) is requested and updated.The principle behind the scheduler relates to the capabilities of SAP background jobs. The information request will be scheduled either immediately or it could be scheduled with a background job and started routinely at a later point in time.

With the help of an InfoPackage, you determine the choice conditions in BW for the data request from a supply system. On this section, you'll have the option to select the contents of the InfoPackages in order that it may be scheduled.

Monitor of Data Extraction

The detail tab web page delivers information on the current Monitor element display (up to date information, up to date infos, Scheduler, all IDocs) in addition to additional info sorted based on the dataflow in an overview tree. The overview tree means that you just can navigate with the current functions (IDoc or PSA upkeep, simulated booking,...) utilizing the context menu.The logs on rebuilding, cancellation, and deletion are also integrated, as are the functions for activating the ODS object knowledge, and for the further update of the data in the information targets.Technical data that cannot be displayed in the textual content of the Monitor element tree, is displayed in the footer row when you select a node.

Data Transfer from BW

You'll have the opportunity to optimize buyer relationships by deploying the insights you gained from measuring performance and predicting events within the operational processes.To enable the information from SAP BW for use within the operational processes in SAP CRM, it is vital for the data to be transferred from the BW system into the CRM system.Not like with data extraction from SAP CRM into SAP BW, there is no single course of that can be applied usually

Related Posts
SAP CRM Technology Overview
CRM Middle ware System Architecture
CRM Software Logistics and Support

Master data for sap

No comments :

Post a Comment