Generic Extractor Appends Missing

Hello,
I am trying to append an already existing generic extractor. I have appended the extract structure with the new fields and it is activated. However i cannot see my new fields in RSO2 or RSA6 or the ROOSFIELD table! How do i get the new fields to show up?
Regards,
TMS

Hi...You must enter to RSA2 in order to modify the datasource structure and uncheck the "hidden" check box for this new fields....after that you will see the fields...
Regards

Similar Messages

Problems appending to a Generic Extractor

I have a Generic Extractor which is built on a customer defined table. I have tried to append a ZZ field to the Extract structure but the Append button is greyed out.
I therefore directly added the ZZ field into the structure and wrote the logic in the user exit to populate.
When I go to RSA6 the field is not visible. Why is this and how can I resolve? Thanks

Hi-
Is it possible to delete DS? If so....do that first!
goto RSO2 Create it again
RSA6/Select DS/Enhance Extraction Structure/Add fields/Activate
CMOD/Program/Include....
Then come back to RSA6, try it
I hope this can be out the issue!
Thanks,
Chandra.

Generic extractor and an append structure

Hi all,
this system is driving me crazy. So, that's something worked in former times..
I created an generic extractor on VEKP. I have not restricted to any selection criteria or hide any field. The system generated the extractor and everything is fine. THEN I created an append on the generic extractor and put different fields inside the append. I want (and this works) to fill this different field via user exit for extraction. All field in the append are having the prefix ZZ, all field are characteristic and there is no inconsistency in the append. I activated the append.
AND NOW - none of the fields of the append is available in RSA6 to hide or none hide or do anything. They are not available. By checking with SE11 on the generated structure - all field including the append are there.
We are on ECC 5.0 with PI 2004.1 for 5.0 SP 10.
Can anyone help. As i told you, this worked in former times (with SAP 4.6C with PI 2004.1 or lower).
Regards
OJ

Hi Siggi,
I have not created an special Append on the VEKP. I created an generic extractor on the VEKP. All fields of VEKP are available and I can hide or choose selection-field for all of these fields. No problem.
i created an append on the extract structure via RSA6 - enhancement. I know that after generating the generic extractor with RSO2 all settings done in former times in RSA6 are lost. But, my problem is: I can not see any of the fields I put into the append. They are not there. Not in ROOSFIELD and following not in RSA6. And that's the problem.
Thanks for your support.
OJ

0WBS element (external format) as append field in generic extractor?

Hi Guru's,
we use an generic extractor for our CO-PA data, as a join of different tables. Now I get the issue with this internal format of PSP element. It is of NUMC 8 and my basic data PSP element is CHAR 24. As they are not matching I want to add the POSID as an append field. But how to do this?
In table PRPS I found the Include PRPS_INC an thought about using this in my extract structure? Is this possible? How do I need to go on and to simply have my additional field - with content! - in my extract structure?
First I used an append and put in my include. As there are no fields extracted to BI I think this is wrong!? How can I delete my append?
Thanks

Hi Siggi,
I have not created an special Append on the VEKP. I created an generic extractor on the VEKP. All fields of VEKP are available and I can hide or choose selection-field for all of these fields. No problem.
i created an append on the extract structure via RSA6 - enhancement. I know that after generating the generic extractor with RSO2 all settings done in former times in RSA6 are lost. But, my problem is: I can not see any of the fields I put into the append. They are not there. Not in ROOSFIELD and following not in RSA6. And that's the problem.
Thanks for your support.
OJ

Missing new fields in generic extractor but present in table view

Hi
I can't see new fields in generic extractor but they are present in the table view.
Few days ago I created a generic datasource based on table view. Now I included 2 more fields in the table view but these fields doesn't show in RSA6 and RSO2.
how can i resolve this.
thanks

Hi Bhat,
GO to RSA5 and give ur generic extractor name ....
Click on edit the newly added fields will be hided ...so u need to uncheck the hide olumn
once this is done save that.
U will find the fields in RSA3 and RS02
Regards
vamsi

Generic Extractor on Table VBAP

Hi Gurus,
I want to develop a Generic Extractor on table VBAP, but unfortunately its not giving me the extract structure when I save in RSO2, the screen wherein we select our fields are not displayed. Is there anything i am missing in the steps. Pls help us out with this issue.
I am able to create the generic extractor with other tables with usual proceedure.
Thanks in Advance.
Regards,
MSS

