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...

Similar Messages

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 ".

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

Difference between initialization with data transfer?

Dear Ones,
What is the Difference between initialization with data transfer,initialization without data transfer and early delta initialization?
Please explain me in senario basis..
Thanks
Shiva

Hello Shivananda,
See oss note 505700 :
The early delta initialization is used to admit document postings
in the OLTP system as early as possible during the initialization
procedure.
Regards,
Fred

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.

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.........

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

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.

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

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

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.

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

Flat File loading Initialize with out Data transfer is disabled in BI 7.0

Hi experts,
When loading through flat file in BI 7.0 for Info Package Level Initialization Delta Process with data Transfer is coming by default,but when i want to select Initialization Delta Process without Data transfer is disabled. (in the creation of Data Source (flat file) in the Extraction Tab Delta Process is changed to FIL1 Delta Data (Delta Images).
please provide me Solution.
regards
Subba reddy.

Hi Shubha,
For flat file load please go throught he following link:
http://help.sap.com/saphelp_nw70/helpdata/EN/43/03450525ee517be10000000a1553f6/frameset.htm
This will help.
Regards,
Mahesh

Init with out data transfer option is not enabled

Hi Friends,
I am loading data from the data soruce 0CO_OM_OPA_7 - (Internal order items) into BI. This datasoruce is delta enabled. Flow is designed in 3.5. I checked the extractor RSA3, it shows 9 records and then i tried to load using init with data transfer, the load is not successful, it is in yellow for long time and gives the messages no record found. I tried with full load then load is successful. why init load is not successful? Is there any setting i am missing here?
Then I tried to go other option, run init without data transfer and then a full load, but I could not change the radio button to without data transfer option, it is defaultly taken init with data transfer and greyed out. How can i check init without transfer option?
thanks in advance.
Regards
Sreekanth

Hi,
In the present case you need to delete the earlier initialization flag from infopackage. Once done then you can be able to view the init without data transfer option.
So delete the flag in the menu bar --> Initialization option for source system
in the popup select the init entry and use the trash icon to delete the same.
Before doing that you can mark your earlier init load to Red and then perofrm this activity.
Once done then you can execute init-without transfer wiht no issue.
Once after this you can perform repair full load to load the data to your target.
Hope this helps.
Murali

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

Initialization without data transfer

Similar Messages

Maybe you are looking for