Generic extraction -Infoset

Hello Gurus,
I searched a lot on this but could not find Why and when we do we use Infoset for Generic extraction?
when i searched the SDN they give info about why a Table/View and Function Module is used but not on Infoset.
Any document is helpful with a scenario.
I am asking this query after lot of research itself.
I read the help and could not understand why joins in Infoset.
Thanks,
Sahasra.

Hi Sahasra,
Go through the below thread and article, you will get clear idea on when to create and how to to create generic data source using Infoset query
when we would create genric extractor on a infoset query
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9018e4f3-5537-2e10-238e-ef06d9ab31e8?QuickLink=index&overridelayout=true
Regards,
Venkatesh

Similar Messages

When to go for generic extraction using view and infoset query?

Hi,
Can anyone clarify me when we should go for generic extraction using view and when we should go for generic extraction using infoset query....
Also what is the difference between view and infoset?
I tried but could not find out....
Regards,
Kalyani.

Hi Kalyani,
We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
Regards,
Pratap Sone

Generic extraction

Hi,
in generic extraction in which scenarios you extract data from table,view,infoset query,FM
sridhar

Transparent Table
If you're wishing to create a generic DataSource based on a single Transparent Table in the source R3/ECC system, then using that table as the source for your generic DataSource would be appropriate because it will expose all of the columns in that table to your generic extraction structure. There is one exception to this and that is, if you have more than one date field (e.g. Created On and Changed On dates) that you're going to use for generic delta. Pool/Cluster tables and structures wouldn't be allowable for this type of generic DataSource setup.
View on Transparent Tables
If your requirement is to create a generic DataSource based on multiple Transparent Tables in your source R3/ECC system, then a view would be appropriate. You can either use SAP delivered views in the source R3/ECC environment or create a custom view. The same exceptions (generic delta on more than one date field, pool/cluster tables and structures).
Function Module
A custom Function Module can be coded for the extraction of data for a generic DataSource. This type would be appropiate if you're extracting data from pool/cluster tables or structures. Another use for a Function Module as the source for a generic DataSource would be if you're going to use more than one data field for a generic delta. Finally, a Function Module would be used if there is some transformational-type logic required to be done on the extracted data before it is passed to BW.
InfoSet Query
An InfoSet (not to be confused with an InfoSet in BW) query in a source R3/ECC environment, is created in tocde SQ01, and is a way of creating "quick-and-dirty" reports with summarized values, derived values, et. al. This can be used as the basis for a DataSource, if the queries are already built. If not, then a Function Module can perform and necessary aggregations, derivations or other transformational-type logic, instead of creating a query. I say this because I'd highly discourage using this as a source for a generic DataSource because InfoSet queries are usually extremely inefficient and can consume a lot of the valuable system resources.

Generic Extraction (or) How to use table in R/3 system as datasource in BW?

Hi all,
Hope all are having a great day
Can any1 tell me the steps, for Generic Extraction.
It will be very helpful, if the steps are as much as simpler as posible.
I know to create a simple cube in BW.
I have this much knowledge, depending on this can any1 tell me the steps for Generic Extraction from R/3.
examples wud be vry useful
Regards,
Sourav

hi,
Maintaining Generic DataSources
Use
Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Procedure
Creating a Generic DataSource(RSO2)
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create.
The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process Flow
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
       6.      Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
When extracting, look at SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
        Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
        Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
        Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
        Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource ® Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource ® Test Extraction.
        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
For more information about extracting using SAP Query, see Extraction using the SAP Query.
hope this helps.
assign point if so
partha

Generic Extraction-example

hello EXPERTS
I am trying to give one presentation about 'Generic Extraction using View'...I know how to explain the process.But as I donot have project experience,I have never worked with Generic Extraction.
Can any one give an example where they used generic extraction(by view) on SAP standard tables.Its enough if you can mention the fields you used and from which tables you took these fields?
Thanks
S

Hi,
Processing steps for creating the Generic Datasource by useing View:
1.Goto RSo2.
Datasource can be created for
a). Transaction Data
b). Master data Attributes
c). Master data Text
2.Specify Application component(SD/MM..)
3.There are three extraction methods to fill datasource.
    i).Transparent table or Database view
    ii).InfoSets of the SAP query
    iii).Using a Function Module
