Error in Dtp while loading to master data

[Former Member]

Hi friends,

while loading data from a standard data source to master data the DTP end s with following error

i tried several times,tried clearing temp tables like psatemp, etc, then i tried removing semantic group,

nothing is really working,dtp fails within seconds,basically the status of DTP is yellow and as you know i cant change the status to red in master data,but in details tab it is red with following below errors please assist.

Data structures were changed. Start transaction beforehand

Exception CX_RS_FAILED logged

[Former Member]

Hi,

This seems to be authorization related issue, try giving SAP_ALL authorizations to ALEREMOTE and execute your load.

Regards,

Durgesh.

[Former Member]

*actually,there is no aleremote user in the system,ad system user has SAP_all authorization,*

*i tried checking locks ,there are no locks on that masterdata,i tried loggig off and logging in again for 3,4times from last two days*

*could you please check the below dump it is giving*

`````````````````````````````````````````````````````````````````````

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_SY_NO_HANDLER

Date and Time 08/05/2011 11:23:29

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_SY_NO_HANDLER' was raised, but it was not caught anywhere

along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program

'CL_RSBK_CMD_X=================CP' has to be

terminated.

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

An exception occurred which is explained in detail below.

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

and

therefore caused a runtime error.

The reason for the exception is:

An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled

locally, nor declared in a RAISING clause

The occurrence of the exception is closely related to the occurrence of

a previous exception "CX_SY_OPEN_SQL_DB", which was raised in the program

"CL_RSODSO_SEMANTIC_PACKETIZER=CP",

specifically in line 79 of the (include) program

"CL_RSODSO_SEMANTIC_PACKETIZER=CM002".

The cause of the exception was:

The database returned a value containing an error

How to correct the error

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:

"UNCAUGHT_EXCEPTION" "CX_SY_NO_HANDLER"

"CL_RSBK_CMD_X=================CP" or "CL_RSBK_CMD_X=================CM00S"

"IF_RSBK_CMD_X~GET_DATAPACKAGE_GENERAL"

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.

System environment

SAP-Release 700

Application server... "sap01226"

Network address...... "157.163.136.77"

Operating system..... "Linux"

Release.............. "2.6.16.60-0.74.7-smp"

Hardware type........ "x86_64"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 30

Shortdump setting.... "full"

Database server... "sap01226"

Database type..... "ORACLE"

Database name..... "B2Q"

Database user ID.. "SAPB2D"

Terminal................. " "

Char.set.... "en_US.ISO-8859-1"

SAP kernel....... 700

created (date)... "Feb 27 2011 20:47:14"

create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"

Database version. "OCI_102 (11.2.0.2.0) "

Patch level. 291

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 700

Operating system..... "Linux 2.6"

Memory consumption

Roll.... 16128

EM...... 8371072

Heap.... 0

Page.... 24576

MM Used. 4117912

MM Free. 64896

User and Transaction

Client.............. 080

User................ "Z001TMRX"

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

Transaction......... " "

Transactions ID..... "4E2DFA7C39383D47E10000009DA3884D"

Program............. "CL_RSBK_CMD_X=================CP"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

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

in "IF_RSBK_CMD_X~GET_DATAPACKAGE_GENERAL".

The main program was "RSBATCH_EXECUTE_PROZESS ".

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

of the (Include) program "CL_RSBK_CMD_X=================CM00S".

The program "CL_RSBK_CMD_X=================CP" was started as a background job.

Job Name....... "BIDTPR_730051_1"

Job Initiator.. "Z001TMRX"

Job Number..... 11231300

Edited by: vishnupsbi on Aug 5, 2011 6:37 PM

Edited by: vishnupsbi on Aug 5, 2011 6:37 PM

[former_member182470]

Hi,

Take the help of an ABAPer to debug the dump. You will be able to find out the inconsistency. He may put breakpoints in the code to run the process successfully.

Regards,

Suman

[Former Member]

Thanks guys the issue has been solved,it was because of inadequate PSATEMP space.

Basis increased the space.

[Former Member]

Thanks guys the issue has been solved,it was because of inadequate PSATEMP space.

Basis increased the space.