Duplicate member created

Hello,
I get the following error message when I execute my query with the query designer. Curious is, when I execute the query and don´t choose a value of the variable "debitor" I get a list of all debitors and other characteristics, keyfigures but when I choose one debitor of the variable who was also in the list before I get the error message. ZCUSTFI1 is the name of the InfoObject, where I get my master data.
Have somebody an answer herone?
The error:
Die erste Ausnahme, die dazu geführt hat, dass der Request fehlgeschlagen ist, war:
Ungültiger Programmzustand: Duplicate member created: ZCUSTFI1: 070210021002100000100175, Sids: 3863513 & 3715343
com.sap.ip.bi.bics.exceptions.BicsProgrammErrorException: Invalid program status: Duplicate member created: ZCUSTFI1: 070210021002100000100175, Sids: 3863513 & 3715343
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.addMember(ProviderInfoObject.java:310)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.addMember(ProviderInfoObject.java:594)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.addMember(ProviderInfoObject.java:535)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.getMembers(ProviderInfoObject.java:964)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.getMembers(ProviderInfoObject.java:912)
Thanks.
Michael

English :
The first exception, which led to it that the Request failed, was: Invalid program mode: Duplicate more member created: ZCUSTFI1: 070210021002100000100175, Sids: 3863513 & 3715343

Similar Messages

Duplicate member names 9.3.1

The planning documentation seems to suggest that duplicate member names can occur in Planning 9.3.1 although I have seen a post ~(Nov 2007) on here that states that this won't be available until 9.5.
Is this still the case?
If not, is there any documentation showing how this can be achieved from within bpma/planning? It all seems to suggest it is done in Essbase but that leaves me in a chicken and egg situation as I can't deploy it to essbase with duplicates.
Cheers

Ok guys, back on this issue.
If I wanted to model the following hierarchy in Planning, given the absence of the duplicate members facility, how would you go about it?
Group - Product
Cars - Wheel
Cars - Seat
Cars - Window
Vans - Wheel
Vans - Seat
etc
where all products are not shared and must be able to accept individual values. This is a simple example so creating another dimension isn't an option.
This is a very real requirement and I'm wondering whether I'm missing something very obvious here. Are we really limited to planning hierarchies where duplicate product names are not used? Am I going about this in the wrong way?
Any guidance on how I should be solving this problem greatly appreciated.
Regards

Duplicate member name

Hi Everyone,
My database currently set to Allow duplicate names None. Now I want to enable it. (Its a planning application 9.3.1).
What are the impacts in doing so. Does duplicate members Store data?? Or are they like Shared members????
Can I create another hierarchy under a duplicate member??? Any inputs would be appreaciated.
Regards,
Anil

Agree with both posts.
Don't do it for the reasons Glenn stated and I agree you wouldn't be able to actually create any duplicates anyway for the other stated reasons.
but don't think that means it will not have an impact. Enabling duplicate members will impact other areas such as your ability to partition (you cannot create a partition between a duplicate enabled and a non duplicate enabled database.
So you will receive no benefits and face potential consequences.

Duplicate Appraisal Created

hi,
In this scenario, when I create an appraisal for a person thru the report phap_admin_pa, am getting two appraisals created for a person. Out of the two appraisals one is the old manager and other is the new manager. but the old manager is already terminated but still appraisal is created , how to solve this.
Kindly help.
Regards,
Jenni
Edited by: Indumathy Ravindran on Oct 3, 2008 8:08 AM

English :
The first exception, which led to it that the Request failed, was: Invalid program mode: Duplicate more member created: ZCUSTFI1: 070210021002100000100175, Sids: 3863513 & 3715343

Duplicate Messages created on target with Multimapping(No BPM)

