Google+ SAP CRM E Commerce Introduction - SAP ABAP

SAP CRM E Commerce Introduction

The CRM Server is the central SAP system within CRM landscapes.Largely all business situations (for example, mySAP E-Promoting) run on this system.Some business functions of mySAP CRM also can run within Java applications. The E-Selling Internet Applications are applied as Java applications which might be deployed on the SAP J2EE Engine.SAP R/3 is linked to the CRM Server as a again-end system and supplies further business functions comparable to material administration and financials.SAP BW is an optionally available analysis software that gathers and refines info from inside and exterior sources. In mySAP E-Promoting, it evaluates the sales and distribution data from CRM Marketing.SAP APO is a half of supply chain management. SAP APO comprises instruments for real-time planning and resolution support. For example, SAP APO performs product availability checks for gross sales orders in mySAP E-Selling.

The SAP Index Administration Service (IMS) is a device for indexing many forms of documents that may be dealt with within the SAP or CRM environment. To attach the IMS Server to CRM, an SAP Gateway is used.The TREX (Textual content Retrieval and Extraction) search engine helps flexible doc looking out,structuring of extensive doc collections by using computerized doc classification, and the extraction of fascinating data from a doc corpus (text mining). Within the mySAP E-Selling situation, TREX is used for searching within the product catalog. It meets the SAP IMS Server API specification and is used in combination with the SAP IMS.

With the SAP Web Pricing and Configurator (IPC), you presumably can easily configure products, process product configurations, and decide their appropriate prices.A 3rd-get together Internet server can be utilized for safety causes (for example, in entrance of a firewall). On the Net server (MS IIS and Apache Web server are supported), a selected plug-in is installed. This plug-in enables direct communication with the SAP J2EE Engine.

The important thing space, E-Promoting, offers comprehensive capabilities for promoting services via the Internet, whereas creating a new, strategic gross sales channel. Organizations can present clients with personalized, interactive, and straightforward-to-use sales and self-providers via the Net, and streamline sales and fulfillment operations to enable an end-to-finish order-to-money process. Companies can help business to enterprise or business-to-consumer selling scenarios, while significantly reducing their value of sales.E-Selling contains, for example, Enterprise Situations for Net store administration, citation and order management (Internet gross sales), interactive promoting and configuration, and Net auctions.This unit considers two enterprise eventualities which are shipped with mySAP CRM E-Selling:

  1. B2C - Enterprise to Consumer
  2. B2B - Enterprise to Business
The method of purchasing merchandise from the Web Shop using mySAP CRM E-Promoting could be divided into the following main steps:
  1. Search: Enter the Internet Shop and select products
  2. Select & Configure: Fill the buying basket
  3. Order: Create a gross sales order
  4. Test standing: Test the standing of the gross sales order
A client enters your Web Store, performs self-registration, and places a sales order.During self-registration, a enterprise companion grasp document is created in CRM.After self-registration, the business accomplice grasp document is routinely transferred to the OLTP SAP R/3 System and mapped to a customer grasp record.The following description of the B2C situation presupposes that the enterprise partner quantity is the same in both systems. The enterprise companion quantity needn't be the identical, however this makes the method easier to follow.Within the description, the number assignment in CRM is inside and the number task within the OLTP SAP R/3 is external. Other number assignments within the two programs are possible.

The situation shown in the graphic describes how a new customer grasp (B2B buyer) is created in SAP R/three and is then transferred to CRM, where the shopper grasp document is mapped to a business companion grasp record.On this case, the enterprise partner quantity is identical in both systems.It is usually potential to create the business companion in the position customer immediately in CRM.In this instance, the quantity assignment in SAP R/3 is inside and the number project in CRM is external.Pricing information for the products are maintained in the back finish and loaded into CRM via initial download (CRM Middleware). Pricing knowledge is then accessed during on-line processing of the CRM application by the IPC. Internet users can configure products and discover out costs with out producing again-finish load (CRM Server).From CRM 3.0 onwards, CRM E-Selling (previously generally recognized as Web Sales) uses Java Server Pages (JSP) technology.In CRM E-Promoting, it's necessary to set up a cluster model of the SAP J2EE that's unbiased of the CRM Server. Technically, it's possible to put in the J2EE Engine on the same host because the CRM Server. However, we don't suggest that you use the SAP J2EE Engine, which is included within the CRM Server.To determine a connection between the CRM E-Selling Java Utility and CRM, the SAP Java Connector (SAP JCo) is required.