Hi
This is the problem with the amount and currency reference fields in your extract structure.
"This operation failed, because the template structure quantity fields or currency fields, for example, field CMPRE_FLT refer to a different table."
As you have an amount field, the currency reference table might be different and hence, it is giving this error.
I think u need to create view and then append the currency or quanity fields , and populate them through User exit.
Hope this helps.
Sonal...

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

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.

Generic extractor question/problem

Hello,
I want to create a generic extractor on custom table which should delta enabled . This custom table has ERDAT( creation date) and ERZET u2013 Entry time but the client is asking me to use both fields for delta functionality . I am not sure how to do this . Please help .
Regards,

As you said client want you to use both the date n time stamp field to extract delta you can follow the below steps.
- Create the generic data source as per you requirement in order to pic the delta
- Open you extract structre and append the field TZNTSTMP, this is the field which holds the time stamp.
- to setup deltas click on generic delta --> select time stamp(UTC)
Regards
KP

Generic extractor OK in RSA3 but no result with IP

Hi Gurus
I have a generic extractor which runs well in RSA3 but when I call it with an IPAK the R/3 job (BI_REQ) runs forever and gives no result.
This happens in full and delta mode.
Any ideas ?
Thanks

Here is the main code.
The idea is to use the input packet to create an output packet with the same structure but different fields populated.
FUNCTION zbw_biw_pricing.
*"*"Interface locale :
*" 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
*" 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 ZBW_KONH OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
* DI.08.0055 Remontée prix VKPB
* 'Delta hook' par BTE, voir transactions FINF, FIBF et
* MF Z_BW_BTE_DELTA_00503301_01 et Z_BW_BTE_DELTA_00503301_01_WRI
* Création
* Auteur: JWA Date: 30/04/2007
* DataSource for view of Delta Q alimenté par le BTE
TABLES: zbw_konh, usr01.
* 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,
* Vue 1 article actifs -> 1 GM
 t_mara TYPE STANDARD TABLE OF zmatnr_matkl,
* Vue 1 GM -> n articles actifs
 t_mara2 TYPE STANDARD TABLE OF zmatnr_matkl,
* Vue 1 division -> 1 OA + 1 Société
 t_zvt001_wk TYPE STANDARD TABLE OF zvt001_wk,
* Date de validité pricing
 w_datextract TYPE sydatum,
 w_separator TYPE zseparateur,
* Data pour selections IP
 l_r_matnr TYPE STANDARD TABLE OF matnr_ran WITH HEADER LINE,
 l_r_werks TYPE STANDARD TABLE OF werks_ran WITH HEADER LINE,
 l_r_spart TYPE STANDARD TABLE OF spart_ran WITH HEADER LINE,
 l_r_matkl TYPE STANDARD TABLE OF matkl_ran WITH HEADER LINE.
* Data pour paramètrer VKPB
DATA :
 t_matnr_low TYPE STANDARD TABLE OF matnr_ran ,
 t_werks_low TYPE STANDARD TABLE OF werks_ran ,
 w_t_mara TYPE zmatnr_matkl,
 w_e_t_data TYPE zbw_konh,
* Data pour liste VKPB
 t_liste TYPE STANDARD TABLE OF abaplist ,
 t_listasci TYPE STANDARD TABLE OF zchar150 ,
* Paquet retourné d'après la liste VKPB.
 e_t_data2 TYPE STANDARD TABLE OF zbw_konh .
* 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 'ZDS_PRICING'.
 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
 APPEND LINES OF i_t_fields TO s_s_if-t_fields.
* Date extraction
 w_datextract = sy-datum.
* Vue 1 article actif -> 1 GM pour binary search.
 SELECT matnr matkl spart FROM mara INTO TABLE t_mara
 WHERE lvorm = ' '.
 SORT t_mara BY matnr.
* Vue 1 GM -> n articles actifs pour binary search.
 t_mara2[] = t_mara[].
 SORT t_mara2 BY matkl.
* Vue 1 division->1 OA, divison->1 société pour binary search
 SELECT * FROM zvt001_wk INTO TABLE t_zvt001_wk.
 SORT t_zvt001_wk BY werks.
