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?

Similar Messages

How to do delta management for fi module?

how to do delta management for fi module?

Hi,
Take a look on the following help site,It has all most all information about FI extraction:
http://help.sap.com/saphelp_bw32/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
With rgds,
Anil Kumar Sharma .P

How To Generate Spool request for a SAP-Script form

How To Generate Spool request for a SAP-Script form

Hai Rahaman,
After getting the print preview of the SCRIPT.
Click On PRINT.
Buttom of the page one spool request will be generated by system.
Go to SP01.
You Can Find SPOOL Reqest Number.
Regards.
Eshwar.

Should I buy the imac with expandable memory slot for future os upgrade size?

Should I buy the imac with expandable 8gb memory slot for future os upgrade size?

I Always try to have a little more RAM on my computers that I think I'll need when I purchase them. Either have more ram installed when you order the iMac or purchase one with open slots for upgrading.
I Purchase my iMac 5K with only 8 GB RAM but it had two open slots. As soon as I received the iMac I purchased two 8 GB modules form Other World Computeing. That brought my RAM to 24 GB. I run multiple applications and the iMac runs smoothly.

How to configure the database monitoring (DBA Cockpit) after Support pack

Hi,
I did the Support Pack Upgrade for BW system and i ran SGEN as well, now i need to configure the database , could you please suggest how to configure the database monitoring (DBA Cockpit) after Support Pack Upgrade.
Server is MSSQL , Component is SAP NetWeaver 2004s and OS is Windows NT.
Plesae suggest.
Chandu.

Hi,
You are right. SAP delivers this functionality from SP-12. So when you have applied the SP-12, you must have done these config steps to enable the DBA Cockpit.
If you have done these steps earlier, So you must have DBA Cockpit enable right now and putting extra SPs like 13, 14 and so on, should not be a matter.
Now if you have not performed those config steps before, Please do them now and you will be able to use DBA cockpit.
Please understand that SP12 is the base to run DBA Cockpit.
With Regards,
Saurabh

SAP BW Support pack

BW Experts,
Can anyone tell me what is the recent most SAP BW Support pack? My client is on support pack 19, and they want to upgrade it with the version previous to the most recent one.
Thanks
Ashwin

hi Ashwin,
yes, the note mention the impact.
for steps please find here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/ff9036e1e4b603e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
normally this task is done by basis.
hope this helps.
783253
Symptom
Support Package 23 for BW Release 3.1 Content
Other terms
SAPBWNEWS, Support Packages for 3.1 Content, BW 3.10, BW Patches
Solution
This note contains the SAPBWNews for Support Package 23 for BW Release 3.1 Content. It contains a list of all notes that describe the corrections and enhancements in Support Package 23 (SAPKW31023). This note will be updated as soon as further notes are added.
The information is divided into the following areas:
Manual actions that may be required:
Factors you must take into account when you import the Support Package.
Errors that may occur after you import the Support Package
General information:
This Support Package corrects the following errors.
Enhancements delivered with this Support Package
Note 539867 contains further important and necessary information about importing Support Packages for BW 3.1 Content, and this information does not refer to any particular Support Package.
For example, Note 539867 contains the necessary patch level for the basis system and other essential information about importing the Support Packages, as well as information about problems that originate in other systems but may also appear in BW.
Note 539867 also contains the planned Support Package release dates. The note is regularly updated to include the most current information (the last update was on NOV/08/2004).
Therefore, we strongly recommend that you refer to this note before you import the Support Package. To subscribe to the note, refer to the instructions contained in Note 487366.
Support Package 23 for BW 3.1 Content corresponds to the technological level of Support Package 29 for BW 3.0B (SAPBWNews 783251).
Factors you must take into account when you import the Support Package:
After you import the Support Package, remember to restart the application or to use $sync to clear the temporary storage.
If filter value selection takes a long time, refer to Note 912773.
Errors that may occur after you import the Support Package:
Querys on MultiCubes in read mode A. For more information, see Note 896066.
The query shows more rows. For more information, see Note 901097.
The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
This Support Package corrects the following errors:
Enhancements that are delivered with this Support Package:
Refer also to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.x Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Enhancements in the area of OLAP technology:
General performance improvements for OLAP. For more information, see Note 825396.
The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
Unnecessary reading of partprovider. For more information, see Note 885733.
The performance in from SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
Query runtime if there are several nested formulas. For more information, see Note 872904.
Information regarding the system component validation:
The Support Package was validated at a specific level of the system components that are available at this time. We therefore recommend that, in parallel to the BW Support Package upgrade, you adjust the system environment to the version of the individual components.
You can find more information in the SAP Support Portal at http://service.sap.com/swdc:
-> Additional Download Information -> SAP Support Package Stacks -> SP Stack Information and Download -> SP Stack SAP BW 3.1 Content

