Connection Object Error

[Former Member]

Hi,

When i create an Connection oBject in the fresh system,the system throws the below error message:

""Error in reading table EFISEL

Message no. E9014

Diagnosis

An error occurred during reading of one or more table entries. This error was reported by the database system.

System Response

The system does not permit the reading of one or more table entries.

It is possible that an SAP short dump has been written from the SAP basis system.

Procedure

Find out if the SAP short dump provides additional information.

You can view SAP short dumps using Transaction SM21.""

Can any one suggest the solution.

Thanks.

[Former Member · Accepted solution]

Hi Santhosh,

Please check the entries in the following path:

SPRO-SAP Utilities-Master Data-Connection Object-Define Field Selection for Address Data.

It might happen that for some of the fields data are not maintained properly. Please look into this and hopefully it will solve your issue. Please check which are required and which not to be displayed etc. The error is happening due to some inconsistency in the above configuration as understood from the error message.

Thanks.

Nirmalya

[Former Member]

Hi,

Since your system is fresh, configuration mentioned by Nirmalya might not be maintained at all. As suggested by Nirmalya, please maintain an entry at SPRO-SAP Utilities-Master Data-Connection Object-Define Field Selection for Address Data.

All the best!

Regards,

Avinash

[Former Member]

Thanks to all.

[Former Member]

Hello everyone

I'm having the same message, this time however it was an error reading table EASTL.

Job started

Step 001 started (program ZDM_EXTRACT_CON_ANALYSER, variant VAR1)

Error in reading table EASTL

Job cancelled after system exception ERROR_MESSAGE

Any idea on where this error is coming from?

Thanks

Guru

[Former Member]

Never mind answering this one. I found a solution, as described below.

It was actually a Z program error, where the program was trying to select from EASTL for a non existing installation. The exception raised by SAP was however not caught properly by the calling Z program, & that's why we had the error. For similar errors in future, the accompanying error message in the batch job log needs rto be looked at closely as it gives us all the clues we need.