DTPs - Delta Init without Data transfer.

Hi All,
I am implementing the DTPs in my project where we replicate the old 3.x extractions with the bw7x functioanlity;
Can anyone tell me if their is way to implement the "Delta Init without Data transfer" scenario with DTPs for
both R/3 to BW(ODS) extraction or for the Datamarts - ODS to Cube within BW??
Thanks in advance!
Cheers
Rao

Hi Rao,
Yes u can achieve Initialization without data in BI 7 DTPs.
Goto ur DTp's Execute Tab, and Processing mode there drop down the list and select No Data Transfer,Delta Status in Source: Fetched.
Assign points if helpful.

Similar Messages

Does "Init without data transfer" creates delta queues?

Does "Init without data transfer" creates delta queues?

Hi,
Yes, Once initialization successful for particular source system, you can see entry at Delta Queue(RSA7).
Hope it Helps
Srini

Init without data transfer is not working in the Production box for FICA extractors

Hi Guys,
We are unable to do Init without data transfer for FICA Extractors(0FC_INVDOC_XX) from BODS system. And the job is successfully completed from the BODS end but it is not hitting the source system.. Can any one please let me know how to resolve this issue.
Thanks,
Kovur

Hi,
After triggering your info pack with init without data transfer, are you able to see delta pointer at info pack-->scheduler--> init options source system.
Are getting any error message? if yes then please share here.
Thanks

Initialize Delta Process without data transfer

Dear Gurus,
I am facing a problem when I try to "initialize Delta Process without data transfer" an ODS.
I first deleted the initialization request in Scheduler->Initialization Options for Source system and then I executed the Infopackage.
The status of the new init. request is red and I get the following error message :
Request REQU_DMJI1J66397EM5OZMC1EQJLWZ (192.384) for DataSource 8ZSALETXT from source system PW1CLNT600 has the status green and a lesser SID (and is therefore older) than the request that you currently want to update into the DataStore object.
This is not possible because the sequence of requests has to be followed.
Delta- and init requests have to be updated to the DataStore object in the request sequence.
The problem is that I can't find this request (REQU_DMJ...) anywhere.
Could you please explain me what to do with this issue and tell me if it is possible to make the system just ignore this request ?
Thank you in advance
Fabien

Hi............
U r not able to find REQU_DMJI1J66397EM5OZMC1EQJLWZ in the Manage screen of the ODS right?.........
Go to RSRQ...................give this request number and check...........if the Status is green........in the Header tab check whether the load is till PSA or not............if it is till PSA............then go to the Status tab and click on Process Manually to push the request in the target........otherwise just make the QM status red here..............then do the load.......
Regards,
Debjani.........

Init without data transfer

Hi sdn
my data is going form ods to cube and i already done full update from Source system now we want to do init without data transfer but when I'm seeing in monitor then requst is running for 5 hrs still yellow and when i cancell that request then run it again the when I press start load button then it ask me for ods activation for all request and for one request i had tried either way but didn't got successful, what to do we are using generic datasource
rubane

Hi,
I think you are doing data upload to ODS .
In the seetings of ODS Select Automatic Activation.
Since you have cancelled the data upload,So delete the Data from the ODS . And then Do Delta init with out data transfer .and then do full upload. But when you are doing full upload you have to make it as Repair request. And then continue Delta loads.
Once Delta init (with out data transfer) and Full upload is over to ODS ,you can start Delta init upload to Cube.
With rgds,
Anil Kumar Sharma .P

For Init without data transfer showing records 0 from 0

Hi all,
Iam doing Init without data transfer to ODS. In the ODS manage it is showing 1 from 1 which is correct. This ODS data is automatically updated to a cube. There in the cube manage it is showing 0 from 0. My mappings in update rules also correct , but why it is not giving 1 from 1.
In the cube manage the status is showing green but in the monitor of cube always it is yellow.
Help me please
Ram

Hi Ram
If you load data with INIT without data transfer then system shows the defualt record in the monitor.
If check that record in the PSA then you dont find it and on the cube as well.
If the load is green with 1 record then extractor working fine.It's not actaully a data reocrd.
Hope it helps...
Regards,
Chama.

How do I "Init without data transfer' using 7.0 transformations and DTP's?

I have a data-mart situation where I have a standard DSO object that sends deltas up to a standard cube. This data flow is created with 7.0 transformation and a delta type DTP and has been running fine.
I now have a new single activated request loaded to the DSO object but I DO NOT want this request to delta update to the cube. In 3.x, I used to go into the init infopackage, manually delete the initialization pointer, and run a 'Initialize Without Data Transfer' to make this work. Deltas could then continue as before.
I do not see a way to do this using 7.0 transformations and DTP's. I want to reset the init from DSO to cube so this request does not get updated. Does anyone have step by step ideas on how this can be accomplished?
Thanks in advance for any help on this issue.

