4 Basic Configuration AFS PP

7/27/2019 4 Basic Configuration AFS PP

http://slidepdf.com/reader/full/4-basic-configuration-afs-pp 1/8

SAP BW 7.0

August 2007

English

BS3: Basic Configuration

– AFS ProductionPlanning

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices Basic Configuration – Sales Analytics: Configuration Guide

Copyright

Copyright 2007 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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents 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, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarksor registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks of Adobe Systems Incorporated 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World WideWeb 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, SAP NetWeaver, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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. Datacontained in this document serves informational purposes only. National product specificationsmay 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 representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are setforth 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 8




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 fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

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 keywords 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 asnames 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 thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.





Content

Basic Configuration – Sales Analytics.............................................................................................5





Basic Configuration – Sales Analytics

1 UseThis configuration guide describes all the necessary activities to load the sales analytics master

data as well as other activities, which are a prerequisite for the installation of the different buildingblocks, which comprise the Sales Analysis scenario.

2 Prerequisites

Connectivity between SAP ERP and BI has been set up. Refer to the relevant sections of the BI Connectivity building block.

General BI settings have been made. Refer to General Settings BI Integration building block.

3 Configuration

.3.1 Customizing for the Extractors3.1.1 Transferring Business Content DataSources

Use

If you want to transfer data from a source system into a BI using a Business Content DataSource,then you have to first transfer the data in the source system from the D version into the activeversion (A version). This means that the necessary dictionary objects like extract structures andextraction programs are created on the database.

Prerequisites

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

Procedure

SAP BI Menu Modeling Data Warehousing Workbench: Modeling

Transaction Code RSA1

Carry out the following steps:

1. In the Data Warehousing Workbench: Modelling in the left hand frame choose the SourceSystems tree.

2. In the right hand frame expand the node SAP and make a right mouse click on your SAPERP source system. From the context menu choose Customizing Extractors.

3. If the system prompts you to log on to your source system client enter the correspondinguser-id and password.

4. The Display IMG screen is displayed. Expand the node Data Transfer to the SAP Business

Information Warehouse Business Content DataSources.

5. Choose Transfer Business Content DataSources.





6. In the Installation of DataSource from Business Content view expand the node SAP-R/3 (SAP Application Components) mark the relevant DatasSources or the complete nodes (see table

below) and choose Select Sub-tree +/- .

7. Once you have selected all required DataSources and nodes from the application toolbar choose Activate DataSources.

8. An Information dialog box might appear. Choose Continue.

9. Use the Back button ( several times) to return to the Data Warehousing Workbench:Modelling view of your SAP Business Warehouse.

Relevant Data Sources

Path Relevant DataSources(technical name)

Description

PP PP-IO All Data Sources All Data Sources

PP 2LIS_04_P_MATNR Article View from PP/PP-PI

PP 2LIS_04_P_COMP Component View from PP/PP-PI

ROOT IS-AFS 2LIS_AF_PABDSI AFS Requirements (Production Order)

ROOT IS-AFS 2LIS_AF_PABSSI AFS Stock (Production Order)

SAP-R/3-IO All Data Sources All Data Sources

1. Once you have selected all required DataSources and nodes choose Activate DataSourcesfrom the application toolbar.

If a dialog box appears requesting the user to enter a development class enter theappropriate development class and choose Save.

2. Choose Back to return to the Display IMG view.

Result

You have transferred the DataSources for transaction data and master data that are required for Sales Analysis analysis to the active version.

3.1.2 Logistics Extract Structures Customizing Cockpit

Use

Administration of extract structures that are to be used to copy logistics movement-data fromonline transaction processing into the Business Information Warehouse.

Procedure

This step has to be carried out in the SAP ERP system.

IMG Menu Integration with Other mySAP.com Components Data Transfer

to the SAP Business Information Warehouse Settings for





Application-Specific DataSources (PI) Logistics Managing

Extract Structures Logistics Extraction Structures Customizing Cockpit

Transaction Code LBWE

Then carry out the following steps:

1. Expand the nodes Logistics applications 04:Shop Floor Control Extract structures.

For the extract structures 2LIS_04_P_MATNR and 2LIS_04_P_COMP below the node click onInactive in column Update of the line containing the extract structure

2. In the Notifications MCEX 146 dialog box choose Continue. The entry changes from Inactive to Active.

If the system prompts you for a customizing request enter the appropriatecustomizing request or create a new one.

3. In the column Update Mode of the logistics applications ( 04 – Shop Floor Control ) the entryshould be Direct Delta. To change the entry click on it. In the Select Update Mode dialog boxselect Direct Delta and choose Continue.

4. Choose Back to return to the Display IMG view.

Result

You have activated the update of the extract structures.

Transaction data can be written into the extract structures from now on. (subsequent activitiesmust be completed as well)

3.1.3 Deleting the Contents of the Setup Table

Use

In order to upload existing transaction data to your BI you call up selected data records of salesand trigger the statistical update for the BI extraction structures for sales orders. To make surethat there is no data in the relevant tables that has already been set up in this activity, you deletethe content of the respective tables before you trigger the statistical update for sales orders data.

Prerequisites

Before you can carry out this activity, you must have activated at least one extraction structureper application. For more information, see previous chapter Logistics Extract Structures

Customizing Cockpit .

Procedure

This step has to be carried out in the SAP ERP system.

IMG Menu Integration with Other mySAP.com Components Data

Transfer to the SAP Business Information Warehouse

Settings for Application-Specific DataSources (PI) Logistics





Managing Extract Structures Initialization Delete theContents of the Setup Tables

Transaction Code LBWG


1. In the Delete setup data view in field Application enter 04.2. Choose Execute.

3. Confirm the warning with Yes.

4. Choose Back to return to the IMG view.

Result

You have deleted the content of the setup tables for sales orders, deliveries and billing documents. Now youcan be sure that data of existing documents is not stored twice in the setup tables if you trigger the statisticalupdate.

.3.2 Replicating DataSources from the SAP ERP System

Prerequisites

Connectivity between SAP BI and SAP ERP has been set up. DataSources have been created or activated in the SAP ERP Source System.

Procedure

This activity has to be carried out in the BI system:

SAP BI Menu Modeling Data Warehousing Workbench: Modeling

Transaction Code RSA1


1. In the Data Warehousing Workbench: Modeling view choose Source Systems.

2. Make a right mouse click on your SAP ERP Source System in the right-hand window andchoose Replicate DataSources.

3. If the Unknown DataSource dialog box occurs, choose This and the following <…>as 3.x DataSource.

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 hand frame choose Update Tree. The DataSources from your SAP ERPsystem are displayed in another frame.

The DataSources that you have activated before should be seen.


Documents

4 Basic Configuration AFS PP