Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Similar Messages

LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

Dear all,
We have received the below errors during our upgrade from 4.6C to ECC 6.0.
Basically we have received three types of errors:
1.
4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
2.
A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
3.
3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Can anyone help us how to solve this issues.
Thanks & Regards
Senthil

Hi,
Senthil following are ans to ur questions
1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
Refer following note for further information --
SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
This is the reason why SAP always asks you to follow a proper transport path.
4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
I hope i have answered all your queries.
Regards,
Suhas

Table Enhancement Category during upgrade from 4.7 to ECC 6.0

When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables. The enhancement category was previously u2018not classifiedu2019 on these tables.
Is this really necessary? Has anyone not changed the enhancement categories on tables that were flagged during the upgrade? Also, what happens if we select the wrong enhancement category?

Jane,
This is what SAP says,
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

Unicode error while upgrading from 4.6 to ECC 6.0

Dear All,
I am getting unicode errror while upgrading from 4.6 to ECC 6.0, when iam trying to open downloaded file in excel.
In debugging, error occurs while executing statment "CALL METHOD OF obj_ex_sheet " in the code given below:
FORM open_downloaded_file_in_excel            *
FORM open_downloaded_file_in_excel.
DATA:
    lv_ole_books       TYPE ole2_object,
    lv_ole_sheets      TYPE ole2_object,
    lv_subrc           LIKE sy-subrc,
    lv_title(70)       TYPE c,
    lv_text1(70)       TYPE c,
    lv_text2(70)       TYPE c.
start excel
CREATE OBJECT obj_ex_sheet      'EXCEL.SHEET'.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
CALL METHOD OF obj_ex_sheet     'Application' = obj_ex_app.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
SET PROPERTY OF obj_ex_app 'Visible' = 1.
open data file: main file
CALL METHOD OF obj_ex_app        'Workbooks' = lv_ole_books.
CALL METHOD OF lv_ole_books      'Open'       = obj_ex_wbook
    EXPORTING #1 = gv_filename
              #2 = 2
              #3 = 0
              #4 = 1
              #5 = 0
              #6 = 0
              #7 = 1.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_wbook.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
FREE OBJECT lv_ole_books.
CALL METHOD OF obj_ex_wbook      'Worksheets' = lv_ole_sheets.
CALL METHOD OF lv_ole_sheets     'Item'       = obj_ex_wsheet
    EXPORTING #1 = 1.
FREE OBJECT lv_ole_sheets.
GET PROPERTY OF obj_ex_wsheet    'UsedRange' = obj_ex_usedrange.
CALL METHOD OF obj_ex_usedrange 'AutoFormat'
    EXPORTING #1 = 18.
SET PROPERTY OF obj_ex_wsheet    'Name'       = sy-tcode.
FREE OBJECT obj_ex_usedrange.
PERFORM free_ole_objects.
CALL FUNCTION 'FLUSH'
       EXCEPTIONS
            OTHERS = 0.
ENDFORM.
regards,
Divya

hi,
In the OPEN DATASET STATEMENT ADD THE ENCODING ADDITION IN TEXT MODE.
Regards,
Balakumar.G
Reward Points if helpful.

Schema error after upgrade from 4.6C to ECC 5.0

Hi all,
We have recently upgraded from 4.6C to ECC 5.0. We are having problem in payroll run. When I did a syntax check in schema, I got "UDPM" rule doesn't exist. I checked, this rule is present in 4.6C. This is the standard rule. If I am right, it should have come with upgrade right?
or SAP has changed this? From where Can I get the info about this?
Also similar error I got in Function 'USTAX' parameter 3 is not allowed. If I remove that parameter, I don't know what is the implication of that.
I checked for SAP notes. I did not find anything.
Please let me know if any of you have come with such situation.
Thanks in advance.
Sarika.

