Cut Over Activities Specific For LIS Data Sources: Applies To

Cut Over Activities Specific for LIS* Data Sources
Applies to:
SAP BW 3.5/SAP BI 7.0. For more information visit the Enterprise Data Warehousing Homepage
Summary
The basic purpose of this document is to explain all the basic activities to be taken care of while performing the cut-over of an LIS* data source. In other words, the document will give you details of the things to be done before you move LIS* data source (enhanced or otherwise) to the production environment. Author: Rahul Manickan
Company: Infosys Technologies Limited Created on: 10 September 2011
Author Bio
Rahul Manickan is a Technology Analyst in Infosys Technologies Limited. He has been involved in SAP BW/BO Implementation Projects.
SAP COMMUNITY NETWORK 2011 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1
Table of Contents
Overview: ............................................................................................................................................................ 3 What are the Cut over Activities? ....................................................................................................................... 3 Clearing the BW Delta Queues for LIS extractors in ECC ................................................................................. 3 Clearing of Outbound Queues in ECC ............................................................................................................... 4 Clearing the Extraction Queues by executing the V3 collective job using T-Code SE38: ............................. 4 Clearing of Extraction Queues by scheduling the job using T-Code LBWE: ................................................. 5 Processing of Delta Queues ............................................................................................................................... 5 Deleting the Setup Tables .................................................................................................................................. 6 How to check if the setup tables needs to be cleared? .................................................................................. 6 How do we delete the data from the setup tables? ......................................................................................... 7
By using t-code SBIW .................................................................................................................................................. 7 By using program RMCSBWSETUPDELETE .............................................................................................................. 8
Related Content .................................................................................................................................................. 9 Disclaimer and Liability Notice .......................................................................................................................... 10
Overview:
LIS stands for Logistics Information Systems. The purpose of this document is to brief about the steps to be taken with regard to LIS data sources before and after any planned maintenance to the ECC component. These activities are required to be performed to ensure that no data is lost.
What are the Cut over Activities?

Typical cut over activities for LIS data sources include the following: 1. Clearing the BW Delta Queues for LIS extractors in ECC. 2. Clearing the Outbound Queue in ECC. 3. Processing of Delta Queues. 4. Deletion of setup tables. Now we will look at each step in detail
Clearing the BW Delta Queues for LIS extractors in ECC

The Delta Queue can be accessed by T-Code RSA7 in ECC. There you would be able to see the name of the LIS data sources and the records in the Total column as shown below.
We can clear the queues by triggering the Auto (Delta) manually. Once a particular queue is cleared the total column would show zero. For example for the data source 2LIS_06_INV we see 13 in the Total column. Once the Auto (Delta) info package is triggered and the queue is cleared we would see 0 in the total column as shown below.
This sums up the step, Clearing of BW Delta Queues.
Clearing of Outbound Queues in ECC

The Extraction Queues that needs to be cleared can be identified using the T-Code LBWQ. If we go to LBWQ, we would see the Queues waiting to be cleared as shown below.
Now for clearing the extraction Queues we need to either execute the V3 collective job using T-Code SE38 or by scheduling the job immediately using the transaction LBWE. Clearing the Extraction Queues by executing the V3 collective job using T-Code SE38: a.) Go to T-Code SE38. b.) The program to be used is RMBWV3XX. XX here stands for the application number. Suppose if you want the clear the Extraction Queue for Application 02, then the program name would be RMBWV302. Take another look at the above screenshot of Outbound Queues and you would notice one entry which reads MCEX17_1. What should the Program name be for clearing this queue? The program name is RMBWV317, same as the one used for clearing MCEX17. Here is the list of all program names for the above shown applications for convenience. Program RMBWV302 (Clears queue MCEX02) Program RMBWV303 (Clears queue MCEX03) Program RMBWV304 (Clears queue MCEX04) Program RMBWV305 (Clears queue MCEX05) Program RMBWV306 (Clears queue MCEX06) Program RMBWV308 (Clears queue MCEX08) Program RMBWV311 (Clears queue MCEX11) Program RMBWV312 (Clears queue MCEX12) Program RMBWV313 (Clears queue MCEX13) Program RMBWV317 (Clears queue MCEX17 & MCEX17_1).
Clearing of Extraction Queues by scheduling the job using T-Code LBWE: a.) Go to LBWE. The screen will look as shown below. b.) Click on Job Control for the application for which you want to process the extraction queues. c.) Schedule the job as immediate. The LUVs or entries in the Extraction Queue would be processed.
This completes the second step i.e., clearing of Outbound Queues.
Processing of Delta Queues

After clearing the Outbound Queue, the Delta Queues which needs to be processed can be seen using the T-Code SMQ1. It would be something similar to the below screenshot.
Now again trigger the Auto (Delta) info packages under each data source to fetch data to BWP. The info packages should be triggered till we see two empty records in the PSA (a best practice). This completes the third step i.e. processing of Delta Queues.
Deleting the Setup Tables

How to check if the setup tables needs to be cleared? By using the Program RMCEXCHK via T-Code SE38, we can check what all setup tables can be cleared. Have a look at the screenshots
Now as seen from the above screenshot, we can see that setup tables needs to be cleared for applications 02, 03, 04, 06, 08, 11, 12, 13, 17.
How do we delete the data from the setup tables? There are two ways to delete the contents of the setup table a.) By using t-code SBIW b.) By using program RMCSBWSETUPDELETE By using t-code SBIW Go to t-code SBIW. Go to Delete the contents of the setup table using the following flow Settings for Application-Specific Data Sources (PI) contents of the setup table. It is shown in the below screenshot Logistics Initialization delete the
After clicking execute, the new screen would ask to input the application as shown in the next screenshot-
Say for example, you want to delete application 02, enter it in the above screen as shown below and execute it.
This ensures that all the setup tables for application 02 are emptied. Repeat this step for all the applications which are showed in the check. By using program RMCSBWSETUPDELETE By using the program RMCSBWSETUPDELETE via T-Code SE38, for the selected application we can delete the data for that application. It is shown below.
After clicking execute, the new screen would ask to input the application as shown in the next screenshot-
Say for example, you want to delete application 02, enter it in the above screen as shown below and execute it.
This ensures that all the setup tables for application 02 are emptied. Repeat this step for all the applications which are showed in the check. This completes the step of deleting setup table data.
Related Content
How-to enhance LO-Cockpit DataSources with delta-relevant fields Blog - LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1034bcbe-b459-2d10-2a89ecdeb4e53ff1?QuickLink=index&overridelayout=true For more information visit the Enterprise Data Warehousing Homepage
Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Cut Over Activities Specific For LIS Data Sources: Applies To

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cut Over Activities Specific For LIS Data Sources: Applies To

Hochgeladen von

Copyright:

Verfügbare Formate

Cut Over Activities Specific for LIS* Data Sources

Company: Infosys Technologies Limited Created on: 10 September 2011

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1