Skip to Content
0
Former Member
Nov 30, 2006 at 01:26 AM

Messsage Type X while creating transformation for data store object

514 Views

Experts:

While creating transformation for a data store object in BI 7.0 SP09, I am getting into dumps with message type X. After researching this forum and also the dump, I have applied the latest patch 22 on SAP GUI 640. But, it looks like, it did not resolve the problem. I am pasting the dump information, below. Any help is appreciated.

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:

Control Framework : Error processing control

Long text of error message:

Diagnosis

An error occurred when the system tried to process the commands

from the Automation Queue on the presentation server.

There are several possible reasons for this:

- The installation of the SAP GUI on the presentation server is

faulty or obsolete.

- There is an error in the application program

- There is an error in the SAPGUI or an integrated control

Procedure

1. Make sure that you have imported the appropriate Support

Package, the current kernel, and GUI patch for the release of your

system

2. Check whether the error occurs locally on one or a few PCs, or

generally on all PCs. Note whether the error only occurs for some

users, for example because of a specific Customizing setting.

If it only occurs locally, this suggests an installation problem

with the PC. Check the installation; if necessary, reinstall the

software. In the dump, search for the SY-MSGLI field, since it may

point to the cause of the error.

3. Activate the Automation Trace (in accordance with SAP Note

158985).

4.Start the transaction and continue until the screen immediately

before the dump.

5. From the System -> Utilities menu, choose Autom. Queue,

Synchronous Processing.

The status bar of the GUI displays the text:

"Automation synchron flush mode on"

6. If you now proceed with the application, the short dump will

display the ABAP call that caused the error; the Automation Trace

will contain the error on the presentation server.

7. If necessary, load the short dump and trace files on to

sapservX, so that SAP can analyze them.

Technical information about the message:

Message class....... "CNDP"

Number.............. 006

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

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

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

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

How 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" " "

"CL_GUI_CFW====================CP" or "CL_GUI_CFW====================CM002"

"FLUSH"

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)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

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

actions and input led to the error.

Information on where terminated

Termination occurred in the ABAP program "CL_GUI_CFW====================CP" -

in "FLUSH".

The main program was "RSAWBN_START ".

In the source code you have the termination point in line 23

of the (Include) program "CL_GUI_CFW====================CM002".

Thank,

RR