Partiotning, pseudo delta, LUW

Hi gurus,
could you please tell me
how PSA partiotining done. need steps to do it. How is cube partioitning done .need steps.
what is pseudo delta and where is it done , please tell me the steps to do it
What is LUW abbriviation, and whai is its functionality in BW and R/3
thanks in advance
regards

Hi Chaudary,
PSA Partition will be done automatically also in the transaction RSCUSTV6 you could set Packet size and Partition size.
And you can partition InfoCubes using two characteristics calendar month (0CALMONTH) and fiscal year/period (0FISCPER). The special feature of the fiscal year/period characteristic (0FISCPER) being compounded with the fiscal year variant (0FISCVARNT) means that you have to use a special procedure when you partition an InfoCube using 0FISCPER.
You use partitioning to split the total dataset for an InfoCube into several, smaller, physically independent and redundancy-free units.
http://help.sap.com/saphelp_erp2005/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Partitioning infocube :
http://www.crmexpertonline.com/archive/Volume_01_(2005)/Issue_01_(October)/v1i1a1.cfm?session=
PPT:http://www.cs.utk.edu/~huangj/CS594S02/infovis.ppt
Hope The above two links (article and ppt) helps you to understand ..
Pseudo delta is used with generic extractors, to make a a generic extactor delta enabled ...In RSO2 after creating the datasource at the top of the screen you have "Generic delta" icon, click on this & in the following screen you need to select the field on which the delta is to be performed along with the type of delta i.e Numeric or time stamp or on 0calday.
Save the datasource & relicate it in the BW system.
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o each time you start a transaction
o when the database changes of the previous LUW have been confirmed (database commit) or
o when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o when the database changes have been confirmed (database commit) or
o when the database changes have been canceled (database rollback)
Points = thanks,
Regards
Message was edited by:
samara reddy

Similar Messages

Pseudo delta with ABAP or OLAP variables

Hey gurus!
Since I have to post my first question at SDN one day, it may better be now! I'm rather new to SAP BI, therefore your help is requested:
I'm currently implementing a pseudo delta, a full data load from ODS to ODS and subsequently ODS to Cube. The data requested should consist of yesterdays records, which was relatively easy in SAP BW 3.5.
Since it is not possible anymore to, and I quote, choose one of the following selections in the Type (Variable Changing of Selections with Background Processing) entry column from the Data Selection tab page (numbers 0-7, 0 is required), I can now only solve it with creating another OLAP variable or ABAP coding.
Is there anyone that can give me some advice or provide me with some basic ABAP coding which selects data from 'yesterday?'
Your help is appreciated!
Regards,
Joost

Thanks for your reply Pom!
I'm not sure where to insert the '0' as type in my case. I've created a data transfer process instead of an infopackage now, but when setting up my filter there is nowhere to select the type. Or do I have to create an 'old fashioned' infopackage?!
Your help is appreciated, please provide some directions.
Regards,
Joost

Reverse images in Pseudo delta

Hi All,
I have a generic extractor which fetches data from ECC based on pseudo delta.
I am using type 0 in the date field to bring the delta records to BI.
Problem.
when I load a record to bw for example a PO today and today the PO is deleted in ecc and when I load the data tommorow to the bw, the record needs to get deleted from DSO and CUBE.
To identify this I have a field 'deletion indicator' which i mapped to 0strno info object in the DSO.
Reverse images are identified by the indicator 'R' but deletion indicator is marked as 'L'.
How will the system identify the reverse image in this case?
Please le me know the solution for this.
Points assured.
Regards
Joga