Hi,
delete the data in the cube by using oprtion selective deletion based on request number.
(if delta request is deleted from cube, with next load last delta records will also come)
in this scenario there is no need to delete initiaizations option.
in BI 7.0, initialization load is not there.
see below documentation on DTP in SAP help.
"On the Extraction tab page, specify the parameters:
a. Choose Extraction Mode.
You can choose Delta or Full mode.
In contrast to a delta transfer with an InfoPackage, an explicit initialization of the delta process is not necessary for the delta transfer with a DTP. When the data transfer process is executed in delta mode for the first time, all existing requests are retrieved from the source and the delta status is initialized. "
Link: [http://help.sap.com/saphelp_nw70/helpdata/EN/42/f98e07cc483255e10000000a1553f7/frameset.htm]
Regards
Daya Sagar

Data Source 2LIS_11_VAHDR deliver rows with mode "Delta init. without data"

Hi.
I have the problem, that my datasource 2LIS_11_VAHDR does deliver the full content like mode C even with mode S. Does somebody know about the problem and how to solve it (perhaps OSS).
Thanks in advance,
Nils

To see the delta data, we use trandaction code RSA7. is that right? This is the place i used to view the delta data after every document changes.
per say: If I have 2 line items in a sales order and I have increased the quantity of one line item and saved it. The delta maintenance transaction shows me 3 records. 2 for changed line item and 1 for unchanged line item.
Please tell me why I have 3 records of data in delta table. Please clarify.

Source for Init with data transfer and full load

Hi Experts,
1. Please tell me where the data comes when we do the
    following actions :-
    a) Init with data transfer
    b) Full load
i want to know the source of data i.e (setup table or main table or any other table)
Helpful if you can provide the data-flow.
kindly tell which is prefrable and why?
Regards,
RG

Hi.......
When you do init with data transfer it will read data from the set up table only..........but beside this it will also set the init flag..........due to this from next time any new records will go to the delta queue...........and next time when you run delta load it will pick records from delta queue...........
Now suppose data are alrady available in the BW side...........then you can run init without data transfer.......this will only set the init flag.........it will not pick any records.........
Extraction structure gets data from set up table in case of full upload ............and in case of delta load from delta queue.......
Regards,
Debjani...........
Edited by: Debjani Mukherjee on Sep 20, 2008 11:45 AM

Diff between init with data transfer and repair full request

hi,
i have observed that even in the new flow we are doing init without data transfer and then repair full request
if i do init with data transfer also i can achieve the same?
i want to know why we need to do this ,do we have any advantage of doing init without transfer and repair full request?
please suggest me

Hi Venkat,
A repair full request is loaded in cases where you get erroneous records or where there are missing records which you want to load. In such cases, a repair full request for the selective records can be loaded and is the most efficient way to correct the data, since you won't be required to load the entire data once again. Also you acheive the desired result without disturbing the delta. (You are not required to do an init w/o data transfer after a repair full, people just do it a a precaution)
However, repair full requests should only be loaded to infoproviders with update mode 'overwrite'. Otherwise, if the InfoProvider, its very probable that you might double the value of the key-figures due to rows being added twice - in case of an InfoProvider with update mode 'Additive'. So, if your InfoProvider is additive, you will need to delete the entire data and do an 'init with data transfer' to avoid corrupting the data. (Note: you can do a repair full request for an additive infoprovider in case of lost records or if you can delete erroneous records with selective deletion.But you have to be careful with the selections lest you inadvertently load other records than required and corrupt the data)

Initialize delta without data transfer not possible

Hullo,
I want to switch the upload procedure for an ODS from full to delta. For I have researched SAP Note 689964 and executed the program RSSM_SET_REPAIR_FULL_FLAG for the ODS-object and datasource. It successfully modified the request and set the 'REPAIR_FULL' flag.
Now I want to change the InfoPackage from Full update to Delta. According to the note I have to perform an init simulation, my problem is that the option initialize delta without data transfer is in display mode only (i.e. it's gray and I cannot select it).
The InfoSource in question is "0HR_PY_1". I've checked several others and with some it is possible to select the initialization simulations and with others it's not.
My questions are a) Why is it this option grayed out? and b) What can I do to enable the selection of this option?
Any help is appreciated.

