EXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT

Hi,
I add the following fields REMNG /REWRT/ WEMNG /WEWRT in the LO cockpit
but do not understand the delta behavior.
When i extract a Invoice receipt in delta : (0processkey = 3).
fields REMNG /REWRT are OK but REMNG /REWRT are set to 0 and
infoobject are overwritten in the ODS.
When i extract a good receipt in delta : (0processkey = 2)
REMNG /REWRT are set to 0.
I do not understand how good receipt key figure and invoice receipt key figure 0GR_VAL 0 INV_RC_VAL can be correctly populate in delta mode with 2LIS_02_SCL ?
thanks for your help

Hi,
the scl-extractor for purchase delivers the granualrity Schedule line.
But in Purchase, with respect to a schedule line, you can have various things happenig. As youve described: Goods receipt, invoices and so on ...
As far as I know it's only possible to use the scl-extractor in additive mode. This is beause the fields that are delivering the required values deliver only the values of the latest event that has taken place (invoice OR goods receipt).
So if oyu use an ODS in overwrite-mode, the old, proper values are overwritten by the values of the latest record, coming via 02_scl.
One option is, to enhance the Extractor with the document-number an FI-Document-Number and add these fields as well to the ODS (overwrite).
This should work. But then you must make sure that, when initialising, you split up the cummulative record for the init into the several records provided by the document flow in pruchase.
To cut it short: chage the update-rules to "additive" on the way to your ODS.
sorry.
hth
cheers
Sven

Similar Messages

Delta error in GE-Function Module

Hi ,
my GE-delta is based on UDATE ( chenged date) from CDHDR table.
i created datasource in RS02 and i defined delta based in UDATE with upper limit 1 day and lower limit is '0'..
i created FM based on RSAX_BIW_GEDATA_SIMPLE.
for full load it working fine.
i put some extra code for delta.
it is not take any records...
i dont know much ABAP.
plz tell me where is wrong in my code for delta..
code ...
FUNCTION ZXBWMM_INV_POT_ID.
""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 STRUCTURE ZVSAIPID OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table SFLIGHT
TABLES: SFLIGHT.
TABLES: EBAN , CDPOS , CDHDR , ZVSAPR.
TYPES : BEGIN OF TY_OBJDATE ,
        OBJECTID TYPE CDHDR-OBJECTID,
        VALUE_NEW TYPE CDPOS-VALUE_NEW,
        VALUE_OLD TYPE CDPOS-VALUE_OLD,
        UDATE TYPE CDHDR-UDATE,
        MINBE TYPE MARC-MINBE,
        BSTMA TYPE MARC-BSTMA,
        WERKS TYPE MARC-WERKS,
        VERPR TYPE MBEW-VERPR,
        STPRS TYPE MBEW-STPRS,
        LBKUM TYPE MBEW-LBKUM,
        BUDAT TYPE MKPF-BUDAT,
        MBLNR TYPE MSEG-MBLNR,
        MENGE TYPE MSEG-MENGE,
        DMBTR TYPE MSEG-DMBTR,
        END OF TY_OBJDATE.
data : int_cdhdr type table of cdhdr with header line,
       int_cdpos type table of cdpos with HEADER LINE,
       INT_OBJDATE TYPE TABLE OF TY_OBJDATE WITH HEADER LINE.
      int_marc type table of marc with header line.
*DATA: int_pr1 TYPE TABLE OF ZVSAIPID WITH HEADER LINE.
DATA : BEGIN OF INT_MATNR OCCURS 10,
         MAtnr like mara-matnr,
         end of int_matnr.
DATA : BEGIN OF INT_MARC OCCURS 10,
         matnr like marc-matnr,
         MINBE like marC-mINBE,
         BSTMA LIKE Marc-bstma,
         WERKS LIKE MARC-WERKS,
         end of int_marc.