4.Select extraction method extracts the data from a transparent table or database view.
5.select Extraction from View, then we have to create the View.
   a).specify the view name.
   b).choose the view type (Database view) from bellow mentioned views.
      Database view.
      projection view.
      maintainance view.
      help view.
6. Specify Tables and Join Conditions and define view fields.
7. Assign View to Datasource
8. Once you specify view in Data source, the extract structure willgenerate.
9. then select the filds in selection column.
10. Specify Delta-Specific Field and type.
11. Specify Safety Interval and Delta Type and select Save button.
12. Testing the Generic extraction.
Select Datasource option from menu bar-->select Test Extraction or you can check in RSA3.
Regards,
Suman.

Any docs regarding Table/View,Function Module for Generic Extraction

Hello All
I need to do Generic Extraction,for that if anyone has docs., I need docs on how to create table,view,Function module and infoset query ,on that pl forward to my id
[email protected]
Many Thanks
balaji

hi Amit
Thanks for your docs,but this docs i have already,do u have any thing different one,if so please forward?
Facing a Problem
Iam trying to create view(database view)for vbak and vbap and given in Tables in Table/Join Conditions tab and clicked in Relationship and the relantionship has been generated automatically,now when i tried to activate this view its saying like "No tables and/or fields are defined for view xxxxx(xxxx-> name of a view)
what will be the problem?pl let me know how to create a view?
And also I need to know the diffference between database view,Manintenance view,Projection view and help view?
Pl let me know on this?
Many Thanks
balaji

Where to find deltas in generic extraction

hi experts,
could you please explain me tcodes which are used to find the delta data while we go for generic extraction. Also can anyone explain me the full process of extracting the data using
infoset query and function module.
Cheers,
Pragya.

Hi
You can define delta's in generic using " calendr day, numeric pointer, time stamp."
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
source: help.sap.com
Hope it helps
kalyan

Generic extraction using table

Hello friends,
We have three methods in Generic extraction, as we know.
1. Using view/Table
2. Using FM
3. Using Infoset Query
I know pretty well the extraction using View, but when do we use "Table"?
Is there a specific method to perform generic extraction using TABLE?
Please clarify

Thanks for the replies.
In case of a generic extraction with view, i've followed the below procedure.
1. RSO2.
2.create a generic datasource by giving a view name and selecting the fields for selection criteria, save and generate.
3. replicate data sources in BW.
4. create an infosource and assign the data source, mapping and create an infopackage to load data.
Now ,
1. how do we enable Delta for this method?
2. Is this possible at all? if yes, how?
3. How do we proceed after the replication of DataSources in BI? specifically, procedure in BI?
Pls clarify.

Scenarios for Generic extraction

Hello experts ,
Please give me some scenarios where we will go for the extraction using
function module,
infoset query,
View.
Thanks in advance,
pragya.

Hi Pragya,
Generic extractors are of 3 types:
1. Based on table/view
2. Based on Infoset Query
3. Based on Function module
In some cases Business Content will not give your required data sources , In such scenarios you need to develop your own data sources ( Views / Function modules ) , Then you can bring that data source to BW and use that .
if you can't find the suitable business content data source then you have to create
your own data source ( Generic )
or enhance the given data source.
Need for customized generic extractor
Business Content may not have a suitable
Data Source for your application.
Business Content may require additional enhancements that need data that is not supplied by SAP BW.
The application may not have its own generic data extraction method.
We have used our own custom programs to populate tables in SAP system.
Please see link below
http://help.sap.com/saphelp_nw04s/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Good weblogs
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
Regards, ABY

No BERDATUM while generic extraction with LDB ADA

We do a generic extraction to BW with LDB ADA. Therefore it was created an additional field in InfoSet on note ANLAV, where BERDATE=BERDATUM. BERDATUM is a selection parameter in LDB ADA. In extractor checker BERDATE is not filled.
Does anybody have an idea what the problem is?
Regards
Pramid Mehta

Hi,
thanks for that hint. I checked this already. DataSource is ok and the field is not hidden.
Regards
Pramid

Generic Extraction creation

HI All,
I want to extract data from two tables from CRM(Z tables).
When I goto RSO2 to create a generic data source it is giving me the options of Extract from View,Extract from Info Set and Extract BY FM.
But when I select Extraction from View it is giving me an option to select from one table only.
HOw can I extract data from two tables?
Please help me
Sridath

