SAP BW 3.

5
October 2004
English

Building Block
Service Level: Order Items
Building Block Configuration Guide

SAP AG
Neurottstr. 16
69190 Walldorf
Germany
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and
Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies. Data contained in this document serves informational purposes
only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

© SAP AG Page 2 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

© SAP AG Page 3 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Content

Service Level: Order Items............................................................................................................. 5

1 Preparation.......................................................................................................................... 5
1.1 Prerequisites.................................................................................................................. 5
2 Configuration........................................................................................................................ 6
2.1 Customizing for the Extractors.......................................................................................6
2.2 Replicating DataSources for R/3 System.....................................................................11
2.3 Activating Business Content........................................................................................ 12
2.4 Loading Data............................................................................................................... 15

© SAP AG Page 4 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Service Level: Order Items

Use
This Building Block contains all the necessary configuration steps to install the InfoCube “Service
Level: Order Items” (Technical Name: 0SD_C12 ) in your SAP BW-System
This Cube enables you to make evaluations with respect to the service level on the order item
level. In this way, you can analyze, for example, the total number of order items for the share of
order items with late delivery.

1 Preparation
1.1 Prerequisites
Before starting activities in this Building Block, you need to perform or check the following steps:
1. BW Connectivity:
Local Settings  SAP R/3 the following activities have to be completed:
 Defining a Logical System for SAP R/3 (SAP R/3)
 Creating an RFC User (SAP R/3)
 Assigning Logical System to Client (SAP R/3)
Local Settings  SAP BW the following activities have to be completed:
 Defining a Logical System for SAP BW (SAP BW)
 Assigning Logical System to Client (SAP BW)
 Creating an RFC-User (SAP BW)
Cross Connectivity  SAP R/3 with SAP BW the following activities have to be completed:
 SAP R/3  Defining a Logical System for SAP BW (SAP R/3)
 SAP R/3  Connecting SAP BW (SAP R/3)
 SAP BW  Defining a Logical System for SAP R/3 (SAP BW)
 SAP BW  Connecting SAP R/3 (SAP BW)
 SAP BW  Creating R/3 Source System (SAP BW)
2. General Settings for BW Integration:
General Settings in R/3 for the following activity has to be completed:
 Transferring Application Component Hierarchy (R/3)
General BW Settings for the following activities have to be completed:
 Settings for Material Number Conversion
 Transferring Global Settings from R/3
 Maintaining Source System IDs

© SAP AG Page 5 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2 Configuration
2.1 Customizing for the Extractors
Use
This section describes the activities in an R/3 source system to set up the Customizing for the
Extractors.
These activities can be accessed in two ways:
1. As described in the subsequent sections from the SAP Business Warehouse
2. Directly from the source system. In the SAP Reference IMG look for the node Business
Information Warehouse or execute transaction SBIW.
Below the node Business Information Warehouse you will find all the described activities.
Search for the activities with the title of the chapter!

2.1.1 Transferring Business Content DataSources

Use
If you want to transfer data from a source system into a BW using a Business Content
DataSource, then you have to first transfer the data in the source system from the D version into
the active version (A version). This means that the necessary dictionary objects like extract
structures and so on are created on the database.
This activity is also required for the use of InfoCube Sales Overview (0SD-C03).
If you performed it already you do not have to do it again.
In that case you can skip this chapter.

Prerequisites
The activity Transfer Application Component Hierarchy (transaction RSA9) must have been
completed for your source system client.
Refer to the General Settings for BW Integration configuration guide.

Procedure
This step has to be carried out in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1

Then carry out the following steps:

1. In the Administrator Workbench: Modeling view in the SourceSystems tree, make a right
mouse click on the R/3 source system in the right-hand window and choose Customizing for
the Extractors.

© SAP AG Page 6 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