DATA : BEGIN OF INT_MBEW OCCURS 10,
         MATNR LIKE MBEW-MATNR,
         VERPR LIKE MBEW-VERPR,
         STPRS LIKE MBEW-STPRS,
         LBKUM LIKE MBEW-LBKUM,
         end of int_MBEW.
DATA : BEGIN OF INT_MKPF OCCURS 10,
         MBLNR LIKE MKPF-MBLNR,
         BUDAT LIKE MKPF-BUDAT,
         END OF INT_MKPF.
DATA : BEGIN OF INT_MSEG OCCURS 10,
         MATNR LIKE MSEG-MATNR,
         MBLNR LIKE MSEG-MBLNR,
         MENGE LIKE MSEG-MENGE,
         DMBTR LIKE MSEG-DMBTR,
         END OF INT_MSEG.
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.
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
         L_R_CONNID FOR SFLIGHT-CONNID.
RANGES : ra_OBJECTID FOR E_T_DATA-OBJECTID.
          RA_UDATE FOR E_T_DATA-UDATE.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
IF NOT G_FLAG_INTERFACE_INITIALIZED IS INITIAL.
IF 1 = 2. MESSAGE E008(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'008' "message number
' ' "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDIF.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZOI_MM_INVENTORY_IPID'.
      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.
Check for supported update mode
CASE I_UPDMODE.
WHEN 'F'.
WHEN 'D'.
WHEN 'R'.
WHEN OTHERS.
IF 1 = 2. MESSAGE E011(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'011' "message number
I_UPDMODE "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
READ TABLE I_T_SELECT INTO L_S_SELECT
WITH KEY FIELDNM = 'UDATE'.
    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.
    G_S_INTERFACE-INITFLAG = I_INITFLAG.
    G_S_INTERFACE-UPDMODE = I_UPDMODE.
    G_S_INTERFACE-DATAPAKID = I_DATAPAKID.
    G_FLAG_INTERFACE_INITIALIZED = SBIWA_C_FLAG_ON.
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
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'UDATE'.
ENDLOOP
    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 = 'CARRID'.
       MOVE-CORRESPONDING L_S_SELECT TO L_R_CARRID.
       APPEND L_R_CARRID.
     ENDLOOP.
     LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CONNID'.
       MOVE-CORRESPONDING L_S_SELECT TO L_R_CONNID.
       APPEND L_R_CONNID.
     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 SFLIGHT
                              WHERE CARRID IN L_R_CARRID AND
                                CONNID IN L_R_CONNID.
     IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''. "FULL or INIT
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      select * from cdhdr where OBJECTCLAS = 'MATERIAL' AND TCODE = 'MM02'.
      ELSE. "DELTA
     OPEN CURSOR WITH HOLD G_CURSOR FOR
     select * from cdhdr where OBJECTCLAS = 'MATERIAL'
     AND TCODE = 'MM02'
     AND UDATE >= L_S_SELECT-LOW
     AND UDATE <= L_S_SELECT-HIGH.
     ENDIF.
     ENDIF.
   ENDIF.
    "First data package ?
    FETCH NEXT CURSOR S_CURSOR
          APPENDING TABLE int_cdhdr
          PACKAGE SIZE S_S_IF-MAXSIZE.
   into table int_cdhdr
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    SELECT * FROM CDPOS INTO TABLE INT_CDPOS
         FOR ALL ENTRIES IN INT_CDHDR
         WHERE OBJECTID = INT_CDHDR-OBJECTID
         AND TABNAME = 'MARC'
         AND ( FNAME = 'BSTMA' OR FNAME = 'MINBE' ).
    LOOP AT int_cdpos.
      int_matnr-matnr = int_cdpos-objectid.
      APPEND int_matnr.
    ENDLOOP.
    SELECT matnr MINBE BSTMA WERKS FROM MARC INTO TABLE INT_marc
            FOR ALL ENTRIES IN int_matnr
           WHERE MATNR = INT_matnr-matnr.
    SELECT matnr VERPR STPRS LBKUM FROM MBEW INTO TABLE INT_MBEW
            FOR ALL ENTRIES IN int_matnr
           WHERE MATNR = INT_matnr-matnr.
    SELECT matnr MBLNR MENGE DMBTR FROM MSEG INTO TABLE INT_MSEG
            FOR ALL ENTRIES IN int_matnr
           WHERE MATNR = INT_matnr-matnr.
     LOOP AT int_MSEG.
      int_MKPF-MBLNR = int_MSEG-MBLNR.
      APPEND int_MKPF.
    ENDLOOP.
    SELECT MBLNR BUDAT FROM MKPF INTO TABLE INT_MKPF
            FOR ALL ENTRIES IN int_MKPF
           WHERE MBLNR = INT_MKPF-MBLNR.
*BREAK-POINT.
    LOOP AT INT_CDPOS.
      READ TABLE INT_CDHDR WITH KEY OBJECTID = INT_CDPOS-OBJECTID .
      IF SY-SUBRC = 0.
        INT_OBJDATE-OBJECTID = INT_CDPOS-OBJECTID.
        INT_OBJDATE-VALUE_NEW = INT_CDPOS-VALUE_NEW.
        INT_OBJDATE-VALUE_OLD = INT_CDPOS-VALUE_OLD.
        INT_OBJDATE-UDATE = INT_CDHDR-UDATE.
        READ TABLE INT_MARC WITH KEY MATNR = INT_CDPOS-OBJECTID .
        IF SY-SUBRC = 0.
          INT_OBJDATE-MINBE = INT_MARC-MINBE.
          INT_OBJDATE-BSTMA = INT_MARC-BSTMA.
          INT_OBJDATE-WERKS = INT_MARC-WERKS.
          ENDIF.
        READ TABLE INT_MBEW WITH KEY MATNR = INT_CDPOS-OBJECTID .
        IF SY-SUBRC = 0.
          INT_OBJDATE-VERPR = INT_MBEW-VERPR.
          INT_OBJDATE-STPRS = INT_MBEW-STPRS.
          INT_OBJDATE-LBKUM = INT_MBEW-LBKUM.
         ENDIF.
        READ TABLE INT_MSEG WITH KEY MATNR = INT_CDPOS-OBJECTID .
        IF SY-SUBRC = 0.
          INT_OBJDATE-MBLNR = INT_MSEG-MBLNR.
          INT_OBJDATE-MENGE = INT_MSEG-MENGE.
          INT_OBJDATE-DMBTR = INT_MSEG-DMBTR.
         ENDIF.
        READ TABLE INT_MKPF WITH KEY MBLNR = INT_MSEG-MBLNR .
        IF SY-SUBRC = 0.
          INT_OBJDATE-MBLNR = INT_MKPF-MBLNR.
          INT_OBJDATE-BUDAT = INT_MKPF-BUDAT.
         ENDIF.
        APPEND INT_OBJDATE.
      ENDIF.
    ENDLOOP.
*SELECT * FROM EBAN
    INTO CORRESPONDING FIELDS OF TABLE INT_PR1
    FOR ALL ENTRIES IN INT_OBJDATE
    WHERE BAnfn = int_objdate-objectid.
*ZZPRREL
    LOOP AT INT_OBJDATE.
      E_T_DATA-OBJECTID = INT_OBJDATE-OBJECTID.
      E_T_DATA-UDATE = INT_OBJDATE-UDATE.
      E_T_DATA-VALUE_NEW = INT_OBJDATE-VALUE_NEW.
      E_T_DATA-VALUE_OLD = INT_OBJDATE-VALUE_OLD.
      E_T_DATA-MINBE = INT_OBJDATE-MINBE.
      E_T_DATA-BSTMA = INT_OBJDATE-BSTMA.
      E_T_DATA-WERKS = INT_OBJDATE-WERKS.
      E_T_DATA-VERPR = INT_OBJDATE-VERPR.
      E_T_DATA-STPRS = INT_OBJDATE-STPRS.
      E_T_DATA-LBKUM = INT_OBJDATE-LBKUM.
      E_T_DATA-MBLNR = INT_OBJDATE-MBLNR.
      E_T_DATA-MENGE = INT_OBJDATE-MENGE.
      E_T_DATA-DMBTR = INT_OBJDATE-DMBTR.
      E_T_DATA-BUDAT = INT_OBJDATE-BUDAT.
      APPEND E_T_DATA.
      CLEAR E_T_DATA.
    ENDLOOP.
Fetch records into interface table.
named E_T_'Name of extract structure'.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
i assign points....
Regards,
PSR.

Hi ,
i am not find any sollution for this..
any body help me for this problum...
i assign points..
Regards,
PSR

Delta error in PRD

Hi
We are extracting the deltas into ODS from R/3. There was an error in extraction and activation into ODS didnt take place. The error is of invalid characteristics. The status is RED in monitor where as in data target--> manage the request is in green color but not active. I clicked on activate button and tried to activate manually but it was not getting activated.
I did the following steps.
1. In monitor screen, i converted the request into RED status.
2. In data target, i deleted the request.
3. Went to PSA, Manually changed the record and saved it. AFter changing the record the status in PSA is RED.
4. From PSA i scheduled the upload into data target immedialtely.
5. AFter scheduling, i could see the green request in datatarget with reporting icon. But the strange thing is in monitor screen the status [total] is in RED status and Technical is in GREEN status.
Q1. Now will delta takes place in next schedule, if tis in RED status?
REgards
Rak

Hi
ABY: If i repeat the delta, i will get the same error. Now i know what the error is and fixed up in PSA. We informed client and told them that it should not be done again.
Singh: After editing the record in PSA. i scheduled the upload and upload went fine in ODS. As i mentioned in the earlier thread.
In monitor screen the status is in RED where as in data target the request is in green status.
The editied record in PSA is In GREEN status,,,whereas total status is in RED.
What heppens if i turn that status into GREEN now? As i got the delta records into datatarget now.
Regards
Rak

0MATERIAL and 0CUSTOMER Delta error

Hi Gurus,
I have a problem regarding the 0MATERIAL and 0CUSTOMER Delta. It stopped due to an error in source system. When I tried to do a Repeat Delta, the system did not permit me because the Infosources does not allow update mode R (repeat). I checked previous SDN topics and found the solution.
1. Delete 'Delta Init' in Delta Channel (InfoPackage)
2. Do a Init load.
My questions are:
1. Is this the proper process or did I misinterpret the posts.
2. Would creating a new Init for the InfoSource not affect the data in the Cubes?
3. Do I have to create a Delta right after the Init?
Please advise,
Jake

Hi Jake,
1. Is this the proper process or did I misinterpret the posts.
>>Solution suggested by you is fine,
2. Would creating a new Init for the InfoSource not affect the data in the Cubes?
>> It should not affect the cube data, remember to activate your master data ( customer & material) after data load ( right click -->activate)
3. Do I have to create a Delta right after the Init?
>> you need to create delta Infopackage whenever you wish to take delta from R/3. When you do the intialization system starts tracking delta for you irrespective of whether you create delta infopackage in BW or not.
hope it helps
regards
VC
Message was edited by: VC

0sd_C01 Delta Error

Hi All,
I installed the 0SD_C01 and did the init delta without data transfer. In R3, when I try data extractor RSA3 for 2lis_01_s001 it extracts 0 records. Also when I try delta load as soon as I do init without data transfer, I get an error. Does this mean I have no data in R3 or something wrong with my delta extraction.
In the monitor I see 'Caller 09 contains an error message'
Further analysis says 'Error in SOurce System'
But I see no errors in SM37, ST22 or ST21 in R3.
Please Help.
Thanks,
Arthur.

Hi Arthur,
As you are using the old LIS Structures,
First you have a look at communication tables MCVBAK MCVBAP and so on .Then have a look at 2 tables and One Infostructure,
they are XXXXSBIW1 , XXXXSBIW2 , XXXXSBIWS.
These are transparent tables , BIWS is extract Structure and other two are data tables . u can check the active status of data transfer table in the TABLE TMCBIW
Check in Transaction MC23 and check for the Update Rules, they all should be active .
u can maintain Updating in LBW1 trasaction.
Hope it helps.
Thanks,
krish
*Awarding Points is a way of Saying thanks in SDN

0FI_GL_10 can't delta :Errors occurred during the extraction.

hi,sdn!
i have 3 DataSources,
0FI_AA_11(FI-AA: Transactions),
0FI_AA_12(FI-AA: Posted Depreciations) and 0FI_GL_10(General Ledger: Leading Ledger Balances).
The initialize and full extraction is ok.
when i delta it in rsa3,the system tell me:Errors occurred during the extraction.
Is Append Structure result in this error?
i want to know the reason,thanks!

For summarization of line items by master record characteristics (such as cost center) during posting of ODS objects to InfoCubes, master data must already exist prior to extraction of transaction data. The following sequence must therefore be kept to during extraction:
0FI_GL_4
General Ledger: line items (if required)
0ASSET_ATTR_TEXT
Asset subnumber (flexible updating)
0ASSET_AFAB
Depreciation area real or derived
then the transaction data
0FI_AA_11
FIAA : transactions and / or
0FI_AA_12
Posted depreciations (period values)

Delta Error

Hi,
While loading delta, i got an error.
Record 3873 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
Record 3874 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
can anybody can explain what it means.
how to rectify this error.
delta was loaded into PSA but not loaded into ODS.

Hi Rajini,
This ios because the request which is being loaded from PSa to DSo contains some invalid data in the field mentined.
1)go to PSA right click - > manage.
2)select the request and click on display data.
3)go to the record numbers mentioned and check the field ZWEMPF of the records for invalid data.
4)correct this records. and save data.
5)delete the red request from DSO.
6)run the delta DTP again.
Hope this helps.
Cheers,
Srinath.

