Upgrade APO 3.0 to SCM 5.0 SR2 (requirements in source system)

Hello!:
We want to do and upgrade upgrade APO 3.0 to SCM 5.0 SR2
And we have seen the Guides SCM5.0 SR2 and SCM5.0 SR3, but appears info in the page 26 only about check the software requirements from APO 3.0 to SR3, but we want to check the information about APO3.0 to SR2.
Regards,
Alfredo.

Alfredo,
This is not a easy question, since you are several releases behind on APO. I have done upgrade from APO 3.0 to SCM 4.1 and then subsequently to 5.0 so there were lots of learnings specific to the Projects and develoments. The Setup being different in different industries and companies, there is no one answer to this question. Try the following ...
- Read the Release Notes of SCM 3.1, 4.0, 4.1, 5.0. You will see a Host of New Functionalities - Newer in SNP, PPDS, TPVS, Master Data (PDS along with PPMs).
I do not know what functionality you are live with in APO 3.0.
On the Existing Setup that you may find changed, I remember the following big changes ...
- GUI Changes are galore in master data, less
- SNP Side - Changes in TLB Engine & TLB Prioritization.
                 - Deployment Split Functionality
                 - Changes in User Exits (old code would not work). You will find this painfull if you've implemented User Exits. eg : If you were determining OrderTypes in orders sent from APO to R3. TLB User Exits. Lesser changes in Masterdata userexits.
                  - Newer fields in Master Data (eg : SNP Checking Horizon in Product Master and it's implications on Deployment & TLB. ).
                 - Subcontracting Planning in APO.
- Enhancements in VMI.
- Use of Parallel Processing for all Modules planning.
- Enhancements in Aggregated Planning
- Enhancements in Product Interchangeability.
- Several Newer Functionalities like ICH to make/replace the earlier Collaborative Planning better.
- Master Data several changes (eg : PDS)
- Several improvements in CoreInterface Function and Que Issues. In 4.0 onwards there is new functionality around CIF Postprocessing
- Use of Process Chains to streamline Batch Jobs and especially BI Loads into Cubes and Planning Areas.
- Several enhancements in PPDS (newer heuristics), Alerts
- BW underwent a Major change from BW 2.0 to BW 3.0 to now BI 7.0 which impacts Setup for Demand Planning. eg : The InfoCube got renamed to InfoProviders.
I suggest you start with the Release Notes. Form a List of your Test Scenarios, then Upgrade in your Development and start to Test. Don't plan less, but more time for testing since you are undergoing a several releases change. First start to get your Existing Business Scenarios documented as Test Scripts in Order.
I STRONGLY recommend doing a Technical Upgrade Only (i.e : do not upgrade Major Functionality unless there is no other way). In Summary for SURE SCM 5.0 is a Much better and Stable System than APO 3.0.
Hope this helps. Reward Points If you find it usefull.
Regards,
Ambrish Mathur

Similar Messages

Plug-Ins and Extractors - Related to Upgrade of Source system

Hi,
We are upgrading from R3 to ECC.
Can I say that, if the Plug-in in current R3 system and the new system(post upgrade)(ECC) are same then, the extractors will also remain same ? hence, nothing will be affected in BW ?
For example, if the current system(R3) has the Plug-in as PI 2004.1 and the upgraded ECC also has the same Plug-in PI 2004.1 , Can I say that the extractors will also be the same ?
Regards,
Rekha .

You have to take care of all your deltas are picked into the bw before upgradation.
Some times you may required to replicate the data sources after upgradation.
You may lose the connection between your R3 and you BW.
Please do a souce system check after the upgradation.
You have to take care of all deltas :
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895 [original link is broken]
OSS notes 328181 and 762951 as a prerequisites.
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B

Step by step screen shots fro APO and SRM, CRM , SCM extractions.

hi friends,
can i get step by step screen shots fro APO and SRM, CRM , SCM extractions.
Thanking u
suneel.

Hi,
I am not sure that you can find something like you asked but from my point of view BI Content is enough.
Regards,
®

After upgrading to Mavericks on my Mac Pro, mail always requires that I type in my password when launching. How do I change that?

After upgrading to Mavericks on my Mac Pro, mail always requires that I type in my password when launching. How do I change that?

If your password is accepted, and Mail connects to the account, but you're prompted for the password repeatedly, take each of the following steps that you haven't already tried. Note: these steps don't apply if the server rejects the password. That's a different problem.
Step 1
When prompted for the password, check the box marked Remember this password in my keychain.
Step 2
Check that the keychain is working.
Step 3
Check that the default keychain is unlocked.

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Create Source System in APO and BW

Hi Gurus,
i want to create a Source System in APO it should be connected to BW.
is there any "HOW TO" documentation to do this?
thanks
Younes

Hi,
there are business content delivered datasources
0APO*, e.g 0APO_PPDS_ORDER_01
http://help.sap.com/saphelp_bw33/helpdata/en/56/22f93a000f7550e10000000a11402f/frameset.htm or generate datasource, check
Re: APO/BW: How to get back from APO to BW/ How the send data from BW to APO
http://help.sap.com/saphelp_scm50/helpdata/en/c9/199170f13711d4b2f20050da385632/frameset.htm http://help.sap.com/saphelp_scm50/helpdata/en/e0/9088392b385f6be10000000a11402f/frameset.htm 1. Generate an export DataSource for the planning area
2. Replicate the DataSource 3. In the Data Warehousing Workbench, you are still in the source system view. Right-click the source system and choose DataSources Overview in the context menu. 4. Assign an InfoSource to the DataSource 5. In the Data Warehousing Workbench, branch to the InfoSource view. 6. Right-click the InfoSource that you have just created and choose Change. We can genetrate data sources for Plan Book, which will be used to load data. Other Datasources use live cache for data. OSS notes DP-- 549184 SNP--428147

APO source system folder in BW

Hi Experts!
In need create the APO source system in BW.
Does I need create this in 'Sap folder' or in 'External System' folder?
Thanks in advance!

Since APO is an SAP application and you'll most likely be using native functionality for extraction, you should set it up as an SAP system, just like what was done for R3/ECC (I'm making the assumption that you already have that connection).
Edited by: Dennis Scoville on Sep 17, 2009 6:57 AM

