Generic extractor replication process

Hi All,
How to replicate Generic extractor in BI7.O?
In BI 7.0 transport required for Generic extractors to replication?
Please guide me.
Thanks,
KN

Hi Kumaran,
To Replicate follow the below steps,
1.Go to Source System>Select your Source System(R3/ECC)>Double Click it-->It will Take u to the DS Screen
2.Select your DS(It should be your MM,SD etc...)-->Expand the tree and check the DS which needs to be replicated
3.Right Click and select Replicate...
Hope it should work... Cheers
Regards,
Syed

Similar Messages

Delta fo Generic extractor using function module

Hi,
I am using the following function module for generic extractor but its always showing me extraction error.Could anyone please suggest to resolve the issue.
Thanks in advance fo rsuggestion.
FUNCTION Z_BW_SALESDATA_EXTRACT_CHNG2.
""Local interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*" VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*" VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*" VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*" VALUE(I_PRIVATE_MODE) OPTIONAL
*" VALUE(I_CALLMODE) LIKE ROARCHD200-CALLMODE OPTIONAL
*" VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*" I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*" E_T_DATA OPTIONAL
*" E_T_SOURCE_STRUCTURE_NAME OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
The input parameter I_DATAPAKID is not supported yet !
Example: InfoSource containing TADIR objects
TABLES: VBFA,VBRK,tadir.
Auxiliary Selection criteria structure
DATA: l_s_select TYPE sbiwa_s_select.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize.
user defined variables.
DATA : X_UPDMODE(1) Type c, " Update Type
 X_LastUpdate Like Sy-Datum. " Last Update Date
 X_LastUpdate TYPE RODELTAID. " Last Update Date "TCS_KAP
Select ranges
RANGES: L_R_VBELN FOR VBAK-VBELN,
 L_R_AUDAT FOR VBAK-AUDAT.
Parameter I_PRIVATE_MODE:
Some applications might want to use this function module for other
purposes as well (e.g. data supply for OLTP reporting tools). If the
processing logic has to be different in this case, use the optional
parameter I_PRIVATE_MODE (not supplied by BIW !) to distinguish
between BIW calls (I_PRIVATE_MODE = SPACE) and other calls
(I_PRIVATE_MODE = X).
If the message handling has to be different as well, define Your own
messaging macro which interprets parameter I_PRIVATE_MODE. When
called by BIW, it should use the LOG_WRITE macro, otherwise do what
You want.
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
The input parameter I_DATAPAKID is not supported yet !
Invalid second initialization call -> error exit
 IF NOT g_flag_interface_initialized IS INITIAL.
 IF 1 = 2. MESSAGE e008(r3). ENDIF.
 log_write 'E' "message type
 'R3' "message class
 '008' "message number
 ' ' "message variable 1
 ' '. "message variable 2
 RAISE error_passed_to_mess_handler.
 ENDIF.
Check InfoSource validity
 CASE i_isource.
 WHEN 'Z_BW_SDDATA_CREATEON'.
 WHEN 'Y'.
 WHEN 'Z'.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE e009(r3). ENDIF.
 log_write 'E' "message type
 'R3' "message class
 '009' "message number
 i_isource "message variable 1
 ' '. "message variable 2
 RAISE error_passed_to_mess_handler.
 ENDCASE.
Check for supported update mode
 CASE i_updmode.
 WHEN 'F'.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE e011(r3). ENDIF.
 log_write 'E' "message type
 'R3' "message class
 '011' "message number
 i_updmode "message variable 1
 ' '. "message variable 2
 RAISE error_passed_to_mess_handler.
 ENDCASE.
Check for obligatory selection criteria
 READ TABLE i_t_select INTO l_s_select WITH KEY fieldnm = 'VBELN'.
 IF sy-subrc <> 0.
 IF 1 = 2. MESSAGE e010(r3). ENDIF.
 log_write 'E' "message type
 'R3' "message class
 '010' "message number
 'PGMID' "message variable 1
 ' '. "message variable 2
 RAISE error_passed_to_mess_handler.
 ENDIF.
 APPEND LINES OF i_t_select TO g_t_select.
