DeLta or not Delta?

What does mean that number "16570-10A" near CPU socket?
How I can differ old k7n2 mobo series and Delta-series(BIOS,serial№,part number)?

WCPUID TEST RESULT:
[ WCPUID Version 3.1a (c) 1996-2002 By H.Oda! ]
$$--- Chipset Information
Host Bridg : 10DE 01E0 C1 00000000 NVIDIA nForce2 ISA Bridg : 10DE 01EB C1 57001462 NVIDIA nForce2 MCP
IDE Controller : 10DE 0065 A2 57001462
VGA Device : 10DE 0201 A3 0C3C10B0 NVIDIA GeForce3 Ti 200
AGP Revision : 2.0 / Enabled
(Status) (Command)
Data Rate : 1x 2x 4x / 4x
Fast Write : Supported / Disabled
4GB Addressing : Not Supported / Disabled
Side Band Addr.: Supported / Disabled
40:[02] 41:[60] 42:[20] 43:[00] 44:[17] 45:[02] 46:[00] 47:[1F]
48:[04] 49:[01] 4A:[00] 4B:[00] 4C:[FF] 4D:[FF] 4E:[FF] 4F:[FF]
##--- Date 07/11/2003, Time 09:27:19

Similar Messages

Delta records not updating from DSO to CUBE in BI 7

Hi Experts,
Delta records not updating from DSO to CUBE
in DSO keyfigure value showing '0' but in CUBE same record showing '-I '
I cheked in Change log table in DSO its have 5 records
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - -1
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   1
ODSR_4LH8CXKUJPW2JDS0LC775N4MH -   0
but active data table have one record - 0
how to corrcct the delta load??
Regards,
Jai

Hi,
I think initially the value was 0 (ODSR_4LH8CXKUJPW2JDS0LC775N4MH - 0, new image in changelog) and this got loaded to the cube.
Then the value got changed to 1 (ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 0, before image & ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 1, after image). Now this record updates the cube with value 1. The cube has 2 records, one with 0 value and the other with 1.
The value got changed again to 0 (ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - (-1), before image &
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - 0, after image). Now these records get aggregated and update the cube with (-1).
The cube has 3 records, with 0, 1 and -1 values....the effective total is 0 which is correct.
Is this not what you see in the cube? were the earlier req deleted from the cube?

Delta package not fetching all records from Delta queue in r/3

Hello,
I have loaded Goods Movement Data using 2LIS_03_BF datasource into my BI system.
The Delta has been initialized and everyday the delta is being moved from r/3.
I observed that when I execute my delta package not all delta records are fetched into PSA from r/3.
For Ex: Before starting my delta package I checked in SMQ1 of my R/3 system and see that there are around 1000 records.On executing the delta package I see that the record count is reduced from 1000 to 400 in SMQ1.On executing the delta package again I get the remaining 400 records into my PSA.
Shouldn't the delta package get all records from the queue on single execution??
Is there some setting to define the nr of records to be loaded?
I'm confused with this behaviour.Please help me understand this behaviour.
Thank You.

Hello,
First thing: the data is not transferred from the SMQ1 queue, rather the data is transfered to BW from the RSA7 Delta queue. You need to check the number of records present in the RSA7 queue.
Since SMQ1 is involved, i think you are using the unserialized V3 update method. In this method, when data is first written to the application tables, it is first transferred to the SMQ1 update queue,then via a job to the LBWQ extractor queue and then to the RSA7 delta queue. So the number of entries that you see in the SMQ1 queue are not the number of entries that have to be transferred to BW but rather the records that are waiting to be transferred to the extractor queue in LBWQ. Similarly, in LBWQ, the number of entries displayed here are not the no of entries that are going to be transferred to BW, they are the no of entries that will be transferred to the delta queue RSA7 when the next v3 update job runs.
If you want to check the number of records that will be transferred to BW, select the datasource in rsa7 and then click on the display data entries button.
Hope this helps.
Regards.

I have copied the 0datasource to Zdatasource.but delta is not working

