Practical Tips to Set Up and Implement the Logistics Cockpit

Practical Tips to Set Up and Implement the Logistics Cockpit

Luis Orama

Platinum Consultant

SAP

SAP AG 2003, slide 2

Agenda

Understanding the LO Cockpit

Setting up the LO Cockpit

Initializing Your Setup

Tips & Tricks

Conclusion

Appendix: Minimum Downtime Initialization

!

!

!!

BONUS


Agenda




Tips & Tricks

Conclusion


!

!

!!

BONUS



" Plug-in PI.2002 for R/3 installs the LO Cockpit" LO Cockpit = Logistics Extract Structures Customizing Cockpit" One-stop shop for setting up & managing logistics extracts to BW" Access via R/3 transactions SBIW or LBWE

R/3 BW

Plug

-in P

I.200

2


Launching the LO Cockpit: Option 1

TcodeSBIW


Launching the LO Cockpit: Option 2

TcodeLBWE


How SAP Logistics Data Flows to SAP BW

" Documents are created, changed or deleted in R/3 (SD, MM, PP)

" The data is transferred to Central Delta Management" Uses R/3 Extract Structures" Only responds to delta requests from BW b/c Central Delta

Management is only used during online postings

" A statistical setup uses extract structures to write data directly into a setup table

" The setup table data is transferred to BW " Only when there is a full update or an initialization request " A full update request and an initial loading is used solely for setup

of historical documents


LO Cockpit: Availability & Prerequisites

.0B P I 2002.2

(m odifying) - R /3 S P

A9

P I 2002.2 - R /3 S P

38

P I 2002.2 - R /3 S P 16 P I 2002.2 - R /3 S P

03

P I 2002.1


98

P I 2002.1 - R /3 S P

38

P I 2002.1 - R /3 S P 16

P I-A 2002.1 - R /3 S P

27

P I-A 2002.1 - R /3 S P

20

P I-A 2002.1 - R /3 S P 03

P I 2001.2


85

P I 2001.2 - R /3 S P

38

P I 2001.2 - R /3 S P 16

P I-A 2001.2 - R /3 S P

27

P I-A 2001.2 - R /3 S P

20

P I-A 2001.2 - R /3 S P 03

.1

ent

P I 2002.2


A9

P I 2002.2 - R /3 S P

38

P I 2002.2 - R /3 S P 16 P I 2002.2 - R /3 S P

03

P I 2002.1


98

P I 2002.1 - R /3 S P

38

P I 2002.1 - R /3 S P 16

P I-A 2002.1 - R /3 S P

27

P I-A 2002.1 - R /3 S P

20

P I-A 2002.1 - R /3 S P 03

P I 2001.2


85

P I 2001.2 - R /3 S P

38

P I 2001.2 - R /3 S P 16

P I-A 2001.2 - R /3 S P

27

P I-A 2001.2 - R /3 S P

20

P I-A 2001.2 - R /3 S P 03

P I 2002.1 - R /3 S P

03

P I 2001.2 - R /3 S P

03

P I 2002.1 - R /3 S P

03

P I 2001.2 - R /3 S P

03

BW 3.1

BW 3.0B

R/3 3.1I R/3 4.0B R/3 4.5B R/3 4.6B R/3 4.6C R/3 Enterprise


Agenda




Tips & Tricks

Conclusion


!

!

!!

BONUS


LO Cockpit: Setup Steps

" Step 1 - Maintain Your Extract Structures

" Step 2 - Maintain Your DataSources

" Step 3 - Activate Your Extract Structures

" Step 4 - Choose an Update Method

" Step 5 - Schedule Your Update Job


Step 1 - Maintain Your Extract Structures

" Extract Structures define the fields to be transferred to BW" The plug-in installs standard Business Content structures" You can modify these structures or create your own

" Common modifications" Add standard fields from the communication structure

# Example: MCVBAP – Sales Order Item" Add user-defined fields through append structures" Fill field(s) through user exit EXIT_SAPLRSAP_001


1 - Maintain Your Extract Structures (cont’d)

Click to maintain the structure’s

fields



Add/remove fields by

transferring them from the

communications structure



This is the LBWQ

transaction for the delta

queue

TcodeLBWQ


Step 2 - Maintain Your DataSources

