cancel
Showing results for 
Search instead for 
Did you mean: 

generic

Former Member
0 Kudos

Hello Experts,

What is the step to create the generic data source ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Mr ROy ,

the following are the standard steps to create the generic Datasource :-

1. Select the DataSource type and assign a technical name to it.

2. Choose Create

The screen for creating a generic DataSource appears.

3. Choose an application component to which the DataSource is to be assigned.

4. Enter the descriptive texts. You can choose these freely.

5. Choose from which data sets the generic DataSource is to be filled.

a) If you want to extract data from a transparent table or database view, choose Extraction from View and enter the name of the table or database view.

The result of generation is a DataSource whose extract structure corresponds to the database view or transparent table.

For more information on creating and maintaining database tables and views, see the ABAP Dictionary documentation.

b) If you want to use an SAP query functional area as a data source, choose Extraction from Query. Select the required functional area from the functional area catalog.

Enhancements for Extracting Using SAP Queries

The result of generation is a DataSource whose extract structure corresponds to the functional area.

You can find additional information about the maintenance of functional areas in the SAP query documentation.

c) If you want to extract data using a function module, choose Extraction Using FM and specify the function module and the extract structure.

The data must be transferred from the function module to an interface table E_T_DATA .

Interface Description and Extraction Process

You can find information about the function builder in the ABAP Workbench documentation.

d) For texts, data can also be extracted from domain fixed values.

6. If necessary, maintain settings for the Delta Transfer.

7. Choose Save.

Thanks

Answers (4)

Answers (4)

former_member205352
Active Contributor
0 Kudos

I guess above posts mention about all possible methods.

For generic extraction using function module check the below blog

Hope this helps.

Former Member
0 Kudos

Hi

Go to RSO2 >> Now select the right option(Transaction data,Master data attributes or texts) >> Now in the next screen enter the Application Component >> enter the descriptions >> Now select how you want to populate data in your data source .....following options are there :

View/table >> Choose the extraction from view button if you want to want to extract the data from a transpatrent table or database view,and enter the name of the table or view...the extraction structure of the generated datasource is then identical to that of view or table.......

SAP Query/Infoset>> Choose the extraction from query button if you want to use SAP query infoset as datasource..then select the required infoset from the infoset catalog...you can go to the screen for maintaining an existing infoset by double click on its name...

Function Module

To make your datasource delta enable >> Click on Generic Delta on the top >> Here first give the field name .This field from the extract structure of a DataSource meets one of the following criteria:

1. The field has type: time stamp. New records to be loaded into the BW using a delta upload have a higher entry in this field that those which have already been loaded.

2. The field has type: calendar day. The same criteria applies to new records as in the time stamp field.

3. The field has another type. This case is only supported for SAP Content DataSources. In this case, the maximum value to be read must be displayed using a DataSource-specific exit when beginning data extraction.

Now choose one of the three options :

Time Stamp

Calender day

Numeric pointer...

Safety Interval Upper Limit >>This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.

The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.

Leaving the value blank increases the risk that the system could not extract records arising during extraction.

Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.

A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.

For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).

Safety Interval Lower Limit >> This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.

For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.

Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.

DataSource Is Real-Time Enabled

The "Real-time enabled" indicator determines whether a delta-enabled DataSource can supply data for a real-time demon.

If the DataSource finds the delta generically using a delta-relevant field, observe the following with regard to the safety intervals:

The safety interval at the lower limit may cause redundant data to arrive in BW. This data is not suitable for InfoCubes and ODS objects with key figures that are updated in appended order. With real-time updates, the redundancy of the data is increased by the short time spans between the individual runs of a real-time demon. With a lower safety interval of 2 minutes and a demon frequency of one per minute, all data may potentially arrive in the PSA three times. This can lead to database and runtime problems.

The safety interval at the upper limit makes the data less up to date. How up to date the data is with real-time is always the sum of the upper safety interval and the time span between two runs of the demon.

The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.

A distinction is made between the following:

1. Additive delta

The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.

2. New status for changed records

Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.

Now save it...

Follow the following links for the contain step by step all the processes requires for the creation of "Generic data sources " and all the related settings and even all the precautionary measures for the same.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b06...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0ded994-c520-2a10-9da7-bc92c9e9...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba3...

Hope it will be expedite in a gr8 way

Regards

gaurav

rajkumar_kandula
Active Contributor
0 Kudos

Goto RSO2 of your R/3 system.

There you can create your required generic data sources.

you can find more info and step by step guide in fourms and help.sap.com.

Also refer this link

http://www.allinterview.com/showanswers/2920.html