ExternamSystemId identical values error when InsertOrUpdate Campaign Object

Question

Hello,
My requirement is want to insert or update the values in Campaign object to linking with List object(its Child object of campaign)
I'm using CRMOD webservice InsertorUpdate method using proxy class.
Whenever i try to import the same data with different/same child object. Its throws the following error
For instance of Integration Component 'Campaign', using user key '[External System Id] = "1-7QH3N"', a record with identical values already exists in the Siebel database.
Please ensure that the field values in the input message are unique.(SBL-EAI-04381)
I'm getting this error when i was pass the same value for ExternamSystemId and Campain's SourceCode fields
eg: (ExternamSystemId = 1-7QH3N and SourceCode = 1-7QH3N )
is ExternamSystemId and SourceCode values should be different in Campaign object ??? if i pass different values or pass just 2 or 3 records per request then i didn't get any error. if i pass 20 records per request then it throw the above error.
Please give some advice for this issue
Thansk in advance
Best Wishes
Sathis Kumar P

Answer 1

Hi All,
Below is my SOAP Message
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<SOAPSDK1:AccountWS_AccountInsertOrUpdate_Input>
<SOAPSDK2:ListOfAccount>
<Account>
<ParentAccountExternalSystemId>990038131</ParentAccountExternalSystemId>
<stLEID>11207733</stLEID>
<stSubProfileID>2</stSubProfileID>
<plGroup_Status>Subsidiary</plGroup_Status>
*<ExternalSystemId>11207733/2</ExternalSystemId>*
</Account>
</SOAPSDK2:ListOfAccount>
</SOAPSDK1:AccountWS_AccountInsertOrUpdate_Input>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here I'm calling Upsert and a Client is already found with this Exact ExternalSystemId.
I am not updating any Name or location It should go ahead and update the Account based on the ExternalSystemId field is my understanding correct ?
I wonder why am I getting
*'For instance of Integration Component 'Account', using user key '[External System Id] = "11207733/2"', a record with identical values already exists in the Siebel database.'* in the response..
Any reasoning .....