Support Package Apply

hi,
   To get the TDS certificate in a new format (funvtionality) we have to apply new support package.
   My system is ECC-6.0 & SPAM/SAINT version is 7.00/0023.
   So i applied SPAM/SAINT 7.00/0034. & it was succesed & after that when appply Basis SAPKB70012
   it was succesfully by when i again execute T-code SPAM it is showing Error in ABAP_GENRATION
Can anybody suggest me.
Thanks in advance
Regards
Manoj

hi,
   thanks for respons. i went to SE38-->RSSPAM10 i got this report
                                SPAM                                   SAINT
     Name       Update        Test      Standard     Downt.min.        Test      Standard     Downt.min.
1 PROLOGUE         X         X         X         X         X         X         X
2 CHECK_REQUIREMENTS         X         X         X         X         X         X         X
3 DISASSEMBLE         X         X         X         X         X         X         X
4 CREATE_COMPONENTS                             X         X         X
5 ADD_TO_BUFFER         X         X         X         X         X         X         X
6 MODIFY_BUFFER         X         X         X         X         X         X         X
7 ADD_SYNCMARKS                                  X         X
8 IMPORT_OBJECT_LIST         X         X         X         X         X         X         X
9 OBJECTS_LOCKED_?         X         X         X         X         X         X         X
10 TEST_IMPORT         X         X         X         X         X         X         X
11 ADDON_CONFLICTS_?              X         X         X         X         X         X
12 OPTIMIZE_OBJLISTS
13 SCHEDULE_RDDIMPDP         X              X         X              X         X
14 CREATE_VERS_BEFORE                   X         X              X         X
15 SPDD_SPAU_CHECK              X         X         X         X         X         X
16 DDIC_IMPORT                   X         X              X         X
17 AUTO_MOD_SPDD                   X         X              X         X
18 RUN_SPDD_?                   X         X              X         X
19 LOCK_EU                        X                   X
20 INACTIVE_IMPORT                        X                   X
21 DDIC_ACTIVATION                   X         X              X         X
22 IMPORT_PROPER         X              X         X              X         X
23 PREPARE_XPRA                   X         X              X         X
24 UNLOCK_EU                        X                   X
25 AUTO_MOD_SPAU                   X         X              X         X
26 XPRA_EXECUTION                   X         X              X         X
27 ABAP_GENERATION                   X         X              X         X
28 RUN_SPAU_?              X         X         X         X         X         X
29 CLEAR_OLD_REPORTS                        X                   X
30 EPILOGUE         X         X         X         X         X         X         X

Similar Messages

InfoObjects Key disappeared after BW support packages applied

Hi.
We have a serious problem, after we applied BW support packages (7.0110) all our infoobjects that are created as text only, no master data, are only displaying the text. The objects key is empty. Do anybody have a solution for this?
Koos.

Hi.
We have found a work around for the problerm for know and here it is:
5.1.3 Optimizing detail object syntaxFor queries on BI universes that include only the key and medium name detail objects of adimension, it is possible to modify the generated syntax of the objects to improve queryperformance, due to some internal details of the OLAP BAPI interface.To modify the syntax:
1.Open the universe in Designer.
2.Double click the key detail object you want to modify.
3.In the Select text box on the "Definition" tab of the "Edit Properties" dialog box, changethe syntax to refer to the NAME attribute of the SAP characteristic.For example, for the objectL01 Customer Key , change the generated select syntax:[Z_CUSTOM].[LEVEL01].[[2Z_CUSTOM]].[Value] to refer to the NAME attribute:[Z_CUSTOM].[LEVEL01].[NAME]4.ClickOKto save the changes.5.Follow the same steps for the name object. Change the syntax to refer to theDESCRIPTION attribute of the SAP characteristic.

Error in the phase IMPORT_PROPER while applying support packages

