SAP Upgrade Error

Dear All
I have upgraded the system from SAP R/3 47 to ECC6.0 on Oracle 10g and window 32 bit. At one stage it is asking to enter the
password. The phase is JOB_J_3GJUPGCD.
The second is that my IGS is not working
Please let me know where we get this password
Thanks & Regards
Vimal

Hi Ashok
I have checked the job log, sm21 and others : error as below
A) ST22
Database error text........: "ORA-08102: index key not found, obj# 77835, file       
9, block 161914 (2)"                                                                
Internal call code.........: "[RSQL/DELE/USOBT_C ]"                                  
Please check the entries in the system log (Transaction SM21).                                                                               
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                            
"EUPDOWN" or "EUPDOWN"                                                               
"CHECK_AND_UPDATE_SPACES"                                                            
B): SM21 as below
12:41:15 DIA  000 000 SAPSYS                BB  D Reset buffer CUA ; mode and status: InvalEnd                                          
12:46:41 BTC  010 000 DDIC                  BY  4 Database error 8102 at DEL access to table USOBT_C                                    
12:46:41 BTC  010 000 DDIC                  BY  0 > ORA-08102: index key not found, obj# 77835, file 9, block                           
12:46:41 BTC  010 000 DDIC                  BY  0 > 161914 (2)                                                                          
12:46:41 BTC  010 000 DDIC                  AB  0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred                                         
12:46:41 BTC  010 000 DDIC                  AB  1 > Short dump "090831 124641 i3lkol02 UP100 " generated                              
12:46:41 BTC  010 000 DDIC                  D0  1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20090831124641i3lkol02_UP1_00 DDIC 00
13:03:06 DIA  000 000                       BY  M SQL error 3106 occurred; work process in reconnect status                             
Regards
Vimal

