on 01-17-2013 10:31 AM
Hello,
I have opened Message 1023096 with SAP Support.
The SAP employee says:
"Reason behind this error is inactive status of the table DDNTT and
DDNTF at database level. However the nametabs tables DDNTT/F exist on
database level only. They are not defined in the SAP dictionary ( SAP
Note :932779)
Kindly activate the table and validate the issue."
After reading the Note 932779, I understand that tables DDNTT and DDNTF
are not defined in ABAP dictionary.
1. Can these tables be activated in ABAP dictionary?
2. Is there a risk of activating these two tables in the ABAP dictionary?
Thanks in advance for your answers.
Good Day
I am not sure about the real scenario behind this issue but, here is what the SAP Note 932779 says:
DDNTT / DDNTF tables
The tables DDNTT/F exist on database level only. They are not defined in the SAP dictionary. Contents can be displayed with the function module 'DD_SHOW_NAMETAB'. Use the "Status" parameter to look in the active (Status = A) or inactive (Status = I) nametabs.
Here are the answers:
1. Can these tables be activated in ABAP dictionary?
You activate the table ONLY if the table is present in the in the ABAP Dictionary by using Tx SE11. As these tables are present only at the DB level then you will not be able to see in Tx SE11. So this is not possible.
2. Is there a risk of activating these two tables in the ABAP dictionary?
The previous answer clarifies this.
I suggest you to go back to SAP with the details.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Reagan Benjamin wrote:
I suggest you to go back to SAP with the details.
I will do so.
But, this is not the first time that this SAP employee is on the wrong track.
Even worse, this SAP support message is on the wrong track for months.
What do you do when you have such problem with SAP support?
Thanks in advance for your help.
Hello,
In November, I have opened a call because I have Oracle Net problems between
SAP work processes and the Oracle Listener.
Basically there are ORA-12170 (connection timeout) error when I start SAP on one host.
My DB and WAS are running on the same machine, therefore the firewall or the network
in between are not involved.
The processor asks me to activate tables that shouldn't instead of focusing on Oracle Net
related tuning.
Does this answer your question?
Regards,
Hello,
I have said that the table can not be activated in abap dictionnary.
This is the answer:
Kindly goto Trx SE16/SE14/SE11 and check the status of this table and
get back to me with screenshots.
I guess you can understand my frustration.
What do you do when you have such problem with SAP support?
Thanks in advance for your help.
Hello
The only option you can see this table is using the database utility (Tx SE14)
You will not be able to see or list these tables from SE11 or SE16.
I suggest to arrange a call back from the support person who is dealing with this ticket or just open a connection to the SAP system for them to connect and check it themselves.
It saves your time.
Cheers
RB
Hello Benjamin,
Reagan Benjamin wrote:
I suggest to arrange a call back from the support person who is dealing with this ticket or just open a connection to the SAP system for them to connect and check it themselves.
It saves your time.
I fully agree with you.
I have already explained that se16 and se11 are useless.
The worst is that she already has a connection my system for several weeks.
As she is replying:
"I have provided solution for the problem which you are getting at the
moment. I just want you to active table DDNTT and DDNTF at database
level"
After getting this answer, I strongly believe that I speak to a wall.
Therefore I would like to know do what you do when a ticket with a SAP
expert is becoming such a nightmare.
Thanks in advance for your answer.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.