Ian, after looking at what SAP suggested 'Get Delta Only Once,' this should work for your scenario:
Indicator: Only Get Delta Once
Source requests of a DTP for which this indicator is set are only transferred once, even if the DTP request is deleted in the target.
Use
If this indicator is set for a delta DTP, a snapshot scenario is built.
A scenario of this type may be required if you always want an InfoProvider to contain the most up-to-date dataset for a query but the DataSource on which it is based cannot deliver a delta (new, changed or deleted data records) for technical reasons. For this type of DataSource, the current dataset for the required selection can only be transferred using a 'full update'.
In this case, a DataStore object cannot usually be used to determine the missing delta information (overwrite and creation of delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this indicator and perform a snapshot scenario. Only the most up-to-date request for the DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again during the DTP delta process. When the system determines the delta when a new DTP is generated, these earlier (source) requests are seen as 'already fetched'.
Setting this indicator ensures that the content of the InfoProvider is an exact representation of the source data.
Dependencies
Requests that need to be fetched appear with this indicator in the where-used list of the PSA request, even is they have been deleted. Instead of a traffic light you have a delete indicator.
-Alex

Pseudo delta load problem

Hi all
I have schedule a pseudo delta for HR Training, input for the package is as 01.08.2008 to 30.08.2008 but if my package does not have any record for that month then it will not delete my request for the month so I have 30 request in the cube. If I get a single record then it delete all request of that month
So pl. guide me how I can overcome this situation , so even if there is no record for entire month it should delete my previous request.
Thanks in advance
Charudatta

Hi Kotha123:
Take a look at SAP Notes below.
745445 - "CRM-BW: Incorrect partners extracted in the delta".
1178613 - "CRMBW Sales: Created date differs in delta from init upload".
987142 - "CRM BW:Incorrect data from data source 0CRM_QUOTATION_I".
793986 - "Extractor:Status fields not filled in parallel processing".
Regards,
Francisco Milán.

Pseudo Delta Document

Hi,
We are planning to implement Pseudo Deltas for FI-SL transactional data. I don't know how to set Pseudo Deltas for FI-SL in R/3. Could any one send me the Pseudo Delta document.
Any one help is really appreciated.
Thanks,
Kiran

Hi,
Psuedo deltas are usually set up by putting in selection criteria in the infopackage selection of the full infopacakge.
Or you can write routines to filter out specific data and then load that.
Cheers,
Kedar

What is Pseudo Delta

Hi,
Can anyone throw light on Pseudo Delta Concept ??
Thanks in Advance,
Vishali.G

Hi Vishali,
Pseudo Delta processing is achieved by filtering dates in the InfoPackages.This is not the same as normal delta process that we do to extract the newly updated/ modified records. if you look at the data load it would say FULL LOAD instead of DELTA. But as a matter of fact, its only pulling the records that are changed or created after the previous load. This can be achieved multiple ways like logic in infopackage routine, selections identifying only the changed records and so on.
1) Normal delta (change log table will identify the changed records) with the option of Delta in the update tab of IP.
2) Psuedo Delta: This is a full load with calendar day selected as today's date in the selection tab of infopackage.
Realize that in both the cases you would be sending the same records, but the second method uses full load with restrictions (psuedo delta) while the first load is a straight delta.
Regards
KP

Pseudo Delta

Hi Gurus,
I want to implement a function module extraction in CRM with psedo delta field as change date, but this field is a time stamp field and and even when i enabled selection option for this field, this is not coming in the infopackage selection in BW side.
I want to know Whether timestamp cannot be made as an infopackage selection field? or do we have to make some setting to replicate this in BW side?
Regards,
Raghavendra.

Hi,
What are the changes that i should make in the function module to make it delta enabled. i have used the standard function module rsax_biw_get_data_simple and modified it according to my needs.My delta field is change date which is a timestamp field.Is there no way to make timestamp field as selection field in infopackage?
Regards,
Raghavendra.

What is Pseudo or Fake Delta

Can any One Please Give Some SAP link/Documentation for Pseudo Delta .

Check these links:
Fake Delta
Data Recovery in delta loading
Hope it helps.
Regards

0FC_BP_ITEMS: ERP customizing and delta mechanism

Hi BI fans
I have two questions:
1.) The following link describes how to make the settings for delta enabling of datasource 0FC_BP_ITEMS:
http://help.sap.com/saphelp_nw70/helpdata/en/27/42073e774a4329b6dd6bab21eef613/frameset.htm
Prerequisites-
"...If you want to use the delta method, you first have to activate it in the Implementation Guide for Contract Accounts Receivable and Payable -> Integration Business Intelligence -> Maintain Central Settings in the clients of the OLTP system..."
But I cannot find the setting for "Maintain Centrall Settings" in the implementation guide!
Any idea from your side?
What I see are entries for:
Define Fields for the Extraction of Items
Define Grid for Grouping of Items
2.) What is the exact delta logic of this extractor (working through function module)?
Which fields are relevant for the delta logic?
Thanks
BEOplanet