Hi Sarika,
We are also in a similar transition i.e. 4.6C to mysap Ecc5.0 . But we are on Canadian Payroll.
I had search OSS and got a PDF document regarding " Upgrading to SAP R/3 Enterprize - A User Guide to Canadian mysap HR Customers" . U may be can find a similar one for US payroll. I can give u mine, but it wont be of any use as it is for Canadian Payroll.
In Canadian mysap Upgrade , the function P0224 has been replaced by function KXDTM . Although P0024 is still in used in Schema K00T for conversion purposes.
Regards,
Jay Gandhi

Unicode error while upgrading from 4.7 to ECC 6.0

Hello all,
I am upgrading our SAP from 4.7 to ECC 6.0. while doing so we had folllowing error in the adjoinig statement of Search.
Error : Table I_VBLS must have a character line type (data type C,N,D,T or string)
Statement :
W_TMP10 = I_VBLS-VBELN.
SEARCH I_VBLS[] FOR W_TMP10 STARTING AT 1
IF SY-SUBRC NE 0.
   EXIT.
ENDIF.
Now I tried to remove this error by putting a loop on internal table I_VBLS and inside it concatenating the header line with a Field symbol and after that to a string variable. Then I used SEARCH statement for the same string. but unfortunately this is changing the functionality of the program by large extent. Does anybody know the exact code snippet to replace search Internal Table
Edited by: Aalhad Deshpande on Feb 23, 2009 3:18 PM
Edited by: Aalhad Deshpande on Feb 23, 2009 3:19 PM

Hi,
Try to use this method.
CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
E:G :-
        WRITE crlf TO i_linea-linea2.
In this case also their are not mutually convertable. try to use this method and let me know
        CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
          EXPORTING
            IM_VALUE               = crlf
          IMPORTING
            EX_CONTAINER           = i_linea-linea2
          EXCEPTIONS
            ILLEGAL_PARAMETER_TYPE = 1
            others                 = 2.
Regards,
Sathish

Error in upgrade from 4.6 to ecc 6.0

Hi all,
We are upgrading from SAP 4.6 c to ecc 6.0 anr we are getting the following messages
UPGRADEPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR700WG4.ORD" < Long text:
Cause
During the upgrade, a message relevant for postprocessing was writte to a log file. This message is not dealt with until the end of the entire upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by R3up.
What to do
Note the messages following this message and proceed according to the instructions.
A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_CONFIRM" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_UPDATE" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZWORKORDER_UPDATE" must still be migrated
1PEPU203X> Messages extracted from log file "SAPR700ZG1.ORD" < Long text: see above
A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
UPGRADEPHASE JOB_RDDNTPUR
1PEPU203X> Messages extracted from log file "RDDNTPUR.ORD" < Long text: see above
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Long text:
Cause
A runtime object was found for a table which is unknown in the ABAP Dictionary. The table contains data, which is why, as a precaution, the runtime object was not deleted. Since there is a runtime object, this means the table was once create in the ABAP Dictionary. The fact that the table can no longer be found in the ABAP Dictionary could be due to the following reasons:
It is a customer-specific table which was created when the correction system was switched off.
Depending on the history of your system, there may also be SAP tables which were not deleted completely, or for which only the runtime object was delivered without the related definition in the ABAP Dictionary
System Response
What to do
RESET N1
Customer-specific tables
If it is a customer-specific table, and you still need the data, try to restore the table in the ABAP Dictionary.
Note the specified table type
when you do this (transparent table, pool table, and so on). The table may still, for example, be contained in the version database.
You can access version management through the menu "Utilities" in the in the ABAP Dictionary (transaction SE11).
You may also still have a copy of the system that still contains the table definition. You can also display the runtime object and create the table according to the field names, types and lengths specified in the definition. You can display the runtime object in the menu "Extras" of the database utility (transaction SE14).
Tables in the SAP namespace
Search for notes on these tables in OSS using the key words RDDNTPUR and TG447.
3PETG447 Table and runtime object "STGLTRAN" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLEVNTSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLTOBJSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLTRANSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIBAN_ACTIVE" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "ZPH_RESS_STATUS" exist without DDIC reference ("Transp. table")
Long text: see above
Please suggest what to be done in these cases.
Thanks