Dear All,
I am on ECC 6.0(ABAP+JAVA) SR2, SUSE Linux 10 SP1, DB2.
I have successfully applied the kernel patch and started applying the support packages, i have successfully completed applying the ABAP, Basis, BW, HR and other related patches, but i am not sure why i am stuck at the import_proper phase when applying the SAP_APPL patches (SAPKH60008 and SAPKH60009 both in the same queue) and my tp log is as follows
========================================================================================================
START imp all              SCD        20081229080538              DDIC         sealcpro 20081229080537
INFO: event SAP_IMPORT_START triggered successfully
INFO TBATG CONVERSION OF SCD N      not needed                  DDIC         sealcpro 20081229080537
START tp_getprots          SCD P      20081229080539              DDIC         sealcpro 20081229080537
2EETP000 sap_dext called with msgnr "1":
2EETP000      db call info
2EETP000 function:   db_setget
2EETP000 fcode:      RT_SETB (65535)
2EETP000 tabname:    TRBAT
2EETP000 len (char): 0
2EETP000 key:
2EETP000 retcode:    1
1AETP000 exit in function texitnow
ERROR: EXIT(16) -> process ID is: 5319
STOP imp all              SCD   0016 20081229080602              DDIC         sealcpro 20081229080537
=========================================================================================================
And also when i look at the Support package import logs they show that
TEST IMPORT
Import ABAP Dictionary Objects and
ABAP Dictionary Activation phases ended with return code 4
But i dont think this can give any problem.
I have tried to import from the phase where it stopped, but all of a sudden i get disconnected from SAP and get an error message saying that NO CONNECTION TO THE DATABASE, then when i check for the processes for dw and db2 there are process already running.
I had to start SAP and only then i was able to connect to the SERVER again.
Can you please help me on this..
For any more information plz let me know
Thanks and regards
Hunky

Dear Balaji,
Thank you very much for the reply...
I deleted the import request in the STMS and wi ran the RDDIMPDP and RDDMNTAB reports and restart the SPAM, but this time the SPAM immediately stopped, but i am still connected to the system and the error which i got earlier (database connection error ) is now not occuring.
But otherwise also i noticed that i get the following ABAP Dump while this error is triggering
===================================================================
DBIF_REPO_INTERNAL_ERROR
Internal error when accessing program "CX_SY_OPEN_SQL_DB=============CP ".
An unspecified internal error occurred in the SAP-internal
database interface.
For further analysis the SAP system log should be examined
(transaction SM21).
Check the entries in the developer trace of the relevant work process
(transaction ST11).
Attempted to access component "LOAD" of program
"CX_SY_OPEN_SQL_DB=============CP ".
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:
"DBIF_REPO_INTERNAL_ERROR" " "
"SAPLSTPA" or " "
==========================================================================
Based on this error i searched few notes and got the below results 309583 and 132383 but these are not for my release.
So i request you to kindly help me on this as i am running out of time in delivering my server.
Waiting for all the valuble replies
Thank you in advance
Regards
Hunky

Applying BASIS support package 14 on IDES (DB2 & Windows)

Hi all,
   I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSALC ".
at happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSALC " in include "LSALCU65
   " in
line 1:
"Function "SALC_INFO_GET_TREE" not found in Function Library."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Can anyone of you help me on this issue.
AWAITING REPLY
Thanks

>    I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
There are a few known issues with KB70014, those are documented in
Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Markus

Error in Applying Java support packages through JSPM

Hi All,
While Applying support packages, Package CAF 7.00 SP 13 is through an error
help required.
                   For detailed information see the log file of the Deploy Service.
07/12/05 21:55:26 - ***********************************************************
Dec 5, 2007 9:55:26 PM   Info: End of log messages of the target system.
Dec 5, 2007 9:55:26 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 5, 2007 9:55:26 PM   Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0', grouped by software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 5, 2007 9:55:26 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:28 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:28 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 5, 2007 9:55:28 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0' : aborted
Please, look at error logs above for more information!
Dec 5, 2007 9:55:28 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:30 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:30 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 5, 2007 9:55:30 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0':
No further description found.
Dec 5, 2007 9:55:30 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:32 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:32 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 5, 2007 9:55:32 PM   Error: -
At least one of the Deployments failed -
Regards,
Prashant.

