0008 error

Hi,
I am saving the 0008 infotye i m getting the entry in table T510 for the key 40 013 on 29.02.2008.
Pls let me know on this.
Thanks and Regards,
Revathi.

Hi revathi,
See i am not creating any wage types for capturing salary components, cause there are a lot of settings to be done for that to work.
Instead of the that in a custom IT i will create fields such as Basic, HRA, Traveling allow., Dearness Allow. etc. then the value will be entered against every heading such as Basic = 5000.
Now HRA is 40% of Basic so i will ask my ABAP'er to write a field validation as when basic is entered the HRA field is automatically calculated and displayed. Similarly i can get the gross and net salary by writing more field validations.
regards.

Similar Messages

HR_INFOTYPE_OPERATION 0008 Error

hi guys,
i am using HR_INFOTYPE_OPERATION FM to upload data at infotype 0008 (basic pay).
i get a short dump error with the following message:
Error analysis
    You cannot call a COMMIT WORK in a FORM not executed by the variants
    PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK until the commit of the
     calling program.
i did the nocommit = 'X' parameter for the FM, then COMMIT WORK later at the program.
dump still appears.
if i remove that parameter, and the COMMIT WORK as well, i still get the same dump.
if i assign nocommit = space or remove it at all, no dump happens, but IT0008 is not updated as well.
i tried my same code with other infotypes, with nocommit = 'X' and COMMIT WORK later in the program.
it works fine. no dumps.
it seems that i only get the dump at infotype 0008.
any ideas what is happening?
anyone had the same problem at infotype 0008?

Hi,
R u adopting the parameters in the following way.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
         INFTY            = '0008'
         NUMBER           = OLD_P0008-PERNR
         SUBTYPE          = OLD_P0008-SUBTY
         OBJECTID         = OLD_P0008-OBJPS
         LOCKINDICATOR    = OLD_P0008-SPRPS
         VALIDITYEND      = OLD_P0008-ENDDA
         VALIDITYBEGIN    = OLD_P0008-BEGDA
VALIDITYEND      = I0573-endda*
VALIDITYBEGIN    = I0573-begda*
         RECORDNUMBER     = OLD_P0008-SEQNR
         RECORD           = I0008
         OPERATION        = OPERN
         TCLAS            = 'A'
         DIALOG_MODE      = DIALOG_MODE
NOCOMMIT         =*
VIEW_IDENTIFIER =*
SECONDARY_RECORD =                             IMPORTING*
        RETURN           = BAPISUBRC
        KEY              = INFTY_KEY.
Thanks
Pavan

Infotype 0008 error

While creating reason for change in IT 0008 , showing abap runtime error when trying to save the description.

Good to see you after a long time
Can u let us know wht is the error you are getting........
and check with your ABAPER also ......
hope everything is fine from your side

Infotype 0008 error for Brazil

I am trying to run the confirmation ation for brazil employee, in the middle of the month.
but then infotype 8 is throwing error saying " Accorning to Law salary increase should begin on the 1st day of month."
the problem did not occur for other countries, though the confirguration is same. and Infotype 8 is in COP mode for CN- confirmation action
maybe someone might be having some idea about it.
Please do let me know.

Hi,
seems that local law prohibits mid-month salary changes.
I would ask local (brazilian) experts whether such a law indeed exists....
Wilfred.

Transport control program tp ended with error code 0008

Hi !
I trying to realize an export of client like that :
Source Client                     400
Target System:                    ASI
Copy Type                         Client Export
Profile                           SAP_RECO
Status                            Ended with Errors
User                              ST01051
Start on                          17.06.2009 / 17:41:00
Last Entry on                     18.06.2009 / 00:20:40
Transport Requests
- Client-Specific                 ASIKT00028
- Texts                           ASIKX00028
The export ended with this error :
Transport control program tp ended with error code 0008
Error when exporting request ASIKT00028 00:20:39
Program ended with error or warning, return code: F
What happen ?
If somebody can help me to solve this problem ?
Regards,
Johan

hai johan ,
of the return code is 008 then it is error,
what have u transported to target just chekc the log an du might find the error ,
just click the expand button of the error and u will get the detials what errror occured
may be some objects might be inactive just chekc once
m.a

