cancel
Showing results for 
Search instead for 
Did you mean: 

Error during import BI_CONT 353 on ERP ECC5.0 Platform

Former Member
0 Kudos

Hi There,

i have the same problem in the SAINT Queue during the import of S.P. "BI-Cont 3.5.3" on ERP ECC 5.0 Platform.

This the Status Log:

" The installation was stopped, since an error occurred during the phase

XPRA_EXECUTION, which the Add-On Installation Tool is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Continue in the queue display.

The following details help you to analyze the problem:

- Error in phase: XPRA_EXECUTION

- Reason for error: TP_STEP_FAILURE

- Return code: 0012

- Error message: OCS Package SAPKIBIFIZ, tp step R, return code

0012"

I read the previous posts and i tried to apply yours suggests on SPAU transaction but i did not succeded as well.

Thanks in advance for your collaboration.

Federica

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

It turns out that you must have SAP_BW 350 SP13 installed prior to upgrading the BI_CONT 353.

However, since SAINT is locked during XPRA_EXECUTION phase, you must import the note 844007 through SNOTE instead.

This note provides a fix that is now incorporated in SAP_BW 350 SP13.

-Raymond

Former Member
0 Kudos

Hi,

I am having the exact same problem and can't seem to find any relevant notes on this topic.

The error I have in the SAINT job log is:

2005.09.06 17:02:22 Job started

2005.09.06 17:02:22 Step 001 started (program RDDEXECL, variant , user ID DDIC)

2005.09.06 17:02:22 All DB buffers of application server homer were synchronized

2005.09.06 17:02:55 ABAP/4 processor: GETWA_NOT_ASSIGNED

2005.09.06 17:02:55 Job cancelled

I have tried to run RDDEXECL manually, and it comes back with a success.

Any help is appreciated.

Thanks,

Ray Tam

Former Member
0 Kudos

Hello Federica,

Please look at the job logs of the SAINT import, owned by user DDIC. The latest of them should be the one with the error in the XPRA execution phase. Hopefully you'll be able to determine the cause of the error and solve it using this error message.

Best regards,

Daniel