DDIC_ACTIVATION ERROR SP queue SAPK-70103INPIBASIS-SAPKA70104

[Former Member]

Hello all,

I am facing this error during Queue Import

- Error in phase: DDIC_ACTIVATION

- Reason for error: TP_STEP_FAILURE

- Return code: 0008

- Error message: OCS Package SAPK-70103INPIBASIS, tp step A,

return code 0008

i have a queue of following patches

SAPK-70103INPIBASIS

SAPK-70104INPIBASIS

SAPKB70103

SAPKB70104

SAPKA70103

SAPKA70104

in the transport log file its showing following entries in RED color

Table UMGSIUUC1 could not be activated

(W- Flag: 'Incorrect enhancement category' could not be updated )

Field KEY: Component type or domain used not active or does not exist

Table /1PYXXFO/SAP_PAYSLIP_____L0001 could not be activated

Field KEY: Component type or domain used not active or does not exist

Table /1PYXXFO/SAP_PAYSLIP_____L0020 could not be activated

Function EMINT_GET_NEW_CENTRAL_NEGLIST (S4EM|01) does not fit into the existing function group ((S2EM|10))

I tried to activate them manually but still the same error.

Is it something related to RSA7 (BW delta queue Maintenance)? As a step in deleting setup-up table data i deleted all the BW delta queue maintenance as we are not using it anymore. We built the system from a export image of system which was used to update BW system using BW extractions.

Can any body please shed some light on the same. i allready tried these notes nut in vain.

822379

556962

556972

here is the extract from SLOG file

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165213 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165230 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165231 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165239 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165707 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165713 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165730 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165731 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090527165739 :

WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

STOP tp_getprots <SID> Q 20090527165803 <USERNAME> <HOSTNAME> 20090527134327126

STOP INFORM SAP-SYSTEM OF <SID> Q 20090527165803 <USERNAME> <HOSTNAME> 20090527134327126

STOP tp_getprots <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477

START INFORM SAP-SYSTEM OF <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477

START tp_getprots <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477

ERROR SAPK-70103INPIBASIS <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPK-70104INPIBASIS <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70103 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> Q 20090527170454 <USERNAME> <HOSTNAME> 20090527140355477

STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170454 <USERNAME> <HOSTNAME> 20090527140355477

ERROR SAPKA70104 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70103 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70104 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> J 20090527170457 <USERNAME> <HOSTNAME>

STOP DD ACTIVATION <SID> A 20090527170457 <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224

START INFORM SAP-SYSTEM OF <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224

START tp_getprots <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224

STOP tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847

START INFORM SAP-SYSTEM OF <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847

START tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847

STOP tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135646224

STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135646224

STOP tp_getprots <SID> Q 20090527170502 <USERNAME> <HOSTNAME> 20090527135046847

STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170502 <USERNAME> <HOSTNAME> 20090527135046847

thanks

Mani

[Former Member]

Hi,

We had a similar situation and I feel the reply posted by Mirko Edling on

Posted: Jun 5, 2009 9:04 PM

is the proposed and recommended solution for the error

1EEDO519X"Table" "UMGSIUUC1" could not be activated

Regards,

Senthil

[Former Member]

I had to delete some HR forms related structure manually n then it worked fine.

[Former Member]

How and witch HR reports?

Imre

[Former Member]

these were the structure deleted from system afterwards patches were installed successfully.

/1PYXXFO/SAP_PAYSLIP_____L0001

/1PYXXFO/SAP_PAYSLIP_____T0001

/1PYXXFO/SAP_PAYSLIP

/1PYXXFO/SAP_PAYSLIP_____L0020

/1PYXXFO/SAP_PAYSLIP_____T0020

I don't know if i answered your question? let me know.

Mani

[Former Member]

Thank you. This solution working fine

I hope nobody use the PAYSLIP HR form...

Imre

Edited by: Imre Ihring on Aug 6, 2009 8:51 PM

[Former Member]

Even if somebody use it you just need to re-generate the program for HR PAYSLIP forms and it will work fine after generation.

Thats what i heard from SAP support.

Enjoy.

Mani

[Former Member]

Hi Imre

I think I have the same issue, could you please tell me how did you manage to delete these structures and where did you see them, i cant seem to find them anywhere.

Thanks,

Nadim

[Former Member]

Hello Nadim, u can find them in SE11. See in data element structures.

Mandeep

[sunny_pahuja2]

Hi Mani,

Could you please tell me source stak and target stack ?

Also, I think you are doing EHP upgrade. If you are using EHPI tool then when you are getting this error, you will get a option to accept non-sevre errors and proceed. Try to use this option and proceed further. If you are still facing this problem, please attach logs *.ECO.

Thanks

Sunny

Edited by: Sunny Pahuja on May 29, 2009 12:19 AM

[Former Member]

We are on SP 2 right now on NW 701 and ECC 6 EHP 4 and i am trying to install target SP 4.

Mani

[sunny_pahuja2]

Hi Mani,

Have you tried the option which I have suggested ?

Thanks

Sunny

[Former Member]

Well there is no other option is just halting the operation no 'CONTINUE' or 'SKIP' Button. i dont know what is *.ECO file but i have *.<SID> file.

