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

Similar Messages

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)

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.

Record count is different for Full load and Init with data transfer

Hi all,
We have a data source for which delta is enabled on Calendar Day.
If I run the full load record count is 2670.But If I run the delta record count is 2665.5 records are missing.
Would you please help on this.Why those records are missing.

Hi,
Actually for Full Load say you have 50 records. When you run it will upload 50 records.
Now if you run delta if there is no records changes it wouldnt update because there is no update in the existing records.
only delta is done when there is changes in the records.

Init with out data transfer and DELTAS

Dear Gurus,
I created Generic data source using Function module on FAGLFLEXT table. Here i used TimeStamp for capturing DELTAS. In the first run while loading into PSA i selected INIT WITH DATA TRANSFER then it got failed. Again i deleted INIT Request in Schedular and RUN INIT WITH OUT DATA TRANSFER then it got Sucess. Again i run Delta then it also it got failed. Again i deleted the INIT Request and out FULL LOAD. IT got success. May i know why MY Deltas are getting Failed.even in R/3 side when i checked in RSA7 then in status column and in Current Status Tab it showing time stamp field like this . . : :.
I got Stuck up I dont know what to do............
Can one kindly give solution for this.
Thanks,
Sony

Debug your generic DataSource, using RSA3, to determine why the delta failures are occurring. It's most likely in the delta logic portion of your custom Function Module.

Error while executing Initialize with Data Transfer for 0FI_GL_10

Hello All,
Post Pre prod refresh, our timestamp for the datasource 0FI_GL_10 got reset. Due to which our deltas did not bring any records to the BW system.
First we did an Initialize without data transfer for all the BW related datasources. The deltas were then set properly for all datasources except 0FI_GL_10.
We then raised a message to SAP and they suggested to run the 'Initialize with data transfer' for 0FI_GL_10 so that the timestamp is set and accordingly the deltas are fixed.
The issue now is we are getting the following error message while running INIT with data transfer.
Job terminated in source system --> Request set to red
Message no. RSM078
We have copied the data till July 1st week of 2011.
Please advice. The issue is very critical.
Thanks & Regards
Sneha

Hi Arvind
Thanks for your inputs.
Please find below the details of the short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          09/07/2011 11:25:32
Short text
     SQL error in the database when accessing a table.
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "ORA-01652: unable to extend temp segment by 128
      in tablespace PSAPTEMP"
     Internal call code.........: "[RSQL/FTCH/FAGLFLEXT ]"
     Please check the entries in the system log (Transaction SM21).
     If the error occures in a non-modified SAP program, you may be able to
     find an interim solution in an SAP Note.
     If you have access to SAP Notes, carry out a search with the following
     keywords:
     "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
Information on where terminated
    Termination occurred in the ABAP program "GP_GLX_FAGLFLEXT" - in
     "FETCH_TO_ISTRUCTURE".
    The main program was "SBIE0001 ".
    In the source code you have the termination point in line 903
    of the (Include) program "GP_GLX_FAGLFLEXT".
    The program "GP_GLX_FAGLFLEXT" was started as a background job.
    Job Name....... "BIREQU_4N3PZQ12IA0X0PYGEA85IG39S"
    Job Initiator.. "BIWREMOTE"
    Job Number..... 11203300
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "FETCH_TO_ISTRUCTURE" "(FORM)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "GP_GLX_FAGLFLEXT "; its source code begins in line
    840 of the (Include program "GP_GLX_FAGLFLEXT ".

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

Init load, delta load and full load

Hi BW,
Please when can I use init delta, delta and full load in a data load process.
Which of them is suppose to be in a process chain and which one is manual.
Regards.

Hi,
When you want to run delta, you have to initialize it first, thats when you run the init delta.Here you have 2 options with data transfer and without data transfer. If the data target is empty and there's no data, you can run the init with data transfer. This'll act as a full pull and also set up the initialization. If there's data already present, then you are better off running the init w/o data transfer. This dosen't pull over any data, but just sets up the initialization.
Then you can start using the delta pulls.That'll just bring over the changes and any new records rather than the whole data and is much more efficient.
You can use full pulls for say generic datasources that are not delta enabled or during a first time data load, or if there is a specific business requirement that needs you to pull over the full data everyday. Or in cases where the std datasource is not delta enabled.
Cheers,
Kedar

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

Error loading init with data request in BW for 0mat_plnt

Hi experts,
I had a failed init request for 0mat_plant , I have deleted and run an inti request with a certain plant 0000-0001,
the Init requests is showing me a warning "Was not able to determine company code or cost center for plant 0001".
I have marked the request red and ran an init without data transfer (completed successfully ) , subsequently ran a full repiar request (is showing the same issue).
I have checked in rsa3 (R/3) The datasource is picking up the correct data , and the transfer structure doesnt have the filed Company code , neither the Cost center.
Please post you comments , that would be helpful.

yes the update tab is flaged as " always update data, even if not master data exist for the data.
I have not been able to resolve the issue yet ,
Has anyone faced this kind of issue, request to post your comments..
Edited by: Abbriti on Mar 25, 2010 2:36 PM

Azure Site Recovery to Azure - cost for data transfer and storage

Hello,
I send you this message on behalf of a small firm in Greece interested to implement Azure Site Recovery to Azure.
We have one VM (Windows 2008 R2 Small Business Server) with 2 VHDs (100GB VHD for OS and 550GB VHD for Data) on a Windows 2012 server Std Edition.
I would like to ask you a few questions about the cost of the data transfer and the storage
First: About the initial replication of the VHDs to Azure. It will be 650GBs. Is it free as inbound traffic? If not the Azure Pricing calculator shows about 57€. But there is also the import/export option which costs about the same:
https://azure.microsoft.com/en-us/pricing/details/storage-import-export/
What would be the best solution for our case? Please advice.
Second: What kind of storage is required for the VHDs fo the VM (650GBs). My guess is Blob storage. For this storage locally redundant, the cost will be about 12-13€/month. Please verify.
Third: Is the bandwidth for the replication of our VM to Azure free?
That's all for now.
Thank you in advance.
Kind regards
Harry Arsenidis

Hi Harry,
1st question response: ASR doesn't support Storage Import/Export for seeding the initial replication storage. ASR pricing can be found
here which details about 100GB of Azure replication & storage per VM is included with the purchase of the ASR to Azure subscription SKU through the Microsoft Enterprise Agreement.
Data transfer pricing
here indicates that inbound data transfers are free.
As of now only option will be online replication. What is the current current network link type & bandwidth to Azure? Can you vote for the feature & update requirements here?
2nd question response: A storage account with geo-redundancy is required. But as mentioned earlier with Microsoft Enterprise Agreement you will get 100GB of Azure replication & storage per VM included with ASR.
3rd question response: Covered as part earlier queries.
Regards, Anoob

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

Hi,
Regarding the issue here, please take a look at the below links to see if they could help:
Slow data transfer speed in Windows 7 or in Windows Server 2008 R2
And a blog here:
Windows Server 2012 slow network/SMB/CIFS problem
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Why Apple doesn't provide .jpg-files for photos with date and our like Blackberry and Samsung?

why Apple doesn't provide .jpg-files for photos with date and our like Blackberry and Samsung?
I have to save photos (for medical use) on my pc and this suffix would be useful to identify them quicker.
Thanks

http://www.learn.usa.canon.com/resources/blogs/2014/20140708_winston_filenames_b log.shtml

Full Load" and "Full load with Repair full request"

Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.

Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM

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.

Source for Init with data transfer and full load

Similar Messages

Maybe you are looking for