" Next, maintain the DataSources that control your extract" You maintain field indicators for each field to modify R/3’s behavior" Use transaction RSA6 or through LBWE

" The 3 field indicators" For Selection – Allows the characteristic to be a filter parameter" Hidden – Hides the field and it is not passed to BW" Inverse (Key Figures Only)

# The indicator for the key figure to be inverted is very important

When the “Inverse” field is selected, and the key figure value changes, R/3 passes the old value with a negative value and another record with the new value. 0STORNO field (ROCANCEL) = (X),


2 - Maintain Your DataSources: Tips

TcodeRSA6


0STORNO Example:

Original record:Document Sold to QTY

40000 1000 100

Changed record:Document Sold to QTY

40000 1000 125

Document Posting:ROCANCEL Document Sold to QTY

(X) 4000 1000 -100

4000 1000 125

2 - Maintain Your DataSources: Tips (cont’d)


Step 3 - Activate Your Extract Structures

" You need to activate your extract structures before use" SAP’s standard structures are all delivered inactive" You can do this within the LO Cockpit

Once a structure is active, it will immediately start a collection of records in the SM13 log" The records will be transferred to the delta queue when a V3

collection run is executed" You need to be aware of this before starting your statistical setups

(historical collection)

Note


3 - Activate Your Extract Structures (cont’d)

Yellow light = inactive

Green light = ready to collect data

Click to activate update


The SM13 Log captures all records that have been created/changed in

R/3 for active structures

TcodeSM13



MCEX_UPDATE_11 of “Init” = our structure is ready to pass data to the

delta queue upon V3 execution


TcodeSM13



Transaction LBWQ shows the delta queue

TcodeLBWQ


Step 4 - Choose an Update Mode

" You need to specify an update mode for the group" Determines how and when the update occurs" Your selection will impact performance

" As of PI 2002.1, there are 4 update methods for delta records" Serialized V3 update

# Conventional Method" Direct delta

# Synchronous update (V1)# Data is transferred directly from postings to the BW delta queue

" Queued delta# Collects extraction data from postings into an extraction queue

" Non-serialized V3 update# Like V3, but the documents are not serialized


4 - Choose an Update Mode (cont’d)


4 - Choose an Update Mode: Tips

" Data is written to the extract structure " online " when data is supplied to the setup tables

" If you chose “V3 update”" You’ll see entries in the updated records overview (tcode SM13)" The collective (V3) update status for BW will be “Initial”

# Shows that data is waiting to be collected

" If you chose “Queued delta” as the update method" You can view the records posted online " Use the Logistics extraction queue overview (transaction LBWQ)" Queued Delta bypasses the SM13 log


Step 5 - Schedule the Update Job

" Finally, maintain the update job’s scheduling parameters

" Collection run options" Can be a BW “pull” through the InfoPackage scheduler" Can be event-triggered from the R/3 system

# Kicks off the InfoPackage after a successful collection run

" Scheduling tips " You may chose to execute the run once or several times per day" The frequency will depend on your needs & the volume of data

112

2

3

45

678

9

10

11

Timing


5 - Schedule the Update Job (cont’d)


Agenda




Tips & Tricks

Conclusion!

!

!!



" To load historical data, you need to initialize the setup tables" This only needs to be done once per application area" Afterward, only deltas are sent

R/3 OLTP-System Business InformationWarehouse

MasterData

∆-MANAGEMENT---------------------------------------------------

Delta Extract

∆-MANAGEMENT---------------------------------------------------

Delta Extract

Full Extractor Delta Extract

Full Extractor Delta Extract

TransactionData

StagingEngine

StagingEngine

Setup Tables Setup-API


Initializing Your Setup: Traditional Approach

" The traditional process involves some “downtime”" 1 - Block users from creating/changing orders in R/3" 2 - Activate the DataSource " 3 - Flush the setup table(s)" 4 - Populate the setup table(s) with historical records" 5 - Execute a delta initialization to load the data into BW" 6 - Flush the setup table(s) used" 7 - Unblock user activities/access in R/3


Initializing Your Setup: Min. Downtime Approach

" New approach available as of Plug-in PI2002.1" 1 - Trigger the extraction in BW without transferring data " 2 - Block users from creating/changing orders in R/3" 3 - Create a mirror of your R/3 system" 4 - Unblock user activities/access in the production R/3" 5 - Flush the setup table(s) in the mirror R/3" 6 - Populate the setup table(s) in the mirror R/3" 7 - Execute a delta initialization to load the data into BW" 8 - Transfer monitor info from the mirror system to productive R/3" 9 - Discard the mirror system