Error message: OCS Package SAPK-603DDINEAAPPL, tp step A, return code 0008

Hi Experts,
I got an issue upgrading ECC 6.0 to EHP 4
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPK-603DDINEAAPPL,
tp step A, return
code 0008
This is the message log from SAINT of the SP:
Field SGTXT in table FILA_POINF is specified twice. Please check
Field ZUONR in table FILA_POINF is specified twice. Please check
Regards.

Dear Jorge,
How did you resolve this issue?
I encounter same error during EHP4 ECC IDES upgrade in phase SHADOW_IMPORT_INC
I repeated the step, currently still running.
Best Regards,
Jacco Raymakers

Playbook Appworld Install Error :[0008]

"If you have a list of apps where you see this issue please let me know and we'll look into it.
Michael Clewley
Senior Product Manager, BlackBerry Software
Research In Motion"
I'm getting the 0008 error with a few FREE apps.
HAM
aWallet
Frequency
Webmaster's HTML Editor
There were a few others but I've deleted them and don't remember the names.
Any idea on how to fix or get around this problem?? I've already tried a hard reset and a complete wipe and reinstall.

I made some space by removing some unused apps and the update installed with no problems.

Support package / add on import error in DB2 V9.1 / windows 2003 system

Hi
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
I have read some notes it may be due to "Row compression" and "Deffered table creation" option in DB2. Please help me in resolving this issue if it is DB2 related.
Regards,
Nallasivam.D

Hi,
Please find the real error message which I found in the same log file. This is a new installation.
System configuration details:
ERP 6.0 IDES SR3 + Windows 2003 enterprise server SP2 + DB2 V9.1 / FP5
BASIS and ABAP support pack level: (700) 13.
Error message:
3 ETP399 INDEX IN "IDS#BTABI"
3 ETP399 LONG IN "IDS#BTABD COMPRESS YES"
3 ETP399
2WETP000 02:53:26: Retcode 1: error in DDL statement for "/OSP/T_REPINFO                " - repeat
2EETP345 02:53:38: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#BTABD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/OSP/T_REPINFO
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:05: Retcode 1: error in DDL statement for "/SAPPO/CMP_ASG                " - repeat
2EETP345 02:54:17: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CMP_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:17: error in DDL, nametab for "/SAPPO/CMP_ASG" not activated
3 ETP399 IN "IDS#POOLD"
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:17: Retcode 1: error in DDL statement for "/SAPPO/CSCRN_HDR              " - repeat
2EETP345 02:54:29: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CSCRN_HDR
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:29: error in DDL, nametab for "/SAPPO/CSCRN_HDR" not activated
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:29: Retcode 1: error in DDL statement for "/SAPPO/F_ASG                  " - repeat
2EETP345 02:54:41: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/F_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:41: error in DDL, nametab for "/SAPPO/F_ASG" not activated
Regards,
Nallasivam.D

Error in Spam / saint update TP_STEP_FAILURE and DDIC_ACTIVATION

Dear All,
While updating spam/ saint update I am facing this error
Details of Error:
The installation was stopped, since an error occurred during the phase
DDIC_ACTIVATION, 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: DDIC_ACTIVATION
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0008
    -   Error message: tp step A, return code
        0008
Notes on phase DDIC_ACTIVATION
In this phase the system activates the imported Data Dictionary objects.
This phase may terminate for several reasons:
o   TP_INTERFACE_FAILURE: The system was unable to call the tp
     interface.
o   TP_FAILURE: The system was unable to execute the tp program. For
     more information, see the SLOG or ALOG log file.
o   TP_STEP_FAILURE: The system was unable to perform the tp step DDIC
    activation successfully. To see the cause of the problem in the
    activation log, choose Logs.
    If you import two or more OCS packages in one installation queue,
    and activate the Data Dictionary objects in the incorrect sequence,
    this can cause errors. In this case, the activation errors disappear
    if you repeat the activation run. To do this, choose Continue.
The Add-On Installation Tool requires that the Change and Transport
System (CTS) be configured correctly. For more detailed information,
read the online documentation available from Help -> SAP Library ->
mySAP Technology Components -> SAP Web Application Server -> BC Change
and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
Please help me
Thanks
Senthil