How to delete the data in update queue and delta queue for Queued delta?

Dear BWers,
How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
Thanks
Raj

Hi Raj,
I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance.
Please let me know if these material has been suffecient enough.
regarda,
raj

Critical issue - delta queues for LIS empty after upgrade BW3.5

The delta queue in R/3 for LIS sources (S260-261-262) remains empty,
even after a successful init delta. Hence I cannot extract delta
records.
BW3.5
PI2004.1
Does the BW upgrade has an effet on the delta queue management in R/3 ?
The previous configuration BW2.0B PI2004.1 did work fine in that
respect.
Laurent Querella
BI Consultant ALTI

Laurent,
from OSS Note 534296 'LBW0: DataSource generation possible for SAP info str.' you can read:
"(...)it is no longer possible to generate DataSources for info structures (transfer) Snn delivered by SAP (where nnn is between 001 and 500) in the BW interface for LIS info structures (TR: LBW0) in the OLTP. (...)The corresponding DataSources are delivered with the Business Content."
I think this is the issue...
However, are you saying that all infostructures are empty ?
And from where your init is taking data ?
After an init your delta tables have to be empty...did you empty all these tables before doing your upgrade ?
Bye,
Roberto

How to find the report for the SAP query (Query exists in table AQLQCAT)

Hello Experts,
I need to find the tables used in the SAP Query but i don't have access to transaction SQ01,SQ02 and SQ03 to check the same.
Therefore i checked table AQLQCAT and got the SAP Queries in the system. Then searched for the reports that would have been generated for the same passing AQusergroupquery name* in transaction SE38.
But unfortunately the program does not exists for the given paramenter.
Could you please let me know how to get the report name for the SAP Query.
Secondly please suggest any other way of checking the tables used in the SAP Query.
Also the table name from where i can download the SAP Queries.
Thanks in advance.
Regards,
Rahul Sinha

I suggest you a simple method.
Execute the query. When the selection screen is showed, go to menu and click to SYSTEM->STATUS.
Check the program name and double click it to access the program code.
Search for tables or functions into the source code in order to understand where data are taken.
If you do not find anything , go to the program atttribute and check for logic database, sometimes they are used....
Best regards.

No records in delta queue for 0CRM_SALES_ACT_1 & 0CRM_COMPLAINTS_I

Hi all,
we are linking a SAP CRM system 4.0 (patch level 10) with BW 7.0. We have initialized the delta extraction and everything was fine. Data was extracted and we can see the delta queue in RSA7 but no records are added. Users are creating new activities and nothing appears in the delta queue. We have other extractors delta capable which are working fine.
The main difference is that these two extractors have been enhanced using the Badi CRM_BWA_MFLOW. When we check the extractor using transaction RSA6, records include the information we add in the Badi.
We think the problem is in CRM because, it does not collect any delta data (queue is always empty). BW is capable to extract when initilitialization. We have tried the early delta initialization and the simple delta initialization.
Any help will be appreciated.
Thank you in advance.
As an extension: we can't see the extractors in the qRFC monitor (trans. SMQ1). We can see there the ones which are working...

Hi again,
we finally solved the problem. The thing was that no BDOCS with type BUS_TRANS_MSG were not being generated when creating or modifying CRM activities. Theses datasources need the BDOCS to work. Transaction SMW3_00 had the flag "Do Not Send" set. We unmarked it and everything seems to work now.

How portal finds the vale for the sap-language parameter for iView

In the portal one of the ABAP WebDynpro iView is getting displayed in German. The reason for that is the sap-language parameter is being passed as DE. All other iViews in the system are passing the sap-language parameter is as en.
In our system the Logon Language property is blank for the all the iViews. Could you tell me why one specific iView the sap-language is being passed as a DE?
How the portal finds the value for the sap-language parameter?

