| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The object name is not set on the business object |
« View previous topic :: View next topic » |
| Author |
Message
|
| tatyeong |
 Posted: Wed Aug 25, 2010 11:23 pm Post subject: The object name is not set on the business object |
 |
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Does any one knows what this error means? I tried to do a search on google but couldn't find anything on this.
BIP3450-throw a RecordNotFoundException--com.ibm.j2ca.extension.metadata.exceptions.InvalidMetadataException: The object name is not set on the business object.
My WMB message flow contains a SAP outbound adapter, and I use configurable services to maintain the SAP connection parameters. When I compile the project and build the BAR there is no error.
However when I tried to send a message through the message flow to SAP, I receive this error.
Any help is appreciated |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Aug 26, 2010 7:13 am Post subject: Re: The object name is not set on the business object |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| tatyeong wrote: |
Does any one knows what this error means? I tried to do a search on google but couldn't find anything on this.
BIP3450-throw a RecordNotFoundException--com.ibm.j2ca.extension.metadata.exceptions.InvalidMetadataException: The object name is not set on the business object.
My WMB message flow contains a SAP outbound adapter, and I use configurable services to maintain the SAP connection parameters. When I compile the project and build the BAR there is no error.
However when I tried to send a message through the message flow to SAP, I receive this error.
Any help is appreciated |
Re-discover your IDoc again, it is missing one of the BO in the IDoc Sets.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| tatyeong |
| Posted: Thu Aug 26, 2010 5:25 pm Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Thanks Gaya,
But if that's case, why doesn't it gives any error when I build the message set and message flow? |
|
| Back to top |
|
|
| Maximreality |
| Posted: Fri Aug 27, 2010 12:41 am Post subject: |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
| tatyeong wrote: |
Thanks Gaya,
But if that's case, why doesn't it gives any error when I build the message set and message flow? |
Your messageset is a representation of the data format in SAP, it was taken as a snapshot. When you build your BAR file no validation against SAP is done.
So in your case it seems like someone changed the format in SAP, if this is done without re-discovering the IDoc, you will get an error when SAP starts sending messages in the new format.
As far as i remember this "issue" is similar to what would happen on SAP's own integration platform (SAP PI) when changing the idoc structure in WE30 |
|
| Back to top |
|
|
| tatyeong |
| Posted: Fri Aug 27, 2010 12:49 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Thanks.
It works now when I use the SAP adapter wizard to re-create the message set |
|
| 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
|
|
|
|
