| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| A Message Set can not contain two global type definitions |
« View previous topic :: View next topic » |
| Author |
Message
|
| tatyeong |
 Posted: Wed Sep 15, 2010 6:51 am Post subject: A Message Set can not contain two global type definitions |
 |
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Hi,
I have a message flow that uses an SAP inbound adapter and convert the idoc into XML before putting in a MQ queue.
Recently there is an additional field added to the IDOC structure. Instead of regenerating the message set using the SAP adapter wizard, I manually added the new field in one of the mxsd file.
When I clean and rebuild the message set project, I get the following error. Even as I undo the changes by restoring the original mxsd file, I am still getting the same error.
| Code: |
A Message Set can not contain two global type definitions with the same name and namespace (target or chameleon): 'http://www.xyz.com/types/crm/sapzmdbupainboundmainsave01z201tbuseibupatelephone000#SapZMdBupaInboundMainSave01Z201tBusEiBupaTelephone000' MSP_CRM_BPandBPRFromCRM/MS_CRM_BPandBPRFromCRM/com/xyz/www/types/crm/sapzmdbupainboundmainsave01z201tbuseibupatelephone000 SapZMdBupaInboundMainSave01Z201tBusEiBupaTelephone000.mxsd line 548 |
Can anyone tell me what this error means, and how do I correct the error?
Appreciate any help on this |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Sep 15, 2010 11:19 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| It means exactly what it says. What don't you understand? |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Sep 15, 2010 11:25 am Post subject: Re: A Message Set can not contain two global type definition |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| tatyeong wrote: |
Hi,
I have a message flow that uses an SAP inbound adapter and convert the idoc into XML before putting in a MQ queue.
Recently there is an additional field added to the IDOC structure. Instead of regenerating the message set using the SAP adapter wizard, I manually added the new field in one of the mxsd file.
When I clean and rebuild the message set project, I get the following error. Even as I undo the changes by restoring the original mxsd file, I am still getting the same error.
|
Wrong way, dont do it atleast this kind of manipulation for IDocs later at one point you will get more errors.
its better to re-discover the idoc BO from SAP, how did you confirm the headers of SAP IDoc, did any ABAP developed told you this, i am damn sure there you might have went wrong.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| tatyeong |
| Posted: Thu Sep 16, 2010 4:59 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
I guess there is no shortcut. I did get the Idoc header from the ABAP developer.
Anyway, I regenerate the BO and all is fine.
Thanks |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Sep 16, 2010 5:43 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| tatyeong wrote: |
I guess there is no shortcut. I did get the Idoc header from the ABAP developer.
Anyway, I regenerate the BO and all is fine.
Thanks |
its better to discover the BO from SAP ECC rather than updating manually.
the reason is ABAP developer do a lot of version changes on SAP Side.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