The CRM Internet Application could be started with the following URL:
http://:///init.do is an abbreviation for Enterprise Archive and here means Web application archives, like b2b or b2c On the Web server, a selected plug-in is installed (only MS IIS). This plug-in allows direct communication with the SAP J2EE Engine. In addition, a firewall might be set up between the Web server and the SAP J2EE Engine to separate the Net server from the inner network. To use Microsoft’s IIS as an middleman server with the SAP J2EE Engine, SAP supplies the IisProxy plug-in module for the IIS. This module replaces the SAPJ2EE ISAPI module that was supplied with Launch 6.20. The IisProxy module accommodates an ISAPI filter and an ISAPI extension. It consists of the dynamic hyperlink library IisProxy.dll (Filter and Proxy) and the corresponding configuration file IisProxy.xml. To help the usage of SSL, it uses the SAP Cryptographic Library.

The Internet Sales 4.0 Net functions have to be deployed with the Software Delivery Supervisor (SDM). ?? The next record contains a very powerful archives that should be deployed on the SAP J2EE Engine. For an entire checklist, seek the recommendation of the E-Promoting and Channel Management Installation Information:

  1. b2b.ear: This file incorporates the Web software SAP Web Sales Enterprise to Business Situation
  2. b2c.ear: This file accommodates a Web software for the SAP Internet Gross sales Business to Consumer State of affairs
  3. shopadmin.ear: This utility is required to manage the Shops, which ought to be available in
  4. your Net Store
  5. isauseradmin.ear: The User Administrator is a Internet utility to manage users within the back-end system
  6. webcatadmin.ear: The Net Catalog Administrator is a Internet software to manage your catalogs in a browser. It affords the same performance because the SAPGui of your again end.
  7. For all Web applications (ear files), you should maintain deployment parameters. They're described in the SDM Dialog.
  8. You must set the deployment parameter customer.config.path.xcm.config.isa.sapmarkets.com for all Internet applications (ear information). If you don’t set this path, you will not be able to configure your Internet application with the XCM - Admin. Set this parameter even when the SDM shows, that no parameter has to be set.
CRM Web Application XCM Administration

This tool is used to configure the Web application. XCM Administration is used after the installation of the Net component to configure settings needed during runtime. The XCM Administrator is out there with SAP J2EE Engine 620 SP11 or higher.The end result of configuration with XCM Administration is an utility configuration. There may be a quantity of application configurations. Every Internet utility provides one or more pre-defined configurations. Create a brand new customer configuration primarily based on one of many delivered SAP configuration and to adjust it to your needs. A buyer configuration consists of the following:
  1. Configuration identify
  2. Base configuration (the SAP configuration on which the client bases his configuration)
  3. Quite a few configuration parameters with associated values
  4. The XCM Administration tool is started utilizing the following URL: http://://admin/xcm/init.do. Enter a user/password (default: Administrator/empty password)
  5. The shopper information managed by XCM must be situated exterior the J2EE engine. The situation of those recordsdata is specified in the course of the SDM deployment of the appliance (context parameter:customer.config.path.xcm.config.isa.sapmarkets.com). The path have to be distinctive for each deployed application.
The situation of the client configuration data is situated in the folder specified utilizing the customer.config.path.xcm.config.isa.sapmarkets.com context parameter. There are two recordsdata used for this form of configuration:
  1. situation-config.xml: Comprises the totally different Web application configurations
  2. config-data.xml: Accommodates the totally different components configurations
  3. The XCM administration UI is used for configuration of these two files.
  4. Modification data isn't changed and due to this fact, not maintained by the XCM Admin tool. This buyer modification information is situated in WEB-INF/xcm/buyer/modification.
  5. If you plan to set up a J2EE cluster with several nodes assign a file share as an alternative of a direct path (e.g. \\sapmnt\\java\xcm\b2b for CRM ISA b2b, \\sapmnt\\java\xcm\b2c for CRM IS b2c). In that case, all cluster parts can share the identical configuration data.
  6. For information about usage of the XCM Administrator, seek advice from XCM Administrator.
  7. An software configuration defines the behavior of the application. Every application supplies one or extra pre-outlined configurations. Pre-defined configurations might be found within the SAP folder. By selecting this, you probably can entry the outline and default configuration.It is advisable to create new configuration primarily based on one of the configurations provided. Your new configuration can be placed within the Buyer folder.
