Question:
Hi Guys,
I want to extract the KONV able from R3 side and bring it to BW, when I use generic datasource extraction using RSO2 it is not allowing me to create it and saying "EXTRACTION FROM POOL TABLES AND CLUSTER TABLE IS NOT PERMITTED".
I will appreciate if u hel me how to extract this table.
thnaks
lp
Answer:
One way is to create an ABAP program and include any filters and conditions from this table to SELECT necessary data from it and write the end results to a Z custom table. Then use RSO2 on this Z custom table for the datasources for BW.
Answer:
Hi, Can I create an InfoSet Query to generate a Generic Data Source for this cluster table KONV
Thanks
Answer:
No, the limitation of InfoSet Querys (SQ01/SQ02, formerly ABAP Query) is that it won't work on Pool or Cluster tables. You either must use ABAP to pull the data, or use ABAP to create a ZTABLE with which to dump the data to.
This is the same limitation as RSO2. The only other alternative would be if you had a third party extractor.
- Stephen
Answer:
Hi.. You know I haven't tried this approach, so I can't really add any comments. Hope others have done this can make additional comments.
Answer:
/forums/viewtopic.php?t=67873&postdays=0&postorder=asc&start=0
Not sure if this can be of use for you. It is talking about a corresponding transparent table for KONV.
Answer:
Hi,
My Project Manager is saying:
Special Comments: The KONV Table is a Pooled Table. Data cannot be directally pulled from a pool table. So the data must be extracted via an InfoSet Query. Remember to set the Query Area to Global before you start creating the Functional Area. The InfoSet used for Extraction must belong to the Global Area. Set the Query Area to Global - SQ02 - Environment -Query Area.
My question is - the above statement is correct or not, again is it possible to do using InfoSet Query?
Thanks for all ur responses...
lp
Answer:
No the above statement is NOT correct, the limitation of InfoSet (ABAP) Queries is as I stated - pooled and cluster tables are not able to be queried.
The only way (*I think*) that you could use an InfoSet query is by incorporating ABAP code to read out the data in KONV, however I am not an ABAP'er so I can't say for sure. I just know that you can incorporate ABAP code into an InfoSet.
Not remembering KONV off the top of my head, if it is like BSEG, I am guessing there are other tables (which are not pooled or clustered) that you could access to get to the same information.
- Stephen
Answer:
One way is to really try it on your system and experiment to see if it works. It seems that you can according to the link here because most HR tables are cluster tables.
http://help.sap.com/saphelp_pserv463/helpdata/EN/f9/cc9138e4a0341fe10000009b38f8cf/content.htm
If you're trying to make it work, another approach is to create a View - a Projection View of KONV and go from there if you don't want to code ABAP.
Answer:
Hi Guys,
Creating an Extractor using Infoset Query for a Cluster table is possible.
The spoon feeding steps are:
First got to SQ03 click Environment <> Query Area <>
Select Global Area(Cross-client)
#1. Create a user group (SQ03)
#2. Create Functional Area (SQ02)
#2a. Assign Functional Group
#3. Create a Query (SQ01) and execute it
#3a. Go to [b]Basic list [/b]and select the fields
#4. Got to RSO2 and create Data Source
#5. Go to BW and replicate it
thanks
lp
Answer:
If you want to access a cluster table in Query SAP you have to access it through a logical database. Look for logical databases using KONV.
Answer:
Hi
I would go for a function module - it's fast and doesn't have any limitations. The best way to extract data!
Good luck!
Answer:
SMOX,
Would you please detail how to 'go for a function module' with KONV as an example?
Thanks,echoes
Answer:
Use functin module "RSAX_BIW_GET_DATA_Simple" as a template.
SSH.
Answer:
If you are interested only in billing documents, you could create an InfoSet on logical database VFV and join KONV, VBRK and VBRP. That way you will extract only billing documents from KONV. Then create a generic extractor with the fields from the InfoSet that you require.
You still have the limitation of generic extraction in terms of volumes of data though - therefore accumulating history could be painful (you would need to determine suitable selection ranges) dependent on data volumes and the size of the pricing schemas.