Fill parameter buffer for data extraction calls
 g_s_interface-requnr = i_requnr.
 g_s_interface-isource = i_isource.
 g_s_interface-maxsize = i_maxsize.
 g_s_interface-initflag = i_initflag.
 g_s_interface-updmode = i_updmode.
 g_s_interface-datapakid = i_datapakid.
 g_flag_interface_initialized = sbiwa_c_flag_on.
Store Update mode in static variable...
 X_UPDMODE = I_UPDMODE.
 Select Single DELTAID
 Into X_LastUpdate
 From ROOSGENDLM
 Where OLTPSOURCE = 'Z_BW_SDDATA_CREATEON'.
 If X_LastUpdate Is Initial.
 X_LastUpdate = '19800101'. " The oldest..., this should not happen
 Endif.
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 g_t_segfields.
ELSE. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
 Following Calls FETCH only
X_UPDMODE = I_UPDMODE.
First data package -> OPEN CURSOR
 IF g_counter_datapakid = 0.
Fill range tables for fixed InfoSources. In the case of generated
InfoSources, the usage of a dynamical SELECT statement might be
more reasonable. BIW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
 LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'VBELN'.
 MOVE-CORRESPONDING l_s_select TO L_R_VBELN.
 APPEND L_R_VBELN.
 ENDLOOP.
 LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'AUDAT'.
 MOVE-CORRESPONDING l_s_select TO L_R_AUDAT.
 APPEND L_R_AUDAT.
 ENDLOOP.
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 InfoSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
*added by Yogesh
 DELETE FROM ZBWSALEDATA.
*ended by Yogesh
 l_maxsize = g_s_interface-maxsize.
Check for supported update mode
 CASE X_UPDMODE.
 WHEN 'F' Or 'I'. " Full or Init
**get sales orders
 SELECT *
 INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
 FROM VBAK AS K
 INNER JOIN VBAP AS P
 ON PVBELN = KVBELN
 WHERE K~VBELN IN L_R_VBELN
 AND K~AUDAT IN L_R_AUDAT
 AND K~VBTYP = 'C'.
 IF I_SALESDATA[] IS NOT INITIAL.
 PERFORM F_GET_DATA. "get data
 PERFORM F_DEL_VATCOND. "delete vat conditions
 PERFORM F_GET_TAR_COSTUNIT. "get tariff cost unit
 PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
 PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
 PERFORM F_INSERT_DB_ZBWSALEDATA. "insert into table ZBWSALESDATA
 LOOP AT I_SALESDATA WHERE NETPR = 0.
 MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
 APPEND I_SALESDATA_FIN.
 ENDLOOP.
 SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
 DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
 COMPARING VBELN POSNR
 KSCHL.
 INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
 ENDIF.
 WHEN 'D'. " Delta
 SELECT *
 INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
 FROM VBAK AS K
 INNER JOIN VBAP AS P
 ON PVBELN = KVBELN
 WHERE K~ERDAT >= X_LastUpdate
 WHERE K~ERDAT >= X_LastUpdate+0(8) "TCS_KAP
 AND K~VBTYP = 'C'.
 IF I_SALESDATA[] IS NOT INITIAL.
 PERFORM F_GET_DATA. "get data
 PERFORM F_DEL_VATCOND. "delete vat conditions
 PERFORM F_GET_TAR_COSTUNIT. "get tariff cost unit
 PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
 PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
 PERFORM F_INSERT_DB_ZBWSALEDATA. "insert into table ZBWSALESDATA
 LOOP AT I_SALESDATA WHERE NETPR = 0.
 MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
 APPEND I_SALESDATA_FIN.
 ENDLOOP.
 SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
 DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
 COMPARING VBELN POSNR
 KSCHL.
 INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
 ENDIF.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE E011(R3). ENDIF.
 LOG_WRITE 'E' "message type
 'R3' "message class
 '011' "message number
 I_UPDMODE "message variable 1
 ' '. "message variable 2
 RAISE ERROR_PASSED_TO_MESS_HANDLER.
 ENDCASE.
**end get sales orders
 OPEN CURSOR WITH HOLD g_cursor FOR
 SELECT (g_t_fields) FROM ZBWSALEDATA.
 WHERE pgmid IN l_r_pgmid AND
 object IN l_r_object.
 ENDIF. "First data package ?
