SAP ABAP IMG Activity ESH_SD_ANLY (Overview: Operational Reporting/Search with Enterprise Search and BWA)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ SD (Application Component) Sales and Distribution
     ⤷ ERP_SD_ANALYTICS_CORE_TR (Package) Sales, Billing and Delivery Analytics - Translation Relevant
IMG Activity
ID ESH_SD_ANLY Overview: Operational Reporting/Search with Enterprise Search and BWA  
Transaction Code S_EBS_44000357   (empty) 
Created on 20110120    
Customizing Attributes ESH_SD_ANLY   Overview: Operational Reporting/Search with Enterprise Search and BWA 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ESH_SD_ANLY    

Use

Under Enterprise Search, you perform various activities in order to integrate the powerful SAP NetWeaver Enterprise Search for use in search and analytics in the areas of Sales, Shipping, and Billing.

This document contains an overview of all activities you need to perform. In Customizing (IMG), you can find more information in the documentation for the individual activities.

Requirements

You have installed SAP NetWeaver Enterprise Search in a version whose SAP NetWeaver Search and Classification (TREX) component is also used in SAP NetWeaver Business Warehouse Accelerator (BWA).

Standard settings

Activities

Activate ABR Delta Method for Allocation of Sales and Shipping Data

The search and analytics models for the allocation of sales and shipping data (0OPS_11_V_ITM_T01 and 0OPS_11_V_SCL_T01) are based on DataSources 2LIS_11_V_ITM and 2LIS_11_V_SCL, which the delta update in the standard system cannot transfer entirely using the ABR delta procedure.

When you create or delete a delivery, the system returns additive records for the two DataSources, in accordance with the ADD delta method. This logic is not suitable for indexing an SAP NetWeaver BW Accelerator (TREX). This requires the entire delta update to run using the ABR delta method.

If you want to keep this data in indexes in SAP NetWeaver BW Accelerator (BWA), use this activity to specify that all delta records for the corresponding DataSources are updated using the ABR delta method.

To do this, activate the ABR delta method in the Activate Analytics activity.

Switching to the ABR delta method throughout has no effects on data updates in SAP Business Warehouse, as the ABR delta method supports both additive and overwriting updates.

Note:If you activate Analytics and at the same time change the updates of the affected key figures in BI Content to Overwrite, it is no longer possible to turn off the function retroactively. Doing so would result in faulty key figures in BI. We recommend that you do not turn off the function.

Create Search Object Connectors

At query runtime, the search object connector creates a connection between the TransientProvider and SAP Enterprise Search. The TransientProvider is based on a search and analytics model.
As well as containing other settings, the model determines the search attributes that the system uses to search for each business object (for example, for orders or customers).

To create search object connectors, perform the following steps:

  • Create the search object connectors To do so, choose Open Administration Cockpit.
    For each search and analytics model that is defined for movement data in Sales, Shipping, and Billing, you need a search object connector.
  • Choose Create. The system displays a dialog box, in which you select the software component SAP_APPL .
    Note: In some cases, the software component SAP_APPL is not available. If that is the case, select, for example, SAP PLM-Web-UI PLM/WUI, or select a software component that depicts SAP_APPL.

    The system displays a list of models in the selected software component, including search and analytics models for Sales, Shipping, and Billing (for example 0OPS_11_VAHDR_T01).
    Select a model. The system generates the connector using various pieces of technical data. For example, the system reads the data structure from the search and analytics model and generates the search structure from it.

Prepare Setup Tables

When determining SD data to be indexed, the system uses selection programs for the setup of statistics data from legacy documents. It then adds the data to the setup tables.

The following process is described in SAP note 602260 (Procedure for Reconstructing Data for BW) with further details and examples.

Note: So that the system can create the setup tables for indexing, the relevant search object connectors must exist before setup.

Caution: Perform setup during a period when there are no postings.

Background:You must not make any changes to existing data while the system is reading legacy documents from the database and writing them to the setup tables. For example, if you change orders during statistics setup, the system cannot include these changes in the setup. In the worst case, this might result in incorrect statistical values, requiring the system to perform setup again.

To prepare setup, proceed as follows:

  1. Lock all users.
  2. Lock all update tasks, for example jobs for backorder processing, order creation by EDI or service.
  3. To ensure that no more data is waiting to be posted, proceed as follows:
    • Check the activation status of the extract structures. If you selected the queued delta posting method, check the RFC Monitor: Outbound Queue (transaction LBWQ).
      If data for the Sales, Shipping, or Billing application (application number 11, 12, or 13) is still in the queue, post this data by starting the relevant posting report RMBWV3nn (nn = application number) directly in transaction SA38.
      • If you selected the delta direct posting method, this step is not necessary.
    • Load all the data from the BW delta queue (transaction RSA7) into the SAP Business Warehouse. This empties the extraction queues.
  4. To delete the data in the setup tables, perform the Delete Data in Setup Tables activity.
    By deleting, you ensure that no data is left in the setup tables when you perform indexing. If you do not delete, it is possible that after setup, for some objects (for example orders), several data records exist for the same object.
  5. Activate the business function Sales and Distribution, Analytics 01 (LOG_SD_ANALYTICS_01).

    Activating the business function adds new fields to the DataSources. This does not add to the standard BI content delivered by SAP. However, you can use the new fields for your own BI content and for analytics in SAP NetWeaver BW.

    For more information on the new DataSource fields, see SAP Help Portal under http://help.sap.com -> SAP ERP -> SAP ERP Central Component -> Logistics -> Sales and Distribution (SD) -> Operative Reporting in Sales and Distribution -> DataSources.

  6. If you have not yet activated the new version of the DataSources using Direct Access, activate it using transaction RSA5.
  7. In the Logistics Customizing Cockpit (transaction LBWE), check that the update is active for all DataSources mentioned below.

DataSource    Description

2LIS_11_VAHDR    Sales Document Header Data

2LIS_11_VAITM    Sales Document Item Data

2LIS_11_V_ITM    Sales Shipping Allocation Item Data

2LIS_11_VASCL    Sales Document Schedule Line

2LIS_11_V_SCL    Sales-Shipping Allocation Schedule Line

2LIS_11_VAKON    Sales Document Condition

2LIS_12_VCHDR    Delivery Header Data

2LIS_12_VCITM    Delivery Item Data

2LIS_13_VDHDR    Billing Document Header Data

2LIS_13_VDITM    Billing Document Item Data

2LIS_13_VDKON    Billing Document Conditions

  1. Activate the content.

    Activate the respective BI content in Customizing activity Start BI Content Activation Workbench. Under the business category 03(Business Functions), in the Activation of Sales Analytics content bundle (LOG_SD_ANALYTICS_01), all content objects are gathered together that were created for Sales, Shipping, and Billing.

    You can include the activated content objects in a transport request and transport them to a production system. If you use a Business Warehouse Accelerator, you have to create the connectors again manually in the production system.

Fill Setup Tables

You can perform setup for selected documents. The system determines the documents according to the selection criteria entered, and initializes the statistics update accordingly.

Perform setup for the required area:

Perform Indexing for Search Object Connectors

Once the system has generated the search object connectors and filled the setup tables, start indexing for TREX.

You can find the next processing steps based on the current processing status in input help for Actions.

  • For scheduling indexing, the connector must have the status Prepared.
  • As soon as you choose Schedule Indexing, the system displays a dialog box for&#x
Business Attributes
ASAP Roadmap ID 207   Establish Reporting 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ESH_SD_ANLY 0 HLA0009600 O HLA0009602  
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20110725 
SAP Release Created in 606