Hi,
Check the below links, you will get more info on Generic Extraction.
Generic Extraction:
http://help.sap.com/saphelp_nw70/helpdata/en/28/4c553c42360a40e10000000a114084/frameset.htm
Check the link.
http://www.erpgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%202.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Generic Extraction with Table, View, FM & Infoset
Creating a datasource for generic extraction
Generic Extraction
Customer and Generic extraction difference ?
generic extraction
Re: Generic extractors
generic extraction
Reg
Pra

Generic extraction with function module

hai experts,
can u please forward the material about Generic extraction using FM
and infoset query with step by step and real-time requirements to my
mail id.([email protected])
Regards
DJReddy

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

Generic Extraction business Requirement, through function module,

Generic Extraction business Requirement, specifically through function module and source code in function module.

Dear Karthik,
Go to transaction SBIW -> Generic Datasource -> Maintain Generic Datasources -> Choose Master/Transaction Data -> Maintain proper entries (Application Component, Descriptions) -> Extraction by FM if you want to extract using FM.
Maintaining Generic DataSources - Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Creating a Generic DataSource
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create. The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
       Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
       Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
       Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
       Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource -> Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
·        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource -> Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource -> Test Extraction.
·        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
Also visit :[Data Extraction from SAP Source System | http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/content.htm]
Regards,
Naveen.

About Generic Extraction

Hi all,
              I would like to have some links r docs to mail about DB view extraction. I am stuck in it. I would like to know it from how to create a view and till how do i recognize a delta field in the given 2 tables.
my mail ID is [email protected]
Thanks and regards.

hi pradeep,
Maintaining Generic DataSources
Use
Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Procedure
Creating a Generic DataSource
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create.
The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process Flow
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
       6.      Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
When extracting, look at SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
        Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
        Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
        Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
        Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource ® Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource ® Test Extraction.
        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
For more information about extracting using SAP Query, see Extraction using the SAP Query.
if helpfull assign points
regards,
yunus

Urgent: Problems in Generic Extraction by Function Module

Hi BW Gurus,
I am new to SDN and also new to generic extraction using function module. My requirement is to extract long text(142 char) from CRM to BW as the text is not stored in database table I used function module read_text with in another ZXXX function module copy of (RSAX_BIW_GET_DATA_SIMPLE). In my extract structure I used GUID(char,32), Langu, long text(142 char) and 2 placeholders. Text can be extracted by passing STXH table fields(Tdname, Tdid, Tdobject, Tdspars) to read_text as parameters and i also need to use CRMD_ORDERADM_H field GUID(32 char) to compare 1st 32 chars of tdname(70 char) with Guid to select Guids and loop thru this Guids and for each Guid i need to append lines of text to e_t_data but as i donot know ABAP i unable to write the code for this. Through my friends help i wrote code when i check in RSA3 it is displaying the text but when i replicate into BW and load into data target in monitor the status is red with records initially but afterwards it will be red status again with 0 from 0 records for initial load again.when i check on job logs the errors i have are:
The background job has created a job log file of 2Gb size and it is currently on a infinite loop writing entries into the SAP System Log that it cannot write to the Job log file due to Error 22 for write/read access to a file this is because of the datasource i have created. Please find my Function module and if anyone would please correct FM and send me that will be really great.I appreciate it in advance.
MY Function Module is:
FUNCTION Z_CRMORDERH_STR_TXT.
""Local Interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE YCRM_TEXT_STR OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
***" EXCEPTIONS NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
Tables: CRMD_ORDERADM_H, STXH.
Auxiliary Selection criteria structure
data: l_s_select type srsc_s_select.
Maximum number of lines for DB table
Statics: s_s_if type srsc_s_if_simple,
counter
 s_counter_datapakid like sy-tabix,
Cursor
 s_cursor type cursor.
data: i_crmtext type standard table of TLINE .
types: begin of xsreph ,
 GUID type CRMD_ORDERADM_H-guid,
 end of xsreph.
 data: i_guid type standard table of xsreph.
data: I_TEXT type STXH-TDNAME.
data: xempl like YCRM_TEXT_STR occurs 0 with header line.
data: t_tab like dd03l-tabname.
Select ranges
ranges: l_r_guid for CRMD_ORDERADM_H-guid.
 l_r_connid for sflight-connid.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