Fetch records into interface table. There are two different options:
- fixed interface table structure for fixed InfoSources have to be
named E_T_'Name of assigned source structure in table ROIS'.
- for generating applications like LIS and CO-PA, the generic table
E_T_DATA has to be used.
Only one of these interface types should be implemented in one API !
 FETCH NEXT CURSOR g_cursor
 APPENDING CORRESPONDING FIELDS
 OF TABLE E_T_DATA
 PACKAGE SIZE l_maxsize.
 IF sy-subrc <> 0.
 CLOSE CURSOR g_cursor.
 RAISE no_more_data.
 ENDIF.
 g_counter_datapakid = g_counter_datapakid + 1.
ENDIF. "Initialization mode or data extraction ?
Best regards,
Yogesh

Dear Yogesh,
Try to debug the code by putting a break point at select statement...is the FM Syntactically correct ??
Check the Select statements..if all fields are not required avoid using Select * , and use always for all entries rather than JOINS..
Note : For Joins you have to specify the Fields in the Select...Dont use Select * ....
Hope it helps..
Thanks,
Krish

Create generic extractor based on 2 tables

hey BI gurus,
I have to create a generic extractor based on these 3 tables:
eban - i need all fields
vttk - i need only 4 fields i.e
                                     route,
                                     tknum,
                                     datbg,
                                     daten
ekbe - budat.
now the problem is thr is no common field between vttk & eban AND vttk & ekbe. but thr is a common field between eban & ekbe.so i can create a view only on these 2 tables but i want 3 tables
how do i proceed???

Hi,
Sometimes, if your application or requirement makes it necessary, you have to create your own function module to extract the data from whatever sap system to bw.
Therefore you normally make a copy of the standard fm 'RSAX_BIW_GET_DATA_SIMPLE'. To make this new function work for you, you have to realize the following.
1.) the fm gets called by the extraction api for at least 2 times. First time is for initialization and from the 2nd time on it is for data extraction.
2.) right after the last data package (somehow you need to make sure that it is the last one) you have to raise the exception no_more_data.
Refer this links for more Info
SAP BI Generic Extraction Using a Function Module
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
SAP Network Blog: Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Take the help of an ABAPer if your are new to this process
Regards
Karthik
Assigning points is the way to say thanks

How to Generate Information Errors in Generic Extractor Function Module

Hi, In my Generic Extractor logic I am reaching out to an additional table to get a field. I would like to produce an informational error or red error in the process monitor if I'm unable to get the field. Is this possible? How can I generate these messages in the Extractor Function Module?
Thanks!

Hi,
Please go through the below doc. It explanins each and every step of creation of generic extractor through Function module.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c062a3a8-f44c-2c10-ccb8-9b88fbdcb008?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aefb04-7043-2c10-8e92-941536eebc79?quicklink=index&overridelayout=true
Regards,
mahesh

Generic Extractor built on an infoset which uses a logical database

Is anyone aware of any performance issues when building an infoset generic extractor which uses a logical database as the source? Also would anyone also be aware the process of collecting data for extraction? Thanks

Hi Arun,
Thanks for this - I have been informed that there are issues with a small subset of data and I just wanted to get an idea if the steps that would be carried out be the same if the generic extractor is built on table joins or logical data base or does the latter actual carry out say some pre processing steps

Text load af vendor sub range - generic extractor

Hello BW experts,
I have created a generic extractor for transfering vendor sub range texts into the text table of an info object. However the text doen't end up in the table..
It transfers all included lines in the source table to BW, but I get the error message that some posts are duplicate in the PSA. Nothing ends up in the destination table... Can certain lines be erased in the PSA? Could this really be the reason for the difficulties to load?
Please help!!!
BR,
Fredrik

Hi Fredrik,
In your InfoPackage > Processing tab > choose Only PSA and Update Subsequently into Data Targets and also Ignore Double Data Records. This way you will not get the duplicate entries error message and the data should load.
Hope this helps...

Generic Extractor Question

Hi
I would like to create a Generic Extractor on table QMFE which has Created Date and Changed Date fields.
If I have to get deltas, I can use only one field in Extractor for Delta option: Either Created Date or Change Date.
If I use Create Date, I'll miss Changes and vice versa.
I felt Function Module Extractor will be 2much complex.
Can any one suggest what is the best approach to get deltas in this scenario?
Thanks
Sree
Please search the forum before posting a thread
Edited by: Pravender on Aug 12, 2011 3:59 PM