The BW system starts an RFC Call to the Source system client. If the logon screen of
your source system is displayed log on to your R/3 source system client. Otherwise
the Display IMG view is displayed immediately.
2. In the Display IMG view choose Business Information Warehouse  Business Content
DataSources  Transfer Business Content DataSources.
3. In the Installation of DataSource from Business Content view expand the node SAP-R/3.
4. Expand the node LO and select the node LO-IO. From the application toolbar choose Select
Subnode +/- (F9).
5. Expand the node SD and select the node SD-IO. From the application toolbar choose Select
Subnode +/- (F9).
6. From the node SD select the DataSource 2LIS_11_V_SSL. From the application toolbar
choose Select Subnode +/- (F9).
7. From the node SD select the DataSource 2LIS_11_VAITM. From the application toolbar
choose Select Subnode +/- (F9).

The selected DataSources, the selected nodes and all DataSources below the
selected nodes appear in different color in the view.
8. Once you have selected all required DataSources and nodes choose Trans. DataSources
from the application toolbar.
9. If a dialog box appears requesting the user to enter a development class enter the
appropriate development class and choose Save.
10. Choose Back twice to return to your BW system.

Result
You have transferred the DataSources for transaction data and master data that are required for
the InfoCube: Delivery Service to the active version.

2.1.2 Logistics Extract Structures Customizing Cockpit

Use
Administration of extract structures that are to be used to copy logistics movement-data from
Online Transaction Processing into the Business Information Warehouse.
This activity is also required for the use of InfoCube: Sales Overview (0SD-C03).
If you performed it already you do not have to do it again.
In that case you can skip this chapter.

Procedure
This step has to be carried out in the BW system.

© SAP AG Page 7 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

SAP BW Menu Modeling  Administrator Workbench: Modeling

Transaction code RSA1
1. In the Administrator Workbench: Modeling view in the SourceSystems tree make a right
mouse click on the R/3 source system in the right-hand window and choose Customizing for
the Extractors.

The BW system starts an RFC Call to the source system client. If the logon screen of
your source system is displayed log on to your R/3 source system client. Otherwise
the Display IMG view is displayed immediately.
2. In the Display IMG view choose Business Information Warehouse  Settings for Application-
Specific DataSources (PI)  Logistics  Managing Extract Structures  Logistics Extract
Structures Customizing Cockpit.
3. Expand the nodes Logistics applications  11:SD Sales BW  Extract structures.
4. For both extract structures MC11VA0ITM and MC11V_0SSL click on Inactive in column
Update of the line containing the extract structure.
5. If the system prompts you for a customizing request enter the appropriate customizing
request or create a new one. In the dialog box choose Continue.

The entry changes from Inactive to Active.

6. In the column Update Mode of the line containing the logistics application 11:SD Sales BW
the entry should be Direct Delta. If this is not the case click on the entry. In the Select Update
Mode dialog box select Direct Delta and choose Continue.

Choose Direct Update only if you are sure that there will be less than 10 000
document changes ( create, change/ process or delete delivery) per day in delivery
application.
For further information about the different update modes refer to SAP-NOTE 505700
7. On the dialog box choose Continue.
8. Choose Back twice to return to your BW system.

Result
You have activated the update of the extract structures.
Transaction data will be written into the extract structures from now on.

© SAP AG Page 8 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2.1.3 Deleting the Contents of the Setup Table

Use
In order to upload existing deliveries data to your BW you call up selected deliveries and trigger
the statistical update for the BW extraction structures for deliveries. To make sure that there is no
data in the relevant tables that has already been set up in this activity, you delete the content of
the respective tables before you trigger the statistical update for deliveries data.

Prerequisites
Before you can carry out this activity, you must have activated at least one extraction structure
per application. For more information, see Logistics Extract Structures Customizing Cockpit.

Procedure
This step has to be carried out in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1
Then carry out the following steps:
1. In the Administrator Workbench: Modeling view right-click the R/3 source system in the right
hand window and choose Customizing for the Extractors.

The BW system starts an RFC Call to the source system client. If the logon screen of
your source system is displayed log on to your R/3 source system client.
If you have logged on to the source system from your BW system during the current
session before the Display IMG view is displayed immediately.
2. In the Display IMG view choose Business Information Warehouse  Settings for Application-
Specific DataSources (PI)  Logistics  Managing Extract Structures  Initialization 
Delete the Contents of the Setup Table.
3. In the Delete setup data view in field Application enter 11.
4. Choose Execute.
5. Confirm the warning with Yes.
6. Choose Back twice to return to your BW system.

