Generic Extractor Issue

Hello Experts,
I have one small doubt on the Generic Extractor. My Generic Extractor is based on the Delta with the changed on Field(AEDAT) and I wanted to know is it possible to extract the data if changed on is not updated to the document but other fields are getting updated.
Like if the Sales Document status is changing from One status to other. In this case the AEDAT for that sales order wont get updated. in this case is it possible to extract that record as Delta thru the Generic Extractor if the Extractor is based on AEDAT.
Suggestions will be appreciated..
thanks
Bulli

Hello Bulli
Its very muc possible to define delta on 2 fields in generic data source , you need to use created on and changed on field to define delta by modifying standard extractor program
follo below threads
generic delta using function module with two fields AEDAT AND ERDAT
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Thanks
Tripple k

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

How to reduce long extraction time - Generic extractor based on view

Hello. The previous thread about this error was closed without any answer.
I'm in the same configuration.
"Using a generic extractor (Delta enabled on confirmation date) based on view to load data from ECC6 to BI.
Now my issue is that the delta extraction is running for a long time (around 1 hr) even if the data volume is very small
While checking the job overview in source system i saw that the job is hanging at the below step for almost 1 hr."
1 LUWs confirmed and 1 LUWs to be deleted with function module MF RSC2_QOUT_CONFIRM_DATA.
I am not understanding why this is happening.
Here is the log of the job:
30.05.2011 03:58:11 Job started
30.05.2011 03:58:11 Step 001 started (program SBIE0001, variant &0000000166864, user ID ALEREMOTE)
30.05.2011 03:58:11 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
30.05.2011 03:58:11 DATASOURCE = 0CO_OM_WBS_6
30.05.2011 03:58:11 *************************************************************************
30.05.2011 03:58:11 *          Current Values for Selected Profile Parameters               *
30.05.2011 03:58:11 *************************************************************************
30.05.2011 03:58:11 * abap/heap_area_nondia......... 4000000000                              *
30.05.2011 03:58:11 * abap/heap_area_total.......... 8000000000                              *
30.05.2011 03:58:11 * abap/heaplimit................ 100000000                               *
30.05.2011 03:58:11 * zcsa/installed_languages...... DEFS                                    *
30.05.2011 03:58:11 * zcsa/system_language.......... E                                       *
30.05.2011 03:58:11 * ztta/max_memreq_MB............ 2047                                    *
30.05.2011 03:58:11 * ztta/roll_area................ 6500000                                 *
30.05.2011 03:58:11 * ztta/roll_extension........... 2000000000                              *
30.05.2011 03:58:11 *************************************************************************
30.05.2011 03:58:11 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
30.05.2011 05:02:53 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 171 records
30.05.2011 05:02:53 Result of customer enhancement: 171 records
30.05.2011 05:02:53 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 171 records
30.05.2011 05:02:53 Result of customer enhancement: 171 records
30.05.2011 05:02:53 Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
30.05.2011 05:02:53 IDOC: Info IDoc 2, IDoc No. 4667050, Duration 00:00:00
30.05.2011 05:02:53 IDoc: Start = 30.05.2011 03:58:11, End = 30.05.2011 03:58:11
30.05.2011 05:02:53 tRFC: Data Package = 1, TID = AC11082D38B44DE308DD028A, Duration = 00:00:00, ARFCSTATE = RECORDED
30.05.2011 05:02:53 tRFC: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
30.05.2011 05:02:53 Altogether, 0 records were filtered out through selection conditions
30.05.2011 05:02:53 Asynchronous transmission of info IDoc 3 in task 0003 (0 parallel tasks)
30.05.2011 05:02:53 IDOC: Info IDoc 3, IDoc No. 4667051, Duration 00:00:00
30.05.2011 05:02:53 IDoc: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
30.05.2011 05:02:53 Synchronized transmission of info IDoc 4 (0 parallel tasks)
30.05.2011 05:02:53 IDOC: Info IDoc 4, IDoc No. 4667052, Duration 00:00:00
30.05.2011 05:02:53 IDoc: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
30.05.2011 05:02:53 Job finished
Thanks for your help.
Yann

Parth Kulkarni,
following the note and the other thread, I've check the index 4 of the table COEP.
Here is what I got:
Index ID           COEP             - 4
Short text         MANDT/TIMESTMP/OBJNR, Index for Delta read method (CO-PA)
Last changed       SAP             04.01.2010
Status             Active          Saved
                   Does not exist in the database
DB index nme
    Not defined as DB index in the ABAP Dictionary
Is the fact that it doesn't exist in the database a problem ?
Is the fact that it is active is good enough ?
By the way thanks for your speedy reply !
Yann
Edited by: Yann GOFFIN on May 30, 2011 1:35 PM

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

Generic Extractor - Design

