Skip to Content
0

SAP PO XML validation result issue

Sep 16, 2017 at 11:12 AM

80

avatar image

Hi guys,

we are currently working on SOAP to RFC integration and need XML validation by adapter engine. 'validation by adapter' is checked and we got following error message only in NWA log monitoring.

SOAP: Call failed: com.sap.aii.adapter.xi.routing.RoutingException: com.sap.aii.utilxi.xmlvalidation.impl.XMLValidationException: XML Validation for payload with root element name 
SI_POS_SYNC_OUT , target namespace http://sappo.com/EN001/POS Failed!Errors Encountered During Parsing 1.cvc-maxLength-valid: Value 1212222 with length = 7 is not facet-valid with respect 
to maxLength 4 for type #AnonType_BUKRSitemDT_POS_REQ.2.cvc-type.3.1.3: The value 1212222 of element BUKRS is not valid.

we expect XML response to the sender call. Can anyone assist me to solve this issue?

<SOAP:Envelope>
   <SOAP:Header/>
   <SOAP:Body>
		<RESULT>
			<FIELD_NAME></FIELD_NAME>
			<FIELD_VAL></FIELD_VAL>
			<FIELD_ERR></FIELD_ERR>
		</RESULT>
	</SOAP:Body>
</SOAP:Envelope>
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Sedat Göç Sep 18, 2017 at 10:12 AM
0

Any update?

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 18, 2017 at 11:06 AM
0

Your request message appears to contain an element "BUKRS" (SAP Company Code) with a length greater than 4 characters (apparently "1212222"). As BUKRS is defined with a maximum length of 4 characters, the validation fails.

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Patrick,

Please don't answer after 5 Becks.

0
Former Member

Hi Sedat,

In spite of what you may believe, the stereotypical German IT consultant would not drink 5 beers by 11 am in the morning - it will at least be six already and probably something way tastier than Beck's (notice the spelling) :-)

Having clarified this important fact, let's get back to what you probably wanted to imply with your comment: Have you actually checked what I suggested? Based on the error message provided, this is the most likely cause why your request is failing - and "1212222" is definitely not a valid value for an SAP company code.

2