Result
You have deleted the content of the setup tables for deliveries. Now you can be sure that data of existing
deliveries is not stored twice in the setup tables if you trigger the statistical update.

2.1.4 Performing Setup - SD Sales Orders

Use
In order to upload existing deliveries data to your BW you call up selected Sales Orders and
trigger the statistical update for the BW extraction structures for existing invoices.

© SAP AG Page 9 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Completing setup tables is a critical action, that should be carried out with caution.
For large data amounts, this can take longer than one night and may have to be done
at the weekend. Or the setup should be split up into several parts.

Procedure
1. Carry out the following step in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1
2. In the Administrator Workbench: Modeling view in the Source Systems tree, make a right
mouse click on the entry R/3 Source System and select Customizing for the Extractors.

The BW system starts an RFC Call to the Source system client. If the logon screen of
your source system is displayed log on to your R/3 source system client. Otherwise
the Display IMG view is displayed immediately.
3. In the Display IMG view choose Data Transfer to the SAP Business Information Warehouse
à Settings for Application-Specific DataSources (PI) à Logistics à Managing Extract
Structures à Initialization à Filling in the Setup Table  Application-Specific Setup of
Statistical Data  SD-Sales Orders - Perform Setup.
4. On the Statistical Setup from Old Dokuments: Orders screen make the following entries:
Field Entry
Name of run Any name
New run X
Date of Termination Enter a date in the future (e.g. tomorrow)
Time of termination Time in the future
No. tolerated faulty Any number, e.g. 99
documents
5. Choose Execute.
6. In the Information dialog box confirm the message with Continue.
7. Choose Back twice to return to your BW system

Result
You have triggered the statistical update for the BW extraction structures for existing sales
orders. The data is available to be uploaded to BW.
The statistical update used here corresponds to the method you chose in the Logistics Extract
Structures Customizing Cockpit.In order to upload existing deliveries data to your BW you call up
selected deliveries and trigger the statistical update for the BW extraction structures for existing
deliveries. This activity is also part of the configuration of building block Sales Analysis.

© SAP AG Page 10 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2.2 Replicating DataSources for R/3 System

Prerequisites
Connectivity between SAP BW and SAP R/3 has been set up. DataSources have been created or
activated in the R/3 Source System.

Procedure
This activity has to be carried out in the BW system:
SAP Role Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1
In the Administrator Workbench: Modeling view make a right mouse click on the entry R/3 Source
System in the right-hand window and choose Replicate DataSources.

To check the replication of the DataSources make a right mouse click on the entry
Source System in the right-hand window and choose DataSource overview.
In the right frame choose Update Tree. The DataSources from your R/3 system are
displayed in another frame.
The DataSources that you have activated before should be visible.

© SAP AG Page 11 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2.3 Activating Business Content

2.3.1 Assigning Source System for Activation
Use
When you activate Business Content, DataSources from source systems are assigned to
InfoSources in BW. If you do not select a source system, all source systems are automatically
assigned. If you have several source systems, this may take a lot of time because also transfer
rules have to be activated for each DataSource from each source system.
However, an assignment of a DataSource to an InfoSource may not be necessary for all existing
source systems.
Assign only the source systems you need to load data from for the Business Content Objects that
you are going to activate.
You can subsequently change the selection you made.

The assignment of source systems is only relevant for transfer rules, file
DataSources and InfoPackages. If there is more than one source system, only those
objects assigned to the specified source system are collected for the transfer.
Objects that have not been assigned to the specified source systems are ignored.

Procedure
To assign a source system, choose:
SAP BW Menu Modeling  Administrator Workbench: Business Content
Transaction Code RSORBCT
Then carry out the following steps:
1. In the Administrator Workbench: Business Content view choose Edit  Source System
Assignment.
2. On the Choose source system by default? dialog box make sure that the checkbox in the
column Default assignment is selected only in the row containing the source systems you
need to load data from.
3. Choose Continue.

Result
By assigning the source systems, you limit the assignment to the DataSources from the assigned
source systems only. This reduces the time for activation.

2.3.2 Activating Business Content: InfoObject Catalogs

Procedure
This activity has to be carried out in the BW system:

