Transport Management For Enhanced LO Data Sources

Transport Management for Enhanced LO Datasource
Applies to:
SAP BI 2004s or SAP BI 7.x For more information, visit the Business Intelligence homepage.
Summary
This document describes the steps for transporting the enhanced LO Datasources. When enhancements are made to a datasource already in use, certain steps are to be taken into consideration while transporting such a datasource, from one landscape to another (ie. From Development to Quality and Production). Author: Apeksha Maniar
Company: L&T Infotech Created on: 15 July 2009
Author Bio:
Apeksha Maniar, working in L&T Infotech has an experience of almost 3 years in SAP BI. She has been part of Production Support, Development and Implementation Projects.
SAP COMMUNITY NETWORK 2009 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1
Table of Contents
1. Transport Requests ..................................................................................................................................... 3 1.1 1.2 1.3 2. Request for changing the status of the datasource from Active to Inactive ....................................... 3 Request for Enhancing the datasource ........................................................................................... 4 Request for changing the status of the datasource from Inactive to Active ..................................... 6
The 3 requests created ................................................................................................................................... 7 Checks to be maintained before transporting the requests ........................................................................ 7 2.1 2.2 2.3 2.4 2.5 3. 3.1 3.2 3.3 Delete the setup table ......................................................................................................................... 7 Empty the Extraction Queue ............................................................................................................... 8 Check the Extraction Queue ............................................................................................................... 9 Empty the Delta Queue ...................................................................................................................... 9 User Locking ....................................................................................................................................... 9 Replicate the datasource .................................................................................................................. 10 Monitor the queues ........................................................................................................................... 11 Execute next delta ............................................................................................................................ 12
After the transport ...................................................................................................................................... 10
Related Content ................................................................................................................................................ 13 Disclaimer and Liability Notice .......................................................................................................................... 14
1.
Transport Requests
The following requests have to be created while enhancing the LO datasource:
1.1 Request for changing the status of the datasource from Active to Inactive First, the Active datasource needs to be inactivated, so that the required fields can be added to the datasource, ie. The required enhancements to the datasource can be done. For this go to t-code LBWE, and click on Active/Inactive button for your datasource, as shown in Figure 1. Here, it asks for a customizing request. This is the first request. When you successfully complete this step, the traffic light icon turns yellow.
Figure 1
1.2
Request for Enhancing the datasource After the datasource is made inactive, it has to be enhanced. For enhancing your datasource, click on the Maintenance button. After clicking the Maintenance button, you get a prompt to create a Workbench request (Figure 2). This is the second request.
Figure 2
After saving the request, a screen pops up. Here on the left side, you see what has already been selected in the standard extract structure. On the right side, you see all the available fields in the datasource Pool, from where you can select fields for the update. Select the fields required in your datasource from the right side to the left side (Figure 3).
Figure 3 After you successfully complete this step, the traffic light icon turns red, indicating that you have changed the structure. At this point, you have to generate the datasource by clicking on the data source name. Here you can choose fields that can be selected, hidden and if a key figure is inverted or not (Figure 4).
Figure 4 After maintenance in this step, the traffic light turns yellow. 1.3 Request for changing the status of the datasource from Inactive to Active
After enhancing the datasource, it needs to be activated again. This is done by clicking on Active Button. Here, it asks for one more Customizing request (Figure 5). This is our third request.
Figure 5 After you successfully complete this step, the traffic light icon turns green, indicating that the enhancement process is complete. The 3 requests created To summarize, there will be 3 requests, which have to be transported in the order mentioned below: 1. Inactive request Customizing request 2. Enhancement request Workbench request 3. Active request Customizing request
2.
Checks to be maintained before transporting the requests

The following checks have to be maintained before transporting the above requests:
2.1 Delete the setup table The setup table needs to be deleted first, before transporting the enhanced datasource. For this go to t-code LBWG (Figure 6). Enter the Application of your datasource. E.g.: For 2LIS_13_VDKON, enter 13. Click on execute.
Figure 6 2.2 Empty the Extraction Queue The extraction queue also has to be emptied before the transport. For that, go to SE38 and execute the program RMBWV3nn (Figure 7). nn Your application 11, 12, 13 etc.
Figure 7
2.3
Check the Extraction Queue Once the above mentioned program is executed, check in the Extraction Queue For this go to t-code LBWQ (Figure 8). The Queue (MCEXnn) for your application should not be present here if it is empty.
Figure 8 2.4 Empty the Delta Queue
Empty the delta queue by executing the relevant Infopackages, so that the records in the delta queue will be pulled to BI, and hence the Delta Queue (RSA7) will be emptied.
2.5 User Locking
All users should be locked during the transport, so that there are no new postings during the transport. Only ALEREMOTE and your own user-id should be unlocked.
3.
After the transport

After the above requests are successfully transported, the following needs to be done: 3.1 Replicate the datasource
After the transport, replicate your datasource in BW (Figure 9), so that the enhanced structure is updated in BI.
Figure 9
3.2
Monitor the queues
Monitor the extraction queue (LBWQ) and delta queue (RSA7) in your source system, to check whether new records are being updated in these queues or not. To confirm this, check the entries in these queues
Extraction Queue (LBWQ)
Delta Queue (RSA7) 3.3 Execute next delta Once it is confirmed that the queues contain entries for the new records, the next delta infopackage can be executed.
Related Content
For more information, visit Data Extraction from SAP Source Systems For more information, visit LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it ! For more information, visit the Business Intelligence 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.

Transport Management For Enhanced LO Data Sources

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Transport Management For Enhanced LO Data Sources

Încărcat de

Drepturi de autor:

Formate disponibile

Transport Management for Enhanced LO Datasource

Company: L&T Infotech Created on: 15 July 2009

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1