if i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
Check DataSource validity
 case i_dsource.
 when 'yCRM_TEXT'. " for S_SREPH1
 when others.
 if 1 = 2. message e009(r3). endif.
this is a typical log call. Please write every error message like this
 log_write 'E' "message type
 'R3' "message class
 '009' "message number
 i_dsource "message variable 1
 ' '. "message variable 2
 raise error_passed_to_mess_handler.
 endcase.
 append lines of i_t_select to s_s_if-t_select.
Fill parameter buffer for data extraction calls
 s_s_if-requnr = i_requnr.
 s_s_if-dsource = i_dsource.
 s_s_if-maxsize = i_maxsize.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
 append lines of i_t_fields to s_s_if-t_fields.
we will do our selection based on what is in the p table for the
infoobject
else. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
 Following Calls FETCH only
First data package -> OPEN CURSOR
 if s_counter_datapakid = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
 LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'GUID'.
 MOVE-CORRESPONDING L_S_SELECT TO L_R_GUID.
 APPEND L_R_GUID.
 ENDLOOP.
 case i_dsource.
 when 'YCRM_TEXT'. " for S_SREPH1
 t_tab = 'CRMD_ORDERADM_H'.
 endcase.
 select GUID
 from (t_tab)
 into table i_guid where PROCESS_TYPE = 'ZACI' and ( OBJECT_ID < '0000000042').
 select tdname from stxh into i_text where tdobject = 'TEXT'.
 if sy-subrc ne 0.
 message e009(r3).
this is a typical log call. Please write every error message like this
 log_write 'E' "message type
 'R3' "message class
 '009' "message number
 i_dsource "message variable 1
 'No master data found'. "message variable 2
 raise error_passed_to_mess_handler.
 endif.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
 open cursor with hold s_cursor for
 select (s_s_if-t_fields) from CRMD_ORDERADM_H
 where GUID in L_R_GUID .
 ENDIF.
Fetch records into interface table.
named E_T_'Name of extract structure'.
 fetch next cursor s_cursor
 appending corresponding fields
 of table e_t_data
 package size s_s_if-maxsize.
 IF SY-SUBRC <> 0.
 CLOSE CURSOR S_CURSOR.
 RAISE NO_MORE_DATA.
 ENDIF.
as we are doing this only once can use the select statement.
***data: crmtext like tline occurs 0 with header line.
**data: i_crmtext type standard table of TLINE.
**data: i_guid type standard table of xsreph.
data: l_guid type THEAD-TDNAME.
data: st_guid type xsreph.
data: st_crmtext type TLINE.
data: lan type THEAD-TDSPRAS.
lan = 'E'.
loop at i_guid into st_guid.
l_guid = st_guid-guid.
CALL FUNCTION 'READ_TEXT'
 EXPORTING
 CLIENT = SY-MANDT
 ID = 'A002'
 LANGUAGE = lan
 NAME = l_guid
 OBJECT = 'CRM_ORDERH'
 ARCHIVE_HANDLE = 0
 LOCAL_CAT = ' '
IMPORTING
 HEADER =
 TABLES
 LINES = i_crmtext.
EXCEPTIONS
 ID = 1
 LANGUAGE = 2
 NAME = 3
 NOT_FOUND = 4
 OBJECT = 5
 REFERENCE_CHECK = 6
 WRONG_ACCESS_TO_ARCHIVE = 7
 OTHERS = 8
e_t_data-guid = l_guid.
loop at i_crmtext into st_crmtext.
move lan to e_t_data-langu.
move st_crmtext-tdline to e_t_data-description.
append e_t_data.
endif.
endloop.
clear: st_guid,l_guid.
refresh: i_crmtext.
endloop.
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
endif.
ENDFUNCTION.
please Gurus as I donot know ABAP i appreciate if anyone would write a FM based on requirement and send me that will be really great this is my request. I gurantee of award points for good answers.
Regards
Kishore

Hi,
The statement RAISE NO_MORE_DATA should be active (uncommented) in your code. Otherwise, the infinte loop occurs.
See also, the Siggi's blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
BTW, was it your thread here:
Re: Urgent: problems in extracting Long Text
Best regards,
Eugene

Generic extraction -Infoset

Similar Messages

Maybe you are looking for