Extraction Using DBCONNECT

Hello All,
We were trying to extract data from ORACLE sysetm. Source system and bw system have oracle database.
We have successfully created source system at BW side and is able to connect to oracle source system.
But when we try to see the tables (using select database tables )system says "There is no table in database system DBEXT00001" .
What could be reason for this error message ??
Thanks
Regards
Nimesh

Hello AHP,
Actually we have one system on which BW development is installed.
For learning purpose we are trying to connect BW Dev oracle database as external database system.
For that we have assigned the table space BWPSABWD640 to the user , that we are using for the connection.
For current set up as explained above is it possible to extract data from BW Dev database to itself.
Regards
Nimesh

Similar Messages

Extracting data using DBConnect/UDConnect

Hi all,
I need to connect an SAP BW system to an external database (MS SQL Server). The BW server runs on Sun Solaris.
Could anyone kindly clarify whethere to use DBConnect or UDConnect for this purpose?
When I tried to create a DBConnect connection, it threw an error "No shared library found for the database with ID <logical name of source system>". Will this be solved by installing the DBSL? If yes, could you kindly give me the exact location in SAP service marketplace where I can find it?
Or, is it that since the OS is not Windows based, only UDConnect can be used? If so, could you give the step by step processes to use UDConnect?
Best Regards,
Sarath

Hi ,
Plz check the below link. ( Configuring UD Connection and Connecting to BI)
www.bi-expertonline.com/downloads/Schroeder0604.doc
Regards
Ram.

What r the steps that involve while v r using DBCONNECT AND UDCONNEC

Hi All,
What r the steps that involve while v r using DBCONNECT AND UDCONNECT AND IN WHICH DIFFERENT SCENARIOS V USE THEM.
REGARDS
KK

Hi,
To Configure UD Connect on the J2EE Server for JDBC Access to External Databases;
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff
To create Driver on JDBC side
http://help.sap.com/saphelp_nw70/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm
Configuring the BI Java Connectors
http://help.sap.com/saphelp_nw70/helpdata/en/43/e35b3315bb2d57e10000000a422035/frameset.htm
Then to extract data use this...
Before you can transfer data from UD Connect sources into BI, you have to generate the metadata (the information about the source object and source object elements) in BI, in the form of a DataSource with a function module for extraction.
If your dataflow is modeled with objects based on the old concept (InfoSource 3.x, transfer rules 3.x, update rules 3.x), you can generate a DataSource 3.x for transferring data into BI from a database source system.
Prerequisites
You have modeled the InfoObjects that you want to use in the InfoSource and the data target or InfoProvider according to the UD Connect source object elements.
Note the following background information:
Using InfoObjects with UD Connect
Data Types and Their Conversion
Using the SAP Namespace for Generated Objects
Procedure
You are in the Modeling InfoSource tree of the Administrator Workbench. First create in InfoSource and activate the communication structure. Then generate the generic DataSource using the wizard in the InfoSource maintenance.
1. Choose InfoSources ® Your Application Component ® Context Menu (right mouse click) ® Create InfoSource.
2. Select the type of the InfoSource.
3. Under InfoSource, enter the technical name of the InfoSource, and assign a description and choose Continue.
The system creates an InfoSource and shows it in the InfoSource tree under your application components.
4. In the context menu of the InfoSource, choose Change .
The communication structure maintenance screen appears.
5. Using the previously modeled InfoObjects, create the communication structure (see Communication Structure).
6. Save and activate your communication structure
7. In the dialog box that follows you will be asked whether you wish to activate the dependent transfer program. Choose No.
8. In the InfoSource menu, choose Extras ® Create BW DataSource with UD Connect.
You get to the dialog box where you can assign a UD Connect source object to a DataSource and then generate the DataSource with the extractor. The fields for the DataSource are already being displayed in the table on the left side of the screen. The fields have the same name as the InfoObjects that you have used in the InfoSource.
9. Select the RFC Destination for the J2EE Engine.
Make sure that the local server is running. If the local server is running and you cannot open the table for RFC destinations, start the local server again.
10. Choose the UD Connect Source in which the data that you wish to access is located.
All available sources that are connected to the J2EE Engine are provided for selection in the input help. n instances are available per adapter.
11. Select the UD Connect Source Object.
All available source objects that are available in the selected UD Connect source are provided for selection in the input help. Source objects can be multi-dimensional storage or relational objects.
The system generates the name of the DataSource in the namespace 6B.
The DataSource is then replicated in BI.
The myself system is assigned to the InfoSource as source system as well as the DataSource.
The system generates a proposal for the transfer rules.
Since the DDIC structure and the function module are located in the SAP namespace, the following entries can be requested during generation:
Developer and object key or
Developer key or
Object key and
Transport request
If you do not make the requested entries, the generated infrastructure is not usable.
14. Change or complete the transfer rules as needed. For example, if a source object element is not assigned to a unit InfoObject, you can determine a constant for the unit, such as EUR for 0LOC_CURRCY (local currency).
15. Save and activate your transfer rules.
Recognizing Manual Entries
You can enter and change the RFC Destination, UD Connect Source and UD Connect Source Object manually. In order to validate these entries and the ones that depend on them, choose Recognize Manual Entries. For example, if you change the selected RFC destination, all of the field contents (US Connect Source, UD Connect Source Object, list of the source object elements) are invalid. If you choose Recognize Manual Entries, the dependent field contents are initialized and have to be maintained again.
Result
You have created the InfoSource and DataSource for data transfer with UD Connect. In the DataSource overview for the myself system, you can display the DataSource under the application components Non-Assigned Nodes.
When modeling InfoObjects in BI, note that the InfoObjects have to correspond to the source object elements with regard to the type description and length description. For more information about data type compatibility, see Data Types and Their Conversion.
The following restrictions apply when using InfoObjects:
Alpha conversion is not supported
The use of conversion routines is not supported
Upper and lower case must be enabled
These InfoObject settings are checked when they are generated.
Based on the large number of possible UD Connect sources, the most diverse data types are possible in the output system. For this reason, a compatibility check is made at the time of generation of the UD Connect DataSource that is based on the type information supplied by the source systems. This attempts to decrease the probability of errors during the extraction process.
(Refernce:SAP Notes)
Hope this helps,
regards
CSM Reddy

