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

Dump in while splitting the Document

Former Member
0 Likes
1,289

Hi All,

We are posting documents using BAPI_ACC_DOCUMENT_POST.

it is working fine for upto 100 line item, if in the file more than 100 line items

we are getting dump. in check in the deburg mode, in the subroutine of splitting the document it is giving dump.

Kindly share any valuable soluction for this problem.

I searched for OSS note, but i didn't get the proper one.

Pls check the below Dump.

Short text

The current application triggered a termination with a short dump.

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

Short text of error message:

System error (termination point CLEAR_ASSIGNMENTS)

Long text of error message:

Diagnosis

An internal error has occurred.

System Response

You cannot continue with processing.

Procedure

Contact SAP to establish whether the error can only be rectified by

a program correction, or whether it can also be rectified by

changes to the settings. There may also be an error in the updating

of the data which must be resolved.

Specify the following parameters when reporting the error:

o Message : GLT0/000

o Program : SAPLGLT0

o Termination point : CLEAR_ASSIGNMENTS

Technical information about the message:

Message class....... "GLT0"

Number.............. 000

Variable 1.......... "CLEAR_ASSIGNMENTS"

Variable 2.......... "SAPLGLT0"

Variable 3.......... " "

Variable 4.......... " "

ow to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"MESSAGE_TYPE_X" " "

"SAPLGLT0" or "LGLT0FER"

"INTERNAL_ERROR"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

Regards,

Sri

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
677

Have you read the SAP Notes on the subject....

SAP Note 1447089 - Runtime error MESSAGE_TYPE_X

"CLEAR_ASSIGNMENTS" in SAPLGLT0

1 REPLY 1
Read only

Former Member
0 Likes
678

Have you read the SAP Notes on the subject....

SAP Note 1447089 - Runtime error MESSAGE_TYPE_X

"CLEAR_ASSIGNMENTS" in SAPLGLT0