See the Appendix for the specifics of this approachHiddenBonus


When to Consider Minimum Downtime Approach

" Minimum downtime approach " Pros

# Affected production users experience less downtime# Avoids production performance impact during extracts

" Drawbacks# Involves more steps# May require additional hardware for the mirror system# Requires tools & knowledge to create a mirror system


What You Need to Know

" Techniques you need to know regardless of approach" 1 - How to flush setup tables" 2 - How to populate the setup table(s) with historical records

Building Block


Technique 1 - How to Flush the Setup Tables

" Flush the setup tables to " Ensure no unexpected records get sent with your initial load" Clean up after the initialization

" Use transaction LBWG (also available in SBIW)

TcodeSBIW

Launches LBWG


1 - How to Flush the Setup Tables (cont’d)

Run once for each application

area you’ll be setting up

TcodeLBWG


Technique 2 - How to Populate the Setup Tables

TcodeSBIW

Launch the tcode for each

application area you wish to setup

You can run them parallel and in

the background


2 - How to Populate the Setup Tables (cont’d)

Specify a unique name for each run so you can

re-run the job if something goes wrong


Agenda




Tips & Tricks

Conclusion


!

!

!!

BONUS


Changing Active Structures

" Plan carefully if you need to change to active structures!" Run the update to clear the delta queue prior to the change" Restrict making changes to a time when there are no postings" The setup of statistical data and the log are both worthless after a

change

If you change the structure before the update has run# The interface is changed & the update (V3 or queued delta) can no longer

run# Your only option is to physically delete the records that are still to be

updated. YOUR RECORDS ARE LOST!

Warning


Tools for Monitoring the Extract Process

" R/3 Tools to test/check your extractors and delta queue" LBWF ! Use to check the transfer to BW" The Sales and Distribution application (11, 12, 13) can run a

simulation that creates a log" Transaction RSA7 ! Use to check the BW delta queue" Transaction RSA3 ! Use to check your extractor

Tool


Tools for Monitoring the Extract Process (cont’d)

TcodeRSA7


Tools for Monitoring the Extract Process (cont’d)

TcodeRSA3


Places to Troubleshoot Extract Issues

" The LO Cockpit Control tables" Can tell you whether extract structures are active, or inactive, and

events that trigger updates

" Use SE11 or SE16 to view" TMCEXCFS: Field status of communication structures" TMCEXCFZ: Field status of customer communication structures

# All fields selected by the customer, per extract structure and communication structure

" TMCEXEVE: Events and extract structures# Which event supplies which extract structure with which communication

structure." TMCEXACT: Status activation of DataSource" TMCEXUPD: Update method per application


Places to Troubleshoot Extract Issues (cont’d)

" The ROO* tables" ROOSOURCE, ROOSFIELD, ROOSGEN

" Extract Structures " Naming convention is

# 1st - 2nd Letter: MC (related to communication structures)# 3rd - 4th Letter: Application# 5th - 6th Letter: Event, group of events with _ (Example:

MC04P_0ARB)# 7th - 7th Letter: Hierarchy: 0 original, 1..9 substructure# 8th - 10th Letter: optional, addition for further differentiation

" Example MC04PE0MAT


Places to Troubleshoot Extract Issues (cont’d)

" Logistics extraction queues" “MCEXnn”, nn = application number

" Setup tables" <Extract structure name>+“SETUP“, Example MC04PE0ARBSETUP


Agenda




Tips & Tricks

Conclusion


!

!

!!

BONUS


6 Key Points to Take Home

" Use the LO Cockpit to manage all your logistics data extractors

" Plan your initialization carefully

" Remember to clear out the setup tables and delta queues prior to an initialization and delta run

" When doing an your initialization, ensure that# LO users are off the system# No documents will be created or changed# You’ve allowed for sufficient downtime# Sufficient space is available for filling setup tables# Sufficient processing power is available (jobs run in background)

" Run your delta extractions prior to changing extract structures

" Make sure the delta queue is empty!


Your Turn!

Questions?


For More Information

" Important OSS Notes " For a summary of all Notes on Logistics transaction data extraction

