Application Development and Automation 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: 
Read only

RMDATIND

Former Member
0 Likes
997

Hi all,

can anyone tell me why this kind of error occurs when i execute the standard LSMW for : Maetrial Master(RMDATIND)

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure

"ETABS_TO_TRANSPARENT" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The problem has arisen because, within the database interface,

one of the data buffers made available for the INSERT (UPDATE)

is longer than the maximum defined in the database.

On the other hand, it may be that the length in the NAMETAB

does not match the maximum length defined in the database.

(In this case, the length in the NAMETAB is longer.)

Regards

Swanand

Hi all,

can anyone tell me why this kind of error occurs when i execute the standard LSMW for : Maetrial Master(RMDATIND)

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure

"ETABS_TO_TRANSPARENT" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The problem has arisen because, within the database interface,

one of the data buffers made available for the INSERT (UPDATE)

is longer than the maximum defined in the database.

On the other hand, it may be that the length in the NAMETAB

does not match the maximum length defined in the database.

(In this case, the length in the NAMETAB is longer.)

Regards

Swanand

5 REPLIES 5
Read only

FredericGirod
Active Contributor
0 Likes
767

Hi Swanand,

All error on standard program must be report to SAP. And if you check OSS notes you will find a lot of notes about the class CX_SY_OPEN_SQL_DB.

http://service.sap.com/notes

Regards

Frédéric

Read only

Former Member
0 Likes
767

Hi Swanand

Check the following thread which discusses a similar kind off exception,

cheers

sameer

Read only

Former Member
0 Likes
767

What is the value your are using in parameter "Transaction Per Commit Unit" . Try to reduce this value and rerun the load.

Cheers.

Read only

0 Likes
767

Hi Swanand,

Looking at your error log, it looks like there is mismatch of the structures used by the program and the corresponding database tables.

Did you extend the material master structures by any chance? If so, you need to run program RMDATING. Read documentation of this program to know the purpose of it. After you run this program, then run your RMDATIND.

Regards,

Srinivas

Read only

Former Member
0 Likes
767

At the Screen errors, put /h, select the table <D>-T_ITEM and download the content into excel file.

Delete all registries ITEM_NAME equal 100

Using Text to Columns option in Data excel menu, divide the NODE_KEY field in two peaces, put off the first part and sort A to Z the second one.

And voilá!! The errors will be listed below of each corresponding Material.