Hi
I am working on PI7.1 .
My sceniro
IDOC to JMS using message split
Receiving IDOC with Header and Items, PI splitting IDOC and sending to Multiple JMS queues, Header segment data to header queue, Item segment data to Item queue
PI Successfully Posting data to Queues, but duplicate messages creating on target sys(One IDOC with one header and one item date, PI sending 2 header messages , two item messages to target sys) .
I did following steps
ESR
1. Created two target messages
2. Created Two target inbound interfaces
3. Created Message mapping using with multiple target messages, changed signature occurrence to 0 : unbounded , and mapped to source node to target nodes
4. Created operation mapping with one source to two target interfaces
EB
1. Created one business components and assigned one sender and two receiver service interfaces
2. Created Two receiver communication channel
3. Created One receiver determination
4. Created One interface determination , added two inbound interfaces with one operation mapping (Multiplicity is blank )
5. Created two receiver agreement
Please help .

Thanks Gouri ,
My IDOC structure (Source Message Type)
HEADER_SEG Node (0:9999) -
> MT_HEADER ( 0:unbounded) (this one of target message type)
                                                                HEADER_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
ITEM_SEG Node (0:9999) -
>MT_ITEM(0:unbounded ) (this is another message type)
                                                                ITEM_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
I tried with the below mappings
                HEADER_SEG Node -
>MT_HEADER
                HEADER_SEG Node -
> HEADER_FLDS (element )
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node -
> ITEM_FLDS (element )
2. method
                HEADER_SEG Node -
>MT_HEADER
                                                       HEADER_FLDS (element )(not mapped)
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node   ITEM_FLDS (element )(not mapped)

SAP BPC 7.5 SP 7 - Master Data Load Detected duplicate member ID

Hi Gurus I have a requirement.
I am loading the Master data for Cost Center - initially while loading master data i didnot load hierarchy. Now I started to load the Master data with Hierarchy but when ever I tried vailidate the transformation file then it is throwing the "Detected Duplicate member "
Let me show you the transformation - what I wrote there
*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER = TAB
*MAPPING
ID=ID
*CONVERSION
ID=Master_Data_Conversion.xls
Conversion Master_Data_Conversion.xls has the following code this is to remove the spaces EXTERNALINTERNAL
*js:%external%.toString().replace(/\s+/g,"")
Let me show you how I have selected the Data type - Master Data /text from NW BW Infoobject
Selection of infoobject - 0costcenter
Format - External Format
Set Selection - first Tab - Attribute I only wante the Control Area which is 1000 so - Control Area = 1000
2nd Tab - Hierarchy - Import Text node - yes Hierarchy node - xxxxxxx Version - Empty Member ID - first member Level - Blank
3rd Tab Language - English
4th Tab Attribute list - Controling Area only is selected
Note: Let me tell you that when I am loading the Master data with out Hierarchy inthe Set Selection the loading is succesful but when I am doing it with the Hierarchy as mentioned in the 2nd Tab I am getting the error as following.
Master data (dealt by table level) has errors
Detected duplicate member ID '201100'
Also, the Master data for Cost Center in the BW is a time dependent so it is having Valid to and Valid from fields which is not there to be delt in the BPC.
Please Help

@Vinay let me tell you when the BW is having the master data which is time dependent then it will have this Duplicate member as we will have duplicate cost center names which are compounded with the Time, so BW will not show an error as there is compounding but BPC do not have that feature.
The was raised with SAP and they resolved this issue.
SAP Note 1641529 - Loading Master Data gets duplicate error in special case
When running Data Manager Package 'Loading Master Data from BW
InfoObjects', 'Duplicate Members are found' error may be reported in below
case:
o In the source BW InfoObjects, there are master data that have
different lengths, and their IDs are all numeric characters. And
o If the members are sorted by their lengths first and then IDs gets
a different order compared with the one if they are sorted directly
by their IDs. Take member '122' and '1101' for instance. In BW,
they are sorted as [122, 1102]; if they are sorted directly by the
IDs, the order is [1102, 122]. And
o when running the package, the members are in both 'Attribute' and
'Hierarchy' selection, and the option Filter members by Attributes
or Hierarchies is used. And
o Select 'External Format' when running the package.
Other terms
DM, Loading Master Data from BW, Duplicate Members
Reason and Prerequisites
It's a program error.
Solution
Please apply this note or upgrade to SP11.
I hope this will help you else let me know the entire requirements so that I can provide some kind of assistance.
Do check how the master data in ur BW is then how the hierarchy nodes and costcenter nodes are there?
Good Luck
Vijay Sumith

