7/27/2019 Standard Datasource Enhancement

1/19

Transport Management for Enhanced LO Datasource

Table of Contents

1. Transport Requests .................................................................................................................................... . 3

1.1 Request for changing the status of the datasource from Active to Inactive ....................................... 31.2

Request for Enhancing the datasource........................................................................................... 4

1.3 Request for changing the status of the datasource from Inactive to Active..................................... 6

The 3 requests created ................................................................................................................................... 72. Checks to be maintained before transporting therequests ........................................................................ 7

2.1

Delete the setuptable ......................................................................................................................... 7

2.2

Empty the ExtractionQueue ............................................................................................................... 8

2.3

Check the ExtractionQueue ............................................................................................................... 9

2.4 Empty the Delta Queue ..................................................................................................................... . 9

2.5

UserLocking ....................................................................................................................................... 9

3. After the transport ......................................................................................................................................

1

03.1 Replicate the datasource ..................................................................................................................

1

03.2 Monitor the queues .......................................................................................................................... .

11

3.3 Execute next delta ........................................................................................................................... .

1

2

Related Content ................................................................................................................................................1

3

Disclaimer and Liability Notice ..........................................................................................................................1

4

http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page3http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page3http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page4http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page4http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page6http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page8http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page8http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page10http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page10http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page11http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page12http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page13http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page14http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page3http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page4http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page4http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page6http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page7http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page8http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page8http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page9http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page10http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page10http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page11http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page12http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page13http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page14http://var/www/apps/conversion/tmp/scratch_5/HYPERLINK%23page3

7/27/2019 Standard Datasource Enhancement

2/19

7/27/2019 Standard Datasource Enhancement

3/19

Transport Management for Enhanced LO Datasource

1. Transport Requests

The following requests have to be created while enhancing the LOdatasource:

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 addedto 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, asshown 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

7/27/2019 Standard Datasource Enhancement

4/19

Transport Management for Enhanced LO Datasource

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

7/27/2019 Standard Datasource Enhancement

5/19

Transport Management for Enhanced LO Datasource

After saving the request, a screen pops up. Here on the left side, you see what has already beenselected in the standard extract structure.

On the right side, you see all the available fields in the datasource Pool, from where you can selectfields 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.

7/27/2019 Standard Datasource Enhancement

6/19

Here you can choose fields that can be selected, hidden and if a key figure is inverted or not (Figure 4).

7/27/2019 Standard Datasource Enhancement

7/19

Transport Management for Enhanced LO Datasource

7/27/2019 Standard Datasource Enhancement

8/19

Figure 4After 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 isdone by clicking on Active Button.

Here, it asks for one more Customizingrequest (Figure 5). This is our third request.

7/27/2019 Standard Datasource Enhancement

9/19

Transport Management for Enhanced LO Datasource

Figure 5

After you successfully complete this step, the traffic light icon turns green, indicating that theenhancement process is complete.

The 3 requests created

To summarize, there will be 3 requests, which have to be transported in the order mentionedbelow:

1. Inactive request Customizing request

2. Enhancement request Workbench request

3. Active request Customizing request

7/27/2019 Standard Datasource Enhancement

10/19

2. Checks to be maintained before transporting the requests

The following checks have to be maintained before transporting theabove 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.

7/27/2019 Standard Datasource Enhancement

11/19

Transport Management for Enhanced LO Datasource

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

7/27/2019 Standard Datasource Enhancement

12/19

7/27/2019 Standard Datasource Enhancement

13/19

Transport Management for Enhanced LO Datasource

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, sothat the records in the delta queue will be pulled to BI, and hencethe Delta Queue (RSA7) will be emptied.

2.5 User Locking

All users should be locked during the transport, so that there areno new postings during the transport. Only ALEREMOTE and yourown user-id should be unlocked.

7/27/2019 Standard Datasource Enhancement

14/19

7/27/2019 Standard Datasource Enhancement

15/19

Transport Management for Enhanced LO Datasource

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

7/27/2019 Standard Datasource Enhancement

16/19

Transport Management for Enhanced LO Datasource

3.2 Monitor the queues

Monitor the extraction queue (LBWQ) and delta queue (RSA7) inyour 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)

7/27/2019 Standard Datasource Enhancement

17/19

7/27/2019 Standard Datasource Enhancement

18/19

Transport Management for Enhanced LO Datasource

Delta Queue (RSA7)

7/27/2019 Standard Datasource Enhancement

19/19

3.3 Execute next delta

Once it is confirmed that the queues contain entries for the new records, the nextdelta infopackage can be executed.