Parts are elements of the application that can be configured independently. Every part has one or more pre-defined configurations that are delivered with the application. These configurations can be discovered within the SAP nodes of the control tree. Typically, it's important to create your personal configurations based on the default configurations. You do that within the Customer nodes of the control tree. Some parts present a configuration-check which helps to test your configuration. You should always use the check whether it is available.



SAP J2EE Engine

This configuration is utilized by the SAP Java Connector (JCo) for communication with the SAP system. It
relies on the Distant Operate Name (RFC) protocol. SAP system software server may be related straight (direct_connect) or utilizing load balancing via message server (group_connect).Maintain parameters in XCM Administrator (orange: value is derived from base configuration + should be changed by customer):
  1. Default language of the appliance, password, hostname, occasion quantity, consumer
  2. Consumer: For CRM E-Promoting, enter a user with person type Service and function SAP_CRM_ISA_ITSLOGIN
  3. A connection pool have to be used in order to entry the CRM server efficiently. The size of the connection pool is specified utilizing the parameter maxcon (most measurement of SAP JCo connection pool).
The value should be at the least twice as big because the number of concurrent users. Should you enhance this worth you should additionally regulate the CPIC_MAX_CONV surroundings variable. This variable specifies the maximum number of RFC connections the appliance server can handle concurrently (the bodily server, not the J2EE Engine). With one Net application (for instance, B2B), this worth should be twice as huge as the connection pool size.

Settings for the connection SAP J2EE Engine to the web server could be maintained in XCM Administrator. The parameter imageserver defines the directory the place to find mimes information for the merchandise which may be ordered using the product catalog.

Product Catalog

Making a product catalog allows you to present and sell your products within the Internet Store or by other media. To create a product catalog, in your SAP CRM System you must have created a fabric master and replicated this to the SAP CRM system. This product master is offered to the CRM system. You can create a product catalog as follows:
  1. You assign the product catalog you wish to create a number and a name and keep the data relevant to cost determination.
  2. You define the variants of the product catalog, specifying the number, language, foreign money and, if required, the name.
  3. You define how the product catalog is to be structured (the format) by creating structure areas. A structure area can both contain articles or different format areas assigned to it.
  4. You'll have the opportunity to assign multimedia objects (texts, pictures, or video animation, etc.) by method of the Document Management System to each structure space or article assigned. You too can enter long texts and headers (titles).
  5. To publish the catalog data within the World Wide Net, you need to set off a replication of the contents of the product catalog. Should you change the product catalog, set off a change replication of the contents of the product catalog. You can too make changes to the already revealed contents of the catalog.
  6. You can transport the product catalog knowledge in XML format. For example, you'll give you the chance to send the information to a enterprise companion or a printing company.
A product catalog is structured hierarchically. Every hierarchy level can include catalog areas in addition to product information. A catalog space itself might comprise additional catalog areas or product information.Optionally, there are any number of MIME objects (footage or different multimedia files) linked to each catalog space or product data.An instance for a catalog hierarchy would be an digital articles catalog of an electronics firm the place one prime level catalog space could be Electronic Elements and one other might be Products. Sub catalog areas of Digital Components is perhaps the areas Integrated Circuits and one other might be Resistors. Below the Resistors, there could be the products a hundred Ohm and 1000 Ohm and for each of these products there are jpeg information (photos) that present the true resistors with their colored rings.


Retrieval and classification

TREX offers an ABAP and a Java client. This enables ABAP and Java functions to make use of TREX functions. ABAP and Java functions talk with the TREX servers using totally different protocols and components.ABAP functions talk with TREX servers using the RFC protocol. Communication takes place using an instance of the SAP Gateway and an RFC server.Java applications talk with TREX using the HTTP or HTTPS protocol. This communication takes place using a Internet server that is enhanced with TREX-particular functions.For mySAP CRM Internet Gross sales, only the ABAP Consumer is used.You need:

An SAP Gateway installed on the TREX host for RFC calls outdoors the SAP Web Software
Server to the Index Administration Service (IMS).
  1. An RFC Server is the Index Management Service (IMS). The IMS consists of two layers: the ABAP administration and the Search Server. The first layer incorporates all administration data for the IMS and is positioned contained in the CRM Server. It provides ABAP operate modules for indexing and looking out documents and administering the indexes. The second layer (Search Server) is positioned outside the CRM Server. It implements communication by distant perform call (RFC) and offers an software programming interface (SAP Search Server API) for connecting totally different search engines like google and yahoo (for example, TREX or Veritas) ?? The TREX Server for indexing and searching within the Product Catalog.
  2. In order for the SAP System to give you the chance to ship indexing and search requests to TREX, you need to create RFC destinations.
  3. Two RFC destinations are required for connecting IMS/TREX and CRM Server:
  4. RFC Vacation spot IMSDEFAULT with activation sort = start for indexing documents.
  5. RFC Destination IMSDEFAULT_REG with activation kind = registration for looking out documents.
  6. Particulars for RFC Connection:
  7. IMSDEFAULT
This destination is used when product catalogs are printed and indexed.It's set to start the exterior program ims_server_admin.exe. This implies for each RFC call to publish a catalog, this program shall be began on the server the place the IMS/TREX component is installed. It'll really be began by the SAP gateway running on the IMS/TREX server. Due to this fact, the gateway options of the IMSDEFAULT RFC vacation spot need to be set to point to this SAP gateway.

IMSDEFAULT_REG This vacation spot is be used when full textual content search is needed. It is defined as a registered RFC server program named ims_server_regis.exe.Registered servers keep active ready for requests and aren't started every time when they're needed. This reduces response time at the cost of laptop assets as these processes don't terminate. When the IMS/TREX service (SAP_Retrieval_Service) is started, it begins a quantity of ims_server_regis.exe processes (by default three) and they register themselves on the local SAP gateway.From then on, RFC requires looking out might be despatched to this SAP gateway, which can distribute the calls over the accessible registered processes. Therefore, multiple search requests will be handled in parallel.Preserve the search server relation in CRM in transaction SRMO. In this transaction, a relation to an RFC destination is formed by approach of the search server relation.The search server relation setup can handle a number of search servers with completely different search engine types.In the CRM Internet Sales environment, there is just one used. The search engine that's shipped with CRM Web Sales is recognized as SAP TREX however the inside title of the search engine continues to be DRFUZZY.

Therefore, you have to enter this internal name here.As a consequence of efficiency problems with the productive system, you'll give you the option to adapt preliminary TREX settings. When the SAP Gateway is began on the TREX computer, several processes may be registered in the operating system to distribute the load (standard: two processes). To alter the variety of registered processes:
  1. Edit the file sapservice.reg in the set up path (for instance, Program Files\SAP\SAPTREX) in sub directory tune.
  2. For parameter Situations, enter the new variety of registered processes.
  3. To activate the modified settings, you could update the registry and restart the SAP Retrieval , and execute the file reconfigure.bat in the installation path in subdirectory tune. The batch file carries out the next steps: a) stops the SAP Retrieval Service; b) updates the registry; c) begins the SAP Retrieval Service.
The connection SAP J2EE Engine to IMS is configured using the ims component in XCM administrator. There are two potentialities to configure the connection utilizing parameter useDynConnParams:value true: default setting.

The values of the RFC destination to the IMS server are retrieved mechanically from the underlying SAP CRM system. When selecting this setting, you shouldn't have to specify every other parameter for this component.

The other risk is to manually specify the RFC vacation spot data within the XCM tool.Specify the right RFC connection parameters (gwhost, gwserv, tphost, and tpname) to the IMS server. To maintain these settings, use parameter useStaticConnParams.You probably can manually specify the connection parameters the place totally different IMS servers (on different machines) serve the same indexes. Completely different Web purposes on one Net server, or Net functions on completely different Internet servers, are due to this fact capable of entry completely different IMS servers, thus, implementing Web load balancing or high availability. The distribution and replace management of the indexes between such totally different IMS servers needs to be carried out by different mechanisms .