Hello Venkata,
Check if your Component locale is set to DE.
Component locale
This locale is defined by the following component profile properties:
--ForcedRequestLanguage
--ForcedRequestCountry
Check this for more:
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/938297a5061d69e10000000a1553f6/content.htm
Greetings,
Praveen Gudapati
p.s Points are always welcome for helpful answers

How to create t.code for a sap query

i have created a sap query.
user wants this as a t.code.
how to assign a t.code for teh sap query.
kindly explain me.

hi,
The other way of doing it.
1. Instead of creating your queries in SQ01, use SQVI. Create a query in your production system.
2. Now execute the query. When you have reached the selection screen, go to System > Status.
3. Copy the program name.
4. Now create a Z executable program in your development client. Put this one line of code in it:
submit program_name_copied_fr_production via selection-screen and return.
5. Create a TCode and assign the Z program to the TCode.
6. Transport the Z program and TCode over to Production system.
Hope this works for you, Do reward.

Zero records in Delta Queue for Non-LO Datasource

Hi,
I have a process chain which loads data daily and last loaded on 5th of this month which is a delta load to DSO, and then I have triggered process chain on 10th and now the process chain got successful but delta is returning zero records. I have gone through the Delta queue monitor, in that the data source is showing 0. what could be the reason for this? The data source is a Generic data source built on View and it is not a LO data source and delta is on timestamp.
Thanks,
Karan.

Hi lokesh.
Repair Full delta option it wont distub existing deltas.....
repair full delta put full update indicate request as repair request.
Via the Scheduler menu we can indicate a request with full-update mode as Repair Full Request. This request can be updated into every data target even if the data target already contains data from an initialization run or delta for this Data Source/ source system combination, and has overlapping selection criteria.

How do we find tables for standard SAP programs?

Dear Friends!
I have received a project in which I have to create a report on the employees skill-sets(qualifications). Qualifications we can see in in the Transaction PA30 in the form of infotypes. But infotype tables are not sufficient itself. So do you guys have any idea that where else do we maintain records like this moreover how do we find tables in standard SAP Programs.
Please reply!!

Whats up Guys...??
Gave up??
I have found a table for position but not really for Qualifications.. (Not in terms of Infotypes..)
Tables ARE
HRPY_WPBP
- PERNR
- PLANS
T528T
- PLANS
- PLSTX
See if you guys can do something more about it.

Generic delta queue for CDHDR

Hi,
Has anyone used the function module to create a generic delta queue to work for extracting data from tables CDHDR and CDPOS when using the UDATE as the change date? I was able to find an alternate solution to extracting the data from these tables, but the solution is not approved, and it is suggested to use the function module and use a changed date to create the generic delta queue from RSO2.
Please advise.
Thank you

Hi Siggi,
Thank you for your insight on this. Well, UDATE is the changed date in the table CDHDR, and I am wondering if that should be used to provide to the RSO2 setup and set the interval to 1 day. I am extracting this UDATE to my extract structure.
Here is what I have in the FM and I am loading right now. I provided the date range to the 'Data Selection' tab for a complete year, which should only be 100K records but it is now extracting up to 17M records and still going. I am not sure if I should stop the load because it seems that it is loading the complete table CDHDR which is 80M.
Here is my code form my FM:
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'UDATE'.
        MOVE-CORRESPONDING L_S_SELECT TO L_R_UDATE.
        APPEND L_R_UDATE.
      ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
      OPEN CURSOR WITH HOLD S_CURSOR FOR
     SELECT (S_S_IF-T_FIELDS) FROM CDHDR
                              WHERE UDATE IN L_R_UDATE
                              AND   OBJECTCLAS ='ORDERBUCH'.
SELECT OBJECTID CHANGENR USERNAME UDATE UTIME OBJECTCLAS TCODE
         FROM CDHDR
      WHERE UDATE IN L_R_UDATE
      AND   OBJECTCLAS ='ORDERBUCH'.
I have the other SELECT commented out because I was getting an error dump on the R3 side saying "One of the field names in the SELECT clause was not recognized.", referring to statement "OPEN CURSOR WITH HOLD S_CURSOR FOR", so I am using the other SELECT that is not commented out.
I think I am following what you are referring to about the SELECT but not quite completely. What would you suggest to rewrite for the UDATE issue to process both the Full and Delta data?
Thank you

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

Similar Messages

Maybe you are looking for