Kontakt

Ansicht
Dokumentation

New features in CRM Middleware ( RELNCRM_30A_MIDDLEWARE )

New features in CRM Middleware ( RELNCRM_30A_MIDDLEWARE )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

New features in CRM Middleware

With Release 3.0, SAP CRM Middleware now supports additional, heterogeneous scenarios such as a mySAP CRM solution scenario without an SAP R/3 backend system or, with some restrictions, with multiple SAP R/3 backend systems.

Many mySAP CRM scenarios do not require replication to mobile clients.

Taking into account the increased importance of SAP CRM Server applications, a number of enhancements to SAP CRM Middleware have been implemented.

While the business content of messages to be replicated to mobile clients must be made persistent in a consolidated database, replication to other sites does not require such a persistence layer.

Key enhancements have therefore been made in the message processing model. Standard flow contexts can be used for outbound and inbound messages. This implies changes to the replication mechanism and the creation of new interfaces between the SAP CRM Server applications and SAP CRM Middleware.

New User Roles

The following composite roles are available in the CRM Server.

  • Administrator role:,,SAP_CRM_MW_ADMINISTRATOR
  • Developer role: ,,SAP_CRM_MW_DEVELOPER
  • Customizing role: ,,SAP_CRM_MW_CR_CUSTOMIZING

Each composite role is a collection of single roles.

Customers can change these roles or create their own roles by selecting SAP R/3 -> Tools -> Administration -> User Maintenance -> Roles.

If you want to use the SAP WebGUI, you must upload the composite roles to your SAP Workplace server. Note that the Administration Console and the Communication Monitor do not support the SAP WebGUI.

New Categories of BDoc Types

  • Messaging BDocs (mBDocs)
The message exchange with SAP CRM Server Applications, SAP R/3, and external systems now takes place within the SAP CRM Middleware using mBDocs exclusively. Outside of the SAP CRM system, these mBDocs are presented as external XML and IDoc interfaces in a mapping function.
mBDocs are not exchanged with mobile clients and are not stored in the CDB. Therefore, mBDocs are not limited to CDB structures. SAP CRM Server application scenarios do not require data replication with a realignment function.
mBDocs consist of the following parts:
  • Hierarchical segment structure (modeled with the BDoc Modeler)

  • Optional container for additional data (of complex data type, modeled in the Data Dictionary)

  • Synchronization BDocs (sBDocs)
Synchronization BDocs are the BDocs used for communication with mobile clients, which means, BDocs that are stored in the CDB.
  • Mobile Application BDocs
Mobile application BDocs are processed only outside the CRM Server. They are used by SAP CRM mobile applications. Mobile application BDocs also support mass processing as far as data exchange with the local persistence layer is concerned.

Mapping functions are provided for sBDocs and mBDocs.

In some flow contexts, sBDocs and mBDocs support mass processing, which means several business objects can be distributed in one BDoc. Post-processing is possible when the processing is only partly successful.

BDoc Modeler

The new BDoc Modeler is available in the CRM Server with role-based functions.

It has the following enhancements:

  • Modeling of mBDoc types
  • Assignment of an sBDoc type to an mBDoc type (n:1 relationship)
  • Assignment of site types to sBDoc and mBDoc types
  • Data type information for segment fields

New Site Types

New site types allow Flow Control to send BDoc messages to sites other than mobile clients. For example, OLTP R/3 is now a new standard site type.
Additional new site types may be created to extend the CRM landscape.

Message Flow Control and Error Handling

New flow services and interfaces support the enhanced message processing model :
  • Service for mapping sBDocs to mBDocs
This mapping service takes one sBDoc and produces exactly one mBDoc of exactly one predefined type (n:1 relationship).
  • Validation service for the SAP CRM Server applications (CRM Adapter)
The validation service is called from the synchronization flow or initial download flow to validate the inbound BDoc in the CRM Server applications.
  • Simple replication service for mBDoc types
This replication service does not provide CDB access for mBDoc types. Therefore, there is no realignment function. This service is used for data transfer to OLTP R/3 sites.
  • Service for mapping mBDocs to sBDocs
This mapping service takes an mBDoc and creates one or more sBDocs (1:n relationship).
Different flow contexts are available. A flow context is an informally described step in the general processing model of BDocs. Flow contexts are predefined and are associated with lists of services to be called in this context.

Error handling has been enhanced to take into account the new message processing model. Message exchange with an OLTP R/3 system either triggers a new flow by creating a new response BDoc or updates the status of the BDoc sent.

Data Exchange with OTLP SAP R/3

You can filter the load data in OLTP SAP R/3.

The Adapter Framework has been enhanced as follows:

  • The adapter service is no longer called in the main message flow.
  • Several SAP R/3 backends can be maintained, with some restrictions. They are treated as site type R/3 in the Administration Console.
  • The Adapter Framework receives data through the replication mechanism.
  • Status tracking is available for each object instance and R/3 site.
  • Predefined filter criteria are available for adapter objects.