Hi Andrea
First of all I activated the whole content (datasource, BW content, etc.).
Regarding the pseudo-delta on CPUDT I have designed a BEx variable on a DATS 8 time characteristic, e.g. 0NETDUEDATE. It is a BEx variable feeded by a customer exit, you will find a sample coding below. Furthermore an interval variable, mandatory input.
Screen for BEx variable properties:
Assign this BEx variable into your infopackage for intended use of pseudo-deltas, type OLAP-variable:
The sample coding below gives you an idea about our pseudo-delta mechanism, from 1st. of last month until sy-datum.
Data wa1 like line of e_t_range.
data d1 type d.
data fdate type d.
data fyear type d.
data ldate type d.
data fmonth type d.
case i_vnam.
when 'ZL2MTDY'. "BEx variable on 0NETDUEDATE or any other DATS 8 time characteristic
d1 = sy-datum.
fdate = d1 - 31.
fdate+6(2) = '01'.
ldate = sy-datum.
wa1-opt = 'BT'.
wa1-sign = 'I'.
wa1-low = fdate.
wa1-high = ldate.
append wa1 to e_t_range.
ENDCASE.

0HR_PY_1_CE - Delta init with time limitations

Hallo everyone,
I want to use the Content-Extractor 0HR_PY_1_CE to transfer payroll data into SAP BW in delta mode.
As the source system is running payrolls for a very long time allready, I would like limit the data by time. Pittily the extractor does not support filtering by time in delta mode. (Found this on SAPs help pages and also tried to set start and enddate ... no luck as assumed.)
So I had a look at the source systems customizing, but the only setting regarding a time frame for extraction I found is the one for PT-data. (Transaction SBIW -> Settings for Application-Specific DataSources (PI) -> Human Resources -> Define Time Frame for Transfer)
Within the PY-Customizing there is no option to limit the extraction interval.
Is there any other way to limit the extraction to a specific time frame when loading data via 0HR_PY_1_CE?
Thanks a lot in advance and regards
Chris
Edited by: Christian Baum on Jul 27, 2010 12:15 PM

Hi Yuvaraaj,
thanks for taking the time to answer my question.
For time selection I use the extractors default datafields: BEGDA and ENDDA.
Pseudo-delta might be an option IF the two fields you mention are processed in the extractors selection logic. I actually don't know and would need to take a closer look on the extractors programm logic.
Anyway my goal is to stay as close to SAPs standard as possible.
Pittily the extractor does not support filtering by time in delta mode. (Found this on SAPs help pages and also tried to set start and enddate ... no luck as assumed.)
I had another look at [SAPs documentation for 0HR_PY_1_CE|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6a/cccc6015484464b25605375a5db965/content.htm] and have to recall the statement above.
As there is no restriction mentioned about delta and time selection there must be a way to pass a time frame when initializing the delta.
I tried the following:
1. I startet an Infopackage in full mode with the follwing filter criteria: BEGDA = 01.10.2009; ENDDA = 31.10.2009
The extractor dilivers ~60000 records; their inper is allways 10.2009. -> Selection worls fine
2. I started an Infopackage in delta init mode and exactly the same selection criteria as the full mode Infopackage and i receive millions of records whichs inper is spread over several years.
So the time selection is definitely not working in delta mode.
Are there any customizing settings I missed in the OLTP system?
Regards
Chris

Stop/start of BW 7.0 system-- how to deal with deltas when moving instance?

Dear BW guru's,
we are moving a BW 7.0 system to a new datacenter, where the R3 source systems remain the same.
What should we consider when we want to stop the system, move it, and restart the next day, when the source systems cannot be stopped?
Specifically I may need to clear the delta queues in BW before stopping and moving the system.
After the system has been installed in it's new location, can we just the delta process chains without any other action, and will it extract the delta's from source system where it left of before?
is there something I am overlooking?
thanks for tapping your collective brainpower,
-jh

Hi,
When you are miving instance and source would be on during that period then you may look for follwoing.
Stop the loads and resume the delta after movement.
If there are some jobs for fetching data in R3/ for BW data source then those needs to be stopped and rescheduled as some time those jobs define the delta in BW.
If there are pseudo delta or some hardcoding for extracting delte then need to take care of the as well.
I hope it will help.
Thanks,
S

