Creating BO universe on Transparent tables

Hi,
Can we create a BO universe on Transparent tables in the BW system?
Kindly respond if you hvae any inputs

Hi,
Assuming your are using BOE XI 3.1, Integration Kit for SAP, and WebIntelligence
Then, NO, that MDX BAPI driver is for consumption of BEx Queries only.
Regards,
H
p.s. however, you might have more luck using Crystal Reports "SAP Table, ABAP function, and InfoSet" driver - although that is intended for ERP access (R/3 // ECC)

Similar Messages

View on "Transparent Table and DataBase View" ????

Hi
I have three transparent tables and four database views in R/3.
Is it possible to create the view on "Transparent Table and DataBase View". Please let me know
kumar

no it's not possible.

How can I create a universe with the BO repository tables?

Hi. I need make a universe with the BO repository tables, in order to get user information .
But, when I try to insert tables in designer, using a new conecction to BO repository. I can't see tables.
Someone can help me?

The CMS repository is organized into both physical and virtual tables. Only the CMS can access the virtual tables, therefore you cannot create a universe on the CMS repository. You can access the CMS repository information through the Enterprise SDK.
https://www.sdn.sap.com/irj/boc/businessobjects-sdklibrary

How to create a transparent table(z table) dynamically

Hi,
Can anyone explain me how to create a transparent table(z table) dynamically in the program.
Any function module or suggestions welcome.

Hi Mithun
 we will not create transparent table in the program . you could do it by using native SQL in the ABAP Program . the sample is show in below .
This is a sample that show how to connect to Database directly and can use the native SQL to select , create or delete table.
PARAMETERS dbs TYPE dbcon-con_name default 'SDB'.
DATA carrid_wa TYPE scarr-carrid.
DATA lv_int TYPE i.
*Types
data: begin of ty_equi,
equipment(25) type c,
SERIALENERGY(25) type c,
end of ty_equi.
*Internal Tables
data it_equi like table of ty_equi.
data wa_equi like line of it_equi.
DATA dbtype TYPE dbcon_dbms.
SELECT SINGLE dbms
 FROM dbcon
 INTO dbtype
 WHERE con_name = dbs.
IF dbtype = 'ORA'.
TRY.
 EXEC SQL.
 CONNECT TO :dbs
 ENDEXEC.
 IF sy-subrc <> 0.
 RAISE EXCEPTION TYPE cx_sy_native_sql_error.
 ENDIF.
 EXEC SQL.
 OPEN dbcur FOR
 SELECT
 EQUIPMENT,
 SERIALENERGY
 FROM emd.meter
 ENDEXEC.
 DO.
 EXEC SQL.
 FETCH NEXT dbcur INTO :wa_EQUI
 ENDEXEC.
 IF sy-subrc <> 0.
 EXIT.
 ELSE.
 WRITE: /
 wa_equi-equipment,
 wa_equi-SERIALENERGY.
 ENDIF.
 ENDDO.
 EXEC SQL.
 CLOSE dbcur
 ENDEXEC.
 EXEC SQL.
 DISCONNECT :dbs
 ENDEXEC.
 CATCH cx_sy_native_sql_error.
 MESSAGE `Error in Native SQL.` TYPE 'I'.
ENDTRY.
ENDIF.
Regards
Wiboon

Can anyone explain me how to create a transparent table(z table) dynamicall

Can anyone explain me how to create a transparent table(z table) dynamically in the program.

Hi,
Look at the below link
http://www.sap-img.com/ab030.htm
Regards
Sudheer

Creating Transparent Table by code in Memory

Hi,
Iu2019m trying to create a transparent table by code using ABAP and store the table in the memory.
I want to be able to create a physical data dictionary table, just like using se11 (Database table -> Transp. Table), but I want to create it in the memory during runtime without actually creating the table in the system. Iu2019m not interested in using an internal table.
I want to simulate the existence of an transparent table in the system by creating it dynamically on runtime and have it available in the memory so that I can use it as any other table that is created using se11. Iu2019m aware of the FMs DD_CREATE_TABLE and DDIF_TABL_PUT, but these FMs actually create the table in the system, Iu2019m not interested in creating the table permanently.
Thanks & Regards,
Behzad

Hi,
I donu2019t want to be rude, but please, if you are unlettered and canu2019t understand why someone asks for something that you believe is unnecessary because you have never thought about it, just donu2019t answer the question.
Why Iu2019m asking this question is of course NOT because I donu2019t know what an internal table is or how to use it, but because Iu2019m trying to achieve a specific scenario that is not possible with internal tables.
What Iu2019m trying to accomplish is to build an structure in runtime that can be used with the SQL JOIN-statement without the need of creating the transparent table in the system permanently. Joining tables with SQL-query is not possible using internal tables, but if one could create an transparent table in memory on runtime that contains values from an internal table then this temporary transparent table could be used in the SQL-query scenario. This way different types of optimization could be performed on runtime.
So now, if someone can answer my question, without any ridicules and ignorant answer I would be really thankful.
Thanks in advance,
Behzad

Procedure for creating transparent table, data element and domain

Hi,
Can anybody let me know the procedure for creating transparent table, data element and domain.
Thanks,
Mahathi

Hi
Database table and its components
A database table is the central data structure of the ABAP/4 data dictionary.
The structure of the objects of application development are mapped in tables on the underlying relational database.
The attributes of these objects correspond to fields of the table.
A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
A field has a unique name and attributes; for example it can be a key field.
A table has one or more key fields, called the primary key.
The values of these key fields uniquely identify a table entry.
You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
A field is not an independent object. It is table-dependent and can only be maintained within a table.
You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
Two Level Domain Example
A domain defines a field technically and therefore it may
be used at different business levels.
A data element describes the meaning of a domain in a certain business context.
A domain, however, is used for the technical definition of a table field (for example field type and length).
Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
Definitions of Table in Database
In SAP R/3 tables are defined as
A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
SAP is evolving R/3 tables in transparent tables.
Elaboration on each of the definitions
A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
Tables can also reside on the database as Pooled tables or cluster tables
Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
As mentioned above, these table types require special data handling, therefore they are not transparent tables.
Technical Settings in Dictionary
The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
The most important data classes are master data, transaction data, organizational data and system data.
Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
System data is data that the R/3 System itself needs. The program sources are an example.
Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
Modifications to the entries of a table can be recorded and stored using logging.
To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
Parameter 'rec/client' can have the following settings:
rec/client = ALL All clients should be logged.
rec/client = 000[...] Only the specified clients should be logged.
rec/client = OFF Logging is not enabled on this system.
The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
Logging creates a 'bottleneck' in the system:
Additional write access for each modification to tables being logged.
This can result in lock situations although the users are accessing different application tables!
Create transparent table
Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
Enter the delivery class and the table maintenance criteria
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
Enter the name of the table field and the data element. The
System automatically populates the technical details for
existing data elements.
So far as possible it is advisable to use existing data elements which befit the business requirements.
However, we may create data elements if need be. The same is shown in the next slide.
To create a data element simply double click on it.
Alternately create a data element by simply choosing the
data type radio button on SE11 initial screen.
Create data element
The system prompts you to create a new data element.
Choose the Yes pushbutton.
Under the data type tab enter the domain name which
determines the technical characteristics of the field.
Further characteristics tab: Allows you to specify a search help assigned to the data element.
It also allows you to specify a parameter id which helps you populate a field from SAP memory.
Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
Create domain
If the domain does not exist in the data dictionary the
system prompts you to create one.
Give the technical characteristics under the definition
tab. Value range allows you value restriction at domain
level.
Value range tab:
As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
Currency/Quantity fields in a table
A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
Field of the reference table, containing the applicable quantity unit or currency
A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

Sales Orders Transparent Tables Needed

I am trying to create a report with SQV1 that shows
Sales Order
Sales Order Status
Material
Rev Level on Material
ECN Number on Material
ECN Description on Material
I need the transparancy tables for
Sales Order Detail; I tried VBAP and VBAK and both do not show me the
Sales Order Status VBSTT
Also I need to know the Rev Level and ECN Number and description. I
thought they would be in MARC because the rev level shows up in the
Material Master but it is not one of the items you can select. Any idea where
I can find it?
Thanks,
Linda

Hi
For the sales order status, you can refer to VBUK or VBUP.
I looked for ECN number, I think the table and the field are MARC-PRENO
Pls check whether the same is useful to you.
Reward point if it helps.

When Creating a universe using excel, universe is blank.

Hi,
I want to create a universe using excel sheet, my server is 64bit windows, and business objects is 3.1 SP 3 FP 2.6,
I created an ODBC connection; these are the steps I followed
1) I Navigated to C:, windows, syswow64 and ran the application odbcad32
(Windows server 2008 64 bit) and created a ODBC connection using a Excel sheet 2003.
2) Then i did the following change
<Parameter Name="Transactional Available">No</Parameter> is set to Yes under the Generic ODBC Data Source in below location
...\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\odbc\odbc.sbo
3) Then went to universe created connection using under database middle ware as microsoft -MS Excel 2003 - Odbc drivers- and selected the data source connection, test the connection server is working fine.
4) i created a universe using the connection.
But the problem is i canu2019t see the values, dimensions and measures in my universe it blank.
Please help me to overcome the issue.
Regards
Aflal