Hi,
I think you have some BADIs or other enhancements donne in 4.6, whn tried to migrate to 6.0 causes this. Pls check whether all these objects are available/changed in 6.0.
Regards.
Renjith Michael.

SPAU / SPDD Transport During Upgrade from 4.6C to ECC 6.0

We are currently upgrading R/3 4.6C to ECC 6.0 SR2. During the DEV upgrade, we performed Dictionary Objects adjustments before ACT 7.00 and SPAU adjustments at the end of the upgrade. All the adjustments are collected in a transport.
I read in another thread that we will have to choose 'SELECT FOR TRANSPORT' button in SPAU and not release it. Then, continue with the upgrade. And in the same thread, it is also mentioned that DDIC object modifications should not be handled through transports.
Now, my question is, if I have collected the SPAU adjustments in a transport and continued with the upgrade without choosing the 'SELECT FOR TRANSPORT' button, can I do it after I complete the upgrade before I continue with QAS upgrade? Will the upgrade still automatically detect the transports and move them? And, my other question is, if DDIC modifications are not supposed to be dealt through transports, how else should they be worked upon?
Your response ASAP will be rewarded properly.
Thank you.

Nick, thank you for the reference. Even though I had gone through this note before, I couldn't apply this note because, this note was refering to "R3up" which, I guess, is no more used. "SAPup" is the program currently in use. Also the location mentioned in the note to execute "R3up" is "//usr/sap/put/exe" but, "SAPup" is located under "//usr/sap/put/bin/". So, I am not sure if there is any new notes refering to this. One other question I have with regards to this note is, one of the arguments for the command R3up is, "REL". For SPDD, the note suggests to use target release. And for SPAU, the note suggest to use the release mentioned in the DDIC activation phase.
In my case, I am upgrading from 4.6D (kernel) to 700 (kernel). The DDIC activation shows ACT_700. So, I am sure I would use "700" as value for "REL" for SPDD. But, am I supposed to use "46D" for SPAU? or should I use "700"?
Thank you.

Error during upgrade from OBIEE 10G to 11G

Hello All
I ran into this issue while trying to upgrade my 10g RPD and catalog to 11.1.1.7
After installing 11G, I launched the upgrade utility from Oracle_Common/bin/ua in linux.
I am getting the below error:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Based on the Oracle Doc. it has the following desc:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.
Action: None.
Level: 1
Type: ERROR
Impact: Upgrade
So what should I do to resolve this issue?
Thanks in advance

Hi,
First of all i am not familiar on linux box.
I tried in windows environment the rpd is deployed with out any errors.
But i ran the ua.bat file in the following path
\MWHOME\Oracle_BI1\bin\ua.bat.
while i am running in oracle_common\bin\ua.bat is not responding in my local system.
Please Mark if it helpful.
Thanks

Structure SI_BBSEG not found during upgrade from 4.6C to ECC 6.0

Hi
We are upgradingour SAP system from 4.6c to ECC 6.0 and we are having an issue while generating the programs, error says '.INCLUDE SI_BBSEG ' not found. It seems like structure SI_BBSEG was not created by SAP'. How would i resolve this issue? i couldnt find any OSS note on this. Please advice.
thank you,
- A

Anil
SI_BBSEG is Include structure of BBSEG & comes already included in it as std SAP. (u can see it in SE11 >> BBSEG)
It does not exist till you want to enhance BBSEG & add your custom fields. Normally those fields will be added to Std SAP screens as custom enhancements . You can go to SE11 & double click; it will ask Do you want to create ?
What is the process you are following for moving Enhancements from 4.6 to ECC6 (user Exits, screen exits) ? If this SI_BBSEG exists in old system, then there must be std screen enhanced which uses the fields of this structure. There could be some programs too which are using this structure while creating FI Documents using std BAPI. recomended that these should move to ECC6 together.
If you have not enhanced BBSEG in 4.6 then refer note : 590977

Error during upgrade from sap R3 4.7 ext 110 to ERP6 EHP4