Hi All,
i have copied the datasource from 0ASSET_ATTR_TEXT to ZASSET_ATTR_TEXT. the init is working fine and the Delta is not working for this.
while coping the datasource i have updated the tables
Roosource, roosourcet, roosfeild. Is that enough,
kindly help me on this
regards
KA
Message was edited by: A K
Message was edited by: A K

Hi vishnesh,
It is not a generic datasource, i have copied the datasource thru a Zprogram.
and when i run the RSA3 for the F update mode for the Both datasources(Z and 0) they are perfect. but when i run for D mode it is getting the errors for both the daasources.
Regards
KA
Message was edited by: A K

How to check that Delta is not captured?

Dear Experts,
I am using 2LIS_02_ITM datasource.
PO is created using a program.
The next step in the program, it can change a field in the PO depending on logic, using a abap command 'update'.
Sometimes, this change is not captured in the delta queue, it seems.
why i say this is the PO shows the field value but BI delta load does not.
It is using Queued Delta now.
Initially, the program uses a command 'update' to update the field in PO.
Now, we decided to use ME22N program to ensure delta will be created.
The problem is happening to some records and not all delta records.
Its very difficult to tell what is the cause.
What is the standard method to check that Application table data is not captured in Delta Queue by the extractor?
Or
If PO can show the field value, is there a possibility that Delta may not capture this field change?
regards
Pascal

Well just throwing few possibilities:
1 - Basically PO creation, change in values/quantities etc are Business transactions and they generate evens known as BTEs.
Now we have to explicitly inform SAP ECC that which applications can use BTEs and we do this by tcode BF11.
Check if the software component creating and changing POs is properly linked to BTEs and if BW is set as active in BF11 tcode.
2 - If point 1 is checked and nothing is found to be incorrect, please check if Industry sector is correctly chosen (SBIW). Industry sector generates a set of Transaction keys (BWVORG) without which the values are not updated in BW.
Also rightly pointed by Tbollo, you need to ensure that there's a pattern in the missing docs to identify the rootcause.
Debanshu

Deltas are not updating to next ODS?

Hi,
The deltas are loading from R/3 to Two ODS(O1 and O2) from Two Different data sources(Delta).Again these deltas from O1 and O2 are loaded to ODS O3.The problem is the O2 deltas are upadating to O3 ODS correctly.But the O1 deltas are not being loaded to O3 ODS.All these are loadings are happening through the process chain.Can any one help me to understand why the deltas are not being loaded to O3 ODS from O1 ODS.
Points will be definitely assigned .
Thanks,
Vasu.

Hi,
The next delta will all the request data from Source ODS to target ODS which have not yet been pulled.
You can confirm this by checking the Datamart status (Tick sign) besides each request in the source ODS.
All those without this tick will be updated in the next delta.
All those requests that have this tick is already availble or loaded into target ODS.
So once this delta is loaded things will stabilize.
Hope this helps.
Thanks,
JituK

Data source not delta capable

Hi ,
i have an issue here my copa datasource is not delta capable, how will I make it delta capable.I dont want to use an ODS here.please this is an urgent issue
regards
rak

Hi Rakshita,
Check here.......
COPA Delta
Simple Question on Delta Info Package
dummy delta/pseudo delta
Psedo Delta
Delta load for flat file
Regards,
Vijay.

Generic Datasource eventhough delta enabled not working

Hi Experts,
I have created a Datasource by creating a Function Module and also this function module i copied and did the changes the function module i used as a template is RSAX_BIW_GET_DATA_SIMPLE
and after creating the thing i have created a generic delta by using LAST_CHANGED_ON date as delta specific field and i have initialized the delta its fine it creating an entry in RSA7
in my first init load i got 4000 records so immly i have done delta again it brought 4000 but when i checked in RSA7 for delta their are no records but still its brining 4000 records ...but as per my assumption it should not get any records becoz we already got the delta.
Thanks and regards
Sreedhar

