Impact of ECC 6 upgrade on EBP 3.0

I hav EBP 3.0 and R/3 4.6C is planned to be upgraded to ECC 6. Not sure what will be the impact of upgrade on EBP 3.0. Can I continue to use EBP 3 with ECC 6 w/o having need to upgrade it to SRM. Has anyone seen EBP 3.0 and ECC 5 or 6 combination. Please revert.
Regards
Giriraj

Hi,
We have R/3 4.5c upgraded to ECC 6 and SRM 3.0 (EBP 4.0).
All we have to do is upgrading R/3 plugin and thats all.
Regards,
Marcin Gajewski

Similar Messages

Need to understand impact on workflows during upgrade from EBP 3.0 to SRM 5

Hello experts,
Greetings to all and a Happy New Year!!
I am new to the workflow concept, though i have a fair idea of EBP.
We are using EBP 3.0, classic scenario. Very soon, we would be upgrading from EBP 3.0 to SRM 5.0. I have a few questions which i need to knw before I take up the upgrade part:
1) The impact on the worflows like Shopping cart approval, purchase contract approval etc when we upgrade from EBP 3.5 to SRM 5.0...
2) Does EBP have their own release strategies or are the release strategies defined in R/3 and applied to the shopping cart when it is ordered in EBP? As in classic scenario, POs are created in R/3, then how does the appoval process happen?
3) What are the necessary things, if any, that I should make sure of before upgrading?
4) Does all workflows also get upgraded or is there any tool to upgrade the workflow?
I am not clear with the approval concept in EBP. I know there are workflows that get triggered when a shopping cart is ordered but the approval process in this workflow is something which i want to understand. Please forward me a document, if possible, or a link will also do.
Please let me know the necessary details.
Thanks in advance.
Regards,
Ayush

Hi Ayush,
Most workflows will be the same, but if you have modifications on these workflows' then i'd suggest reverting back to the standards for the upgrade.
Im not quite sure what you mean about the release strategy. What can be done though, is creating Purchase Requisitions in the R/3 and pass them to the SRM system. From here PO's can be created and the approval process will take place in accordance with your workflow rules in tcode: swb_cond.
Before upgrading, try to have the system as clean as possible. When i say clean, i mean make sure that users are consistent, SC's, PO's etc arent left hanging. Try to avoid carrying documents over to the new system. I'd suggest archiving anything you can too.
I don't have any documents to give you but the basic process and transactions are as follows:
SWB_COND: Your workflow start conditions. Which WF's are on/off (defined by green/red light)
SWI6: This will let you examine a document and its relevant WF by its object id. (SC No, PO No etc..
SWUD: Allows for Consistency checks on your workflow and will find any inconsistencies which are occuring. (Use Test Environment and WF Tech Name i.e 14500015)
SWDD: The workflow builder, will let you build, activate, create new version and modify the worklows in your system.
Approval itself is simply the chain of approval which a workflow is defined to follow. You need your managers to approve/reject and the conditions for which Managers should be called for approval. Its works from Possible Approvers for workitems and Excluded Approvers for workitems.
Understanding the WF log is the most essential thing of all. The understanding of BADI is quite important too.
Hope this info helps you. Check help.sap.com cause everything is documented there too!
Cheers
Will

Impact of ECC 6 Upgrade on BI7.0

Hi Experts,
We are on BI 7.0 ( Netweaver 2004S ) and Source system is ECC5 . Our company is in the process of Technical Upgrade from ECC5 to ECC6 with unicode and Ehp4.
Current setup is
BI 7.0 SP 19 Non Unicode Oracle 10g
ECC 5 Non Unicode Oracle 10g
I would like to know the Impact of ECC6 upgrade on my BI system.
1) We have lot of customization in BI extractor .
2) Various Abap routines written for transformation . will there be any change for unicode.
3) Is there any impact on deltas or Do we need to reinitialise the deltas.
Thanks,

Re: ECC upgrade impact on BI
testing in BW for ECC upgrade
Re: ECC upgrade impact on BI
Go through these threads, sure it would help you.

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
venu

Hi
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.

What level of certification is required for ECC 6 upgrades?

Hi everyone,
I'm already a ceritifed SAP technology consultant (up to NW2004), however need to update my certification for ECC 6 (netweaver 7).
What is the appropriate exam to sit (eg associate or professional) to be allowed to perform productive SAP ECC 6 upgrades?
Thanks
Shaun

