Master Data load fails because of Duplicate Records

Hi BW Experts,
I am loading historical data for a info-object using flexible update, first i tried to delete the data but it was not possible as it is being used in infocubes and ODS, As i am doing the rework of that cubes, ODS so i have to reload the whole data again. Anyway without deleting i tried loading the data in the info-object but it has thrown error that dulicate records found, I tried again then it has thrown an error ALEREMOTE has locked the object or lock not set for the object.
Please suggest me what to do in these scenario.
Please consider it as urgent.
Thanks in advance.
Sunil Morwal

Sunil,
First unlock the objects.go to SM12 give ALEREMOTE user name then list...select the request and delete.
Load the data from PSA....
OR reload... rememeber you will have one option at infopackage level in processing tab "<b>Ignore duplicate records"</b>.
Let me know the status.
Thanks
Ram
"BW is Everywhere"
Message was edited by: Ram

Similar Messages

  • Master data load failed due to duplicate records .

    hello friends ,
    need some help .
    I am loading the master data from soruce sys , and it is throwing error of duplicate 56 records.
    I repeated the step , but found the same error once again .
    i could not find out the duplicate record , as thr are more than 24000 records , and in this 56 are duplicate . and this duplicate also looks like same.
    when i click on error records , it is showing me the below procedure .
    maintain the attribute in Psa SCREEN .
    I could not find the duplicate records , could you please let me know how can i maintain this .
    Regards

    Hi ,
    Reload the masterdata by cheking ignoreduplicate records check box.since the master data has overwriting capability the duplicate records will be overwritten
    cheers,
    Swapna.G

  • Data Load Fails due to duplicate records from the PSA

    Hi,
    I have loaded the Master Data Twice in to the PSA.  Then, I created the DTP to load the data from the PSA to the InfoProvider.  The data load is failing with an error "duplicate key/records found".
    Is there any setting that I can configure by which even though I have duplicate records in PSA, I can be successfully able to load only one set of data (without duplicates) in to the InfoProvider?
    How can I set up the process chains to do so?
    Your answer to the above two questions is appreciated.
    Thanks,

    Hi Sesh,
    There are 2 places where the DTP checks for duplicates.
    In the first, it checks previous error stacks. If the records you are loading are still contained in the error stack of a previous DTP run, it will throw the error at this stage. In this case you will first have to clean up the previous error stack.
    The second stage will clean up duplicates  across datapackeages, provided the option is set in your datasource. But you should note that this will not solve the problem if you have duplicates in the same datapackage. In that case you can do the filtering yourself in the start routine of your transformation.
    Hope this helps,
    Pieter

  • Master data infoobject can't handle duplicate records after SP10

    Hi
    I am trying to load master data which happened to contain duplicate records from the source system.  In the DTP of the master data infoobject, I have ticked the 'Handle Duplicate Record Keys' checkbox.  After executing this DTP, the duplicate master data records were trapped in the Error Stack.  I am expecting overwriting of the duplicate master data to take place instead.  I understand that this error was fixed in Note 954661 - Updating master data texts when error in data package which is from SP9.  After applying Support Pack 10, the master data infoobject just can't handle records with duplicate keys.
    Please let me know if you manage to fix this problem.
    Many thanks,
    Anthony

    Found a fix for this problem.  Just applied this OSS note  Note 986196 - Error during duplicate record handling of master data texts.

  • Material Master Data load failed

    Hi All,
    I am loading material master data. I have around 8055 records in R/3. The load has failed with an error "Non-updated Idocs found in Business Information Warehouse" and asking me to process the IDocs manually. I have checked in WE05 for the IDocs and found 3 Idocs with status 64(IDoc ready to be transferred to application).
    But when I checked in the manage screen of the 0MATERIAL I could find the Transfered and Updated records as 8055. I have even checked the data in 0MATERIAL and found that all the data(8055 records) has already been uploaded.
    Why is it still showing an error(load failed) even when all the data has been uploaded? What should I do now?
    Best Regards,
    Nene.

    hi Nene/Sankar,
    for material text no language please check Note 546346 - Material texts: no selection on languages
    and for why idocs problem, check e.g Note 561880 - Requests hang because IDocs are not processed, Note 555229 - IDocs hang in status 64 for tRFC with immediate processing.
    hope this helps.
    Note 546346 - Material texts: no selection on languages
    Summary
    Symptom
    When loading material texts from R/3 into the Business Information Warehouse, you cannot select languages.
    Other terms
    DataSource, 0MATERIAL_TEXT, InfoSource, InfoObject, 0MATERIAL, SPRAS, LANGU, 0LANGU, MAT_BW, extraction, selection field, delta extraction, ALE, delta, change pointer
    Reason and Prerequisites
    As of PI/PI-A 2001_2 Support Package 6, the selection option for the 'SPRAS' field in the OLTP system was undone in the 0MATERIAL_TEXT DataSource. (Refer here to note 505952).
    Solution
    As of PI/PI-A 2002_1 Support Package 4, the 'SPRAS' field is provided for selection again with the 0MATERIAL_TEXT DataSource in the OLTP system. When loading the material texts from BW, the language is still not provided for selection in the scheduler, instead all languages of the language vector in BW are implicitly requested from the source system. However, during the delta update in the source system, the change pointers for all languages in the source system are now set to processed, regardless of whether the language was requested by BW or not.
    Import
    Support Package 4 for PI/PI-A 2002_1_31I - PI/PI-A 2002_1_45B
    Support Package 4 for PI 2002_1_46B - PI 2002_1_46C
    Support Package 3 for PI 2002_1_470
    In transaction RSA5, copy the D version of the 0MATERIAL_TEXT DataSource to the A version.
    Then replicate the DataSources for 0MATERIAL in the BW system. The 'SPRAS' field is then flagged again as a selection field in the transfer structure of the 0MATERIAL InfoSource. The transfer rules remain unchanged. Activate the transfer rules and perform a delta initialization again.
    Note 561880 - Requests hang because IDocs are not processed
    Symptom
    Data extraction in a BW or SEM BW system from an external OLTP System (such as R/3) or an internal (via DataMart) OLTP System hangs with the 'Yellow' status in the load monitor.
    After a timeout, the request status finally switches to 'Red'.
    Information IDocs with the status '64' are displayed in the 'Detail' tab.
    Other terms
    IDoc, tRFC, ALE, status 64
    Reason and Prerequisites
    Status information on load requests is transferred in the form of IDocs.
    IDocs are processed in the BW ALE model using tRFC in online work processes (DIA).
    IDoc types for BW (RSINFO, RSRQST, RSSEND) are processed immediately.
    If no free online work process is available, the IDocs remain and must then be restarted to transfer the request information.With the conversion to asynchronous processing, it can often happen that no DIA is available for tRFC for a short period of time (see note 535172).
    The IDoc status 64 can be caused by other factors such as a rollback in the application updating the IDocs. See the relevant notes.
    Furthermore, you can also display these IDocs after the solution mentioned below, however, this is only intended as information.
    You must therefore analyze the status text.
    Solution
    We recommend asynchronous processing for Business Warehouse.
    To do this, you need the corrections from note 535172 as well as note 555229 or the relevant Support Packages.
    The "BATCHJOB" entry in the TEDEF table mentioned in note 555229 is generated automatically in the BW system when you import Support Package 08 for BW 3.0B (Support Package 2 for 3.1 Content).For other releases and Support Package levels, you must manually implement the entry via transaction SE16.
    Depending on the Basis Support Package imported, you may also have to implement the source code corrections from note 555229.
    The following basic recommendations apply in avoiding bottlenecks in the dialog processing and checking of IDocs for BW:
    1. Make sure there is always sufficient DIA, that is, at least 1 DIA more than all other work processes altogether, for example, 8 DIA for a total of 15 work processes (see also note 74141).
       TIP: 2 UPD process are sufficient in BW, BW does not need any UP2.
    2. Unprocessed Info IDocs should be processed manually within the request in BW;in the 'Detail' tab, you can start each IDoc again by selecting 'Update manually' (right mouse button).
    3. Use BD87 to check the system daily (or whenever a problem arises) for IDocs that have not yet been processed and reactivate if necessary.
    However, make sure beforehand that these IDocs can actually be assigned to the current status of requests.
       TIP: Also check transaction SM58 for problematic tRFC entries.
    IMPORTANT: Notes 535172, 555229 and the above recommendations are relevant (unless otherwise specified) both for BW and for SAP source systems.

  • Time dependant Master data load fail (Invalid time interval)

    Hi,
    I have IO 0HRPOSITION which is time dependant master data.
    When I load master data I have maintained from date 01.03.2007 to end date 01.12.999 in scheduler.
    But there are some positions records in HR system which have from date less than 01.03.2007 and because of that master data load is failing everyday.
    How I can load only those records which fall in-between from date 01.03.2007 to end date 01.12.999???
    Thanks
    Pramod

    Hi Pramod,
    I think you can put a selection in the Infopackage.
    Thanks

  • Master data load fail

    Hi Gurus,
       My master data load is failing because of this error.
    Record 20 :0CAT_GROUP : Data record 20 ('000200000012 '): Version 'D $$OSS001 ' is not valid
    I went back to PSA and found out that I have 6 error records with values $$OSS001 .
    0CAT_GROUP is a attribute of master data object
    I checked in the master data extractors.These values are coming from ECC .
    Can some one tell me how to get rid of these values and reload to Masterdata without errors.i am using BW3.5
    Anyhelp would be appreciated.
    Neo

    You probably have to make appropriate change in settings in RSKC to allow certain characters. Otherwise the best way will be stop these at source, if they are really 'bad' data.
    You could also visit the link below:
    /people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
    alternatively, you can write routine in transfer rules/ transformation by using
    CALL FUNCTION 'RSKC_ALLOWED_CHAR_GET'

  • While loading master data to infoobject Load failed due to Duplicate record

    Hi Experts,
    While loading master data to the infoobject load failed .
    The error it is showing is 24 Duplicate record found. 23 recordings used in table.
    Pls help me to solve this issue
    Thanks in Advance.
    Regards,
    Gopal.

    In infopackage settings u will find a checkbox for 'delete duplicate records'.
    I think it appears beside the radio button for 'To PSA',and also tick checkbox for 'subsequent update to data targets'.
    This will remove the duplicate records(if any) from the PSA before they are processed further by transfer and update rules.
    Use this and reload master data.
    cheers,
    Vishvesh

  • Master data load failed

    Hi Experts,
    One of my master data full load failed, see the below erro message in status tab,
    Incorrect data records - error requests (total status RED)
    Diagnosis
    Data records were recognized as incorrect.
    System response
    The valid records were updated in the data target.
    The request was marked as incorrect so that the data that was already updated cannot be used in reporting.
    The incorrect records were not written in the data targets but were posted retroactively under a new request number in the PSA.
    Procedure
    Check the data in the error requests, correct the errors and post the error requests. Then set this request manually to green.
    can any one please give me solution.
    Thanks
    David

    HI,
    I am loading the data from application server,  i dont have R/3 for this load. and the below message is showing in status tab;
    Request still running
    Diagnosis
    No errors could be found. The current process has probably not finished yet.
    System response
    The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
    and/or
    the maximum wait time for this request has not yet run out
    and/or
    the batch job in the source system has not yet ended.
    Current status
    Thanks
    David

  • Error-Master Data Load Fail

    Hi Friends,
    While loading master data from Process Chain, the load has been failed by having specail Characteristic in it. W e have edited that characteristic record  in SAP R/3 system.
    What we have to do now....... Should i have to Repeat the load Process in process Chain For that Object or should i do Manual Upadate from RSMO. There is another 2 process has to run below that master data object.
    *************points Are Assured********
    Regards
    Revathi

    Hi Revathi.....
    Is ur load is through PSA?......look U hav edited in the source system.........not in BI side.......if the load is through PSA also.........records r still erroneous in PSA.......
    Since u hav already edited in the source system............again editing in PSA is repeating the same job twice.........it is of no use.........
    Since it is master data.................no need to delete the request from the target............actually data target means Infocube or ODS.........Master data is not a Data target.........u will not find the data target icon in the infopackage monitor or the data target tab in the infopackage Scheduler.........
    Just make the QM status red and repeat the load in the PC............if it is a full load making the QM status red is not mandatory...............but for Delta..........it is mandatory...........since only then Init pointer will set back...........and the System ask u for Repeat delta.......
    But another point...........Master data generally does'nt support Repeat delta...........if u try to do Repeat delta.........load will again fail with Update mode R.........then u hav to do re-init...........ie......
    1)delete init flag
    2)Do init with data transfer
    3)then delta.....
    Regards,
    Debjani......

  • Duplicate records during master data loading.

    hello guys,
    I am reading one blog where the blogger wrote about 'Various issues in a BW Production project'.....I came across one issue which I couldnot understand...
    Data loading failed due to Duplicate records during master data loading.......
    Why do this error occur?How can we rectify this in a production environment?
    Thanks and Regards,
    S

    Hi SChandx200 ,
          May I ask where you get "Various issues in a BW production project"?
    Many Thanks,

  • Master Data Loads

    Hello,
    Some of my master data loads failed. It gives me following error:
    Lock NOT set for: Loading master data attributes
    Attributes for characteristic "  " are locked by a terminated change run
    what is this lock? how to rectify the same? what can be cause of this problem.
    Regards,

    Hi Abhijit,
    You can go to RS12 and see the status of the locks of the master data. You can even delete the locks there though not advisable. The chances are that attr/hier change might have been running for some info-obj which was causing the problem.
    You could now try 2 things:
    1. Try the load again. OR
    2. Delete the locks and then try the load.
    Bye
    Dinesh.

  • Master Data loading got failed: error "Update mode R is not supported by th

    Hello Experts,
    I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
    For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
    "Update mode R is not supported by the extraction API"
    Can anyone tell me what is that error for? how to resolve this issue?
    Regards,
    Nirav

    Hi
    Update mode R error will come in the below case
    You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
    This time the load will fail with update mode R.
    As repeat delta is not supported.
    So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
    example your fiorst delta failed with replication issue.
    only replicating and repeaing will not solve the update mode R.
    you will have to do both replication of the data source and re-int for the update mode R.
    One more thing I would like to add is.
    If the the delat which failed with error the first time(not update mode R), then
    you have to do init with data transfer
    if it failed without picking any records,
    then do init without data transfer.
    Hope this helps
    Regards
    Shilpa
    Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

  • Bi admin process chains-  content master data load has failed

    Hi Experts,
    i worked with Bi Admin cockpit set-up, all  the things are going fine
    but Content Master data load (Attribute)has failed and i got the errors like
    1)data records for package 1 selected in PSA-2 errors
    2)Error 4 in the update
    can anyone suggest me how can i sove the issue
    regards
    Mrudula

    Hi
    yes, i got 2 errors in Psa
    when i click the 1st error i got like
    Data record 10023 & with the key
    'EBTCLNT100ACGRAZ_BWRPRT_USR_FBW_Ptest0001 &' is invalid in value
    'EBTCLNT100ACGRAZ_BWRPRT_USR_FBW_attribute/characteristic 0TCTBWOBJECT &.
    And i it gave the procedure as
    if this message appears during a data load, maintain the attribute in the PSA maintenance screens. if this message appears in the master data maintenance screens, leave the transaction and call it again. this allows you to maintain your master data.
    And when i click the 2nd error
    it has showed the data record as 10024 and remaing explanation is same like 1st one
    in this i am not getting, how to proceed the solution.
    plz help me anyone
    Thanks and regards
    Mrudula
    Edited by: mrudularajesh on Jul 1, 2009 7:39 AM

  • Master data load for 0COSTCENTER (Cost Center) failing

    Hi Experts
    I have a master data load for 0COSTCENTER (Cost Center). The Load has started failing from a couple of days at DTP.
    (R) Filter Out New Records with the Same Key
          (G) Starting Processing...
          (R) Dump: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
    I am unable to understand the reason for this failure. I tried loading the data 1 costcenter at a time it is still failing so i doubt if its a internal table storage issue as suggested by the dump.
    Could you help me on this one please.
    Regards
    Akshay Chonkar

    Thanks All
    I have got the issue resolved
    The Error Stack for the DTP had accumulated so many entries that it was unable to process further.
    So i deleted the entries in Error Stack usin SE14. Then again executed my DTP.
    Everything is fine now thanks for your help.
    Regards
    Akshay Chonkar

Maybe you are looking for