Patch upgrade in Source system ECC 6

Hi,
We are plannig Patch upgrade in the ECC 6 r/3 System. This is source system for BI7 (NW2004s).
I want to know, we beibg a BI consultant
1. What we need to check in ECC on patch upgrade.
2. What precautions we need to take for better facilitating the patch upgrade in ECC 6
3. Other related things.
can someone please reply.

Hi
check patch level in BI system :---
Logon to your SAP System
SYSTEM>STATUS>Click the search buttion under SAP System Data
Where you can find your patchelev.
BI Content and Plug-in Information
These are the links to get detailed information about BI Content and Plug-in.
Check the release notes in this link:
http://help.sap.com/saphelp_nw70/helpdata/en/bc/52a4373f6341778dc0fdee53d224c8/frameset.htm
Dependencies of BI_CONT Add-Ons: Functional Correspondences
https://websmp207.sap-ag.de/~sapdownload/011000358700007362962004E/func_corresp.htm
Dependencies of BI_CONT Add-Ons: Technical Prerequisites:
https://websmp207.sap-ag.de/~sapdownload/011000358700007362972004E/tech_prereq.htm
BI Extractors and Plug-in Information:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000682135&
http://sap.seo-gym.com/copa.pdf
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
/thread/178564 [original link is broken]
Asset Mgt Data
http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
/thread/507115 [original link is broken]
Go to sap logon pad on the top left side of the logon pad u can see a small click option beside the logon gui for eg: sap logon710 or 640. click on that and select about sap logon there u can c the patch level, build, file name, file version etc,
Hope it helps
regards
gaurav

Similar Messages

Background job is running for long tome in source system (ECC)

Hi All,
Background job is running for long tome in source system (ECC) while extracting data to PSA.
I checked in ECC system SM66,SM50 the job is still running
in SM37 the job is Active
There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
I had checked enhancements every thing is correct.
Please help me on this how can I solve this issue.
Regards
Supraja K

Hi sudhi,
The difference between Call customer enhancement... and Result of customer enhancement:... is very less we can say this as a second.
The difference is between LUWs confirmed and 1 LUWs -
   and Call customer enhancement -
Please find the job log details below, and give me the solution to ressolve this
01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                 R8           048
01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Job finished                                                                               00           517
Regards
Supraja

Issues on Sources System ECC and BI

Dear Friends,
I m trying to get datas (extractions) from ECC 6.0 QA 110 to BI DEV 100. But I only have the Source System to the ECC 6.0 DEV without any data, this connections is working very well. I asked the Basis Consultant to do another connection of the BI DEV 100 with the ECC 6.0 QA 110 using RFC connections with Bitemote with sapall, between ECC and BI. He already did it and I can see at SPRO under SAP NetWeaver > SAP BIW > Links to Other Systems > General Connection Setting > Assign Logical System to Client, on both sides in BI and ECC. The question is, do I need to do Any configuration at the BI side to active (create?) this new Source System ECC 6.0 QA 110? I hope Im clear. Thanks in advance.
Antony

Hi Frank,
I can't imagine any issues compared to other installations. The only thing you need to take care about is that in BI you can only work in one client and in your ecc system you can have multiple clients to work in. These will be treaten as different source systems for your bw.
regards
Siggi

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.

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

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

BI 7.0 Tools for Source System - ECC 6.0

Our company have following version for BI 7.0, before the upgrade (R/3 4.6) and even after the upgrade (ECC 6.0).
2) What is the recmended version of BI tools that can be applied with ECC 6.0 Version. I see some the some of the business Contents are still missing.
3) What is the latest version of BI 7.0 tools we have in the market ?
BI_CONT,      703, 0007
PI_BASIS,      2005_1_700,0013
SAP_ABA,      700, 0013
SAP_BASIS, 700, 0013
SAP_BW,      700, 0015
ST-A/PI,      01J_BCO700,0000
ST-PI,      2005_1_700,0005
Thanks as always
BI

The versions that you have mentioned for ECC 6.0 are quite enough.
Only one thing you have to do is upgrade the support package level to the latest one.
Other than that, it will be well compatible with ECC 6.0 server.
Hope this would help you.

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

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

How can we change the Job priority in the Source system

Hi All,
We are facing an issue with the process chain execution in the Production system. We have a process chain which runs daily in BI system and the chain is designed in such a way, that as soon as the chain starts in BI system, a corresponding job is triggered in the Source system (ECC 6.0system).
Now the issue is that after we have our Source system upgraded the memory allocation for the particular Job (FIGL )is reduced and due to which the FIGL job is failing frequently. When we have consulted some experts.They advised Us to increase the Priority of the Job in source system to A/1, as of now the job is running in B/2 priority.
Please let us know the way how we can increase the priority of the Source system Job, so that when the process chain triggers a job in source system and that particular jobs should run with Priority A/1.
Thanks in advance.
Regards,
Chandra.