Source System Connection Issue after BI 7 Upgrade

Hi all,
We have just upgraded from BW 3.1 to BI 7.
After the upgrade, I checked the connection to our R3 4.6 source system.
It is now saying the following message:
Source system XXX is marked as inactive in BI.
Check failed for RFC connection XXX ; check destination
After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
The thing is that our name & password ARE correct definitely.
Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
Any ideas?
Thank you
chris

Hi,
as from NW7.0, passwords are case-sensitive.
If you define the passwords in the RFC in uppercase, it will work.
This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

ECC6.0 upgrade and BW steps for mapping the new ECC6.0 source system

Hello gurus
We are upgrading from R3 4.6C to ECC6.0. We use BW 7.0 SP 18. We will create the new ECC6.0 source system in BW, replicate metadata and everything. The question is how do we copy or reassign the existing objects pointing to our current 4.6c dev system (transfer rules, transformations, infopackages, process chains) to point to the new ECC6.0 dev system ? As a note, we also need to keep the current 4.6c source system objects until go-live o ECC6.0.
What is the common practice in such a case ? I am sure we are not unique...
A prompt response would be appreciated.
Thank you all.

So the plan is to copy dev R3 and upgrade that - then Q r3 copied and upgrade that - then upgrade directly prod R3?
If so - then if it were me - I would firstly prove all this in a sandbox environment where BW dev points at an upgraded sandbox R3 ecc
ie same logical system
Then once that is proved I would organise downtime of BW development for a few months whilst the d-q-p ecc happens
Then when they copy dev r43 to ecc r3 i would then just point BW dev at the new ecc box and go from there (ie clear the deltas - change the logical system name to the new ecc box - replicate meta data - transtru all the datasources - run the process chains nothign to worry about)
However if you cant afford the down time - you may have to have an alternative transport route - ie copy dev BW to a another dev bw box and have an alternative path to production for issues
Then once everything is upgraded redo the changes through d-q-p to get the transports back in line (thats what we did)

Deletion of source system after an upgrade : consequences ?