Dear all
we doing an upgrade in test server to ERP6 with EHP4,source release is sap Entreprise 4.7 110.We have copied all the required DVDs to the server .During the configuration phase while giving the EHP package we got the error.
EHP_INCLUSION.log details
4 ETQ233 Calling function module "SPDA_PREPARE_PATCH" by RFC
4 ETQ234 Call of function module "SPDA_PREPARE_PATCH" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20100915210509
2 ETQ732 Package descriptions uploaded successfully
4 ETQ399 Looking for SAINT package for 'SAP_APPL' ...
4 ETQ399 R3upReadNewPackages:
4 ETQ399   patchType='U', langVect='DE'
4 ETQ359 RFC Login to: System="MBD", Nr="00", GwHost="saptest", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "spda_read_new_packages" by RFC
4 ETQ399   ismovesVersion='0'
4 ETQ399 R3upReadNewPackages: exit: rc=0
4 ETQ399      Found: name = 'SAP_BS_FND', release = '701', package = 'SAPK-701GGINSAPBSFND', type = 'AOX'
4 ETQ399             (not usable, different component
4 ETQ399 ... No matching package found.
Is this related to the current SAP_APPL support pack version ?.currently we have
SAPKH47031 SP 31 for SAP_APPL 4.70
Regards
Shahnas.S

> i have few questions regarding above
(Almost) all of your questions are answered in the note:
> 2.Do wee need to apply the above note for non-unicode upgrade
<...>
Even on non-Unicode system you should replace all matchcodes that are still required by search helps.
<...>
> 3.Note 1330256 recomends to apply support pack or to apply the Note 1330256 ,but we can do it only at upgraded version.
Yes - it avoids dumping with the dump mentioned in the note
> 4.How to identify the matchcodes
<...>
You can use the program TWTOOL01 to determine the existence of matchcodes.
<...>
> 5.How to delete them
<...>
You can then use the function module DD_MCOB_DEL to delete matchcode objects, and the function module DD_OBJ_DEL to delete matchcode IDs.
<...>
> 6.Impact of deleteing matchcodes
None since they were replaces by search helps.
Markus

M_vmvah missing during upgrade from 4.6C to ECC 6.0

Hi,
After upgrading, our Z programs are having compilation errors due to missing table m_vmvah. Is there any replacement table for m_vmvah in ECC 6.0? Thanks.
Regards,
Abner

1. Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.
2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.

Error during upgrade from Deployment manager.

My OWB 10.1.0.2 design repository is on an Oracle 10.1.0.2 database running on Solaris 9, using WE8ISO8859P15.
I created a new 10.1.0.2 runtime database with UTF8 character and deployed all the objects successfully.
But now, when I run the upgrade, it gives me the following error:
123
RTC-5351: A serious error occured whilst generating the Impact Report. Please review the Runtime Service Log.
In the runtime service log, the following message shows up:
2006/05/07-13:21:58-PDT [16FE0F4] java.lang.ArrayIndexOutOfBoundsException: 123
at oracle.net.nl.NVTokens.parseTokens(Unknown Source)
at oracle.net.nl.NVFactory.createNVPair(Unknown Source)
at oracle.net.nl.NLParamParser.addNLPListElement(Unknown Source)
at oracle.net.nl.NLParamParser.initializeNlpa(Unknown Source)
at oracle.net.nl.NLParamParser.<init>(Unknown Source)
at oracle.sysman.vdb.VdbUtil.findInTNSFile(Unknown Source)
at oracle.sysman.vdb.VdbUtil.findInTNSNAMES(Unknown Source)
at oracle.sysman.vdb.VdbUtil.buildConnectDescriptor(Unknown Source)
at oracle.sysman.vdb.VdbUtil.buildConnectDescriptor(Unknown Source)
at oracle.sysman.vdb.VdbSession.buildConnectionInformation(Unknown Source)
at oracle.sysman.vdb.VdbSession.establishConnection(Unknown Source)
at oracle.sysman.vdb.VdbSession.<init>(Unknown Source)
at oracle.sysman.vdb.VdbSession.<init>(Unknown Source)
at oracle.sysman.vdb.VdbAutoCommitSession.<init>(Unknown Source)
at oracle.sysman.vdb.VdbSessionFactory.getNewAutoCommitSession(Unknown Source)
at oracle.sysman.vdb.VdbSessionFactory.getAutoCommitSession(Unknown Source)
at oracle.sysman.vdb.VdbSessionFactory.getAutoCommitSession(Unknown Source)
at oracle.sysman.cmSDK.CMClient.getDBSession(CMClient.java:479)
at oracle.wh.runtime.platform.adapter.odb.OdbCMUpgradeAdapter.prepare(OdbCMUpgradeAdapter.java:91)
at oracle.wh.runtime.platform.service.controller.DeploymentController.prepare(DeploymentController.java:101)
at oracle.wh.runtime.platform.service.controller.DeploymentController.prepare(DeploymentController.java:27)
at oracle.wh.runtime.platform.service.DeploymentManager.run(DeploymentManager.java:41)
at java.lang.Thread.run(Thread.java:534)
Please help.

Hi
Is there any script which was generated by the OWB in the upgrade process?
Maybe OWB generates a drop and create script instead of alter script.
But I suggest to you to desing and manage the database modell in a design tool (Deveploper, PowerDesigner, ...) and generate the changes from this tool.
Ott Karesz
http://www.trendo-kft.hu

HR Objects in SPAU during upgrade from 4.6C to ECC 6.0

Hello,
We are in the process of upgrading and have come to the point in SAPup where we need to address all customizations in SPAU. There were several HR objects displayed (both logical and physical info objects), and from what I have been reading, there should be no HR objects listed. I followed the instructions in OSS note 519678 to remove unnecessary HR objects from table SMODILOG using program H99PDSY_REPAIR_SMODILOG. This did remove quite a few, but I am still left with some.
Can anyone provide information on what I should do to resolve this issue. I thought that maybe, the information that HR objects should not be in SPAU could be wrong, so I attempted to reset one object to original. When I did this, it prompted me to create a new "customizing" transport request, when all of the other objects related to SPAU were put into a "workbench" transport. I also understand that there should only be one transport for all SPAU adjustments, so this further makes me believe these objects should not be showing up.
Thank you,
Leeanna

Hello Leeanna,
Apply this note. and execute the mentioned report, this deletes all the HR objects
Note 634146 - SPAU: Objects from the customer namespace in SPAU

Find button issue in tool bar during upgrade from 4.6c to ECC 6

Hi All,
I came across one issue during the upgarde.
In new system ECC 6:
When i run the transaction IW51 then give the notification type SE(service notificaton) and then hit enter key.
It leads to next screen there enter the value in the FUNCTIONAL lOCATION field some ex 9000004 and
opposite to that field there is a structure list icon.
Clicking that icon it leads to a structure list.
My issue is: the FIND button and FIND NEXT button are disabled in the menu bar.I need the both buttons to be active
When i seen in old system i.e 4.6c
FIND button and FIND NEXT button are active.
I made little change in the new system in include MIHIXF82 as shown below.
SET PF-STATUS 'MAIN' ."EXCLUDING gt_excl_tab.
I commented the EXCLUDING gt_excl_tab.
Now FIND button and FIND NEXT button is active but when i click the FIND button there is no pop up is displayed.
Usually pop up is displayed when we click FIND button in that we can enter the value which we have to find out.
Regards
Jai
Edited by: Jayanth16 on Jan 28, 2010 8:07 AM

Hi,
In that program gui status MAIN is used.
When i see that gui status and in FUNCTION KEYS the FIND button and FIND NEXT button
the function codes are in orange color.Remaing BACK,EXIT,and CANCEL button function code are in white color.
Whether the orange color indicates is in inactive mode?
If so how can i activate those Function codes?
Regards
Jai

Error during Upgrade from 4.6c to ECC 6.0

Similar Messages

Maybe you are looking for