Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Transparent Table changes

Former Member
0 Kudos

1. Changes to active transparent tables: The type for the non-key field is to be changed from NUMC to CHAR. What follow up actions are to be expected?

2. Can we buffer database view table? Does it exist in the underlying database in R/3? Can we insert, change, modify data into database view table?

3. How database view is different from logical database?

4. Performance wise which one will be better and why?

Regards,

Mau

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

<b>1. Changes to active transparent tables: The type for the non-key field is to be changed from NUMC to CHAR. What follow up actions are to be expected?</b>

If the table is a standard table, you will have to apply for the SSCR key. Once you get the SSCR key, then you can go on and change the standard table. But, as soon as you get the key, SAP will no longer support that table, that means, if something goes wrong in the system because of that field type change, SAP will not suppprt. So, think clearly before changing the field type. That field might have been used in many other tables, so even in those tables this change will reflect which may cause inconsistency in the system.

<b>2. Can we buffer database view table? Does it exist in the underlying database in R/3? Can we insert, change, modify data into database view table?</b>

Yes, database view can be buffered. It does not exist in the underlying database. You can insert, change, modify data into database view but it is not advisable because view is made up of different fields from different tables. So, by inserting, changing, modifying data in a view can cause inconsistency.

<b>3. How database view is different from logical database?</b>

Logical database has its own selection screens, own hierarchy and data fetching logic. Whereas view does not have any of it. Logical database exists in the underlying database whereas view does not.

<b>4. Performance wise which one will be better and why?</b>

It is based on the scenario.

Reward points if the answer is helpful.

Regards,

Mukul

1 REPLY 1

Former Member
0 Kudos

Hi,

<b>1. Changes to active transparent tables: The type for the non-key field is to be changed from NUMC to CHAR. What follow up actions are to be expected?</b>

If the table is a standard table, you will have to apply for the SSCR key. Once you get the SSCR key, then you can go on and change the standard table. But, as soon as you get the key, SAP will no longer support that table, that means, if something goes wrong in the system because of that field type change, SAP will not suppprt. So, think clearly before changing the field type. That field might have been used in many other tables, so even in those tables this change will reflect which may cause inconsistency in the system.

<b>2. Can we buffer database view table? Does it exist in the underlying database in R/3? Can we insert, change, modify data into database view table?</b>

Yes, database view can be buffered. It does not exist in the underlying database. You can insert, change, modify data into database view but it is not advisable because view is made up of different fields from different tables. So, by inserting, changing, modifying data in a view can cause inconsistency.

<b>3. How database view is different from logical database?</b>

Logical database has its own selection screens, own hierarchy and data fetching logic. Whereas view does not have any of it. Logical database exists in the underlying database whereas view does not.

<b>4. Performance wise which one will be better and why?</b>

It is based on the scenario.

Reward points if the answer is helpful.

Regards,

Mukul