Hello Prashant.
Check this supporting SAP note 1010640. It will solve your problem.
This is typical problem when you upgrade from < SP8 to higher version.
You need to Undeploy the CAF components from the system using SDM first and then reply the patches from JSPM.
It should go with out errors.
Let us know if this worked.
*Reward points for helpful answer.
Regards,
Prashant P.

Syntax Error while applying support package stack 8

I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors         SYNTAX_ERROR
Date and Time          23.07.2009 14:09:27
Short text
     Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
     Error in the ABAP application program.
     The current ABAP program "SAPLSCR2" had to be interrupted because it con
     a statement that cannot be executed.
     In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
      program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
     errors occur:
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
     Author and last person to change the include are:
     Author "SAP "
     Last changer "SAP "
Error analysis
     The following syntax error was found in the program
      CL_DYNPRO_PROPERTY_BAG========CP :
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
Trigger Location of Runtime Error
     Program                                 SAPLSCR2
     Include                                 LSCR2U47
     Row                                     31
     Module type                             (FUNCTION)
     Module Name                             RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *"     REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *"     REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *"     REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *"     REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *"     REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *"     REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *"     REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16       l_prop_list type prop_list,
17       l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23   clear l_prop_list.
24   clear l_prop.
25   l_prop-name   = sprop_c_tag_textfield_name.
26   l_prop-syntax = sprop_c_syntax_content .
27   l_prop-value = p_textfield.
28   append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>>   call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32     exporting
33       prop_list = l_prop_list
34     importing
35       properties = l_string.
36 * Property-Eintrag zusammensetzen
37   clear l_prop.
38   l_prop-name   = sprop_c_tag_textfield.
39   l_prop-type   = sprop_c_type_string.
40   l_prop-syntax = sprop_c_syntax_content .
41   l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43   read table p_prop_list transporting no fields
44       with key name = l_prop-name.
45   if sy-subrc = 0.
46     modify p_prop_list index sy-tabix
47         from l_prop.
48   else.
49     append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.

Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu

Error while applying support packages

Hi,
I was applying support packges for NW 7.0 EHP2 for the components SAP BASIS/ABAP/PI BASIS & BW, the support package level was 02, I have downloaded 03,04,05,06 for all the above four components. While updating spam/saint update I got the above error, displayed below. But even while applying support packages I got a list of errrors.
1.
Category: Abap programming error
Runtime error: call_function_parm_unknown
CX_SY_DYN_CALL_PARAM_NOT_FOUND
abap program: RSSPAM07
Function parameter "IV_IMP_SCENARIO" in unknown
this first error displayed after applying SPAM/SAINT update.
2. The import was stopped, since an error occured during the phase IMPORT_PROPER, which the support package Manager is unable to resolve without your input
The following details help you to analyse the problem:
Error in phase : IMPROT_PROPER
Reason for error:
Return code:
Error Message:
Please provide any solution as soon as possible....

