R/3 Delta queues in support package upgrade

Hi gurus,
Our team needs to apply a support package upgrade to our BI 7.0 (without an upgrade in R/3 source system).
Do I need to worry about SM13 and RSA7 in my source system R/3 or just my data marts inside 7.0?
Or do I need to empty R/3 delta queues before BI upgrade to prevent data loss?
Best regards,
Enric

You may wish to take a look at below for few insights -
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
https://forums.sdn.sap.com/click.jspa?searchID=10299818&messageID=3221895
Hope it Helps
Chetan
@CP..

Similar Messages

Impact of Support Package Upgrade on languages

Dear Experts,
We have our client with SAP CRM enterprise, ISA and MSA implemented in various countries and many languages (HU, PL, CZ, N, GR etc). We would like to know if SP (Support Package) upgrade will have any impact on the languages.
Any pointers or help would be grateful. Since we need this information urgently, any help in this regard would be of great help.
Points will be rewarded for useful answers.
Regards,
Kathir

There will be no impact of SP's on languages. We recently installed a few SP's for our CRM 4.0 system and did not have any impact.

How to flush Delta queue for future SAP upgrades/support pack !

Guys,
I'm making documentation regards to " How to flush Delta Queues" in case SAP wanted to upgrade the system or any support pack. Please anyone let me know the effective way to flush out the delta queue in step by step methods. I really appreciate your help.

1. Run V3 for associated application(s), this will load any potential delta data to the delta queues.
2. Run the delta load for each datasource twice. The second load will clear the delta repeat data so that there should not be any more data in the delta queues defined with the format of the current datasources.
Does this help?

Support package upgrade / SPAU with multiple queues

Hello, We are upgrading our support package level on our ECC 6.0 system. I divided up the support packages into 4 different queues:
SAP_BASIS
SAP_ABA
PI_BASIS
ST-PI
SAP_BW
SAP_AP
SAP-HR
After importing each queue, I had a few things to do in SPDD and SPAU. I created a new SPDD or SPAU transport request for each queue. My question is now what is the recommended procedure to handle these SPAU/SPDD transport requests when you have multiple queues? I plan to define the same queues when doing QA and PRD. Do I mark all of the requests and then when I do each queue, I only specify that particular request? Thank you in advance for your help.
Best regards,
Russ Cook

Hi Russ,
when did you export the different SPAU requests or didn't you export them at all?
If the export happens only after all queues are already imported, this final system state (component version + SP level) is stored in the requests.You are then not able to include e.g. the request for the SAP_BASIS SPs into the SAP_BASIS queue, because the other components are still on the old version, while according to the request they should be on the newer state.
So, the right procedure would be; import the SP queue, do the modification adjustment for this queue, mark the workbench request as modification adjustment transport request and export this request. Then you can import the next SP queue.
Best regards,
Dirk

R/3 Delta queue during 3.5 upgrade

Greetings Experts,
We're upgrading from BW 3.1 to 3.5, and the documentation calls for clearing the R/3 delta queue before the upgrade. My first question is...how do I do this? If I run all of our delta loads to clear the queue, they will start filling up again almost immediately. Do I have to cancel all my delta loads, then reinitialize after the upgrade?
Also, should I time clearing the delta queue with the BW 3.5 upgrade, or should I time it with the upgrade to the PI 2004 in the R/3 system?
Thank you very much

Hi,
I am still in doubt if it is necessary to stop the productive work in the R3 system during the upgrade or if it is enough to stop the collector jobs (RMBWV3*) and empty the delta queues?
If the R3 system would be up then the MCEX queues would be filled during the upgrade. So there would be entries in LBWQ but no entries in RSA7.
Has onyone left the R3 system in production mode during the upgrade?
Thanks,
Timo

Custom application is not working after the support package upgrade.

Hi SDN Folks,
I have upgraded the portal from SP09 to SP25 successfully. But after the upgrade our custom application is not behaving as before. When we submit anything in the custom page its returning to home page. No error in the log files also.
Custom application is a devoloped in webdynpro java.
Kindly suggest.
regards,
Mahesh.N.R

