Initialisation option - Delta problem

Hi guys..
I tried to load my delta request and it says,no active delta initialisation is available for the data source.
I checked in the infopack->scheduler->init option for source system,and there is no init request available there.( Think got deleted accidentally)
In my target we have init request as well as delta requests for the past two months.
So how do i reccover this initialisation request..
Can i do initialisation without data transfer and then continue loading my deltas.Will it give any problem???
Thanks & Regards
Ragu

Hello ,
You can do the deltas without re-doing init. But it depends on the no. of deltas records since you have done init (populated setup) last time.
if the deltas are huge, then by just running the v3 again may overflow the delta queues!!
Due to this risk i suggested to redo the setup run.
But if you have some costraints, you dont delete the set up tables. delte from Rsa7 the delta queues for ur datasource. reschdule the v3.
again run the delta in BW. check with the reports against the R/3 tables-records(just to check if the delta queues didnt overflow and all deltas have been taken care of).
Hope this helps..
thanks,

Similar Messages

Initialisation option for source system in schedular tab

What initialisation option for system in schedular tab signifies? Does it acts as pointer and points to the last record loaded in cube or ods?

Hi....
Welcome to SDN..........
Initialisation option for source system in schedular tab........
shows to you all the init you made for a specific datasource/sourcesystem...if you find a row here, it means that the init channel is active and you can load delta for that specific flow.....
Initialization may with data transfer or without Data Transfer.......If you do with data transfer it will set the init flag............as well as it will fetch the data from set up table...........if you do without data transfer it will only set the init flag.....it will not fetch any records.........As soon as this init flag get set.......delta queue will get generated in the source system........after that any changes or new records will go to the delta queue.............So initialization load will be followed by delta load......
When you have to reinit, first of all you have to delete this row and then request a new initial load, otherwise the system cannot allow to perform a new init (with overlapping condition) if you don't deete the previous one....
Hope this helps
Regards,
Debjani.......

Initialisation option for source system

Hi Gurus
Can anyone explain clearly about
Initialisation option for source system
Thanks in advance
Raj

Hi,
This option is used when you want to init / re-init delta loads from source system (R/3 or BW Datamart). You have to set-up your Initialization before you can run your deltas.If you have already deltas loaded or want to load deltas from source you have to do an init load. In case you have already loaded deltas you have to delete the existing Init Request from your data target and perform re-init.
You have two options Init with data transfer and without data transfer.
Init is just setting path for deltas to follow.
Steps for Re Init from R/3 to BW
1)Delete the contents of Application area 11 inRSA7 delta queue/LBWQ
2) Delete the setup table for the application 11 in LBWG
3) Delete the initialization information in BW , By deleting the 'initializing option for source system ' from infopackage(delta initialization).
4) Delete the PSA and data in Datatargets.
5) Fill the setup table for the application 11.
6) Execute the delta initialization infopackage for these Datasources.
Thanks,
JituK

Initialisation options for source system

If I am in an InfoPackage and seleet the option "Initialisation options for source system" and have more than one entries, is there any way that I can delete just one of the entries? Thanks

Hi there as a test scenario I am trying to delete one entry but it deletes both giving a message as below pre deletion, what am I doing wrong? Thanks
There are active init selections in source system for this data source
Therefore, only ALL init selections can be deleted at once
Do you want to delete all init selections (all channels)?

Copa delta problem

Hi All,
I enhanced the copa DataSource by adding the new value field,then i have loaded the data
Initial Load without data transfer then run the delta update it is give ZERO records.
When i checked in COPA table level and KE24 report level in r/3 side data is there.
Is there any problem in my delta.If is there delta problem where to check and how to resolve this.
Please help me ASAP.
Thanks in advance.
prasantha