* Séparateur
 SELECT SINGLE * FROM usr01
 WHERE bname = sy-uname.
 IF usr01-dcpfm = 'X'. "decimal separator is point
 w_separator-sep1 = ',' . "suppress commas
 ELSE.
 w_separator-sep1 = '.' . "suppress points.
 ENDIF.
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 = 'MATNR'.
 MOVE-CORRESPONDING l_s_select TO l_r_matnr.
 APPEND l_r_matnr.
 ENDLOOP.
 LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'WERKS'.
 MOVE-CORRESPONDING l_s_select TO l_r_werks.
 APPEND l_r_werks.
 ENDLOOP.
 LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'SPART'.
 MOVE-CORRESPONDING l_s_select TO l_r_spart.
 APPEND l_r_spart.
 ENDLOOP.
 LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'MATKL'.
 MOVE-CORRESPONDING l_s_select TO l_r_matkl.
 APPEND l_r_matkl.
 ENDLOOP.
* Determine number of database records to be read per FETCH statement
* from input parameter I_MAXSIZE.
 OPEN CURSOR WITH HOLD s_cursor FOR
* SELECT (s_s_if-t_fields) FROM zbw_konh
 SELECT kotabnr vakey FROM zbw_konh
 WHERE
 kvewe = 'A' AND "Détermination prix
 kappl IN ('M','V') AND "ADV et Achats'
* A modifier si nouvelle condition, + extraction des champs paramètre
 kotabnr IN ('017', '018', '071', '073', '074', '079') .
 ENDIF. "First data package ?
* Fetch records into interface table.
 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.
* Dérivation des paramètres pour VKPB
 PERFORM params_vkpb
 TABLES
* Paquet entrée
 e_t_data
* Paramètres lancement VKPB
 t_matnr_low
 t_werks_low
* Paramètres venant de l'IP
 l_r_matnr
 l_r_werks
 l_r_matkl
 l_r_spart
* vues
 t_mara
 t_mara2
 t_zvt001_wk.
* Appel de VKPB si au moins un article trouvé
 IF NOT t_matnr_low[] IS INITIAL.
 PERFORM submit_vkpb
 TABLES
* Paramètres lancement VKPB
 t_matnr_low
 t_werks_low
 t_listasci
 USING w_datextract.
* Interpretation Liste VKPB
* BREAK ALEREMOTE.
* BREAK JWADDELL.
 PERFORM list_vkpb
 TABLES
 t_listasci
 e_t_data2
* Paramètres venant de l'IP pour filtrage
 l_r_spart
* pour le cas toutes divisions
 l_r_werks
* vues
 t_mara
 t_zvt001_wk
* Date validité
 USING w_datextract
 w_separator.
* Retourner paquet
 e_t_data[] = e_t_data2[].
 REFRESH e_t_data2[].
 ELSE.
* no data
 REFRESH e_t_data[].
 ENDIF.
 s_counter_datapakid = s_counter_datapakid + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.=

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 help needed badly.

Hi Geeks,
As continuation to questions I posted in the morning.
1> I have created a generic extractor say ZBW_PRICING.
2> ZBW_PRICING is based on tables A508 & KONP.
3> One of the currency fields I am interested in that is
   KBETR has reference field RV13A-KBETR.
4> Rv13A is a structure not a DB table so I can not give
   reference to RV13A while building view.
5> So I appended the extract structure with two fields.
   ZZKBETR (rate) & ZZKONWA (currency key) to populate it from KONP.
6> I activated the appended structure as well as extract structure.
7> In RSA6 when I try to unhide field & save it.
   I get following error.
   The OLTP source still has errors.
   Message no R8417.
Please help fellows its important for me.
thanx in advance.
Monica

Kunal and Subray,
I had the same problem while trying to unhide the field.
I solved the error by giving the proper reference table and field names to the required field in extract structure, which in my case has been a currency field.
( Since I have a generic extractor, I changed the Reference Table name to Transparent table name. I changed the field name to corresponding field name within the Transparent table).
Thank you.
(Also, I see that Transparent Table name = extract structure name = DataSource name. I think the names might be same for Generice Datasources by default)

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

Generic Extractor Appends Missing

Similar Messages

Maybe you are looking for