Hi,
i am having the same problem with SPAM
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPKA70012, tp step A, return code
0008
however i dont have the option to continue.. Please help
thanks

Upgrade erp6 to ehp3--- error ddic

im trying to upgrade ecc6 to ecc6 ehp3
i have import SAPK-603DHINSAPAPPL
and SAPK-603DHINEAAPPL
togther- and get error in the and of it/
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPK-603DDINEAAPPL, tp step "A",
return code 0008
i read note 822380
and after that 791984,1015068
1022755
but still cant find the cuese of thise error
in the log i find:
Error in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPK-603DDINEAAPPL, tp step "A",
return code 0008
indexes 001 and KEY for table PFO_GO_00IS have identical fields
need help here please
yossi:-)

There are some solutions given here. You can follow them
The Add-on installation terminated during phase DDIC_ACTIVATION
http://sapbasis2407.blogspot.com/2010/01/ecc6-ehp3-upgrade.html
Regards,
Subhash

BI Content add on installation error in IMPORT PROPER - tp step failure

Hi All,
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
Regards,
Nallasivam.D

Hi,
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301 -
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301 -
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
Regards,
Nallasivam.D

Error occured in the phase MOVE NAMETABS while updating patch.

Hi Gurus
When i implementing a SP15 to SP16 in a queue, i got the Dump.
Please help me in this issue.
The import was stopped, since an error occurred during the phase
   IMPORT_PROPER, which the Support Package Manager is unable to resolve
   without your input.
   After you have corrected the cause of the error, continue with the
   import by choosing Support Package -> Import queue from the initial
   screen of the Support Package Manager.
   The following details help you to analyze the problem:
       -   Error in phase: IMPORT_PROPER
       -   Reason for error: TP_STEP_FAILURE
       -   Return code: 0008
       -   Error message: OCS Package ALL, tp step "6", return code 0008
   Notes on phase IMPORT_PROPER
   In this phase repository objects and table entries are imported. This
   phase can terminate due to the following reasons:
   o   TP_INTERFACE_FAILURE: The tp interface could not be called.
   o   TP_FAILURE: The program tp could not be executed. For more
       information on this, see the SLOG or ALOG log file.
   o   TP_STEP_FAILURE: A tp step could not be executed. To find the cause
       of the error, see the appropriate log, such as the import log.
       If the cancelation message contains a tp step 6, N or S, the step in
       question is independent of the transport request. You can find these
       logs under the node Import steps not specific to transport request
       in the log overview.
       Alternatively, you can find these logs in the following files in the
       log directory of your transport directory (usually:
       /usr/sap/trans/log):
    -   tp Step 6: P<YY><MM><DD>.<SID>
    -   tp Step N: N<YY><MM><DD>.<SID>
    -   tp Step S: DS<YY><MM><DD>.<SID>
    You can display these files using the report RSPUTPRT or by calling
    transaction AL11.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
Regards,
Ganesh