Hi everyone,
Major update on the "do you need to be certified" topic ...
I finally got a reply from SAP Education regarding two queries I had regarding what level of certification was required as a basis "guy" to perform production SAP installations and upgrades.
SAP Education wrote:
You don't need to be certified to do installations. In reality, customers will have much more comfort having an install done by someone who is certified rather than someone who isnu2019t, but ultimately itu2019s the customeru2019s call.
I then asked if this was applicable for SAP upgrades also ...
SAP Education wrote:
Hi Shaun,
Indeed it is.
Best of luck!
I then went on to clarify that their is no support implications for customers who don't you certified Basis personel to perform their upgrades/installs:
Shaun wrote:
So your saying that although itu2019s preferable to be certified ... you donu2019t have to be, and there is no impact to the support provided by SAP?
SAP Education wrote:
Ultimately, SAP cannot mandate for individuals (excluding those employed by SAP) or SAP Partners to be certified to work on projects. However, customers and partners will employ the consultants to work on the projects, from what we have seen recently customers and partners are now asking for SAP certified consultants to work on implementation and upgrade projects.
Thus we suggest to have an advantage to be employed on future SAP projects that you are certified in the solution you will be working on, or upgrading to.
Example: If you are looking to work on an upgrade from CRM 5.0 to CRM 7.0 the customer would look for certified consultants in CRM 7.0
So it is solely up to you if you wish to certify yourself in the latest release of the solution you are working in.
I then rang SAP education and had a very pleasant discussion with one of the ladies there. She went on to explain that the requirement for certification really became an optional thing a few years back. SAP was no longer in a position not to support customers regardless of who they use to perform their upgrades/installs since a customer continues to pay their yearly maintenance costs - thus SAP is obligated to provide support.

New Development project in the middle of ECC EHP7 upgrade project

Hi All,
We are performing ECC EHP7 upgrade project in our project system landscape and i have already started Dev system upgrade.Suddenly our development team wants to perform new project which required to install add-on product from third party application. Installing new add-on will require us to regenerate stack.xml file right? if that is the case do we need to perform re upgrade to Dev right?. As per my knowledge this is not recommended to perform parallel project with upgrade project.
Is there any best practice or recommended method to perform multiple projects with upgrade project at the same time.
Thanks,
Raghu

Hi Raghu,
First here i would like to suggest you & your development team i.e during an upgrade project dual maintenance is required as per SUM guide,as per SUM guide you need to maintain parallel systems to perform regular activities, for same you could refer SUM guides and follow the standard procedures.
Installing new add-on will require us to regenerate stack.xml file right?
Yes you need to regenerate the stack.xml file .
if that is the case do we need to perform re upgrade to Dev right?
If you are under upgrade phase no need to perform re upgrade,required add on can be installed after completion of an upgrade as per availability for EHP7.
Try to avoid perform multiple projects with upgrade project .
Regards,
Gaurav

SAP Query in ECC 6 Upgradation

Hi All ,
I am working in an ECC 6 Upgradation project , upgrading from 4.6 C to ECC 6.
Somebody told me , Query cann't be coppied from 4.6 C to ECC 6.
Is it true ? If so what is the alternative ?
Thanks in advance.
Regards
Srikanta

Hi Srikanta,
U didnt need to re-copy all the queries. When you upgrade from 4.6, the new version of sap does not default to the correct query area. You merely need to point it to the correct one. Just set a parameter against you own user data called AQW and leave the parameter value blank.
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (by using the lorry button) or run report RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Hope it will be useful.
Regards,
Lakshman.

Upgrading from EBP 3.1 to EBP 5.0

We are running EBP 3.1 and plan to upgrade to EBP 5.0.
Current EBP details:
EBP 3.1 SR1 BBPCRM Support package 14
ITS 610
Requisite Bugseye 3.5
Backend R/3 version: 4.7 SR1 extension set 2
Backend PI version: 2004_1_470
Using blended-codepage: eurojapan
Target release:
EBP 5.0 on WAS 640
Requisite Bugseye 4.0
Questions:
1- Can Requisite Bugseye 4.0 be installed on WAS 640 (on the same server as the EBP 5.0)?
2- What codepage is recommended for EBP when the backend R/3 is using eurojapan blended code page setting?
I am looking for lesson learned and problems encountered during implementation and upgrade from an infrastructure point of view.
Thanks,
Asif

Asif,
You must be using Ebp 3.0 or Ebp 3.5.
Requisite products will not be supported by SAP after December 2006. You should consider migrating to SAP CCM.
You will see several discussions on CCM on how to get more information in this forum. You can also look in the service marketplace under SRM 4.0
CCM can be installed as an "add-on" on the same SRM Server as a low TCO option. Can reside on a separate Server for production system for performance reasons (if you have lot of items)
Hope this helps.
Kind Regards, Suresh.

Impacted Object List - when upgrade

When a customer upgrade from E1 8.10 to E1 8.12, he should know the impact over his customization on standard objects. Where can he get the consolidated list of impacted objects by this upgrade?

Hi,
There is a guide (7MB) available on MetaLink3 that lists all changes to ALL objects. The one I came across is JD Edwards EnterpriseOne Programmer's Guide - Xe to 8.12
You can find them in:
Knowledge > Browse Home > JD Edwards EnterpriseOne > All Products Information > Documentation - Install & Updates > All Products > Implementation Guides & Updates > Browse Results
Good luck
Greg

IS Retal ECC EHP6 Upgrade Material not Article

Hi
I am busy testing our ECC EHP6 upgrade in an IS Retail System.
I have noticed the system is now referring to Material and no longer Article (MB51, MM41/2/3 even the W10T menu shows material and not article)
My developer has suggested I go to SE93 to change the transaction description from Material to Article.
This does not seem correct
Has anyone experienced this before?
Do you have a solution?
Thanks
Rory