© SAP AG Page 12 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

SAP BW Menu Modeling  Administrator Workbench: Business Content

Transaction code RSORBCT
Then carry out the following steps:
1. On the Administrator Workbench: Business Content screen:
a. At the top of the right frame, choose Grouping and select only necessary objects.
b. At the top of the right frame, choose Collection mode and select collect automatically.
c. In the left frame, select Object types.
d. In the middle frame, expand InfoObject Catalog and make a double-click on Select
Objects.
2. In the Input help for Metadata dialog box.
a. Select the following InfoObject catalogs:
InfoObject Catalog InfoObject Catalog
(technical name) (description)
0SD_DLV_CHA01 Delivery Service: Characteristic
0SD_DLV_KYF01 Delivery Service: Key figures

For multiple selection keep the Ctrl-Key pressed and select all the objects you want
to activate with the left mouse button.
b. Choose Transfer selections.
c. If a dialog box appears Exceeded runtime when collecting objects choose Continue.
3. At the top of the right frame, choose Install and select Install in Background.
4. In the Install Business Content in the Background dialog box choose Yes.
5. In the Information dialog box choose Continue.
6. Choose Exit.

2.3.3 Activating Business Content: InfoCubes

Procedure
This activity has to be carried out in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Business Content
Transaction code RSORBCT
Then carry out the following steps:

© SAP AG Page 13 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

1. On the Administrator Workbench: Business Content screen:

a. the top of the right frame, choose Grouping and select in dataflow before.
b. the top of the right frame, choose Collection mode and select Collect automatically.
c. the left frame, select Object types.
d. the middle frame, expand InfoCube and make a double click on Select Objects.
2. In the Input help for Metadata dialog box:
a. the InfoCube 0SD_C12 (Service Level: Order Items).
b. Transfer selections.
c. a dialog box appears Exceeded runtime when collecting objects. Choose Continue.
3. At the top of the right frame, choose Install and select Install in Background.
4. In the Install Business Content in the Background dialog box choose Yes.
5. In the Information dialog box choose Yes.
6. Choose Exit.

© SAP AG Page 14 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2.4 Loading Data

2.4.1 Loading Master Data / Texts / Hierarchies
Use
This section describes the procedure for loading master data texts and hierarchies into SAP BW.

For further information about loading master data/texts/hierarchies refer to Building

Block Working with SAP BW: Essential Information.

Procedure
If there is no master data in the Source systems, do this step later and go to the next activity.
This activity has to be carried out in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1
Then carry out the following steps in the Administrator Workbench: Modeling view in the
InfoSources tree for each relevant Infosource that you need to load data to ( see table below ):
1. Select the Source System below the InfoSource and choose Create Info Package from the
context menu.
a. In the Create InfoPackage dialog box you can see all assigned DataSources.
b. Make the following entries:
Field Entry
InfoPackage description Any name
c. Select one DataSource.
d. Choose Save.
2. On the Scheduler (Maintain InfoPackage) screen:
a. If you want to load master data hierarchies choose the Hierarchy Selection tab.
Otherwise proceed with step c.
b. On the Hierarchy Selection tab make the following changes:
 Click Available Hierarchies from OLTP.
 Choose the hierarchies you want to upload by clicking the radio box.
 Tick the checkbox of the selected hierarchies.
c. Choose the Processing tab and make the following entries:

Field Entry
PSA and then in the InfoObject X
d. Choose the Update parameters tab and make the following entries:
Field Entry
Full update X

© SAP AG Page 15 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

e. Choose the Schedule tab and make the following entries:

Field Entry
Start data load X
immediately
f. Choose Start.

For testing purposes you can start the job immediately.

In productive BW systems you should start the job later in the background.

Create an InfoPackage for all DataSources you need.

You don’t have to load data from all DataSources just for the characteristics you
want to be displayed in your queries. The following list contains all the
InfoObjects (Characteristics) that are included in the InfoCube. You will need at
least Master data for the plant and the company code.

Info Object Description

0DLV_STS Delivery status

0DLV_STSO Overall delivery status of order item

0MATERIAL Material

0SOLD_TO Sold-to party

0COMP_CODE Company code