How many Delta types are availabvle in Lo Extraction

How many Delta types are available in Lo Extraction
please tell me i am facing in every interview.
Thanks in advance,
Ashok V

hi
now three types of update methods are available in Lo extraction
A.Direct Delta:- In case of Direct delta LUWs are directly posted to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUWs are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
B.Queued Delta: - In case of Queued Delta LUWs are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUWs, which are missed.
D.Un serialized V3 Update: - In case of Un serialized V3 update LUWs are posted to Update Queue ( SM13 ), by scheduling the V3 job which move the documents from Extractor queue ( LBWQ ) to Delta Queue ( RSA7 ) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Since the LUWs are not moved in a Serial fashion from Update queue to Delta queue if we have any error document it considers the subsequent documents and no sorting of documents based on the creation time. It improves the OLTP system performance as it forms a segment for one language.
hope this will solve your problem
nagarjuna

What is a queued delta?

SDN experts
I like to know what is a queued delta and whe we use this?
What is a data dictionary can you explain me in detail?
Thank you,
York

Hi Les,
Queued Delta:
In case of Queued delta LUW's are posted to Extractor Queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. Generally we prefer Queued Delta as it maintain the Extractor Log which us to handle the LUW's which are missed.
Direct Delta:
In case of Direct Delta LUW's are directly posted to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW's are directly posted to Delta Queue (RSA7) the application is kept waiting untill all the enhancement code is executed.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
https://websmp102.sap-ag.de/~sapdownload/011000358700007535452002E/HOWTOCREATEGENERICDELTA.PDF (need id)
http://help.sap.com/saphelp_bw33/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Business Intelligence Performance Tuning [original link is broken]
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
How to load data
/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
Delta Types and methods;&#57245;
Hope this helps.
****Assign Points if Helpful*****
Regards,
Ravikanth

Init+delta in BW, subsequent delta in BI - upgrade issue

We are upgrading to BI patch 16 from BW 3.5.
Our BW dataload flows are - R/3 extractor to ODS via infopackages (PSA and then data target option), then to the infocubes via infopackages (same option).
In BI, data come to PSA via infopackages, then to DSO via DTP. From DSO data go to the infocube using DTP (no PSA). For DTP we use 'Get data by Request' option and extraction mode is delta.
We already have deta loaded in the system in BW. Daily process chains load delta records. We would like to continue the process by doing just the delta load in BI (without deleting old records and doing a new init in BI).
What happened is, delta load to DSO went fine after the upgrade. However, when loading to the cube DTP started to bring back all old data to the cube (past init and delta records) duplicating data in the cube. After first run subsequent run to the cube goes fine, bringing just the delta records.
What set up are we missing for the infocube so that we can continue with delta loads in BI after upgrade from BW?

Delta Load to DSO must have been fine due to Overwriting updated option in the transformation which will not cause duplication of data.
However, executing the DTP to the Cube will fetch all data from the Source as the previous data was not loaded using the DTP.
To prevent this you should have a pseudo Delta DTP
Or
There is some new feature for DTP - something like " Donot fetch data set the delta pointer " - You may use that if available.
Remember to run the DTP " N " number of times if you have N number of requests in the source if you have checked the feature " Get data by Request " .
After all requests have been marked as fetched by the Delta DTP - Remove the filter.

0operation_text - delta available?

Hello,
I am trying to use the datasource 0operation_text loading text related order/operations. It looks like only full load option available. In our system we have more than 20 million records if I use the full load option. This means every time I run this load it will have to reload all 20 million records. Do you know of any ways to load this same data using delta, so I don't have to reload 20 million every time? Currently only order# / lanugage / operation only available for selection in the infopkg of this data source. These fields are not helpful in our situation.
Thanks in advance for your help.

There is no delta available for 0OPERATION_TEXT. In order to "delta-enable" this extractor, we have added a User Exit to populate the creation and change date from the operation and then do a pseudo-delta in two InfoPackages with ABAP routines, one for each date, to extract create and change date records that are within 3 days of the current date. If there's a better way to do this, I'd be glad to hear it because this isn't exactly how I'd like to do this.

Partiotning, pseudo delta, LUW

Similar Messages

Maybe you are looking for