HI Sathish,
Based on in your information i have checked in KEB2 it is giving the below error.can you help wht is this
and how to resolve this error.
the below error is keb2 tcode(based on below error i have one doubt delta is geting the data into
head level data.
Subsequent time stamp information only has statistical character.
The time stamp relevant for reading data is found in the header information for the
DataSource.
For data extraction from several BW systems, the number of records read and sent that is
displayed does not have to agree with the actual number (due to Service API logic).
Delta init simulations are not listed in the overview because the CO-PA extractor
is not called in this case and it consequently does not update any log entry.
Thanks and regards,
kumar.k
Edited by: kumar reddy on Jan 20, 2009 8:10 AM

Generic delta problem : in init load, the request is in yellow.......

Hi all,
I have created a table in R/3, and created a Generic data source using this table, and coming to deltas, i have selected Numeric pointer in which I have given the sales document number which comes from the table as the Delta relevant field. And the other things like replication, creation of info source, info package did well and I als got Initialization option in Info Package, but when I schedule the load, its coming in yellow signal and says that 0 records from 0 records, and gives error message as no records in the source system. This is the case if I use Init option in Info package.
If I use Full load option in info pack, every thing is fine and I am able to extract the data from R/3 with out any problem, the load is getting succeeded.
The only problem is with deltas. Is there anything else to do on R/3 side to enable the delta mechanism? or is it required to use functional module to enable the deltas ( I read this in some posts)? Please give me some solution.
Thanks
Ganesh

Hi,
There is no need to make any settings of delta...in general..it should work as similar as your full load....try to locate the problem area..and revert...
Advise, check if there are any previous init. and delete...otherwise create a new
infopackage and try..
Cheers,
Pattan.

BW GENERIC EXTRACTION DELTA PROBLEM

I have a problem for extracting delta from R/3 to BW.
Init data is loaded from R/3 to BW system for ZST_ORDER datasource.
Repair full request and selection parameter is created on date August 1st 2007 to August15th 2007.
During the delta extraction - A lot of records around 500,000 records are getting extracting from R/3 to BW.
R/3 side - There is only 5 entries available in AUFK table.
It should extract delta only less than 35 entries.
ZST_ORDER is generic datasource . Delta captured field is DATUM -New status changed record value 2.
Advance Thx for your help. The code looks like
FUNCTION ZST_ORDER.
""Local Interface:
*" IMPORTING
*" REFERENCE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" REFERENCE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" REFERENCE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE DEFAULT 1000
*" REFERENCE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" REFERENCE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" 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 ZST_ORDEROPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
TABLES: AUFK, "Order master data
TJ02T, "System status texts
TJ30T, "Texts for user status
JSTO. "Status object information
DATA DECLARATION
DATA: L_DATE TYPE DATS,
L_STATUS TYPE J_STATUS,
L_LINES TYPE SY-TABIX,
L_CHANGED(1) TYPE C.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Another data objects
Service Order Data
DATA: BEGIN OF LT_AUFK OCCURS 0,
AUFNR LIKE AUFK-AUFNR,
AUART LIKE AUFK-AUART,
ERDAT LIKE AUFK-ERDAT,
AEDAT LIKE AUFK-AEDAT,
STDAT LIKE AUFK-STDAT,
AEZEIT LIKE AUFK-AEZEIT,
ERFZEIT LIKE AUFK-ERFZEIT,
IDAT1 LIKE AUFK-IDAT1,
IDAT2 LIKE AUFK-IDAT2,
IDAT3 LIKE AUFK-IDAT3,
LOEKZ LIKE AUFK-LOEKZ,
OBJNR LIKE AUFK-OBJNR,
END OF LT_AUFK.
Individual Object Status
DATA: BEGIN OF LT_JEST OCCURS 0,
OBJNR LIKE JEST-OBJNR,
STAT LIKE JEST-STAT,
INACT LIKE JEST-INACT,
CHGNR LIKE JEST-CHGNR,
END OF LT_JEST.
***Change Documents for System/User Statuses (Table JEST)
DATA: BEGIN OF LT_JCDS OCCURS 0,
OBJNR LIKE JCDS-OBJNR,
STAT LIKE JCDS-STAT,
CHGNR LIKE JCDS-CHGNR,
USNAM LIKE JCDS-USNAM,
UDATE LIKE JCDS-UDATE,
UTIME LIKE JCDS-UTIME,
INACT LIKE JCDS-INACT,
CHIND LIKE JCDS-CHIND,
END OF LT_JCDS.
DATA: BEGIN OF LT_JSTO OCCURS 0,
OBJNR LIKE JSTO-OBJNR,
STSMA LIKE JSTO-STSMA,
END OF LT_JSTO.
STATIC FIELDS
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
S_CURSOR TYPE CURSOR.
User-defined Ranges
RANGES: L_R_AUFNR FOR AUFK-AUFNR ,
L_R_ERDAT FOR AUFK-ERDAT.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Check DataSource validity
CASE I_DSOURCE.
WHEN 'ZST_ORDER '.
WHEN OTHERS.
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
Copy selection criteria for future extractor calls (fetch-calls)
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.
S_S_IF-INITFLAG = I_INITFLAG.
APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.
First data package -> OPEN CURSOR
IF S_COUNTER_DATAPAKID = 0.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'AUFNR'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_AUFNR.
APPEND L_R_AUFNR.
ENDLOOP.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'ERDAT'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_ERDAT.
APPEND L_R_ERDAT.
ENDLOOP.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'DATUM'.
L_DATE = L_S_SELECT-LOW.
ENDLOOP.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT AUFNR AUART ERDAT
AEDAT OBJNR AEZEIT
STDAT ERFZEIT IDAT1
IDAT2 IDAT3 LOEKZ
FROM AUFK
WHERE AUFNR IN L_R_AUFNR AND
ERDAT IN L_R_ERDAT.
ENDIF.
Fetch records into interface table LT_AUFK
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS OF TABLE LT_AUFK
PACKAGE SIZE S_S_IF-MAXSIZE.
IF SY-SUBRC <> 0.
CLOSE CURSOR S_CURSOR.
RAISE NO_MORE_DATA.
ENDIF.
Determining the number of lines of the table LT_AUFK .
L_LINES = LINES( LT_AUFK ).
IF L_LINES IS NOT INITIAL.
Sort the internal table LT_AUFK
SORT LT_AUFK BY OBJNR ASCENDING.
Selecting the records from JCDS depending upon the entries in LT_AUFK.
SELECT OBJNR STAT CHGNR USNAM
UDATE UTIME INACT CHIND
INTO TABLE LT_JCDS
FROM JCDS
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR EQ LT_AUFK-OBJNR
AND ( CHGNR EQ '001'
OR UDATE >= L_DATE ).
Sort the internal table lt_jcds.
SORT LT_JCDS BY OBJNR STAT CHGNR ASCENDING.
Select records from table JEST depending upon the entries in LT_AUFK.
SELECT OBJNR STAT INACT CHGNR
INTO TABLE LT_JEST
FROM JEST
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR = LT_AUFK-OBJNR.
SELECT OBJNR STSMA
INTO TABLE LT_JSTO
FROM JSTO
FOR ALL ENTRIES IN LT_AUFK
WHERE OBJNR = LT_AUFK-OBJNR.
SORT LT_JSTO BY OBJNR.
ENDIF.
LOOP AT LT_JEST.
CLEAR: LT_AUFK,
l_changed.
CLEAR L_CHANGED.
CLEAR LT_JSTO.
READ TABLE LT_JSTO WITH KEY OBJNR = LT_JEST-OBJNR BINARY SEARCH.
IF SY-SUBRC EQ 0.
E_T_DATA-STSMA = LT_JSTO-STSMA.
ENDIF.
*End**
Read the data from LT_AUFK.
READ TABLE LT_AUFK WITH KEY OBJNR = LT_JEST-OBJNR BINARY SEARCH.
E_T_DATA-AUFNR = LT_AUFK-AUFNR.
E_T_DATA-AUART = LT_AUFK-AUART.
E_T_DATA-ERDAT = LT_AUFK-ERDAT.
E_T_DATA-AEDAT = LT_AUFK-AEDAT.
E_T_DATA-AEZEIT = LT_AUFK-AEZEIT.
E_T_DATA-ERFZEIT = LT_AUFK-ERFZEIT.
E_T_DATA-IDAT1 = LT_AUFK-IDAT1.
E_T_DATA-IDAT2 = LT_AUFK-IDAT2.
E_T_DATA-IDAT3 = LT_AUFK-IDAT3.
E_T_DATA-LOEKZ = LT_AUFK-LOEKZ.
E_T_DATA-INACT = LT_JEST-INACT.
E_T_DATA-CHGNR = LT_JCDS-CHGNR.
e_t_data-datum = lt_aufk-erdat.
READ TABLE LT_JCDS WITH KEY OBJNR = LT_JEST-OBJNR
STAT = LT_JEST-STAT
CHGNR = '001'
BINARY SEARCH.
IF SY-SUBRC EQ 0.
E_T_DATA-UDATE = LT_JCDS-UDATE.
E_T_DATA-AEDAT = LT_JCDS-UDATE.
E_T_DATA-UTIME = LT_JCDS-UTIME.
E_T_DATA-AEZEIT = LT_JCDS-UTIME.
E_T_DATA-CHIND = LT_JCDS-CHIND.
E_T_DATA-USNAM = LT_JCDS-USNAM.
e_t_data-chgnr = lt_jcds-chgnr.
IF LT_JCDS-UDATE GE L_DATE
AND L_DATE IS NOT INITIAL.
L_CHANGED = 'X'.
ENDIF.
IF LT_JEST-CHGNR NE '001'.
CLEAR LT_JCDS.
READ TABLE LT_JCDS WITH KEY OBJNR = LT_JEST-OBJNR
STAT = LT_JEST-STAT
CHGNR = LT_JEST-CHGNR
BINARY SEARCH.
IF SY-SUBRC EQ 0.
L_CHANGED = 'X'.
E_T_DATA-AEDAT = LT_JCDS-UDATE.
E_T_DATA-AEZEIT = LT_JCDS-UTIME.
E_T_DATA-CHIND = LT_JCDS-CHIND.
E_T_DATA-USNAM = LT_JCDS-USNAM.
e_t_data-chgnr = lt_jcds-chgnr.
ENDIF.
ENDIF.
IF LT_JEST-STAT(1) EQ 'I'.
E_T_DATA-ISTAT = LT_JEST-STAT.
ELSEIF LT_JEST-STAT(1) EQ 'E'.
E_T_DATA-ESTAT = LT_JEST-STAT.
ENDIF.
IF L_CHANGED EQ 'X'
AND L_DATE IS NOT INITIAL.
APPEND E_T_DATA.
ELSEIF L_DATE IS INITIAL.
APPEND E_T_DATA.
ENDIF.
ENDIF.
CLEAR: LT_AUFK,
E_T_DATA.
ENDLOOP.
CLEAR LT_JEST.
REFRESH LT_JEST.
next data package
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.

hi,
for that quantity SALK3 is referring a different table in the reference field for your table fields. check that field and refer the correct table for that field in table view.
table join has a problem in that. i think your joined some other table with that field. replace the field assignment or create a new view.
hope this help you
regards
harikrishna N

Generic extractor Delta problem

hello,
i have created a Generic extractor based on the AUFM table and the delta field is MBLNR (Material document no) that is a numeric pointer used for delta. My problem is that when i pull the delta not all records are being pulled. Why is that so? Can anyone give suggestions.
thanks
Laura.

Well, using Function module is one approach. I can provide you another approach.
You can create a View based on the following tables
AUFM and MKPF,
use the join condition
AUFM-MANDT= MKPF-MANDT.
AUFM-MBLNR = MKPF-MBLNR
AUFM-MJAHR = MKPF-MJAHR
In AUFM select all the fields that you want and MKPF select the "Accounting Document entry date" field which you can take it as delta field and select calday as your delta option.
Once view is created, you can generate the datasource.
Please check this option.
I think it should work...
Thanks
Vj

Delta Problem while extracting the data by using function module

Hi Experts,
I have extracted the data by using Function module, for delta loads I have given Calday and additive delta in Generic delta settings, in BW side I have initialized the data after that I have given delta update option in infopackage and I made process chain also, every day process chain is running successfully but it is showing zero records, but there is a data in Data source (RSA3), means delta is not working.
What is the problem,
Is there any another settings for delta loads,
Please help me to do this,
Helpful answer will be appreciated with points,
Regards,
Venkat

Hi,
Try this delta type :NEW STATUS FOR CHANGED RECORDS.
More information from Nagesh, this information may help
1. New status for changed Records.
2. Additive delta.
New status for changed records means
New Order
order no quantity
1000 10
order changed to quntity 8. then 2 records will posted 2 BW in first case.
1000 -10
1000 8
if you come to Additve delta.
for the same case it will send the same record as
1000 10
changed records
1000 -2
this is the difference. New status with changed records should be used only in association with ODS not cube becoz we don't have overwrite option.
Additive delta we can use for ODS and Cubes with update mode Addition.
Regards,
Satya

K7N2 Delta problems

Hey all..having a huge problem with my computer and have no idea what's going on.....when i try to reformat, i am getting errors with blue screen. errors are as follows: Page_Fault_In_Non_Paged_Area followed by the stop error numbers
Driver_IRQL_Not_Less_Or_Equal
IRQL_Not_Less_Or_Equa
as well as a wait or yield error in a DPC routine
Now, when i reset the bios, it will reformat and install windows, but I never had to do this before. Also, when i am up and running, i am getting both crash and reboots, as well as lock-ups. Again, never happened before a month or so ago. Does anyone have any ideas? I don't know if this is a PSU issue, a BIOS issue( I just updated to the latest BIOS version, but after all the problems), a heat issue or what. Here are my specs:
MSI K7N2 Delta
Athlon XP 3200+
2x512 mb of DDR333 RAM
usually use Radeon 9700 Pro, but am currently forced to use FX 5200
WD 60 gb hdd with 8 mb cache
AOpen 300 watt psu
3.3v - 20.0A 5v - 30.0A 12v - 13.0A
any help would be appreciated gang...have a good one !!

Flash the bios back to B30. Much more stable than B40. B40 are really buggy same as the beta one. Good Luck.
Tbred B 2400 (180 x 13.5) 2.10 volt
MSI K7N2 Delta2 LSR
2 x 256 PC2700 Kingston Value RAM
Powercolor Radeon 9600XT 600 core 800 memory
450 Icute PSU.

PM Delta problem. Notifications coming into lbwq but Orders are not coming.

Hi,
I'm talking about 2 datasources of PM modules. I've problem with one of them only.
1. 2LIS_17_I3HDR(I've problem here)
2. 2LIS_17_I0NOTIF(I've no problem here)
When I create or modify some notification I get the information immediately in lbwq and then I take it to bi system. But when I create some orders or modify some I don't get them in lbwq.
My analysis:
The difference between these two datasources in our server is
1. I've converted 2LIS_17_I3HDR data flow to bi7 i.e. transformations and dtps. I've deleted the update rules and infosources and transfer rules i.e. 3.x objects.
2. I've enhanced 2LIS_17_I3HDR and written some code in cmod or exit to fill the enhanced fields.
I've searched the sdn thoroughly and couldn't find any solution. Please help.
Regards,
Sujit.

Hi All,
I've found solution to my problem. After trying so many methods I found one which solved my problem. The function module PMEX_UPDATE_17_1_QRFC was not active. I activated that and delta records started coming into lbwq.
Now one more question is do I need to activate this function module in Production server also when we go live? What is the exact procedure?
Another doubt is : is there any way to recover the delta records which didn't come to lbwq before the activation of function module. I know I need to delete the setup tables and fill it again. But is there any other way?
Thanks,
Sujit.

"JPEG Options" Box Problem--Help!

I am new to Lightroom and having a problem using the "Export Actions" function. I am a wedding editor and I send thousands of files through the Bridge Photoshop>Image Processor every week. Well now that I switched over to Lr, I am using the Export Actions function during exporting in order to run my Photoshop actions on the files.
Here's what I do: I export Tiff files and save them as a Jpeg, while also running an Export Action. As a Bridge image processor action, this worked perfectly fine (ie Photoshop opened the files, ran the action, saved, and closed). Now that I am running the action through Lr as an Export Action, Photoshop displays a "JPEG Options" save box for EACH file that you must click "OK" in order to go on to the next file. Again, I run thousands of files and I cannot click "OK" on each one.
Why is this "JPEG Options" box suddenly appearing when it never used to? How can I get Lr/Photoshop to run this action like normal (save and close without being prompted by me)?
Additional Infor: I have Lightroom 2 and Photoshop CS3.
When I create the droplets in Photoshop, I have "Override Action Open Commands" unchecked.
[See "Problem with a Scott Kelby Action" post below for someone who had the same exact problem]

Another thing you could do (although I'm sure you won't want to do it) is export TIFF images from Lightroom so that they include all of the Lightroom changes. Then exit Lightroom and load those exported images into Bridge and run your action.
I like Lightroom, and I use it every day. But occasionally I find that it's easier to just forget about it and do all of the work in Photoshop. This is probably because I haven't taken the time to really become proficient with Lightroom, especially integrating it with Photoshop. So I just take the easy way out when I'm forced to do so.

Inconsistencies data between ODS and RSA3 in SAP system (delta problem??)

Hi everyone,
I have a problem in my SAP BW production system. There is inconsistencies data between ODS (using tcode LISTCUBE) and Datasource in SAP system (tcode RSA3).
I'm using Datasource: 0FI_GL_10 and ODS: 0FIGL_O10.
In SAP system (using RSA3):
GL Account: 1202012091
Comp Code : 5400
Bus Area: 5401
Fiscal Year :2008
Period: 07
Accum Balance : $0
Credit Total: $350
Debit Total: $350
Sales : $0
And in ODS (using ListCube):
GL Account: 1202012091
Comp Code : 5400
Bus Area: 5401
Fiscal Year :2008
Period: 07
0BALANCE : $350 (it should be $0,shouldn't it? )
0CREDIT: $0 (it should be $350,shouldn't it? )
0DEBIT: $350
0SALES: $350 (it should be $0,shouldn't it?)
I have tried these :
1. Check if there is a start routine / routine or not in transfer or update rules....and...i get nothing
2. Check the data using tcode FBL3N..but the data is ok
And then i tried to trace the process chain and find error on delta infopackage which pull these data
Date
07.30.2008 : 231141 records --> error (ODS activation) --> request has deleted forever
07.31.2008 : 2848 records --> error (ODS activation) --> request has deleted forever
08.01.2008 : 135679 records --> error (ODS activation) --> request has deleted forever
08.02.2008 : 135679 records --> successfull repeat delta action
From 30 July until 1 August there is an error on delta infopackage because
fail to activate ODS (No SID found for value 'RIM' of characteristic 0UNIT). On 2 August someone delete the red requests and repeat the delta and success. Is there any possibilities that this problem arise because of this? If this the cause, how to bring back 2848 and 231141 records which has deleted?
Thank you and Regards,
-Satria-

Hi everyone,
I have solved my problem. I executed my infopackage again (selection condition using GL Account which have wrong amount) with update mode 'Full update' and choose Scheduler > Repair Full Request and tick the checkbox.Thank you.
Regards,
-Satria-

Urgent Help Reqd: Delta Problem....!!!

Hi Experts,
Urgent help reqd regarding follwoing scenario:
I am getting delta to ODS 1 (infosource : 2LIS_12_VCHDR) from R/3. Now this ODS1 gives delta to Cube1. I got one error record which fails when going to cube (due to master data check).And this record would be edited later.
So I thought of re loading cube and using error handling to split request in PSA and load valid records in cube.Later when I have coorect info abt error, I would load erroneous record manually using PSA.
I did following steps:
1)Failed request is not in cube...(setting is PSA and then into target)....also it has been deleted from PSA.
2)Remove data status from source ODS1.
3)Change error handling in infopackage to valid " Valid records update, reporting possible".
4)start loading of cube.
But when I did this I got following message :
<b> "Last delta update is not yet completed.Therefore, no new delta update is possible.You can start the request again if the last delta request is red or green in the monitor"</b>
But both my requests in cube and ODS are Green...no request is in yellow...!!
Now the problem is :
1) I have lost ODS data mart status
2)how to load valid records to cube, since errorneous record can be edited only after 3- 4 days.
3)How not to affect delta load of tomorrow.
Please guide and help me in this.
Thanks in advance and rest assured I will award points to say thanks to SDNers..
Regards,
Sorabh
Message was edited by: sorabh arora

Hi Joseph,
Thanks for replying....
I apolgize and I have modified the message above..
I just checked in cube...there is no failed request for today...and neither in PSA....Person who has handed this to me may have deleted this is PSA..and why req is not in failed state in cube...I am not sure..though setting is "PSA and then into data package".....
So how to go frm here....
Thanks
Sorabh

PSE10 Layer Panel Options display problem

Anyone else have this problem with PSE10?
Select the Layers Panel Options:
The dialog box should be displaying some kind of images and descriptions for the thumbnail sizes, shouldn't it?
This is Win7 x64, and happens whether or not I've disabled the SWF files to get rid of those animated help tips in the lower right corner....
Ken

Hi Ken,
This is what I get
I'm using Win7/64 & PSE10
Brian

Initialisation option - Delta problem

Similar Messages

Maybe you are looking for