Hi jazz,
I want to update the patch SAPKA70016 for SAP_ABA component.
Queue log
System              : ISP
tp path             : tp
Version and release: 372.04.36 700
Activate inactive nametabs
End date and time : 20081215012202
Ended with return code: ===> 8 <===
TP request log is
START CMDIMPORT            ISP L      20081222014354              DDIC         usirs254 20081222014354043
STOP CMDIMPORT            ISP L      20081222014401              DDIC         usirs254 20081222014354043
START DD IMPORT            ISP H      20081222014540              DDIC         usirs254 20081222014540574
STOP DD IMPORT            ISP H      20081222014616              DDIC         usirs254 20081222014540574
START DD ACTIVATION        ISP A      20081222014617              DDIC         usirs254
START tp_getprots          ISP J      20081222014617              DDIC         usirs254
STOP tp_getprots          ISP J      20081222014723              DDIC         usirs254
STOP DD ACTIVATION        ISP A      20081222014723              DDIC         usirs254
START imp all              ISP        20081222014723              DDIC         usirs254 20081222014723434
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O ISP S      20081222014723              DDIC         usirs254 20081222014723434
START tp_getprots          ISP S      20081222014723              DDIC         usirs254 20081222014723434
STOP tp_getprots          ISP S      20081222014726              DDIC         usirs254 20081222014723434
STOP DISTRIBUTION OF DD-O ISP S      20081222014726              DDIC         usirs254 20081222014723434
INFO TBATG CONVERSION OF ISP N      not needed                  DDIC         usirs254 20081222014723434
START MOVE NAMETABS        ISP 6      20081222014726              DDIC         usirs254 20081222014723434
START tp_getprots          ISP P      20081222014726              DDIC         usirs254 20081222014723434
ERROR ALL                  ISP 6 0008 20081222014743              DDIC         usirs254 20081222014723434
STOP tp_getprots          ISP P      20081222014747              DDIC         usirs254 20081222014723434
STOP MOVE NAMETABS        ISP 6      20081222014747              DDIC         usirs254 20081222014723434
ERROR: stopping on error 8 during MOVE NAMETABS
START INFORM SAP-SYSTEM OF ISP Q      20081222014747              DDIC         usirs254 20081222014723434
START tp_getprots          ISP Q      20081222014747              DDIC         usirs254 20081222014723434
STOP tp_getprots          ISP Q      20081222014748              DDIC         usirs254 20081222014723434
STOP INFORM SAP-SYSTEM OF ISP Q      20081222014748              DDIC         usirs254 20081222014723434
STOP imp all              ISP   0008 20081222014748              DDIC         usirs254 20081222014723434
START CMDIMPORT            ISP L      20081222015155              DDIC         usirs254 20081222015155637
STOP CMDIMPORT            ISP L      20081222015158              DDIC         usirs254 20081222015155637

Error in DDIC_Activation while updating SAP_APPL

Hello All,
I'm getting following error while executing SAP_APPL component. Please guide me on this.
The import was stopped, since an error occurred during the phase
DDIC_ACTIVATION, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: DDIC_ACTIVATION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPK-60016INFICA, tp step "A", return
code 0008
In this phase the imported Dictionary objects are activated. This phase
can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
information, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: The tp step DDIC activation could not be performed
successfully. To see the cause of the error in the activation log,
choose Goto -> Log -> Queue.
If you import two or more Support Packages in one queue, and you do
not activate them in the correct sequence, activation errors may
occur. In this case, the activation errors disappear when you repeat
the activation run. To do this, choose Support Package -> Import
Support Package Queue.
Thanks in advance,
Uday

Hi Rupali,
Please see below logs...
Following are the logs that I'm getting, please have a look and let kindly know the solution. SLOG: ERROR: RFC function TRINT_PROGRESS_INDICATOR error: SYSTEM_FAILURE ERROR SAPK-60016INFICA P01 A 0008 20120208012229 SAPUSER BASISADMIN paritas ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18 ERROR SAPK-60016INISPSCA P01 A 0008 20120208012229 SAPUSER BASISADMIN paritas ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18 ERROR SAPKH60016 P01 A 0008 20120208012229 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208012235 BASISADMIN paritas START DD ACTIVATION P01 A 20120208012235 BASISADMIN paritas START tp_getprots P01 J 20120208012236 BASISADMIN paritas STOP tp_getprots P01 J 20120208012235 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208012236 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208012404 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208012404 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208012404 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208012412 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208012412 BASISADMIN paritas START DD ACTIVATION P01 A 20120208094139 BASISADMIN paritas START tp_getprots P01 J 20120208094139 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208094143 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208094143 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208094143 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208094146 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208094146 BASISADMIN paritas START DD ACTIVATION P01 A 20120208094300 BASISADMIN paritas START tp_getprots P01 J 20120208094300 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208094301 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208094301 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208094301 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208094304 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208094304 BASISADMIN paritas START DD ACTIVATION P01 A 20120208095211 BASISADMIN paritas START tp_getprots P01 J 20120208095211 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208095212 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208095212 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208095212 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208095215 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208095215 BASISADMIN paritas START DD ACTIVATION P01 A 20120208100218 BASISADMIN paritas START tp_getprots P01 J 20120208100218 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208100219 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208100219 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208100219 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208100222 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208100222 BASISADMIN paritas START DD ACTIVATION P01 A 20120208102626 BASISADMIN paritas START tp_getprots P01 J 20120208102626 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208102632 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208102632 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208102632 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208102636 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208102636 BASISADMIN paritas START DD ACTIVATION P01 A 20120208111556 BASISADMIN paritas START tp_getprots P01 J 20120208111556 BASISADMIN paritas ERROR SAPK-60016INFICA P01 A 0008 20120208111857 SAPUSER BASISADMIN paritas ERROR SAPK-60016INISPSCA P01 A 0008 20120208111857 SAPUSER BASISADMIN paritas ERROR SAPKH60016 P01 A 0008 20120208111857 SAPUSER BASISADMIN paritas STOP tp_getprots P01 J 20120208111902 BASISADMIN paritas STOP DD ACTIVATION P01 A 20120208111903 BASISADMIN paritas ALOG: SAPK-60016INFICA P01.ALL A 0008 20120208012229 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208012229 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208012229 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208012404 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208012404 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208012404 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208094143 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208094143 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208094143 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208094301 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208094301 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208094301 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208095212 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208095212 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208095212 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208100219 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208100219 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208100219 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208102632 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208102632 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208102632 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208111857 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208111857 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208111857 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208113704 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208113704 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208113704 SAPUSER BASISADMIN paritas SAPK-60016INFICA P01.ALL A 0008 20120208123518 SAPUSER BASISADMIN paritas SAPK-60016INISPSCA P01.ALL A 0008 20120208123518 SAPUSER BASISADMIN paritas SAPKH60016 P01.ALL A 0008 20120208123518 SAPUSER BASISADMIN paritas
Thanks in advance
Uday

