Skip to Content

Data extraction

Hi All

I need to extract data from MaxDB Data Base into BI 7.0......Can anyone please point me to some information how to extract data from Max DB .. what all steps are needed to get data to BI side from data base?

Thanks & Regards

Shivanjali

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Aug 22, 2007 at 07:43 AM

    Hi,

    you can either use UDConnect or DBConnect.

    I am not so familiar with UDConnect but with the SAP documentation that shouldn't be an issue.

    For DBConnect, I believe it is quite more simple:

    - install the DBSL (database shared library) for this DB system on your BI7.0 host (perhaps this step is not necessary since the library could already be installed)

    - in BI7.0 create a source system under DBConnect and select ADA as DBMS

    - enter a valid user name and pwd for connecting to your MAXDB

    - in conn info enter <Server>-<DBName>

    Call transaction RSDBC and verify that you see views/tables from this source system

    hope this helps...

    Olivier.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi All

      This is the way i followed and successfully created the connection....

      To Configure UD Connect on the J2EE Server for JDBC Access to External Databases

      i followed this PDF

      https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff

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

      Following data type assignments are permitted:

      Data Type in SAP BW

      Data Type in the UD Connect Source

      ACCP

      C

      CHAR

      All except X and b

      CUKY

      C

      CURR

      P, I

      DATS

      D, g

      DEC

      P, I

      FLTP

      F, I

      INT1

      B

      INT2

      S

      INT4

      I

      LCHR

      G, V

      NUMC

      I

      PREC

      b

      QUAN

      I, P

      SSTR

      C

      STRG

      g

      TIMS

      T

      VARC

      All except X, P, F

      UNIT

      C, g

      Abbreviations for the data types of UD Connect sources:

      C – character

      X – hexadecimal

      P – packed decimal, decimal

      I – integer

      n – numeric string

      D – date

      b – tiny int

      g, G – long string

      F – float

      s – small int

      V – variable character

      T – time

      All the things i get from sdn...

      Thanks & regards

      Shivanjali