0FIGL_O02 Init/Delta loading, Why more data ??

Hi,
We usually load the 0FIGL_O02 using the 0FI_GL_4 extractor in Full mode.
Because of the very long loading time, we decided to use it in Delta mode instead, so we deleted all the data inside the DSO and we lunched the Init loading.
The situation is :
In full mode we load approx. 6 Million lines,
Everyday full loading inserts approx 200.000 more lines,
So when we converted to Init in day D, we were expecting to load approx. 6M and 200.000 lines of data, But we have now 9 Million, and still loading (not finished yet).
Why don't we have the same number of loaded lines ?
We are sure that we don't have 3Million new lines between D and D1, and we were loading in full with constant value of 6M (20000) everytime.
Is the Init load accessing other tables than the Full ? and are we having the good informations ?
Please help !!
Regards
Raed

Hi,
I am curious to know the finding for this.
We are also planning to reduce teh load time for 0FIGL_O02.
Thanks
Mukesh

Similar Messages

"Error occurred in the data selection" on init delta load ODS- InfoCube

Hi, gurus and experts!
I'm trying to do Init delta load from 0FIAR_O03 ODS into 0FIAR_C03 InfoCube in PRD env. by InfoPackage "Initialize with delta transfer (with data transfer)". Immediately after the load was started I got error
"Error occurred in the data selection"
with details
"Job terminated in source system --> Request set to red".
Where are no any short dumps. There are 1 activated init load in ODS - nearly 6 500 000 records.
Any ideas about error? And the way I can load data?

Hi Gediminas Berzanskis,
I faced the similar error when I tried to load data from an ODS which contained huge amount of data to a Cube. Even in your case the volume of data is more (around 6.5 million records). The error could be due to the table space issue, please contact your Basis team to check if enough table space exist for both the data targets.
Meanwhile you may also check the RFC connection of the Myself source system.
You can replicate the DSO datasource once and then reactivate the transfer rules using the program RS_TRANSTRU_ACTIVATE_ALL.
Try load with a small amount of data with a Full load option and then with a delta option..
Hope this Helps,
Prajeevan (XLNC)

Delta loading take more time

Hi
the daily delta load from 2lis_03_bf to cube 0ic_c03
daily its take max 2 hars but to day its still running for 5 hrs not yet finished with 0 from 0 records
why,
how can i get the reason
In rsa7 its showing 302 records
Regards
Ogeti
Edited by: Ogeti on May 8, 2008 7:47 AM

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
Also see if there is any 'sysfail' for any datapacket in SM37.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
5) SM58 and BD87 for pending tRFCs and IDOCS.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the data tables.
SM21 - System log can also be helpful.
Also RSA7 will show LUWS which means more than one record.
Thanks,
JituK

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Delta loading of generic data source.

Hi,
please tell me the procedure for How to load Delta data For generic data source?

Hi
You can use the following procedue
Enabling Delta Load
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
     1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
           a.      Set Applic. Component to BW.
            b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
            a.      Choose Local Object to see the DataSource information.
             b.      Choose Save to return to the Change DataSource maintenance screen.
4.      Choose Generic Delta. In the Generic Delta dialog box:
            a.      Browse Field Nm. to select the delta-relevant field.
           b.      Mark the Time stamp radio button.
            c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
       1.      Launch the SAP BW Administrator Workbench and go to Modeling.
      2.      Open the list of InfoSources and select the DataSource assignment you want.
      3.      With the secondary mouse button, choose Replicate DataSources.
      4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
      5.      In the InfoSource Change screen, choose with the quick info text Activate.
Initializing Delta Load
Prerequisites
You have configured the DataSource for the delta loading process. For more information, see Enabling Delta Load.
Procedure
1. Starting Delta Initialization
     1.      Launch the SAP BW Administrator Workbench and go to Modeling.
     2.      From the Modeling pane, click InfoSource to populate the InfoSource pane and select the InfoPackage you created for the InfoSource in, for example, Example of Data Extraction.
      3.      From the Update tab page, activate the Initialize Delta Process indicator.
      4.      To define parameters to be used for the delta load process, go to the Data Selection tab page and define relevant parameters.
      5.      In the Schedule tab page, choose Start to begin delta initialization.
If you defined parameters to be used in delta load (step 4 above), use PSA in the modeling component of Administrator Workbench to view the request results.
     6.      To check when delta initialization is finished, go to the Maintain InfoPackage screen of the Monitor u2013 Administrator Workbench and press F6.