Product Catalog Definition of object

For the definition of publishing targets for the Product Catalog enter the Implementation Guide (Transaction SPRO).If you do not want to restrict entry authorization, do not enter a password and use the person ANONYMOUS which can be entered within the corresponding field.FTP Target Directory for Publishing describes the listing by which the HTTP publication took place.The FTP directory accesses a subdirectory of the HTTP listing, on the identical time. You need this listing to delete already published documents.


Product Catalog Initial ReplicationFor the catalog, it is advisable to specify the catalog title to be replicated. Replication means copying knowledge from the catalog stored within the CRM Server to the IMS/TREX and to the Net Server components. As this makes the catalog data additionally seen on the internet in an web gross sales situation, it's typically also known as publication.It's doable to define so-referred to as variants of a catalog throughout the product catalog maintenance in the CRM Server. This is only a simplification in case two catalogs are very similar. Below the run parameters, you have to specify the search server relation to be used to communicate with IMS/TREX for the catalog replication.The publishing pc ID is the publishing target that was entered in the customizing setup before . It's used to define the communication path to the Net Server for the replication of the MIME objects.

Product Catalog Index Staging

While the Catalog Replication is working the Catalog indexes will not be available. This time can be reduced if the index is staged to a standalone IMS (master) earlier than it's made accessible to the Web Middleware.Index Staging means to create an Index version on a standalone IMS or grasp and in a second step distribute the index directories recordsdata plus the configuration file bartho.ini to IMS/TREX servers connected to the Net middleware, the so known as slaves.Be sure, that no other indexing exercise is performed to TREX0. Stop the TREX service on TREX1 (these are by default the NT companies named SAP_Retrieval_Service and SAPGWS_47), copy the index directory (or at the least the sub directories containing the new or updated indexes) and the initialization file bartho.ini from TREX0 to TREX1and start the TREX companies on TREX1XML Export Of CatalogThis perform enables you to export variants of the product catalog, for instance, to ship to a enterprise partner. You utilize the SAP Enterprise Connector to ship the mapped XML file. Mapping is the method of adapting the XML file to the goal format of the receiver. For more information about mapping and the routing rules, see the integration information that is installed with the Business Connector.The next sending options can be found:
  1. Storing the XML file in a file system by calling the SAP Business Connector
  2. Ship to an HTTP port by calling the SAP Business Connector
  3. Send to FTP server, B2B service, Market by the routing rules of the Business Connector
  4. To begin XML export, select Master Knowledge ?? Product Catalog ?? XML-Export.
  5. Import of external product catalogs which are accessible in SAP XML, xCBL, Requisite XML or BMECAT, to the product grasp of your CRM system via the SAP Enterprise Connector is possible.
Make positive that you do not robotically generate product catalogs once you use this function. The XML import will be began within the following ways:
  1. In the SAP CRM system (see CRM Content material Management)
  2. Through the SAP Enterprise Connector: Additional info could be discovered within the documentation delivered with the SAP_catalog and SAP_catalog_customizing packages in the SAP Business Connector.
SAP Content material Server

If you want to administer a bigger amount of paperwork within the product catalog (for example, in CRM ESelling),you can use the SAP Content Server. Nonetheless, it's no must to use a content server. The SAP Content Server is accessed using HTTP. It is applied as a Internet server Plug-In and interfaces to SAPDB as storage system .During Catalog Creation, the paperwork are stored into the Content Server by the Catalog Administration in CRM.For Catalog information replication, the documents are retrieved from the Content Server and are handed down to the IMS TREX for indexing and then revealed on the Net server. The documents will not be held within the CRM Server. The Content material Server is used as an external storage system for the documents. 

Related Posts


SAP CRM Technology Overview
CRM Data Exchange with SAP R/3
CRM Data Exchange via Adapter
SAP CRM Organizational Model
People Centric SAP CRM Introduction
CRM Interaction Center Agent Perform

No comments :

Post a Comment