i executed RDDNEWPP as suggested by some people using user DDIC in client 000 but i dont know what to do next.

I am updating my Support Package not implementing Enhancement package 4, i alllready have EHP 4 ECC^ system in place, i want to implement TREX EMBEDDED SEARCH functionality into our system and that require Support package 4 for some functionality. that what i am stuck into.

I imlpemented note 71353, 26966 and note 11677 but no luck.

Can i know if we can import transport queue from OS level on Windows plateform.

but now i am getting different error in SLOG file.

SLOGXXXX.<SID> log is

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090528181849 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090528182349 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090528182849 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090528183349 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System <SID>. Warning. 20090528183850 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

STOP tp_getprots <SID> J 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853

STOP DD ACTIVATION <SID> A 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853

START DISTRIBUTION OF DD-O <SID> S 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> S 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> S 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853

STOP DISTRIBUTION OF DD-O <SID> S 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853

START TBATG CONVERSION OF <SID> N 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> N 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> N 20090528184730 <USERNAME> <HOSTNAME> 20090528173755853

STOP TBATG CONVERSION OF <SID> N 20090528184730 <USERNAME> <HOSTNAME> 20090528173755853

START MOVE NAMETABS <SID> 6 20090528184731 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> P 20090528184731 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> P 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853

STOP MOVE NAMETABS <SID> 6 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853

START MAIN IMPORT <SID> I 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853

STOP MAIN IMPORT <SID> I 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853

START TBATG CREATION OF EN <SID> n 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> Y 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> Y 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853

STOP TBATG CREATION OF EN <SID> n 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853

START SET VERSION FLAGS <SID> V 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> V 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> V 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853

STOP SET VERSION FLAGS <SID> V 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853

START EXECUTION OF REPORTS <SID> R 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> R 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> R 20090528191940 <USERNAME> <HOSTNAME> 20090528173755853

STOP EXECUTION OF REPORTS <SID> R 20090528191940 <USERNAME> <HOSTNAME> 20090528173755853

START GENERATION OF REPORT <SID> G 20090528191941 <USERNAME> <HOSTNAME> 20090528173755853

START tp_getprots <SID> G 20090528191941 <USERNAME> <HOSTNAME> 20090528173755853

STOP tp_getprots <SID> G 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853

STOP GENERATION OF REPORT <SID> G 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853

STOP imp single <SID> 0004 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853

START DD ACTIVATION <SID> A 20090528235747 <USERNAME> <HOSTNAME>

START tp_getprots <SID> J 20090528235747 <USERNAME> <HOSTNAME>

ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70103 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70104 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70103 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70104 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> J 20090529000423 <USERNAME> <HOSTNAME>

STOP DD ACTIVATION <SID> A 20090529000423 <USERNAME> <HOSTNAME>

START DD ACTIVATION <SID> A 20090529105521 <USERNAME> <HOSTNAME>

START tp_getprots <SID> J 20090529105521 <USERNAME> <HOSTNAME>

ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70103 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70104 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70103 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70104 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> J 20090529110127 <USERNAME> <HOSTNAME>

STOP DD ACTIVATION <SID> A 20090529110127 <USERNAME> <HOSTNAME>

START DD ACTIVATION <SID> A 20090529121729 <USERNAME> <HOSTNAME>

START tp_getprots <SID> J 20090529121729 <USERNAME> <HOSTNAME>

ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70103 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKA70104 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70103 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

ERROR SAPKB70104 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>

STOP tp_getprots <SID> J 20090529122905 <USERNAME> <HOSTNAME>

Mandeep

[sunny_pahuja2]

Hi Mani,

As per your logs i have two observstions

1) Check system is up.

2) WARNING: Background job RDDIMPDP could not be started or terminated abnormally. Please check that the R/3 system is running.

RDDIMPDP job is running or not.

Please check above and paste last two log files in your upgrade directory.

Thanks

Sunny

[Former Member]

Hi Mani,

i have the same error during the EHPi upgrade with package 3 and 4.

I found the solution:

Please implement note 1256384 with TX SNOTE into the shadow instance.

First you have to unlock the shadow instance and then you have to maintain the password for RFC destination SAPOSS again -> PW = cpic (PW in secure store is invalid).

After that you can implement the note with tx snote.

Then restart the phase ACT_UPG.

regards

Mirko

Edited by: Mirko Edling on Jun 5, 2009 9:04 PM

[Former Member]

Hi Mirko,

I have a similar problem and also need to adjust objects in the shadow instance.

The question is: how do you unlock the shadow instance as EHPi is not using SAPup or R3up?

Thx in advance,

Jérôme

[sunny_pahuja2]

Hi,

Please go to <upgrade directory>/EHPI/abap/bin...and use below command to unlock

./SAPup unlockshd <SID>

Thanks

Sunny

[Kathrin_Henkel]

Please donu2019t follow this hint, calling transaction SNOTE will not work during ACT_UPG

[Former Member]

seems to be some problem with RDDIMPDP job, reschedule it by running RDDNEWPP report and again continue SP

Note 71353 - Transports hang during background steps

Note 26966 - Background jobs do not start when transporting

358813