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

Similar Messages

Generic Extractor using Function module with Complex Interface

Hi,
Has anyone created Generic extractor using Function module with Complex Interface?
What is the difference between Complex and Simple interface in Function module?
Pls explain.
Thanks,
Gopal

Hi,
Go through this link.....
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
GTR

F1 & F2 interfaces in generic extractors using function module

Hi experts,
I created generic extractor using copy of function module RSAX_BIW_GET_DATA_SIMPLE with Delta capability. In ROOSOURCE, DataSource Extraction Method showing as F2. I checked In some blogs that we need to change the DataSource Extraction Method in ROOSOURCE table from F2 to F1 using test program . here my concern is:
1) What is meant by complete(F1) and simple(F2) interface, where our generic DataSource differs with this interface?
2) Do we need to change it from F2 to F1 in my case?
Many thanks,
Zakir.

Here is the difference between an F1 interface and a F2 interface (more importing parameters for the F1 interface):
Interface F1 :
FUNCTION BUPA_CCARD_EXTRACT_BW.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_CHABASNM) TYPE SBIWA_S_INTERFACE-CHABASNM 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_S_TIMEINT) TYPE SBIWA_S_TIMEINT OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE RSONLYREAD OPTIONAL
*" TABLES
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*"      E_T_BUS0CC_BW STRUCTURE BUS0CC_BW OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Interface F2 :
FUNCTION RSVL_CHARNO_GET_MASTER_DATA.
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE
*"                             OPTIONAL
*"             VALUE(I_INITFLAG) LIKE RSAAPI_IF-INITFLAG OPTIONAL
*"             VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE
*"                             OPTIONAL
*"             VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR OPTIONAL
*"       TABLES
*"              I_T_SELECT STRUCTURE RSSELECT OPTIONAL
*"              I_T_FIELDS STRUCTURE RSFIELDSEL OPTIONAL
*"              E_T_DATA STRUCTURE ROVERCHAR OPTIONAL
*"       EXCEPTIONS
*"              NO_MORE_DATA
*"              ERROR_PASSED_TO_MESS_HANDLER
The function module you copy (RSAX_BIW_GET_DATA_SIMPLE) seems actually more compatible with the F1 interface than the F2 (due to the I_REQUNR parameter).
So yes, I think you should switch your interface type to F1.
Regards,
Fred

Generic extractor using function module

Hi all,
We have created a generic extractor using a function module.
We created a new custom function copied from 'RSAX_BIW_GET_DATA_SIMPLE'. has been set as the delta date for this data source in transaction RSO2.The function module is a custom version of the FM RSAR_BIW_GET_DATA_SIMPLE.

Hi Anitha,
Please send your email id...
I will send the documnent to you.
My mail id [email protected]

Create a generic extractor using Function module, what steps must I follow

Hello gurus team
I need to Create a generic extractor using Function module, what steps must I follow?
Just I have a function module not estructures or something, only the program.... and I have intented to do it in rso2 using the fm option, but give an error... somebody can helpme???
BR

Hi,
Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
http://help.sap.com/saphelp_nw04/helpdata/en/86/1c8c3e94243446e10000000a114084/frameset.htm
Thanks,
JituK

Delta with Generic Extractor using function module

Hi,
I have created an extractor using function module and it work fine (mode FULL)
It's an extractor based on the FM RSAX_BIW_GET_DATA_SIMPLE.
In TCODE RSO2, I have specified a delta field (AEDAT).
In table ROOSOURCE, this extractor is defined by :
DELTA = AIE
EXMETHOD = F1
When I extract data in Init mode, there is no problem. But delta don't extract any entries.
When I trace with TCODE ST01, in Init mode the function module is executed but in delta mode, there is no trace of any use of this function module.
I don't know how to do to make this extractor work fine in delta mode.

Hi Pascal,
The same function module i have used and succesffuly doing delta using it. So it works for both full & delta.
How ur testing it and where are you testing it for delta.
Do the delta testing through BI end. Set the
As u have already set the delta field., now Follow below steps:
1. First set the safety interval upper limit to -1, so that it will extract the delta data of 1 day back records also.
2. Please make sure wether the delta records are available or not in r/3, if there is no records to be fetched in for delta then u will not be able to track out wether delta is working or not.
3. Now do the init from BI end first. Delta initialization without data transfer. - It will give u green status with 1 dummmy record.
4. Now do the delta. It will extract the delta records.
Before that make sure that if any selection your giving in Infopackage should be met out by these delta records.
Thanks
Dipika

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 is not reading delta

Hi !
I have a generic extractor with delta queue, for a Z view.
The delta is on 'ZLOAD_DATE' field / calendar day /safety interval upper limit = 1 / new status for changed records
In BI the init with data is ok.
In ECC the delta queue (RSA7) show as actual status: 03 June 2010
then, I add 3 new records
ZMAT    ZLOAD_DATE
x            01 June 2010
x            02 June 2010
x            03 June 2010
But when I run again the delta load in BI, dont load any records.. (0 records readed)
> What is wrong?
Thanks in advance!

Hi Prem
The new record were created after the init (the same day), but specify manually in the ZLOAD_DATE several dates (diferent from the real load date, today)
1 - If I load records today and after run a delta, can I see they in BI or I need wait until tomorrow?
2 - if the upper limit is regarding the actual date, which is the meaning of specify a delta key field?
3 - if I want a delta with the same behaivour than standard delta, do I need add the field timestamp to the table, and change the extractor?
Thanks for your support!

Using Transformations with Delta enabled Datasources