2. Monitoring Delta Initialization
     1.      Launch the BW Delta Queue Maintenance and select the DataSource in question.
     2.      Use the secondary mouse button to see the current pointer value in Generic Delta Current Status.
     3.      You can delete the delta initialization (if you want, and subsequently create a new delta initialization) in Scheduler (Maintain InfoPackage) by choosing the delta request from Initialization Options For Source System and choosing Remove.
In this screen, you can also check the status of the delta initialization request.
To see the content and results of the delta initialization request, go to PSA in the modeling component of Administrator Workbench to view the request results.
3. Running Delta Load
You can run the delta load process only after delta initialization has been completed.
     1.      Open the InfoPackage and in the Update tab page activate the Delta Update indicator.
      2.      Go to the Schedule tab page and choose Start.
*Enabling Delta Load *
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
      1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
        a.      Set Applic. Component to BW.
        b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
           a.      Choose Local Object to see the DataSource information.
            b.      Choose Save to return to the Change DataSource maintenance screen.
   4.      Choose Generic Delta. In the Generic Delta dialog box:
       a.      Browse Field Nm. to select the delta-relevant field.
       b.      Mark the Time stamp radio button.
       c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
   6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
   1.      Launch the SAP BW Administrator Workbench and go to Modeling.
   2.      Open the list of InfoSources and select the DataSource assignment you want.
3.      With the secondary mouse button, choose Replicate DataSources.
    4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
5.      In the InfoSource Change screen, choose with the quick info text Activate.
Hope this helps
Regards
Shilpa

Question for delta loading, why can not update existing record in cube

Hi, Gurus,
I load data from a flat file into one infocube with delta loading option, and in the related datasource, i chose 'additive delta' option.
However after delta initial and delta update, when I checked cube content, I found that there are 2 records with the same characteristic value (just like duplicated key), and my expectation is to sum key figure with the same characteristic. Who can help me on that?
BTW: when I check delta queue, why there is not any queue?

Hi,
In uploading of flat file , If you are able to capture the changes to the previously loaded records, Then you can follow the additve delta. So it decreases the time of uploading .Only changed or new records will be uploaded every time.
If you are not able capture the changes in flat file ,Every time you have to do full upload ,Before this delete the contents of Infocube. (Assuming there is no ODS B/W Infocube and Flat file).
With rgds,
Anil Kumar Sharma. P

Delta load for a data source not enabled

Dear Experts,
We have got the requirement to create reports on shipment details.
Based on the requirement we have identified the
Infosouce/ Data source : 0OI_TD_OIGSII
Info Cube: 0OI_TDC01. we think this cube will satisfy the requiremnt.
But the problem is the data source is not delta enabled. so how do we extract the data and how to capture the delta.
when we checked in Roosource table the delta field is blank (Delta only with Full Upload (ODS or InfoPackage Selection))
These data sources are IS OIL specific, so dont know the data extraction procedure.
Please through some light and help me.
Please advise.
Regards
venu

Delete duplicate request is a process chain variant, which will allow you to set the duplicate request deletion options. You need to explore those options.
Now say you have a routine in the DTPs.
DTP1 = Current Month
DTP2 = Prevoius Month
In the month of July,
DTP1 = 07/2009
DTP2 = 06/2009
On daily basis DTP1 will load data for July and DTP2 will load data for June. Now delete duplicate request will delete the previous requests loaded by each of them for the same month. Meaning delete duplicate request for DTP1, will delete the request loaded for 07/2009 and DTP2 will delete the duplicate request for 06/2009.
Now when you will be in Aug, the routine will change the selection criteria
DTP1 = 08/2009
DTP2 = 07/2009, so now DTP2 will delete teh duplicate request for 07/2009 and load the new data. Now the data changed for 06/2009 is not possible to load as you have only 2 DTPs.
For safer side, you can create 3 DTPs to take care of the last 3 months, but first test the logic for two DTPs and then go further for the third DTP.
- Danny

Full Load and delta loads of HR Data using ABAP Program

Hi All,
I need to write an ABAP program that will pull some HR data from some of the infotypes.When i run it for the first time it should pull all the data for all the employees but in the subsequent runs it should run only the delta changes
for example
inital run is on 04/30 it should pull all the data for all the employees
next run 05/02 then it should pull onlly the infotypes for which there is a change between 04/30 and 05/02
Please let me know the solution
Thanks
Bala Duvvuri

Rob,
I understand that I need to AEDTM field but the problem is
during the initial load i will not have any control date stored in the z table so i will fetch all the records using the select queries on various infotypesin the if condition but the problem is i need to repeat the same queries by adding the AEDTM condition in the else condition where control date is not initial(not an initial load) so it will be a duplicacy of all the select queries.
is it a good programming style?please let me know your thoughts on this
if p_ctrl is initial " Initial load
select queries
else " subsequent runs
same select queires with AEDTM condition
endif.
Thanks
Bala Duvvuri