Hi Sita,
Currently I canot take help form the developers, please let me know where i ca checkwhether the custom URLs are set to home page.
regards,
Mahesh.N.R

How to deal with delta queue when importing Support Package/Kernel Patch

Hi,
From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
Do we need to clear down the delta queue every time we import support package?
Anyway, is there anyone have any suggestions or steps regarding this question?
Many Thanks
Jonathan

Hi,
Delta queues during support package upgrade
Its always better to drain the delta queues before an upgrade.
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.
Page 17
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.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
Start with the Why Not the How When You Upgrade to SAP ERP 6.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
Rapid SAP NetWeaver 7.0 BI Technical Upgrade
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
Hope this helps.
Thanks,
JituK

Basis Support package level of ECC 6.0

Dear All,
I use SAP Version ECC 6.0 (700 Kernel, 64bit) Database SQL.
My question is what should be the support package level of ECC 6.0? SAP recommends for the latest support package level always. But, whether the latest support package level will be stable?
We are in the blue print stage now, I haven't received any requirement from the fuctionals for the support package upgrade.
We have modules like, SD, MM, FI, FICO, HR, PS and CS.
Anyone worked with these modules who can provide me, the particular components related to these modules with the stable support pack level.
Thanks in Advance,
Abu Sandeep

Hi,
Yes, for a new installation always go for the last support packages.
After going live, NEVER, NEVER apply support packages without qualifying them for YOUR company in a test system. It takes a lot of time to do non regression tests but it is mandatory IMHO.
Regards,
Olivier

Support Pack upgrade issue: Request deletion dose not work on CUBE

Hi Gurus,
We recently had a support package upgrade from SAPBW701 SP6 to SAPBW702 SP7.
We have an Info package request stuck in yellow state for DSO Load in HR Data.
We manually made it red and are trying to delete it manually/by creating a variant for Delete target contents in the process chain. It is not getting deleted.
Rather if we use the Delete target contents variant previously created before the support package upgrade, it works fine.
Please help me if any one can suggest any SAP NOTE or some other solution if possible.
Thanks in advance,
Sourabh Deo

Hi,
i think you have made it to red in request tab and tried deleting. Actually , you have to make the QM status red in Dataload monitor by double clicking the TOTAl technical status.
After the above activity, then try deleting.
I don't think its a Service Pack problem.
Regards,
Suman

Unable to Login & Ececute any transaction after Applying Support Package

Dear all,
After applying SAP_BASIS Packs (SAPKB700..) support pack from level 15 to 18, the it got cancelled and when i try to execute any transaction i am receiving ABAP dump "syntax_error".
When i try to login i m getting the following msg. " Syntax error in program "SAPLSDOC ""..
SAME MESSAGE IS POSTED IN 2007 BUT NO ANSWER
Unable to login after applying patches
could you help me to resolve this problem?
Thanks and regards.
Subbu

Hi,
Is Support Package upgrade failed in IMPORT_PROPER step ? then plesae refer
support pack SAPKB70014 stuck at import _proper! Very urgent.
http://www.sapfans.com/forums/viewtopic.php?f=12&t=309661&p=954180
We also faced same issue in Solution manager and issue solved by running to r3i commad
tp r3i <SP_name> <SID> pf=<transport profile> -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= tag=SPAM
eg:
D:\usr\sap\trans\bin>tp R3I SAPKB70014 SID pf=TP_DOMAIN_SID.PFL
-Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= tag=SPAM
Note: Before executing above command please contact SAP (OSS message)
Thanks,
Preethish

Support Package and Delta/Extractor functionality

Hello Experts,
We have been testing the New GL Totals Delta and Extractor functionalities. Previously when Support Packege 13 was installed, the Delta was bringing incorrect results.
Now we are using Support Pack 15. Now if i post documents in ecc and upload to bi, the Delta is working properly and values match in ecc and bi.
Could you please suggest if there have been any changes or upgradations in the New GL Totals Delta/Extractor functionality between Support Packages 13 and 15.
Thanks and Regards,
Labanya.