You can configure different kinds of data load per BDoc type in object management:

  • Initial load
The following flow contexts are used for initial data loads:
  • Validate,,From OLTP R/3 to CRM (SAP CRM Server applications)

  • Initial Load ,,From CRM to CDB

  • Direct Send ,,From CRM to any allowed non-mobile site

  • Delta load
The Validate flow context is used in most cases. It is used, for example, when mobile clients, SAP R/3 and others receive delta data from any sending system.
  • Load to OLTP R/3
The Adapter Framework is called using the outbound adapter. The central upload function module is called directly and returns status information from OLTP R/3.

Site-Specific Filtering

For the new mBDoc types, a function module is provided that determines the segments (of the classical BDoc part) for which filter criteria are not fulfilled. The application program deletes this data and any related data (especially in the enhanced BDoc part).

Loading of Customizing Data

The following initial load contexts can be used for a two-step loading of customizing data:

  • Validation
From SAP R/3 to the SAP CRM Server applications.
As long as an SAP R/3 System is available, customizing settings can be downloaded to the SAP CRM Server applications.
  • Initial Load
From the SAP CRM Server applications to the CDB.
Customizing settings can be enhanced and changed in the CRM application before they are passed to the CDB for replication to the mobile clients. During the transfer, mBDocs are mapped to sBDocs. This kind of customizing data load can also be used in a CRM standalone scenario without an OLTP system.

Data Exchange with Non-SAP Systems

The external Interfaces (XIF) Adapter provides interfaces that support XML and IDocs.

Initial data load from non-SAP systems to the CRM Server can take place entirely using the SAP Data Transfer Workbench and the external CRM interfaces for IDocs.

Administration Console

The Admin Console is available in the CRM Server with role-based functions.

It provides the following new features.

  • New field for object name
The Object name field is a new optional entry field in the navigation area of the user interface. Entering an object name limits the number of objects to be displayed in the navigation window.
  • New types of replication objects
Following the introduction of mBDocs, two new replication objects are available based on mBDocs:
  • Simple intelligent (msg)

A simple intelligent replication object of type msg has the same properties as a conventional simple intelligent replication object of type sync, but it is based on an mBDoc rather than on an sBDoc.
In contrast to a replication object of type sync, a replication object of type msg has no look-up table. Therefore, no automatic realignment is performed. Replication is based on a recipient list, which must be determined each time.
  • Simple bulk

A replication object of type simple bulk has properties similar to a replication object of type bulk, but it is based on an mBDoc, rather than on an sBDoc.
In contrast to a replication object of type bulk, a replication object of type simple bulk has no look-up table. Therefore, no automatic realignment is performed. Replication is based on a recipient list, which must be determined each time.
  • New publication types
Following the introduction of mBDocs, two new publication types are available that have replication objects assigned to them that are based on mBDocs:
  • Simple intelligent (msg)

A simple intelligent publication of type msg is one that has only one simple intelligent replication object assigned to it that is based on an mBDoc.
  • Simple bulk (msg)

A simple bulk publication of type msg is one that has one or more replication objects assigned to it, which can be sent to sites completely, and are based on mBDocs.
  • Site type selection
Following the introduction of new site types, a site type must be selected when creating a new site. In addition to the site type selection, the relevant site attributes must be selected.
  • New functions for SAP BW data extract
Functions for extracting information from BW systems are enhanced as follows:
  • User Mapping

Mapping of BW users to mobile sales users using an option on the initial screen
  • Clear up of BW Variants

Clear up of variant definitions and user mappings using an option on the initial screen. The clear up is not performed automatically, which prevents the removal of variant definitions that are no longer used.
  • General BW Variant

User-independent variant definition using an option in the query details view
  • User Variants

User-specific variant definitions using an option in the user overview
  • Preview Variants

A preview of variants that can be called from both definition screens
The query and user detail screens have extra fields to provide the new information and to adapt to the enhanced workflow.

Monitoring

Message flow

The Display Message Flow Statistics function (SMWMFLOW) has been adapted to the new structure of message processing with a new or enhanced user interface.

Middleware trace

The Middleware Trace Monitor is a tool for tracing events and displaying such information. It replaces the Flow Trace and Middleware Log functions.

It has the following features:

  • Information storage

  • User interface for displaying the stored information

  • Tool for exporting and storing data as simple text files

  • Reorganization tool for cleaning up the database

The traced data is first stored in the Trace Buffer within the global memory. Particular events trigger an automatic buffer flush, which saves the buffer content in the database.

Database Recovery for Mobile Clients

If a mobile user's laptop computer becomes unusable, a replacement may be the fastest solution.

You can use the Mobile Client Recovery Manager to transfer all relevant data from the CRM Server to a replacement laptop computer.

Use

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 15206 Date: 20240520 Time: 203636     sap01-206 ( 237 ms )