# Notes 428294 and 514543 + the Notes they reference" For info on new update methods as of Plug-in Release 2002.1

# Note 505700

" White papers on service.sap.com/bw" Extraction of Logistics Transaction Data" How to…Minimize Downtime For Delta Initialization


Agenda




Tips & Tricks

Conclusion


!

!

!!

BONUS


Initialization: Traditional Approach

" Prior to Plug in PI2002.1, Logistics initialization needed downtime

" To initialize sales, for example, the process was" Block users from creating/changing orders or from the system" Activate the DataSource " Execute LBWG to clear out the setup table(s)" Execute OLI’X’BW to fill the setup table" Execute a delta initialization data load into BW" Delete data from setup table (LBWG)" Unblock user activities/access

Issue


Initialization With Minimal Downtime!

" With Plug-in PI2002.1 you are now able to initialize setup tables with much less downtime" Uses a “mirror” system from which to do the load to BW

" Prerequisites" For this approach, you’ll need to be able to quickly perform a

system copy, or a synchronization/split of a mirror system" We’ll demo the process using TimeFinder™ from EMC2™

Solution


Initialization With Minimal Downtime (cont’d)


How to Do It

" Step 1 - Trigger the extraction without transferring data " Sends the request IDoc

" Step 2 - Split the mirror system

" Step 3 - Extract data from the mirror system to BW

" Step 4 - Transfer monitor information generated by extraction


Step 1 - Trigger the Extraction in BW...

" First, trigger the extraction in BW without transferring data

" How to do it" Transfer monitor info into the original system

# At the end of the extraction, use an RFC to transfer monitor info from the mirror system into the original system

" In BW, enter your user as "Debugging User" in tcode RSADMIN" Switch off immediate data update

# In the InfoPackage, switch off immediate data update in the source system

# The checkbox needs to be empty" Start loading the data

# A request IDoc is sent to the source system without being processed


1 - Trigger the Extraction in BW … (cont’d)

TcodeRSA1


Step 2 - Split the Mirror System

" Next, take your system down and perform the split" Downtime for your productive system begins now

" How to do it" Make sure no users or jobs are active in the system

# Check transactions SM04, SM50, and SM66" Copy or mirror your original system

# Complete the required steps for copying the original system or # Synchronizing the mirror system with the original system # Perform the split

continued >


2 - Split the Mirror System (cont’d)

" How to do it (cont’d)" Get the original IDoc number from the initialization request

# Use transaction BALE (<4.6C) or BD87 (>= 4.6C)" Open the view for "Data records”" Monitor the IDoc entries

# Double-click on the data records to find the relevant data for the IDoc


2 - Split the Mirror System (cont’d)

" Call up the function module RSC1_ZDD_DELTA_ENABLE and specify the request IDoc number in parameter I_DOCNUM

" Afterwards, the system is able to collect deltas for the DataSource and now you can resume work in the production system


Step 3 - Extract Data From the Mirror System

" Next, extract data from the mirror system

" How to do it" Start the R/3 mirror system" Post the request IDoc as usual in the mirror system

# i.e., NOT with the report that was used in the original system# Instead, start transaction BD87 and choose "Posting" with status 64

" Enter the same IDoc number that you already specified in step 7,and start the processing

" The extraction will start running" Monitor the status in the BW monitor

# Also note the system-assigned request number for the loading process# You’ll need this number later on


Step 4 - Transfer Monitor Information

" Finally, transfer the monitor information generated by the extraction into the original system" Enables useful monitoring for the DeltaInit request" Execute function module RSC1_ZDD_REPLAY_SET" You receive the request number from the monitor and enter the RFC

connection from step 1 in the second field


Tips

" If the DataSource has been activated for awhile prior to initialization, then the SM13 log needs to be cleared out prior to a setup run" This ensures that you will not duplicate the records

" A statistical setup can take a long time depending on the amountof historical data needed to be captured. Plan accordingly

GOTCHA!

Warning


" 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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 and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

" HTML, DHTML, XML, XHTML 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.

" MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

" SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com 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 trademarks of their respective companies.

Copyright 2003 SAP AG. All Rights Reserved

Practical Tips to Set Up and Implement the Logistics Cockpit

Documents

Transcript of Practical Tips to Set Up and Implement the Logistics Cockpit