Hi Sree,
1) The simplest approach will be to create a single extractor and set the delta pointer to Changed Date, but this is only possible if you populate changed date = Created date for the very first time you create records. So that by using changed date you will not miss any newly created delta records, check with your functional team whether this is possible or not?
2) Otherwise you can create two generic extractors and use two different delta pointers one with Created Date and other with changed date. In the generic extractor you simply need to set your delta pointer and modify the OPEN CURSOR statment to include the proper delta field in selection of data. Rest of your code will be same for both the extractors.
Now if you go for 1st approach then you will have to create only one IP in BW and include it in process chain but in 2nd approach you will have to create two IP (one for each DS) and include both in process chain. It will only increase your data loading time.
Regards,
Durgesh.

Error in delta generic extractor

I made a generic extractor using a Module Function. And I used the RSVD_BW_GET_DELTA_DATA function, as an example to implement the Delta process for my own generic extractor.
Although when I executed the Delta process in the RSA3 transaction, the program did not use the function I made, but used the RSC1_DELTA_BIW_GET function! So the delta process did not extract any data.
I also modified EXMETHOD field from the ROOSOURCE table:
I changed the status from F2 to F1.
Could you explain me how the delta process works in a Generic Extractor?
Is any special configuration that I missed?
Thanks for your cooperation and regards.

Hi Sirneni,
Is your Init load in BW successfull. Only after
successfull completion of init load in BW the data source appears in delta queue RSA7 in R/3. Also check whether any materials are being changed in R/3 because u r delta is based on last changed date.
Regards,
Prakash B

Generic Extractor using FM with Delta Logic

Hi,
i want to create a generic extractor with Delta Logic based on a FM.
The extractor works fine for full loads (extractor method "F" or "C"), but delivers no record for the extractor method "D" (Delta). I placed a hard coded break-point in the FM, so that the processing should stop while testing it with TC "rsa3". Using the extractor method "D" the debugger doesn't stop. So it seems, that this FM will not be processed for method "D". What could be wrong?
I tried different ways to create the generic extractor:
First i copied the template "RSAX_BIW_GET_DATA_SIMPLE" and tried to get the information for delta-run by "LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'DATE_FIELD'." But as the processing for method "D" does not consider the FM, there is no chance to get delta data.
On second try i used the template "RSAX_BIW_GET_DATA" and changed "EXMETHOD" from "F1" to "F2" in table ROOSOURCE for the Data Source. In this case i get information about the Update mode (Parameter i_updmode). But the processing leaves the FM for extractor method "D" out too.
Does anybody know, why the FM is not processed for extractor method "D"?
Is there another way to get delta capable extractors based on FMs?
Thanks for help in advance!

Hello
See this blog which uses the same FM with explanation
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
See this forum too
Generic Delta Function Module
Other docs
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm
Thanks
Chandran

Generic Extractors for LO

Hi,
Has anyone attempted to write their own generic extractors to mimic the LO process because the results from this module did not meet their requirements? Would you recommend doing this?
Thanks
"Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws." ~ Plato (427-347 B.C.)
"Forgive your enemies, but never forget their names." ~ John F. Kennedy (1917-1963)
Forgivenes - Just get out of my life and spare me the anguish of pitying you ~ Anonymous Author
Message was edited by:
Ellen DeGeneres

The LO process of extraction cannot be mimicked. If the requirement is such that you need more/different fields then you have the following options.
1. If the fields are in the extract structure of the datasource in question then just add the fields to the datasource and use the LO extraction process.
2. If you need to add some fields which are not in the extract structure of the datasource then add them to the datasource and use user exit to fill them.
3. If the need is for a completely different extractor. Then creat the extractor in RSO2,
More detailed info is in the weblogs by Robert Negro.
Hope this helps.
Bhargava

Difference between Customer Generated Extractors and Generic Extractors

Hi all,
Can anyone please tell me the difference between Customer Generated Extractors and Generic Extractors. I know that for all modules Generic extraction is possible by creating a datasource(RSO2) on top of a table, View or SAP Query in SE11. What are customer generated extractors like LIS, CO/PA and FI/SL.
What kind of extraction is used for FI/AR and FI/AP. To my understanding we have BW Content Extractors. Can anyone explain the extraction method and delta extraction for AR and AP.
Thanks,
Sabrina.