0CUST _GROUP Customer group

0CUST _GRP1 Customer group 1

0CUST _GRP1 Customer group 2

0CUST _GRP3 Customer group 3

0CUST _GRP4 Customer group 4

0CUST _GRP5 Customer group 5

0DISTR_CHAN Distribution channel

© SAP AG Page 16 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

0SALESEMPLY Sales employee

0SALES_GRP Sales group

0SALES_OFF Sales office

0SALESORG Sales organization

0MATL_GROUP Material group

0MATL_GRP_1 Material group 1

0MATL_GRP_2 Material group 2

0MATL_GRP_3 Material group 3

0MATL_GRP_4 Material group 4

0MATL_GRP_5 Material group 5

0PROD_HIER Product hierarchy

0PLANT Plant

0SHIP_TO Ship-to party

0SHIP_POINT Shipping point

0DIVISION Division

0FORWAGENT Forwarding agent

0PAYER Payer

© SAP AG Page 17 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

2.4.2 Loading Transaction Data

Use
If there is no data in the source systems, complete this activity later and go to the next activity.

Prerequisites
The R/3 source system has been connected to the SAP BW.
In the R/3 source system the customizing for the extractors has been set up.
In SAP BW the Business Content has been activated.

Procedure
This activity has to be carried out in the BW system:
SAP BW Menu Modeling  Administrator Workbench: Modeling
Transaction code RSA1
In the Administrator Workbench: Modeling view in the InfoSources tree perform the following
activities for each of the relevant InfoSources (see table below):
1. Select the Source system below the InfoSource.
a. From the context menu choose Create InfoPackage.
b. In the Create InfoPackage dialog box: Make the following entries:
Field Entry
InfoPackage description Enter a description
c. Select the DataSource.
d. Choose Save.
2. On the Scheduler (Maintain InfoPackage) screen:
a. Choose the Processing tab and make the following entries:
Field Entry
PSA and then into data X
targets (packet by
packet)
b. Choose the Data targets tab and make the following entries:
Field Entry
Update in all data X
targets for which active
rules exist
c. Choose the Update tab. Here you have the following options for the update mode:
Update Mode Description
Full Update A full update requests all data that corresponds to the
selection criteria you determined in the Scheduler.
If you load data the first time and you want to load all
existing data into BW, choose update mode Full update

© SAP AG Page 18 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Delta Update A delta update only requests data which has appeared
since the last loading of data from the DataSource.
Choose this update mode for periodic upload of
transaction data.

A delta update is only possible for loading from

SAP source systems.
Before you can request a delta update, you must first
initialize the delta process (see next table row).
Initialize delta process To request deltas, you need to have initialized the delta
process.

Actually this is an The delta process is initialized when a data loading

indicator for the source request with update mode Initialize delta process has
system that from now on been executed succesfully. Then it has the status green
only newly created or in the administrator workbench monitor.
changes/deletions of
transaction data are to If there is no data found in the source system the
be transferred to SAP request remains with status amber!
BW. To make sure that the request is executed successfully
even if there is no data yet in the source system select
the checkbox Initialize Without Data Transfer!
d. Choose the appropriate update mode. We recommend to select also the button Always
update data, even if no master data exists for the data.

The update mode refers only to the data that meet the selection criteria that you
insert on the Data Selection tab.
e. Choose the Schedule tab and make the following entries:
Field Entry
Start data load X
immediately
f. Choose Start).

For testing purposes start the job immediately.

In productive BW systems you would start the job later in the background.

Relevant InfoSources

InfoSource InfoSource
( technical name ) Description

2LIS_11_V_SSL Sales Document: Order Delivery

2LIS_11_VAITM Sales Order Item Data (As of 2.0B)

© SAP AG Page 19 of 20
SAP Best Practices Building Block Service Level: Order Items: Configuration Guide

Result
Depending on the update mode you chose either data is loaded into the data target and/or the
delta process is initialized in the source system.

The success of the initialization of the delta process can be checked in the source
system in transaction RSA7 (Delta Queue Maintenance). If the initialization has been
successful for an InfoSource, you will find the corresponding data source (with the
same technical name) in the view with status green.

© SAP AG Page 20 of 20