Getting "MESSAGE_TYPE_X " while executing a T Code

[vamshi_sapient]

Hi,

I am getting dump with MESSAGE_TYPE_X . Please check and help me.

Category ABAP programming error

Runtime Errors MESSAGE_TYPE_X

ABAP Program SAPLGLIU

Application Component FI-SL-SL

Date and Time 06/22/2022 22:18:47

Short Text

The current application has triggered a termination with a short dump.

What happened?

The current application program has detected a situation that should

not occur. A termination with short dump has therefore been triggered

by the key word MESSAGE (type X).

What can I do?

Note which actions and entries caused the error to occur.

Consult your SAP administrator.

Using transaction ST22 for ABAP dump analysis, you can view, manage,

and retain termination messages for longer periods.

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 the error message:

Update problem in line item table GMIA (FI-SL)

Long text of the error message:

Diagnosis

The system attempted to update one or more documents in table GMIA

(FI-SL). This attempt failed due to a problem when inserting line

items.

It is highly likely that this runtime error was caused by a DUPREC

problem. The system attempted to insert a line into line item table

GMIA (FI-SL) for which a line with the same unique key already

exists (duplicate record).

Normally, the SL-based line item tables must have unique keys for

the following combinations:

o Key 1:

- RCLNT

- GL_SIRID

o Key 2:

- RCLNT

- DOCNR

- RYEAR

- DOCCT

- RBUKRS

- RLDNR

- DOCLN

The following causes for a DUPREC error are possible in this case:

o The number range objects for the DOCNR or GL_SIRID fields (if

available) are not maintained correctly.

Note here that the number range objects for the DOCNR field can

differ according to application.

The GL_SIRID field (if available) is normally assigned to the

number range object GL_RECID.

o Documents or line items were subsequently posted that have

already been posted once before or that were not previously

deleted.

o An additional customer-specific UNIQUE index was created.

stem Response

The update was terminated with a runtime error.

Procedure

Check whether the line item table GMIA (FI-SL) contains one or more

data records for the document(s) listed below. The next steps for

this procedure are described in SAP Note 62150.

Analysis information:

o The system attempted to update the following documents

(ledger/company code/year/SL document number):

- 90/IBRD/2022/0000000001,

-

o The system attempted to update the following GL_RECID keys

(min./max. values):

- GL_SIRID: 000000001693169663 - 000000001693169664

If the analysis shows that the problem is not a duplicate record,

further causes for the runtime error (such as problems in the

database system) must be analyzed.

Technical information about the message:

Message class....... GI

Number.............. 217

Variable 1.......... GMIA (FI-SL)

Variable 2.......... 90/IBRD/2022/0000000001,

Variable 3..........

Variable 4.......... "GL_SIRID: 000000001693169663 - 000000001693169664"

How to correct the error

If the error occurs in one of your own ABAP programs or an SAP program

that you have modified, try to correct the error yourself.

If the error occurs in a non-modfied SAP program, you might be able to

find a solution in the SAP Notes system. If you have access to the SAP

Notes system, check there first using the following keywords:

"MESSAGE_TYPE_X"

"SAPLGLIU" bzw. LGLIUF20

"CHECK_DUPRECS_IN_TAB"

If you cannot solve the problem yourself, please send the following

information to SAP:

1. This description of the problem (short dump)

To do this, choose System -> List -> Save -> Local File (unconverted)

on the screen you are in now.

2. A suitable system log

To do this, call the system log in transaction SM21. Restrict the time

interval to ten minutes before the short dump and five minutes after

it. In the display, choose System -> List -> Save -> Local File

(unconverted).

3. If these are programs of your own, or modified SAP programs: Source

code of these programs

To do this, choose More Utilities -> Upload/Download -> Download in

the Editor.

4. Details regarding the conditions under which the error occurred or

which actions and input caused the error.

System environment

SAP Release..... 750

SAP Basis level 0019

Application server... ts1ci50

Network address...... 10.177.64.16

Operating system... Linux

Release.............. 3.10.0-1160.49.1.el7

Hardware type....... x86_64

Character length..... 16 Bits

Pointer length........ 64 Bits

Work process number... 38

Shortdump setting. full

Database server... w1sqlnng01

Database type..... ORACLE

Database name..... TS1

Database user ID SAPR3

Terminal.......... ts1ci50.worldbank.or

Character set C

SAP kernel....... 753

Created on....... Jan 29 2022 13:06:05

Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr220129

Database version OCI_112, 12.1.0.2.0, V2, default

Patch level....... 921

Patch text.......

Database............. ORACLE 11.2.*.*.*, ORACLE 12.*.*.*.*