Hi
Even after making changes to code its still bring all the records with each load.
below i am pasting my code please advise what is that i am doing wrong so that delta is not getting picked up. instead every time its a full load.
FUNCTION ZRSAX_BIW_GET_DATA_SIMPLE.
""Local Interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*"      I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      E_T_DATA TYPE ZDPR_DASHBOARD_T OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table SFLIGHT
TABLES: DPR_DASHBOARD.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
DATA : LF_OBJECT TYPE EVE_TV_OBJECT_GUID.
DATA : LF_DATE TYPE DPR_TV_LAST_CHANGE_DATE.
Select ranges
RANGES: L_R_OBJECT FOR LF_OBJECT .
RANGES: L_R_DATE FOR LF_DATE.
L_R_CONNID FOR SFLIGHT-CONNID.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZDPREXTRACTION'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
    S_S_IF-REQUNR    = I_REQUNR.
    S_S_IF-DSOURCE = I_DSOURCE.
    S_S_IF-MAXSIZE   = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
First data package -> OPEN CURSOR
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
     LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'OBJECT_GUID'.
       MOVE-CORRESPONDING L_S_SELECT TO L_R_OBJECT.
       APPEND L_R_OBJECT.
    ENDLOOP.
LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'LAST_CHANGE_DATE'.
        MOVE-CORRESPONDING l_s_select TO l_r_date.
        APPEND l_r_date.
      ENDLOOP.
     ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT (S_S_IF-T_FIELDS) FROM DPR_DASHBOARD
                               WHERE LAST_CHANGE_DATE in l_R_DATE. "AND
                                       OBJECT_GUID IN L_R_OBJECT.
ENDIF.                             "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
Regards
Sreedhar
Message was edited by:
        Sreedhar M

Why 0FI_Gl_40 is not delta supported?

Hi Team,
         Why 0FI_Gl_40 General Ledger Accounting: Line Items datasource is not delta supported? Full upload of FI-GL line item for any big industries is not a feasible solution. 0FI_GL_4/14 all prev extractors were delta enable but why SAP has made new 0FI_GL_40 delta disable? Quite strange step. Please share with me your suggestion or view.
Thanks & Regards,
Ashish

check this Note 1290358 - DataSource 0FI_GL_40: Extraction of entry view
Reason and Prerequisites
The DataSource 0FI_GL_40 also returns data from the entry view. The selection is controlled and the data separated from the general ledger view using the ledger: The initial value is allowed as a valid restriction and an initial ledger in a returned data record is to be interpreted as an entry view. To assist the selection and the replication, the general ledger (G/L) fields DOCNR, DOCLN and RYEAR in these data records are not left empty but transferred from the corresponding fields in the entry view (BELNR, BUZEI, GJAHR).
Note also that no delta method can be supported for the entry view. With this in mind, check whether the replication of the data compared to the (leaner) direct access offers enough advantages in your business scenario.
Solution
To extract data in the entry view, the InfoPackage in BI must contain the initial value for the ledger selection.
The simplest variant is where no ledger selection takes place. In this case, the initial value automatically lies within the (empty) selection, and the entry view is requested together with all G/L ledgers. However, note that this option is only available as of ERP 6.0 Enhancement Package 4, according to related note 1270834.
One possibility is to restrict the document status: If you are only interested in non-posted documents from the entry view, then it is sufficient to restrict the document status accordingly (the value 1 cannot be contained for BSTAT_S in the selection).
To request the entry view specifically in the InfoPackage, store an ABAP routine (variable type 6) in the data selection area for the characteristic RLDNR. In the predefined source code, between the lines
"$$ begin of routine - insert your code only below this line" and
"$$ end of routine - insert your code only before this line",
insert the following lines (or similar source code with the same semantics):
data: l_idx like sy-tabix.
read table l_t_range with key fieldname = 'RLDNR'.
l_idx = sy-tabix.
l_t_range-fieldname = 'RLDNR'.
l_t_range-iobjnm    = '0AC_LEDGER'.
l_t_range-sign      = 'I'.
l_t_range-option    = 'EQ'.
l_t_range-low = l_t_range-high = space.
modify l_t_range index l_idx.
p_subrc = 0.
In this case, only the initial ledger is requested with the InfoPackage. This corresponds exactly to the entry view.
Santosh
Edited by: Santhosh Nagaraj on May 12, 2010 12:37 PM