Hullo AK,
thanks for pointing out that note, sadly it's for "0HR_PY_PP_1" and not "0HR_PY_1".
However it lead us to note '611199'...
Symptom
Some attributes of the following DataSources are not defined.
0HR_PY_1 DataSource:
- Commit after initialization phase
- DeltaInit Simulation
0HR_PY_PP_1 DataSource:
- Commit after initialization phase
0HR_PY_PP_2 DataSource:
- Commit after initialization phase
Other terms
PXDW, extractor, posting transfer, settlement, PCPO, PCP0
Reason and Prerequisites
The SAP settings for the DataSources are incomplete.
The following attributes should be set:
0HR_PY_1 DataSource:
- Commit after initialization phase: no commit
- DeltaInit Simulation: Mode is not supported
0HR_PY_PP_1 DataSource:
- Commit after initialization phase: no commit
0HR_PY_PP_2 DataSource:
- Commit after initialization phase: no commit
Solution
Import the corresponding Support Package into the Plug-In Releases 2003.1 and 2002.2 and copy/activate the DataSources in the plug-in system again.
If the correction is imported, you can no longer select the "DeltaInit simulation" option for the delta initialization of the 0HR_PY_1 DataSource/InfoSource.
As long as you have not imported the correction or you are using an even older plug-in release, you should never select the "DeltaInit simulation" option during the delta initialization for the 0HR_PY_1 DataSource/InfoSource. The 0HR_PY_1 DataSource does not support this mode.
The 0HR_PY_1 DataSource only supports the delta initialization (without the DeltaInit simulation) and subsequent delta calls.
Sadly enough, not what I wanted to read, but well at least I now know that I shouldn't look into this solution anymore.
Again, thanks for your help.

How to enable delta without data transfer option for Collections - Extracts

Hi All,
My question is basically related to FSCM - Collections related data sources and Init and Delta loads of the same.
Once the Init is completed, I wanted to do delta without data transfer and option is graded out - means can not really select the option for Collections Data Sources ..
For Example I have OCLM_INVOICE as my data source which has lot of data to extract - and in the Init stage itself, its either giving errors or keeps running for longer time (Records to be extracted is ONLY 400000) and finally shows in the monitor as 400000 of 0 Records..
And also Is there any place where I can find that all of Collection data sources are TIME STAMP based or other options.
I appreciate your quick an ddetails reply and points will be awarded for sure.
Thanks
AK.

As far as I remember there some datasources which wont support init w/o data transfer. I guess COPA is one of them. I havent worked on datasource 0CLM_INVOICE but it is possible that even this could be same case. When I seached on help.sap.com for this datasource, I found this info -
(I am pasting content because strangely the webpage doesnt give html link for this search result window)
DataSource Transactional Data: 0CLM_INVOICE
This DataSource is used to extract the transaction data of an invoice from Accounts Receivable Accounting (FI-AR). The system determines the key figures from the amounts of the line items belonging to the invoice. The date fields each contain the respective date of an action that refers to a line item. The extractor provides the data in optimized form for SAP Collections Management.
Technical Data
Application Components Collections Management (0FSCM-CLM)
Available as of Release mySAP ERP Value Pack 2005.1
Shipment SAP NetWeaver 2004s BI Content Add-On 3 SP02
Content Versions There are no content versions.
RemoteCube-Capable No
Delta-Capable Yes
Extraction from Archives No
Verifiable Yes
Data Modeling
Delta Update
The DataSource permits delta update with generic delta processing using the time stamp. The system determines the invoice reference for a document in Business Transaction Event (BTE) 5010 and saves it with a time stamp. In the case of a delta upload, it determines the amounts of the line items based on these document numbers.
Extractor Logic
Verification of Key Figures
If necessary, you can check the key figures of the individual customers as follows:
In the source system, from the SAP Easy Access screen, choose the following function: Accounting u2192 Financial Supply Chain Management u2192 Collections Management u2192 Integration with Accounts Receivable Accounting u2192 Process Receivables (Old).
Enter the required customer.
The Customer Account - Process Receivables screen appears. Here you see a list of all invoices for which there are open receivables.
Using this list, you can compare the following key figures:
Original Amount of Invoice or Credit Memo (INVOICE_AMOUNT)
Amount Paid (PAID_AMOUNT)
Open Amount (OPEN_AMOUNT)
Total of All Credit Memos for Selected Invoice (CREDITED_AMOUNT)
Amount Arranged for Payment (PAYMENT_ARRANGED)
Unsychronized Backup Recovery in BW System
If you import backup copies asynchronously, you have to initialize the delta procedure for the DataSource again.
Abhijit
Edited by: ABHIJIT TEMBHEKAR on Nov 18, 2008 5:00 PM

Need of Change log deletion for a DSO, when DTP delta Init with Active Tabl

