Problem Transaccion usmm

[former_member294588]

when trying to generate the report I generated the following error MESSAGE_TYPE_X.

Annex the error log

Runtime Errors	MESSAGE_TYPE_X
Date and Time	01.08.2013 18:52:49

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.

[former_member294588]

when trying to generate the report I generated the following error MESSAGE_TYPE_X.

Annex the error log

Runtime Errors	MESSAGE_TYPE_X
Date and Time	01.08.2013 18:52:49

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.

usmm.TXT.zip

[arindam_m]

Hi,

Just saw the sy-subrc is set to 1 after FM TUJOB_START_MEAS_JOB call. The German text for exception means 'Can not be started because not scheduled'. Entries in table tujob might be missing. Hope that gives some pointers as I am not aware of the context in which the dump occurs.

Cheers,

Arindam

[Former Member]

Hi!

Please check whether the job is scheduled properly in sm36 or sm37.

You can also check the logs for any hints.

Hope this helps.

Regards,

Shruti