Record 3 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key i

Hi
when i am loading the data i got the error " Record 3 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key is initial " .
lot of records are there like this.
Can you put a light on this.
Reward points .
Thx
siva

Even I am facing the same problem. Can any one help us out. I have Master data load, but as Info provider loading. I have added 0LANGU in attributes info source and in my flat file, i have 'E' as the value for 0LANGU. When I load attributes data, it gets succesfull along with 'EN' for 0LANGU (Conversion). In my text info source I have Key Number and Medium description fields. When I load Text file, it gives me the error ' ' Record 1 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key is initial' and its for all records in the text file.
Edited by: venu Avula on Jun 16, 2008 9:52 PM

Similar Messages

Load Same Text data for all language key

Hello Everyone,
I have a datasource with Material and Desc fields but no language key.I need to load the same desc into my infoobject for all the languages i am maintaining (EN/DE/IT/FR/PL). Is this possible?
Thanks,
Ajay.D

Hi Ajay,
you can load same description for all the languages by maintaining constant language value at Transfer rules/ Transformations.
but here you need to change the constant value for each language.
Ex, if you are loading for EN, maintain language as Constant "EN".
and then for DE, maintain language as Constant "DE".
but this is repetitive process, if new materials are added then need to load again.
Best Regards.
Edited by: Daya Sagar on Sep 16, 2009 11:16 AM

Info Package Selection Language key is not diplaying while this is checked

Hi
i am facing an issue in BI 7.0
in Info Package Data Selection Tab "Language key field" is not diplaying while this field is checked as a Selection option in R3 Data source.
How can i put Language key field in Info package data selection
Regards
Atul
Edited by: AtulMohan Mishra on Apr 28, 2011 11:50 AM
Edited by: AtulMohan Mishra on Apr 28, 2011 11:50 AM

Hi,
Please see OSS note 1033537 .Even if langauge selection is available in infopackage it wont work .Tthe only way to restrict a particular language is in DTP or in transformation routine. Infopackage will extract all the language that is installed in BW system and you have to place your restriction in DTP or transformation.
Regards,
Raghavendra.
Edited by: Raghavendra Padmanaban on Apr 28, 2011 9:18 AM

Master data records with one key

Hello All,
I have scenario that I need to load the master data records with one key.
For ex--
Cluster            Dcode               version
5000                 DC1                  2008
5000                 DC1                  2008
5001                  DC1                  2009
Could you please let me know possible ways.
Thanks

In your case if Cluster is the key then the underlying attributes data will be overwritten when the same cluster key comes.
as per you example data finally it loads only two records in to the target, since first two records key is same.
Hope this helps.
Veerendra.

Unique data record means you can't update a record from ECC with same key.

Unique data record means you can't update a record from ECC with same key fileds right?
Details: For example i have two requests Req1 and Req2 in DSO with unique data record setting checked. on day one Req1 has a filed quantity with value 10 in Active data table. On day two Req1 can not be overwitten from ECC with Req2 with the same key fields but different value 20 in the filed quantity because of the Unique data record settings. finally the delta load fails from ECC going to DSO because of this setting. is it right?
I think we can only use unique record setting going from DSO to cube right?
Please give me a simple scenario in which we can use this setting.
I already search the threads and will assign points only to valuable information.
Thanks in advance.
York

Hi Les,
Unique Data Records:
With the Unique Data Records indicator, you determine whether only unique data records are to be updated to the ODS object. This means that you cannot load a data record into the ODS object the key combination for which already exists in the system otherwise a termination occurs. Only use this setting when you are sure that only unique data records are to be loaded into the ODS object (for example, single documents). A typical application of this is in the loading of mass data. It improves the load performance.
Hope it Helps
Srini

DTP Error: Duplicate data record detected

Hi experts,
I have a problem with loading data from DataSource to standart DSO.
In DS there are master data attr. which have a key containing id_field.
In End routine I make some operations which multiple lines in result package and fill new date field - defined in DSO ( and also in result_package definition )
I.E.
Result_package before End routine:
__ Id_field ____ attra1 ____ attr_b ...___   attr_x ____ date_field
   ____1________ a1______ b1_________ x1
   ____2________ a2______ b2_________ x2
