SAPSQL_EMPTY_TABNAME

Hello Evryone,
Presently we are facing dumps 1 in every second in CRM system saying
"SAPSQL_EMPTY_TABNAME" CX_SY_DYNAMIC_OSQL_SYNTAXC
"SAPLIPC_V01" or "LIPC_V01U02"
"SELECT_COUNT"
can someone please help me with this.
Rajesh

Hi,
This seems to generic dump message. This might occur due to many reasons.
One might be ' You execute many read operations in parallel processes. In this case, both parallel processes are requested to create a new table. However, only one process can be successful. The other terminates.
If you can explain the scenario of dumps bit more clearly, i can help you out.
Regards,
Venkat

Similar Messages

Activating data in DSO got dump SAPSQL_EMPTY_TABNAME after BW system copy

Hi all,
We had an issue after system copy.
After a system copy the data in the standard DSOs(all of them) cannot be activated. The DOSs themselves are active, the transformations are active but if one attempts to load data and activate u2013 it does not work. The job terminates with shortdump SAPSQL_EMPTY_TABNAME.
Found the issue is caused by u201Cmore than one versionu201D of the change log.
We tried the Program RSAR_RSTSODS_CHANGELOG_VRS but it didn't work.
We had the solution like this:
After activating the DSO itself(the object) using RSDG_ODSO_ACTIVATE the issue disappears and the data can be activated. Issue also disappears. BUT Drawback: Activating the DSO causes the transformations to deactivate.Then we used the program RSDG_TRFN_ACTIVATE to activate all transformations. And then the issue disappeared.
Want to know what the root cause for this. From some SDN threads, mentioned BDLS job in the post refresh steps are not correctly done during system copy may cause this issue. How did the BDLS run wrongly cause this issue? And what is the exact correct way? We ran BDLS for each source systems inlcuding the target refreshed BW system itself by the default selection - conversion of Client-Dependent and Client-Independent Tables; because we used database copy
for the system refresh.
We also restored all source systems in RSA1 inlcuding the refreshed BW system own in the post-refresh steps.
Thank you very much for your information and suggestion.
Heming

Hi Arun, as you say two change log tables it´s strange. In fact in my opinion it´s not right but the problem is that the second change log table appears after executing std SAP report RSDG_ODSO_ACTIVATE in order to be able to activate the DSO. So the solution provided by SAP it works but i´m not sure if the right one. Besides this the original change log table is full of data while the second one is empty... for new loads which are gonna a be filled by the activation process ? I suppose the second one... will this have some impact with the data stored in the first one... not in theory but.... i do not feel confortable with the consequences of this report.
And the most important, it seems that the reason why the DSO and the change log table had problems is due to a some problems or missing steps after executing the BDLS after BW system refresh but nobody can confirm this point...
So, i´ve been able to solve the issue but now i have two change log tables for the same DSO.
Anybody has the same situation after executing the above mentioned SAP std report ?
Regards,
Joaquin Casas Baca-Castex

Short dump in SPRO bcozof CX_SY_DYNAMIC_OSQL_SYNTAX / SAPSQL_EMPTY_TABNAME

Hi,
In SAP ECC 6.0 SPRO, when I try to search 'special fields', it gives me three values.
Out of which, when I select third result 'Define Special Fields for Line Item Display - General Ledger Accounting (New)', it result into syntax error because of Runtime Errors SAPSQL_EMPTY_TABNAME or Exception CX_SY_DYNAMIC_OSQL_SYNTAX in FM STREE_READ_NODE_GENER.
I tried to find SAP note to clear the issue, but only get 2 SAP notes 1137512 & 1415372 which are invalid for SAP ECC 6.0 release.
Even after searching for any relevant note, I couldn't get anything. I want to know whether SAP has provided any note for this issue or not yet?.
Thanks in advance.
Regards,
Ni3

Solved on my own, the process I followed:
Transaction SPRO
Click 'SAP Reference IMG' box
Click 'Find' icon (binoculars)
In the popup box, there is Text Index Info area, you will get the last time the text index was generated. If it has been a while, simply click the 'Refresh in Background' button.
It creates background job 'SHI3_TEXT_INDEX_UPDATE_E'. Once the job is finished, you can access the SPRO transaction without any syntax error.
Regards,
Ni3

Error while saving the Sales Order

Hi experts,
i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
Thanks.