The details of SLOG
START CMDIMPORT            NG1 L      20120227162812              SHABZ        BasisTrn3 20120227162811973
STOP CMDIMPORT            NG1 L      20120227162813              SHABZ        BasisTrn3 20120227162811973
START imp all              NG1        20120227162821              SHABZ        BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_START triggered successfully
START DD IMPORT            NG1 H      20120227162822              SHABZ        BasisTrn3 20120227162821661
STOP DD IMPORT            NG1 H      20120227162839              SHABZ        BasisTrn3 20120227162821661
START DD ACTIVATION        NG1 A      20120227162839              SHABZ        BasisTrn3 20120227162821661
START tp_getprots          NG1 J      20120227162839              SHABZ        BasisTrn3 20120227162821661
STOP tp_getprots          NG1 J      20120227162925              SHABZ        BasisTrn3 20120227162821661
STOP DD ACTIVATION        NG1 A      20120227162925              SHABZ        BasisTrn3 20120227162821661
START DISTRIBUTION OF DD-O NG1 S      20120227162925              SHABZ        BasisTrn3 20120227162821661
START tp_getprots          NG1 S      20120227162925              SHABZ        BasisTrn3 20120227162821661
STOP tp_getprots          NG1 S      20120227162929              SHABZ        BasisTrn3 20120227162821661
STOP DISTRIBUTION OF DD-O NG1 S      20120227162929              SHABZ        BasisTrn3 20120227162821661
INFO TBATG CONVERSION OF NG1 N      not needed                  SHABZ        BasisTrn3 20120227162821661
START MOVE NAMETABS        NG1 6      20120227162929              SHABZ        BasisTrn3 20120227162821661
START tp_getprots          NG1 P      20120227162929              SHABZ        BasisTrn3 20120227162821661
STOP tp_getprots          NG1 P      20120227162935              SHABZ        BasisTrn3 20120227162821661
STOP MOVE NAMETABS        NG1 6      20120227162936              SHABZ        BasisTrn3 20120227162821661
START MAIN IMPORT          NG1 I      20120227162936              SHABZ        BasisTrn3 20120227162821661
STOP MAIN IMPORT          NG1 I      20120227163023              SHABZ        BasisTrn3 20120227162821661
START TBATG CREATION OF EN NG1 n      20120227163024              SHABZ        BasisTrn3 20120227162821661
START tp_getprots          NG1 Y      20120227163024              SHABZ        BasisTrn3 20120227162821661
STOP tp_getprots          NG1 Y      20120227163034              SHABZ        BasisTrn3 20120227162821661
STOP TBATG CREATION OF EN NG1 n      20120227163034              SHABZ        BasisTrn3 20120227162821661
START EXECUTION OF REPORTS NG1 R      20120227163035              SHABZ        BasisTrn3 20120227162821661
START tp_getprots          NG1 R      20120227163035              SHABZ        BasisTrn3 20120227162821661
STOP tp_getprots          NG1 R      20120227163202              SHABZ        BasisTrn3 20120227162821661
STOP EXECUTION OF REPORTS NG1 R      20120227163202              SHABZ        BasisTrn3 20120227162821661
INFO EXECUTION OF STANDAR NG1 9      not needed                  SHABZ        BasisTrn3 20120227162821661
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all              NG1   0004 20120227163203              SHABZ        BasisTrn3 20120227162821661
START CMDIMPORT            NG1 L      20120227164418              SHABZ        BasisTrn3 20120227164416991
STOP CMDIMPORT            NG1 L      20120227164454              SHABZ        BasisTrn3 20120227164416991
START DD IMPORT            NG1 H      20120227165608              SHABZ        BasisTrn3 20120227165607479
STOP DD IMPORT            NG1 H      20120227170309              SHABZ        BasisTrn3 20120227165607479
START DD ACTIVATION        NG1 A      20120227170313              SHABZ        BasisTrn3
START tp_getprots          NG1 J      20120227170313              SHABZ        BasisTrn3
STOP tp_getprots          NG1 J      20120227171206              SHABZ        BasisTrn3
STOP DD ACTIVATION        NG1 A      20120227171206              SHABZ        BasisTrn3
START imp all              NG1        20120227171208              SHABZ        BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O NG1 S      20120227171208              SHABZ        BasisTrn3 20120227171207614
START tp_getprots          NG1 S      20120227171208              SHABZ        BasisTrn3 20120227171207614
STOP tp_getprots          NG1 S      20120227171303              SHABZ        BasisTrn3 20120227171207614
STOP DISTRIBUTION OF DD-O NG1 S      20120227171304              SHABZ        BasisTrn3 20120227171207614
START TBATG CONVERSION OF NG1 N      20120227171304              SHABZ        BasisTrn3 20120227171207614
START tp_getprots          NG1 N      20120227171304              SHABZ        BasisTrn3 20120227171207614
STOP tp_getprots          NG1 N      20120227171307              SHABZ        BasisTrn3 20120227171207614
STOP TBATG CONVERSION OF NG1 N      20120227171307              SHABZ        BasisTrn3 20120227171207614
START MOVE NAMETABS        NG1 6      20120227171307              SHABZ        BasisTrn3 20120227171207614
START tp_getprots          NG1 P      20120227171308              SHABZ        BasisTrn3 20120227171207614
STOP tp_getprots          NG1 P      20120227171755              SHABZ        BasisTrn3 20120227171207614
STOP MOVE NAMETABS        NG1 6      20120227171755              SHABZ        BasisTrn3 20120227171207614
START MAIN IMPORT          NG1 I      20120227171756              SHABZ        BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP MAIN IMPORT          NG1 I      20120227195335              SHABZ        BasisTrn3 20120227171207614
START TBATG CREATION OF EN NG1 n      20120227195335              SHABZ        BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
START tp_getprots          NG1 Y      20120227195335              SHABZ        BasisTrn3 20120227171207614
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
STOP tp_getprots          NG1 Y      20120227195521              SHABZ        BasisTrn3 20120227171207614
STOP TBATG CREATION OF EN NG1 n      20120227195521              SHABZ        BasisTrn3 20120227171207614
INFO EXECUTION OF STANDAR NG1 9      not needed                  SHABZ        BasisTrn3 20120227171207614
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all              NG1   0903 20120227195522              SHABZ        BasisTrn3 20120227171207614