Result_package after End routine:
__ Id_field ____ attra1 ____ attr_b ..___   attr_x ____ date_field
   ____1________ a1______ b1_________ x1______d1
   ____2________ a1______ b1_________ x1______d2
   ____3________ a2______ b2_________ x2______d1
   ____4________ a2______ b2_________ x2______d2
The date_field (date type) is in a key fields in DSO
When I execute DTP I have an error in section Update to DataStore Object: "Duplicate data record detected "
"During loading, there was a key violation. You tried to save more than one data record with the same semantic key."
As I know the result_package key contains all fields except fields type i, p, f.
In simulate mode (debuging) everything is correct and the status is green.
In DSO I have uncheched checkbox "Unique Data Records"
Any ideas?
Thanks in advance.
MG

Hi,
      In the end routine, try giving
DELETE ADJACENT DUPLICATES FROM RESULT_PACKAGE COMPARING XXX YYY.
Here XXX and YYY are keys so that you can eliminate the extra duplicate record.
Or you can even try giving
    SORT itab_XXX BY field1 field2 field3 ASCENDING.
    DELETE ADJACENT DUPLICATES FROM itab_XXX COMPARING field1 field2 field3.
this can be given before you loop your internal table (in case you are using internal table and loops) itab_xxx is the internal table.
field1, field2 and field 3 may vary depending on your requirement.
By using the above lines, you can get rid of duplicates coming through the end routine.
Regards
Sunil
Edited by: Sunny84 on Aug 7, 2009 1:13 PM

How to avoid 'duplicate data record' error message when loading master data

Dear Experts
We have a custom extractor on table CSKS called ZCOSTCENTER_ATTR. The settings of this datasource are the same as the settings of 0COSTCENTER_ATTR. The problem is that when loading to BW it seems that validity (DATEFROM and DATETO) is not taken into account. If there is a cost center with several entries having different validity, I get this duplicate data record error. There is no error when loading 0COSTCENTER_ATTR.
Enhancing 0COSTCENTER_ATTR to have one datasource instead of two is not an option.
I know that you can set ignore duplicates in the infopackage, but that is not a nice solution. 0COSTCENTER_ATTR can run without this!
Is there a trick you know to tell the system that the date fields are also part of the key??
Thank you for your help
Peter

Alessandro - ZCOSTCENTER_ATTR is loading 0COSTCENTER, just like 0COSTCENTER_ATTR.
Siggi - I don't have the error message described in the note.
"There are duplicates of the data record 2 & with the key 'NO010000122077 &' for characteristic 0COSTCENTER &."
In PSA the records are marked red with the same message (MSG no 191).
As you see the key does not contain the date when the record is valid. How do I add it? How is it working for 0COSTCENTER_ATTR with the same records? Is it done on the R/3 or on the BW side?
Thanks
Peter

I can record midi data from my Mason & Hamlin Piano Disc Pro Record through my MOTU Traveller into Logic but Logic won't send midi data out to the MOTU Traveller to the Piano Disc player

Hello All,
I can record midi data from my Mason & Hamlin Piano Disc Pro Record through my MOTU Traveller into Logic Pro 9.1.8 but Logic won't send the midi data back out to the MOTU Traveller and thus to the Piano Disc player. I got it to playback one time but have no idea how and when it did it was looping or something because the velocity was way high coming back in and the damper pedal was slamming down. When I play a key on the piano the midi "in" light on the Traveller lights up. When I play the track back on my computer no lights blink on the Traveller and when I did the apple midi studio test in utilities when I play a key I get the confirmation signal noise and the Traveller blinks when I click on the down arrow of the Traveller in the Apple midi studio test the midi out light on the traveller never lights and the signal light on the piano does not blink either. No outbound signal at all...
I have messed with every possible parameter I can find and and have had help from one of Piano Disc's premier editors but no luck. The piano was prepped for me on Logic so it would work with my studio. I'm positive it's my fault and I'm overlooking something really simple and stupid but what!??!
Somebody please help. Thank you all in advance for ANY ideas you might have!