Full-Init-Delta Loads

Friends
I have done full loads into a ODS and then I did Init with no data transfer. But the Message said that the request cannot be activated because the ODS has had full loads and activating INIT and DELTAS is not possible...Any Ideas?
Regards
VISHAL

Hi Ashwin,
there is a seperare procedure to activate delta mechanism in ODS. After you load the full requests you cannnot run init without making all the full requests to "Reapir full requests".
See SAP Note: 689964
Symptom
You want to switch the upload procedure for an ODS object from full to delta. However, the delta initialization fails with a message indicating that there are already full uploads in the ODS object and therefore inits or deltas cannot be posted or activated.
Other terms
Delta; ODS object: delta initialization, RSM 098, full, Init
Reason and Prerequisites
If a full upload occurs once for an ODS object, you can no longer activate an init for the same DataSource/source system combination in this ODS object. The system does not check for overlapping selection conditions.
Solution
In the case if an ODS object, you can change the upload procedure from full to delta by subsequently marking the full requests that exist in the ODS object for this DataSource/source system combination as repair full requests.
These requests are therefore characterized by the fact that they can be posted into any data targets in any sequence. The repair full requests are never checked in a data target, that is, you can activate initializations and deltas (also with selections) in the ODS object. All ODS objects filled with these full requests behave as if the full requests did not exist in the ODS object.
Checks do not take place in all of these ODS objects.
Note the following:
Since the repair full requests are not checked, duplicate data records may be created or data may disappear if there is a subsequent init.
Since the repair full requests are not checked, you should take account of the extractor behavior, update modes, aggregational behavior of key figures and characteristics, among other things, when you are deciding whether you want to mark the full requests as repair full requests.
If you perform an init simulation after changing to repair full requests, make sure that no data is updated between the last full upload and the first delta upload.
Procedure for changing full requests to repair full requests:
After you import Support Package 19 (3.0B) or Support Package 13 (3.1C), the RSSM_SET_REPAIR_FULL_FLAG report is available which you can use to convert all full requests for a DataSource/source system combination that are in an ODS object into repair full requests.
Before you import this Support Package:
Use transaction SE16 to call the RSSELDONE table.
Here, enter an "x" in the "Repair_Full" field for all full request records that you want to mark as repair full requests.CAUTION: This ONLY concerns those requests that begin with 'REQU_...'. The repair flag CANNOT be set for activation requests that begin with 'ODSR_'.
If the full requests still exist in the PSA, you can also use the scheduler under the 'Scheduler' menu option in the PSA tree (when you post from the PSA) to switch a PSA full request to a repair full request before loading.
If you load new requests with an InfoPackage, you can also assign the repair indicator to this full report.

Lost connection on heavy load, no more data to read from socket

Hi,
we are using a webapplication on a clustered tomcats 6-installation (about 10 tomcats :-)) (running on windows server 2008) - all with java 1.6 / 64bit.
Database 11g and corresponding jdbc ojdbc6.jar.
On heavy load, the application on a tomcat loses the connection:
Caused by: java.sql.SQLRecoverableException: Keine weiteren Daten aus Socket zu lesen
     at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1200)
     at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1155)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:279)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:861)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3493)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
I checked the link Re: JDBC Connection Reset when using many processes on 64 bit system Re: JDBC Connection Reset when using many processes on 64 bit system but the forum-link handles linux and not windows.
Any suggestions?
Thanx a lot!
Regards
Wolfgang

This is just the driver/connection being the innocent victim. Something (the network/firewall, but most likely the DBMS)
has simply cut the socket out from under the running JDBC connection. This can be caused by any sort of DBMS
internal problem such as some serious resource error that requires it to terminate a DBMS session abruptly. I suggest
you ask your DBA to examine the DBMS error log to see if there were any SEGFAULTS or resource emergencies at
that time that required aborting some sessions.
HTH,
Joe

Init. Delta load in BI 7.0?

Hi, Experts:
I just changed to a new BI application team. We have a delta load from ECC into an ODS then into a cube. I thought that there must be an initial delta load before the daily delta load. But I don't see init delta load request when right click the ODS/cube then select "Manage". The application started to load from January 2008. I have put the request display date to sometime 2007 then click the refresh button. But still could not see init delta load. From the very 1st load till date, I only see all are delta loads. Is this some thing new in BI7.0 that init delta is not needed any more? Or something is wrong?
Thanks,
Jenny