DDIC_ACTIVATION ERROR WHILE APPLYING SUPPORT PACKAGE SAPKW35020 IN ECC5.0

Hi Gurus,
I am getting error DDIC_ACTIVATION while applying support package(BW) SAPKW35020 in ECC5.0 with MSSQL database in Windows server.
I am not able to reset the queue, when i tried to reset the queue the system prompting that " cannot reset queue while DDIC_ACTIVATION" phase".
Can you please help to reset the queue and implementing this support package.
Thank you,
Regards,
Ganesh

Paste the SPAM log here.
Regards,
Nick Loy

Error in "Test IMPORT" during applying BASIS Support Package

Hi All,
I'm applying basis support package from SAPKB70014 to SAPKB70018,
now it hangs in Import phase: TEST_IMPORT, there maybe something wrong with the import object.
For detail screenshots, please kindly have a look at URL: http://nickfiles.150m.com/Question_1.html
And for the detail import log, please have a look at http://nickfiles.150m.com/SAPPB70015.html.
I think the root cause is located in:
2EETW165 Function "TMW_TAOAGENT (TMW_TAOINTERFACE|01)" does not fit into the existing function group "(TMW_CLIENT_INTERFACES|06)".
2 ETW167 Please transport the whole function group.
But I do not know how to solve it. Could anyone help me?
Thank you very much.
Best regards,
Nick

Hi Nick,
This is the solution to your Issue..
Note 1156706 - Function TMW_TAOAGENT (TMW_TAOINTERFACE 01) does not fit...
Other SAPnote you can read .. for your help..
Note 42379 - SPAM aborts at step TEST_IMPORT
Note 1092979 - TMW_TAOAGENT: Repairing function group after SAPKB70013
Hope it will solve your issue ....
All teh best !!

Support Package SAPKB71101 hangs while applying