Hi,
Customer generated extractors are running on top of statistics data collection process in R/3. They extract data from statistical tables already available in R/3 and also use the mechanism already provided in R/3 to capture the delta.
For example, PO data goes to statistical table S012 (it is an LIS table) and you can build a generated extractor on top of it. The difference between such extractor and a generic one is the fact that these extractors (eg LIS) use the same mechanism of capturing delta that the statistics table was doing (for example data that goes into S012 is also captured by these generated extractors). Some system tables and structures are generated automatically to support this functionality, you do not have to develop anything for this.
Generic extractors on the other hand simply let you pull data from table/view/query etc. You have to develop code/functionality to support delta capturing for such extractors. If you built a generic extractor on top of S012 (it is a statistical table - LIS), you can pull its data to BW, but you do not have the delta capturing functionality in such case, you will have to code it yourself.
As a thumb rule, you go with the standard/generated extractors, and use generic extractors only if it is necessary to be so.
FI/AR and FI/AP extractors are part of business content (I think) and support delta functionality. To get detailed info on these, you can also look at help documentation -
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
cheers,

Creation of generic extractor in CRM

Hi Experts,
I want to create generic extractor in CRM.
In R/3 we can use table like VBAK,VBAP..etc while creating Generic extracor.But I am not able to find tables for transactions like Activities,Opportunities ...etc in CRM.
Pls let me know how to find tables in CRM.
Regards
Vishal.

Hi Vishal,
The orders tables in CRM are CRMD_ORDERADM_H (header) and CRMD_ORDERADM_I (item-level).
For other tables, usually they begin with CRMD_*. They're related to document informations, like for example: CRMD_PARTNER for partners, CRMD_ORGMAN for document organizational data, and so on....
Kind regards,

Problem in creating a Generic Extractor on a custom 'Z' table

This is regarding an earlier question I posted in sdn today. I am trying to create a generic extractor on a custom 'Z' table and iam getting the following message.
Invalid extract structure template YBW_Z3PVR of DataSource YCNA_3PVAR_RPT
Message no. R8359
Diagnosis
You tried to generate an extract structure with the template structure Z3PVR. This operation failed, because the template structure quantity fields or currency fields, for example, field MENGE refer to a different table.
Procedure
Use the template structure to create a view or DDIC structure that does not contain the inadmissable fields.
Please advise. how do i solve this?

Hi there,
Is your Z* table working? It must be add check field for quantity field and currency field.
Hope this helps.

Error while creating Generic Extractor via Function Module

Hello Guys
I have created a Generic Extractor through a Function Module. I took the Standard FM: RSAX_BIW_GET_DATA_SIMPLE, gave it a new name and activated it. I made a few changes in it, like giving my structure name for E_T_DATA and giving the list of tables, from where I need to get the data. Then I created the datasource in RSO2 by giving this function module and the extract structure.
The DS was created properly, but when I check in RSA3 for records, its giving me an error: ---> The extraction program does not support object YCNA_INVY_TRNS
What do i do now? Can someone please tell me, what changes I need to make in the standard FM to suit my requirements??
Thanks.

Hi,
Just try to reactivate the structure once again. And when you open the function module, if the problem still persists just try to press Return key several times. The message you are getting is just a warning message.
PS: I am not sure whether this is the correct way, but i personally resolved this by pressing the ENTER key 4 or 5 times. So just give a try.
Regards
Sunil

Creation of a generic extractor and data source for the FAGLFLEXA table

Hi All,
Need to create a generic extractor and data source for the FAGLFLEXA table to support AR reporting. This table contains the necessary profit center information to perform LOB reporting against the AR data.
Please advice on how to do this.
Regards, Vishal

Hi Vishal,
Its seems a simple a work out.
1.Go to RSO2 & choose the relevant option ie. whether you want to create Transactional DS, Master Data DS or Text DS.
2. Name it accordingly & then create.
3. Give description to it & then give table name FAGLFLEXA.
4. Save it & activate. If you need it to be delta enabled then click over Delta & you can choose accordingly.
If you still face some problem then do mail me at [email protected]
Assign points if helpful
Regards,
Himanshu

Generic extractor replication process

Similar Messages

Maybe you are looking for