Caller 09 Error while Extraction using DB connect

Hi all,
I am working on BI7. I had created the process chain while its running it gives "Caller 09" Error and Error Message consist of
" UnKnown Error while uploading the Data from the DB table
Error in Source System." Now what i Hav to do, V r extracting the data using DBconnect. what r the steps i need to follow
Help will b appreciated
Regards
Priya

Hi,
It may be a Time stamp issue with DS.
Try this.
Replicate the data source in BW.
Run the program RS_TRANSTRU_ACTIVATE_ALL for the source system.
Then retrigger the load.
Hope this helps.
Refer
Re: tickets
Also Go to SM37 in source system and see the job log.
In BW > RSMO > Details see where it failed.
Let us know.
thanks,
JituK

Code For Delta Extraction Using Function Module

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Dear KJ,
Thank for your response. I saw the code that you sent, you have used some ztables like ZSC_DELTA_IP, ZSC_SAFETY_DELTA, ZSC_SET_EXT_TIME
What are the fields that you have created in these tables , what is use of these tables, can you send the fields that you have used in these tables.
Thanks & Regards,
SGK

IS-U enhancing transaction FPBW (open items extraction using table DFKKOPBW

Has anybody experiances with IS-U Accounts Receivable & payable - 'Open Items' extraction using transaction FPBW
(which fill the table DFKKOPBW).
1. I need to fill an custom included structure in this table (DFKKOPBW) and I am searching for the correct time (for performance reasons) & place in the (SAP) source (in the program flow) to do this.
2. Anybody any clues on Custum/user exits in this part?
See also function group FKKOPBW.
Jos Reithofer

Try this code that can search a user exit in a transaction. I got it from previous post in this forum.
*& Report Y_SEARCH_USEREXIT                                           *
REPORT y_search_userexit LINE-SIZE 140 NO STANDARD PAGE HEADING.
CONSTANTS
*CONSTANTS: c_user_exit(22) TYPE c VALUE 'CALL CUSTOMER-FUNCTION',
constants: c_badi(30) type c value 'CALL METHOD CL_EXITHANDLER=>',
           c_funcao_1(13) TYPE c VALUE 'CALLFUNCTION''',
           c_funcao_2(13) TYPE c VALUE 'CALL FUNCTION',
           c_include(07) TYPE c VALUE 'INCLUDE',
           c_submit(06) TYPE c VALUE 'SUBMIT',
           c_comentario TYPE c VALUE '*',
           c_ponto TYPE c VALUE '.',
           c_aspa TYPE c VALUE '''',
           c_x TYPE c VALUE 'X'.
TABELAS INTERNAS
DATA: BEGIN OF ti_programa OCCURS 0,
codigo_fonte(200) type c, " LIKE rssource-line,
END OF ti_programa.
DATA: BEGIN OF ti_includes OCCURS 0,
nome LIKE sy-repid,
nivel(2) TYPE n,
END OF ti_includes.
DATA: BEGIN OF ti_user_exit OCCURS 0,
programa LIKE sy-repid,
linha(10) TYPE n,
codigo_fonte LIKE rssource-line,
nivel(2) TYPE n,
END OF ti_user_exit.
VARIÁVEIS GLOBAIS
DATA: vg_caracter TYPE c,
vg_palavra(50) TYPE c,
vg_inicial LIKE sy-index,
vg_conta_aspa TYPE n,
vg_pname LIKE tfdir-pname,
vg_texto(50) TYPE c,
vg_contador LIKE sy-tfill,
vg_nivel(2) TYPE n,
vg_ini_contagem TYPE c, " INDICA QUE DEVE SER INICIADA A CONTAGEM
vg_conta_espaco TYPE n. " TOTAL DE ESPAÇOS ( MÁXIMO 2 )
PARAMETERS
*- DADOS OBRIGATÓRIOS.
SELECTION-SCREEN BEGIN OF BLOCK bl01 WITH FRAME TITLE tl_001 .
selection-screen begin of line.
selection-screen comment 1(25) tl_003.
PARAMETERS: p_prog LIKE sy-repid.
selection-screen end of line.
selection-screen begin of line.
selection-screen comment 1(25) tl_004.
parameters: p_tcode LIKE sy-tcode.
selection-screen end of line.
selection-screen begin of line.
selection-screen comment 1(25) tl_009.
parameters: p_exit(30) TYPE c default 'CALL CUSTOMER-FUNCTION'.
selection-screen end of line.
SELECTION-SCREEN END OF BLOCK bl01.
*- DADOS OPCIONAIS.
SELECTION-SCREEN BEGIN OF BLOCK bl02 WITH FRAME TITLE tl_002.
selection-screen begin of line.
PARAMETERS: p_incl TYPE c AS CHECKBOX.
selection-screen comment 4(25) tl_005.
selection-screen end of line.
selection-screen begin of line.
parameters: p_func TYPE c AS CHECKBOX.
selection-screen comment 4(25) tl_006.
selection-screen end of line.
selection-screen begin of line.
parameters: p_submit TYPE c AS CHECKBOX.
selection-screen comment 4(25) tl_007.
selection-screen end of line.
selection-screen begin of line.
selection-screen comment 1(25) tl_008.
parameters: p_nivel(2) TYPE n.
selection-screen end of line.
SELECTION-SCREEN END OF BLOCK bl02.
initialization.
tl_001 = 'Program Selection'.
tl_002 = 'Search Depth'.
tl_003 = 'Program Name'.
tl_004 = 'Transaction Code'.
tl_005 = 'Process INCLUDEs'.
tl_006 = 'Process FUNCTION MODULEs'.
tl_007 = 'Process SUBMITs'.
tl_008 = 'Depth level'.
tl_009 = 'Search string'.
INÍCIO
START-OF-SELECTION.
*- CONSISTÊNCIAS DOS PARÂMETROS.
PERFORM consisti_parametros.
*- INICIALIZA TABELA.
PERFORM inicializa_tabela.
*- VERIFICA SE NO PROGRAMA EXISTE ALGUM INCLUDE,FUNÇÃO OU SUBMIT.
PERFORM verifica_include_funcao_submit.
*- ANALISA OS INCLUDES E PROCURA POR USER EXIT.
PERFORM procura_user_exit.
*- EXIBE TODAS USER EXIT ENCONTRADAS.
PERFORM exibe_user_exit.
FIM
END-OF-SELECTION.
*& Form PROCURA_USER_EXIT
text
--> p1 text
<-- p2 text
FORM procura_user_exit.
*- VERIFICA SE NOS INCLUDES SELECIONADOS EXISTEM USER EXITS.
LOOP AT ti_includes.
*- ESVAZIA TABELA INTERNA.
    REFRESH ti_programa.
*- REALIZA LEITURA DO INCLUDE ARMAZENANDO-O EM TABELA INTERNA
    READ REPORT ti_includes-nome INTO ti_programa.
    LOOP AT ti_programa.
*- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
      SEARCH ti_programa-codigo_fonte FOR p_exit.
*- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
      IF sy-subrc EQ 0
      AND ti_programa-codigo_fonte+0(1) NE c_comentario.
        CLEAR ti_user_exit.
*- REMOVE ESPAÇOS NO INÍCIO DA STRING.
        SHIFT ti_programa-codigo_fonte LEFT DELETING LEADING space.
        MOVE: ti_includes-nome TO ti_user_exit-programa,
        sy-tabix TO ti_user_exit-linha,
        ti_programa-codigo_fonte TO ti_user_exit-codigo_fonte,
        ti_includes-nivel TO ti_user_exit-nivel.
        APPEND ti_user_exit.
      ENDIF.
    ENDLOOP.
ENDLOOP.
ENDFORM. " PROCURA_USER_EXIT
*& Form EXIBE_USER_EXIT
text
--> p1 text
<-- p2 text
FORM exibe_user_exit.
PERFORM cabecalho.
PERFORM user_exit_nao_encontrada.
PERFORM lista_user_exit_encontrada.
PERFORM rodape.
ENDFORM. " EXIBE_USER_EXIT
*& Form PROCURA_INCLUDE
text
--> p1 text
<-- p2 text
FORM procura_include.
CLEAR vg_palavra.
*- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
SEARCH ti_programa-codigo_fonte FOR c_include.
*- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
IF sy-subrc EQ 0
AND ti_programa-codigo_fonte+0(1) NE c_comentario.
*- VERIFICA TODOS OS 72
    DO 72 TIMES.
      vg_inicial = sy-index - 1.
      MOVE ti_programa-codigo_fonte+vg_inicial(1) TO vg_caracter.
      IF NOT vg_caracter IS INITIAL.
*- VERIFICA SE NÃO É FIM DO COMANDO.
        IF vg_caracter EQ c_ponto.
          EXIT.
        ENDIF.
*- MONTA PALAVRA.
        CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
*- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
        TRANSLATE vg_palavra TO UPPER CASE.
*- SE ENCONTROU ALGUM INCLUDE
        IF vg_palavra EQ c_include.
          CLEAR vg_palavra.
        ENDIF.
      ENDIF.
    ENDDO.
*- SALVA NOME DO INCLUDE P
    READ TABLE ti_includes WITH KEY nome = vg_palavra.
    IF NOT sy-subrc IS INITIAL.
      IF vg_nivel LE p_nivel.
        MOVE: vg_palavra TO ti_includes-nome,
        vg_nivel TO ti_includes-nivel.
        APPEND ti_includes.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM. " PROCURA_INCLUDE
*& Form PROCURA_FUNCAO
text
--> p1 text
<-- p2 text
FORM procura_funcao.
CLEAR: vg_conta_aspa,
vg_palavra.
*- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
SEARCH ti_programa-codigo_fonte FOR c_funcao_2.
*- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
IF sy-subrc EQ 0
AND ti_programa-codigo_fonte+0(1) NE c_comentario.
*- VERIFICA TODOS OS 72
    DO 72 TIMES.
      vg_inicial = sy-index - 1.
      MOVE ti_programa-codigo_fonte+vg_inicial(1)
      TO vg_caracter.
      IF NOT vg_caracter IS INITIAL.
*- VERIFICA SE NÃO É FIM DO COMANDO.
        IF vg_caracter EQ c_aspa.
          ADD 1 TO vg_conta_aspa.
          IF vg_conta_aspa EQ 2.
            EXIT.
          ENDIF.
        ENDIF.
*- MONTA PALAVRA.
        CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
*- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
        TRANSLATE vg_palavra TO UPPER CASE.
*- SE ENCONTROU ALGUM INCLUDE
        IF vg_palavra EQ c_funcao_1.
          CLEAR vg_palavra.
        ENDIF.
      ENDIF.
    ENDDO.
*- PESQUISA NOME DA FUNÇÃO PARA FUTURA PESQUISA POR USER EXIT.
    CLEAR vg_pname.
    SELECT SINGLE pname
    INTO vg_pname
    FROM tfdir
    WHERE funcname EQ vg_palavra.
    IF sy-subrc EQ 0.
      READ TABLE ti_includes WITH KEY nome = vg_pname.
      IF NOT sy-subrc IS INITIAL.
        IF vg_nivel LE p_nivel.
          MOVE: vg_pname TO ti_includes-nome,
          vg_nivel TO ti_includes-nivel.
          APPEND ti_includes.
        ENDIF.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM. " PROCURA_FUNCAO
*& Form VERIFICA_INCLUDE_FUNCAO_SUBMIT
text
--> p1 text
<-- p2 text
FORM verifica_include_funcao_submit.
LOOP AT ti_includes.
    ADD 1 TO vg_contador.
    DESCRIBE TABLE ti_includes.
    PERFORM evitar_time_out USING sy-tfill.
    MOVE ti_includes-nivel TO vg_nivel.
    ADD 1 TO vg_nivel.
*- ESVAZIA TABELA INTERNA.
    REFRESH ti_programa.
    READ REPORT ti_includes-nome INTO ti_programa.
    LOOP AT ti_programa.
*- PROCURA POR INCLUDES.
      IF p_incl EQ c_x.
        PERFORM procura_include.
      ENDIF.
*- PROCURA POR FUNÇÃO.
      IF p_func EQ c_x.
        PERFORM procura_funcao.
      ENDIF.
*- PROCURA POR SUBMIT.
      IF p_submit EQ c_x.
        PERFORM procura_submit.
      ENDIF.
    ENDLOOP.
ENDLOOP.
ENDFORM. " VERIFICA_INCLUDE_FUNCAO_SUBMIT
*& Form EVITAR_TIME_OUT
text
-->P_SY_TFILL text
-->P_SY_SUBRC text
FORM evitar_time_out USING p_sy_tfill.
DATA: vl_total(10) TYPE n,
vl_atual(10) TYPE n.
MOVE: p_sy_tfill TO vl_total,
vg_contador TO vl_atual.
CONCATENATE 'Total:' vl_total '-' 'Atual:' vl_atual
INTO vg_texto
SEPARATED BY space.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
    EXPORTING
      text = vg_texto.
ENDFORM. " EVITAR_TIME_OUT
*& Form PROCURA_SUBMIT
text
--> p1 text
<-- p2 text
FORM procura_submit.
CLEAR: vg_conta_espaco, vg_palavra, vg_ini_contagem.
*- VERIFICA SE NA LINHA DO PROGRAMA EXISTE ALGUM INCLUDE.
SEARCH ti_programa-codigo_fonte FOR c_submit.
*- SE ENCONTROU INCLUDE E SE A LINHA NÃO ESTÁ COMENTADA...
IF sy-subrc EQ 0
AND ti_programa-codigo_fonte+0(1) NE c_comentario.
*- VERIFICA TODOS OS 7
    DO 72 TIMES.
      vg_inicial = sy-index - 1.
      MOVE ti_programa-codigo_fonte+vg_inicial(1) TO vg_caracter.
      IF vg_ini_contagem EQ c_x AND vg_caracter IS INITIAL.
        ADD 1 TO vg_conta_espaco.
      ENDIF.
      IF NOT vg_caracter IS INITIAL.
        MOVE c_x TO vg_ini_contagem.
        IF vg_caracter EQ c_ponto.
          EXIT.
        ENDIF.
*- MONTA PALAVRA.
        IF vg_conta_espaco LT 2.
          CONCATENATE vg_palavra vg_caracter INTO vg_palavra.
*- CONVERTE PARA MAÍUSCULA PARA FUTURA COMPARAÇÃO.
          TRANSLATE vg_palavra TO UPPER CASE.
*- SE ENCONTROU ALGUM INCLUDE
          IF vg_palavra EQ c_submit.
            CLEAR vg_palavra.
          ENDIF.
        ELSE.
          EXIT.
        ENDIF.
      ENDIF.
    ENDDO.
*- PESQUISA NOME DA FUNÇÃO
    READ TABLE ti_includes WITH KEY nome = vg_palavra.
    IF NOT sy-subrc IS INITIAL.
      IF vg_nivel LE p_nivel.
        MOVE: vg_palavra TO ti_includes-nome,
        vg_nivel TO ti_includes-nivel.
        APPEND ti_includes.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM. " PROCURA_SUBMIT
*& Form CONSISTI_PARAMETROS
text
--> p1 text
<-- p2 text
FORM consisti_parametros.
IF p_nivel IS INITIAL.
    MOVE 1 TO p_nivel.
ENDIF.
IF p_prog IS INITIAL AND p_tcode IS INITIAL.
*- NOME DO PROGRAMA E NOM
*- DEVE SER INFORMADO.
    MESSAGE ID 'ZF' TYPE 'I' NUMBER '000' WITH text-003.
    STOP.
ENDIF.
IF NOT p_prog IS INITIAL AND NOT p_tcode IS INITIAL.
*- SOLICITA AO U
    MESSAGE ID 'ZF' TYPE 'I' NUMBER '000' WITH text-004.
    STOP.
ENDIF.
ENDFORM. " CONSISTI_PARAMETROS
*& Form INICIALIZA_TABELA
text
--> p1 text
<-- p2 text
FORM inicializa_tabela.
DATA vl_pgmna LIKE tstc-pgmna.
REFRESH ti_includes.
IF NOT p_prog IS INITIAL.
    MOVE: p_prog TO ti_includes-nome,
    '0' TO ti_includes-nivel.
    APPEND ti_includes.
ELSEIF NOT p_tcode IS INITIAL.
    SELECT SINGLE pgmna
    FROM tstc
    INTO vl_pgmna
    WHERE tcode EQ p_tcode.
    IF sy-subrc EQ 0.
      MOVE: vl_pgmna TO ti_includes-nome,
      '0' TO ti_includes-nivel.
      APPEND ti_includes.
    ENDIF.
ENDIF.
ENDFORM. " INICIALIZA_TABELA
*& Form CABECALHO
text
--> p1 text
<-- p2 text
FORM cabecalho.
DATA vl_complemento(50) TYPE c.
IF p_tcode IS INITIAL.
    CONCATENATE '(Program)' p_prog
    into vl_complemento
    SEPARATED BY space.
ELSE.
    CONCATENATE '(Transaction)' p_tcode
    INTO vl_complemento
    SEPARATED BY space.
ENDIF.
FORMAT COLOR COL_KEY.
WRITE: /001 sy-uline,
/001 sy-vline,
040 'User Exits in a Program',
vl_complemento,
140 sy-vline,
/001 sy-uline.
WRITE: /001 sy-vline,
003 'Program Name',
044 sy-vline,
046 'Level',
052 sy-vline,
054 'Lineno',
065 sy-vline,
067 'UserExit',
140 sy-vline,
/001 sy-uline.
ENDFORM. " CABECALHO
*& Form USER_EXIT_NAO_ENCONTRADA
text
--> p1 text
<-- p2 text
FORM user_exit_nao_encontrada.
DESCRIBE TABLE ti_user_exit.
CHECK sy-tfill IS INITIAL.
FORMAT COLOR COL_NORMAL INTENSIFIED ON.
WRITE: /003 'Userexit does not exist',
139 ' '.
FORMAT RESET.
ENDFORM. " USER_EXIT_NAO_ENCONTRADA
*& Form LISTA_USER_EXIT_ENCONTRADA
text
--> p1 text
<-- p2 text
FORM lista_user_exit_encontrada.
DATA vl_cor TYPE c.
LOOP AT ti_user_exit.
    IF vl_cor EQ c_x.
      CLEAR vl_cor.
    ELSE.
      MOVE c_x TO vl_cor.
    ENDIF.
*- AJUSTA COR NA TELA.
    IF vl_cor EQ c_x.
      FORMAT COLOR COL_NORMAL INTENSIFIED ON.
    ELSE.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    ENDIF.
*- INÍCIO DA IMPRESSÃO.
    WRITE: /003 ti_user_exit-programa,
    046 ti_user_exit-nivel,
    054 ti_user_exit-linha,
    067 ti_user_exit-codigo_fonte,
    139 ' '.
ENDLOOP.
ENDFORM. " LISTA_USER_EXIT_ENCONTRADA
*& Form RODAPE
text
--> p1 text
<-- p2 text
FORM rodape.
DESCRIBE TABLE ti_includes.
FORMAT COLOR COL_TOTAL.
WRITE: /001 sy-uline,
/001 sy-vline,
003 'Total include searched:', sy-tfill,
' - with level:', p_nivel,
140 sy-vline,
/001 sy-uline.
ENDFORM. " RODAPE

Generic Extraction - Using Function Modules

Hi Friends,
Can you pl let me know the step by step process for creating generic extraction using function module?
Thanks in Advance.
Regards,
Ari.
Please search the forum before posting a thread
Edited by: Pravender on Aug 5, 2010 7:31 PM

Hi,
Plz find this doc.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33.
And go this link...
http://www.sdn.sap.com/irj/scn/advancedsearch?query=genericextractionwithfunctionmadule
Regards.....KP
Edited by: kundan.sap on Aug 5, 2010 4:35 PM

Generic extraction using table

Hello friends,
We have three methods in Generic extraction, as we know.
1. Using view/Table
2. Using FM
3. Using Infoset Query
I know pretty well the extraction using View, but when do we use "Table"?
Is there a specific method to perform generic extraction using TABLE?
Please clarify

Thanks for the replies.
In case of a generic extraction with view, i've followed the below procedure.
1. RSO2.
2.create a generic datasource by giving a view name and selecting the fields for selection criteria, save and generate.
3. replicate data sources in BW.
4. create an infosource and assign the data source, mapping and create an infopackage to load data.
Now ,
1. how do we enable Delta for this method?
2. Is this possible at all? if yes, how?
3. How do we proceed after the replication of DataSources in BI? specifically, procedure in BI?
Pls clarify.

When to go for generic extraction using view and infoset query?

Hi,
Can anyone clarify me when we should go for generic extraction using view and when we should go for generic extraction using infoset query....
Also what is the difference between view and infoset?
I tried but could not find out....
Regards,
Kalyani.

Hi Kalyani,
We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
Regards,
Pratap Sone

Issue with generic extraction using FM

Hi All,
I am trying to load from one DSO to other DSO, where i am trying to use generic extraction using FM, where i created strucutre of second DSO .
created Generic datasource with Function module.
when i am loading data using infopackage, its loading perfectly into PSA(with 100 records) and when i am loading thru DTP to Data target( second DSO), it is looping many records in each datapackage(like 8 million in each package) and updating into datatarget finally 100 records. but it is taking long time to finish the process.( i copied RSAX_GET_SIMPLE_DATA) and added transformation logic to it .
so i would like to know, if there is anything i have to change in the Function module code, to fix this.
i would also like to know, request is already in PSA, will it again extract from FM, when updating thru DTP.
Thanks
R,man
Points will be awarded.

Hi
I also had the same process. In the code of the function module. just check the Raise Exception code, probably ABAP guy can help. Also try to debug the code in RSA3 in debug mode. Actually it is going to a infinite loop, I guess.
Regards
Souresh

How to schedule Query Extracts using RSCRM_BAPI

Hi,
Can you give me the link to the document How to schedule Query Extracts using RSCRM_BAPI . I do not have userid password to view the same.
Thanks for the help.

Hi,
this is the link for the document..
https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700004400232004E
thnks.

Hierarchy Extraction using Open hub Destination

Hi,
I need to extract hierarchy data for Application code(YAPPLCD) using OHD. In the Hierarchy there are 4 components(Industry, Market, Application Group and Application Code). i need to get all the 3 details for the Application Code(i.e to which Indusrty does it belong, Market and Application Group).But HIerarchy table is having one record for each apllication code, Market, Application Group, Application code.
How to get relevant data for the application code?
My file format should be:
Appl.Code | Appl.Group | Market | Industry.

Hi Suma...
The SAP Open Hub service enables you to distribute data from an SAP BI/BW system into external data marts, analytical applications, and other applications. With this, you can ensure controlled distribution using several systems. The central object for the export of data is the InfoSpoke. Using this, you can define the object from which the data comes and into which target it is transferred, leveraging SQL Server Integration Services (SSIS) as the transfer/transform mechanism.
SAP BI objects such as InfoCubes, ODS objects, or InfoObjects can act as open hub data sources. You can select database tables or flat files as open hub destinations, and then use those destinations as actual sources within SSIS. To automate the extraction using SAPu2019s Open Hub Service, youu2019ll need to setup a process chain. Note that both a full and delta modes are also available as the extraction mode.
As stated already with direct extraction from SAP R/3, once data is extracted out of SAP NetWeaver® BI (SAP BW), the destination of that data could be any relational database (such as SQL Server), and then reports (from SSRS) and multi-dimensional cubes (from SSAS) can be created from that database data. The resulting SQL Server reports/cubes could then be used within the Microsoft Business Intelligence delivery mechanisms, such as through Excel, SharePoint, PerformancePoint, etc.
Hope this below link may helpful
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c08b1f70-6fb1-2b10-97a5-df4c503e03cb
Regards
Sudheer

Import java class that uses DbConnection

How to import java class that uses DbConnection? I don't want to write my own PluginDataSource.
It is possible to get Connection in imported java classes?

This is not possible. Even connection used by individual PDS are only limited to those individaul PDS only and are not shared across them.
Thanks
Rohit

String extract using regular expression

Hi
I have text like this "<a>45</a><ct>Hi</ct><R>45 85</R><H>Here</H>" .I want to extract using regular expression or any techniques the text between <R> and </R> also need to replace the space with pipe between 45 and 85 like "45|85"
Edited by: vishnu prakash on Mar 2, 2012 4:42 AM

Hi,
Here's one way:
REPLACE ( REGEXP_REPLACE ( txt
                , '.*<R>(.*)</R>.*'
                , '\1'
     , '|'
     )This assumes there is only one <R> tag in txt.
Always say which version of Oracle you're using. The expression above will work in Oralce 10 and up, but starting in Oracle 11 you can use REGEXP_SUBSTR rather than the less intuitive REGEXP_REPLACE.
Edited by: Frank Kulash on Mar 2, 2012 7:48 AM

Delta Extraction Using Function Module ( Customization )

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Hi SGK,
I've done this for a delta based on a timestamp and it's actually pretty easy. The basic steps are:
1) Create an extract structure in SE11. Make sure the structure has a date or timestamp field in it that you can use for delta. You'll need to include the field twice if you also want to extract it to BW/BI since once it's chosen as the delta field then it will be hidden in the interface.
2) Create the extractor function module in SE37. You can use RSAX_BIW_GET_DATA_SIMPLE as a template. Make sure your logic restricts the data it retrieves according to the selections that are passed in I_T_SELECT, including restrictions on the delta field.
3) Create a generic DataSource in RSO2. Click Extraction by FM then fill in your extract structure and function module. Click Generic Delta and pick your delta field and the appropriate radio button (time stamp or calendar day). If your delta field is a timestamp field then be sure to set the upper and lower safety limits to -86400 and 86400 respectively. This might not be necessary on your version of SAPI but on mine there is a bug where it doesn't translate between system time and UTC (GMT) correctly so this was necessary.
You don't need to program any special delta handling logic in your function module as long as you restrict the data you retrieve based on the delta field (I_T_SELECT). This is because the SAPI takes care of catching the init, delta and repeat requests, translating them to the appropriate delta field values, and then passing them to your function module as if it was a full extraction for a specific date or timestamp range.
Hope this helps!
Jason

Extraction Using DBCONNECT

Similar Messages

Maybe you are looking for