Hi,
I am applying basis support package SAPKB71101, it is getting hanged in Main Import. I was trying to import from last 4 days. But still it is hanged in the Main Import only. When i try to check the log in Slog, i am getting the warning as /usr/sap/trans/tmp/SAPKKB711001.PI7 is already in use (1890), I'm waiting 1 sec (20100325184152). My name: Pid 26022.
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (1850), I'm waiting 3 sec (20100325183950). My name: pid 26022
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (230), I'm waiting 5 sec (20100325184000). My name: pid 8531 o
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (830), I'm waiting 5 sec (20100325184001). My name: pid 11084
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (1860), I'm waiting 1 sec (20100325184022). My name: pid 26022
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (240), I'm waiting 4 sec (20100325184031). My name: pid 8531 o
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (840), I'm waiting 3 sec (20100325184031). My name: pid 11084
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (1870), I'm waiting 3 sec (20100325184054). My name: pid 26022
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (850), I'm waiting 1 sec (20100325184056). My name: pid 11084
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (250), I'm waiting 4 sec (20100325184100). My name: pid 8531 o
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (1880), I'm waiting 4 sec (20100325184119). My name: pid 26022
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (860), I'm waiting 5 sec (20100325184125). My name: pid 11084
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (260), I'm waiting 5 sec (20100325184131). My name: pid 8531 o
WARNING: /usr/sap/trans/tmp/SAPKKB71101.PI7 is already in use (1890), I'm waiting 1 sec (20100325184152). My name: pid 26022
I am getting this warning continously. Please suggest me the solution.
Regards
Karunakar

Hi,
Could you check if a (tp or R3trans) still exists for the same PID.
If this process does, exist, you can
1. wait for a time when no normal transports (STMS, tp, ...) run.
2. wait for a time when nothing is done in SPAM or SAINT.
3. also no client exports or imports should be done, so no tp or R3trans process should run on the System.
4. If then still tp or R3trans processes run, kill the R3trans processes at Operating system level.
5. wait a bit and then also the tp processes should end with an error.
6. check again tht no tp and no R3trans process exists on the server.
7. Go to /usr/sap/trans/tmp and check whether there is file names SAPKKB71101.PI7.
rename the file SAPKKB71101.PI7 to SAPKKB71101.PI7.old
The system will create a file again in DIR_TRANS/tmp when new TP process is trigger later.
Read note #12746.
Best Regards
Niraj

Best way to apply Support Packages to Solution Manager

We have a single instance dual stack for SOLMAN 4 running. I want to apply Suppot packages, I need some suggestion what would be the best way to do this, the way I am thinking to proceed for this is -
1. Do kernel and igs upgrade thru JSPM
2. Apply ABAP Support packages and then,
3. apply JAVA support packages
Is it possible to apply ABAP support packages with JSPM?
Any suggestion would be helpful

Patch your abap stack first then the java...
No, its not possible to pacth abap with JSPM (JAVA Support Package Manager)
Regards
Juan

How to find and apply new Support Packages?

Hi to everyone.
The system is SAP R/3 Enterprise (may 4.7 ext2?)
The spam version is 6.20/0020
i have to update the support packages, so i went on https://websmp107.sap-ag.de/swdc, but i dont know what SP i have to download.
the situation is (so i have to update all of them?):
SAP_BASIS     620     0059     SAPKB62059
SAP_ABA     620     0058     SAPKA62058
SAP_APPL     470     0018     SAPKH47018
SAP_HR     470     0058     SAPKE47058
EA-IPPE     200     0004     SAPKGPIB04     .
PI     2003_1_470     0002     SAPKIPZH52
PI_BASIS     2003_1_620     0002     SAPKIPYH52
ST-PI     2005_1_620     0002     SAPKITLQG2
EA-HR     200     0015     SAPKGPHB15
LSO     200     0018     SAPK-200PIINLSO

For eg. for 4.6C you have upto 52 in BASIS ,ABAP,and cross application components.
you download 43..44..52 and using SPAM you can upload from front end or you can uncar them on the App.server.
However, during the course of implementing patches, during the SPDD and SPAU phase system gives the option to retain the changes that are made to standard programs / objects / tables etc or to reset the objects to SAP standard objects. It is during these changes only that the functional consultant has to study the program/changes which are done and the impact of the changes.So when you come through this SPDD or SPAU phase you have to make sure from your ABAPers and functional consultants regarding whether to reset all to original or retain the changes.This is crucial otherwise you will impair your business unknowingly.
Click on the info button beside the support pack name and see the dependencies.
The order of applying patches will be BASIS,ABAP,Cross application components,HR etc...
And finally it's not the case that we should go for applying a support pack because it's available at SAP market place.

