cancel
Showing results for 
Search instead for 
Did you mean: 

Xpra_execution phase error execution of report return code 12

Former Member
0 Kudos

Hi,

i am installing BI_CONT add on my ides system.

At phase xpra_execution its giving error "Execution of reports after put finished returncode 12". I have tried continuing 3 times.

-


Program terminated (job: RDDEXECL, no.: 00174500

See job log

Execution of programs after import (XPRA)

End date and time : 20081017002051

-


job entries for RDDEXCEL:-

-


Job started

Step 001 started (program RDDEXECL, variant , user ID DDIC)

All DB buffers of application server idesminda were synchronized

Error Building the ENH TreeObject Type:XHObject Name:/POSDW/COND_TRANSBAL

Function module CMMATGRP_O_WRITE_DOCUMENT deleted

Saved

ABAP/4 processor: CALL_FUNCTION_PARM_MISSING

Job cancelled

-


Along with that , it also giving an dump

-


An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_MISSING', was

not caught in

procedure "OSOA_UPLOAD" "(FORM)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

When calling the function module "RSA1_DSOURCE_ALL_D_GET", one of the

parameters

needed according to the interface description was not specified.

This parameter was "E_T_OHIECOM".

Kindly provide the solution

Regards

Vikas

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Chen

Thank you very much for the information.

I could able to resolve my issue by going through this forum:

Ravali

Former Member
0 Kudos

Hi

XPRA_EXECUTION terminates due to the following reasons:

○ TP_INTERFACE_FAILURE: The tp interface could not be called.

○ TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.

○ TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, read the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.

○ CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, read the SLOG log file.

○ CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.

For more details on this,please refer to the link :

http://help.sap.com/erp2005_ehp_04/helpdata/EN/7e/c6c2ad98a711d2b429006094b9ea64/frameset.htm

Alternately, you have to follow the following steps:

unlock the shadow instance (cd /usr/sap/put/bin && ./SAPup unlockshd)

logon as DDIC

copy DDIC to a different user

logon with the other user

start transaction SE06 and make the system "changable"

start transaction OSS1 -> Technical settings - Change - Save

use SNOTE

Apply SAP Note 1153235.

Regards

Chen

Former Member
0 Kudos

Hi

I am getting the same issue. I am upgrading BW 3.1C to BI 7.00

Were you able to resolve it? If yes, could you tell me how you did it?

I am unable to figure it out

Thanks