Hi,
Its always better to drain the delta queues before an upgrade.
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.
Page 17
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.
upgrade preparation and postupgrade checklist
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.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820 [original link is broken]
thanks,
JituK

Impact of database upgrade in Bw delta queue

Hi Gurus,
We are going to upgrade the R/3 oracle database. I suppose that it have an impact in the BW delta queue, and that before the upgrade the logistics queues should be uploaded to BW.
I'm right? exits some note or some checklist about wihch activities should be performed in BW due to the database upgrade?
Thanks in advance for your help.

Hi,
This speaks about support pack upgrade. But i think this also applies for DB upgrade too.
Its always better to drain the delta queues before an upgrade.
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.
Page 17
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.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
thanks,
JituK

Upgrading the BI Content to 7.03 and Support package 14 in BI client

Hi Experts,
My Production system is having BI content 7.03 and the support package is 1. I wish to import the support package upto 14 as soon as possible for my requirement.
Can anyone please answer my below questions..
1. What steps should be followed ?
2. What should be taken care of ?
3. What downtime should I take ? Should it be for R/3 and BI both ?
4. Should I clear the queues in RSA7 before upgrading the content ?
If some point is left, please write it so that it can be considered in my case.
Your help at the earliest will be appreciated.
Thanks in advance.
Regards,
Romil

Note 1000822 - Overview: Notes for the add-ons BI_CONT and BI_CONT_XT
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/c0994772-53d7-2a10-7eb3-a8cee3cf5c35 [original link is broken]
https://websmp208.sap-ag.de/swdc
Colin

Upgrading the support package

Dear All,
We are going to upgrade the support package in R/3 side. Our delta records are running everyday.
Kindly let me know what are the precautions to be taken.
Points will be rewarded
Thanks in advance
Sathiya

Hi,
All V3 jobs to be suspended and all the delta records to be fethed into BW side before the SP implementation.
For this the easier and better approach, if you have so many delta packages for different applications to handle, bette create a Info package group and run it just before the SP implementation twice to bring all the records,
Hope this helps
Regards
Srini

Delta package not fetching all records from Delta queue in r/3

Hello,
I have loaded Goods Movement Data using 2LIS_03_BF datasource into my BI system.
The Delta has been initialized and everyday the delta is being moved from r/3.
I observed that when I execute my delta package not all delta records are fetched into PSA from r/3.
For Ex: Before starting my delta package I checked in SMQ1 of my R/3 system and see that there are around 1000 records.On executing the delta package I see that the record count is reduced from 1000 to 400 in SMQ1.On executing the delta package again I get the remaining 400 records into my PSA.
Shouldn't the delta package get all records from the queue on single execution??
Is there some setting to define the nr of records to be loaded?
I'm confused with this behaviour.Please help me understand this behaviour.
Thank You.

Hello,
First thing: the data is not transferred from the SMQ1 queue, rather the data is transfered to BW from the RSA7 Delta queue. You need to check the number of records present in the RSA7 queue.
Since SMQ1 is involved, i think you are using the unserialized V3 update method. In this method, when data is first written to the application tables, it is first transferred to the SMQ1 update queue,then via a job to the LBWQ extractor queue and then to the RSA7 delta queue. So the number of entries that you see in the SMQ1 queue are not the number of entries that have to be transferred to BW but rather the records that are waiting to be transferred to the extractor queue in LBWQ. Similarly, in LBWQ, the number of entries displayed here are not the no of entries that are going to be transferred to BW, they are the no of entries that will be transferred to the delta queue RSA7 when the next v3 update job runs.
If you want to check the number of records that will be transferred to BW, select the datasource in rsa7 and then click on the display data entries button.
Hope this helps.
Regards.

R/3 Delta queues in support package upgrade

Similar Messages

Maybe you are looking for