Communication error CPIC return code 019 SAP return code 728. Delta error

Hello Experts,
Would just like to ask if what we suspect is correct. We have running deltas in process chains occurring every early morning. However, upon checking the delta that should have run today, I found that the delta did not push through. I only found this one dump in SM21 that I think is related to the issue:
MNo.
R49 Communication error, CPIC return code 019, SAP return code 728
R5A > Conversation ID: 61442686
R49 Communication error, CPIC return code 019, SAP return code 728
R64 > CPI-C function: CMSEND(SAP)
R5A > Conversation ID: 61443687
R64 > CPI-C function: CMSEND(SAP)
R49 Communication error, CPIC return code 019, SAP return code 728
R5A > Conversation ID: 61444687
R64 > CPI-C function: CMSEND(SAP)
Now we think that the delta did not push through because we are encountering issues with regards to our SAP R/3 system (the source system) and it is currently inaccessible. Did the delta not push through because of the issues and inaccessibility/uber slow processing of our SAP R/3 server? And is the error specified above illustrating this? Any explanation would help. I have already tried looking for similar issues but cannot find anything. Please help. Thanks!

Hi
As far I know, The SAP Gateway carries out CPI-C services within the SAP world, which are based on TCP/IP. These services enable SAP Systems and external programs to communicate with one another.
CPI-C services can be used either in the ABAP program or for the external programs via the interfaces.
As RFC (remote function call) is based on CPI-C, all RFC connections also pass through the SAP Gateway.
Errors When Starting Remote Programs Using Remote Shell
When you use remote shell to start CPIC programs on other hosts, the following conditions apply:
The (gateway) UNIX ID must be available on the other host
The gateway host must be entered in the remote host in the file ".rhosts". This file must be located in the HOME directory of the (gateway) UNIX ID.
The program you want to start must be installed in the HOME directory of the (gateway) UNIX ID on the remote host.
Read more from help
http://help.sap.com/saphelp_nw04s/helpdata/en/99/5f8c0bcb7d4280aa862254cffceada/frameset.htm