Blues Piano,
I'm not sure if this will be a help or not. I'm so Logic Pro wet behind the ears that I make newbies look experienced. However, I'm not expecting many on the Apple support forums have a PianoDisc system, much less one with the new optical record strip. While I don't have any record strip on my PianoDisc, I do have a PianoDisc iQ that's only a month old. I've been playing converted paper scrolls from hundred year old player pianos through it via the MIDI in port of the PianoDisc CPU. I've found I have to open the MIDI file in Logic Pro (10.0.4) then go to <Track><New External MIDI Track> then copy the existing track to that new external track. Only then can I see in the Track inspector (defaults left side of screen with the Icon for the instrument) the "Port" parameter. Then I can select my external MIDI device in that Port selector.
I've also encountered problems with the PianoDisc not using enough force on the notes or using too much force. To get around this problem, until I understand Logic better, I've been setting minimum and maximum volicities. To do that I right click on the track and select "Select All." Then I right click again and select "MIDI" then "MIDI Transform" then "Velocity Limiter." In the resulting pop up window in the center is a drop down and you can play with the velocity from "MIN" to "MAX" along with "ADD" "SUBTRACT" etc.
I hope this helps. I envy you your Mason & Hamlin. If you need more help on this just email me at pfleischmann at mac dot com.

How to get the Data Record Number in BI 7.0?

Hi All,
In our requirement we need to load the Data Record Number in the DSO. I got the Request ID and Data Packet Number but not the Data Record Number.
Does anyone has any idea?

Hi......
When the data is activated in DSO, it is written to the table of active data, where it is then available for reporting. Requests are sorted by the key of the DataStore object, request ID, data package ID, or data record number.
You just load the data to the DSO.....and activate it.......it will autometically get generated.......You cannot load it from one DSO to other beacuse in this case Change log table is used........and this filed is in active table..........I think you need this fir reporting purpose.....so load it and activate the DSO......then it will be available in your active table for reporting.........because reporting is done on active table.......
Check this link :
http://help.sap.com/saphelp_nw04s/helpdata/en/a9/49453cabf4ef6fe10000000a114084/frameset.htm
Hope this helps you....
Regards,
Debjani....
Edited by: Debjani Mukherjee on Sep 16, 2008 5:22 PM
Edited by: Debjani Mukherjee on Sep 16, 2008 5:25 PM

Identifing duplicate master data records using the MDM Import Manager

hi all
I read the Topis "How to identify duplicate master data records using the MDM Import Manager</b>"
i tried to create import maps and to set rules. but when i import them it creates the new vendor records for each rule with rest of the fields blank.
when i import vendor data all the three fields i.e Match rate , match type and match group are blank.
My Question is :
I am getting vendor data from SAP R/3.
In which source (in lookup xml file or data xml file) do i have to include these above three fields and how all the rules will be reflected in repository?

Hi Sheetal
Here we go when do you Import any data (vendor master) please follow the following steps;
1. First of all apply the map to the source data
2. In the Match Record tab there are 3 possiblities
   a.[Remote Key] : Checks the current source rec with
     repository along with all the fields - This is
     default
   b.Remove [Remote key] - by double click the same; and
     choose any single fields like Vendor Number or
     name - Then the current record will be matched
     with the repository based on the field.
   c.Instead of single field you can choose combination
     also.
3. Based on the Match results, match class will be set
   automatically;
   a. None
   b. Single
   c. Multiple
4. Then Match Type
    a.Exact-All the individual value matches are Equal.
    b.Partial-At least one value match is Equal and at least one Undefined; no value matches are Not Equal.
    c.Conflict-At least one value match is Equal and at least one value match is Not Equal.
5. then chek the Import status and Execute the import.
Hope this helps you.
cheers
Alexander
Note: Pls dont forget reward points.

Loading ODS - Data record exists in duplicate within loaded data