I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
If you see what they are, you can check to see what the usages represent. Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc. In our system, we only have A entries.
What are the usages for the 521 entries? Do they relate to Free Goods/Pricing???
Does the table KOTN521 exist in the ABAP Dictionary?
Answering these questions may get you closer to the answer.
Can you compare the values in these entries to what you have in different SIDs?
Is this problem happening in Production, or is it still in a development or Quality Assurance client?
If it is still in development or Q, then it may be that a recent customization change was made.
Compare the entries across your systems, if possible.
Good luck
Brian

Define Service Desk Destination in the Solution Manager System (Dump creen)

hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors         SAPSQL_EMPTY_TABNAME
Except.                CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time          13.07.2008 14:05:57
Short text
    A dynamically specified FROM clause has an unexpected format.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSHI2" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
     caught in
    procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The running ABAP program attempted to execute an Open SQL statement in
    which a FROM clause was specified dynamically in the field "TABLE_NAME". In
     this
    FROM clause, either a table name after a join operator is missing, or an
     alias name after the key name "AS". The field "TABLE_NAME" could be empty as
    well.
regards

Hi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks.

OPEN_CURSOR JOIN_FLEXA_BKPF error sap BI in FM FAGL_GET_LINE_ITEMS.

Hi Experts,
ECC to BI extraction job getting failed in ECC for extractor 3FI_GL_LG_SI and dumps in ST22 are getting generated. As per the initial analysis from Basis team, seems to be an ABAP Programming Error.
Below is the error details:
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX' and was not caught
in procedure
"FAGL_GET_LINE_ITEMS" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
The reason for the exception is:
The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field "LD_DBTAB_SYNTAX".
In this
FROM clause, either a table name after a join operator is missing, or an
alias name after the key name "AS". The field "LD_DBTAB_SYNTAX" could be
empty as
well.
We are getting dump in the Function Module FAGL_GET_LINE_ITEMS as it shown in the screenshot.
Regards,
Rajesh

Hi Manish,
It says "A dynamically specified FROM clause has an unexpected format" and the Name of the Runtime Error showing as "SAPSQL_EMPTY_TABNAME". Here dump is coming during the processing of the FM FAGL_GET_LINE_ITEMS which is a standard one.
What we have found here is that the Internal Table lt_where_tab(Line No. 360) contains no value, hence the ELSE portion is getting processed.
Regards,
Rajesh

Change Log issues - Post Upgrade

Hi Experts,
We are in the process of Upgrading BW from 3.X to BI 7. As part of this we copied our existing Production system into the sand box and basis did the technical upgrade on the same (Sand Box). Later we ran some post upgrade Jobs as part of the SAP defined Upgrade Process.
1) But after the upgrade i can notice that most of the ODS objects, doesn't have 'Change Log' table in the 'Information (Log/Status)' screen.
2) Even when i try to view the change log content in Manage screen, it gives me a pop up to enter the change log table, instead of directly taking me to the selection screen.
3) When i try to activate a request, even that fails with an SQL error 'SAPSQL_EMPTY_TABNAME'.
Is there any process that has to be run to link the Older version change log tables to the corresponding ODSs after Upgrade?
Has anyone come accross similar issues? If yes, how was it solved? All suggestions are invited.
Thanks and Regards,
Jay

HI JayaPrasad,
Chek the note : 1059171 which is related to Change log,
I too faced this issue when upgraded to Bi7.0 on SP12, but as soon as SP13 is installed the issue is solved, so I suggest to go for SP 13 for upgrading to Bi7.0.
Regards,
Srinivas

DSO Request Activation

Hi All:
When trying to activate a successfully loaded request in an ODS, the job cancels.
When I check the Job Logs, it mentions error "SAPSQL_EMPTY_TABNAME", Exception "CX_SY_DYNAMIC_OSQL_SYNTAX". Short Text "A dynamically specified FROM clause has an unexpected format".
I checked SAP Notes but couldn't find anything. Somebody mentioned a similar error some time ago, but it was fixed with SP 13... We're in BI 7.0, SP 15...
Did anybody get this error or a similar one?
Thanks in advance.
Regards,
Luis

Pls raise an OSS to SAP.
If not in production ,try deleting all the data ,reload small data and try activating it.
Also check DB02 transaction for any active or change log table errors
Hope it Helps
Chetan
@CP..

Activate Error

Hi experts,
When I activate data of ODS.Error happened.
Runtime error: SAPSQL_EMPTY_TABNAME
exception:CX_SY_DYNAMIC_OSQL_SYNTAX
What's the root reason? and how to solve it? Thank you.

Hi,
have you checked the keys of the ODS...chaeck if it's any fields are empty...if yes then it is not possible to activate it.....all the key fields of the ODS should be populated.
Thanks

SAPSQL_EMPTY_TABNAME

Similar Messages

Maybe you are looking for