delta 0CO_OM_OPA_6

[Former Member]

Hi,dear experts

We have done the follow step:

1. Activate the indexes 1 and 4 delivered by SAP on the database for

the table COEP

2. create or modify entries in BWOM_SETTINGS table like below

OLTPSOURCE PARAM_NAME PARAM_VALUE

-

---

-

---

-

---

OBJSELSIZE X

0CO_OM_OPA_6 OBJSELSIZE X

3. Init. extraction of 0CO_OM_OPA_6(without data)

After those steps , the delta of transaction data(0CO_OM_OPA_6) should

be enabled. We created some Internal orders cost allocation. We check the

delta queue in RSA7. we can see those data sources which has done the init

extraction. But, there is no data entry in the delta queue. And, when I

try to extract the delta data from BW side ,it took a very long time(5 hours) and got 93 records data. when I delta again,it took 3 hours to get 0 records data.Please help us to solve this or give some suggestion.Thanks!

our enviroment is BI7.0,ECC6.0

SAP_BW 700 7 SAPKW70007 SAP NetWeaver BI 7.0

PI_BASIS 2005_1_700 7 SAPKIPYJ77 PI_BASIS 2005_1_700

Best Regards

Jero

[Former Member]

hi,

wait for the next delta to happen via process chain if it still brings zero records in BW check in DELTA queue of r/3 if records are there else due reinilisation with required selection patrameters and then delta.

see this blog how to add filds for Lo data sourses it helps you.rhttps:///people/pradip.patil/blog/2006/06/07/how-to-retain-deltas-when-you-change-lo-extractor-in-production-system

[Former Member]

David,

Did you happen to know what is causing so long extraction times for this particular DS - 0CO_OM_OPA_6? if so, how did you overcome the issue?

Even we have some very similar problem, just for 2 records it is taking more than 5hrs which is ridiculous, and this happens only with this datasource. And other parallel processes in the chain run pretty fast.

Any help would be appreciated.

[Former Member]

Index 4 is or paramount importance in rasing the bar for extraction of CO line items and the next step of BWOM_SETTINGS table,OLTPSOURCE = ' '

PARAM_NAME = 'OBJSELSIZE' should help a lot.

<b>However;The CO delta extraction only selects (by default) line items that have been posted in a 120 minute safety interval before the extraction run is started (this is to ensure that the update is not still running for the extracted time interval).</b>

By adding a new entry to the BWOM2_SAFETY table (BWOM2_V_SAFETY view) for the DataSource, the safety time interval can be defined on another minutes value for test purposes, but SAP would strongly advise against implementing a change for the production operation (for more information, see note <b>553561</b>).

The line item selection is performed in the BWOMR_OM_READ_COVP_DATA function module (via the COVP view).

Hope it Helps

Chetan

@CP..

[Former Member]

Hi David,

To improve performance and minimize the transfer time from the source system into the BW:

1)Decide which fields in the extract structure you require for your reports.

2)Add only those fields to the transfer structure.

3) If the standard transfer structures and InfoSources do not meet your requirements, copy them and then modify them as needed. All delta-update-compatible DataSources are intended as a basis for defining your own InfoSources.

4) If you only want to display aggregated data, do not add the fields document number, posting row, or document row text to your transfer structure.

The delta records that u have changed might not get updated in OLTP(r3) system,because r3 requires a certain amount of time to update line items. Since the time stamp is set when the update begins rather than when it is completed, there may be a lag between the time stamp and the actual time of the update event. Because of this lag, some line items may not yet be updated to the database even though their time stamp is within your selection conditions. Consequently, they cannot be selected when you create a delta dataset and are not loaded into the BW , for SAP R/3 requires a certain amount of time to update line items. Since the time stamp is set when the update begins rather than when it is completed, there may be a lag between the time stamp and the actual time of the update event. Because of this lag, some line items may not yet be updated to the database even though their time stamp is within your selection conditions. Consequently, they cannot be selected when you create a delta dataset and are not loaded into the BW,by specifying a safety time (the time during which line items can be safely updated), the standard safety interval is 2 hrs.

You can define the safety time using the BWOM2_V_SAFETY view in the OLTP You can use different safety times in minutes for each DataSource.

A safety time that does not refer to a DataSource applies to all DataSources for which you have not made a special entry.

Regards

KK