Hi,
Thanks for your time, please help me with the following
Scenario: I have Cube1 being updated from DSO1 with DTP delta, for quite some time. As per new requirement, I would need to create new data mart such that Cube2 gets updated from DSO1.
In order to Configure the delta, I am Considering Following options, please let me know, which one is right one.
Note: DSO1 is in Overwrite Mode.
Create one DTP with update Mode "Delta" , and "Active Table". I knew Delta Changes are captured in change log, but my understanding is, when you execute the DTP for the First time, it fetches the records from Active Table. And from 2nd Run onwards the very "same DTP" without "any changes" get the records from change log, even if we choose "Active Table".
is my understanding is Right?
Do I have to consider deleting the change log, because DSO1 is in Production from quite some time which is in Overwrite mode?
Do I have to create a DTP with Delta and Active Table, run the dtp Once(Init), then choose "Change Log for subsequent runs explicitly
please help me with these. I have reviewed many sap help articles and sdn threads but none of them were helpful. all of them explains, difference b/w active table and change log table, also gives scenarios like use a full DTP and then 2nd DTP with Delta without Data transfer. I am not looking for that kind of details.
Appreciate any help, Thanks again
Edited by: curious maven on Mar 28, 2011 8:35 AM

Hi Uma,
Thanks for your response.
to your question, If I need to load all the data from DSO1 to Cube1, answer is NO. if you read my post once again,
Existing Flow is : DSO1 --> Cube1 (Means, Active Table and Change Logs of DSO1 already Filled Up)
Requirement is: DSO1 --> Cube2. (Need to Init the Delta, and Detlas going forward)
My Questions:
(1) Imagine, DSO1 has 10 requests, so we see resepctive data in Active Table as well as Change Log. As a matter of fact, Data is being updated to DSO1 in Overwrite Mode, so all the changes(10 requests equivalent) would be captured in Change Log, which in turn helpful / used when we do Delta from DSO1 to any Cube, in my case, it used to update to Cube1. As per new requirement, it needs to update to Cube2.
My assumption is, if I choose "Active table and Delta in Extraction Tab" in DTP, During First Run (Delta Init), Data would be fethed from Active table. And the 2nd Run Onwards, delta records would be fetehced from Change Log automatically, even if we don't change the selection from Active Table to Change Log.
Is My Assumption Right?,
in this process, Do I have to Delete Change Log
(2) Do I have to Explicitly change DTP setting from "Active Table to Change Log" Once Delta Init has been run with setting "Active table" inorder to get Deltas from DSO1 --> Cube2 ?
Appreciate your help
Edited by: curious maven on Mar 30, 2011 3:14 PM
Edited by: curious maven on Mar 30, 2011 3:29 PM

Initialization without data transfer

Hi bw experts,
when i am loading data to ods 0fiap_o06.actually i loadded selection wise data in same infopackage for full update .after that when i try load initialization without data transfer iam getting this error
1.Full updates already available in DSO 0FIAP_O06 ; Cannot update init./delta     RSM     98
2.Activation of M records from DataStore object 0FIAP_O06 terminated     RSM1 102
after that i tried. iloaded first initialization without data transfer then i loaded full update this time these error is coming.
1.Full 1,848 has overlapping selections with init. 0000001844 : No updates into 0FIAP_O06     RSM     94
2.Activation of M records from DataStore object 0FIAP_O06 terminated     RSM1     102
right now iam doing in quality system before going to production system ,i would like to selection wise data bcoz this is huge data.can any one suggest me how to proceed this .
regards
RK
Edited by: rama krishan on May 12, 2008 12:04 PM

Hi,
Initially Just do Initialise Delta Process.....
Do not select anything (Initialise w/o data transfer (or) Early delta initialisation)..
After loading Do Delta Update
We are successfully working on this...
I think first do the following things..
1. Delete data from the Cube.
2. Load INIT
3. After completing INIT -- Do Delta
Now you will not have any problems..
Hope it works...

Initialize Delta Process with Data Transfer - Split the job in two/three

Hello,
I am trying to load master data into BI (DEV) and there are 700,000 master data records in my source system. When I tried to load Initialize Delta Process with data transfer, at some point (after 300,000 records) my load failed in source system and job log I found that this issue "ABAP/4 processor: TSV_TNEW_OCCURS_NO_ROLL_MEMORY"
When I informed this issue to BASIS consultant, they suggest me to split the job in 3 (Three). My question: how can I split the job in three? I can do one Initialize Delta Process load and followed by delta load.
Regards,
Md

Hi Md.
Even at Infopackage level you can reduce the number of records per package.
Go to Infopackage Schedular Menu -> DataS. Default Data Transfer. you can reduce the Maximum size of a data packet in kByte.
Regards,
Pratap Sone

DTPs - Delta Init without Data transfer.

Similar Messages

Maybe you are looking for