Delta Initialization vs Delta Update

We're having some issues with performance when loading our GL cube. What I would like to do is perform many delta initializations, each delta inititialization containing one month/period.
My confusion is in the fact that the last time I attempted this, when I subsequently went to run my delta UPDATE the same selection criteria was automatically inserted into my delta update.
So for example my INIT may look like this;
REQUEST1: Selection = 001.2005
REQUEST2: Selection = 002.2005
etc........etc...
REQUEST12: Selection = 012.2005
Next the UPDATE info package seems to inherit the same criteria... doesn't this mean it will not update anything beyond that criteria??
I'm just wondering if it is possible to do an incremental initialization and still be able to enable delta updates for future periods?
Thanks!

Hi Patrick,
The delta update will load the data as per the selections made in the Init run. A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
Take a look here for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Hope this helps...

How to do delta detection and delta creation

Hi
i am new to OWB , please help me in
how to do delta detection and delta creation using OWB
Thanks

Hi Bassem,
for delta detection in your data source there are three possibilities:
1. the source data has some identifier when it has been modified and deleted data is marked an not physically deleted
In this case you just filter the data that has been changed in your owb mappings.
2. you use some change data capture technologies
You have to install this manually when using owb 11.1 or older versions (google for oracle and cdc). owb 11R2 brings built in support for change data capture.
3. you get all the data and identify the delta manually
In the owb mapping you left outer join the data from your source with the existing data in your target and filter for the data that is new or has been modified. In a second step you identify the deleted data by selecting the data in your target minus the data from your source.
Which approach is the best depends on your specific system architecture.
Regards,
Carsten.

Repeat Delta bringing previous delta too

Hi BIs,
SAP system sometimes acting strangely by bringing Current days delta + previous days delta when Delta Info package was requested again.In Monitor it is displaying as Repeat delta only.
This strange behavior is occuring once in a while and not evry time
Could any one tell me why it is behaving like this,if so any possible ways to avoid this
Thanks and regards
Bala

HI ,
generally if you make the delta request red and then repeat it that only will set your init pointer ..
but i think there is some problem with the init pointer setting .. so can try one thing run once init without data transfer that will set you init flag .. and run your deltas... this might solve your problem ..
Regards,
shikha

Direct delta and Qued delta.............

Hi Gurus !
Both Direct delta and Qued delta in LO are independent of the success of the V2 Update process( Roberto Negro too mentioned this in his weblog).This means that V2 update Exists both in Direct and qued delta( Am I correct?).
As the data is written in the Delta que within V1 Update
for the case of direct delta, in Extraction que in Qued delta , where does the V2 Update come into the Picture?
Pls can anyone help in this regard.
Regards
Durai

Hi !
I am very eager to know the answer.
Regards
Durai

Differences between FULL, DELTA and REPEAT DELTAs

Please distinguish Full, Delta and Repeat Delta loading from R/3 to BW/BI and give some example for their uses
Your answer would be appreciated.
Cheers,
Nari

please search in SDN before posting Novice questions

Delta load not picking the changes to Custom Fields in 0CRM_QUOTA_ORDER_I

We have enhanced the structure of CRM datasource 0CRM_QUOTA_ORDER_I for some additional fields that are held on the quotation. These are being successfully extracted when the quotation is being created. We have been running with this exctract for some time but we have been made aware that the additional fields on the append structure are not being updated when the quotation is being changed. Therefore delta changes are not being picked up making the reports incorrect.
The user exit we are using to extract the information is EXIT_SAPLRSAP_001
Does anyone know how we can enable this change so that delta changes are picked up by the extractor.
Many thanks
Gareth
Edited by: Gareth Aspinall on Jan 14, 2010 2:04 PM

Hi Gareth,
Can you please check that the custom fields were added as described in question 4 in the SAP note
692195? If yes and there is still a problem please check that the SAP note 1319891 has been applied
in your system, it is a pilot note so you will need to raise a message with SAP to get added to the pilot
note.
Best Regards,
Des Gallagher.

DeLta or not Delta?

Similar Messages

Maybe you are looking for