Error while updating SAINT SAPKINDA6B - Upgrade ECC 6.0

Hi SAP Experts.
I have a System SAP R/3 4.6 with Windows 2003 and SQL Server 2005.
I can´t updating the component PI to release 2004_1_46C.
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
The following details help you to analyze the
problem: Error in phase: IMPORT_PROPER Reason for error:
TP_STEP_FAILUREReturn code: 0008 Error message: OCS Package ALL , tp
step "6", return
code 0008.
2EETP345 20:48:35: Retcode 1: SQL-error "468-Cannot resolve the
collation conflict between "SQL_Lat
2EETP345 in1_General_CP850_BIN2" and "SQL_Latin1_General_CP850_BIN" in
the equal to operation." in
2EETP345 DDL statement for "V_FLQSUM "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 20:48:35: error in DDL, nametab for "V_FLQSUM" not activated
Please, How can I solve the problem?.
Best regards.
Luis Gomez.

Check
Note 1019320 - sap_update_MSSDBSTATT Cannot resolve collation conflict
Markus

Error while upgrading NW04s ABAP from sp7 to sp8

Hi,
I installed NW04s in my system and its ABAP stack is upgraded to sp7. When i was upgrading its SAP_BASIS support package to sp8, i got the following error.
Error in phase: IMPORT_PROPER
Reason for error: TP_BUFFER_INCONSISTENCY
Return code: 0008
Error message: Pkgs. in queue don"t exist in the tp buffer (e.g. SAPKB70008)
This phase imports all Repository objects and table entries. It may terminate for 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: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.
If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.
You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display these files, run report RSPUTPRT or call transaction AL11.
Can anyone help me to resolve this problem?
Thanks in advance.

I have the similar problem to yours with tp_buffer_consistency at the xpra_phase when I was runing SAINT on a SAP R/3 Service Tool (RTCTOOL) with SAPKITAR19.
Shall you confirm what you have solved your problem are:
1) You have removed registers from the file /usr/sap/trans/buffer/SID which contains the troubled register, an example SAPKNNNNNN. First make a backup of that file before removing registers.
2) You have removed registers from the two tables: PAT01 (PATCH=SAPKNNNNNN), and PAT03 (PATCH=SAPKNNNNNN)
3) Invoke the trx SAINT
4) Installation package-->load package --> from application server
5) Select the uploaded SP and click the button Continue.
6) Anything else.
Appreciate in hearing from your input.
Rodolfo

0008 error

Similar Messages

Maybe you are looking for