Hi,
that's right, there is no special request for Delta/Init.
The DTP can do it itself at the first time.
If you want to check which DTP is the Initialization, you can go on the DTP log, and in the header you will see "Extraction Mode" -> Delta.
If the corresponding DTP request is the init, the flag "Delta Init" is ticked.
Hope it helps !
Mickael

MAster Data - Delta Load Error?

Hi,
I am having error in 0COSTCENTER delta load. In the Info Package of 0COSTCENTER, it was not selected to PSA. It was selected to InfoObject directly.
Since this is a delta load for Master data, how can i correct this error?
Thanks!
Venkata

Hi Venkat,
You can done a full upload without affecting Delta upload. Make a test on Dev or Qual and you will see that a full on Master Data does not stop delta process.
Ciao.
Riccardo.

COPA Init Delta

Hello,
In loading our COPA cube from R/3 to BW, when we run two init delta infopackages in parallel, we get the following error "An init or delta request is already running for this DataSource".
We believe this has to do with the timestamp functionality. According to the documentation we have found, it appears as though we should not split our init delta load into multiple infopackages, but rather limit it to one singe infopackage that loads everything. Can anyone confirm this?
Our COPA datasource is costing based and set up as a generic delta. We are on R/3 PI 2004.1 and BW 3.5.
Thanks,
Kelley

Hi,
That is right, and it will have to do with the timestamp functionality as you said.
Following is from the HOW-TO document which is not exactly for this scenarion but implies the same reason.
"There can only ever be one valid initial package for a DataSource. If, for the same DataSource, a separate initialization is scheduled for different selections, for example, and data is posted to the operating concern between the individual initializations, data inconsistencies could occur between SAP BW and OLTP. The reason for this is that, with each initialization, the time stamp of the DataSource in the OLTP system is set to the current value. Consequently, records from a previous selection are no longer selected with the next delta upload if they were posted with a different selection prior to the last initial run."
hope this helps..
cheers,
Ajay

Init Delta for 0FIGL_O06 required?

Quick question for everyone.
I need to delete and re-load data in 0FIGL_O06 due to some missing deltas (which are no longer avail in PSA). If I look back at the requests in the ODS now (done by my predecessor) I don't see an INIT delta...just delta loads starting several months ago.
If I need to delete and reload do I first need to run an INIT DELTA load?
Thanks

Hi Barnaby,
I guess there are so many requests that you are not able to see the Init request in the display. Change the display selection criteria and see if you can see the Init request. The delta requests can not run without init request. Hope this helps.
Thanks and Regards
Subray Hegde

Doubt in Delta Loading !

Hi,
I have a Doubt in Delta Data Loading
Please check the following Procedere is Right / wrong ?
I did Full Load it is successful.
I am doing Delta Loading.
For the Business Content Info Cube 0COPA_C01 --
CO-PA: Published Key Figures I am Loading the Data.
I am doing INIT & Delta Load.
This cube has the Data source 1_CO_PA_110_BILDA
I had checked in RSA6 : 1_CO_PA_110_BILDA
ExtractStruct : ZOXGDV0108
Direct Access : D
Delta Update is check -
First I Created a info package --
In Update Tab
Update Mode
Full Update
Delta Update
Initialize Delta Process
Initialization with Data Transfer
Initialize without Data Transfer
I have choosen Initialize Delta Process -- Initialization with Data Transfer
Then For the DTP --
In DTP -- Extraction tab -- Extraction mode is set to Delta.
There is no difference in Records when I loaded Full/Delta.
showing same records.
is the Right Procedure I followed !
When Next time I load Delta then I need to follow the Same procedure ?
Thanks
prasanna

Hi Prasanna
I thought that u r in to Bw 3.x
Ny ways in this case u should create a proces chain..
and schedule it in the start process it self .
Still there is one ancient option like define the subsequent process in the in fo pak
schedule once the PSA request is sucessfull then put a Event and then place the
same event in the start process or scedule process of DTP.
But as per Expert Suggestion U should Go for Process chain.
Thanks & Regards
R M K
**Winners dont do different things,they do things differently**
> Hi R M K thank you,
>
> if we do Info Pack -- schedule Tab
>
> In the option Start Later in background-- set
> periodic values
>
> Then it will update only in PSA.
>
> But if we want to get these Records in info cube
> we need to Execute the DTP.
>
> That is not doing.
> (selecting the option start later in background and
> set the periodic values is sufficiant)
> here you are not discussed for DTP.
>
> cause i don't want to load manually.
>
> How do we Execute DTP automatically ?
>
> thanks
> prasanna

0FIGL_O02 Init/Delta loading, Why more data ??

Similar Messages

Maybe you are looking for