Similar Messages

  • Sap upgrade-Error when using DP90-OK 530-field catalog not found

    Hello,
    We are upgrading from 4.6c to mySAP ERP 2004 version. In 4.6c, we are using VA90 to create a sales order from service order to bill the customer. However in mySAP ERP 2004 version, VA90 does not exist. So we created DP profile and are  using transaction code DP90 to create billling request for the service order. However, System gives an error 'Field catalog not found'. The diagnosis says that -The field catalog cannot be determined because the output table structure name was not specified.
    Please help us how to solve the above problem.
    Thanks
    Mala

    hi mala,
    did you see SAP-message 442170?
    it is all about conversion VA90/DP90.
    hope this helps.
    br,
    matthias
    Message was edited by: Matthias Leitner

  • SAP Upgrade error  , All goods receipt but still supplier geting warning

    Dear All ,
    Recently our one of client upgraded from SAP 4.6C to ECC6.00 , One of the purchase order july 2009 dated , all the goods receipt did in the month of july it self and no open good receipt for this and it was created in 4.6c , when last week they gone live for SAP ECC 6.00 , for the same order supplier geting a warning message that goods are yet to deliver . Actually all material was delivered in july 2009 only , because of upgrade release all this error are coming , what will be the technical reason for this . Any one came across same kind of problem .
    Thanks
    RB

    Hi,
    Open a call to SAP for a quicker response.........
    Mark

  • Error in SAP Upgrade 4.6C to ECC 6.0 in CONFLICT_CHECK Phase

    Hi All,
    I am doing an SAP Upgrade frm SAP 4.6C SR2 to ECC 6.0 SR2. When it enters the CONFLICT_CHECK we are facing the following error. i am performing this on Production system. Your immediate help is highly appreciated.
    #---- MASKING file CONFLCHK.LOG from E:\usr\sap\put\log
    #---- TIME: 20091212095249
    1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20091212094722")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '22', GwService = 'sapgw22'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
    4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
    2 ETQ160 Starting conflict check
    4 ETQ010 Date & Time: 20091212094722 
    4 ETQ230 Starting RFC Login to: System = "CPA", GwHost = "DERSHASKFI140", GwService = "sapgw22"
    4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
    2EETQ360 RFC of "spda_conflict_check" failed:
    2EETQ361 code/exception  : SYSTEM_FAILURE
    2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
    2EETQ364 message         :
    2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ                    .
    4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
    4 ETQ232 RFC Login succeeded
    2EETQ235 Call of function module "SPDA_CONFLICT_CHECK" by RFC failed (error-status "-2")
    4 ETQ239 Logging off from SAP system
    4 ETQ010 Date & Time: 20091212094903 
    4 ETQ010 Date & Time: 20091212094903 
    Hemanth

    Hi,
    > 2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ           
    Have you checked tablespace have sufficient space ?
    Thanks
    Sunny        .

  • Frequently faced errors in Unicode while SAP Upgrade

    Hi Gusy,
    I am going work on Unicode upgarde project, can any one share Frequently faced errors in Unicode while SAP Upgrade.
    Thanks,
    Gourisankar.

    Hi
    MESSAGEG@3      
    Replace variable declaration of type X with appropriate value from method cl_abap_char_utilities
    i.e.      CONSTANTS:      con_tab TYPE x VALUE '09',
                   con_cret TYPE x VALUE '0D'.
    would be replaced with
         CONSTANTS:      con_tab TYPE c value cl_abap_char_utilities=>HORIZONTAL_TAB,
                   con_cret TYPE c value cl_abap_char_utilities=>CR_LF.
    *UPLO      *
    Upload/ws_upload and download/ws_download are obsolete, since they are not Unicode enabled. Replace
    with appropriate methods from cl_gui_frontend_services. Please also note that the data types of the various
    parameters will also probably also need changing for the new method calls but the code below demonstrates
    how to do this. I_TABLE is the original table and IT_UCTABLE is the converted table.
    i.e. Function module u2018WS_DOWNLOADu2019
      CALL FUNCTION 'WS_DOWNLOAD'
          EXPORTING
               FILENAME                = p_file
               FILETYPE                = 'ASC'
             MODE                    = ' '
           TABLES
                DATA_TAB                = i_table
          EXCEPTIONS
    would be replaced with
    data: gd_file type string.
    types: t_uctable like line of i_table.
    data:  it_uctable type standard table of t_uctable.
      gd_file = p_file.
      it_uctable[] = i_table[].
      CALL METHOD cl_gui_frontend_services=>gui_download
      EXPORTING
        filename = gd_file
        filetype = 'ASC' " DAT,WK1
        Append   = ' '   "if mode = A then this would be X
      CHANGING
        data_tab = it_uctable
      EXCEPTIONS
        OTHERS   = 1.
    Function module u2018DOWNLOADu2019
          CALL FUNCTION 'DOWNLOAD'
            EXPORTING
              filename = p_file
              filetype = 'WK1'
            TABLES
              data_tab = i_table.
    would be replaced with
    data: gd_file type string.
    DATA: ld_filename TYPE string,
          ld_path TYPE string,
          ld_fullpath TYPE string,
          ld_result TYPE i.
    types: t_uctable like line of i_table.
    data:  it_uctable type standard table of t_uctable.
      gd_file = p_file.
      shift gd_file RIGHT DELETING TRAILING '\'.
      shift gd_file RIGHT DELETING TRAILING '/'.
      shift gd_file left DELETING LEADING space.
      CALL METHOD cl_gui_frontend_services=>file_save_dialog
        EXPORTING
          DEFAULT_EXTENSION = 'WK1'
          default_file_name = gd_file
          INITIAL_DIRECTORY = gd_file
        CHANGING
          filename          = ld_filename
          path              = ld_path
          fullpath          = ld_fullpath
          user_action       = ld_result.
      check ld_result eq 0.
      gd_file = ld_fullpath.
      gd_file = p_file.
      it_uctable[] = i_table[].
      CALL METHOD cl_gui_frontend_services=>gui_download
      EXPORTING
        filename = gd_file
        filetype = 'ASC' " DAT,WK1
        Append   = ' '   "if mode = A then this would be X
      CHANGING
        data_tab = it_uctable
      EXCEPTIONS
        OTHERS   = 1.
    Or in circumstances where you need to add field texts to the first line of the file you could use the
    GUI_DOWNLOAD function module:
    DATA: BEGIN OF fields_tab OCCURS 0,
            f1(50),
          END   OF fields_tab.
    fields_tab-f1 = 'field1 text'.
    APPEND fields_tab.
    fields_tab-f1 = 'field2 text'.
    APPEND fields_tab.
    fields_tab-f1 = 'field3 text'.
    APPEND fields_tab.
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename                = i_filename
          filetype                = 'DAT'
        IMPORTING
          filelength              = filelen
        TABLES
          data_tab                = itab
          fieldnames              = fields_tab
        EXCEPTIONS
    Note: u2018ws_uploadu2019 and u2018uploadu2019 would be the same as above but would use the
    cl_gui_frontend_services=>gui_upload method call instead:
    CALL METHOD cl_gui_frontend_services=>gui_upload
      EXPORTING
        filename = gd_file
        filetype = 'ASC' " DAT,WK1
        Append   = ' '
      CHANGING
        data_tab = it_uctable
      EXCEPTIONS
        OTHERS   = 1.
    OPEN 004      
    Add u2018ENCODINGu2019 addition to statement
    i.e.      OPEN DATASET G_DATAFILE for OUTPUT IN TEXT MODE.
    would be replaced with
         OPEN DATASET G_DATAFILE for OUTPUT IN TEXT MODE ENCODING NON-UNICODE.
    OPEN 002      
    IN..Mode is expected within open dataset command.
    i.e.      OPEN DATASET wfilepath FOR OUTPUT.
    would be replaced with
         OPEN DATASET wfilepath FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE.
    Or      OPEN DATASET wfilepath FOR OUTPUT IN BINARY MODE.
    OPEN 001      
    FOR INPUT, FOR OUTPUT, FOR APPENDING or FOR UPDATE expected!
    i.e.      OPEN DATASET wfilepath FOR OUTPUT.
    would be replaced with
         OPEN FOR OUTPUT DATASET wfilepath FOR OUTPUT IN TEXT MODE.
    DESCIBE002      
    THE DESCRIBE LENGTH can only be used with the IN BYTE or IN CHARACTER MODE
    i.e.      describe field e_text length line_length.
    would be replaced with
         describe field e_text length line_length IN CHARACTER MODE.
    ASSIGN 019      
    The statement u2018ASSIGN PATH+PATHLENGTH TO
    .u2019 Returns the following error message:
    "You cannot use ASSIGN f+offset. Always use an explicit length (or '*')".
    i.e.      ASSIGN PATH+PATHLENGTH TO
    would be replaced with
         ASSIGN PATH+PATHLENGTH(2) TO
    . u201Creplace 2 with the length of the field
    MESSAGEG!2      
    Itab/structure and u201C u201C  are not mutually convertible in a Unicode program
    i.e.      G_SHOW_LIST = SPACE.
    would be replaced with
         Clear: G_SHOW_LIST.
    Or       G_SHOW_LIST-field1 = space.
         G_SHOW_LIST-field2 = space.
                             u2026etc
    *MESSAGEG!3      *
    var and var  are not comparable in a Unicode program
    Example      Data: VAR like tabix.
    was replaced with
              Data: VAR type sy-tabix.

  • SAP Upgrade issue  ABAP-PI Proxy error

    Hi Guys,
    We have an issue in SAP R3 system after the recent SAP upgrade.
    The proxy programs in R3 were using SAP Standard structure in their development.
    Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
    And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
    We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
    So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
    Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
    Kind Regards
    Rajesh.S

    Hi Harald,
    Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
    Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import  the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
    Best Regards,
    Rajesh.S

  • SAP Upgrade wizard crashes on upgrading users SAP Business One 8.82 PL12 to 9.0 PL5

    Dear Forum,
    Good Evening!
    I have an issue while upgrading, present we are using SAP Business One 8.82 PL12.  We would like to upgrade SAP Business One 9.0 PL 5 as per SAP Overview note SAP Business One 9.0 PL5.
    At the time of upgrading Users
    System Automatically crashed.
    Further does not upgrade.
    Please give your suggestion.

    Hi Manivannan,
    Please check below link.
    SAP B1 8.82 to SAP 9.0 PL3 Data Upgrade Error
    Hope help
    Regards::::
    Atul Chakraborty

  • Error while printing (SAP spool error)

    Hi,
    I have configured a printer of type 'C : Direct Operating System Call'. On printing a page, an error occurs with the following log entries
    SAP spool error log
    =====================
    Print request processing log
    The host spool is reporting errors
    Windows/NT error 1775: "A null context handle was passed from the client to the host during a remote procedure call."
    Errors occurred processing this print request
    Error during print request output. l_rc = 1
    There may be no printout
    Please. can someone help me out here.
    Thanks!
    Regards,
    Angad

    Ok I am upgrading from R/3 46C to ECC 6.0, on the 46c system the printers are configured as follow:
    Device type          HPLJ4    : HP Laserjet 4 series
    Spool server          sapprod1_PRD_00       sapprod1
    Device class          Standard printer
    Host spool access method C: Direct operating system call
    Host printer          
    srtroot03.startek.com\srt-dc-c4-sharp
    Host name          sapprod1
    On the ECC 6.0 system the printers are configured as follows:
    Device Type          HPLJ4    : HP Laserjet 4 series
    Spool Server          srtsapeccdev1_DEV_00
    Server Description
    Host               srtsapeccdev1
    Device Class          Standard printer
    Host Spool Access Method C: Direct operating system call
    Host printer          
    srtroot03.startek.co\srt-dc-c4-sharp
    HostName          srtsapeccdev1
    The 46c system prints just fine, on the ECC 6.0 systems; I can not get the printers to work.  I have made sure that the hosts file on the ECC server has the printer host address, and I get the following error back:
    SAP spool error log
    =====================                                                     
    Print request processing log
    The host spool is reporting errors
    Windows/NT error 5 [
    srtroot03.startek.com\srt-dc-c4-sharp]: "Access is denied."
    Errors occurred processing this print request
    Error during print request output. l_rc = 1
    There may be no printout
    The access to the Printer Host is wide open, what do I need to do to resolve this issue.

  • SCM2007 upgrade error in SHDINST_CPY phase of PREPARE in MSCS

    Dear all,
    we're trying an experimental upgrade from SCM5.0 to SCM2007 on an MSCS cluster (sql server rdbms on a separate cluster).
    Currently the SCM5.0 is installed on a multi-SID cluster, with ASCS only in HA, 2 standalone enqueue replicators on the 2 nodes, CI and DIA on the 2 nodes, exacttly as of the manual, and it worked great so far.
    Now we're trying to upgrade this clustered SCM instance to SCM2007, and
    the upgrade is stuck in SHDINST_CPY phase of PREPARE, with the error:
    SEVERE ERROR: copy of O:\usr\sap\put\bin\NTINSTASCS.PFL failed
    In fact, the file above (ASCS profile template) doesn't exist in the put folder.
    Tried the PREPARE twice, by using a new empty put folder and fresh upgrade media, same result.
    So far very little or no support from SAP.
    Any hints will be sincerely appreciated.
    Franco.

    Hmm, thanks for the suggestion but that doesn't apply to our case.
    Here you see out UpgDialog file with all the events registered. Apart of the error: ERROR: RFC of "subst_get_uvers" failed. (DDIC was locked before), to me it seems pretty clean.
    Target SAP system is SCD
    Enter the SAP instance number [13]:
    ? INSTANCE NUMBER   =
    Waiting for input since May 13, 2008 9:55:13 AM
    > INSTANCE NUMBER   =  13
    Type of database system is mss
      >>>>>>>>>> Input Wizard <<<<<<<<<<
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 01 =
    ? MOUNT POINT 02 =
    ? MOUNT POINT 03 =
    ? MOUNT POINT 04 =
    ? MOUNT POINT 05 =
    ? MOUNT POINT 06 =
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 07 =
    ? MOUNT POINT 08 =
    ? MOUNT POINT 09 =
    ? MOUNT POINT 10 =
    ? MOUNT POINT 11 =
    ? MOUNT POINT 12 =
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 13 =
    ? MOUNT POINT 14 =
    ? MOUNT POINT 15 =
    ? MOUNT POINT 16 =
    ? MOUNT POINT 17 =
    ? MOUNT POINT 18 =
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 19 =
    ? MOUNT POINT 20 =
    ? MOUNT POINT 21 =
    ? MOUNT POINT 22 =
    ? MOUNT POINT 23 =
    ? MOUNT POINT 24 =
    Waiting for input since May 13, 2008 9:55:32 AM
    > MOUNT POINT 20 = 
    > MOUNT POINT 15 = 
    > MOUNT POINT 01 =  V:\SCM2007\51033041
    > MOUNT POINT 13 = 
    > MOUNT POINT 04 = 
    > MOUNT POINT 07 = 
    > MOUNT POINT 11 = 
    > MOUNT POINT 08 = 
    > MOUNT POINT 03 = 
    > MOUNT POINT 17 = 
    > MOUNT POINT 14 = 
    > MOUNT POINT 10 = 
    > MOUNT POINT 06 = 
    > MOUNT POINT 09 = 
    > MOUNT POINT 24 = 
    > MOUNT POINT 18 = 
    > MOUNT POINT 23 = 
    > MOUNT POINT 19 = 
    > MOUNT POINT 05 = 
    > MOUNT POINT 16 = 
    > MOUNT POINT 21 = 
    > MOUNT POINT 22 = 
    > MOUNT POINT 02 = 
    > MOUNT POINT 12 = 
    There are either some mount points which can't be accessed
    or the currently mounted set of Data Carriers does not satisfy a mount
    request.
    Do you want to correct mount points?
    ? yes
    ? no
    Waiting for input since May 13, 2008 10:06:10 AM
    > yes
      >>>>>>>>>> Input Wizard <<<<<<<<<<
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 01 =
    ? MOUNT POINT 02 =
    ? MOUNT POINT 03 =
    ? MOUNT POINT 04 =
    ? MOUNT POINT 05 =
    ? MOUNT POINT 06 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 07 =
    ? MOUNT POINT 08 =
    ? MOUNT POINT 09 =
    ? MOUNT POINT 10 =
    ? MOUNT POINT 11 =
    ? MOUNT POINT 12 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 13 =
    ? MOUNT POINT 14 =
    ? MOUNT POINT 15 =
    ? MOUNT POINT 16 =
    ? MOUNT POINT 17 =
    ? MOUNT POINT 18 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 19 =
    ? MOUNT POINT 20 =
    ? MOUNT POINT 21 =
    ? MOUNT POINT 22 =
    ? MOUNT POINT 23 =
    ? MOUNT POINT 24 =
    Waiting for input since May 13, 2008 10:06:13 AM
    > MOUNT POINT 12 = 
    > MOUNT POINT 09 = 
    > MOUNT POINT 21 = 
    > MOUNT POINT 17 = 
    > MOUNT POINT 08 = 
    > MOUNT POINT 18 = 
    > MOUNT POINT 16 = 
    > MOUNT POINT 14 = 
    > MOUNT POINT 22 = 
    > MOUNT POINT 13 = 
    > MOUNT POINT 01 =  V:\SCM2007\51033041
    > MOUNT POINT 02 =  V:\SCM2007\D51032928
    > MOUNT POINT 05 = 
    > MOUNT POINT 15 = 
    > MOUNT POINT 23 = 
    > MOUNT POINT 03 =  V:\SCM2007\D51032924
    > MOUNT POINT 04 =  V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86
    > MOUNT POINT 24 = 
    > MOUNT POINT 07 = 
    > MOUNT POINT 10 = 
    > MOUNT POINT 19 = 
    > MOUNT POINT 20 = 
    > MOUNT POINT 11 = 
    > MOUNT POINT 06 = 
    There are either some mount points which can't be accessed
    or the currently mounted set of Data Carriers does not satisfy a mount
    request.
    Do you want to correct mount points?
    ? yes
    ? no
    Waiting for input since May 13, 2008 10:09:17 AM
    > yes
      >>>>>>>>>> Input Wizard <<<<<<<<<<
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 01 =
    ? MOUNT POINT 02 =
    ? MOUNT POINT 03 =
    ? MOUNT POINT 04 =
    ? MOUNT POINT 05 =
    ? MOUNT POINT 06 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 07 =
    ? MOUNT POINT 08 =
    ? MOUNT POINT 09 =
    ? MOUNT POINT 10 =
    ? MOUNT POINT 11 =
    ? MOUNT POINT 12 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 13 =
    ? MOUNT POINT 14 =
    ? MOUNT POINT 15 =
    ? MOUNT POINT 16 =
    ? MOUNT POINT 17 =
    ? MOUNT POINT 18 =
    The requested Data Carrier is not mounted on any of the mount points
    you entered.
    Please enter up to 24 mount points for CDs.
    Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
    ? MOUNT POINT 19 =
    ? MOUNT POINT 20 =
    ? MOUNT POINT 21 =
    ? MOUNT POINT 22 =
    ? MOUNT POINT 23 =
    ? MOUNT POINT 24 =
    Waiting for input since May 13, 2008 10:09:21 AM
    > MOUNT POINT 21 = 
    > MOUNT POINT 02 =  V:\SCM2007\D51032924
    > MOUNT POINT 24 = 
    > MOUNT POINT 08 = 
    > MOUNT POINT 17 = 
    > MOUNT POINT 07 = 
    > MOUNT POINT 15 = 
    > MOUNT POINT 12 = 
    > MOUNT POINT 19 = 
    > MOUNT POINT 05 = 
    > MOUNT POINT 13 = 
    > MOUNT POINT 23 = 
    > MOUNT POINT 01 =  V:\SCM2007\D51032928
    > MOUNT POINT 14 = 
    > MOUNT POINT 06 = 
    > MOUNT POINT 03 =  V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86
    > MOUNT POINT 11 = 
    > MOUNT POINT 09 = 
    > MOUNT POINT 04 =  V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master
    > MOUNT POINT 22 = 
    > MOUNT POINT 20 = 
    > MOUNT POINT 10 = 
    > MOUNT POINT 18 = 
    > MOUNT POINT 16 = 
    Reading data from "Upgrade Master CD/DVD"...
    Extracting archive "V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\DBINDEP\CTRL7000.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\DBINDEP\CTRL7000.SAR successfully unpacked to O:\usr\sap\put.
    Extracting archive "V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\DBINDEP\CTRL700X.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\DBINDEP\CTRL700X.SAR successfully unpacked to O:\usr\sap\put.
    Extracting archive "V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\MSS\UPTOOLS.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\51033041\SAP_SCM_2007_Upgrade_Master\UMU_WINDOWS_X86_64\MSS\UPTOOLS.SAR successfully unpacked to O:\usr\sap\put.
    Welcome to the SAP upgrade control program.
    Important information for this upgrade is included
    in the upgrade Note and further Notes mentioned therein.
    Refer to the upgrade manual for the number of this note.
    It is advisable to obtain this Note before starting any process
    since it also contains important information about preparing
    the upgrade.
    It is essential that you get a current version of this Note
    before starting the upgrade with SAPup. It contains a keyword
    which is necessary to start the upgrade procedure.
    Please look into the SAP Service Marketplace or, if not available,
    use the form in your packet to request the upgrade Note.
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:09:53 AM
    > continue
    SAP  UPGRADE  CONTROL  PROGRAM
    ================================
    This is SAPup version 7.00/2 upgrade to release
            703 of BI_CONT
            400 of EA-IPPE
            2006_700 of LCAPPS
            2006_1_700 of PI_BASIS
            200 of QIE
            700 of SAP_ABA
            700 of SAP_AP
            700 of SAP_BASIS
            700 of SAP_BW
            510 of SCEMSRV
            510 of SCM
            510 of SCMBPLUS
            510 of SCMEWM
            510 of SCMSNC
            510 of SCM_BASIS
            2005_1_700 of ST-PI
    Target SAP system is SCD, MSSQL database
    SAPup started in PREPARE mode.
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:09:59 AM
    > continue
    The following options are available:
    select: Display screen for selecting PREPARE modules
    status: Display the statuses of the PREPARE modules
    exit:   Exit PREPARE
    help:   Getting help about PREPARE
    ? select
    ? status
    ? exit
    Waiting for input since May 13, 2008 10:10:02 AM
    > select
    Select the PREPARE modules
    ?                             name     status  mandatory
    ?                  Parameter input    initial        yes
    ?                   Initialization    initial        yes
    ?                           Import    initial        yes
    ?                        Extension    initial        yes
    ?                      Integration    initial        yes
    ?                     Installation    initial        yes
    ?                   General checks    initial        yes
    ?                Activation checks    initial        yes
    ? Necessary checks for conversions    initial        yes
    ?  Optional checks for conversions    initial         no
    ?             Modification support    initial         no
    ?                   Pre-processing    initial         no
    Waiting for input since May 13, 2008 10:10:05 AM
    >                  Parameter input    initial        yes >                   Initialization    initial        yes >                           Import    initial        yes >                        Extension    initial        yes >                      Integration    initial        yes >                     Installation    initial        yes >                   General checks    initial        yes >                Activation checks    initial        yes > Necessary checks for conversions    initial        yes
    You selected the following PREPARE modules:
    Parameter input
    Initialization
    Import
    Extension
    Integration
    Installation
    General checks
    Activation checks
    Necessary checks for conversions
    execute: Execute the selected PREPARE modules.
             Make sure that you have carried out the actions described in
             O:\usr\sap\put\log\CHECKS.LOG before continuing.
             (Note: The contents of file CHECKS.LOG are saved
              in O:\usr\sap\put\log\CHECKS.SAV)
    select:  Display screen for selecting PREPARE modules.
    exit:    Exit PREPARE.
    help:    Getting help about PREPARE modules.
    ? execute
    ? select
    ? exit
    Waiting for input since May 13, 2008 10:10:14 AM
    > execute
    Execution of PREPARE module Parameter input begins at 20080513101018
    >> 10:10:18  PREPARE: START OF PHASE BEGIN_PRE
    Generating html phase list files 'phase_toc.html' and 'phaselist.html'
    >> 10:10:18  PREPARE: END OF PHASE   BEGIN_PRE
    >> 10:10:18  PREPARE: START OF PHASE KEY_CHK
    Upgrade Correction Package
    The upgrade correction package FIX_SCM51.UPG for this upgrade
    could not be found in directory O:\usr\sap\put
    Please check note 813658 on SAPNet for more details.
    ? retry
    ? exit
    Waiting for input since May 13, 2008 10:10:18 AM
    > retry
    Correction package 'O:\usr\sap\put\FIX_SCM51.UPG' found, extracting to 'O:\usr\sap\put'
    Archive successfully unpacked.
    Enter the SAPup keyword of note 1010762
    ? SAPup keyword =
    Waiting for input since May 13, 2008 10:10:55 AM
    > SAPup keyword = 17824163
    >> 10:11:25  PREPARE: END OF PHASE   KEY_CHK
    >> 10:11:25  PREPARE: START OF PHASE EXTRACTKRN_PRE
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPMMC.SAR" to "O:\usr\sap\put\exe" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPMMC.SAR successfully unpacked to O:\usr\sap\put\exe.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\UNINSTSAP.EXE" to "O:\usr\sap\put\exe" ...
    Done.
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPEXE.SAR" to "O:\usr\sap\put\exe" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPEXE.SAR successfully unpacked to O:\usr\sap\put\exe.
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\MSS\SAPEXEDB.SAR" to "O:\usr\sap\put\exe" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\MSS\SAPEXEDB.SAR successfully unpacked to O:\usr\sap\put\exe.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\IGSEXE.SAR" to "O:\usr\sap\put\exe" ...
    Done.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\IGSHELPER.SAR" to "O:\usr\sap\put\exe" ...
    Done.
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPMMC.SAR" to "O:\usr\sap\put\exenew" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPMMC.SAR successfully unpacked to O:\usr\sap\put\exenew.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\UNINSTSAP.EXE" to "O:\usr\sap\put\exenew" ...
    Done.
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPEXE.SAR" to "O:\usr\sap\put\exenew" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\SAPEXE.SAR successfully unpacked to O:\usr\sap\put\exenew.
    Extracting archive "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\MSS\SAPEXEDB.SAR" to "O:\usr\sap\put\exenew" ...
    Archive V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\MSS\SAPEXEDB.SAR successfully unpacked to O:\usr\sap\put\exenew.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\IGSEXE.SAR" to "O:\usr\sap\put\exenew" ...
    Done.
    Copying file "V:\SCM2007\51033508_16\NW_7.0_SR3_Kernel_WINDOWS__LNX_X86\KU_WINDOWS_X86_64_AUPG\DBINDEP\IGSHELPER.SAR" to "O:\usr\sap\put\exenew" ...
    Done.
    >> 10:11:47  PREPARE: END OF PHASE   EXTRACTKRN_PRE
    >> 10:11:47  PREPARE: START OF PHASE INITPUT_PRE
    Supply the following information:
    Confirm the name of your SAP system:
    ? SAP SYSTEM ID     =
    The hostname of your central SAP server:
    ? SAP SYSTEM HOST   =
    Enter the SAP instance number:
    ? INSTANCE NUMBER   =
    Waiting for input since May 13, 2008 10:11:47 AM
    > INSTANCE NUMBER   =  13
    > SAP SYSTEM HOST   =  DEVCI1
    > SAP SYSTEM ID     =  SCD
    The system identifier of your database:
    ? DATABASE ID       =
    The hostname of your database server:
    ? DATABASE HOST     =
    Waiting for input since May 13, 2008 10:12:04 AM
    > DATABASE HOST     =  OLTPDTSQL
    > DATABASE ID       =  SCD
    Executing script MSSCONCHECK ...
    Supply the following information:
    The password for SAP user DDIC in client 000
    (may be 19920706):
    ? DDIC PASSWORD  =
    Verify password for SAP user DDIC:
    ? DDIC PASSWORD  =
    Waiting for input since May 13, 2008 10:12:10 AM
    > DDIC PASSWORD  =  <hidden input>
    > DDIC PASSWORD  =  <hidden input>
    The hostname of your batch server:
    ? BATCH HOST        =
    Waiting for input since May 13, 2008 10:12:17 AM
    > BATCH HOST        =  DEVCI1
    Supply the following information:
    The maximum number of parallel processes during uptime:
    ? MAXIMUM UPTIME PROCESSES =
    The number of parallel import processes:
    ? R3TRANS PROCESSES =
    The maximum profile value of "bufreftime":
    ? MAXIMUM SYNC TIME =
    Waiting for input since May 13, 2008 10:12:21 AM
    > MAXIMUM UPTIME PROCESSES =  1
    > MAXIMUM SYNC TIME =  120
    > R3TRANS PROCESSES =  3
    The password for Operating System account ATRSAP\SAPServiceSCD:
    ? PASSWORD  =
    Verification of the password for Operating System account ATRSAP\SAPServiceSCD:
    ? PASSWORD  =
    Waiting for input since May 13, 2008 10:12:24 AM
    > PASSWORD  =  <hidden input>
    > PASSWORD  =  <hidden input>
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    Executing script MSSUPGSPS ...
    Executing script MSSINCHK ...
    >> 10:12:34  PREPARE: END OF PHASE   INITPUT_PRE
    >> 10:12:34  PREPARE: START OF PHASE DBCHK_PRE
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    Is there more than one system running in this database?
    (MCOD: Multiple components in one database)
    ? no
    ? yes
    Waiting for input since May 13, 2008 10:12:35 AM
    > no
    >> 10:13:07  PREPARE: END OF PHASE   DBCHK_PRE
    >> 10:13:07  PREPARE: START OF PHASE CONFCHK_IMP
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    Your database and your central SAP instance
    are running on different hosts. Please select
    the operating system which is running on the
    database host (see next page).
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:13:09 AM
    > continue
             The following operating systems are supported
    ? Windows NT INTEL
    ? Windows NT IA64
    ? Windows NT X86_64
    ? AIX
    ? HP-UX
    ? HP-UX IA64
    ? SunOS
    ? Linux
    ? OS/400
    ? z/OS
    Waiting for input since May 13, 2008 10:13:17 AM
    > Windows NT X86_64
    >> 10:13:21  PREPARE: END OF PHASE   CONFCHK_IMP
    >> 10:13:21  PREPARE: START OF PHASE SOLMAN_CHK
    The SAP Solution Manager Key is required for the upgrade.
    Further informations can be found in the upgrade guide,
    the SAP Service Marketplace and SAP note 805390!
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:13:22 AM
    > continue
    ? SAP Solution Manager Key =
    Waiting for input since May 13, 2008 10:13:30 AM
    > SAP Solution Manager Key = 72AEDE0F91
    >> 10:13:33  PREPARE: END OF PHASE   SOLMAN_CHK
    >> 10:13:33  PREPARE: START OF PHASE CHKSYSTYPE
    >> 10:13:35  PREPARE: END OF PHASE   CHKSYSTYPE
    >> 10:13:35  PREPARE: START OF PHASE HIAV_CHK
    >> 10:13:35  PREPARE: END OF PHASE   HIAV_CHK
    >> 10:13:35  PREPARE: START OF PHASE J2EE_CHK1
    >> 10:13:35  PREPARE: END OF PHASE   J2EE_CHK1
    >> 10:13:35  PREPARE: START OF PHASE REQ_J2EEUPG
    >> 10:13:35  PREPARE: END OF PHASE   REQ_J2EEUPG
    >> 10:13:35  PREPARE: START OF PHASE SETSYNC_PREP_STARTED
    >> 10:13:35  PREPARE: END OF PHASE   SETSYNC_PREP_STARTED
    >> 10:13:35  PREPARE: START OF PHASE REQ_READNOTE
    >> 10:13:35  PREPARE: END OF PHASE   REQ_READNOTE
    >> 10:13:35  PREPARE: START OF PHASE INIT_CBU
    >> 10:13:35  PREPARE: END OF PHASE   INIT_CBU
    >> 10:13:35  PREPARE: START OF PHASE CHECKGROUP_END0
    Execution of PREPARE module Parameter input ends at 20080513101335
    Execution of PREPARE module Initialization begins at 20080513101335
    >> 10:13:35  PREPARE: START OF PHASE INITCURENV
    >> 10:13:35  PREPARE: END OF PHASE   INITCURENV
    >> 10:13:35  PREPARE: START OF PHASE DBCHK_INI
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SCD
    >> 10:13:35  PREPARE: END OF PHASE   DBCHK_INI
    >> 10:13:35  PREPARE: START OF PHASE RFCCHK_INI
    ERROR: RFC of "subst_get_uvers" failed.
    key             : RFC_ERROR_SYSTEM_FAILURE
    message         :
    Password logon no longer possible - too many failed attempts
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:13:36 AM
    > continue
    SEVERE ERROR: couldn't read UVERS entry via RFC
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:14:33 AM
    > continue
    SEVERE ERROR(S) OCCURRED IN RFCCHK_INI !!!
    ? exit
    ? retry
    Waiting for input since May 13, 2008 10:14:38 AM
    > retry
    >> 10:14:41  PREPARE: START OF PHASE RFCCHK_INI
    >> 10:14:41  PREPARE: END OF PHASE   RFCCHK_INI
    >> 10:14:41  PREPARE: START OF PHASE VERSCHK_INI
    >> 10:14:41  PREPARE: END OF PHASE   VERSCHK_INI
    >> 10:14:41  PREPARE: START OF PHASE VALCHK_INI
    >> 10:14:42  PREPARE: END OF PHASE   VALCHK_INI
    >> 10:14:42  PREPARE: START OF PHASE TOOLVERSION_INI
    >> 10:14:43  PREPARE: END OF PHASE   TOOLVERSION_INI
    >> 10:14:43  PREPARE: START OF PHASE UNICODE_CHK_PRE
    >> 10:14:43  PREPARE: END OF PHASE   UNICODE_CHK_PRE
    >> 10:14:43  PREPARE: START OF PHASE TOOLVERSION_UPG1
    >> 10:14:45  PREPARE: END OF PHASE   TOOLVERSION_UPG1
    >> 10:14:45  PREPARE: START OF PHASE DBCONNCHK_INI
    Checking DB connect with 'O:\usr\sap\put\exe\R3trans.exe'.
    >> 10:14:45  PREPARE: END OF PHASE   DBCONNCHK_INI
    >> 10:14:45  PREPARE: START OF PHASE SETSYNC_INFO_FINISHED
    >> 10:14:45  PREPARE: END OF PHASE   SETSYNC_INFO_FINISHED
    >> 10:14:45  PREPARE: START OF PHASE UCMIG_DECISION
    >> 10:14:45  PREPARE: END OF PHASE   UCMIG_DECISION
    >> 10:14:45  PREPARE: START OF PHASE CLNT_CHK_INI
    >> 10:14:50  PREPARE: END OF PHASE   CLNT_CHK_INI
    >> 10:14:50  PREPARE: START OF PHASE PATCH_CHK1
    >> 10:14:56  PREPARE: END OF PHASE   PATCH_CHK1
    >> 10:14:56  PREPARE: START OF PHASE INTCHK_INI
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getddxttent SCD
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getddxtfent SCD
    >> 10:14:56  PREPARE: END OF PHASE   INTCHK_INI
    >> 10:14:56  PREPARE: START OF PHASE ADJ_CNTRANS
    Calling R3trans to import 'RSUPDTEC.60X'.
    Waiting 130 seconds for buffer synchronization ...
    working ...
    >> 10:17:18  PREPARE: END OF PHASE   ADJ_CNTRANS
    >> 10:17:18  PREPARE: START OF PHASE INIT_CNTRANS
    >> 10:17:18  PREPARE: END OF PHASE   INIT_CNTRANS
    >> 10:17:18  PREPARE: START OF PHASE CNTRANS_PRE
    >> 10:17:18  PREPARE: END OF PHASE   CNTRANS_PRE
    >> 10:17:18  PREPARE: START OF PHASE DMPSPC_INI
    >> 10:17:18  PREPARE: END OF PHASE   DMPSPC_INI
    >> 10:17:18  PREPARE: START OF PHASE JOB_RSDB4090
    >> 10:17:18  PREPARE: END OF PHASE   JOB_RSDB4090
    >> 10:17:18  PREPARE: START OF PHASE CHK_DB6_REG_PRE
    >> 10:17:18  PREPARE: END OF PHASE   CHK_DB6_REG_PRE
    >> 10:17:18  PREPARE: START OF PHASE CHK_DB6_PAR_INI
    >> 10:17:18  PREPARE: END OF PHASE   CHK_DB6_PAR_INI
    >> 10:17:18  PREPARE: START OF PHASE SPACECHK_INI
    Executing script MSSSPACE ...
    >> 10:17:19  PREPARE: END OF PHASE   SPACECHK_INI
    >> 10:17:19  PREPARE: START OF PHASE KRNCHK_DEST
    >> 10:17:19  PREPARE: END OF PHASE   KRNCHK_DEST
    >> 10:17:19  PREPARE: START OF PHASE DBPREP_CHK
    >> 10:17:19  PREPARE: END OF PHASE   DBPREP_CHK
    >> 10:17:19  PREPARE: START OF PHASE EXECCV
    >> 10:17:24  PREPARE: END OF PHASE   EXECCV
    >> 10:17:24  PREPARE: START OF PHASE EXECAV
    >> 10:17:29  PREPARE: END OF PHASE   EXECAV
    >> 10:17:29  PREPARE: START OF PHASE COMPINFO_INI
    >> 10:17:29  PREPARE: END OF PHASE   COMPINFO_INI
    >> 10:17:29  PREPARE: START OF PHASE ADDON_CHK
    >> 10:17:29  PREPARE: END OF PHASE   ADDON_CHK
    >> 10:17:29  PREPARE: START OF PHASE ADDON_INFO
    >> 10:17:29  PREPARE: END OF PHASE   ADDON_INFO
    >> 10:17:29  PREPARE: START OF PHASE ADDON_SPEC1
    >> 10:17:35  PREPARE: END OF PHASE   ADDON_SPEC1
    >> 10:17:35  PREPARE: START OF PHASE ADDON_TREAS
    >> 10:17:35  PREPARE: END OF PHASE   ADDON_TREAS
    >> 10:17:35  PREPARE: START OF PHASE ADDON_WFM
    >> 10:17:35  PREPARE: END OF PHASE   ADDON_WFM
    >> 10:17:35  PREPARE: START OF PHASE ADDON_DMC
    >> 10:17:35  PREPARE: END OF PHASE   ADDON_DMC
    >> 10:17:35  PREPARE: START OF PHASE ACE_CHK
    >> 10:17:35  PREPARE: END OF PHASE   ACE_CHK
    >> 10:17:35  PREPARE: START OF PHASE CRM_BILL
    >> 10:17:35  PREPARE: END OF PHASE   CRM_BILL
    >> 10:17:35  PREPARE: START OF PHASE PR_DBPAR
    >> 10:17:35  PREPARE: END OF PHASE   PR_DBPAR
    >> 10:17:35  PREPARE: START OF PHASE CHECKGROUP_END1
    Execution of PREPARE module Initialization ends at 20080513101735
    Execution of PREPARE module Import begins at 20080513101735
    >> 10:17:35  PREPARE: START OF PHASE REQIMPORT
           The PREPARE module Import will be started now.
    During this module programs, structures, and table entries
    required by PREPARE are imported (the socalled "tool import").
    Note: This can cause a loss of performance in R/3
    In rare cases, a concurrent transport via the transport directory
    may disturb the tool import. Please avoid any concurrent import
    during this PREPARE module.
    ? continue
    ? cancel
    Waiting for input since May 13, 2008 10:17:35 AM
    > continue
    >> 10:17:40  PREPARE: END OF PHASE   REQIMPORT
    >> 10:17:40  PREPARE: START OF PHASE READDATA
    Trying to find archive files ...
    Extracting archive "V:\SCM2007\D51032928\UPG1\DBINDEP\MISC7000.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG1\DBINDEP\MISC7000.SAR successfully unpacked to O:\usr\sap\put.
    Extracting archive "V:\SCM2007\D51032928\UPG1\DBINDEP\MISC700X.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG1\DBINDEP\MISC700X.SAR successfully unpacked to O:\usr\sap\put.
    Extracting archive "V:\SCM2007\D51032928\UPG1\DBINDEP\MISC_SP.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG1\DBINDEP\MISC_SP.SAR successfully unpacked to O:\usr\sap\put.
    Trying to find archive files ...
    Extracting archive "V:\SCM2007\D51032928\UPG2\DBINDEP\MISC700W.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG2\DBINDEP\MISC700W.SAR successfully unpacked to O:\usr\sap\put.
    Trying to find archive files ...
    >> 10:17:50  PREPARE: END OF PHASE   READDATA
    >> 10:17:50  PREPARE: START OF PHASE READDATA_EXT
    Trying to find archive files ...
    Extracting archive "V:\SCM2007\D51032928\UPG2\DBINDEP\M_I_0002.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG2\DBINDEP\M_I_0002.SAR successfully unpacked to O:\usr\sap\put.
    Extracting archive "V:\SCM2007\D51032928\UPG2\DBINDEP\M_Q_0001.SAR" to "O:\usr\sap\put" ...
    Archive V:\SCM2007\D51032928\UPG2\DBINDEP\M_Q_0001.SAR successfully unpacked to O:\usr\sap\put.
    >> 10:17:50  PREPARE: END OF PHASE   READDATA_EXT
    >> 10:17:50  PREPARE: START OF PHASE TOOLFIX_CHK
    Correction package 'O:\usr\sap\put\FIX_SCM51.UPG' found, extracting to 'O:\usr\sap\put'
    Archive successfully unpacked.
    >> 10:17:51  PREPARE: END OF PHASE   TOOLFIX_CHK
    >> 10:17:51  PREPARE: START OF PHASE CPYFIL0_CBU
    >> 10:17:51  PREPARE: END OF PHASE   CPYFIL0_CBU
    >> 10:17:51  PREPARE: START OF PHASE EXEC_CPYFIL1_CBU
    >> 10:17:51  PREPARE: END OF PHASE   EXEC_CPYFIL1_CBU
    >> 10:17:51  PREPARE: START OF PHASE FRP_CHK
    >> 10:17:51  PREPARE: END OF PHASE   FRP_CHK
    >> 10:17:51  PREPARE: START OF PHASE UNICODELIB_CHK1
    >> 10:17:51  PREPARE: END OF PHASE   UNICODELIB_CHK1
    >> 10:17:51  PREPARE: START OF PHASE CNV_CHK_IMP
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP getconvent SCD
    >> 10:17:51  PREPARE: END OF PHASE   CNV_CHK_IMP
    >> 10:17:51  PREPARE: START OF PHASE ICNVCHK_IMP
    >> 10:17:51  PREPARE: END OF PHASE   ICNVCHK_IMP
    >> 10:17:51  PREPARE: START OF PHASE SCRIPT_CHK_TOOL3
    >> 10:17:51  PREPARE: END OF PHASE   SCRIPT_CHK_TOOL3
    >> 10:17:51  PREPARE: START OF PHASE SCRIPT_CHK_TOOL4
    >> 10:17:52  PREPARE: END OF PHASE   SCRIPT_CHK_TOOL4
    >> 10:17:52  PREPARE: START OF PHASE SCRIPT2_TST_RESTART
    >> 10:17:52  PREPARE: END OF PHASE   SCRIPT2_TST_RESTART
    >> 10:17:52  PREPARE: START OF PHASE TRBATCHK_IMP
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\DEFAULT.TPP gettrbatent SCD
    >> 10:17:53  PREPARE: END OF PHASE   TRBATCHK_IMP
    >> 10:17:53  PREPARE: START OF PHASE CLNT_CHK_IMP
    >> 10:17:58  PREPARE: END OF PHASE   CLNT_CHK_IMP
    >> 10:17:58  PREPARE: START OF PHASE INTCHK_IMP
    running S:\usr\sap\SCD\DVEBMGS13\exe\tp.exe pf=O:\usr\sap\put\bin\

  • 2007 Upgrade Error Company DB not consistent

    Hi there,
    I am currently using SAP b1 2005 server and client
    im using Sql server 2005 for for database
    while upgrading the system from 2005 to 2007
    every thing(b1 server, client,company database) upgraded succesfully
    but while loging into company it is showing error
    "The company DB is not consistent, Check the SAP Business One log file for more information [Message 131-219]"
    Thank you for your intrest in reading,
    if you encountered similar problem or you know the solution please tell the solution
    also plz tel where can i find solution for this kind of technical issues...
    Thanks & Regards
    Radhakrishnan
    in the log file the error is like the following
    Failed to read threshold from file - ReadThresholdFromFile     C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=2828     TID=2180
    30/04/2008  20:27:25:452211        Upgrade            Note           Threashold for IRU is 0.050000     C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=2828     TID=2180
    30/04/2008  20:28:16:635453        Upgrade            Error          FromVersion=680318     ToVersion=860029     UPG_DoObjectUpgradeInt 2, error in object index=276, object name=Japanese Local Era, object ID=275
    STACK:
    Frame id=00: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02DF9710
    Frame id=01: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02BCC676
    Frame id=02: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02BCB392
    Frame id=03: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02BCB30D
    Frame id=04: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02BC9344
    Frame id=05: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x0257D254
    Frame id=06: "C:\Program Files\SAP\SAP Business One\SAP Business One.exe"; base=0x00400000, offset=0x02C3EEB1
    Frame id=07: "C:\WINDOWS\system32\kernel32.dll"; base=0x7C800000, offset=0x7C80B50B
         C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=2828     TID=2180
    30/04/2008  20:25:09:463527        Upgrade            NoteLogAlways     FromVersion=680318     ToVersion=860029     Ending the company upgrade     C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=2828     TID=2904

    Radhakrishnan,
    I ran into a similar problem recently while attempting an upgrade.  I didn't find a solution to my specific problem but, I was wondering if you had run the pre-upgrade query.  There is a SAP note
    1000846 that refers to upgrade issues and the pre-upgrade query I would run this if you haven't already and see if it returns any results.
    Also: here is a link to the query directly
    [http://service.sap.com/~sapidb/012006153200000918392007E/UpgradeCheckScript_25_2004A_V.txt]
    hope this helps,
    Lucas

  • SAP Upgrade ORA-00905: missing keyword

    Dear experts,
    we have a very urgent SAP upgrade case,
    From SAP R/3 470 SR1 110 to ECC 6 EHP4 SPS09
    source system have three languages ZH EN DE,it's a
    non-unicode system,before SAP upgrade,From rscpinst, i delete language
    German and change contry code to CN,
    (China). Then there is only code page 8400,T-code: I18N check ok,now we have
    a error during upgrade,i was already replace the kernel to 385 version(640_Rel Non-unicode,TP and R3trans alreay the latest version) repeat the SHADOW_IMPORT_UPG1 step but still fail,log result as follow,the SAPKLZHSR1EHP4ERP6F8.GS1 has incomplete conversion
    but the previous log file I.E SAPKLZHSR1EHP4ERP6F7.GS1 also have incomplete conversion but no ORA-00905,we only have codepage 8400 and Non-unicode but why the log mention 4103 it's a Unicode code page,thanks a lot!
    SHDUPGIMP1.ELG
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    SHADOW IMPORT ERRORS and RETURN CODE in SAPKLZHSR1EHP4ERP6F8.GS1
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW000 SQL error 905 occured: ORA-00905: missing keyword
    2EETW000 SQL error 905 occured: ORA-00905: missing keyword
    1 ETP111 exit code           : "8"
    SAPKLZHSR1EHP4ERP6F8.GS1
    4 ETW000  22 entries for RSMPTEXTS~ imported (SAPLMCB2                                1*).
    4 ETW000   1 entry for TLIBT~ updated  (1MCB2).
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN           %) deleted.
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN           %) deleted.
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from FUNCT~ (1ANALYSE_DURCHF#HREN           %) deleted.
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN           ) deleted.
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN           ) deleted.
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '41004e0041004c005900530045005f00440055005200430048004600dc004800520045004e0020002000200020002000200020002000200020002000' -> 'ANALYSE_DURCHF#HREN           '
    4 ETW000   0 entries from TFTIT~ (1ANALYSE_DURCHF#HREN           ) deleted.
    4 ETW000  [     dev trc,00000]  Wed Sep  7 10:41:04 2011                                             815387003  1338.120210
    4 ETW000  [     dev trc,00000]     OCIStmtExecute() failed with -1=OCI_ERROR                              10  1338.120220
    4 ETW000  [     dev trc,00000]     SQL error 905:                                                          6  1338.120226
    4 ETW000  [    dbsloci.,00000]  *** ERROR => Error 905 in stmt_fetch() from oci_execute_stmt(), orpc=0
    4 ETW000                                                                                12  1338.120238
    4 ETW000  [    dbsloci.,00000]  *** ERROR => ORA-905 occurred when executing SQL stmt (parse error offset=110)
    4 ETW000                                                                                9  1338.120247
    4 ETW000  [     dev trc,00000]  sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
    4 ETW000                                                                                17  1338.120264
    4 ETW000  [     dev trc,00000]  SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
    4 ETW000                                                                                9  1338.120273
    4 ETW000  [     dev trc,00000]  TWEEN :A2 ANALYSE#_DURCHF#REN           % :A3 #?;                         5  1338.120278
    4 ETW000  [     dev trc,00000]  sc_p=0x140f618,no=67,idc_p=(nil),con=0,act=1,slen=149,smax=256,#vars=4,stmt=0x1783c10,table=
    4 ETW000                                                                                11  1338.120289
    4 ETW000  [     dev trc,00000]  Dumping DBSL stmt. cache:                                                  5  1338.120294
    4 ETW000  [     dev trc,00000]  prep=0,lit=0,nsql=1,lobret=0,xop=1,dbcnt=0,upsh=(nil),stmtp=0x1784758,rtc=0
    4 ETW000                                                                                29  1338.120323
    4 ETW000  [     dev trc,00000]  IN : cols=4,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=4294967295,rsize=28,vmax=32,bound=1,iobuf_p=0x1493510,vda_p=0x1784db0
    4 ETW000                                                                                10  1338.120333
    4 ETW000  [     dev trc,00000]       lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0                 6  1338.120339
    4 ETW000  [     dev trc,00000]  SELECT ID,OBJECT,LANGU,TYP,VERSION FROM "DOKIL~" WHERE (LANGU IN ( :A0 )) AND ID = :A1 AND OBJECT BE\
    4 ETW000                                                                                7  1338.120346
    4 ETW000  [     dev trc,00000]  TWEEN :A2 ANALYSE#_DURCHF#REN           % :A3 #?;                         5  1338.120351
    4 ETW000  [    dbds    ,00596]  ***LOG BY2=>sql error 905        performing FET        [dbds#2 @ 596]
    4 ETW000                                                                                14  1338.120365
    4 ETW000  [    dbds    ,00596]  ***LOG BY0=>ORA-00905: missing keyword [dbds#2 @ 596]                      6  1338.120371
    2EETW000 SQL error 905 occured: ORA-00905: missing keyword
    4 ETW000   0 entries from FUNCT~ (1MCB_GRAPHIC_DAILY             %) deleted.
    4 ETW000   0 entries from FUNCT~ (%MCB_GRAPHIC_DAILY             %) deleted.
    4 ETW000   0 entries from TFTIT~ (1MCB_GRAPHIC_DAILY             ) deleted.
    4 ETW000   0 entries from TFTIT~ (%MCB_GRAPHIC_DAILY             ) deleted.
    SAPKLZHSR1EHP4ERP6F7.GS1
    4 ETW000   1 entry for LDBNT~ imported (1FTI_TR_PL_CF        *).
    4 ETW000   0 d /   1 i /   0 u /   0 =   0% ucf LDBT~
    4 ETW000   1 entry for LDBT~ imported (1FTI_TR_PL_CF).
    4 ETW000   1 entry for TRDIRT~ inserted (SAPDBFTI_TR_POSITIONS                   1*).
    3WETW000 some text was mutilated during conversion from unicode to ascii in language '1'. This is the result: 'SP_JOTC          ###############'
    3WETW000 language = '1', converted from codepage 4103 to codepage 8400, incomplete conversion due to invalid chars: '530050005f004a004f005400430020002000200020002000200020002000200020003a571659a44e13664d881f75a74ec1542000200020002000200020002000' -> 'SP_JOTC          ###############'
    4 ETW000 REPOT1SAPDBFTI_TR_POSITIONS                    A replaced.
    4 ETW000   0 entries from D020T~ (SAPDBFTI_TR_POSITIONS                   %) deleted.
    4 ETW000   0 entries from D021T~ (SAPDBFTI_TR_POSITIONS                   %) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSFXXX                  1%) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSNXXX                  1%) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSN001                  1%) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSEL                   1%) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSSXXX                  1%) deleted.
    4 ETW000   0 entries from TRDIRT~ (DBFTI_TR_POSITIONSTOP                   1%) deleted.
    SAPup.ECO
    Phase SHADOW_IMPORT_UPG1:
    BLOCKED SIGNALS: ''
    SAPup> Starting subprocess 2865 at 20110907101845
    ENV: DIR_LIBRARY=/usr/sap/upgrade/upg_dir/abap/exenew
    ENV: LD_LIBRARY_PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64/server:/usr/sap/upgrade/upg_dir/jvm/jre/lib/amd64:/usr/sap/upgrade/upg_dir/jvm/jre/../lib/amd64:/usr/sap/GS1/SYS/exe/run:/oracle/GS1/102_64/lib
    ENV: NLS_LANG=AMERICAN_AMERICA.WE8DEC
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/GS1/102_64
    ENV: ORACLE_PSRV=GS1
    ENV: ORACLE_SID=GS1
    ENV: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
    ENV: PATH=/usr/sap/upgrade/upg_dir/abap/exenew:/oracle/GS1/102_64/bin:.:/home/gs1adm:/usr/sap/GS1/SYS/exe/run:/opt/gcc295/bin:/opt/gnome/bin:/usr/games:/usr/bin/X11:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/global_lx/bin:/usr/global/bin
    ENV: SAPSYSTEMNAME=GS1
    ENV: auth_shadow_upgrade=0
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPDAT
    ENV: dbs_ora_tnsname=GS1
    EXECUTING /usr/sap/upgrade/upg_dir/abap/exenew/tp (/usr/sap/upgrade/upg_dir/abap/exenew/tp) pf=/usr/sap/upgrade/upg_dir/abap/bin/SHDUPGIMP1.TPP put GS1
    This is /usr/sap/upgrade/upg_dir/abap/exenew/tp version 376.03.38 (release 701)
    This is /usr/sap/upgrade/upg_dir/abap/exenew/R3trans version 6.14 (release 701 - 03.06.11 - 17:57:00).
    2EETW000 SQL error 905 occured: ORA-00905: missing keyword
    2EETW000 SQL error 905 occured: ORA-00905: missing keyword
    /usr/sap/upgrade/upg_dir/abap/exenew/R3trans finished (0008).
    ERROR: stopping on error 8 during SHADOW IMPORT
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    stopping on error 8 during SHADOW IMPORT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 8
    WARNS: Highest tp internal warning was: 0118
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    Process with ID 2865 terminated with status 8
    B.R
    Lance.
    Edited by: Yen on Sep 7, 2011 8:11 AM

    Hello,
    Following upg master was used -
    51036889_1 BS 7 SR1 Upgrade Master 1/2
    51036889_2 BS 7 SR1 Upgrade Master 2/2
    And the kernel dvd used was NUC -
    51036767_4 BS 7 SR1 Kernel 7.01
    After successful upgrade to ecc6 EhP4, Unicode conversion was done later with UC kernel DVD (during IMPORT)
    Thanks

  • Sap Payroll error log report

    Hi All,
    We are developing Report on SAP Payroll log with the error message . Is any table exist in SAP where we can get the standard error message repositery and then convert it in the User freindly error message ?
    Thanks
    H

    Hello hg,
    Before developing report on SAP Payroll error log I suggest taking a look at below blog. There is a new functionality from SAP to improve payroll data validation and they are calling it "Control Center Add-On".
    This is going to be a free add on for anyone who is on EHP7 and NetWeaver on 7.4 release. The general availability is June 2nd 2014.
    Improve payroll data validation with SAP Payroll control center add-on
    Hope this helps.
    Thanks,
    Hemanth Jamithi.

  • How to catch SAP application errors in BPM.

    Hi,
    I have a IDOC to Soap Sync Scenario where I send the message to a Webservice. I have used a BPM since we need to catch the resposne of this message and map it to a RFC. For ex if I get a success resposne I need to map success if not than I need to catch the error and map it to the RFC. Now here in some cases like if the target system (webservice) is down than XI raises a sap application error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Normally XI stops the process in these cases and does not proceed to the next step but I need to catch this message and map the content in the AdditionalText to the target RFC. Can anyone let me know how to catch this SAP Application Error in BPM and map it to the RFC.
    Thanks,
    Bhargav

    Hi Gaurav,
    As I have mentioned I need to catch the application error in the BPM. If you see the discussion that is mentioned after the blog you have mentioned it is stated that the fault messages or the application error cannot be caught in BPM.
    In the blog that you stated we can catch the fault message and map it to a message structure but only to that extent after that it would stop the BPM process at that step but would not proceed further as shown in the screenshot given in the blog it would fail as "application error restart not possible".
    I need to proceed further and capture this error to an RFC Structure and call a proxy.
    Here after the error it does not proceed to the next step.
    Thanks,
    Bhargav

  • Sap-plugin error when deploying a par file

    Hi,
    We are getting sap-plugin error when ever we are trying to deploy the application to the portal.Even after restarting the server the problem is not getting solved.
    The application we are trying to deploy is perfectly alright as we tested the same earlier.
    Can any one provide some inputs to solve this issue.
    To add some more points
    In brief ,we are not able to deploy our Portal applications . It is giving us error like this
    NFO: Detected Portal Archive File: com.abc.par
    INFO: Deployment failed - exception caught: Application upload failed: com.abc.par - more detail at: /usr/sap/POD/JC30/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.abc.par.log…
    We got this error many times , but after some time , when we restart the portal it works,
    this time it is not working even after I restarted the server many times

    hi all, i have same problem with upload of .par file, it doesn't work both from the portal and from the NWDS,
    here i post first part of log file:
    this is   sap-plugin.log :
    [16.05.07 / 13:05] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Response: <?xml version="1.0" encoding="utf-8"?>
    <query-result><info><type>1</type><message>Detected Portal Archive File: test.par</message></info><info><type>1</type><message>Deployment failed - exception caught: Application upload failed: test.par - more detail at: C:\usr\sap\SWB\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\test.par.log</message></info></query-result>
    this is  test.par.log :
    2007-05-16_12-03-10
    Application upload failed: test.par
    com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: test.par
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
         at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException
    Cannot assign a zero-length byte array to host variable 18.
         at com.sapportals.portal.pcd.pl.PlFactory.handleUnexpectedSQLError(PlFactory.java:2490)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:652)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1360)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1118)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1076)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:846)
         at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:185)
         at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:188)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:244)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:133)
         at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:500)
         at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:425)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:426)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:446)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:460)
         at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1317)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:501)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:663)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:668)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.updateObject(ApplicationRepositoryService.java:717)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeApplication(ApplicationRepositoryService.java:389)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:306)
         ... 34 more
    Caused by: com.sap.sql.log.OpenSQLException: Cannot assign a zero-length byte array to host variable 18.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.dispatch.BlobHostVariable.setBinaryStream(BlobHostVariable.java:143)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:776)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:401)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.storeAttribute(AttributeHeadersTable.java:431)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:248)
         at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:541)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:616)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:640)
         ... 54 more

  • SAP Upgrade  from SAP R/3 4.6 C to ECC6.0,  Delete DMC componenet

    Dear All,
    We are upgrading SAP from R/3 4.6C  to ECC6.0 . Our client has installed DMC in 4.6C as a "Main transport" request .   DMC becomes an Add-on tool in ECC6.0 . SAP pepare phase recognize DMC is already installed in 4.6C  and required  upgrade CD 51031689.  Upgrade CD 51031689 is not available in marketplace and required an restricted access . Actually  we are not using DMC component and would not  planning to upgrade to DMC 6.0 . SAP Upgrade Prepere phase has  facility to mark as "Delete" for unwanted add-on componenets. We are able to select "delete" radio button for other Add-on compoenents  but unfortunately "IS_SELECT" phase doesn't provide me an option to select "delete" radio button .Any  help/suggestions are highly appreciated.
    Thanks
    Mahendra

    Hi
    Try this link, which will give functionality enchancements between different versions of SAP.
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Regards
    Ramakrishna

Maybe you are looking for