Hi All,
Ii have built a generic extractor as Master data, it has fields like MATRNR, WERKS, DESC and PRCTR. Now I want to load it to another IOB. Should I create an info object with attributes such as WERKS, PRCTR and DESC for a master data object ZMATNR?
My concern is can I use the existing IOB like 0PLANT, 0PROFIT_CTR as attribute to my Z-object ZMATNR, C18, no text, with ZDESC as another text item. Though it is not a typical master data situation (Lots of duplicate materials accross plants are possible). I don't want to create a DSO to avoid activateion time load issues.
Am I right? Any second openions?
Thanks,
Alex (Arthur Samson)

Thank for all.
I completed the design and it worked well.

Delta in generic extractor.

Hi Everyone,
I have created one of the generic extractor on a table and the other one on a view. While selecting the GENERIC DELTA, I let the numeric pointer selection checked.
Now, my question is will it allow me to do delta load in my cube using this extractor?
2nd question is how?
3rd question is if not then what is the change that I need to make so that it allows me to load the delta load. How this changes need to be made can you please explain step by step. thanks in advance.
My issue arose after loading the data when I went to change the InfoPackage to load the delta part, I realised in my InfoPackage I do not have the choice to load delta. How do I settle this. Actually this is an inventory cube where the data is loaded at the end of each month and now when I wanted to test it for today's month I realised that I do not have the choice to load delta for inventory load.
Please explain. Thank you once again in advance.

1. my question is will it allow me to do delta load in my cube using this extractor?
Yes... you build Generic Extractor with Delta based on Numeric Pointer. Material Documents is the Perfect Example for that (We can't Sales Document or Purchase Document for this).
2. 2nd question is how?
Simple enable Material Document Number Fileds for Numeric Pointer (Select Numeric Pointer... provide Mat. Document No. field i.e. MBLNR).
3rd question is if not then what is the change that I need to make so that it allows me to load the delta load. How this changes need to be made can you please explain step by step. thanks in advance.
you need to create Material Documents in SAP R/3. If you build your Extractor on MSEG Table. You need to create any Material Document which populates in MSEG.
I don't remember wht exactly option we will get in Infopackage for Numeric Pointer. To my knowledge, it should give Delta only in Update Tab page.
Hope this helps.
Nagesh Ganisetti.
Assign points if it helps.

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.

Building a Generic Extractor on the Material (MBEW) Valuation table

When I build an extractor based off the MBEW table does it matter whether the generic extractor is transactional i.e. any performance, conflict type issues? My thought is to build it as a Master data generic extractor? Thanks

Hi,
I hope, It Does not matter. We can created Master data source on MBEW.
If you want to define this DS as Transaction datasource and If MBEW has More than material and plant as primary key, then it is better to upload the data to ODS first to avoid duplicate records problems while uploading to master data infoobject.
With rgds,
Anil Kumar Sharma .P

Generic Delta issue..

hi experts,
i have created Datasource based on view which is based on EKPO and EKBE tables.
i have date fields BUDAT, CPUDT and CPUTM.
I have selected CPUDT as Delta Field.
select Calendar Day and Safety Interval Upper Limit as 1.
I have initialized yesterday, though the records are created and i can see the new records with today's date, in RSA7 i cannot see any records.
what is the issue in it, do i need to change delta field as CPUTM as it is time.
if yes then how can i set the Delta to capture the Delta Records?
regards
venuscm

Hi,
All three fields are from EKBE table, so kindly check whether there is any change in source system table EKBE, for these fileds for the new records created.
New record created will be updated in table EKPO and EKKO only.
Also make sure that delta field should be one of the extracted field in your generic extractor.
wish u all the best
Regards,
Vinod

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...

CRM Extractor issue 0CRM_SRV_IBASE_ATTR

Hello,
This is a production issue.
CRM system has the installed bases created and extracted to BW and reporting is fine.
When there is a change to these installed bases such as
* serial number is changed AND/OR
* material number is changed
the delta still brings in the complete hierarchy 'After Image' only.
Meaning old material number and old serial number still remains in the BW cube and hence reporting is faulty.
Example.
In Ibase 30, Material 500085 with Qty 1, is overwritten/changed in CRM as Material 600088. (This is seen in Activity log in CRM correctly).
The extractor sends whole Ibase content as one row for Component header and one row for Material 600088 details(as seen in PSA).
However material 500085 row is still valid in BW as the validto is 12/31/9999.
So BW reports qty as 2 instead of 1.
I see the extractor delta process is AIM.
So this should have been an ongoing issue. However user complained only now.
How to solve this problem. Since this is a generic extractor others would also face this situation i would think.
Please advise.
Thanks

Hi Meenakshi,
As i understand you had two issues 1. with the new material 2.with qty.I hope the modified record is not coming to DSO.Some part of the code in the start routine is blocking the record.Please analyze the code in start routine.And check the change log table for this record for any clue how it is not being overwritten.
Regards,
Rambabu

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

Generic extractors with delta

hi all,
can any one please provide any thing on generic extractors particular to delta (time-stamp)
VRKR

Hi,
please search the forums. This question has been asked already a lot of times. Additionally you might check my business card --> there is a link to a weblog related to that issue.
Siggi

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.

Generic Extractor Issue

Similar Messages

Maybe you are looking for