Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Master Data Datasource not getting loaded

Hi All,

I am using BI 7.0 Environment .I am trying to load a Master data . But when i am scheduling the load via infopackage the data is not getting updated to PSA and the request stays "Yellow" . When i am seeing in ST22 it gives the Below Short Dump :

What happened?

When writing a data record to the database (i.e. when

updating the database), only part of the data field was

written (updated). The rest was truncated.

What can you do?

If the error occurred in Open SQL, there is probably an inconsistency

between the NAMETAB and the ABAP Data Dictionary.

Compare the length specifications of the fields in the NAMETAB with

those in the ABAP Dictionary and contact someone who is able to

perform a consistency check and eliminate the problem.

In most cases, this person will be your SAP consultant.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "INSERT_ODS" "(FORM)", 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 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.)

Any pointers how to solve it ??

Former Member

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question