Hello,
I'm a sap basis guy.
We have a SAP BI 701 sytem mapped to our 4.7 Non Unicode source system.
I have now perfromed the unicode migration and upgrade to ECC6 of the source system on another server.
It means now, that I have two sourtce systems with exactly the same SID, and logical name.
Sicne the BI connexion in RSA1, is based on the logical system name , I have no ther choice than delete the old
source system, and recreate it with the same logical name but different connexion parameters (hosts, ...) and differentversion (
I have talked with the BI team, but thnigs are quite unclear about the consequences of deleting a source system in RSA :
Do all Transformations/ Transfer Rules between DataSources and targets are deleted ?
Does it mean that they have to be manually recreated after the new source system has been recreated ?
Is there any workaround ?
Thank you in advance for your help.
Regards.

Hello,
If you do not save the source system dependent objects to a transport request before you delete the connection then the objects will be lost , you can avoid this by saving the objects to a transport request and then release the transport before you delete the connection and import it in the new system, the steps in general are below:
RSA1
Transport Connection
Button 'Collection mode' set to 'start manual collection'
Press 'Source system assignment' button (it's the one left of the
'Request BEx' button)
Select the source systems you want to save the transfer rules for
Continue
Button 'Grouping' set to 'Save for system copy'
At the left border click on 'Object Types'
Extend tree 'Source system' LSYS
Double click on 'Select objects'
Select the source systems you want to collect objects for
the source system is now displayed in the right box
Press collecting button ('gather dependent objects')
this may take a while
Right click on the root of the tree and select
Transport all below
Expand the whole tree and check if there isn't an object which is locked
by an other open transport request !!
(the column 'Transport request' has to be empty (BEFORE deleting the corresponding source system
connection!)
Best Regards,
Des

Will an BI Content upgrade from affect the source systems?

Our current BW has BI Content 7.02 patch 003; we are planning an upgrade to 7.03 patch 012. Will we have any impact on the source systems (ECC and SRM)? We are trying to decide if we need to archive and backup the operational systems. Since it is a lot of extra work and increases the number of people affected, we prefer not to do it unless necessary.
What type of regression testing is most common after a BI Content upgrade?
thank you very much,
LLK

Hi
As a data fetching from Source system -- the BI Upgrade does nt have any impact on Source Systems normally -- But u need to prepare a check list with before and after upgrade with DS ( Some times DS get de activated while upgradation ) and the DS are source system dependent so you may have to re activate the same based on requirement/possibilites-- And also you may have to empty the Delta Queues on Source System side -- otherthan that no impact , as far I know.
Hope it helps and celar

Deletion of Data from Infoprovider after upgradation of source system

HI All,
In our project source system is upgraded from 4.7 to ecc 6.
I have kept the same logical name and changed the RFC connection so that it points to new source system.
Now do i need to delete all data before uploading data from source system or it will be fine as source system name is same.
If i need to delete data ,can u help me how to delete master data especially Hierarchy data. do we need to Delete Hierarchy and recreate it.
Please help em to resolve this issue

Hi,
It depends on your requirements whether you have to keep the history or not.
If you delete the data from your info providers, you have to reload everything from scratch.
If you want to delete the data from all
1. first delete the data in data targets such as cubes, DSO's or ODS then
2. master data
use these programs to delete from se38
-> rsdrd_delete_facts - for Cubes and DSO or ODS
-> rsdmd_del_background - for master data in background
-> rsdmd_del_master_data_texts - for master data right away
manage your master data info objetcs after the deletion, if you still find them....
go to se14 and delete individually each and every table such as attributes, texts, sids, hierarchy.
hope it helps you better.
But I dont recommend you to delete try to load full repair options for all yur loads

Data load delay after DB upgrade in source system

we have upgraded our source system DB to oracle 11g over the weekend. The first loads of our process chain the master data is taking huge time with the message as
I am getting message as
Data Package 000001: sent,not arrived
Info IDoc 2 : sent , not arrived ; Data passed to port OK
Info IDoc 1 : sent , not arrived ; Data passed to port OK
Info IDoc 3 : sent , not arrived ; Data passed to port OK
Info IDoc 4 : sent , not arrived ; Data passed to port OK
Request IDoc : Application document posted
processing (data packet) : No data
can anyone share ideas on this
thanks and regards
Edited by: AAL123 on Sep 26, 2011 7:17 AM

Hi,
Check the below given SAP Notes,
Note: 580869 ( RFC calls can be processed with report RSARFCEX) & 530997.
Regards,
Durgesh.

Steps in BW after the upgrade of the source system R3 in netweaver 2004s???

Hi,
1. Who can tell me which are the steps to execute in BW after the upgrade of the source system R/3 4.6 to Netweaver 2004s (ECC6) ?
2. Do the delta loads continue to run or must be re-initialized?
Thanks for your help
Dominique

hi Dominique,
you should take care not after upgrade, but also before upgrade
or your upgrade has been done ?
also stated, before upgrade
If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
These are absolutely prerequisit notes for using Logistic Cockpit.
Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
458305-OLTP system upgrade: What should I be aware of afterwards?
Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
Note 301192 - Procedure after upgrading an R/3 source system
Note 359412, there may be some others
hope this helps.

Have 7 mo. old iPhone running 4.3.3 and am wondering if I can upgrade my software. Apps I want to load require minimum of 5.0. Am out of luck or what? Where do I go to find upgrade if it exists? Yes, I am that dim I guess. OS can't be updated?

Have 7 mo. old iPhone running 4.3.3 and am wondering if I can upgrade my software. Apps I want to load require minimum of 5.0. Am I out of luck or what? Where do I go to find upgrade if it exists? Yes, I am that dim I guess. Was under impression software could be updated similarly to std. Apple OS practices with other products.

How to upgrade iPhone, iPod, iPod Touch

Upgrade APO 3.0 to SCM 5.0 SR2 (requirements in source system)

Similar Messages

Maybe you are looking for