Hi Rory:
You need to apply Retail Text after every upgrade.
Please take note of the following:
SAP Note 897714 - Activating Retail Short Text Replacement
SAP Note 904437 - Some short texts contain std terms instead of retail terms
- Paul
Paul R. Gendreau Jr,
SAP Retail, Inc.

4.6c to ECC 6 upgrade - Mass activation program RADMASG0

During 4.6c to ECC 6 upgrade - when we try to use Mass activation program - RADMASG0 - how to remove warnings in a single shot ?
When I am giving some 6 table names as input for activation (under 'DIRECT OBJECTS' in Program RADMASG0 ),after execution i am getting the warning for all the three programs. (same warnings)
How to clear this.....whether i have to go one by one. If so then what is the use of this program ?
regards,
N. Prasanna kumar.

Hi,
What Message you are getting.
One suggestion is that going one by one is most suitable. Other wise you will not able to detect the errors.
With regards,
Sumodh.P

Impact in portal for Upgrade ECC 5.0 SP04 to ECC 6.0

We are upgrading the ECC system from SAP_APPL 500 SP04(ECC 5.0) to SAP_APPL 600 EHP4 SP10(ECC 6.0) . I need to know what will be the impact on Portal 6.4 VErsion which is having ESS/MSS and BI integrated .

Hi GjEPCons ,
The Ess/mss application are standard some application webdynpro java and web dynpro abap so nothing happen upgrade one version to another version in backend and bi reports also but we can check the system object if case any thing happen ,
Ecc 5.0 and Ecc 6.0 nothing more change some features have add in Ecc 6.0 so we dont bother tome to upgrading .
Upgrade from ECC 5.0 to ECC 6.0
Hope this information help s to you
Thanks&Regards,
G.srinu

Regression Testing for BW 7.01 - Impact of EHP 1 upgrade for CRM 7.0

Hello All,
The CRM team has rolled out enhancement pack 1 for CRM 7 to Development box and we need to do some regression testing on the BW side to make sure the upgrade goes smoothly on QA and Production. If you have gone through the same process, could you please provide a list of or link to standard CRM extractors that could be used as checklist for regression testing on BW side?
Thanks.

Re: ECC upgrade impact on BI
testing in BW for ECC upgrade
Re: ECC upgrade impact on BI
Go through these threads, sure it would help you.

ECC EHP5 upgrade:is i mandatory to upgrade netweaver portal & BI systems

Hi Gurus,
Currently we are having landscape of :
1.SAP ECC6.0 SP stack at 17
2.Netweaver Portal 7.0 SP stack at 17
3.Netweaver BI 7.0 SP stack at 12
Currently, viewing BI reports using Portal.
We are planning to upgrade our ECC 6.0 system only to EHP5
My questions are:
1. Is it mandatory to upgrade netweaver portal and BI systems also.
2. We are very less dependent on BI. So, can we continue with the same old BI system with ECC6.0 upgraded to EHP5?
Please shed some light on this.
Thanks in Advance.
Regards
Balaji Nampally

There is no any specific details available for the same.. But it seems some BPs need to be upgrade on portals side..
SAP ESS 603(SP06)                                 BP ERP05 ESS 1.41
SAP MSS 600(SP17)                                 BP ERP05 MSS 1.51
SAP PCUI_GP 603                                 BP ERP05 COMMON PARTS 1.51
                                                      BP ERP05 HR ADMINISTRATOR 1.51
                                                      BP ERP05 SELF-SERV ADMIN 1.0
                                                      BP TECHNICAL INFORMATION 1.51
Pl provide if any has more details.. we are also looking for the same..
Thanks

ECC/ERP Upgrading to EHP4 - basic steps?

Just installed fresh ERP/ECC 6 from disks labeled EHP4 ready. Needing to upgrade immediately to EHP4. To do this, my understanding is that I need to initiate a maintenance transaction from solution manager to start the process and then proceed (basically following these directions http://sap.wsteinert.com/blog/2009/10/implementing-the-ehp-4-part-2/ ).
Can anyone describe (in detail) the maintenance transaction process and what I have to configure on the solution manager side to get this up & going?
Also, does the EHP4 process require that I download the components? It looks like I already have some media that may have EHP4 components on it. Can I just do a local upgrade using the media?

> Can anyone describe (in detail) the maintenance transaction process and what I have to configure on the solution manager side to get this up & going?
You have to Create a maintenance transaction in the SAP Solution Manager and select the
appropriate technical usages in order to calculate the corresponding software
packages.
Refer https://websmp204.sap-ag.de/~sapidb/011000358700000293582009E.PDF
> Also, does the EHP4 process require that I download the components? It looks like I already have some media that may have EHP4 components on it. Can I just do a local upgrade using the media?
refer https://websmp104.sap-ag.de/~sapidb/011000358700000931872009E .
regards,
Nibu Antony

Impact of ECC 6 upgrade on EBP 3.0

Similar Messages

Maybe you are looking for