| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP debmas03 validation failure |
« View previous topic :: View next topic » |
| Author |
Message
|
| kevinobyrne |
 Posted: Fri Mar 13, 2009 8:28 am Post subject: SAP debmas03 validation failure |
 |
|
Voyager
Joined: 17 Jul 2007
Posts: 83
Location: Ireland
|
Hi,
I'm trying to pass an idoc through a flow with a validate node, the messageset is sap_debmas03_e2kna1m005, and it's a sequence with maxoccurs/minoccurs = 1,, so I've got every element being set (to '/'). The problem is that the element lib_itwithdrawn throws an exception:
| Code: |
<Text>cvc-complex-type.2.4.e: Unexpected element. Element "lib_itwithdrawn" is not one of the choices.</Text>
|
I can't see anything that distinguishes lib_itwithdrawn from the other elements. I understand that it's a validation error, but I just can't see anything in the mxsd that would explain it. Anyone encounter this, or anything like it? There isn't even an xs:choice in the messageset.
Thanks,
Kevin |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Mar 13, 2009 9:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
- Insert a Trace node before the Validate node.
- Compare the message tree from the Trace node with the schema
You have to be rigorous in your analysis because the error might be further up in the document ( i.e. some previous tag might be incorrect, but the problem could not be detected until lib_itwithdrawn was reached ). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 14, 2009 1:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| kimbert wrote: |
- Insert a Trace node before the Validate node.
- Compare the message tree from the Trace node with the schema
You have to be rigorous in your analysis because the error might be further up in the document ( i.e. some previous tag might be incorrect, but the problem could not be detected until lib_itwithdrawn was reached ). |
Could he be running an old version of the IDOC? The adapter IIRC has the capability of checking the document against SAP's definition in real time.
So if the realtime definition is different from the buildtime definition what happens? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kevinobyrne |
| Posted: Sun Mar 15, 2009 3:11 am Post subject: Resolved |
|
|
Voyager
Joined: 17 Jul 2007
Posts: 83
Location: Ireland
|
Turns out that with 2 different SAP instances, the messagesets were slightly different.
SAP1 had the field lib_itwithdrawn (KATR1) and SAP2 had the field facilitystatus (KATR1). So the broker was correct to throw a validation error. This is the case with 3 of the fields in the debmas03 msgset. I'll have to talk to the SAP team. |
|
| 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
|
|
|
|
