Reload delta

From R3 delta loded into the cube and rollup it. from there it loaded into an ODS.  Then it deleted from the ODS. how can I load it again from the Cube to the ODS for this delta? Please help me

Hi,
you have to reset the delta flag in the cube. Goto to cube administration and see the flag for the data mart status of request. There should be a checkmark. Click on this checkmark and in the next screen delete the selected request.
After that, the checkmark shuold disappear in the cube. Then you can goto your delta infopackage and reload the delta from cube to ODS again.
Hope you got an idea.
Regards,
Juergen

Similar Messages

  • Problem in delta job

    Hi guru's,
    Delta job not running.
    Yestarday delta was failed becoz of the incorrect dataformat. I corrected the data in PSA and loaded to dso. But still the request in PSA  is showing red. But data is loaded successfully to dso.
    Today delta job not started. what may be the reason and guide me the corrective actions to take.
    regards,
    Siddes

    Hi Sid,
    Is the QM status of the IP and the status of request in DSO green? As you have corrected the data in PSA and updated it to target both the QM status of the IP and the status of request in DSO should be green.
    If both are green and still the load is failing please post the error message.
    Moreover its better to correct the data in source system and reload delta if possible.

  • Problem in updating delta from cube to cube

    Dear experts,
    I created an delta upload from CUBE A to Cube B. I initialised it yesterday and did my first update. Today I did the second update from Cube A to B.
    But then i found there were some problem in my CUBE A. After I reload data into Cube a. I would like to redo the delta.
    I deleted the request of update load of today in CUBE B. And relauch the infopackage. But there was error message. System said the data is not coherent between datasource and target.
    What could be the problem?
    Thanks in advance!!

    So u want to reload delta from Cube A to Cube B right?
    The load is successful in Cube A?
    Then u need to reset the delta mart and force the request to red in cube B and delete the delta request from cube B and then retrigger the delta load

  • How SAP determines Delta records?

    Dear Experts,
    I have a standard extractor 2LIS_02_ITM. It works like this.
    1. when a sales order is saved, a customized program creates a new PO and updates a field in the PO using direct update, the abap 'update' command.
    2. in BI, this record created is loaded as delta.
    3. We notice that sometimes this when delta loaded, this field is blank and sometimes its not.
    A. We suspect the delta did not capture program-created PO if this field value is populated as blank by the program.
    B. If the program-created PO is opened and edited by user and then saved, SAP would generate a Delta record?
    If this delta is created and BI reloads delta, this delta would be loaded into BI and the report would show the field value.
    So, I need to check with experts here if using customized program to create a PO and update a field in it at the same time, would this be captured by the Delta mechanism?
    Normally, if manually created, the PO would, i assume, be captured in the delta queue. But what about using program?
    Please advise how delta is or can be affected by programs and how exactly is delta determined in this case. This standard extractor is set to use delta, i think using numeric field.
    So, I am not sure if its due to R/3 or BW. For BW, its a direct mapping of the updated field. So, I do not think there is an issue on BW side.
    regards
    Pascal

    Dear Debjani,
    On your reply to point 2 about the timing of LIS V3 update run, I like to seek clarification how the timing could cause the problem given that many delta records have successfully been loaded with existing way where a collection run is scheduled to run every around 15 minutes and is able to capture the delta except in some cases which is the problem? How can the field value change be missed due to this?   On your point 3 reply, the PO is created by program and it can be created by user.
    I still require some clarification . Hope you can kindly bear with me.
    1. For most of the delta records loaded into BI from R/3, there is no problem with the data. The program-created PO records can be loaded. But for some cases, even when this field is populated by program or EDI, after auto-creation of the PO. This delta is loaded into BI with this field being blank.
    2. This suggests to me, for most cases of the auto-PO creation, the BI Delta mechanism in R/3 is able to handle PO created by automated program in R/3.
    3. So, seems to me, regardless of how the PO is created : user created / by program / by EDI, the delta mechanism seems to work. So, I like to learn more how exactly can TIMING difference (asynchronous) between the creation of PO records and the LIS V3 update delta queue creation batch job have resulted in the field update from not being extracted into the delta queue ?
    Solutions (i think):
    1. Is it possible to Change the current delta queue update extraction method from periodic (every x minutes) V3 update batch run to the Direct / Unserialised V3 update  extraction method as mentioned by Arvind earlier? Would this mean every time PO is created by any means, even by program or field updated by EDI, the delta queue is immediately created to capture the change? This sounds like a solution?
    2. Have the auto-PO creation program Trigger an R/3 event to run the V3 update whenever it has completed an update or PO creation to generate the delta queue. Would this load the r/3 too much if run frequently? Or since frequent run would mean also less delta queue created which means shorter run time?
    Dear Sven,
    would it be good idea to use the program for ME22N to update the particular field After the PO is auto-created by the ME21N program? Would this mean, using these programs will assure that delta is captured?
    Best regards
    Pascal
    Edited by: Pascal Gabin on May 11, 2011 9:24 AM

  • Production Error

    It was in yellow status from long time and it will go to red status
    iam getting this type of errors
    No statistics vendor could be found for article VCA1177431OT2406ZZ     RTBW     
    No statistics vendor could be found for article VCA1177417OT2409ZZ     RTBW     302     
    No statistics vendor could be found for article VCA1177419OT2409ZZ     RTBW     302     
    Users have created this it was around 500 articles like this
    I have reloaded Master data and reloaded delta but the error was same this was happening from 5 days
    may I know the solution of this
    It very urgent issue plz
    Thanks & Regards
    Sipra

    Hi Sipra,
    The statistics error occurs at the Operating System(OS) level.
    You should contact with your basis team , to solve with this.
    Hope this would help you.
    Assign points if helpful.
    Thanks,
    anu

  • In BI 7, how to reload a red request into a DSO without deactivating delta?

    Hi,
    In BI 7, how to reload a red request into a DSO without deactivating delta?
    I have a red request in DSO A. I have corrected the Transfer rules and want to reload the request from PSA to DSO A. I have active delta from DSO A to DSO B.
    The only way I have found to reload the red request into DSO A, is to delete it first (like in BW 3.5). The problem then is that the system then gives me no other option than deactivating the delta from DSO A to DSO B. I then have to re-initialize delta from DSO A to DSO B with data transfer. Of course I first have to delete the data content in DSO B. I cannot do this because DSO B is very large. A reload would take several days.
    I have tried to reload the request from PSA without first deleting it from DSO A, but DSO A is not a valid target in the scheduler unless I delete it from DSO A first.
    This scenario must be very common and there must be a very simple solution, I just cannot find it.
    Any one who can help me?
    Best regards
    Kent Dahlgren

    Hi Kent,
    Regarding your questions,
    Have you already  tried to delete the red request and reconstruct it ??
    If the system gives you no choice beside delete delta ODS A to B, how about if you keep deleting the delta from ODS A to B, but after that you re-initilize with the option : no data transfer.
    Hope it can help you a lot.
    Thanks,
    Best regards,
    Daniel

  • How should I reload the delta load?

    Dear all,
    An ODS which includes Sales invoice information with daily delta load. The loading is fine but somehow one KF got different logic from April e.g. for same order this KF has correct value after April but incorrect value before April. So I am going to reload data old than April, but all the old load are fine and existed, so how should I do?
    Thanks

    Hi,
    Thanks for you reply, No date for selection. So I found some data in the ODS for a specific comany code and the bill type(I got 16 recordes), then I created a Infopackage then put the selection same with the company code and bill type, set it to full load and run immediatly, but 0 record was loaded. I am sure the corresponding data exist in R3 because I checked the data using VA03. So what's the problem?
    Thanks in advance

  • Error while resetting the delta in ODS  (BI 7.0)

    Hi all,
    I face a problem in delta resetting...need your help... Thanks..
    I have an ODS-1  which has target cube1, cube2, cube3....One week back a new target has been added as ODS-2....All complete data from ODS1  has been piped into ODS 2..(Note.. ODS2 has many more inputs from other cubes/ODS too)
    NO issues till now....
    I found a data problem in ODS-1 which got loaded 15 days back..... I have removed all 15 requests from cube1, cube2 and cube3... Now I am trying to reset the delta in ODS1...
    I am getting the following error....Infoprovide ODS2 still contains request... Delete this first....
    Since ODS2 has many other data alongwith ODS1... If I try deleting request from ODS2,, I need to clean it totally and redo... I dont want to do this...
    Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
    Let me know your suggestions.... Thanks!
    Regards
    Ayyappan.V

    Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
    I dont think you can disconnect the link. just delete the requests originating from ODS1 in ODS2 and you can leave all other requests intact that are from other dataproviders and do a reinit.

  • Sudden Restarts MSI K7n2 DELTA ILSR

    I've had this setup for about a year now.
    Sudden restarts now plague my system, no virus found per NAV 2004, ran processor burn in wizard, SISOFT sandra, on cpu arithmetic and cpu multimedia setting, 100 cycles (no problems) windows memtest ran with no errors via start up disk full cycle of tests.
    Have reloaded video drivers,to no avail, this happens about once a week, any ideas????
    MSI k7n2 delta ILSR Bios version 7.7
    1.5 Gig Micron PC 3200 (512x3) RAM supporting dual channel stock voltage
    mixed bag o ram, crucial, micron technology, and, patriot
    Athlon xp 2500  stock voltage
    SLK 900A heatsink with 80 mm tornado (temps at idle 35-38c) (42 load)
    Creative SB Live
    Nvidia 256  mb asylum video card GE FORCE USR DATA PCI FAX Modem (V92) 5610b
    Hercules 420W PS
    All drivers are up to date and windows update run regularly (Win XP Pro SP2)
     [/COLOR]

    Quote
    Originally posted by scooter787b
    well for one thing the k7n2 series can only support 2 pc3200 dimms,
    are you really sure ?
    my motherboard which is rather old now supports 3 pc3200 dimms.
    norton antivirus is CRAP.
    i stopped using it when i found my harddrive was full of viruses.
    try avg6 for example which is free.

  • Get back the Data mart status in ODS and activate the delta update.

    I got a problem when deleting the requests in ODS.
    actually there is Cube(1st level. it gets loaded from an ODS(2nd level). this gets loaded from 3 ODS'S( 3rd level). we were willing to delete recents requests from all the data tardets and reload from PSA. but while delting in the request in ODS(2nd level), it has displayed a window, showing as follows.
    - the request 132185 already retrived by the data target BP4CLT612.
    -Delta update in BP4CLT612 must be deactivated before deleting the request.
    - Do you want to deactivate the delta update in data target BP4CLT612.
       I have clicked on execute changes in the window. it has removed the data mart status for all the request which i have not deleted.
    in the same it happened inthe 3 ODS's(3rd level).
    I got clear that if we load further data from source system. it will load all the records from starting.
    so to avoid this can any body help me how to reset the Data mart status and activate the delta update.

    Hi Satish,
    U have to make the requests RED in cube and back them out from cube,before u can go for request deletions from the base targets(from which cube gets data).
    Then u have to reset data mart status for the requests in your 'L2 ODS' before u can delete requests from ODS.
    Here I think u tried to delete without resetting data mart status which has upset the delta sequence.
    To correct this..
    To L2 ODS,do an init without data transfer from below 3 ODS's after removing init request from scheduler menu in init infopackage.
    Do similar from L2 ODS to Cube.
    then reconstruct the deleted request in ODS.It will not show the tick mark in ODS.Do delta load from ODS to Cube.
    see below thread..
    Urgentt !!! Help on reloading the data from the ODS to the Cube.
    cheers,
    Vishvesh

  • Cube to cube data transferred ,and delta status

    Hi Gurus
    I need to do Portioning in cube
    I have a cube Zaa_c01 which is updated by two data source ZDS1 and ZDS2 (Delta Update) I copy the Zaa_c01 and I created new cube Zaa_c02, also I transferred the data to that. But it is shoeing in single request in cube, after partion I again reloaded to ZAA_C01 , know I am seeing only single request in a cube.
    Whether I lose delta in this case , or I am missing any step, this activity I done in Development, and need to do in production. 
    Regards
    Shashi

    Hai Shashidhar,
    Partitioning is split the large dimensional cube into smaller cubes.... regarding performance point of view we have to do this partitioning.
    there are two types of partitioning..
    1. Logical Partitioning.
    2.Physical Partitioning
    physical partitioning is done at Database level . and logical partitioning done at Data target level.(EX: Info cube level)
    Cube partitioning with time characteristics 0calmonth Fiscper is physical partitioning.(so, we need at leats one of the above time charecterstics for doing partioning...).
    Logical partitioning is u partition ur cube by year or month that is u divide the cube into different cubes and create a multiprovider on top of it.
    STEPS :
    SELECT YOUR CUBE.. AND DOUBLE CLICK IT..->
    in the menu's select EXTRAS menu--> in that select -->DB PERFORMANCE sub menu..-> in that again select Partitioning sub menu..
    and specify how many partions you want to do...
    but you cube should be contain atleast ocalmonth or phical varient should be there...
    Prerequisites
    You can only partition a dataset using one of the two partitioning criteria ‘calendar month’ (0CALMONTH) or ‘fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoProvider.
    http://help.sap.com/saphelp_nw04s/helpdata/en/8c/131e3b9f10b904e10000000a114084/frameset.htm
    Thanks,
    kiran.

  • SAP Mobile Sales 2.0 delta load issue for Sales Orders

    Hello,
    we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
    Background
    Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
    During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
    Settings and troubleshooting so far
    We don't have any limitations for sales orders in CRM Sales Mobile configuration.
    We've run delta loads for all objects in transaction SDOE_LOAD.
    MAS_CUSTOMIZATION etc seem fine.
    We've re-run initial load for sales orders from CRM.
    In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
    Checked steps suggested in discussion
    SAP CRM 2.0 initial load issue
    Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
    If I change one of those historical sales orders in the backend, it gets sent to the device.
    If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
    To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

    First Doubt i got clarify by my self as we can go with Unwired Runtime option .
    But i still have doubt in :
    2. How can i Modifying the Main Menu for iOS.
    i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
    Same how can i do for iphone/ipad.

  • How to extract data from ORCL GL in "full" and not "delta " with FDM ERPI?

    Hi
    I am using FDM ERPI 11.1.2.1 to extrct data from Oracle eBS 11.
    I can see that FDM ERPI extracts data in "delta mode" using the GL_TRACK_BALANCES_DELTA (FDM adds a row in this table after the 1st load of the period").
    Is it possible to force the "full mode" in order to reload all the data from Oracle GL for each FDM data load?
    Because I don't know why, but I have each month rows which are not imported into FDM.
    thanks in advance for your help
    Fanny

    Hi
    I had see that I have to install the FDM 11.1.2.1.502 patch in order to see this option in my ERPI adapter options.
    I have passed this patch.
    So I have the ERPI-FIN-C1 adaptor.
    I can see a new option (Time Out Value) but no "Load Data" or "Execution mode" option :-(
    Any idea of where the problem come from?
    Fanny

  • Scenarion of Delta Load problem in COPA Extraction

    Please get me the solution for this particular scenario.
    Let us suppose that i created the datasource some 1 year back and running the deltas successfully since then.
    Let us number the requests from 1,2,3... and so on since 1st jan 2009. And let us suppose each request loads
    some 1000 records everyday from ECC to BI.
    Now on 10th august some change was made to ECC( such as change in the User Exit ) that caused the mismatch in number of data records ( loading only 950 records ) since the change was made on 10th August. But I identified the problem on 17th august with request number 160. Let us say those request numbers are 153(10th),154(11th),155(12th),156(13th),157(14th),158(15th),159(16th),160(17th). I fixed the program in ECC on 17th and further the requests from request number 160(17th) are fetching the correct number of data records. Now I need to delete the data in BI for request numbers 153 till 159 since they are not reconciling the data of ECC with BI. Now  we reload the deltas for such requests from ECC to BI. So how do I reload the deltas now in this scenario since ECC system keeps track of the last delta ie.. on 17th august(Req no 160). But how do I Load the deltas from req number 153 to 159 from ECC to BI.
    One proposed solution to this problem was setting the timestamp of COPA to 10th august. But it is not advised to set the timestamp for COPA datasources using the KEB5 transaction in a production system.
    Now in this scenario how do I load the request numbers 153 to 159 from ECC to Bi to fetch the correct data records for that period. Please propose a solution for this problem ASAP. U can also call me back whenever u need.
    Thanks in advance

    As stated in a previous post...
    How you choose to do this can be summed up by the question: Does the target for this data have cumulative or non-cumulative Key Figures?
    If you are doing an overwrite to the Key Figures, you could just execute a Full Repair InfoPackage that extracts the data for the days that you found inconsistencies instead of attempting to change the timestamp in KEB5 on the source ECC environment.
    However, if you're target has cumulative Key Figures you're left with very few options (a couple of them are time-consuming):
    1) Changing the timestamp in KEB5, if your plug-in is PI 2003.1 or older. Newer versions of the plug-in do not allow the changing of the timestamp as was pointed out by Ferruccio earlier.
    2) Deleting the keys in the target InfoProvider for those records that you extract in a Full Repair extract.
    3) Delete all data in BW for COPA and start from the beginning. This may be your best bet for cleaning up the issues in this scenario.

  • How to reprocess delta records during subsequent update of data targets

    Hi,
    I have an ODS which sends in delta records to a cube above it. Now there is a data load, happening monthy from a flat file, which was successful upto the ODS, but failed in the cube due to one invalid record. How do I reprocess this data load after correction of the invalid records in the source flat file?
    The method I currently follow is to delete the failed request from the cube and then do a selective delete of records from the ODS and then reload the last data after correction.
    Is there a better way to just reprocess the last load from the flat file?
    Thanks & regards,
    Nikhil

    Hi Bhanu,
    Thanks for the response. I will explain a bit more in detail. Suppose there are 5 records coming in from the flat file - now 4 of those records are correct and one has invalid data.
    All 5 records get loaded to the ODS successfully but in the cube we have a function module which works on the data and aborts the entire data package if it finds even one invalid record. So nothing gets loaded into the cube at all.
    Now if we correct the one invalid record and then reload into the ODS - it will just send this corrected record over to the cube and we will miss out on the other 4 records which were originally correct since the ODS does not detect them as changed.
    If we delete the request from the ODS (rather than doing the selective delete) then it disables the delta in the ODS asnd we have to reinitialise everything - which we cannot afford to do in a production environment.
    Hope the problem is a bit more clear now.
    I was looking for some way to just resend all the five records - with the one corrected record to the cube without going through this selective delete process sinc eits too cumbersome and we run the risk of messing up with actual data ina  production environment.
    Thanks for the help,
    regards,
    Nikhil

Maybe you are looking for