Generic Extraction based on a View – Part 1

WRITTEN BY: supportmymoto.com STAFF

Overview

The aim of this doc is to assist in understanding the best way to create a view based mostly on clear tables, create a generic datasource based mostly on it,
replicate to BI, BI content material set up, mapping fields to infoobjects, create the DSO, the InfoCube, the transformations, the DTP, and eventually taking it to stories.

Generic Extraction is kind when the usual extractors aren’t supporting the extraction what you want.

Generic extractors are of three sorts:

1. Based mostly on desk/view

2. Based mostly on Infoset Question

3. Based mostly on Perform module

We’ll restrict our dialogue to Generic Extraction based mostly on a view. We go for this selection when the info to be fetched to BI is distributed in
completely different tables in SAP R/3.

State of affairs

We have to extract the Companion Perform (PARVW discipline) and Merchandise variety of gross sales doc (POSNR discipline) in VBPA – Sales Doc: Partner desk and few fields current within the VBAK – Gross sales Doc: Header Knowledge desk as detailed beneath.

ECC Steps

1) Verify the tables for the required fields.  The fields we require from VBAK are

VBELN

VKORG

AEDAT

NETWR

WAERK

and

PARVW

POSNR from VBPA Desk.

2) Now we create a be a part of between these tables and for this we have to have no less than one frequent discipline between them.

In SAP R/3 or ECC enter Transaction SE11 which allows you to create a desk or view.  Right here I’m making a view as ZVIEW_VBAK_VBPA.

1.PNG

Click on on Create.

2.PNG

See also  Creating arbitrary PSEs using ‘sapgenpse’ command-line tool.

Choose the view sort. We’re making a database view.

The system now shows the Upkeep view display.

Within the Desk/Be part of Circumstances tab, enter the tables that you just want to construct the be a part of on.

3.PNG

4.PNG

If you’re not sure of the frequent fields to ascertain a be a part of, then choose the tables concerned within the be a part of and choose ‘Relationships’ and system will routinely immediate you the connection hyperlink between these tables.

Within the ‘View Fields’ tab enter the fields that you just want to embody within the View.  Please keep in mind to incorporate the ‘key fields’ from every of the tables within the fields choice else you’ll encounter an error throughout activation of the view.

6.PNG

Save the View. You can be prompted to enter the event class in addition to Transport request quantity for the event that you’re carrying.

Enter the related values. Click on on the ‘Verify’ button to test the View for inconsistencies. If there may be none, Activate the view.

3) Create a Generic datasource based mostly on the view we simply created.

Use Transaction Code RSO2 to create a Generic datasource.

7.PNG

Within the subsequent display enter the values as required.

Software Element: Element title the place you want to place the info supply within the App. Element hierarchy, in our case SD.

Textual content: Descriptions (Quick, Medium and Lengthy) for the datasource.

View/Desk: Identify of the Desk/View on which you want to create the Generic datasource, in our case ZVIEW_VBAK_VBPA.

See also  Partial and Residual Payments in S/4HANA Cloud

8.PNG

Save the datasource.  The Generic datasource is now displayed permitting you to Choose in addition to Cover discipline. The fields ‘hidden’ is not going to be out there for extraction. Fields within the ‘Choice’ tab shall be out there for Worth Choice within the Infopackage throughout information extraction from the supply system to the PSA.

9.PNG

Save.

4) Checking the info within the extract checker (T code – RSA3)

10.PNG

Right here I’m extracting the data with VBELN between 4970 and 4980. (If you wish to have the proper variety of data extracted,

Give Knowledge Data/Calls as 100000 and click on on “Extraction”)

11.PNG

Click on on ‘Show checklist’ to show the variety of information packets out there.

12.PNG

Double-click on the Knowledge packet and the data within the information packet are displayed.

13.PNG

Right here we are able to see that every Gross sales Doc Quantity has 6 entries, so between VBELN (4970-4980) we acquired 6*10=60 information data.

5) Go to RSA6 ( Postprocess Datasources and Hierarchy) and test to your Datasource.  This holds all of the datasources which might be lively in nature.

https://blogs.sap.com/wp-content/uploads/2012/09/14_140696.png

The Steps in ECC is completed.  Now we’ve got to go for Steps in BI.                                                  (continued in Half 2)

Half 2 

http://scn.sap.com/docs/DOC-32026

Thanks for taking day trip to undergo the doc.  Hope its been useful.  Please depart your precious feedback/likes/scores beneath.

NOTE : Please do not copy - https://supportmymoto.com

Leave a Reply