0CUSTOMER Delta Error

My recent delta from R/3 for a customer showed his street address and REGION being changed , however R/3 shows the change occured last september.
Info Object - 0CUSTOMER
Data source is Delta
Any ideas....
All teh deltas are running fine, in fact we did a full/init recently and deltas all doing good.
Any help in this is appreciated.

Hi Gopikrishna,
We had a similar issue recently when soem records that should have been in a delta load 4 months back, suddenly were loaded to BW. The issue was caught due to a date we maintain in the data and the sequence messed up the data (this was a transactional load). The reason turned out to be that the IDocs for this load were "stuck" on R/3 since Feb and another job that is supposed to process all 'hanging' IDocs was executed.
But as your situation is with master data, I guess it would not be a problem...

Delta error in production

Hi,,,
we are updating one cube through DSO during last delta its showing reuest to be red n wen we see the monitor screen its showing yellow.... plz let me know what steps shud be taken to repeat delta at DSO itself .
urgent
help wud b appreciated

Chk for any jobs in SM37 or any background process related to the load in SM66 or SM50. In datatarget if the load is running for long time it might change to red..that doesnt mean the laod has failed. Chk for any hanged IDOCS in sm58.
Regards,
B

Delta error in ods

hi experts,
if delta load fails b/n ods &infocube
how to rectify that , for that what is the procedure
when we are loading the data ods to infocube how to choose the
keyfields?is it equal to dimensions
thanks in advance
venu