Hi,
I have a delta enables datasource which uses incremental update to my infoCube.
In order to populate some fields in the cube I used a transformation routine for a couple of these fields to do some lookups from some tables.
The problem that I am encountering is that when the delta update runs its only updates the directly assigned fields it does not also update the routine delivered fields.
Is there a way to get this to work or is it impossible?
Thanks

HI,
The routines work fine for full load as the data is replaced with new data each time.
What I need to happen is I am using a SAP standard content datasource with delta enabled on the datasource and when loading from datasource to Cube all the 0 fields are updating correctly but my Z fields which i update with routines do not seem to be replaced.
Please advise of anyway to get this to work
Thanks

Custom Extractor using FM for Delta Upload

Hi,
I created a Custom Extractor using FM for Full Upload. The requirement now is that it should be able to handle Delta also.
I used the standard FM RSAX_BIW_GET_DATA_SIMPLE to create my Z FM.
Please suggest me the changes I have to make in this to be able to upload Delta also.
Thanks
Nageswara

Hi Mahesh,
You can selectively load from BI side (through Infopackage) and for that you should have those selection field defined as ranges in your FM.
As per my genius friend Sidharth Gupta:
FM RSAX_BIW_GET_DATA_SIMPLE is a funct. Mod having a simple interface in which I_UPDMODE is not used. Actually FM RSAX_BIW_GET_DATA_SIMPLE is used for a full update and uses an F2 extraction method. However through ABAP we can try to make it delta capable like below.
*Declare
DATA I_UPDMODE.
Now to capture delta on AUDAT
       I_UPDMODE = u2018 u2018.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'AUDAT'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_AUDAT.
             I_UPDMODE = u2018 D u2019.
            APPEND L_R_AUDAT.
          ENDLOOP.
This code works however is not flexible as you do not use a CASE stmt on I_UPDMODE.
CASE stmt gives more flexibility which is used in FM RSAX_BIW_GET_DATA.
FM RSAX_BIW_GET_DATA is a funct. Mod having a complete interface in which I_UPDMODE is passed to funct mod during its call.FM RSAX_BIW_GET_DATA can be used for all update types and uses an F1 extraction method. However after writing the funct mod the default extraction method is F2 in table ROOSOURCE which needs to b changed to F1 for ur mod to work. This change from F2 to F1 can be done via test abap code.
Part two of that Article is yet to be published so wait for sometime or follow above mentioned approach.
Hope it helps.
Regards,
Ashish

Using Reason with Pro Logic

Is it possible to hook up Reason and Logic together ? Is it possible to mix audio out of reason using Logic ?

Here's a paste from an old post of mine:
There are two ways to do this (well, more, but I'll tell you 2)
1 (Easy Way):
Restart Mac (Just to be sure things are sorted, not everytime)
Launch Logic
Launch Reason
Arrange Window
Choose a Channel> Pan Left
Go to the Middle section of the Parameters on the Left
With the Channel pop up menu, select Rewire> RWMix L
Repeat for the Right and away you go.
2 (More Advanced)
Environment Window
In the Middle section of the parameters on the Left select Create
Name it Rewire
Under that windows "New" pull down (Top Left), pull down to Audio Object
In the "Channel" pop up (Left, bottom section) select>Rewire (Left, right, 3,4... What ever you want.
Double Click the Audio Object to expand it
Pan Left or right, or whatever you need.
Rename if you wish
Do the same for the other stereo sideNow's the fun part. Assign these stereo pairs to a bus (above the fader, the default is "Out 1-2")
Go to the Mixer window
Double click the Bus you assigned, this puts it in the arrange window
Arrange window
Name the Bus "Rewire" or "ReDrum" or something great like that.
Now you can use it like a stereo pair (which I wish Logic had) for automation and effects and such.

Using Kerberos with Web logic Server

Hi all,
I am working with Kerberos software for the first time. I have downloaded and installed the 2.6.5 version on my windows XP machine. I do not know how to configure it to work with Weblogic Server. I tried following the steps mentioned in the following link but got nowhere :(
http://fusionsecurity.blogspot.com/2010/02/kerberos-and-weblogic-server-on-windows.html
Please suggest me some links or provide some inputs as to how to get started.

You can also go though this link
http://weblogic-wonders.com/weblogic/2009/11/15/configuring-kerberos-with-weblogic-server/

Ranges in Generic Extractor using FM

Hello,
         I was trying to create a copy of RSAX_BIW_GET_DATA_SIMPLE and use it for extracting data to BI.
      Can anyone through some light on Ranges used in this FM.
What is the purpose of it.also can any one explain S_S_IF-t_Select and L_S_SELECT.
   Appropriate answers will be Rewarded.
Regards,
VJ

Hi,
Range is a statement which has the same structure as a select option (sign, option, low and high). The only difference is like you have to fill these ranges internally (not available as selection for users).
.E_T_DATA takes the form of the structure that you assign to E_T_DATA table in the Table parameters of the FM. If you assign the structure Z_bw_test_struct to E_T_DATA, it means that the return of the DS is in the format of this structure. This basically determines the output of the FM DS. I_T_SELECT is a structure which gets the imput selections for the DS. If you have 3 fields for selection in the DS, this structure gets the values for those 3 fields that you enter either in info package or RSA3. I_T_FIELDS is the list of fields that are available in the DS/TS.
Thanks...
Shambhu

How to do Delta upload using Generic Extractor built on Function Module?

Hello Guys,
I have never created a Generic Extractor using a Function Module. I wanted to know how can we support Delta mechanism if we create Generic extractor using Function Module.
Regards,
Abhishek

Hi Abishek,
Please check the standard Function Module RSAX_BIW_GET_DATA for your delta mechnism.
Hope it will help you.
Thanks,
Chandra

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

Similar Messages

Maybe you are looking for