BI Experts,
I am attemping to load an ODS with the Unique Data Records flag turned ON. The flat file I am loading is a crosswalk with four fields, the first 3 fields are being used as Key Fields in order to make the records unique. I have had this issue before, but gave up in frustration and added an ascending number count field so simply create a unique key. This time I would like to solve the problem if possible.
The errors come back referring to two data rows that are duplicate:
Data record 1 - Request / Data package / Data record: REQU_4CNUD93Q3RCC80XFBG2CZXJ0T/000003/ 339
Data record 2 - Request / data package / data record: REQU_4CNUD93Q3RCC80XFBG2CZXJ0T/000003/ 338
And below here are the two records that the error message refers to:
3     338     3902301480     19C*     *     J1JD
3     339     3902301510     19C*     *     J1Q5
As you can see, the combination of my three Key Fields should not be creating a duplicate. (3902301480, 19C(asterisk) , (asterisk))   and (3902301510, 19C(asterisk) , (asterisk)) I replaced the *'s because they turn bold!
Is there something off with the numbering of the data records? Am I looking in the wrong place? I have examined my flat file and can not find duplicates and the records that BW say are duplicates are not, I am really having a hard time with this - any and all help greatly appreciated!!!

Thank you for the response Sabuj....
I was about to answer your questions but I wanted to try one more thing, and it actually worked. I simply moved the MOST unique Key Field to the TOP of my Key Field list. It was at the bottom before.
FYI for other people with this issue -
Apparantly the ORDER of your Key Fields is important when trying to avoid creating duplicate records.
I am using four data fields, and was using three data fields as the Key Fields. Any combination of all three would NOT have a duplicate, however when BW finds that the first two key fields match, sometimes it apparantly doesn't care about the third one which would make the row unique. By simply changing the order of my Key Fields I was able to stop getting the duplicate row errors...
Lesson - If you KNOW that your records are unique, and you are STILL getting errors for duplicates, try changing the ORDER of your key fields.

Technical data records? What's this???

Hello,
we are on BI7.0.
I have master data for customer. One customer has as a key 0101010101.
When I want to maintain this record it is only possible when the check-box "Display technical data records" is activated.
Questions
Why?
What is this for a checkbox? The online-help does not bring light on that topic. Any idea?

Hi,
Let me take you back to the context help. It says:
Some SAP BW components generate artificial characteristic values with corresponding SIDs. These characteristic values do not have master data or texts but only a SID and are called technical master data values.
If a characteristic does not have attributes and the texts of the characteristic are deleted, you have to set the indicator for subsequent maintenance (new entry) of texts.
The second paragraph makes it pretty clear. If just the key characteristic value exists, and the master data table does not contain any attributes and there is no text maintained, then the characterisitc value becomes a technical master data value and will only be called up for maintenance if this flag is checked.
Why don't you try and maintain this customer's text and save. Now run master data maintenance with this flag unchecked; you should be able to see it.
Cheers...

"Display technical data records"????

Hello,
we are on BI7.0.
I have master data for customer. One customer has as a key 0101010101.
When I want to maintain this record it is only possible when the check-box "Display technical data records" is activated.
Questions
Why?
What is this for a checkbox? The online-help does not bring light on that topic. Any idea?

solved. See documentation from SAP

Duplicate Data records occured while loading

Hai Experts
While loading Duplicate Data records occured earlier there was less no of records i used to delete the duplicate records in background in PSA. Now i am having more records which i am confusing which to delete and which not to delete. Since it is a flatfile loading with delta update mode. and when i went to infopackage it is showing update subsequently in data target in hide position and i went through process chainipdisplay variant---- and made status red--- selected updated subsequently in data target
ignore duplicate data records. and i want to trigger the subsequent process. if we go through process monitor i can rspc_process_finish. I i go display variant then what is the process.......................... is there any function module.

Select the check box " Handle duplicate records key" in DTP on update tab.
Thanks....
Shambhu

Error Conversion foreign curr. (Data Records were recognised as incorrect)

hi all
I am working on SAP BW 3.5 version on Production Server
I am fetching Data from SAP R/3 system to BW 3.5 systems for SD Order and Billing
Data is correctly Loaded for SD Orders and when I am trying to Load Data for SD Billing,I am got the following Error
Data Records were recognised as incorrect, butStatus is Green
Error Request is;
Error Conversion foreign curr.- Local currency ; 0110005292 20050425 GBP - INR
Please let me know on this Error
thanks in Advance

Check currency conversion key in RRC3 transaction.The key should have defined in such a way it translates any currency

Record 3 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key i

Similar Messages

Maybe you are looking for