Hi,
It's the same procedure which we follow for the delta from R/3 to the Bw targets.
The only thing is if you can correct it in the PSA then you can correct it there and then load it from there.
Or you can delete the failed delta request from the cube and relaod the delta
it will give you warning that you are repeating the delta.the new delta will bring the records from the failed delta as well as the records from the new delta if any.
Th key fields of the ODS are not equivalent to dimension.
Dimension are for the logical groupings of the objects and are decided in such a way that the size of dimension table should bve as small as possible.
Where as the key fields of the ODS are like the keys of the table if you want to identify a particular value with respect to a char or combination of char.just imagine it as a table with keys.
hope it clears
Thanks

Please help!! K7N2 Delta error

Today I was playing a game but instantly my monitor shutted down. X( I turned off the power and then back on, but my system hung again :( (monitor didn't get any signal). I had a look in back of my computer and saw some D-Bracket2 lights (1,4 red 2,3 green). Manual says that they means "Processor initilization" or something like that ?( and system hangs right there. Does this mean that my mobo is gone broken? :(
Specs.
K7N2 Delta L
Athlon XP 2600+ on stock
512MB PC2700
Geforce 4 Ti4200 64MB (OC 300/550mhz)

My power supply is 300W thank you for asking, and my ram brand seems to be spectek, why? Isn't that ok? I tried just what you said (clear cmos) but nothing. :( Should the power be turned on or off when you switch the jumpers? ?(
I also found something very iteresting. When i leave the fbs 100/133 jumper open, the D-Bracket complains that my memory is damaged. 8o What does that mean?

After recent patch upgrade, BW delta Data loads for 2LIS_02_ITM failing

Hi All
We have patched our BW 3.5 system from 16 to 25. After updating patches, I am geetting delta load issues.
2lis_02_itm and 2lis_02_scl delta loads are taking long long time. Deltas are failing even for 3000 records . some time it is taking 14 hours . Delta loads are failing and I am getting below message. Please advise.
I am still getting below dump and i could not find any errors in
ST22. Please see below error.
Processing in Warehouse timed out; processing steps mising
Diagnosis
Processing the request in the BW system is taking a long time and the
processing step Update rules has still not been executed.
System response
<DS:DE.RSCALLER>Caller is still missing.
Procedure
Check in the process overview in the BW system whether processes are
running in the BW system under the background user.
If this is not the case, check the short dump overview in the BW system.
Thanks
Pramod

Hello Pramod,
Is this load is to load to initial level ODS? If Yes I understand that you have issue in loading but not at activation of the ODS?
Normally this kind of issue comes during the activation of ODS.
1. If you are getting this during the data loads, then try to check loading only to PSA first and then from PSA to target? And check how much time that it's taking as this will help to track the issue whether its present in Source or in BW?
2. If the load is fine till PSA then try loading the same to ODS and then check whether this issue is present or not?
3. At the same you need to check the source side the system load and the number of processors which are available?
4. Did you perform the delta queue draining before the stack upgrade in R/3 or not? Normally as a pre-requisite this needs to be done if not then you will have issues in extracting the data!
5. Finally this can be avoided by having Initwithout data transfer and then performing the Delta loads. BUt for this need to first extract all the data from Source to BW and then take a down time in R/3 for few min and perform this activity so that the Init Timstamp will be reset properly and the Delta should work fine for you.
Do get back to us with more details.
Thanks
Murali M

Confirmation - error in process - idoc status 29

HI ,
i got one new problem today.
This is one of the case when one user createsconfirmation of the Purchase order and then Confirmation status goes to error in process. i check in RZ20 and found error in Idoc which is generated from that confirmation,When i check the status record it says error in ALE.status 29. Only an inactive partner profile was found with the following key and this is my PRDCLNT100 (production system address).
I can see that all other confiramtions are getting posted but having an issue with one confirmation.
2ndly how i can delte error in process Confirmation . So that we can create new confirmation , or is there any other way to get my present confirmation status to Posted.
Smriti

Hi Smriti,
Regarding working on the faulty IDOC
In WE19 check what Function module will be used to post the data, you can see it when you go to 'standard inbound'. Then you can debug it when you click to the button 'inbound function module', here enter the function module and click 'call in debugging mode' and 'in foreground', then press the button 'enter'. Now you are in the debugger and can check why the error occurs and what should be filled.
If you know the error number set watchpoint at sy-msgno = *** or just set breakpoint at statement message.
If this is only happening for one confirmation, the standard approach to delete this is the following.
Issue:
The corresponding IDOC for the confirmation document has not been processed successfully and ended with error in the backend.
Solution:
Because of this there is entry left in the table bbp_document_tab,
which is not allowing to cancell the confirmation document.
Please find the attached note 338985, which contains the procedure to
to delete entries from table bbp_document_tab.
Hope this helps,
Kind Regards,
Matthew

Data mart error

Hi All
Delta is failed when uploading from delta from ODS to Cube. The error msg is :
<b>Diagnosis
The data update was not completed. A short dump has probably been logged in BW providing information about the error.
System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
Error correction:
Follow the instructions in the short dump.</b>
but when i clicked on the short dump i get msg:
<b>None of selected short dump exist</b>
It happened on 6th dec...since then no delta uploads r taking place from ODS to Cube. how can i fix this...
Regards
Shetty

Hi Everyone
Thanks for your inputs..Now due to some problem our production server will be off for some time,tats y i couldnt do the steps now.
siddu as you gave me the note number in which it explains about indexes.
As per my knowledge its related to performance reasons but after reading the notes i think if we dont delete and create the indexes it may cause the deadlock.
Is it necessary to delete indexes b4 loading then new data?
and one more thing
Actually the delta load failed from ods to cube on 5th, the onwards deltas didnt updated the cube. so i deleted the delta error request from the cube and in ODS i deleted the TICK mark for the MANAGE Request tab. Then i went to the delta package and scheduled. I am getting the msg that last delta is failed and you have to reload the delta and also if the QM status is in green or red.
My question is after deleting the request y i am getting that msg and action is getting cancelled. this is happening to almost all the failed request in the production i am not able to repeat the delta unless i delete the request from the cube and reload...plz provide me a soultion..
Regards
Shetty

EXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT

Similar Messages

Maybe you are looking for