MAM Not Working After Applying Support Package

We have been lived with MAM 2.5 with SP16 for almost a year now. We recently applied support package 19 for ABAP and J2EE stacks but MAM stopped working right after that. To fix the problem we had to do the following steps:
1. Disable all SyncBO
2. Regenate all SyncBO
3. Run Replicate Database
4. Enable all SyncBO
5. Delete MAM 2.5 client by WebConsole for all PDA (over 100 devices)
6. Re-Assign MAM 2.5 client back to PDA from WebConsole
My question is do we have to perform those steps above every time we are applying new support package? If it is a case, it's very time consuming because we have to manually perform step 5-6 for every users.
Does anyone have seen or experience this scenario before? Your comment is highly appreciated.
Regards,
Dai Ly

Hi Karthik,
Let me clarify on "Not working"
It showned synchrozation successuffly but no data transfer between client and middleware and vs. For instance, the user never receive any new work orders, or their times never got transfered back to R/3. Even though, there is no error on the client.
It appear that step 1-4 are required otherwise, you get ABAP Runtime error (using ST22):
Runtime Error          CALL_FUNCTION_NOT_FOUND
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          02/07/2007 08:12:27
After we performed step 1-4 but there were data transfer between client and R/3. The only way to get it working, we had to delete client and re-assign MAM 2.5 back to each users.
No, we didn't apply client patch SP19. We are still using SP16.
As we speak, everything is working because we had to re-assign MAM 2.5 for every users. but I hope we don't have to do this next time we apply another Support Package.
Thanks.
Dai Ly

How to apply java support packages.

hi all,
i applied support packages for 4.7EE but i dont know how to apply java support packages.
can anyone explain about how to apply java support package for netweaver s??
from scratch anyone can explain.
regards
vijay

Hello Vijay ,
Java Support packs can be installed without using SDM also if you are on NW2004.
Process:
Eg SP18
Download the following DVDs
1. WebAS 6.40 SP18(Part 1/4): SAP Installer
2. WebAS 6.40 SP18(Part 2/4): SAPInst Control File for Oracl
3. WebAS 6.40 SP18(Part 3/4): OS Depend. parts of Java RuntiA
4. WebAS 6.40 SP18(Part 4/4): OS Indep. Parts of Java Runtime
Uncar each of them in the sequence
1,4,3,2
Once u uncr then u will get some more uncarred files
eg D:\sapinst\J2EE-RUNT-CD\SCS\NT\I386\SCS.SAR uncar it into run directory : DIR_CT_RUN ( D:\usr\sap\SRX\SYS\exe\runU)
Note: The value of DIR_CT_RUN can be found In Profile SRX_SCS01_B3BPH1W)
Run SAPINST
Note:Give RFC user as 000 DDIC
Java Support packs can be installed using JSPM if you are on NW2004s
1)Download SP Stack or SP
2)Copy the SCA files to /usr/sap/trans/EPS/in
3)Execute the JSPM go.bat from \sapmnt\SID\DVEBMGSXX\j2ee\JSPM
4) Provide SDM Password
5 ) Select the Traget SP level .
6 ) Deploy.
Also, you can find the current SP Level in http://localhost:5<instance numeber>00 and then system information.
Regards ,
Santosh Karadkar <a href="https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=3819594">Click here for further info</a>

DDIC_ACTIVATION ERROR WHILW APPLYING SUPPORT PACKAGES

Hi all,
While applying support package(KB62019),i got error(DDIC_Activation)..
How to resolve it?
Thanks in advance.

Hi,
Which support package are you applying ? Have a look at these notes: 782140 and 447925.
Search for SAPKB62019 in this note and you will get a solution to that. The note refers to some more notes. Please follow the instuctions in the note carefully.
Cheers,
Sunil
PS: Reward points for helpful answers.

Support Package Apply

Similar Messages

Maybe you are looking for