Hi Chandra,
First please find the job name in SM37 for FIGL and check the job status to be in "released" status. Select that job and go to job menu and click on change. then it will take you to the job screen where you have "job class". Here you can change the job class to "A" to get to high priority.
If you are unable to edit the job then create a new job with the same variants by clicking STEP button in the Job screen.
Try these steps, let me know if are able to do so.
Regards,
Ravi Kanth

DYNPRO_SEND_IN_BACKGROUND errors in source system

Hi All,
Yesterday night we kicked DELTA Process Chain.
The PC failed While loading the 0GL_ACCOUNT Attributes, and showing the message Errors in Source System.
and also Failed at Cost Element Attributes but both the error messages are same.
Checked the source system connections and repeated the process, but it was failed again. and tried to load manually and again failed.
When we check the DUMP in Source system (ECC) in ST22 showing the message as below:
"DYNPRO_SEND_IN_BACKGROUND" Current screen: "SAPLSTRD " 0351
Note: We ran FULL load day before yesterday and Ran INITIAL yesterday, We are running DELTA TODAY.
one thing is we just deleted the GL attirbutes Requests manually and loaded INIT , we are able to do INIT load perfectly. but while trying DELTA only this problem is causing.
Thanks in Advance,
Teena

Hello ,
Sometimes the problem happens because the background users do not have the correct authorization. Please check the information in the SAP note 150315.
Kind Regards,
Des

RRI using Tcode in source system giving error

Hi,
I am trying to run a report in BW in tcode RSRT using RRI mechanism and the same is throwing an exception - An error occurred with the report to report interface during the jump. The same when run in BExAnalyzer throws an error "A critical error occured".
The selections I have applied are as under:
Target system -> Source System(ECC)
Report Type -> Transaction
Report Destination -> ME2L
Assignments as under:
0DOC_NUM -> EBELN
Any trace to the cause of the error would be helpful.
Thanks,
Amogh

Try creating a program in source whihc calls t-code ME2L and then from RRI try to call the program., and also check if you have authorization to t-code RSRR_WEB &RSBBS_WEB in you source system,
If this did not help give us more detial on the error you are faceing.
Shashi

Configuring of a new source system in BW

Hi Experts
We have to set up a BW system, which will have 2 source systems( ECC) clients 550 and 590 of the same ECC ( ECC QUALITY). One client is already there and we have to configure another client of source system with the sane BW Client 350. I understand that the dataflow is partly different (e.g transfer rules and datasources are source system dependent). My question are
1.     How we can configure a Source System on BW.
2.     What changes if any I have to make in the existing system (BW)
3.     What will happens to the Existing Data-sources ( Do I have to replicate each and every data-source of the existing ECC clients to New ECC client.)
4.     Do I have to create New transfer and update rule for the new client
Any other point Pl. advice.
Thanks in advance.
Dinesh Sharma

You can more than one source system to onw BW client.
You have to use source system compounding to differentiate between characterstics values if you are loading to the same object. Otherwise you need to use separate characterstics for ex : Yxxxx object for one source system and Zxxxx object for another.
Also the dataload timing should be setup properly. Otherwise it may leads to object locks.

No source system connection

Hi Every One,
I am unbale to find the connected source system(ecc 6.0) in visual composer. I have RFC connection between BI 7.0 and Ecc 6.0. Source system column is showing as [None].
could you please tell me how can i configure the connection with my source system.
Thank you,
Regards,
Niru.

Hi Niru,
Have you created a
[RFC destination in NW Administrator?|http://help.sap.com/saphelp_nwce10/helpdata/en/5a/97a066223e440b8ead3da027b17d9e/frameset.htm]. Have you created a [BI System connection?|http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm]
Best regards,
Dharmi

PSA Source System Update Utility

Hi,
We recently upgraded our Sand box system to EPH1 SPS5. The PSA Deletion Process type now includes a 'Source System' field. Since our system was refreshed from Production prior to upgrade, the Source System Field in the PSA Deletion Process Type contains Production source systems.
Is there a utility program provided by SAP to migrate the PSA from old to new? Or A program to update source system in the PSA?
Thanks,
Kartik

You can find more information and discussion in this thread.
Thread locked to avoid duplicate discussion
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Patch upgrade in Source system ECC 6

Similar Messages

Maybe you are looking for