Hi,
i went to table browser and created the universe, and exported it to the BO server, when i run the report in webi i am getting the following error.
"Microsoft Odbc driver manager data source not found and no default driver specified"
Please help.
Regards
Aflal

Error when define Transparent table

Dear,
When I create a transparent table in ABAP Dictionary, after fill Short Description, Delivery and Maintenance tab, I switch to Fields tab.
When I fill the first field (e.g: name TEST), choose Data Element (e.g: S_CARR_ID) --> ABAP Dictionary recognize that: Data Type is CHAR, Length is 0, and Decimal Places is 0.
But, actually, S_CARR_ID has Data Type is CHAR, Length is 3.
So, ABAP dictionary notifies that Number of positions < minimum number (1) for data type CHAR. Then, I can't do anything except exit.
How to fix the problem

Hi Hannibal2011,
I do exactly what you've done. I.e I filled TEST field with data element S_CARR_ID, nothing happy SAP shows Data type char with 3 character.
I'm afraid that you define a Domain with fix value and forgot to fill 'No. Characters' in definition tab.
please check and reply if any issue.
regards,

Error while trying to create a Universe on Function Module in IDT

Hi,
We are using BO 4.1 Support Pack 2. I am trying to create a Universe on Function Module. I created data foundation layer, but when I right click on the table and click on 'Show table values' it doesn't bring any data (and there is data available in that table). When I click on 'Check Integrity' it says 'Missing Primary key'. Please see the screen shot. Please let me know if any has any idea and I am doing something wrong? I really appreciate it.
Thanks,
Charvi.