Duplicate member names allowed dimension build

I have turned on allow duplicate members in a current ASO essbase cube to test how much rework this will require to allow duplicate aliases. After I switched the property on, I was recieving errors when attempting to associate an attribute to a dimension through a dimension build rule. I realized that I needed to use qualified member names in the load file. Here is an example of the file in Parent Child AttributeValue format
[Domestic-PD].[Test_Comm-PD]     [Test_Comm-PD].[0001-PD]      [Test_Attr-MD].[Test1-MD]
So I want to associate the attribue Test1-MD to product 0001-PD below.
Domestic-PD
     Test_Comm-PD
          0001-PD
What ends up happening is something like this
Domestic-PD
     Test_Comm-PD
          0001-PD( [Test_Attr-MD].[Test1-MD]
          [Test_Comm-PD].[0001-PD]
It attaches the attribute to the correct product but then adds an additional member. I don't want it to add the additional member. Any idea on what is happening?
Thanks for any help!

It ended up working in a different format. I changed the data file to like below. I also started over, recopying the outline, turning duplicate members on, so it is possible that there was just something off with the outline earlier.
Test_Comm-PD     0001-PD      [Test_Attr-MD].[Test1-MD]
It probably will have issues if there is a duplicate member but luckily I only will have duplicate aliases.

"duplicate member names within data preview are not currently supported"

When I clicked "Preview Data" it altered "duplicate member names within data preview are not currently supported".
What's that mean?
And I can not find anywhere to set "duplicate member names" option :(
I'm using EAS 11.1.2

I am very sad to find that "You can change false to true but cannot change true to false".

Duplicate member names in member formulae

How do you reference duplicate member names in a member formulae? In Excel or dimension building you say i.e. [TEST].[test1]. That format doesn't work in member formulae. Is anyone using duplicate name? If you do, maybe you have an answer.

In System 9 databases, you can use a "duplicate member name" outline, in which case when you have the same member name more than once in an outline, Essbase automatically tells them apart. For example, you could have a Gen3 member named "New York" with a child named "New York", or many different states with children named "Springfield", for example. Or you could have a product code named "100" and also a customer code named "100". You don't have any control over how the names are constructed, and unfortunately the automatically-generated name for a member may change if a duplicate for it is introduced in the outline, so you really don't want to use the "unique name" values returned from API calls. You can always refer to them by using a full ancestor path, like this: [Geography].[East].[New York].[New York] I don't know for sure but I would imagine the same is true in calc scripts and non-MDX member formulas: "Geography"."East"."New York"."New York" HTH

Duplicate Member Outline and Loading Shared Members

I have an outline where I want to allow duplicate member names but in some cases I will need shared members. I am trying to build the outline parent child and I cannot get it to understand the fact that I want a shared member.
Here is an example:
[market],east
[market],west
[market],other
[market].[east], nj
[market].[east], ny
[market].[west], ca
[market].[west], lv
[market].[other],[market].[west].[lv] <--- this should be shared
[market].[other],ny <--- this should not be shared
Does anyone know how to do this?

If you would like to less the charecters and if you are retrieving the data using SQL, then you could using the Substr function to restrict the characters to 80 substr( string, start_position, [ length ] )

Duplicate columns created in attribute view

Hi
I created an attribute view as shown in the video Creating an attribute view | SAP HANA using the data given. After creating the attribute view as per the video, when I preview the data in the attribute view, I see that all the columns are created twice. For instance there is Company Name and Company Name 1, Contact_Name and Contact_Name1, ContactTitle and ContactTitle1 and so on. This has happened for all the fields.
I checked the table in the schema to see if there are duplicate fields there. But the DIMSupplier table in the STS schema has no duplicate fields.
What I want to know is how were these duplicate fields created in this attribute view and how do I remove them? I checked the output fields and there also there are no duplicate fields.
When I right click on the attribute view and select data preview, and then under the tab "Distinct Values" I can see all these duplicate field names. I am trying to delete these duplicate field names but I am getting an error message that the field you are trying to delete is being used elsewhere hence it cannot be delete.
Can anyone please advise how to fix this error.
Thank you.
Regards,
Pavan.

Hi Anjali,
Thanks a lot for your reply. But in my data foundation STS_ATTRIBUTE_VIEW, I do not see any duplicate columns to remove them. Today I see a warning and also I am unable to right click on the attribute view.
The warning is given below:
Message :
STS.STS_ATTRIBUTE_VIEW: one or more columns of Table: DIMSUPPLIER have invalid ABAP name
But in the Data Foundation in the Output tab under Columns I do not have any duplicate columns listed.
Also the attribute view is in grey color. Its not in green color even after clicking on Save and Validate and SAve and Activate.
I select the attribute view and hit on the data preview button. There in the Analysis tab under Available objects under String folder I can see all these duplicate column names. I right click on the duplicate column names and I see the options "Distinct Values", "Add to labels", values, filters and "Properties". Having selected the column name I hit on the delete button on my keyboard but nothing happened.
Is this because of the warning that I am getting. What does this warning mean?
Please advise.
Thank you.
Regards,
Pavan.

SNMP: Zone: Duplicate member error message

hello
customer trying to close zone under FM
and received following error message
any advice welcomed i didnt find any reference in documentation
JYP
SNMP: Zone: Duplicate member - RWSE-02A ZoneAliasList .1401.7

Sounds like the message is complaining about a zone with a duplicate member in it. You may want to open a command line session to each of the MDS and see if you can locate and delete any duplicate zone members. You should check all the MDS switches in the VSAN, because the duplicate member could be in any one of them.
Hope this helps,
Mike

Duplicate member in ASO application

Hi,
I need to load data in an ASO application (version 11.1.2.1). Provision for duplicate members is enabled for this application and so, some of the members across dimensions have duplicate members. But during data loading, Essbase is throwing error on duplicate members and data is not loaded. Similarly, in Smart View, query is not accepted if duplicate members are selected.
Please advise if there is any work around to load data for duplicate members.
Thanks.

Hi,
one basic things is duplicate members / member aliases are not allowed within same parent.
Make sure your application is enabled for duplicates and try to create some duplicates manually and then send data through some add-in, etc. For data loads, have you tried to load them using qualifiers ?
Refer the below link for working on duplicates
[http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dotnonuq.html|http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dotnonuq.html]

Hello. I just bought my first Imac. Each family member has created an account. My question is: can each account/family member create their own imesssages, so that each family member can imessage privately?

Hello. I just bought my first Imac. Each family member has created an account. My question is: can each person use imessages privately when logged into their account? instead of everyone seeing everyones imessages? is there a way to do this?

I believe the short answer tot that is "yes" however I recommend you contact AppleCare to find out You have 90 days of free AppleCare telephone support when you buy any new Mac. This is the ideal time to begin using it. I'd also recommend that you purchase AppleCare, it will extend your 1 year warranty to 3 years and offer you 3 years of telephone support in addition to other services. You can locate the correct phone number in your part of the planet (Calgary, Canada??) by clicking Contact Apple for support and service

Duplicate IDOC created for basic type PEXR2002

Hi,
We are using PEXR2002 idoc for some document postings in FI. For a segment EIEDP02, when trying to write a BELNR field value which exceeds its size of CHAR 35. Its creating a duplicate segment with same key value. Because of this, the idoc not getting created and ends up in error.
Could you please anyone help me in this regard?
Thanks and Regards,
Vimala P

Hi,
In our process, the EIEDP02-BELNR value is actually filled with document text field value which is of length more than 35. What is happening right now is, if the length of document text having more than 35 characters and then with first 35 character of BELNR value one segment is created. And it again create one more segment EIEDP02 with BELNR value having the rest of the fields value(>35 characters). Thus creates duplicate segments which results in IDOC creation failure
Thanks and Regards,
Vimala P

Duplicate member created

Similar Messages

Maybe you are looking for