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 .

Similar Messages

Need knowledge on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

please give me some ideas and useful links on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

Hi Jaya,
Not very clear with your question.
Are you looking for changes in areas od ABAP reports & SAP query when we upgrade SAP from 4.7 to ECC 6.0 ??
If the response is YES, then please refer to SAP solution browser www.sapsolutionbrowser.com
Define source release and target release .
You will get module wise details on new features for target release.
Hope this helps.
Regards,
Deepak Kori

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

Dear All,
I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
Please let me know if you have any ideas on the above questions.
Thanks & Regards
Ravikiran

Hi,
I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
Thanks
Sunny

SAP Upgrade 4.7ee to ECC 6.0

Dear experts
we are planing SAP Upgrade 4.6 C to ECC 6.0 on windows 2003 Server with Oracle Database please anybody explain prerequests and post upgrade activities and upgrade phase's.
what are the phase's are inportant...to monitor
Regards
Bandla

Hi Bandla,
Please check this beautiful [WiKi|https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/learning+map].
Regards,
S.Manu.

Add-On ST error in Prepare Upgrade from 46D to ECC 6.0

I have getting Error Add-On ST 2D, and undecided, I don't know what to do, I had installed Solution Manager for 46D and ST 2D, If anybody has this situation, how do I download the Add on
I will appreciate any help on this matter.
Thanks
Jagraj Dhillon

> Dear,
>
> I believe you have the addon component 'SAPKITL02D
> "SAP Solution Manager - Installation 4.6C (02D) "
> installed in 4.6C , is that right?
>
> Since the ST (Solution Manager) cannot be upgraded
> from current version
> to the latest using the R3 upgrade, You need to
> Deinstall the addon. (with import of SAPKITL029 in
> SAINT) Please reset prepare as described in the
> upgrade manual (SAPup reset prepare + empty DIR_PUT)
> and next import the request SAPKITL029 using SAINT
> which should take care of the de-installation of ST
> 02D.
>
> I hope this helps.
>
> Lucio Rodrigues
> SAP AGS
Hello, Lucio. I am in the same boat, only with R/3 version 4.6C, and ST 0.2C (SAPKITL02Y). Would the SAPKITL029 work for me as well, or is there another SAINT package designed to remove ST 0.2C?
SAP support has not been very helpful to this point. If you have an import which would help with uninstalling the addon, please email it to [email protected], or please let me know where to download it if it is available for download.
Mike McCrory - BMW Global Data Center America's
Message was edited by:
McCrory Michael

Pipeline withdrawal fails after SAP upgrade 4.6B to ECC 6.0

Hi experts,
our customer has been using Water as a pipeline material for years now, but after upgrade to ECC 6.0, we receive error message M7009 (Special Stock P not defined) when trying to perform a goods issue to process order for this (same) article.
Strangely, the error message only comes up when we use COR6 or MIGO's 'Goods issue to order' or 'to reservation', and not when we do 'goods issue other', manually take movement type 261 P, and check.
Now since the only difference I can see at this point is the absence of the Reservation tab in MIGO, I assume the reservation has something to do with this error.
Any ideas?

Hi,
before confirming production order via Co15, in goods movements, there is storage location populated for this material. If I delete SL for it, then goods movement is succesfully done.
In ecc 5.0, SL is also populated but it is working fine.
Any idea?
Edited by: Alberto Emilio Gallardo Doñate on Apr 22, 2010 12:21 PM

SAP Upgrade 4.6C to ECC 6.0

Hi,
We are performing the SAP security upgrade from 4.6C to ECC 6.0 for our client.
In the 4.6C landscape the DEV, QAS & PRD systems are not in sync. To add, the upgraded DEV system has already been built in the ECC 6.0 landscape. This has resulted in the DEV ECC 6.0 system not containing all the roles which are present in the 4.6C production system.
My question is how do I bring all the roles & authorizations from the production environment in 4.6C into the DEV ECC 6.0 system so that I am assured I have the correct outputs when I run the SU25 step in the DEV ECC 6.0 system?

Hi,
You have not followed the upgrade cycle. You should have done onne test upgrade by copying the Production database.(system copy). Then you would have copied all the application data as well as roles. Then you should have done the upgrade.
Anyway now you have one option. You have the Quality server. Now move all the roles to quality server and then do the upgrade. Else copy the production data and then do the upgrade. This is will reduce your efforts while doing production upgrade. If helpful please do award points.

Error in SAP R/3 4.7 & ECC 5 versions - while installing Databse Instance