Hi Charvi,
What type of database/application are you trying to connect? Are you getting any error message?
Missing primary key message is just a warning and is not related to the issue.
Cheers
Mohan

Creation of a field of 2000 characters in a transparent table

I wanted to add a new field (say Z_LOC_TERM_COND) in a transparent table and the field should have a length of 2000 characters. But when i am going to create it ,its throwing an error that "Field Z_LOC_TERM_COND is too long (Specify a length between 1 and 255)". Kindly help me on that .

HI,
USe the data type STRING or XSTRING and then you need not bother to assign the Length of that.
But make sure that that field is the LAST field in the table.
Also you can alternatively use LCHR type.
Regards,
Sesh

How to delete a key field in a Transparent table

Hi,
I have created a Transparent table Zemployee in which there are 4 fields ( id, name, job, hiredate). I intend to make primary key consists of 2 fields (id, name) but by mistake I have included job field as well.
Now I want to change job field from a key field to non-key field, I use SE11 to display the maintainance of the Zemployee table, unmarked the key label column on job field then I save and activate the table but the system fail to activate the Zemployee table.
So now, what shoul I do to solve this problem ?
Thanks,

Hi,
I have tried again and it work well ( use SE14 as you talk). and now I make job field become key-field again and use se11 to change it to non-key field and it work well too. So I think the problem maybe at the network or somethings else.
Thanks and regards,

Reg : Creation of Transparent table in background

Hi Experts,
 Whether is it advisable to use 'CL_REBF_DDIC_TABL' to create a transparent table.
 I have used PUT_COMPLETE in this class to create the table, I am able to create it.
 This method has a import parameter 'ID_MSGLIST', I am not getting what need to be passed for this parameter.
 I have simply passed some number (eg: 123) for testing, so inside this class if any sy-subrc check fails it is giving
 dump. If sy-subrc is equal to 0 then the table is created successfully.
Regard's,
Jean.

Following are the steps to assign table to a transport request.
1. Create Transport Request in SE09.
2. Double click the Request and Go to Objects Tab.
3. Create an entry with PROGRAM ID = 'R3TR', Object Type = 'TABL', Object Name = <You Table Name>.
Move the transport request to from one system to another.

Infoset query logical database and transparent table

Hi!
We have an infoset with the data source logical database=PNP.
We get some fields from the infotype 0768, P0768-PERNR, P0768-BEGDA, etc.
Now we need add another table to make a join within infotype 0768 and table T5F99SE.
For instance, in infotype 0768 I have one record with the fields PERNR and BEGDA and in the T5F99SE I have 3 records related to the unique record of infotype 0768, the fields of the table are PERNR, BEGDA, ACTDT and ADDAT .
The fields values in the example can be:
Infotype 0768: PERNR=00101800, BEGDA=20110401, DICOT=20, BACHE=1200
Table T5F99SE: record 1 PERNR=00101800, BEGDA=20110401, ACTDT=20110401, ADDAT=PB    E
                         record 2 PERNR=00101800, BEGDA=20110101, ACTDT=20110405, ADDAT=PC    E01
                         record 3 PERNR=00101800, BEGDA=20110401, ACTDT=20110409, ADDAT=PA    E
The result we want get with infoset query is
PERNR    BEGDA   DICOT BACHE   ADDAT
00101800 20110101 20        1200       PB    E
00101800 20110101 20        1200       PC    E01
00101800 20110101 20        1200       PA    E
I would like to get the fields of the infotype and some fields of the table T5F99SE.
Is possible do this action with ABAP modifying an infoset that already exists adding the fields of the transparent table?
What should I do?
Kind regards,
Julian.

My guess is that it would not be possible to include a transparent table into the LDBs PNP and PNPCE. Would need input from a technical expert there.
However, instead of using the LDB, why don't you explore just using a direct table join? You may need to join PA0000, PA0001, PA0002 along with PA0768 and your other tables. An infoset can then be created on this table join.
To go to the mode where you can create the table join, in your infoset transactions, choose 'Table join' instead of 'LDB'.

Creating BO universe on Transparent tables

Similar Messages

Maybe you are looking for