topic Re: Custom/ transparent table definition without key in Application Development and Automation Discussions

Custom/ transparent table definition without key

Former Member — Wed, 08 Jun 2005 21:39:55 GMT

Hi:

How can I define a custom table / transparent table via SE11 without specifying any fields as part of table key - i.e. table without key fields?

Re: Custom/ transparent table definition without key

ssimsekler — Wed, 08 Jun 2005 22:11:59 GMT

Hi Chetan

For what reason on earth one can require this? This is not suitable for relational DB structure and DDIC does not allow it even just defined. Or do I lack somethings???

Regards

*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Re: Custom/ transparent table definition without key

RichHeilman — Thu, 09 Jun 2005 00:15:41 GMT

The only thing I could think of where you might want to do this is in the case where you need a flat structure. Maybe to hold some comma delimited data to be exported thru some interface. Even then I would probably suggest to write the data to some flat file on the app server.

I am not sure if DDIC forces you to have a key field or not.

Regards,

Rich Heilman

Re: Custom/ transparent table definition without key

Former Member — Thu, 09 Jun 2005 01:41:05 GMT

Hi:

I was about to write not to go into why do I need this, because I really do need this

Actually there is no restriction at the database level that a table must have a key. At database level (Oracle, Sybase etc), it is possible to define a table without key fields; and that's exactly is the requirement. I have to replicate a table in SAP which already exists in some other database without any key fields.

I know from relational database viewpoint it doesn't make sense, but if things are possible at database level, I wonder why is such a restriction when one goes via SE11. One reason is that to make data client-dependent one has to include MANDT; and it is not possible to have more than one record in a table if MANDT is the only key. I am curious to know why SAP won't allow defining a table without MANDT and without any key.

Anyway, I tried all all options and couldn't suceed. Wanted to check with folks on SDN; but I think the answer is no.

Re: Custom/ transparent table definition without key

Former Member — Thu, 09 Jun 2005 06:26:02 GMT

Hi,

SAP does allow defining tables without the key field mandant/client. It's just not recommended.

From my experience you need to define at least 1 key field in the SAP dictionary.

Mabye you can add an extra field, a counter, which your program will fill with a unique value although this information is not present in your other DB table.

Or, if you know your database well on which the SAP system is running and you know your way around SQL, you can use the native SQL statements in an ABAP program.

Native SQL will allow you to bypass the restrictions the SAP dictionary imposes.

Hope this helps.

Regards,

Arjan

Message was edited by: Arjan Aalbers

Re: Custom/ transparent table definition without key

Former Member — Thu, 09 Jun 2005 06:43:06 GMT

Hi,

you must have at least one key field in a table. For you purposes it might work out to create a table with a somehow generic field (counter, time stamp or whatever) as a key and store the relevant information in the rest of the fields. Each database requires a key.

Siggi

Re: Custom/ transparent table definition without key

Former Member — Thu, 09 Jun 2005 07:15:57 GMT

Technically a fully qualified RDBMS should not allow a table be defined without a key. I wonder why databases like Oracle allows it.

However, when a table is defined in ABAP dictionary it should be independent of the underlying database, or rather the dictionary definition should be such that it holds good for all databases. Incase any of the database that doesnt allow a table to be defined without a key field, it would be interesting to know how a table defined in ABAP dictionary without a key field( supposing such a definition is allowed in ABAP Dictionary) is generated in the underlying database. May be this is one of the reasons why such definition is not allowed in ABAP dictionary. Just a thought. I amnt sure!!

Regards,

Vijay

Re: Custom/ transparent table definition without key

Former Member — Thu, 09 Jun 2005 16:22:09 GMT

1st option:

you can achieve desired results,to some extent, by including all the fields of the table in the primary key definition. Then you can populate any data as long it's not a complete duplicate copy of any existing row.

But then in that case I don't see any point in keeping that row in the table as you will never be able to differentiate between the rows if those are exactly same. Further, how does it matter whether it contains 1 row or 2 rows with the same value.

2nd option:

If you really need, what you said,mainly a dump of all the data in one table where you do not need to differentiate the records.. then I think you should use cluster table ( am I forgetting the name ).

Check the help for statement

EXPORT TO dbtable ...

Best Way:

Or else create a number range for record number and make that primary key...

BTW..you can surely define a table without MANDT (for Client independent data ).

Thanks,

Ram