SAP database version. 753

Operating system... Linux

Memory consumption

Roll.... 0

EM...... 0

Heap.... 3713968

Page.... 0

MM used. 3575960

MM free. 133984

User and Transaction

Client................. 300

User.................. XXXXXXX

Language key.......... E

Transaction.........

Transaction ID...... B590E15C6E520080E0062B3B1EF6849F

EPP whole context ID...... 36324233393942463632423339394246

EPP connection ID........ 00000000000000000000000000000000

EPP call counter......... 0

Program.............. SAPLGLIU

Screen.............. RSM13000 3000

Screen line.......... 2

Active debugger..... "none"

Information on where terminated

The termination occurred in ABAP program or include "SAPLGLIU", in

"CHECK_DUPRECS_IN_TAB". The

main program was "RSM13000".

In the source code, the termination point is in line 202 of program or

include "LGLIUF20".

Program "SAPLGLIU" was started in the update system.

SourceCde

ld_msg_03 = ld_work.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-rldnr.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-rbukrs.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-ryear.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-docnr.

CONTINUE.

ENDIF.

IF ld_tabix1 = 4.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-rldnr.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-rbukrs.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-ryear.

REPLACE '$' INTO ld_msg_03 WITH ls_an1-docnr.

CONTINUE.

ENDIF.

ENDLOOP.

REPLACE ALL OCCURRENCES OF '$' IN ld_msg_02 WITH SPACE.

REPLACE ALL OCCURRENCES OF '///' IN ld_msg_02 WITH SPACE.

REPLACE ALL OCCURRENCES OF '$' IN ld_msg_03 WITH SPACE.

REPLACE ALL OCCURRENCES OF '///' IN ld_msg_03 WITH SPACE.

SORT gt_analysis BY gl_sirid.

describe table gt_analysis lines sy-tfill.

read table gt_analysis into ls_an1 index 1.

read table gt_analysis into ls_an2 index sy-tfill.

ld_work = 'GL_SIRID: $ - $'.

REPLACE '$' INTO ld_work WITH ls_an1-gl_sirid.

REPLACE '$' INTO ld_work WITH ls_an2-gl_sirid.

ld_msg_04 = ld_work.

CONCATENATE pd_tab ' (' ld_component ') ' INTO ld_msg_01.

MESSAGE X217(GI) WITH ld_msg_01

ld_msg_02

ld_msg_03

ld_msg_04.

ELSE. "More than 4 documents in FI-SL (not possible to display)

SORT gt_analysis BY gl_sirid.

describe table gt_analysis lines sy-tfill.

read table gt_analysis into ls_an1 index 1.

read table gt_analysis into ls_an2 index sy-tfill.

ld_work = 'GL_SIRID: $ - $'.

REPLACE '$' INTO ld_work WITH ls_an1-gl_sirid.

REPLACE '$' INTO ld_work WITH ls_an2-gl_sirid.

ld_msg_03 = ld_work.

CONCATENATE pd_tab ' (' ld_component ') ' INTO ld_msg_01.

WRITE ld_doc_count TO ld_msg_02 LEFT-JUSTIFIED NO-ZERO.

MESSAGE X218(GI) WITH ld_msg_01

ld_msg_02

ld_msg_03

ld_msg_04.

ENDIF.

Thanks for the help.

[Former Member]

Welcome to the SAP Community. Thank you for visiting us to get answers to your questions.

Since you're asking a question here for the first time, I'd like to offer some friendly advice on how to get the most out of your community membership and experience.

First, please see https://community.sap.com/resources/questions-and-answers, as this resource page provides tips for preparing questions that draw responses from our members. Second, feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html, as that will help you when submitting questions to the community.

I also recommend that you include a profile picture. By personalizing your profile, you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html.

Now for some specific suggestions on how you might improve your question:

* Outline what steps you took to find answers (and why they weren't helpful) -- so members don't make suggestions that you've already tried.

* Share screenshots of what you've seen/done (if possible), as images always helps our members better understand your problem.

* Use the "insert code" feature when sharing your code, so members have an easier time reading.

Should you wish, you can revise your question by selecting Actions, then Edit.

The more details you provide (in questions tagged correctly), the more likely it is that members will be able to respond. As it stands, I don't know if there is enough information here for members to understand your issue. So please consider revising your question because I'd really like to see you get a solution to your problem!

I hope you find this advice useful, and we're happy to have you as part of SAP Community!

[Sandra_Rossi]

It seems to be full standard, did you check the SAP notes?

[tom_wan]

Note 3078176 - Dump MESSAGE_TYPE_X with GI 217 error

This note could help.