Hi
I have installed Windows 2003 in my Laptop . Then I configured MS Loopback adapter and assigned an IP address. Then I changed the Virtual Memory Then I installed Java in C drive & gave the path in System properties. Then Installed Oracle 9i and also the Patch in drive D. Then I installed the Central Instance successfully in drive D and while installing the Database Instance, I'm getting an
Error saying : _NODE D:\SAP\DATA_ doesn't exists ._*
Can anyone help me in this error ? I can't guess why this error is coming & what to do to solve this error .
Any help is very much appreciable.
Regards
Kannan

Hi Kanan,
I think this is because the problem with the software dump.Copy it properly to local drive and retry the installation.
http://www.sapdb.info/wp-content/uploads/2009/07/SAP-47-Installation-Tutorial.pdf
http://www.sapdb.info/wp-content/uploads/2009/04/installation_of_mysaperp2005.pdf
Regards
Ashok Dalai
Edited by: Ashok Dalai on Jul 30, 2009 7:43 AM

Error in upgrade from 46c to ecc 6.0

hi experts,
we are facing an error at the time of upgrade from 46c to ecc 6.0 in the phase JOB_RSUPGAIMEXE.
did anyone face this error anytime during upgrade on windows plotform?
Please let us know your comments..
regards
raghu

Hello,
Can you please look in the /put/log directory and copy the error from the appropriate log file. You should find a log file with a name similar the to upgrade phase that is causing the error.
Thanks
N.P.C

SAP upgradation ?

hii
What will be the major work for MM consultant in SAP upgradation (4.5 to ECC 6.0).
What is the latest version of SAP??
Explain in more detail about MM consultant roles and responsibilities n SAP upgradation (4.5 to ECC 6.0).
Thanks

Normally upgradation project is basis driven project. Basis guys will prepare the system taking into consideration of all the aspects of the system. This itself is project called upgrade. Upgrading project mostly involves testing with the existing system with the new system. SAP already released the release notes for this Upgrading ECC 6.0{example 4.6C to ECC 6.0}. (1).Functional consultant have to do unit test/Integration test/Regression test in new system based on the business process documents prepared for your present system. (2).Functional consultant mostly encounter Interface issues (If exist)/Authorization issues/Enhanced naming issues/Usage issues. (3).Example:In older version you have to do external configuration for CIN. However .In ERP 2005, It is already in built. Hence Knowledge of CIN will be more than sufficient to manage the CIN issues. (4). More over Functional consultant must be very confident in the business process. Unless you will receive many UAT issues. (5). Whenever Functional consultant do unit test and Integration test, use user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id. Using this new id you do the Regression testing. This will avoid many problems. (6). Another Important, big issue is patch work information. For example After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system. These patches are already in built in ECC 6.0, hence you will get diff.result when you do testing. If such a case, advices the user about the patch work, and proceed. In most of my cases, SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
Check this link for further details:
Re: upgrade from 4.7 to 6.0
Edited by: Afshad Irani on Aug 9, 2010 11:35 AM

SAP Security Upgrade 4.6C to ECC 6.0

Hello Gurus,
we are upgrading our systems to ECC 6.0 from 4.6C.
in SU25 step, do i need to manually go into every role and find the differences in Field values ?
there are more than 2500 roles and its becoming tedious task.
Is there any easy or other procedure available for the same ?
Regards,
Chaitanya

There are many tricks you can use to shave a role upgrade down to about 2 day's work, but day 1 is during the implementation design way back when to consider upgrades much later on...
Just knowing that you have 18k roles and 2500 turned red in step 2a is not enough infos to give you any efficient advice (I am not talking about your time... ;-).
What is however obvious is that between 2a and 2c there is 2... ah...?!?! That is your next closest catalyst, but dont hit the "accept SAP data" button unless you have not done any changes in SU24!
Some other key figures for upgrades are:
- Number of roles with distinctly different menus.
- Number of changed auths which are not copies.
- Number of manual auths needing manual adjustments.
- Obsolete and disabled objects.
- Security patches for unnoticed missing auth-checks.
- Cut-over, development freeze and parallel maintenance time period.
Cheers,
Julius

SAP Crystal Report 2013 SP03 - Connection error with SAP ECC tables, clusters

Hi,
I'm trying to connect SAP Crystal Report 2013 with SAP ECC but I'm getting below error. I've read some where that We need to install SAP integration kit but SAP BI 4.1 it comes default, also had to install the ABAP cystal report transport - How to do Install this on SAP side -
and on the ECC side we had to develop Crystal Authorization - how to develop this?
Can someone screenshot of these steps and please suggest if something else can be done.

Hi Pawan,
Search for the error and you should see many threads for this issue.
Anyway, this is what I found:
logon failed. you do not have the necessary rights to design reports
Crystal Reports 2008 and BW - Installation and Configuration - Business Intelligence (BusinessObjects) - SCN Wiki
The wiki should have answers to all your questions regarding Transports, Authorization et al.
-Abhilash

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

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

Similar Messages

Maybe you are looking for