Upgrade Media list Ehp 4 or ECC 6.0 SR3
Hello All,
We are upgrading to ECC 6.0 with Ehp 4 and have ordered media from SAP. We have received upgrade master, upgrade export of Enhancement package 4 (i.e.) 51036889 and 51036903. Can we proceed with this or should we order for upgrade master and upgrade export of ECC 6.0 SR3 (i.e.) 51033520 and 51033501?
Also I understood that Ehp 4 can be included with patches during upgrade. Please clarify
Regards,
Anand
Hi ... generally when i am doing upgrade of ECC 5.0 to ECC 6.0 ehp4 UNICODE system . i required the followng media.
1) Instmaster
2) Exports
3) Kernel
4) Language dvd's
It depends on you SAP Release, OS & DB.
Our source release is 4.6c
Again is your 4.6c system Unicode or NON-Unicode or MDMP.
based on all this & further requirtments we can download media.
-Rahul
Similar Messages
-
Check List for Functional Upgrade from 4.7 to ECC 6.0
Hi Gurus,
Cany anybody tell me what is the check list for SAP SD Functional Upgrade from 4.7 to ECC 6.0.?
My Email : [email protected]
Points for sure for useful answer
Venkat
Edited by: Venkat Goteti on Feb 4, 2008 5:34 AMIf it is possible can you send me file to [email protected]
-
An upgrade of ERP SAP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10 is being planned in the company I work for. However, I don´t know what the benefices are to implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version ECC 6.0 EHP 7 to ECC 6.06 EHP 10?
Regards, AlejandroHi _Miguel
I am going from ECC 6.0 to ECC 6.06. However, I don´t know what the benefices are to implement this upgrade so I wonder if someone knows benefices of upgrading SAP ERP from version 6.0 to 6.06
regards, Alejandro -
After upgrading from 4.6C to ECC 6.0 templates not working in smartform
Hello,
After upgrading from 4.6C to ECC 6.0 templates not working properly in smartform, although value is flowing to the point the template is getting called and inside the template there are text elements where placeholders are kept to display the value, when the print is taken there are no values being displayed by the text elements.
Please note - Text elements doesnot have any conditions present in the condition tabstrip.
Thanks,
AbhishekHi,
After the upgrade, you will have to do the security upgrade.
Please follow these steps.
1. Go To SU25
2. Run step 2A to 2D.
3. In step 2C, you shall get the list of all the affected roles.
Click on first role. It will take you to authorizations of that role. Click on the "New" tab there to find the new objects added to the role after the upgrade.
Note: You can open the same role in the unupgraded system to check.
4. Provide the access to the required authorization objects.
5. Disable the unwanted authorization objects.
6. Generate the profile.
7. Follow the same steps for all the affected roles listed.
Please note that you will have a list of new objects added.You need to maintain them inorder to avoid any access issues.
8. After step 2C, complete 2D.
Regards,
Imran -
Upgrade from 4.7C to ECC 6.0
Hi Gurus,
I am going to do a functional upgrade from 4.7C to ECC 6.0 (classic GL, not new GL). Can someone please list me the steps that I need to do to achieve the upgrade.
I would be very grateful and would assign points as a gesture of appreciation.
Thanks
ChandanIf you are not going to implement new g/l, then all you have to do is test if all the transactions that the client is using are wokring fine in ECC 6.0 or not.Do the unit testing and integration testing and get business sign off.
Assign points if helpful -
What is the impact of R/3 upgradation from 4.7 to ECC 6 on BI
Dear all,
Can any one tell me what will be the impact of R/3 Upgradation on BI... as we are shortly going to upgrade our R/3 from 4.7 to ECC 6.
Do we need to take any precautions in R/3 and aswell as BI
Please give the information...points will be given
Regards
venuHi
Please Refer this as this vll give u the Pros and Cons for upgrade.
Refer
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) teams experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
Contents
1 Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
2 Introduction
3 Overview & Scope
4 Drivers
5 Environment
6 Resource & Timescales
7 High Level Plan
8 Summary Task List
8.1 #Support Pack Hike
8.2 #Plug-in installation
8.3 #PREPARE process
8.4 #Dbase upgrades
8.5 #System Upgrade
9 Lessons Learnt
10 Issues & Fixes
10.1 Unfixed Issues
10.2 Fixed Issues
11 Regression Testing Process
11.1 Introduction
11.2 Set up
11.3 Actions
11.4 Security
12 Transport Freeze
13 Web Applications
13.1 Dashboards
13.2 Internet Graphics Server (IGS)
14 Detailed Task Lists
14.1 Support Pack Hike (detail)
14.2 Plug-in installation (detail)
14.3 Dbase upgrades (detail)
14.4 PREPARE Process (detail)
14.5 System Upgrade (detail)
Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
Introduction
This Wiki contains my teams experiences in upgrading our Business Warehouse System from 3.0B to BW 7.0.
Hopefully it will be useful to anyone else who's about to embark on this. If there's anything I've missed or got wrong, then please feel free to edit it or contact me and I'll try to explain.
Rob Moore - BW Manager, Edwards Limited.
Overview & Scope
This was to be a technical upgrade of BW only. The new BW 7.0 web functionality & tool suite which requires the Java stack rather than the ABAP stack was out of scope. We had heard that the latter was where most of the problems with the upgrade lay. Our plan is to wait for this part of BW 7.0 to become more stable. Also it has a big front end change and the business didn't have sufficient resource to cope with that much change management.
Drivers
3.0B at the end of its maintenance
Opportunities to do better reporting
Options to utilise BI Accelerator
Environment
Our R/3 system was at 4.6C and was not going to be upgraded. We have APO at version SCM4.0.
Our BW system is approximately 300 GB, with 125 global users. It was at version 3.0B SP 18
We have Development, Acceptance and Production environments.
Resource & Timescales
The Project ran for 3.5 months from Feb to May 2007. We used the following resources. The percentages are the approx. amount of their time spent on the project.
Project Manager * 1 70%
BW technical team * 3 50%
ABAP coder * 1 10%
SAP Systems Development expert * 1 20%
Basis * 1 25%
High Level Plan
These are the basic areas. We planned to complete this process for each environment in turn, learning our lessons at each stage and incorporating into revised plans for the next environment. However we did the Support Packs and Plug-Ins in quick succession on all environments to keep our full transport path open as long as possible.
Upgrade BW to the minimum support pack.
Install R/3 Plug-ins PI 2004.1
Run PREPARE on BW
Dbase upgrades (Database & SAP Kernel upgrade)
System Upgrade
Summary Task List
This list contains all the basic tasks that we performed. A more detailed check list is shown below for each of the headings.
#Support Pack Hike
We moved only to the minimum acceptable SP as this seemed most likely to avoid any problems with the 3.0B system prior to the upgrade.
Apply OSS 780710 & 485741
Run Baseline for Regression tests
Full Backup
Apply SP's (we were at SP18, going to SP20)
SPAU list review
Regression testing
#Plug-in installation
Apply SAP note 684844
Import and patch Basis plugin PI 2004.1
SPAU list review
#PREPARE process
BW Pre-Prepare tasks
BW - Inconsistent Data fix
Run PREPARE
Review of results
Any showstoppers from PREPARE?
#Dbase upgrades
Database Upgrade (FixPak)
SAP Kernel Upgrade
#System Upgrade
Reverse Transport of Queries
Reconnect DAB & SAB to AAE
Run Baseline for Regression tests
Full Backup
Run the Upgrade
SPAU list review
Regression testing
Lessons Learnt
Testing is all! We picked up on a lot of issues, but would have picked up more if we'd had a full copy of our production environment to test over.
Our approach of doing a full upgrade on each environment before moving to the next one paid dividends in giving us experience of issues and timescales.
Write everything down as you go, so that by the time you get to upgrading production you've got a complete list of what to do.
We succeeded because we had people on our team who had enough experience in Basis and BW to be able to troubleshoot issues and not just read the manual.
The SAP upgrade guide is pretty good, if you can understand what they're on about...
Remember the users! The fact that the loads have been successful doesn't count for anything unless the users can see the data in Excel! There's a tendency to get caught up in the technology and forget that it's all just a means to an end.
Issues & Fixes
I've listed the main issues that we encountered. I have not listed the various issues where Transfer rules became Inactive, DataSources needed replication or we had to reinstall some minor Business Content.
Unfixed Issues
We could not fix these issues, seems like SP 13 will help.
Cant delete individual request from ODS
After PREPARE had been run, if we had a load failure and needed to set an ODS request to Red and delete it, we found that we could not. We raised an OSS with SAP but although they tried hard we couldn't get round it. We reset the PREPARE and still the issue persisted. Ultimately we just lived with the problem for a week until we upgraded production.
Error when trying to save query to itself
Any query with a re-usable structure cannot be saved (more thsan once!)
OSS 975510 fixed the issue in Dev and Acc, but NOT in Production! SP 13 may solve this once it's released.
Warning message when running some queries post-upgrade
Time of calculation Before Aggregation is obsolete. Not a big issue so we haven't fixed this one yet!
Process Chain Scheduling Timing error
Process chains get scheduled for the NEXT day sometimes and has to be manually reset.
See OSS 1016317. Implement SP13 to fix this. We will live with it for now .
Fixed Issues
Duplicate Fiscal Period values in Query
If you open up a drop down box ("Select Filter Value") for Fiscal Year/Period to filter your query, you are presented with duplicate entries for Month & Year.
Due to Fiscal Year Period InfoObject taking data from Master Data not InfoProvider. Thus it picks up all available periods not just Z2.
Auto-Emails being delayed
Emails coming from BW from process chains are delayed 2 hours on BW before being released
Due to userids that send these emails (e.g. ALEREMOTE) being registered on a diffferent timeazone (i.e. CET) from the BW system (i.e. GMT)
Pgm_Not_Found short dump
Whenever a query is run via RRMX or RSRT
Call transaction RS_PERS_ACTIVATE to Activate History and Personalisation
Characteristics not found
When running a query the warning message Characteristic does not exist is displayed for the following: 0TCAACTVT, 0TCAIPROV, 0TCAVALID
We activated the three characteristics listed and the warnings stopped. NO need to make them authorisation-relevant at this stage.(also did 0TCAKYFNM)
System generated Z pgms have disappeared
Post-upgrade the system Z-pgms ceased to exist
Discovered in Development so we compared with pre-upgraded Production and then recreated them or copying them from production.
Conversion issues with some Infoobjects
Data fails to Activate in the ODS targets
For the InfoObjects in question, set the flag so as not to convert the Internal values for these infoobjects
InfoObject has Conversion routine that fails, causing load to fail
The routine prefixes numeric PO Numbers with 0s. SD loads were failing as it was not able to convert the numbers. Presumably the cause of the failure was the running of the Pre-Prepare RSMCNVEXIT pgm.
Check the Tick box in the Update rule to do the conversion prior to loading rather than the other way round.
Requests fail to Activate on numeric data
Request loads OK (different from above issue) but fails to Activate
Forced conversion within the update rules using Alpha routine. Deleted Request and reloaded from PSA.
Database views missing after pre-PREPARE work
Views got deleted from database, although not from data dictionary
Recreated the views in the database using SE14.
Workbook role assignations lost
We lost a few thousand workbook assignments when we transported the role they were attached to into Production
The workbooks did not exist in Development, thus they all went AWOL. We wrote an ABAP program to re-assign them in production
Regression Testing Process
Introduction
We were limited to what we could do here. We didn't have a sandbox environment available. Nor did we have the opportunity to have a replica of our production data to test with, due to lack of disk space in Acceptance and lack of sufficient Basis resource.
Set up
We manually replicated our production process chains into test. We didn't have any legacy InfoPackages to worry about. We asked our super-users for a list of their "Top 10" most important queries and did a reverse transport of the queries from Production back into test (as we do not generally have a dev/acc/prodn process for managing queries, and they are mostly created solely in prodn). We made sure every application was represented. In retrospect we should have done some Workbooks as well, although that didn't give us any problems.
Actions
Prior to the various changes we loaded data via the Process chains and ran the example queries to give ourselves a baseline of data to test against. After the change we ran the same queries again and compared the results against the baseline. We tried to keep R/3 test environments as static as possible during this, although it wasn't always the case & we often had to explain away small changes in the results. After upgrading BW Development we connected it to Acceptance R/3, so that we had pre-upgrade (BW Acceptance) and post-upgrade (BW Development) both taking data from the same place so we could compare and contrast results on both BW systems. We did the same thing once BW Acceptance had been upgrading by connecting it (carefully!) to Production R/3. To get round the lack of disk space we tested by Application and deleted the data once that Application had been signed off. Once we got to System test we involved super-users to sign off some of the testing.
Security
We chose to implement the new security schema rather than choosing the option to stick with old. For us, with a relatively small number of users we felt we could get away with this & if it all went wrong, just temporarily give users a higher level role than they needed. Our security roles are not complex: we have end user, power-user and InfoProvider roles for each BW application, together with some common default roles for all. In the event we simply modified the default "Reports" role that all our users are assigned, transported it and it all went smoothly. Apart from the fact that everyone's workbooks are assigned to this role and so we "lost" them all !
Transport Freeze
Once you've upgraded Development you've lost your transport path. We planned around this as best we could and when absolutely necessary, developed directly in Acceptance or Production, applying those changes back to Development once the project was complete. Depending on what other BW projects you have running this may or may not cause you pain!
Web Applications
Dashboards
We had various dashboards designed via Web Application Designer. All these continued to function on the upgraded system. However there were various formatting changes that occurred e.g. Bar graphs were changed to line graphs, text formats on axes changed etc. SAP provides an upgrade path for moving your Web applications by running various functions. However we took the view that we would simply re-format our dashboards manually, as we didn't have very many to do. Plus the external IGS (see below) powered all our environments and needs upgrading separately as part of the SAP method. Thus we couldn't have tested the SAP path in Development without risking Production. Sticking with manual mods was a lower risk approach for us. We did find we had to re-activate some templates from BC to get some of the reports to continue to work.
Internet Graphics Server (IGS)
We had an external IGS server with v3.0B. Post-upgrade the IGS becomes part of the internal architecture of BW and thge external server is redundant. We found no issues with this; after the upgrade BW simply stops using the external IGS and no separate config was needed.
Detailed Task Lists
Support Pack Hike (detail)
Apply OSS 780710 & 485741
Communicate outage to users
Warning msg on screen
Stop the jobs which extract data into delta queues
Clear the delta queues by loading into BW
Check RSA7 in PAE that delta queues are now empty
Run Baseline for Regression tests
Stop Delta queues
Lock Out users
Full Backup
Apply SP's
Upgrade the SAP kernel from 620 to 640
SPAU list review
Apply OSS Notes 768007 & 861890
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
Plug-in installation (detail)
Communicate outage to users
Warning msg on screen
Apply SAP note 684844
Lock out users
Full Backup
Empty CRM queues
Import and patch Basis plugin PI 2004.1
SPAU list review
Apply OSS 853130
Switch back on flag in TBE11 (app. BC-MID)
Remove warning msg
Unlock users
User communication
Dbase upgrades
Dbase upgrades (detail)
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Full Backup
Lock Out users
Apply FixPak13SAP to DB2 database
Upgrade the SAP kernel from 620 to 640
Apply OSS 725746 - prevents RSRV short dump
Unlock Test users (inc. RFC id's on R/3)
Regression testing
Regression sign-off
Remove warning msg
Unlock users
User communication
PREPARE Process (detail)
Pre-PREPARE Process
RSDG_ODSO_ACTIVATE
Repair Info objects and recreate the views
Communicate outage to users
Warning msg on screen
Run Baseline for Regression tests
Stop the Data extract jobs
Lock Out users
Full Backup
Run RSMDCNVEXIT Using BSSUPPORT ID
If there conversion process runs longer delay the regular backup
Re-run Baselines and sign off
If there conversion process Fails repeat the steps on Sunday after the regular backup
BW work
Back up customer-specific entries in EDIFCT (note 865142)
Activate all ODS objects
Execute report RSUPGRCHECK with flag "ODS objects" (note 861890)
Check Inconsistent InfoObjects - Upgr Guide 4.4; OSS 46272; Convert Data Classes of InfoCubes - Upgr Guide 4.3
Execute report SAP_FACTVIEWS_RECREATE (note 563201)
Make sure Delta queues are empty (RSA7)
Basis Work
Full Backup of BW
Lock users
Unlock id's RFC id's and designated test users
Confirm backup complete OK
Apply OSS 447341 Convert Inconsistent Characteristic Values - Upgr Guide 4.5
Confirm OK to PREPARE
Run PREPARE
Review of results
System Upgrade (detail)
Communicate outage to users
Process errors from PREPARE
Check disk space availability for PAB
Warning msg on screen
Reverse Transport Queries from PAB to SAB & DAB
Change BW to R/3 connection
Get backup put on hold, for Ops to release later
Ensure Saturday night backup is cancelled
Final run of PREPARE
Run Baseline for Regression tests
Clear Delta Queues
Delete Local Transports
Remove process chains from schedule
Lock Out users (with some exceptions)
Confirm to Ops and Angie that we're ready
Full Backup
Incremental backup of Unix files
UPGRADE "START"
Back up kernel
Unpack latest 700 kernel to upgrade directory
Check ids required for upgrade are unlocked
Check no outstanding updates
Turn off DB2 archiving
Open up the client for changes
Stop saposcol, & delete from exe directory
Run the Upgrade
Execute the saproot.sh script
Perform the database-specific actions
Perform follow-up activities for the SAP kernel
Reimport additional programs
Import Support Packages
Call transaction SGEN to generate ABAP loads
Transport Management System (TMS)
Handover to BW Team
SPAU list review
Apply OSS Notes from SPAU
Process Function Module XXL_FULL_API (part of SPAU)
Restore table EDIFCT (if required)
Transport Fixes from our BW Issue list
Convert the chart settings - manually
Perform activities in the Authorization Area
Activate hierarchy versions
Update the where-used list
Execute the conversion program for the product master
Transport New roles to PAB
Unlock selected users
Regression testing
Regression sign-off
Go / No Go decision
Restore if required
Remove warning msg
Tell Ops that the CR is now complete
Lock down PAB
Unlock users
User communication
Perform the follow-up activities for SAP Solution Manager
Reschedule background jobs
Reschedule weekly backup on Ctrl-M
Drinks all round.
Vendors mentioned: dBase
Hope this helps. -
Information on impact on interfaces due to upgrade from 4.7 to ECC 6.0
Hi friends,
We are upgrading from 4.7 to ECC 6.0. We have some interfaces with the SAP system in our current version.I need information on which of these interfaces will be affected due to Upgrade of the system to ECC 6.0
Mentioned below is the list
SAP R/3 --- CRM 5.0
SAP R/3 --- Xi PAY
SAP R/3 --- Vertex
SAP R/3 --- TEKRF
SAP R/3 --- Virsa
SAP R/3 --- WTX
SAP R/3 --- SOLMAN
It would be really helpful if you can just provide the initial impact analysis for these interfaces due to upgrade.Points will be rewarded.
Thank in advance.
Regards,
Pawan.Hi
there are several oss-notes available which explain how to transfer your text customizing to the new procedure. This happens if you are uppgrading from a release 4.6c or lower. If you are already in 4.7, there should be no problem with text determination.
Regards
Rauno -
OSS notes relevant for FI/CO for upgrade from 4.7 to ECC 6.0
Hello,
I need the list of the applicable OSS notes relevant for the FI/CO module for upgrade from 4.7 to ECC 6.0
Thanks
SidHi,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Please assign points if it useful.
Regards
Ravinagh Boni -
Media List required for EHP7 OF ERP 6
Hello,
We plan to upgrade our ERP 6.0 ABAP systems (Unix,Oracle) on SAP NETWEAVER 7.00 to EHP7 for SAP ERP 6 based on SAP Netweaver 7.4 (Linux,Oracle) after OS/DB migration
I know the path from where I can download the media but want to know if there is any MEDIA list guide for EHP7 for SAP ERP 6 based on SAP Netweaver 7.4 ? Or how do I know which DVDs should I download ?
My Company's Application Components" My Company's Software" SAP ERP" SAP ERP ENHANCE PACKAGE" EHP7 FOR SAP ERP 6.0" SAP NETWEAVER 7.4
My Company's Application Components" My Company's Software" SAP ERP" SAP ERP ENHANCE PACKAGE" EHP7 FOR SAP ERP 6.0
Thanks
ShradhaHi!
Wondering about the media list for a NEW installation of ERP6 EHP7 on Oracle Linux with Oracle DB with ADS.
Is it something like this:
SAP Netweaver 7.4
51049350_5 SAP Kernel 7.42 Linux on x86_64 64bit
51048524_6 NW 7.4 SR2 Java 1/2
51048524_7 NW 7.4 SR2 Java 2/2
EHP7 FOR SAP ERP 6.0
51048902_1 SAP ERP 6.0 EHP7 SR2Installation Export I 1/2
51048902_2 SAP ERP 6.0 EHP7 SR2Installation Export I 2/2
51048902_3 SAP ERP 6.0 EHP7 SR2Installation Export II
51048902_4 SAP ERP 6.0 EHP7 SR2 Language I 1/2
51048902_5 SAP ERP 6.0 EHP7 SR2 Language I 2/2
51048902_6 SAP ERP 6.0 EHP7 SR2 Language II 1/2
51048902_7 SAP ERP 6.0 EHP7 SR2 Language II 2/2
51048902_8 SAP ERP 6.0 EHP7 SR2 Language III
51048902_15 BS7i2013 SR2 Java Components - NW 7.4
51048902_16 SAP ERP 6.0 EHP7 SR2 SAP Components
Or do I need something else?
Any help welcome!
Thanks in advance and Kind Regards,
Joao -
Upgrade from 4.6b to ECC 6.0 abap changes?
Hi all,
Kindly can any one provide me documentation on upgrading from 4.6 to ECC 6.0 Related to changes in abap code, obsolet functions, etc.
It will be very helpful If you can help me.
Thanking you in advance,ERP 6.0 has > 200.000 ABAP programs and function modules and other objects, having such "delta list" doesn´t make sense. Would you want to compare the programs one-by-one?
Between 4.6B and ERP 6.0 are many years of development and many many uncountable changes.
Please be a bit more specific what you want to check, then we may help.
Markus -
Upgrade from 4.6 to ECC 5.0 Functional Upgrade
HI Friends,
We are upgrading from 4.6 to ECC 5.0 Functional Upgrade, with New G/L Functionality, i would like to know what are the pre requistics for performing this upgrade and along with check list.
Thanks in Advance
SatishHi Satish,
Now i am sending some URL for Functional upgrade
May be those are all useful toyou
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
Regards
Surya -
Upgrade from 4.6c to ECC
We are upgrading from 4.6C to ECC.
We have evaluated the UCCHECK results.
I wanted to know is there any other places we might need to change our codes except those indicated in UCCHECK, SPAU and SPDD transactions?
Can we assume that the list provided by other transactions will be complete?
THanks in adv.This note tells about many more things.
So it means we cannot be sure that after doing the changes mentioned in transactions UCCHECK, SPDD, all programs will not give syntax errors, at least?
Thanks in adv. -
Interview questions on upgrades from 4.7 to ECC
Hi,
Can any one please post some potential areas/questions that will be asked for upgrade projects from 4.7 to ECC6.0
Points will be awarded.
ThanksHi Frank,
this is good question, why because sap upgrades from 4.6b to ecc 6.0 is very risky.
take one example , in 4.5b , me21n application having 620 screen where as in ecc 6.0 having 9000 screen . that time we will take care of it.
check the obsolete function modules , 4.5b , having ws_upload, ws_download.... use cl_gui_frontend_services , under these having differnt type of methods.
once you change the code in ecc , go to tranx : SLIN check the error where it is exact. -
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 KHi 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 -
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,
Divyahi,
In the OPEN DATASET STATEMENT ADD THE ENCODING ADDITION IN TEXT MODE.
Regards,
Balakumar.G
Reward Points if helpful.
Maybe you are looking for
-
Clicking noise from new Toshiba Satellite laptop?
I have a Toshiba Satellite C55-A5195 (Windows 7 Home Premium). It was bought brand new around 3 weeks ago. I've noticed that, besides the fan noise, the bottom of the laptop makes a clicking or buzzing noise. The laptop has blue screened twice, somet
-
Always when I close FF 4.0 on my desktop running XP it says it failed to close correctly and is still running ? Same thing happened in another version of FF I believe.
-
Exception in ForEach block causes it to stop
My scenario is a JDBC to JDBC to File scenario. The JDBC sender returns a resultset of a few transaction Ids. I then need to call a SP with each transaction id one by one to return more details. I am doing this by going to BPM, splitting the transact
-
SOAP Messaging Using Crystal Reports Web Services To Return Report in PDF or Excel Format
All, I am trying to use SOAP messaging to fetch a Crystal Report through a Managed repository and getting back either a PDF or Excel file. For some reason, any reference to web services on this site I cannot access. Like thread, "Using Web Services o
-
Soundtrckr Geo social internet Radio for N8
Just launched at Beta labs and only for Symbian^3 Phones, may be worth a try http://betalabs.nokia.com/apps/soundtrckr If I have helped at all, a click on the White Star is always appreciated : you can also help others by marking 'accept as solution'